Page 1 of 1
Upgrade to ErgData 1.45 last night now causes timing errors
Posted: June 3rd, 2017, 6:17 am
by Chris Pomery
Upgraded Android ErgData to 1.45 last night. In the gym this morning I now notice the following faults compared to the previous version last used yesterday:
1. Second Count: rolls over in 2 or 3 second increments, and behind PM counter
2. Metre Count: rolls over about 20m behind the PM count
3. Projected Finish: rolls over one update behind the PM figure
These errors originate because the app does not start as promptly as it did in the previous version, i.e. I am rowing for 2-3 strokes before it registers its first figures. It then lags behind throughout the piece, catching up after I've stopped rowing.
Fault was found in two rows. Afraid I didn't have time to restart phone to see if that changed matters. Using a Samsung GT-19300 under Android 4.3.
Anyone else finding the same problem?
Chris
Re: Upgrade to ErgData 1.45 last night now causes timing err
Posted: June 5th, 2017, 1:07 pm
by MikeD
Hi Chris,
Thanks for the report and sorry about the trouble. A couple of questions:
- Are you using BT or a cable for your connection?
- What model PM are you using?
- Are you connected to any other BT devices?
- Anything else you can tell me about the delay when starting your workout? Does the app show "Ready to Start Workout" in the lower left prior to you starting to row?
Anything else you can think of to report would be helpful. This is the first reported issue of this type (so far) for release 1.45 and I cannot seem to reproduce the issue.
Kind Regards, Mike
Re: Upgrade to ErgData 1.45 last night now causes timing err
Posted: June 6th, 2017, 4:15 am
by Chris Pomery
Hi Mike,
Thanks for your response:
1. Cable, not Bluetooth
2. PM3
3. No. Bluetooth, GPS, wifi, everything is off on my phone by habit: the battery barely lasts for a half marathon

4. I will check this on Thursday, next time I'm in the gym.
I'll see if I can film the problem so you can see it. I'll also try another erg.
I would stress that I have used the app for two years, for about 250 sessions, on the same erg, in the same way. No issue like this until immediately after the update. The fault repeated itself yesterday on sprint & distance rows.
The PM3 is working fine; in fact, I have reversed the phone so I can't see it when rowing and just use the PM3 visual data; I guess you could call this a workaround

Chris
Re: Upgrade to ErgData 1.45 last night now causes timing err
Posted: June 6th, 2017, 12:51 pm
by MikeD
Hi Chris,
Thanks for the willingness to help, I'm very interested in what you find when you try another erg. Also, have you rebooted your phone since the upgrade? Today, I spent the morning looking into this and I came across an issue that might exacerbate the situation. If the time/date is off in the PM and a cable is connected, the change time/date dialog pops up multiple times on top of itself. I have fixed this and am ready to push it out, would you be interested in beta testing? I can send you a link if you are interested.
As far as the lagging updates go, I rolled my test device back to 1.44 (before the recent update) and in my opinion it now has the same update rate as 1.46 (which I'm about to push out). I'd be interested to hear if you agree.
Kind Regards, Mike
Re: Upgrade to ErgData 1.45 last night now causes timing err
Posted: June 8th, 2017, 1:25 pm
by Chris Pomery
Hi Mike,
Rebooted phone: same lag problem.
Tried on another erg, with PM3: same lag problem
I have a video of the lag now, if you can confirm me an email address to send it to.
Also the PM3 serial and update information.
Best,
Chris
Re: Upgrade to ErgData 1.45 last night now causes timing err
Posted: June 9th, 2017, 4:24 pm
by PaulKinlin
I must be lucky, or unlucky. I dont appear to be suffering the lag issue, however heart rate figures have disappeared after synch to logbook. Also the graph is now 'nicely' vertically stretched.
Although after exporting as csv or tcx the hr figures are there.
Not sure if this is in light of the hr figure being previously displayed as the last recorded value instead of what should have been a calculated average. Think I might revert back to the logcard or the concept utility

Re: Upgrade to ErgData 1.45 last night now causes timing err
Posted: June 12th, 2017, 4:15 pm
by MikeD
Hi Paul, Can you tell me what kind of workout you are doing? I don't see a heart rate problem when doing a fixed distance workout.
Thanks! Mike
Re: Upgrade to ErgData 1.45 last night now causes timing err
Posted: June 18th, 2017, 3:47 pm
by PaulKinlin
Hi Mike,
I row a variety of 'just row' and some fixed timings between 30 mins, 10km and half marathons, the majority are just row which prior to 9 June 2017 the heart rate data was displayed of a sort.
Over the next week I'll do a series of fixed 5km, 10km and 30 mins sessions to see if it makes a difference, meanwhile I am exporting csv to excel to carry out some analysis.
As it stands at the moment the only place the heart rate data appears is on the graph. However if I export the csv or tcx file it's all there.
You can view my log here if it helps
https://log.concept2.com/profile/148551 ergdata rows from 22 may 2017, prior to that are log card.
I also have a few more observations that appear differently on the pm4 and ergdata really the heart rate but the will be best captured after my next row and I'll try to get jpg files to you.
I know I'm sounding quite picky as well but occasionally the stroke spikes up around 55 - 80 spm which seems to be the reason for the vertically stretched graphs. Mainly occur after I lean over to grab a drink or skip a music track.
My setup is pm4 on a model d with 318 firmware (although in the past there was a beta firmware version installed then overwritten) , morning rows are logged using Samsung galaxy s7 with ergdata 1.47, then evening/ weekends using Samsung galaxy tab a 10.1 tablet again with ergdata 1.47. Sorry forgot to mention its a Garmin HRM (Ant+) in use...
I have also tried the trick of totally un-installing and re-installing ergdata just incase there was something nasty hanging around.
Cheers