Ik krijg van Stryd gebruikers allerlei vragen over het ondersteunen van de nieuwe Fenix 6 versies door mijn datavelden die ik in de Garmin app store heb gemaakt. De software development kit is deze week uitgebracht en gaf de mogelijkheid om te bezien hoeveel geheugen de nieuwe horloges hebben en welke lettertypen. Op basis daarvan heb ik in de Stryd Facebook groep het volgende gepost, met een kritische noot richting de gewone Fenix 6(s). Aardig om kennis van te nemen mbt beschikbaar geheugen voor lettertypen en wat de consequenties zijn van steeds maar nieuwe lettertypes in nieuwe horloges. De referenties naar mijn Datarun datavelden heb ik laten staan, maar zijn hier niet van belang. Maar wat voor mijn datavelden geldt, geldt ook voor de datavelden van anderen; een beperkt geheugen en een breder lettertype dragen kunnen ervoor zorgen dat de nieuwe Fenix 6(s) niet ondersteund gaat worden.
I just tested DataRun premium with 7 metrics in the Garmin simulator and studied the new software development kit. I was very surprised to see that the Fenix 6s and Fenix 6 have only 32kB available for datafields, but also have the new fonts that were introduced with the Marq watches. Those fonts won’t work in this datafield for the normal Fenix 6s and Fenix 6. There is not enough space for time-based metrics to display one hour or more (see the attached screenshots).
My only option is to remove functionality compared to the already limited functionality of the Fenix 5[s]; that frees up the memory to be able to use a custom font. I might find a workaround for this, but chances aren’t big that I will. So stay away from the Fenix 6[s] if you want to have the functionality that the Fenix 5[s] has.
In my opinion the available memory for datafields is the most important thing for Stryd users, as long running power isn't a native metric. Until then, most people will use the original Stryd datafield (in order to get all the footpod data) and something else what really fits them well and shows running and power metrics.
My short summary:
FR230, FR235, FR630, FR920xt, Fenix 3(HR) have 16kB available for datafields. In my eyes really not enough to show power metrics and running metrics. My Powerdashboard for Stryd (plus) is my only datafield that supports some of these (FR920xt and Fenix 3(HR)). The other watches cannot connect to bike power meters, which is essential.
32kB of memory available for datafields is better (reasonable) . It makes possible to display a balanced set of power and running metrics (I have made Datarun premium for that) or mainly running metrics with colors (Datarun plus). Watches that have 32kB available are: FR245, FR645, FR735xt, FR935, Fenix 5(s), Fenix 6(s), Vivoactive 3(m), Vivoactive 4(m), Venu. Only the watches that support bike power can use Datarun premium: FR735xt, FR935, Fenix 5(s) and maybe the Fenix 6(s) if I find a workaround for the wide native font. All watches, except maybe the Fenix 6(s), can use Datarun plus but not all will show the power metric.
The FR245m and the FR645m have 64kB available. That's nice. I have Datarun premium enabled for them, but currently they don't have power metrics. I will try this year to change that though.
The FR945, Fenix 5x and Fenix 5 plus series, Fenix 6 pro series, Marq series, D2 series and the MK Descent have 128kB available for datafields. All can receive power data and have enough memory to show all possible running and power data, with colors
[
Voor 7% gewijzigd door
Frij5fd op 13-09-2019 07:43
. Reden: Aanvulling ]