CIQ Field on OLD Devices

My client has some published legacy CIQ apps for OLD devices. This one was last released in 2018. SDK 1.4.

I can't even find ForeAthlete in the device options in the manifest. Would 920XT work for this device, even though back in 2018 it is listed as a distinct device?

The app compiles but doesn't run in the simulator (SDK 9.1.0). Normally it should tell me the memory limit at the bottom I believe, but this lists 0.0kb, so I'm not sure what these device limits are. Maybe 16kb? And the debug console doesn't report an Out of Memory fault.

Probably not worth trying to keep these up to date. But is it even possible to refresh an app for these devices?

Top Replies

peterdedecker 5 days ago +2

foreathlete is the asian name for forerunner, it's normal you don't see it in the devices you can select for the manifest. If you select the fr920xt it'll also build the asian models (but you will probably…

All Replies

0 flowstate 4 days ago in reply to DaveBrillhart

DaveBrillhart said:
There is a device generations with primary names: Quatix 6 and Fenix 6. But not Quatix 3, 5, 7, or 8. So to build for those we need to select the Fenix devices in manifest. Just another inconsistency. This table helps disambiguate those.

The secondary device names are included in the display names (from compiler.json) in the product selection list when you select Monkey C: Edit Products in VS Code:

So it's not strictly necessary to look at the device types API.

As I said above (and actually multiple times over the years, in threads that you started or were part of), the device types API is good when you want to map a specific model in the CIQ web store to a part number in *\compiler.json or vice-versa.

It's especially useful when dealing with variants which aren't shown in the display names from compiler.json (like ForeAthlete, for example).