Memory size limits

Any chance the data from this chart for the Biker SDK could be updated to include the Edge 820?
http://developer.garmin.com/index.php/blog/post/connect-iq-2-biker-monkey

Or maybe it would be more useful in the long run to have that information on the device page:
https://developer.garmin.com/connect-iq/compatible-devices/
That way as new devices come out then we can see the memory limits in a central place. (thouh that page looks like it hasmany errors with regard to "Available ANT+ Profiles" like the 735 not supporting power)

Also,is there any indication of CPU speed? As in from a connect IQ app perspective how to tell how much processing power is available. For example I'm guessing the Edge 1000 has much more processing power then the 920XT but how does the Edge 820 compare to the Edge 1000? So far only seen a teardown of the FR 230 to know what CPU is in that so no way of knowing CPU spec differences.

Thanks
  • You can always find the memory limits in the devices.xml file in the SDK. Also, you'll see it on the bottom line in the simulator.
  • Also,is there any indication of CPU speed? As in from a connect IQ app perspective how to tell how much processing power is available. For example I'm guessing the Edge 1000 has much more processing power then the 920XT but how does the Edge 820 compare to the Edge 1000? So far only seen a teardown of the FR 230 to know what CPU is in that so no way of knowing CPU spec differences.
    Thanks


    I agree the CPU power is a necessary information.
    In my tests I noticed a huge diference in performance in Forerunner 235. It seems to be slower than the other devices and in my personal tests it crashed running the same piece of code that runs perfectly on other devices (I compared vivoactive, vivoactive HR, Fenix and Forerunner 235).

    I am not sure if the diference is related to IO speed or CPU speed, since I did not built an app to precisely compare the processing power of the various devices

    My bet is that CPU power in forerunner 235 was lowered to save battery for the optical sensor.

    Well, the point is the more complete the info we have the more stable will be the product we deliver as developers.

    Cheers,

    Robinson
  • You might be able to look at the watchdog_count element in bin/devices.xml for the sim devices. Not all devides list a value, but I believe it may give some indication of the difference in cpu power.

    device watchdog
    ========================================
    fr920xt_sim 80000 1x
    vivoactive_sim 80000 1x
    fenix3_sim
    fenix3_hr_sim
    d2bravo_sim 80000 1x
    d2bravo_titanium_sim
    epix_sim 80000 1x
    fr230_sim 80000 1x
    fr235_sim
    fr630_sim
    vivoactive_hr_sim 120000 1.5x
    fr735xt_sim
    edge_520_sim
    edge_820_sim
    edge_1000_sim 2500000 31.25x


    It appears that there may be a default value, but I really have no good way to tell what it is.
  • Thanks for the info Travis.

    Unfortunately the fr235 and fr630 are not in the list.

    Cheers,

    Robinson
  • You can look at the CPU information provided by https://apps.garmin.com/en-US/apps/91534331-1228-47cd-8156-68458b597a7d - and test your device too. CPU power estimation is based on computation Pi value. Or invent your test to compare results of different devices.
  • You can look at the CPU information provided by https://apps.garmin.com/en-US/apps/91534331-1228-47cd-8156-68458b597a7d - and test your device too. CPU power estimation is based on computation Pi value. Or invent your test to compare results of different devices.


    Nice app to add to your data my 920xt shows speed as 0.5/9.5
  • According to CIQ developer Nicholas Kral in this video, Garmin Vivoactive processor is 48MHz. https://youtu.be/q_ghKkrl3KE?t=290

    According to my teardown of my watch, Garmin Fenix 3 processor is Freescale Kinetis K66 CPU running at 150 MHz and can run at 180 MHz in High Speed RUN mode (HSRUN, sth. like Turbo function of Intel CPUs.). (http://www.f-blog.info/diving-inside-garmin-fenix-3-tear-down-etc/)
    Fenix3 can collect more sensor data during activities and can draw basic maps via courses and waypoints. So it has a faster processor than Vivoactive. But we don't know the real frequency it runs; 'cos it is maybe downclocked for lower frequencies so that it can save power.
  • Former Member
    Former Member over 8 years ago
    I believe the Fenix runs at the same speed as the Vivoactive. If you write any sort of performance tests, you should see similar results between the two.
  • I believe the Fenix runs at the same speed as the Vivoactive. If you write any sort of performance tests, you should see similar results between the two.


    Going by A1234's app the fenix is about half the speed of the vivoactive HR. See the link to the app, he posts the results there. Would love to see an Edge 520/820/1000 comparison.
  • Following this thread, to me the best test would be a watch-app and not a data field. As a data field, it's dealing with things like compute() only running every second, and other things happening in the watch/FW at the time for the activity.

    IMHO, Let the test run in a watch-app and see what the numbers are, as that reflects what CIQ sees when the FW is running at full speed with only that app.