I don't own an erg, I have an OmniKey card reader at home.
The other day the batteries were replaced in a PM3 (on a model C). The date was set wrong - Nov 17th - off by a month.
I rowed a session (two workouts) on a model D with the date set right - 17th Oct. Then rowed a session (two workouts, 375m to test the machine, 5K to cool down) on the machine with the wrong date. (I set the date right after that.)
That was OK, I could read my card with the LCU and nothing special went wrong.
18th I rowed a session (three workouts) on a model D and got a "repair" when I read the card with the LCU.
Today 19th, I rowed a session (three workouts, middle one was three intervals out of a 5*1200m 5:00r variable workout).
After the warm-up 2K and the variable intervals the PM3 was giving me 137-4 errors if I tried the "list by date" option. Same happened after the 2K cool down.
Even though I couldn't use the "list by date" function I could see that the lifetime total had been correctly updated.
I added another user to the card and rowed 100m - that second user could list workout normally, no problems.
When I read the card with LCU (to create an *.LCB file for diagnostic purposes) it offered the repair option again then ran the unassigned workouts dialog. I then chose to delete the temporary user from the card and it offered the repair option again and ran the unassigned workouts dialog again (which was useful as I moved that odd 100m onto my normal user).
There's clearly a couple of logcard bugs.
1. The one I created by rowing a workout in the future then rowing another in the present.
2. The variable intervals bug that I've already documented.
http://c2forum.com/viewtopic.php?t=4966
I'll send my *.LCB file(s) by e-mail to ScottH. (I guess he's busy with preparations for BIRC right now.)
