Connect IQ 2.1 SDK Preview!

The Connect IQ version 2.1 preview SDK is now available on the developer site!

We're excited about this release because it adds a bunch of new features that many Connect IQ developers have been asking for, like custom FIT recording, OAuth, Widget & App support for Edge products, and more! You can find out all about it and download it here:

http://developer.garmin.com/index.php/blog/post/connect-iq-2-biker-monkey

Since this is a preview, you won't be able to export apps for submission to the app store, but you can build apps to side load to your own device for development and testing purposes. Please give it a try! If you have feedback or notice any bugs, you can post to this forum or send your comments to the Connect IQ team at [EMAIL="[email protected]"][email protected][/EMAIL].

Thanks!

- The Connect IQ Team

Former Member over 9 years ago

VivoactiveHRGuy-

What is it you see that's weird in playing back a .fit? I've played back many with smart and 1-sec recording, and the only thing I see that's different is elapsedDistance - it's incorrect in the 2.1.0 simulator. I reported that one to Garmin and I'm sure will be fixed.

Yes .. the elapsed distance is what I am seeing the problem with. Definitely a problem.

Former Member over 9 years ago

Trying to set ANT channel to CHANNEL_TYPE_TX_NOT_RX crashes FR630 with

ERROR: Unhandled Exception
DETAILS:
STORE_ID: 00000000000000000000000000000000
CALLSTACK:

Former Member over 9 years ago

Input on Edge520

Hi,

I've been writing a widget on the Edge 520 with the new SDK and learned something that others may find useful.

Unlike the in the simulator, you don't get access to all the buttons. In fact you only get one, the select button, which generates onSelect (pressed) and onMenu (held) events.
The page up and down buttons are not available as input events - they cycle through installed widgets!

Back to the drawing board. :o

Great update by the way!

Kyle.ConnectIQ over 9 years ago

Trying to set ANT channel to CHANNEL_TYPE_TX_NOT_RX crashes FR630 with

Thanks for the report. We'll see what's going on.

Kyle.ConnectIQ over 9 years ago

Hi,

I've been writing a widget on the Edge 520 with the new SDK and learned something that others may find useful.

Unlike the in the simulator, you don't get access to all the buttons. In fact you only get one, the select button, which generates onSelect (pressed) and onMenu (held) events.
The page up and down buttons are not available as input events - they cycle through installed widgets!

Back to the drawing board. :o

Great update by the way!

The up/down keys generate the onNextPage and onPreviousPage events, which are not available to the first view of a widget. If you push a second view in your widget you can then access these buttons. This behviour is the same across all devices.

Former Member over 9 years ago

The up/down keys generate the onNextPage and onPreviousPage events, which are not available to the first view of a widget. If you push a second view in your widget you can then access these buttons. This behviour is the same across all devices.

Thanks for the tip! I added a "start screen" as an initial view, all working as expected. :cool:
Now to test it out on the MTB Trails! :)

MattinG over 9 years ago

Hi,

I update hrTSS app with 2.1 implementing to save metric in fit file with FitContributor.

Initialize: fit = createField("hrTSS", 6869, Fit.DATA_TYPE_DOUBLE, {});
onTimerReset: fit.setData(hrTSS);

I test with edge 520 624 beta firmware and dont work.

Where i can find info or example about how to save metrics to fit file?

Thanks

travis.vitek over 9 years ago

If you are setting the hrTSS value once for the entire session, you most likely want to set the the message type option when creating the field... Additionally, is there some reason that you used 6869 for the data field id instead of starting with 0?

I believe that some have noticed that the timer functions are not being called consistently, or at all, for some devices. You might want to verify that onTimerReset() is getting called. It might not hurt to set the value in more than just one place.

class TssDataField extends Ui.SimpleDataField
{
    hidden var fitField;

    function initialize() {
        fitField = createField("hrTSS", 0, FitContributor.DATA_TYPE_UINT16, {
            :mesgType => FitContributor.MESG_TYPE_SESSION
        });
    }

    hidden var hrTSS;

    function compute(info) {
        // update hrTSS

        return hrTSS;
    }

    function onTimerReset() {
        fitField.setData(hrTSS);
    }

    function onTimerPause() {
        fitField.setData(hrTSS);
    }

    function onTimerStop() {
        fitField.setData(hrTSS);
    }

    function onTimerLap() {
        fitField.setData(hrTSS);
    }
}

jim_m_58 over 9 years ago

On the devices with beta FW and the 1.3.x VM, onTimerLap() isn't being called, but it works on devices that have the 2.1.0 VM.

As far as the FitContributor stuff, when you create the field, what kind of data do you create?

Here's what I use for lap data. What seems to happen is that the data can be updated many times, but only saved on a lap in this case:

fc1Field = session.createField("fc11", FC1_FIELD_ID, FitC.DATA_TYPE_FLOAT, { :mesgType=>FitC.MESG_TYPE_LAP, :units=>"things" });

There is a utility called "monkeygraph" in the preview SDK, but I've been using fittocsv first to see if the .fit from the simulator looks OK is the best start.

Former Member over 9 years ago

I am experiencing some weird lines that appear on the surroundings of some rectangles I'm drawing. The rectangles appear clean on the device, but on the simulator these lines are popping around. The same code was clean on the simulator on the previous SDK. Of course this is not a nightmare, but it's something that looks like a bug.