Now that is interesting! I was beginning to wonder whether the problem
lay with not being able to decode negative DAC values, but I had no way
of testing it. Clearly, as the data is processed correctly in other
programs - and the monitor works in all other respects - that does
rather point to a specific issue with DAC related sub-routines.
The only puzzle is that most of the monitors do work OK as far as I know
- maybe somebody got different versions of the firmware confused - or is
it something else?
David
On 12/05/2011 08:56, Mark Sims wrote:
I have a sneaking suspicion that I know what is going on...
Ages ago I sent the code for my first TSIP parser to someone (can't remember
who... was it Dieder?) who was going to use it in a microcontroller based
tbolt monitor. Fluke's monitor is just a lift of that design. Well, my code
had a bug in the DAC message processor. If I remember correctly it was
something like reading the DAC value as a single precision number, but the
tbolt was sending a double precision number (or the other way around).
_______________________________________________
time-nuts mailing list -- time-nuts@febo.com
To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts
and follow the instructions there.
_______________________________________________
time-nuts mailing list -- time-nuts@febo.com
To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts
and follow the instructions there.
