Hi all,
In our usual quest to gather data on our runs, we used our GEEZ cube and
rusty Palm M100. Although we got 4 runs each, the machine only recorded 6
total runs for us (my wife and myself. The odd thing was that two of the
runs recorded something like 221 and 170 ETs, while the other 4 were in
the more normal 60 to 80 range. When attempting to read these files, I
got the following errors;
Floating point operation
Floating point division by zero
Invalid floating point operation.
The course screen opens to a black box (no course trace) and the
acceleration trace box is just a single small white box.
The run between these two long runs is a run that has an 80 ET. When I
open it, though, the course trace is a series of straight lines. The
lateral acceleration trace looks like something off an oscilloscope while
the Acceleration tract is a low amplitude sine wave that is centered
around the zero line.
The other three runs look to be okay. The 'bad' runs were the first three
recorded. This is after I reset the options to the settings the Byron
suggests (which always worked well for us before). Any idea what is going
on?
Thanks.
Gene Beaird
86 SVO, G Stock, unless the Firebird is broken
85 Firebird, CP
Pearland, Texas
/// Archives at http://www.team.net/archive
/// Check http://www.team.net/mailman/listinfo for other lists of interest.
|