PM5 Observations & Suggestions

[raotor]

As a sort of addendum to my previous "PM5 problems" post I thought I'd share
my findings after some more recent tests and the conclusions I've drawn and
the suggestions for Concept 2 to perhaps consider for future development of
the PM5 firmware.

I finally got my gym where the PM5 erg is based to replace the almost dead
batteries that were causing various issues as covered in the aforementioned
post and so I decided to take my USB stick back to the scene of the crime
and see how things fared with the low power issue no longer a factor.

I inserted my USB stick and was presented with my lifetime metres and no
error messages as was not the case when the battery level was low
previously. I
then did three "Just Rows" and after each row would wait several seconds and
then press the MENU button to commit the completed Just Row to the USB
stick.

Interestingly, for each of the three Just Rows I got a different result from
the PM5 in terms of response. After the first row the PM showed a memory
stick picture and hour glass as it apparently wrote the session data to the
memory stick. No errors were reported and lifetime metres had been updated
accordingly.

Fine.

After completing the second just row the same action resulted in no memory
stick picture being displayed but only an hour glass. However, lifetime
metres this time did not reflect the additional metres just saved. I used
the
move workout option to transfer the session that had apparently ended up
being written to the PM internal memory instead with no error codes. The
move to the stick function was apparently completed without error and the
lifetime metre count was now correct.

After finishing the third and last just row session and pressing the MENU
button I received an error code 38-84 and was prompted to press the continue
button. I located this session too in internal PM memory having failed to
write it to the USB stick and without error transferred it to the USB stick.
Lifetime metre count was again updated to reflect the successfully moved
workout.

when I got home I then attempted to upload the three workouts to my log
book via the Concept 2 Utility v6.83. Doing so threw up an error informing
me that a file was missing (filename ending info.bin but cannot recall
exactly but was inside the Concept 2 folder).

So, despite the PM reporting no errors during the transfer from internal
memory to the stick or even doing so during the apparent first trouble free
just row session being committed there was nothing on the stick to retrieve
due to a missing file.

I then took a look at the files and folders on the memory stick and quickly
found that the Concept 2 folder was inaccessible or corrupt according to
Windows when I tried to enter it. As there was no easy way to resolve this I
decided to format the stick and return to the gym the following day and have
the PM reinitialize it.

Once I'd supplied my user name and was shown a zero lifetime metre count I
did several just rows and each was written to the stick without issue.

So, what I conclude from this is that operating a PM5 with a memory stick
while in a state of low power has apparently caused corruption to the file
on the memory stick. This corruption subsequently caused the loss of data to
occur but without the PM evidentially detecting this innate write failure.

My suggestion to C2 is to firstly come up with a lower battery power
threshold percentage after which all USB stick I/O is prevented and the user
is clearly notified of this situation. Also, that all files and
folders required for correct PM utilization are verified for existence and
where required checked for write access. This could be done when the stick
is inserted. I am rather surprised something like this is not already done
but seemingly not. Perhaps in some future firmware release the above
suggestions might be implemented to further improve the robustness and
reliability of the system as a whole.

[Carl Watts]

As stated months ago your better off not being on the "Leading Edge Hardware", I have learned this from experience, let someone else sort out all the problems and wait a couple of years for the firmware to get sorted.

Looks like RowPro just release V4.3 to cope with the New PM5 so that's just going to open an even bigger can of worms if your trying to use that as well.

The PM3 and PM4 are rock solid and there really is no reason to jump to a PM5 if you already have one unless your prepared to encounter issues that can potentially stuff up your rows.

[jasontourt]

Looks like RowPro just release V4.3 to cope with the New PM5 so that's just going to open an even bigger can of worms if your trying to use that as well.

My anecdotal experience: PM5 with version 15 firmware connected to RowPro 4.2 was glitchy. A few random errors here and there, and RowPro often not connecting with PM5 unless I pressed a button on the PM5 to wake it.

After upgrading PM5 to firmware version 17, the issues disappeared. I no longer need to facilitate a connection. RowPro 4.3 seems solid. I have had no issues.

Raotor, in the post above, you didn't specify the firmware version. Your post was detailed and contained valuable testing and feedback information. As time passes and people come across your post in the future, the firmware version would be a key piece of information. The issues you describe may be fixed with a firmware update. So it's not a "PM5 issue", it's a "PM5 with firmware XX issue."

[raotor]

Looks like RowPro just release V4.3 to cope with the New PM5 so that's just going to open an even bigger can of worms if your trying to use that as well.

My anecdotal experience: PM5 with version 15 firmware connected to RowPro 4.2 was glitchy. A few random errors here and there, and RowPro often not connecting with PM5 unless I pressed a button on the PM5 to wake it.

After upgrading PM5 to firmware version 17, the issues disappeared. I no longer need to facilitate a connection. RowPro 4.3 seems solid. I have had no issues.

Raotor, in the post above, you didn't specify the firmware version. Your post was detailed and contained valuable testing and feedback information. As time passes and people come across your post in the future, the firmware version would be a key piece of information. The issues you describe may be fixed with a firmware update. So it's not a "PM5 issue", it's a "PM5 with firmware XX issue."

Good point.

V15 is installed on the PM5 in question. However, for the purposes of future reference I have to say that at the time of writing that V17 is the current release and no specific mention has been thus far mentioned in the release notes pertaining to V17 that address the issues raised.

[raotor]

As stated months ago your better off not being on the "Leading Edge Hardware", I have learned this from experience, let someone else sort out all the problems and wait a couple of years for the firmware to get sorted.

Looks like RowPro just release V4.3 to cope with the New PM5 so that's just going to open an even bigger can of worms if your trying to use that as well.

The PM3 and PM4 are rock solid and there really is no reason to jump to a PM5 if you already have one unless your prepared to encounter issues that can potentially stuff up your rows.

The PM5 in question is not mine. It's on an erg at my local gym.

I've had the same view that one should wait at least a year before deciding on anything new and then only if you actually need it. The PM5 has only reinforced this view.

I am quite happy with my PM4 based machine at home

[jackarabit]

Happy as a pig in clover with the PM3 but the day comes when one must adapt. I now carry both log card and USB stick for the old and new machines at the Y. The stick and card both do a great job of data transfer to the C2 utility. The location of the zipstick port is inconvenient and vulnerable. We'll see how that works out in the multi-user context of public gyms?

Jack