The gym jockeys and folks who've not learned how to program the PM5 use it. But most of those don't care about the stats, just whether they've rowed their predefined (in their head) number of calories, or five minutes or approximate distance.
Stroke count is misreported in LogBook
- Citroen
- SpamTeam
- Posts: 8010
- Joined: March 16th, 2006, 3:28 pm
- Location: A small cave in deepest darkest Basingstoke, UK
Re: Stroke count is misreported in LogBook
- jackarabit
- Marathon Poster
- Posts: 5838
- Joined: June 14th, 2014, 9:51 am
Re: Stroke count is misreported in LogBook
Everyone who has picked up the handle and pulled has done. It’s the default monitor activity in the absence of button pushes. Oooo, look! It’s DOing SOMEthing! as in Indiana Jones and The Watched Pot. It’s also convenient for short post-gasper warmdown. Beats writhing and moaning for the first few seconds.
There was this one feller on here who bragged about his habit of extrapolating times for standard distance SBs from justrows. He was rather critical of the sketchy fiddles of other aspiring clockers but quite adept at self-justifcation. IIRC, Fred Dickie disabused him of his curious notion that he was the sole arbiter of all things bright and beautiful and he promised to stop.
There are two types of people in this world: Those who can extrapolate from incomplete data
M_77_5'-7"_156lb
M_77_5'-7"_156lb
- CharleCarroll
- 500m Poster
- Posts: 56
- Joined: January 20th, 2017, 4:01 pm
- Location: San Franciso, CA USA
Re: Stroke count is misreported in LogBook
I strongly suspect that the problem with the PM5's incorrectly reporting the Total Stroke Count is in the hardware.
I think this because both Ergdata and the PM5's Firmware are up to date, and because neither has been updated recently, and because Ergdata has been accurately reporting Total Stroke Count until very recently, and because it suddenly reports the wrong type of workout.
I programmed Ergdata to report in the Logbook that the type of workout is Dynamic Indoor Rower; however when I check the Logbook it records the type as Indoor Rower. This problem has only been occurring recently but is annoying because it forces me to correct every entry for Workout Type.
So two things are being misreported in the Logbook. This leads me to wonder if it could be a microprocessor malfunction in the PM5.
As for Just Row: I have not used anything but Just Row for months now. I only started programming a single distance interval a week or so ago when the Total Stroke Count on the PM5 didn't conform to the actual Total Stroke Count. My sole focus when I row on the erg is the shape of the Force Curve, which should show Peak Force early and sustained through the drive. Pace and timing do not signify. Only the Force Curve matters.
/Charles
I think this because both Ergdata and the PM5's Firmware are up to date, and because neither has been updated recently, and because Ergdata has been accurately reporting Total Stroke Count until very recently, and because it suddenly reports the wrong type of workout.
I programmed Ergdata to report in the Logbook that the type of workout is Dynamic Indoor Rower; however when I check the Logbook it records the type as Indoor Rower. This problem has only been occurring recently but is annoying because it forces me to correct every entry for Workout Type.
So two things are being misreported in the Logbook. This leads me to wonder if it could be a microprocessor malfunction in the PM5.
As for Just Row: I have not used anything but Just Row for months now. I only started programming a single distance interval a week or so ago when the Total Stroke Count on the PM5 didn't conform to the actual Total Stroke Count. My sole focus when I row on the erg is the shape of the Force Curve, which should show Peak Force early and sustained through the drive. Pace and timing do not signify. Only the Force Curve matters.
/Charles
-
- 1k Poster
- Posts: 136
- Joined: March 30th, 2016, 3:00 pm
- Location: Finland
Re: Stroke count is misreported in LogBook
What is this then Had started using ErgData only two days prior to that..CharleCarroll wrote: ↑July 4th, 2020, 4:27 pm... Ergdata has been accurately reporting Total Stroke Count until very recently...
- Citroen
- SpamTeam
- Posts: 8010
- Joined: March 16th, 2006, 3:28 pm
- Location: A small cave in deepest darkest Basingstoke, UK
Re: Stroke count is misreported in LogBook
It's not the hardware. It's most likely a firmware bug in the routines that run "Just Row".CharleCarroll wrote: ↑July 4th, 2020, 4:27 pmI strongly suspect that the problem with the PM5's incorrectly reporting the Total Stroke Count is in the hardware.
I think this because both Ergdata and the PM5's Firmware are up to date, and because neither has been updated recently, and because Ergdata has been accurately reporting Total Stroke Count until very recently, and because it suddenly reports the wrong type of workout.
I programmed Ergdata to report in the Logbook that the type of workout is Dynamic Indoor Rower; however when I check the Logbook it records the type as Indoor Rower. This problem has only been occurring recently but is annoying because it forces me to correct every entry for Workout Type.
So two things are being misreported in the Logbook. This leads me to wonder if it could be a microprocessor malfunction in the PM5.
As for Just Row: I have not used anything but Just Row for months now. I only started programming a single distance interval a week or so ago when the Total Stroke Count on the PM5 didn't conform to the actual Total Stroke Count. My sole focus when I row on the erg is the shape of the Force Curve, which should show Peak Force early and sustained through the drive. Pace and timing do not signify. Only the Force Curve matters.
/Charles
- CharleCarroll
- 500m Poster
- Posts: 56
- Joined: January 20th, 2017, 4:01 pm
- Location: San Franciso, CA USA
Re: Stroke count is misreported in LogBook
My first row on the Dynamic Indoor Rower (DIY) was 17 January 2017. Since then I have rowed over 13,000,000 meters on the DIY, nearly all of which were produced with Type of workout set to Just Row. And I do mean all! Until a few weeks ago everything was working as designed. Now suddenly the PM5 is making incorrect entries in my Logbook. Why?Citroen wrote: ↑July 5th, 2020, 4:52 amIt's not the hardware. It's most likely a firmware bug in the routines that run "Just Row".CharleCarroll wrote: ↑July 4th, 2020, 4:27 pmI strongly suspect that the problem with the PM5's incorrectly reporting the Total Stroke Count is in the hardware.
Tomorrow I am calling Nathan at Tech Support at Concept2. The last time I talked with Nathan he asked for the PM5's Product ID. I have had enough experience with microprocessors to know that Nathan may be looking for a range of PM5s which may have been shipped with faulty chips. This was 3 days ago. Nathan even offered to send me a replacement PM5. But I declined Nathan's offer because I wanted to do more testing.
The price of Concept2 ergometers has been and continues to be an absolute bargain. These machines are well designed and well built, and Concept2 is to be lauded for how it keeps the price affordable. I suspect that the cost of a C2 ergometer would increase considerably were Concept2 to demand that every silicon wafer put into a PM5 be thoroughly tested. Perhaps I am revealing my age, but wasn't the old rule of thumb that if a chip ran for 90 days without failing, it would probably run a lifetime? Of course as with all rules there are exceptions, aren't there?
/Charles