Countdown time corruption

mark osborne · Post by **mark osborne** » July 28th, 2006, 1:14 am

Hi,
When in countdown time mode (we have been playing with 20s time periods for development purposes), we have been finding a semi-consistent corruption when you finish the effort midway through the drive phase of the stroke. The error does not seem to appear when you finish during the recovery phase of the stroke cycle. The final time will often revert to a 0.1s on the display upon completion, and sometimes a number as high as 0.8-9s appears. When connected to a pc, when we do a PM3 call to determine the final distance travelled, we get bizarre numbers and we then have to re-set the drivers by removing and reconnecting the cable.

While we thought this might have been a result of the calls we have been making to the PM3 SDK library, we are able to consistently (~25% of the time) replicate the error/corruption when the PM3 is not connected to the pc.

This has been evident in both firmware versions 88 beta 11 and 17, version 90 and also 94.

Thanks,
Mark

haboustak · Post by **haboustak** » August 2nd, 2006, 9:11 am

Mark,

How do you get the PM3 to display tenths of a second? I'm trying to do some testing with fixed time rows, but I can't seem to find what you're seeing. I've tried about 15 individual 20s or 1:00 timed rows and the monitor always stops at dead 0. I've also tried calling the SDK functions and they too return 0.0 for time at the end of a row.

What SDK Time function are you using. I'm interested in trying some more testing, but I'm not sure how to recreate what you're doing.

Mike