Well that is certainly odd. Have your other rows been ok? Your true stoke count should be around 950 - 1000 which would work for your observed dps . It looks like the counter hasn't reset at the start (or for a while) If you look back in your history does it all look ok? What happens if you just do a one min row? Was this done using just row?
Hopefully someone with more receive of the set up can answer this. BTW what version is the pm5 running?
New member , New model D...New me??
Re: New member , New model D...New me??
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)
500m 1:34 (HW 2020) 2k 7:09.5 (2017 LWT) 10k 39:58.9 (2016 LWT) HM 1:28:26.9 (2017 LWT)
Re: New member , New model D...New me??
Hi - yes all the others look ok, off the top of my head I think it is ver22......the erg is only two and a half weeks old, model D PM5. I'll keep an eye on this going forward
Re: New member , New model D...New me??
...and yes it was a just row.
After I did this row, I stopped and got a drink then went back and did a 1k warm down (with a new just row ) and that seemed to count correctly
After I did this row, I stopped and got a drink then went back and did a 1k warm down (with a new just row ) and that seemed to count correctly
Re: New member , New model D...New me??
My log shows bogus stroke count data as well sometimes. Not sure what the rhyme or reason is.
Ben
5' 11" 153 lbs
5' 11" 153 lbs
Re: New member , New model D...New me??
Wow. What does it look like when you download the CSV? Does it start at stroke 1?
Re: New member , New model D...New me??
At least on mine the CSV looks correct. It's just the displayed stroke count on the online Concept2 Logbook that shows the wrong number. I did not that intervals do not seem to have this issue. Hope that helps.ingtwai wrote:Wow. What does it look like when you download the CSV? Does it start at stroke 1?
Ben
5' 11" 153 lbs
5' 11" 153 lbs
Re: New member , New model D...New me??
my csv file looks fine too....must just be the logbook with issues