Firmware 22 bug report

Maintenance, accessories, operation. Anything to do with making your erg work.
Post Reply
Dunadan
Paddler
Posts: 2
Joined: July 3rd, 2016, 7:30 am

Firmware 22 bug report

Post by Dunadan » July 3rd, 2016, 7:35 am

Hello everyone,

I have two issues with FW 22 :
- stroke rate randomly displayed much too high
- damping factor displayed : 995 (!)

I have a brand new model D...

Pierre

chrisl
500m Poster
Posts: 68
Joined: April 9th, 2013, 5:48 pm
Location: North-west UK

Re: Firmware 22 bug report

Post by chrisl » July 4th, 2016, 1:10 am

Hi, I've seen these same symptoms.

- I've seen stroke data spike when stroke rate has changed on a number of PM5s running firmware 22. It appears to be related to the algorithms which calculate stroke rate getting thrown by rates of change, especially after a momentary pause. It seems that the PM5 interprets a number of 'outliers' when that happens. I've seen the same issue on the data provided by ErgData. I don't know whether that's because ErgData is taking the outliers and uploading them, or whether ErgData is making the same buggy calculations, or both. This has also been discussed at http://www.c2forum.com/viewtopic.php?f=10&t=112886 with an example graph on the second page.

- A few days ago I was viewing my drag factor on one PM5 running firmware 22. One stroke would show the drag factor, the next would show 995 and this sequence repeated with each stroke.

Regards,
Chris

User avatar
c2jonw
6k Poster
Posts: 602
Joined: April 3rd, 2006, 1:08 pm

Re: Firmware 22 bug report

Post by c2jonw » July 5th, 2016, 9:22 am

Bug reports are best sent to rowing@concept2.com.
There have been no changes to the rowing code between 22 and prior versions. If you think this is specific to v22, the best way to test this is to revert to an older version of firmware and confirm the problem goes away. To obtain an older version, please write to Scott Hamilton or rowing@concept2.com and we can send an older copy by download link or via email.
The '995' drag factor seen while on the Drag Factor screen indicates that there were not enough tach pulses during a rundown to get a good DF reading.
Does this happen if someone else rows on the same rowing machine?
What does the Force Curve show when you see spikes in stroke rate?
Can you send us a video of your rowing technique when the problem occurs?
Without getting into too much detail about how the monitor works, suffice to say that the monitor is looking for the change in state when the flywheel goes from accelerating to decelerating (at the end of the drive)and from decelerating to accelerating(at the beginning of the drive). If during the drive there is a drop in force input (like a break between the legs and arms power application) that allows the flywheel to decelerate, the monitor will see that as the end of the stroke. Once power comes back and the flywheel is again accelerating the monitor sees the acceleration as the beginning of the next stroke. These “double” strokes will be displayed as high stroke rates and erroneous stroke values. Observing the Force Curve in these situations will show a double humped curve (or triple or even more if you know how to do it) rather than the prescribed single gumdrop shaped curve. See more about using the Force Curve here:
http://www.concept2.com/indoor-rowers/t ... orce-curve

Hope this helps….C2JonW
69 year old living in Waterbury Center, Vermont, USA
Concept2 employee since 1980! and what a long, strange trip it's been......and retired from C2 in October 2018!

Dunadan
Paddler
Posts: 2
Joined: July 3rd, 2016, 7:30 am

Re: Firmware 22 bug report

Post by Dunadan » July 5th, 2016, 3:00 pm

Hi,

Thanks for your answer.

The machine is new ; I just updated the FW to the latest revision available. This was the first time I was displaying drag factor.
However I very much doubt this was due to my rowing technique ; "995" was constantly displayed except for very brief moments (half a second, with a more plausible figure).

I re tried the next day, and the drag factor was correct. I have not tried again after that (setting was done).
I will let you know if it happens again.

Kind regards,

Pierre

User avatar
c2jonw
6k Poster
Posts: 602
Joined: April 3rd, 2006, 1:08 pm

Re: Firmware 22 bug report

Post by c2jonw » July 5th, 2016, 3:15 pm

Thanks Pierre- Have you had a look at your normal Force Curve for any anomalies? C2JonW
69 year old living in Waterbury Center, Vermont, USA
Concept2 employee since 1980! and what a long, strange trip it's been......and retired from C2 in October 2018!

chrisl
500m Poster
Posts: 68
Joined: April 9th, 2013, 5:48 pm
Location: North-west UK

Re: Firmware 22 bug report

Post by chrisl » July 5th, 2016, 9:39 pm

