Related
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

DCR Tests - 735XT vs. V800 vs. Ambit3 Peak

chimpware
I downloaded Ray's data comparing the 735XT with Polar V800 (arguably the GPS watch standard for track accuracy) and I also included the Suunto Ambit 3 Peak.

http://www.mygpsfiles.com/app/#heulbCdL

My view is that overall the 735XT outperforms the V800 and the Ambit 3 Peak on this run for track accuracy, but Peak is close. In any case very happy to see that 735XT is comparable or better than V800, put's that concern to bed for me (at least based on this data from one run....)

Main concern now is elevation data for the 735. Wonder why it is so bad in this test?

Original data - https://analyze.dcrainmaker.com/#/public/27f6ec11-0dd2-43bd-7b5a-16c08beec189
  • 0
    Today's short 5K run (it was off the bike): https://analyze.dcrainmaker.com/#/public/86accc00-a0ce-4cfa-4e72-aa3fd5519a68

    Roughly similar course. With two FR735XT's (+V800, Ambit3Peak, Vivoactive HR, and FR920XT). Both elevation looks like crap.

    Note I wouldn't fret too much about one of the FR735XT have slightly wonky HR data (latches onto cadence). Typically I don't run with the extra watches and a GoPro in my hand. But for this 5K run I didn't feel like riging up the CamelBak for it. Holding objects can do similar things to all optical HR sensors (albeit rare).

    Edit to add: Note on FR735XT #2, I forgot to switch from default Smart Recording (first run with device). But firmware is current as of 4PM CET today, and GLONASS was enabled on all units.
  • 0
    Did not realize that, thanks.

    Be great if Garmin added an Ant+ barometric altimeter to the Tempe. Would solve issue of needing it onboard on a watch.


    What a brilliant idea!
  • 0
    Today's short 5K run (it was off the bike): https://analyze.dcrainmaker.com/#/public/86accc00-a0ce-4cfa-4e72-aa3fd5519a68

    Roughly similar course. With two FR735XT's (+V800, Ambit3Peak, Vivoactive HR, and FR920XT). Both elevation looks like crap.

    Note I wouldn't fret too much about one of the FR735XT have slightly wonky HR data (latches onto cadence). Typically I don't run with the extra watches and a GoPro in my hand. But for this 5K run I didn't feel like riging up the CamelBak for it. Holding objects can do similar things to all optical HR sensors (albeit rare).

    Edit to add: Note on FR735XT #2, I forgot to switch from default Smart Recording (first run with device). But firmware is current as of 4PM CET today, and GLONASS was enabled on all units.


    Looks like the 1st 735 did not have a great GPS lock along Boulevard Bourdon which can't have helped for a good elevation one bit.
  • 0
    First test run, elevation seems reasonable (with Elevation Correction On in GC) - https://connect.garmin.com/modern/activity/1175587088

    Compared to similar runs int he same park that seems about right for elevation data. I will run f3 compared to 735 on next run, today I just wanted to get used to 735 without the distraction of 2 watches (yeah I know Ray 2 watches is nothing....).
  • 0
    Yeah the elevation corrections looks fine but no particular surprise if the GPS track is reasonable - as here.

    TBH I hardly ever look at elevation on runs and rides and never quite sure why it's a "deal breaker" for some - although often it's people who aren't necessarily looking to use their device for regular triathlon type training.
  • 0
    Yeah I agree during training, not a metric I use for anything either, but I like having it for longer rides as an indication of effort, but TBH with a PM I have a real indication anyway, so probably no real need for it.
  • 0
    I downloaded Ray's data comparing the 735XT with Polar V800 (arguably the GPS watch standard for track accuracy) and I also included the Suunto Ambit 3 Peak.

    http://www.mygpsfiles.com/app/#heulbCdL

    My view is that overall the 735XT outperforms the V800 and the Ambit 3 Peak on this run for track accuracy, but Peak is close. In any case very happy to see that 735XT is comparable or better than V800, put's that concern to bed for me (at least based on this data from one run....)

    Main concern now is elevation data for the 735. Wonder why it is so bad in this test?

    Original data - https://analyze.dcrainmaker.com/#/public/27f6ec11-0dd2-43bd-7b5a-16c08beec189


    Interesting test - I wonder how F3 will blend in here? Also - was Glonass enabled on all Garmins?
  • 0
    First test run, elevation seems reasonable (with Elevation Correction On in GC) - https://connect.garmin.com/modern/activity/1175587088

    Compared to similar runs int he same park that seems about right for elevation data. I will run f3 compared to 735 on next run, today I just wanted to get used to 735 without the distraction of 2 watches (yeah I know Ray 2 watches is nothing....).


    I'm looking forward to that result Chimpware ;-)
  • 0
    TBH I hardly ever look at elevation on runs and rides and never quite sure why it's a "deal breaker" for some - although often it's people who aren't necessarily looking to use their device for regular triathlon type training.


    I agree with you Tim in that I never look at the elevation during runs but that said, Suunto is particularly marketing the Ambit 3 Vertical (A3V) to people who do run a lot of hills etc. What I would like to know is if Garmin measures 3D distance (including the altitude) or 2D (based on Lat - Lon). On the A3V at least this setting is selectable by the user.
  • 0
    Or maybe integrate Tempe with Baro into ... Footpod?


    This is still a great idea but on a second thought, all that Garmin needs to do is integrate the Stryd properly into the Forerunner. The Stryd includes both a barometric sensor as well as HR and Accelerometer. So imagine a Stryd + FR735xt giving you pretty much everything that HRM-RUN provides plus Power and proper Altitude readings.

    Even if Garmin doesn't do it, I would be interesting if Stryd could provide an app for that.

    I do know though that the Running Dynamics "channel" is proprietary to Garmin so no hope there ...