Edge 130 Plus and 3.2.x

Jim,

Thanks for that but still confused.

What is the "3.2.0" in the API docs?

Paul.

The link you posted to WorkoutStep.html doesn't actually list any supported devices, but does say "Since 3.2.0"

That's the version of CIQ which needs to be running on the device, not the SDK used to build with it.

The e130+ is still running 3.1, so when you set a min of 3.2 it's no longer a compatible device, and that's why it's grayed out as a target.

Overview

First place to look is the forum for the device:

https://forums.garmin.com/sports-fitness/cycling/f/edge-130-plus

It doesn't look like it has 3.2.x yet, but I may be wrong.  Ask someone there to check "about" on their device for the CIQ version.  If the version for the main FW doesn't end in 0, it has beta FW, and the SDK devices would be updated until it makes it to production FW.

I do see the supported devices in the SDK doc (but not the online version), and it looks like there is an error where the only edge devices are the e130 and e130+ and shouldn't be there or other edge devices should be there.  All the other devices in the list have 3.2.  Travis.ConnectIQ  Any thoughts?

I have the device. There is no reference to the CIQ version. SW version is 2.60.

Use this in a simple data field.  In the sim I see [3,1,6] (Ciq 3.1.6)

using Toybox.WatchUi;

class sdfvView extends WatchUi.SimpleDataField {

    // Set the label of the data field here.
    function initialize() {
        SimpleDataField.initialize();
        label = "CIQ Ver";
    }

    // The given info object contains all the current workout
    // information. Calculate a value and return it in this method.
    // Note that compute() and onUpdate() are asynchronous, and there is no
    // guarantee that compute() will be called before onUpdate().
    function compute(info) {
        // See Activity.Info in the documentation for available information.
        return (System.getDeviceSettings().monkeyVersion).toString();
    }

}

The code that generates our documentation isn't taking the device SDK version into account when deciding if a feature is supported or not. It can't really do that because there are multiple firmware versions possible for a device. For example, the APAC edge130 supports 3.0.1, but the WW edge130 supports 3.1.1. This means that some edge130 devices will have support for 3.1 features and others will not.

On the Edge 130 Plus - [3,2,0]

4315053 said:

On the Edge 130 Plus - [3,2,0]

But the ConnectIQ version on device doesn't have any impact on the functionality of the compiler.

The edge130plus device definition (downloaded with the SDK manager) lists the currently supported SDK version for that device as 3.1.6. This can be verified by running jim_m_58's code in the simulator, or by inspecting the device files...

C:\> findstr "connectIQVersion" %APPDATA%\Garmin\ConnectIQ\Devices\edge130plus\compiler.json
    "connectIQVersion": "3.1.6",
    "connectIQVersion": "3.1.6",

This means that the compiler doesn't believe that the device has the required support, and that means that you can't set 3.2 as a build target.

You should not need to set the minSDKVersion to 3.2 to be able to access this feature. You should able to leave it at 3.1 and then do a has check to see if the functionality is available or not. You can expect that it won't be available on the simulator, but it should work on a device that has 3.2 support.

We try to keep these numbers up-to-date, but we don't typically update them for beta firmware releases, and we often don't get them updated immediately when the production firmware is released. What firmware are you using on your edge130plus?