Navigation Activity Info doesn't seem to work in 1.3 on Fenix 3 beta 7.31

I have setup a simple data field to output the new distance to next point and name of next point activity info. I have side loaded on to a Fenix 3 with no issue using the new beta 7.31 firmware. I have no problem getting the code to work with most normal data fields only when accessing new navigation info for a course. The course does have waypoints as the they are displayed using the WPT. NEXT and DIST. NEXT fields. As the simulator doesn't support course files yet any ideas? Very simplistic code below.

using Toybox.WatchUi as Ui;

class SimpleFenixDataFieldView extends Ui.SimpleDataField {

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

//! The given info object contains all the current workout
//! information. Calculate a value and return it in this method.
function compute(info) {
// See Activity.Info in the documentation for available information.

// Check if data field exists if so display if not No Data my friend
if (info has :nameOfNextPoint) {
// the feature is supported

if (info.nameOfNextPoint != null) {
return info.nameOfNextPoint;
}
else {
return "No Next";
}

}
else {
return "No Points";
}


}

}
  • It's not clear whether these features will be available in Fenix 3 or not yet. These were added in anticipation of the Oregon 7xx, and while it makes sense to have these available on the Fenix, we're squeezing every last bit of space we can out of it. If it's possible, these may be included, but right now it's uncertain.
  • Bummer we https://www.bestbikesplit.com/ wanted to use that to really fine tune some of our power target race execution using this data to pull power targets by specific lat long to provide it to the athlete.
  • The feature would be extreamly usefull for datafields for ultra running races where you have cut of times that have to be considered.
    If thats not possible exposing the distance remaining would go a long way.
    I have made a datafield for a trail race but as it is now I can only use the elapsed distance and if the runner takes the wrong rout and have to go back that will get off by quite a lot or bad GPS distance data on tracks with lots of switchbacks.
  • Brandon,

    Any hope to get access to this data in the Edge units? Seems Odd the documentation would have it but then each device that is compatible could choose to expose it or not. Though understandable for devices that don't support certain types of data (power for instance) since many devices do support navigation seems the navigation data described in the new SDK would be available if the data was implemented on the device. Maybe you guys could release a new matrix of activity info and what devices will support the different data points. That way developers aren't spending time working on projects that may not actually be viable. Really looking forward to this update just hope some sport devices will support it.
  • 100

    It's not clear whether these features will be available in Fenix 3 or not yet. These were added in anticipation of the Oregon 7xx, and while it makes sense to have these available on the Fenix, we're squeezing every last bit of space we can out of it. If it's possible, these may be included, but right now it's uncertain.


    The navigation data also does not seem to work on the new 520/1000 beta firmware updates. Is there any plan to bring any of the navigation data to the sports devices?
  • Is the navigation data there in the new Fenix 7.36 Beta?

    This is the last big missing part in my opinion..
  • I don't get it.
    How do I know Info.elevationAtNextPoint is not supported on fenix3?
    There is FW CIQ 1.2 and 1.3 for fenix3.
    There is SDK 1.2.x.
    I can build data field using all this and it still not working on watch?
    How do I know whats working whats not?

    Info.elevationAtNextPoint is since 1.2.10.
  • Nocara

    The navigation data also does not seem to work on the new 520/1000 beta firmware updates. Is there any plan to bring any of the navigation data to the sports devices?


    Still no navigation data access it seems :(.
  • It's not clear whether these features will be available in Fenix 3 or not yet. These were added in anticipation of the Oregon 7xx, and while it makes sense to have these available on the Fenix, we're squeezing every last bit of space we can out of it. If it's possible, these may be included, but right now it's uncertain.



    I couldn't find any info about current FW CIQ for Oregon. I might release my datafield at least just for Oregon 7xx.

    On fenix3 there are native data fields Distance remaining, Distance Next, Vert Distance Destination. Are those DFs different then the new ones in SDK 1.2.10(distanceToDestination, distanceToNextPoint, elevationAtDestination, elevationAtNextPoint)?
    Doesn't look like performance issue with implementing them for CIQ for fenix3. There is only elevationAtNextPoint not implemented already.
  • I couldn't find any info about current FW CIQ for Oregon. I might release my datafield at least just for Oregon 7xx.

    https://forums.garmin.com/showthread.php?357783-Data-Field-Connect-IQ-version
    Version is 2.50, it has CIQ 1.2.10. I can test your app in device. Looks like such test should collect more information from real devices - "has" every feature/function/module or not.