Concept2 Forum

Mark,<br />We've just implementing the Force curve data in an application. Thanks very much it looks great.<br /><br />The manual says that we are looking at "Data samples proportional to FORCE".<br /><br /><br />Could you tell us specifically what this number is derived from .<br /><br /><br />Chee...

Mark,<br />We loaded that version and did a number of steady state trials over 1000M<br /><br />It stopped 0.2m short in the 150W and 0.1m short in the 225W trial.<br /><br />MarkA and MarkO<br /><br /><br />

Hello<br /><br />I am not sure if this is a bug or not, or if it has already been fixed. <br /><br />We do our testing in countdown from a set distance to ZERO. We typically set it to 2000M, 1000M or 500M.<br /><br />When the PM3 distance shows ZERO the clock stops and the time trial is finished ON ...

Thanks very much for that reply. <br /><br />It has straightend out of a few misunderstanding for us.<br /><br />Its an understatement to suggest that we are excited about the coming release of the ForcePlotData.<br /><br />MarkA and MarkO<br /><br /><br />

It would be nice if at the higest frequency of polling the PM3 device (around 30-20hz) the key variables were changing at a similar or faster rate.<br /><br />eg Time is resolved to 1/100th of a second but updates/refreshes every 100ms (10hz). Yet we poll at the maximum frequency available (30-25hz)...

Our interpretation of Anu Dudhia's and Marinus van Holst's site is similar to the one that jamesg responded with. <br /><br />Marinus van Holst, "Behind the Ergometer Display" <a href='http://home.hccnet.nl/m.holst/ErgoDisp.html' target='_blank'>http://home.hccnet.nl/m.holst/ErgoDisp.html</a><br /><...

<br />Does anyone know the specific equation used in the PM3 to determine the POWER value expressed at the end of each drive phase.<br /><br /><br />MarkA and MarkO<br /><br /><br /><br />

<br />To: Mark Lyons and Mike haboustak,<br /><br />Thanks for the replys. It has clearly helped me sort out all my issues.<br /><br />I was using a threaded Timer object and at times it was definitely re-entrying before the PM3 was ready. I have also moved back to the CSafe function for the PM3 Spe...

<!--QuoteBegin-mlyons+May 12 2005, 12:34 PM--><table border='0' align='center' width='95%' cellpadding='3' cellspacing='1'><tr><td><div class='genmed'><b>QUOTE(mlyons @ May 12 2005, 12:34 PM)</b></div></td></tr><tr><td class='quote'><!--QuoteEBegin-->MarkL,<br /><br />"The timeouts for both the Csaf...

<!--QuoteBegin-mlyons+May 12 2005, 12:09 AM--><table border='0' align='center' width='95%' cellpadding='3' cellspacing='1'><tr><td><div class='genmed'><b>QUOTE(mlyons @ May 12 2005, 12:09 AM)</b></div></td></tr><tr><td class='quote'><!--QuoteEBegin-->MarkL,<br /><br /><br />"1. Are you explicitly se...

MarkL<br /><br />Thanks for the quick response to the other POST re V976 PM3 Zeroes<br /><br />Here are a couple more:<br /><br />I make repeated calls to the PM3 device using tkcmdsetUSB_do_DDIcommand. <br /><br />Here is the function call in my Visual Studio C++ .NET managed DLL:<br /><br />public...

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

PROBLEM: Under V97/976 the PM3 Specific Command for WorkDistance returns ZEROES ie no distance at all!<br /><br /><br />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 DISTANC...