Weird data in the logbook. 1min 2K ???
Weird data in the logbook. 1min 2K ???
I did 30 mins on justrow and continued for another 5 as a warm down.
Recorded it on ErgData and uploaded it from there to the logbook.
Can anyone tell me what is happening here?
The headline numbers are fine but -13,000m in 1.4 seconds!!
Also my best 2k in there seems to be just over 1 min !?!
35:05.8 8,065m 2:10.5 157 841 19 143
1:58.8 3,000m 0:19.8 45089 155478 20 149
2:06.0 3,000m 0:21.0 37793 130368 22 159
1:50.8 3,000m 0:18.4 55578 191577 17 137
1:54.6 3,000m 0:19.1 50231 173173 19 143
1:55.9 3,000m 0:19.3 48559 167421 19 144
2:04.6 3,000m 0:20.7 39081 134801 22 170
1:34.5 3,000m 0:15.7 89583 308609 15 120
0:01.4 -12,935m 59:59.8.1 -2208377041199 -7600350424691 0 120
Did I do something wrong? Don't know if it's and ErgData or logbook issue.
Recorded it on ErgData and uploaded it from there to the logbook.
Can anyone tell me what is happening here?
The headline numbers are fine but -13,000m in 1.4 seconds!!
Also my best 2k in there seems to be just over 1 min !?!
35:05.8 8,065m 2:10.5 157 841 19 143
1:58.8 3,000m 0:19.8 45089 155478 20 149
2:06.0 3,000m 0:21.0 37793 130368 22 159
1:50.8 3,000m 0:18.4 55578 191577 17 137
1:54.6 3,000m 0:19.1 50231 173173 19 143
1:55.9 3,000m 0:19.3 48559 167421 19 144
2:04.6 3,000m 0:20.7 39081 134801 22 170
1:34.5 3,000m 0:15.7 89583 308609 15 120
0:01.4 -12,935m 59:59.8.1 -2208377041199 -7600350424691 0 120
Did I do something wrong? Don't know if it's and ErgData or logbook issue.
Re: Wierd data in the logbook. 1min 2K ???
89,000 Watts at 15 SPM - you could be a power stationCrushy wrote: ↑December 10th, 2020, 12:07 pmI did 30 mins on justrow and continued for another 5 as a warm down.
Recorded it on ErgData and uploaded it from there to the logbook.
Can anyone tell me what is happening here?
The headline numbers are fine but -13,000m in 1.4 seconds!!
Also my best 2k in there seems to be just over 1 min !?!
35:05.8 8,065m 2:10.5 157 841 19 143
1:58.8 3,000m 0:19.8 45089 155478 20 149
2:06.0 3,000m 0:21.0 37793 130368 22 159
1:50.8 3,000m 0:18.4 55578 191577 17 137
1:54.6 3,000m 0:19.1 50231 173173 19 143
1:55.9 3,000m 0:19.3 48559 167421 19 144
2:04.6 3,000m 0:20.7 39081 134801 22 170
1:34.5 3,000m 0:15.7 89583 308609 15 120
0:01.4 -12,935m 59:59.8.1 -2208377041199 -7600350424691 0 120
Did I do something wrong? Don't know if it's and ErgData or logbook issue.
Born 1963 6' 5" 100Kg
PBs from 2020 - 100m 15.7s - 1min 355m - 500m 1:28.4 - 1k 3:10.6 - 2k 6:31.6 - 5k 17:34.9 - 6k 20:57.5 - 30min @ 20SPM 8,336m - 10k 36:28.0 - 1 hour 16,094m - HM 1:18:51.7
2021 - 5k 17:26 - FM 2:53:37.0
PBs from 2020 - 100m 15.7s - 1min 355m - 500m 1:28.4 - 1k 3:10.6 - 2k 6:31.6 - 5k 17:34.9 - 6k 20:57.5 - 30min @ 20SPM 8,336m - 10k 36:28.0 - 1 hour 16,094m - HM 1:18:51.7
2021 - 5k 17:26 - FM 2:53:37.0
Re: Wierd data in the logbook. 1min 2K ???
I've seen this also.
Only happens on "just row". doesn't always happen. I didn't get enough data to see if it was related to stopping the workout on ergdata via the message pop-up vs stopping the "just row" workout with the menu button on the PM5 -- but I now always stop the workout on the PM5.
For me, the graphs looked good. When I downloaded the CSV data it is all good.
For example, here is a warm up that went bad... (November 28, 2020 12:41:00)
Time Meters Pace Watts Cal/Hr S/M
5:06.7 1,083m 2:21.5 123 724 14
1:46.3 3,000m 0:17.7 62939 216911 18
0:02.1 -1,917m 59:58.8.6 -2129935665 -7330386286 9
Total warm-up distance from the CSV data was only 1065m so every row is bad, even the first one. Last entry in the CSV downloaded data was at 300.7 seconds which is less than the 5:06.7 from the first row. Interesting that "just row" computes a split every 300 seconds (5 mins), and the CSV data ended a split second after 300 seconds.
Only happens on "just row". doesn't always happen. I didn't get enough data to see if it was related to stopping the workout on ergdata via the message pop-up vs stopping the "just row" workout with the menu button on the PM5 -- but I now always stop the workout on the PM5.
For me, the graphs looked good. When I downloaded the CSV data it is all good.
For example, here is a warm up that went bad... (November 28, 2020 12:41:00)
Time Meters Pace Watts Cal/Hr S/M
5:06.7 1,083m 2:21.5 123 724 14
1:46.3 3,000m 0:17.7 62939 216911 18
0:02.1 -1,917m 59:58.8.6 -2129935665 -7330386286 9
Total warm-up distance from the CSV data was only 1065m so every row is bad, even the first one. Last entry in the CSV downloaded data was at 300.7 seconds which is less than the 5:06.7 from the first row. Interesting that "just row" computes a split every 300 seconds (5 mins), and the CSV data ended a split second after 300 seconds.
- Citroen
- SpamTeam
- Posts: 8055
- Joined: March 16th, 2006, 3:28 pm
- Location: A small cave in deepest darkest Basingstoke, UK
Re: Weird data in the logbook. 1min 2K ???
Collect the following info:
1. Phone OS version
2. Ergdata App version
3. PM5 firmware version (and you should updated it https://www.concept2.com/service/monitors/pm5/firmware if it's not V206, V169 or V31)
Then write an email to info@concept2.com to report your bug.
1. Phone OS version
2. Ergdata App version
3. PM5 firmware version (and you should updated it https://www.concept2.com/service/monitors/pm5/firmware if it's not V206, V169 or V31)
Then write an email to info@concept2.com to report your bug.
Re: Weird data in the logbook. 1min 2K ???
I don't think it has anything to do with how you stop it, or at least not solely, as I only use the menu button to stop just row's.Tsnor wrote: ↑December 13th, 2020, 6:40 pmI've seen this also.
Only happens on "just row". doesn't always happen. I didn't get enough data to see if it was related to stopping the workout on ergdata via the message pop-up vs stopping the "just row" workout with the menu button on the PM5 -- but I now always stop the workout on the PM5.
For me, the graphs looked good. When I downloaded the CSV data it is all good.
For example, here is a warm up that went bad... (November 28, 2020 12:41:00)
Time Meters Pace Watts Cal/Hr S/M
5:06.7 1,083m 2:21.5 123 724 14
1:46.3 3,000m 0:17.7 62939 216911 18
0:02.1 -1,917m 59:58.8.6 -2129935665 -7330386286 9
Total warm-up distance from the CSV data was only 1065m so every row is bad, even the first one. Last entry in the CSV downloaded data was at 300.7 seconds which is less than the 5:06.7 from the first row. Interesting that "just row" computes a split every 300 seconds (5 mins), and the CSV data ended a split second after 300 seconds.
I will check out the things suggested by Citroen and let people know.
-
- Paddler
- Posts: 38
- Joined: May 19th, 2018, 2:22 pm
Re: Weird data in the logbook. 1min 2K ???
I had a similar issue two weeks ago. When I started ErgData I got a message that the time on my PM5 (or on ErgData? Not sure, sorry) was apparently wrong, would I like to adjust it. I confirmed. The resulting workout had absurd values, I did 17 km in 20 minutes. The 20 minutes were correct, the 17 km were not.
That was the only faulty session. No further problems since.
That was the only faulty session. No further problems since.
- Citroen
- SpamTeam
- Posts: 8055
- Joined: March 16th, 2006, 3:28 pm
- Location: A small cave in deepest darkest Basingstoke, UK
Re: Weird data in the logbook. 1min 2K ???
Same answer: viewtopic.php?p=513897#p513897fischmeister wrote: ↑December 14th, 2020, 8:46 amI had a similar issue two weeks ago. When I started ErgData I got a message that the time on my PM5 (or on ErgData? Not sure, sorry) was apparently wrong, would I like to adjust it. I confirmed. The resulting workout had absurd values, I did 17 km in 20 minutes. The 20 minutes were correct, the 17 km were not.
That was the only faulty session. No further problems since.
Re: Weird data in the logbook. 1min 2K ???
Sent the info to concept and got this reply
' Sorry for the Glitch in the data. We've seen it from time to time but we haven't been able to resolve it yet. We are currently working on a new version of ErgData which we hope to have out in the first quarter of next year and we expect this version to be more robust as far as data anomalies. '
Looks like we wait for next year.
' Sorry for the Glitch in the data. We've seen it from time to time but we haven't been able to resolve it yet. We are currently working on a new version of ErgData which we hope to have out in the first quarter of next year and we expect this version to be more robust as far as data anomalies. '
Looks like we wait for next year.