I found that its your PM5 and phone combo that makes the difference.
I have an older Samsung Galaxy A3(2017) and I CANNOT use the latest V169 PM5 firmware with it so I had to roll back to V168 which works faultlessly.
The phone just disconnects randomly and it was a total dog on V169. I have a much later Samsung S20FE 5G now but that's not for running ErgData and runs the RowedBiker App for Zwift. The newer phone would probably work perfectly for ErgData with the PM5 on V169. I believe they made changes to the Bluetooth stack but that stuff is over my head but essentially if it doesn't work, it doesn't work and you need to find a combo that does.
Stroke Count wrong
-
Carl Watts
- Marathon Poster
- Posts: 4690
- Joined: January 8th, 2010, 4:35 pm
- Location: NEW ZEALAND
Re: Stroke Count wrong
Carl Watts.
Age:56 Weight: 108kg Height:183cm
Concept 2 Monitor Service Technician & indoor rower.
http://log.concept2.com/profile/863525/log
Age:56 Weight: 108kg Height:183cm
Concept 2 Monitor Service Technician & indoor rower.
http://log.concept2.com/profile/863525/log
Re: Stroke Count wrong
That was my impression too, Carl, and seemed to relate to how the PM5 and the mobile devices handle things like bluetooth beacons. I know that some devices - some smart bulbs, thermostats, cameras, etc - can be very sloppy or not follow the correct standards for things like beacons or channel changes. In the case I described I was using PM5 HW 633 FW 168, ErgData V1.4.3 (0) via TestFlight on an iPhone 6 iOS 12.4.5. The newer 169 and the production release of ErgData fixed the problem in my case.
Regardless of the cause, it was interesting in that it revealed this logic error between ErgData and the logbook where there's an unexpected discontinuity, then ErgData acquires the session from the PM5 and syncs it to the logbook. This results in the logbook showing correct distance, time and pace data from the PM5 but incorrect stroke stats from ErgData, and the whole thing is flagged as Verified.
I'm guessing a bit but it appears that HowardF silently lost his ErgData connection for the latter part of his session (could be any number of reasons, as above), then ErgData acquired it from the PM5 and synced it, and the low stroke count came to light, with a spotlight shone on it by the Garmin stats showing approximately what it should have been as calculated by him and Citroen.
Regardless of the cause, it was interesting in that it revealed this logic error between ErgData and the logbook where there's an unexpected discontinuity, then ErgData acquires the session from the PM5 and syncs it to the logbook. This results in the logbook showing correct distance, time and pace data from the PM5 but incorrect stroke stats from ErgData, and the whole thing is flagged as Verified.
I'm guessing a bit but it appears that HowardF silently lost his ErgData connection for the latter part of his session (could be any number of reasons, as above), then ErgData acquired it from the PM5 and synced it, and the low stroke count came to light, with a spotlight shone on it by the Garmin stats showing approximately what it should have been as calculated by him and Citroen.
Re: Stroke Count wrong
Hi, just some info from my side.
Yes, have been in contact with support and sent them screen shots of my Ergdata version ( = 1.98 ) and the session shown in Ergdata. No reply from them so far.
During my training I did not see any issues on the Ergdata. The stroke counting was normal.
Yes, have been in contact with support and sent them screen shots of my Ergdata version ( = 1.98 ) and the session shown in Ergdata. No reply from them so far.
During my training I did not see any issues on the Ergdata. The stroke counting was normal.
54 years, 183 cm, Norway