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

Edge 830 Version 8.00 Bugs

Luko79
over 3 years ago

As i expected, the 8.00 still contains the previous bugs what i wrote down many times here (too):

#1: GPS LAT/LON position duplication due to bad low priority coding (the cpu doesnt get back new GPS position within 1sec due to bad low priority coding and in this case it is using the latest known position which makes duplication...), i have 19pcs duplicated positions during a 140mins ride (sometimes more, if somebody needs i can check the previous activities with 8.00fw), these duplications happened today within a 4mins window ( between 49.5min - 53.5min), there is no active BT connection during the ride, no route, no segment, no workout, so nothing started in the background. GPS+GALILEO setting but the GNSS setting is irrelevant as i experienced

#2: Record skipping bug , always there is 1 skipped record in the FIT file, today at the 123mins: 

751800 2021. 06. 16. 15:18:02
751900 2021. 06. 16. 15:18:03
752000 2021. 06. 16. 15:18:05
752100 2021. 06. 16. 15:18:06

#3: Comm chip (ANT+) resetting, dropped my powermeter, hrm and speed sensor's signal after ~35mins: 

Timestamp PosLat PosLong Altitude Distance GPSDistance HeartRate Cadence Speed Power
2021. 06. 16. 13:49:35 47,73636265°N 9,07911315°E 449,6 [1] 17,55112000 [6] 17,61077000 132 [4] 98 [5] 51,83 [6] 228 [5]
2021. 06. 16. 13:49:36 47,73623952°N 9,07915740°E 449,2 [1] 17,56558000 [6] 17,62485000 132 [4] 98 [5] 52,00 [6] 211 [5]
2021. 06. 16. 13:49:37 47,73611337°N 9,07918481°E 448,6 [1] 17,57992000 [6] 17,63903000 133 [4] 98 [5] 51,66 [6] 217 [5]
2021. 06. 16. 13:49:38 47,73598588°N 9,07919663°E 448,4 [1] 17,59433000 [6] 17,65323000 132 [4] 98 [5] 51,83 [6] 0 [5]
2021. 06. 16. 13:49:39 47,73585605°N 9,07919051°E 448,2 [1] 17,60873000 [6] 17,66767000 132 [4] 98 [5] 51,83 [6] 0 [5]
2021. 06. 16. 13:49:40 47,73572722°N 9,07916159°E 448,0 [1] 17,62312000 [6] 17,68216000 132 [4] 0 [5] 51,83 [6] 0 [5]
2021. 06. 16. 13:49:41 47,73560015°N 9,07911155°E 447,6 [1] 17,63773000 [3] 17,69678000 132 [4] 0 [5] 51,83 [3] 0 [5]
2021. 06. 16. 13:49:42 47,73547945°N 9,07903771°E 447,2 [1] 17,65222000 [3] 17,71130000 132 [4] 0 [5] 52,20 [3] 0 [5]
2021. 06. 16. 13:49:43 47,73536763°N 9,07894132°E 446,6 [1] 17,66658000 [3] 17,72568000   98 [5] 52,20 [3] 208 [5]
2021. 06. 16. 13:49:44 47,73526789°N 9,07882498°E 445,8 [1] 17,68068000 [3] 17,73979000   98 [5] 51,96 [3] 218 [5]
2021. 06. 16. 13:49:45 47,73518004°N 9,07869388°E 445,6 [1] 17,69454000 [3] 17,75365000 132 [4] 98 [5] 51,12 [3] 218 [5]
2021. 06. 16. 13:49:46 47,73510377°N 9,07854812°E 445,2 [1] 17,70795000 [6] 17,76749000 132 [4] 92 [5] 48,27 [6] 218 [5]
2021. 06. 16. 13:49:47 47,73503722°N 9,07839088°E 445,2 [1] 17,72115000 [6] 17,78141000 132 [4] 96 [5] 47,53 [6] 205 [5]
2021. 06. 16. 13:49:48 47,73498558°N 9,07822626°E 445,0 [1] 17,73423000 [6] 17,79503000 131 [4] 97 [5] 46,82 [6] 222 [5]
2021. 06. 16. 13:49:49 47,73494175°N 9,07805745°E 445,0 [1] 17,74705000 [6] 17,80859000 131 [4] 96 [5] 46,39 [6] 224 [5]

when is the fix expected? still in this century?

  • 0 over 3 years ago

    I have the same ANT issue consistently where it drops all connections for 2-5 seconds and then grabs them all again. On a long ride this happens a few times. 

  • 0 over 3 years ago

    New Recovery Time calculation between Forerunner 945 and Edge 830 isn't syncing correctly, most of the time there are differences, when the Forerruner 945 increases Recovery Time!

  • 0 over 3 years ago in reply to f|33tStA

    check the heart rate zones, i experienced a few times that the HR zone calculation method changed somehow in the 830 (from HRR% to MAXHR%, and i didnt change anything nowhere...), and my HR zones were changed and gave totally false exercise load/vo2max and recovery also... so probably not the firstbeat reco calculation method changed just only the parameters... Slight smile

  • 0 over 3 years ago in reply to Luko79

    i have same HR Zones ond FR945 and Edge830, everything is correct there, it's for sure the Firstbeat Thing

  • 0 over 3 years ago in reply to f|33tStA

    i had the same with my wristwatch, and somehow in the Edge it changed , in the watch did not ... i checked the activities in GC and found the problem immediately (there were different hr zones in the 2 activities from the 2 devices). But it could be FirstBeat thing too, "fortunately" we have a wide range of sources of problems... Laughing

  • 0 over 3 years ago in reply to Luko79

    on FR945 the Recovery Time increases when you don't start an activty, for example when you go only 10.000 steps in arround 45 minutes (you get only a Popup on your watch like high activity detected and so you have to make more recovery), this increases for example don't sync to Edge.

  • 0 over 3 years ago

    Add training status is reset for some of us to the bug list

  • 0 over 3 years ago

    Unfortunately, I have the same problem. After changing the software on my Edge 830 to version 8.0 it keeps restarting when changing profiles. Now it cannot be used. It should never have happened. Quick software update and repair is needed.

  • 0 over 3 years ago in reply to portege

    You must do a factory reset, usually that solves this software restarting issue. Probably something got corrupted there (profile or device xml), so better to start and test again with a "clean" device.