c2jonw wrote: Can you send us a video of your rowing technique when the problem occurs?
Hi C2JonW, speaking for myself, so far it's only ever happened once in all my time rowing and that was when I was displaying the drag factor (I use this function at the start of every session since I'm in a gym). My rowing technique was smooth and steady in a way which gives a normal bell curve on the force graph at around 20 spm. I remember that even more than normal because I noted how it was displaying the correct drag factor of 138 on one stroke followed by 995 on the next stroke, alternating repeatedly as I rowed. I allowed the flywheel to come to a halt and tried again with the same result. However the rowing data from the session which followed was fine and showed no anomalies.

Pie Man
5k Poster
Posts: 569
Joined: May 12th, 2016, 9:35 am
Location: UK

Re: Firmware 22 bug report

Post by Pie Man » July 6th, 2016, 5:12 am

I have seen 995 drag on one of the gym machines i use with a pm3, could it be battery level related, as the battery on that machine isn't in the best of health.
Piers 53m was 73Kg 175cm to 2019 now 78kg
500m 1:34 (HW 2020) 2k 7:09.5 (2017 LWT) 10k 39:58.9 (2016 LWT) HM 1:28:26.9 (2017 LWT)

swingshiftworker
Paddler
Posts: 32
Joined: July 1st, 2016, 6:26 pm

Re: Firmware 22 bug report

Post by swingshiftworker » August 28th, 2016, 9:08 pm

Recently had a problem w/Firmware 22-Build 2, which somehow got uploaded into my PM5. Don't recall clicking on the upgrade link but must have done that w/o realizing that I did After this happened, the PM5 could not "find" my Garmin ANT+ transmitter that I got from Concept 2.

Contacted customer service and got a reply from Scott. He said it was a known bug for Build 2 and told me how to downgrade back to the original version of Firmware 22. Problem solved. If anyone else is having the same problem, I can send you the instructions that Scott gave me or you can get them from him directly.

User avatar
Citroen
SpamTeam
Posts: 6738
Joined: March 16th, 2006, 3:28 pm
Location: A small cave in deepest darkest Basingstoke, UK

Re: Firmware 22 bug report

Post by Citroen » August 29th, 2016, 1:14 am

Go into the utility options pages and unselect the "beta" firmware option if you don't want to run bleeding edge versions and get strange surprises.

steveo0
Paddler
Posts: 1
Joined: September 19th, 2016, 3:07 pm

Re: Firmware 22 bug report

Post by steveo0 » September 19th, 2016, 3:24 pm

Hi Both,

I have been puling my air out with the same issue, heart rate monitor not being picked up, so have gone through battery changes, reversing polarity, trying a different HRM etc. Emailed C2 and John told me to 'On Utility 7.xx, shift-click the firmware update button to force it to allow you to downgrade'.

I shift/clicked the firmware update button but no option to downgrade, I guess I am still uploading 22 Beta 2 onto my USB stick as when I have taken software to the PM5, it is not giving me the option to upload the new software. Have I missed something?

Also looks at the utilities options (on the pm5?) but couldn't find an option to unselect beta firmware?

Surprising how frustrating such a little problem can be. Any help most appreciated!!

svf
Paddler
Posts: 6
Joined: October 17th, 2016, 6:12 am

Re: Firmware 22 bug report

Post by svf » October 17th, 2016, 6:20 am

Hi,

I can confirm the strange 995 drag issue. I also sometimes get error 54 "too many strokes" during the display of the drag factor.

The problem only occurs when I have a USB flash drive inserted. As soon as I remove the USB device the drag factor is displayed correctly.
"Normal" rowing with the flash drive works without any (visible) problem.

Any hints?

Cheers!

wilkes
Paddler
Posts: 18
Joined: September 25th, 2016, 7:54 pm

Re: Firmware 22 bug report

Post by wilkes » October 17th, 2016, 8:00 pm

svf wrote:Hi,

I can confirm the strange 995 drag issue. I also sometimes get error 54 "too many strokes" during the display of the drag factor.

The problem only occurs when I have a USB flash drive inserted. As soon as I remove the USB device the drag factor is displayed correctly.
"Normal" rowing with the flash drive works without any (visible) problem.

Any hints?

Cheers!
I have actually isolated this problem(995). I only get this when the USB drive is in and battery life is below 75 to 80 %. I have just accepted that I need to
set the drag factor before I insert my USB drive.
55yo 5'11 150lbs
Image

Profile: http://log.concept2.com/profile/1052542

svf
Paddler
Posts: 6
Joined: October 17th, 2016, 6:12 am

Re: Firmware 22 bug report

Post by svf » October 18th, 2016, 2:47 am

I just checked and connecting the PM5 to external power via the USB link also solves the problem or at least is another workaround. Thanks.

Post Reply