12-18-2007 08:33 PM
I like the hardware damage sugestion. I can't tell you how many time I have worked on a test system and when wierd thing are going on it usually is the hardware. Contrary to most bosses, customers, and hardware installers.
I think it's a HARDWARE problem, software works fine 😉
Dan (A software guy)
12-20-2007 03:02 PM
12-20-2007 08:37 PM
12-21-2007 06:45 AM
/* You can use a linear function to scale the results returned by the BinaryI16 read. The values will be approximately correct; however, I would recommend using the scaling coefficients, if possible, if your application requires accuracy. The fact that the scaling coefficients are polynomial is a result of the MCal algorithm we use on M-Series. The polynomial coefficients help compensate for small non-linearities across the range of the ADC, which when applied correctly, result in more accurate measurements. */
This is new stuff for me... I did not read it in the documentation. Or, I did not find it.
I read about custom scales and I supposed that the binary reads were linear!
But if I understood, you are talking about internal scaling coefficients not applied when we use the Binary reads and used when we use the scaled Analog reads.
We do not use the scaled Analog reads because they are slow. As you see, we are always looking for the fastest approach. The scalling calculations we can do later, through threads for processing and displaying, instead of when getting the data in the time-critical callback.
But now I need to know what are these internal scalling coefficients ! HOW I get them?
LMP
12-21-2007 09:30 AM