In addition, it is not possible to turn off the SRM auto zero function using an Edge 500. Here is some more information on the SRM / Edge 500 auto-zero flaw - http://alex-cycle.blogspot.com/2013/03/three-two-one-zero-offset.html. There is also a lengthy discussion on the Google Wattage forums about this.
Most of the people “discussing it” are just basing opinions off that one blog post, and have very limited understanding of how the AZO actually works. In my experience, while it has the potential to throw an error it also has the potential to be more accurate if you’re riding in variable temperatures—and the problems with it are greatly overstated. The problem seems to be that most people don’t seem to understand how to actually check the stored offset (Alex included–pulling over to check the stored ZO does not actually tell you the stored offset while you’ve been riding-you have to check it while you’re pedaling). If you’re riding in stable temps, disabling the AZO makes sense, but if you’re riding on a day or terrain with a 20-30 degree temperature change–or you’re the sort to forget to manually zero when you leave a warm house and go out into cold weather, you’re better off leaving the AZO “on”, IMO.
Not sure that’s the right blog post, I think this is the relevant one:
http://alex-cycle.blogspot.com.au/2013/03/more-zo-zen_7.html
What do you mean that you can’t check the stored ZO when stopped? Of course you can. The SRM shows you two values when you go into torque (zero offset) mode on the Powercontrol, the most recently stored ZO and the current “live” torque reading.
Why do you assume I haven’t also observed AZO behaviour while moving just because I didn’t post about it? I didn’t post such data since between the choice of taking a picture of it while moving and killing myself, I chose to be safe and stop to take a photo instead. In fact it was because I had checked while moving that prompted me to stop and record it via photo.
While moving I have seen ZO swings of hundreds of Hz while AZ is enabled (yes, hundreds of Hz), and associated ridiculous power numbers. It’s not normally as bad as that, but because there is no log of zero offset changes, who can actually know what values it stores, how frequently it updates and what level of unknown error is introduced long the way? It’s not like the AZO screen remains on forever when you go in to ZO mode.
The fact that I saw variation in the most recently set auto zero when stopped a few times, when in fact actual ZO had barely moved is sufficient to tell me that it is flawed for me. The sort of swings I would observe with AZO enabled were greater than any actual temperature induced ZO change may have been (which on my units is not all that much in any case).
As always, YMMV
Please re-read what I wrote. I didn’t say you couldn’t check the ZO when stopped–I said it’s not representative of the ZO when you’re actually pedaling–because it’s not. As soon as you stop, if a certain set of conditions are met the AZO will re-set it. I’m not asking you to make my word for it–check for yourself–but check it WHILE you’re pedaling, then check it when you stop. I have (an embarrassing number of times). Checking the ZO after stopping almost never reflects the ZO when riding, since it resets during the act of stopping.
I don’t know what you have or haven’t observed (I can only go by what you posted)–but I can tell you what I’ve observed: checking the ZO into the hundreds of times (while riding), I’ve seen 4 or 5 samples that varied more than 8 hz, and probably 10 samples that varied more than 5 hz. I also have about two dozen power files while using a 510 and 500 concurrently, with autozero set to “off” on the 510. On intervals from :30 to 15:00, 4W (on a 30 second interval) is the biggest differential I’ve seen.
Meanwhile, I’ve had the actual ZO drift by 30hz in a race (not common conditions, but it happens). Mind you, I’m not telling anyone to take my word for it. What I’m saying is that folks should experiment with it for themselves, and not be so dismissive of it because they’ve read on the internet that it sucks (no offense to you Alex, but my own experience with the AZO is that it works pretty well). In absence of the ability to do it manually (such as during a race), I can see it leading to more accurate data in certain circumstances.