V976: Pm3 Specific Commands

[old] bbsportz · Post by **[old] bbsportz** » April 29th, 2005, 1:47 am

PROBLEM: Under V97/976 the PM3 Specific Command for WorkDistance returns ZEROES ie no distance at all! I have written an App that relies on repeated calls to the PM3 Specific commands using tkcmdsetUSB_do_DDIcommand. I am specifically interested in the STROKE STATE, TIME and DISTANCE I posted a question months ago on the 0.01 resolution for Time and Distance. I was pretty happy to see the follwing fix in V976 "6. Fixed GET_WORKTIME PM3-specific command to properly return the displayed worktime w/ 0.01 sec resolution and added fractional time byte for sub-second information. Also modified GET_WORKDISTANCE PM3-specific command to return work distance w/ 0.1 m resolution and added fractional distance byte." Using PM3APIDemo.exe with the tkcmdsetUSB_do_DDIcommand command selected I have placed this command data array as follows 0xF0,0xFD,0x00,0x1A,04, 0xA0,0xA3,0xBF,0xC1,0x63, 0xF2 The AO is TIME, A3 Distance. and the BF StrokeState I have two rowers in the LAB. One with V95 and the other V976 Under V95 the Time, Distance and StrokeState are fine. I have spent months working on a C++/C# application that uses this call. Under V976 Time and StrokeState appears to be incrementing appropriately but DISTANCE is ZERO (ie A3 05 00 00 00 00 00 where the 05 relates to the number of data bytes for the A3 command). Is this a known problem ? Cheers MarkA

[old] mlyons · Post by **[old] mlyons** » April 29th, 2005, 8:21 am

MarkA, Thanks for the feedback. I'm not sure what behavior you are seeing as I have taken your sample command string and using the PM3APIDemo program am able to produce non-zero workdistance values. The only relavent known bug that exists in V976 that was not in V95(0) is the following: If you begin a workout (say a 2000m fixed distance piece) and only complete 200m before terminating the workout (so your actual distance rowed is 200m). Then set up another workout (say a 5000m fixed distance piece) and poll the PM3 w/ your command string the distance reported will be (5000m - 200m = 4800m) until you take a stroke or two. Similarly, if you complete the original 2000m workout and then set up another 2000m workout and poll the PM3 w/ your command string the distance reported will be (2000m - 2000m = 0m) until you take a stroke or two. This is because the PM3 is not "reinitializing" some values until rowing is actually active. This behavior is fixed in the next release so that in the above example, 2000m would be reported before any strokes are taken. For example, if you set up a 2000m fixed distance piece on the PM3 (from a power-up to avoid the above mentioned situation) the response to your command string (0xF0,0xFD,0x00,0x1A,04, 0xA0,0xA3,0xBF,0xC1,0x63, 0xF2) should be something like: F0 00 FD 89 1A 14 A0 05 00 00 00 00 00 A3 05 20 4E 00 00 00 BF 01 00 C1 01 00 94 F2 where the workdistance is 0x4E20 or 2000.0m Let me know if you have any more questions or concerns, or discover any bugs. Mark

[old] c2scott · Post by **[old] c2scott** » April 29th, 2005, 10:13 am

Production Beta Release 88 will be posted today on the Concept2 main web site. I understand that this will solve the issue MLyon describes above. If it does not solve your problem, please advise. -Scott

[old] mlyons · Post by **[old] mlyons** » May 2nd, 2005, 3:52 pm

MarkA, I did notice that V976 and V88Beta5 are not currently handling a JustRow workout properly. The WorkDistance command does return 0m during a JustRow workout. This will be fixed in the next Beta release. Mark

[old] bbsportz · Post by **[old] bbsportz** » May 10th, 2005, 11:20 pm

Thanks for the responses I look forward to the fix. I have a few more questions that I will start in new posts

[old] John 'SugarBoy' Foy · Post by **[old] John 'SugarBoy' Foy** » May 21st, 2005, 5:00 pm

ALL FAR TOO TECHY FOR ME