Additionally, a new screen with torque information (variable).
The intent is that you should always get this screen after you do a zero calibration. The display shows the sum of the torques applied to the two pedals. This is so that you can do scale factor verification by hanging a weight from either pedal (and if necessary, make an adjustment).
The Edge 1030 seems to have a problem in the current firmware, where it does not always bring up the torque report screen. It's being investigated but no estimate of when this behaviour will be corrected.
The Edge 1030 seems to have a problem in the current firmware, where it does not always bring up the torque report screen. It's being investigated but no estimate of when this behaviour will be corrected.
I, too, have noticed that when you follow the prompted calibration that appears when the device first wakes up and connects with my Edge 1030 you eventually see the simple, unchanging ‘[FONT=courier new]0[/FONT]’. However, if I manually initiate calibration, then I see the display with the ongoing, fluctuating sensor zero torque reading with two decimal places (e.g., ‘[FONT=courier new]0.06’[/FONT]).
I don’t really know what to make of the different displays.
I, too, have noticed that when you follow the prompted calibration that appears when the device first wakes up and connects with my Edge 1030 you eventually see the simple, unchanging ‘[FONT=courier new]0[/FONT]’. However, if I manually initiate calibration, then I see the display with the ongoing, fluctuating sensor zero torque reading with two decimal places (e.g., ‘[FONT=courier new]0.06’[/FONT]).
Thanks, that was helpful information that will help the Edge team zero in on the issue.
I don’t really know what to make of the different displays.
Should I worry about it?
The "Calibration successful - 0" display is the simple result code that tells you that the zero offset succeeded.
The torque display with the decimal values will tell you how much load is currently being detected by the pedals, but that is intended as an additional validation tool and is not critical to the zero calibration itself.
Using Vector 3 with an Edge 520. When I first got the Vectors the calibration process always returned a value of zero. I have recently noticed, as others have reported above, that for a little while now I get a "Calibration Successful" message and a non-zero torque value. In particular, although this may have been going on a while, I have just noticed that the torque value is constantly changing - in a range of about +/- 0.30 and sometimes just shows -- (i.e. two dashes) instead of a value. This happens whether it is the initial prompted calibration or a manual calibration. I see someone reporting this above and from the reply it seems that this might be a problem that needs attention. Can someone clarify?
Whether or not a coincidence, I have also noticed over the last week or so that my Vectors are no longer closely tracking my Neo in power numbers. For the first couple of months Vector power numbers for rides in Zwift and Traineroad were typically within 1% of the Neo numbers whereas they now vary +/- about 5%.
Ok, following my post above I have now noticed I have some sort of issue with the right pedal. Just did two short (5-10min) rides with the pedals on my trainer. Looking at the ride data in Garmin Connect on-line the first thing I notice is that whereas the plot for the Left Platform Offset is the usual wiggly line, the plot for the Right is just a dead straight line - i.e. no data. Looking at the ride stats I see a L/R balance, and L/R Pedal smoothness and TE figures, but there is no option to view cycling dynamics. Looking at the same rides in the mobile Connect App under cycling dynamics I only see figures for the left pedal. Now I did get a message about the Right pedal not being found at the start of the ride, but I just turned the pedals and performed the calibration and then assumed all was fine because I was seeing L/R power balance numbers. Not sure whats going on but its does seem I have some sort of problem and would appreciate some input from Garmin.
