Logbook Workout Graph Cuts off

[JCWoody7]

When I have been doing longer rows using the "just row" option the logbook workout graph seems to cut off at about 23 minutes. Perhaps I am missing an option to expand the graph? I also export my workouts to Garmin connect and they come-out truncated as well. Any advice would be appreciated, thank you.

[Tsnor]

FWIW I do not have this problem. Long "just row" workouts (~90 mins) go from ergdata to the C2 log just fine (last one 4 days ago).

For the workout that was truncated in the C2 log ...

If you look in your PM5 workout history is the entire workout there ?

If you look in Ergdata is the entire workout there ?

[Citroen]

When you're finished with a "Just Row" you MUST press the [MENU] button on the PM5. [MENU/BACK] button on PM3/PM4

[Carl Watts]

No idea why people use the "Just Row" function other than perhaps a 5 min warm up in a gym setting because you cannot be bothered pushing any button for that short time.

Just setup a fixed distance or a fixed time, works without a problem.

"Just Row" doesn't go down on the odometer either, its a totally unstructured workout without a goal.

[Ombrax]

its a totally unstructured workout without a goal.

And sometimes that's what someone might be interested in doing. They don't want to decide beforehand how far, how fast or how long they're going to go, and they don't want to bother putting 10,000m (or whatever) as the planned distance.

I can understand why some people might use it. On the other hand, I can also see how a programmer would have a hard time figuring out if a given JR session is really finished, or not, which would make it challenging for the PM to process the results.

[jackarabit]

its a totally unstructured workout without a goal.

And sometimes that's what someone might be interested in doing. They don't want to decide beforehand how far, how fast or how long they're going to go, and they don't want to bother putting 10,000m (or whatever) as the planned distance.

I can understand why some people might use it. On the other hand, I can also see how a programmer would have a hard time figuring out if a given JR session is really finished, or not, which would make it challenging for the PM to process the results.

Failure to add jr volume to PM odometer (or logbk, if there ever was such a problem) obviated by ErgData screen query “Are you finished/yes?/no?” following every pause in sensor activity of more than a few seconds. ErgData is a C2 product by the way. Apparently NOT that difficult for their programmers to correct this deficiency by simply adding the processing capability of your phone to that of the PM.

[Carl Watts]

Well if its an easy fix its never been sorted since 2003.

Pretty sure the "just rows" never end up making it into the memory either, most of the monitors I fix are just blank in the Odo and the memory.

Yeah ErgData throws an "Are you finished rowing" and you get a recorded result, which is handy on the odd occasion that RowPro falls over because the intended distance or time row failed to load to the PM5.

[Tsnor]

Well if its an easy fix its never been sorted since 2003.

Pretty sure the "just rows" never end up making it into the memory either, most of the monitors I fix are just blank in the Odo and the memory.

Yeah ErgData throws an "Are you finished rowing" and you get a recorded result, which is handy on the odd occasion that RowPro falls over because the intended distance or time row failed to load to the PM5.

Just rows do show up in the PM5 memory workout display.

Just row kilometers do show up in total kms rows, lifetime kms etc in the PM5 display. The kms reported by the PM5 closely match the logbook kms. Logbook kms do include "just row" kms.

I sometimes reply Yes to the "are you done" question from Ergdata. I sometimes hit the menu button on the PM5. Both seem to work fine to get all kilometers counted, all stroke data uploaded, etc.

Must have been an older device or older firmware level that lost the "just row" kms. Be interesting to see what the PM5 and what Ergdata reported for the Original Posters truncated session. At a guess this is another variation of the "pm5 to ergdata over bluetooth data corruption" that is planned to be fixed in the next release.

[Tsnor]

At a guess this is another variation of the "pm5 to ergdata over bluetooth data corruption" that is planned to be fixed in the next release.

If so the entire workout will be in the PM5 memory display and only the trucated part of the workout will be in Ergdata and online in the C2 log.

[Carl Watts]

Well just tried the "Just Row" on my PM5v2 on V168 firmware and the results are not stored and the Odometer doesn't increment even if you press MENU a few seconds after the row when the digits have stopped changing.

Trying to use the "Just Row" option and trying to get recorded results you can use is a bad idea.

If you want to use "Just Row" then also use ErgData, it gives you the option of recognizing the end of the row and storing the correct data.

[whp4]

Well just tried the "Just Row" on my PM5v2 on V168 firmware and the results are not stored and the Odometer doesn't increment even if you press MENU a few seconds after the row when the digits have stopped changing.

Trying to use the "Just Row" option and trying to get recorded results you can use is a bad idea.

If you want to use "Just Row" then also use ErgData, it gives you the option of recognizing the end of the row and storing the correct data.

Just row data is not saved by the PM3 unless you row at least 5 minutes. I suspect you are not rowing long enough in your testing, and that newer versions of the monitor also filter out such short rows.

[Ernits]

https://log.concept2.com/profile/1267889/log/55062973

Not the case with PM5, it seems. This session was 4 strokes in and hit the menu button.
Also, as much as I've been in the gym and taken a look in the memory, it pretty much only consists of just row sessions.

[whp4]

Interesting, maybe there were enough complaints about the PM3 not recording short just row sessions that they got rid of that “feature”. Now we are back to not having a theory for why Carl’s Just row sessions don’t get recorded.

[JCWoody7]

So to answer a few of the questions. All the data is logged correctly in the PM5 and the logbook but it cuts the graphing short. So all stroke data and HR data just cuts off at an arbitrary time on chart (even though its keeping track). In the online C2 logbook it shows as just a truncated chart, when I export to Garmin all the graphs go flat at the cutoff time. I have only every used "just row" a couple of times and usually when I only have a specific fixed amount of time to row and am not sure how many meters I am going to be able to do (young kids and not a lot of free time).

[Tsnor]

So to answer a few of the questions. All the data is logged correctly in the PM5 and the logbook but it cuts the graphing short. So all stroke data and HR data just cuts off at an arbitrary time on chart (even though its keeping track). In the online C2 logbook it shows as just a truncated chart, when I export to Garmin all the graphs go flat at the cutoff time. I have only every used "just row" a couple of times and usually when I only have a specific fixed amount of time to row and am not sure how many meters I am going to be able to do (young kids and not a lot of free time).

Compare your last two split times on the pm5 with the last 2 splits in logbook. IF they are different then this is the data corruption going from pm5 to ergdata problem. If they are the same its something else.

If you download the CSV stroke data I think you'll see the stroke data ends at the time the graph ends. The CVS data displays and graphs nicely in openoffice, LibreOffice or excel. The first two are free, safe downloads.