Firmware update creating problems?

[bobsacamano]

Ever since updating to the latest firmware, the erg seems to be having trouble writing data. Anyone else have problems? Specifically, the power curve during the row seems really jumpy (not in the bad technique way, but in the micro jumps way), and the stroke rate data seems erratic. Even the drag factor was jumping around from 110-145, and it is is usually pretty stable 125. I haven't changed anything about my stroke, and it has only been since the update. The stroke rate on the chart bounces from 22 to 80 or even 100.

Any ideas?

[GreenStratMan]

Ever since updating to the latest firmware, the erg seems to be having trouble writing data. Anyone else have problems? Specifically, the power curve during the row seems really jumpy (not in the bad technique way, but in the micro jumps way), and the stroke rate data seems erratic. Even the drag factor was jumping around from 110-145, and it is is usually pretty stable 125. I haven't changed anything about my stroke, and it has only been since the update. The stroke rate on the chart bounces from 22 to 80 or even 100.

Any ideas?

Hi I’m running v169 on a PM5 the stroke rate and drag are fine regarding stability. Will have a look at the power curve tomorrow.

[bobsacamano]

I found this that suggests some firmware updates combined with weak batteries can cause wonky stroke rate data. I'll try to replace the batteries and report back:

https://www.concept2.com/service/monito ... own-issues

[bobsacamano]

I notice that there are quite a few reports out there about spm spikes and erratic power curves, etc. Some seem to be solved by firmware updates, but others are random.

In my case it seems to have been the interaction between the PM5 and ergdata app - probably a bluetooth issue.

Initially, everything was totally fine. Then, one day it started giving crazy data. I troubleshooted and found that the wonky data only appeared when I rowed with the app connected. When I disconnected the app and just rowed, the PM5 showed everything normally. In the app settings I turned off the bluetooth and then turned it back on and reconnected, and things seem to be back to normal.

Bluetooth has always been a flakey technology, so perhaps it was just that.

[GreenStratMan]

I notice that there are quite a few reports out there about spm spikes and erratic power curves, etc. Some seem to be solved by firmware updates, but others are random.

In my case it seems to have been the interaction between the PM5 and ergdata app - probably a bluetooth issue.

Initially, everything was totally fine. Then, one day it started giving crazy data. I troubleshooted and found that the wonky data only appeared when I rowed with the app connected. When I disconnected the app and just rowed, the PM5 showed everything normally. In the app settings I turned off the bluetooth and then turned it back on and reconnected, and things seem to be back to normal.

Bluetooth has always been a flakey technology, so perhaps it was just that.

Glad you’re sorted.

My power curve looked OK, as far as I can tell. First time I’ve used it. Seems useful. Shows how much my stroke needs to improve!

Are you using a Bluetooth hrm?

[bobsacamano]

Yes, I do use an HRM. I find it is super helpful - mostly to help keep my easy rows easy.

The Power Curve is a fantastic resource. I found this classic article really helpful.

http://www.biorow.com/RBN_en_2006_files ... News05.pdf

[jamesg]

the power curve during the row seems really jumpy (not in the bad technique way, but in the micro jumps way), and the stroke rate data seems erratic.

Saw a lot of this on a PM3, and thought it was due to mains frequency interference, since the impulse stream on a machine with one sensor and three magnets is at about 50-60Hz.

Switched to PM5 but with same sensor-magnets, no spikes and force curve always smooth. So bug removed and thanks to C2.

Connected a power supply to the USB B-type socket, and immediately saw spikes. Took said supply off right away. The idea was to avoid using batteries, but gave it up. C2 erg premise being it need no connection at all at all.

Talking of which why as a "lone user" do I have to tell ED to connect to PM5? Why else did I load it and pull the handle? Same with HR, why do I have to tell PM to show HR even if the signal is from the only belt on it's list? Can't I have a default switchon option? ED has, for HR, but won't record it if nil from PM. If I Just Row, I get all the other data, why not HR? Agreed it's useless, but some like it.

[GreenStratMan]

Yes, I do use an HRM. I find it is super helpful - mostly to help keep my easy rows easy.

The Power Curve is a fantastic resource. I found this classic article really helpful.

http://www.biorow.com/RBN_en_2006_files ... News05.pdf

Do you still get problems without the hrm attached/connected?

Thanks for the link, interesting.

[bobsacamano]

Nope. HRM not related. The problem is gone now that I ensure that there is only one ergData connected at a time.