I need expert guidance regarding issues with ModScan32 reading data
Thread Content
When I use ModScan32 to read the cumulative values of the gauge, if those values have more than 7 significant digits, they cannot be read properly and are instead displayed in scientific notation. For example: if the gauge shows an accumulated value of 32508125, reading it with ModScan32 displays it as 3.25e+007 ； Another example: the gauge shows an accumulated value of 5678.1632, while reading it with ModScan32 gives 5678.0000. Is this because the data type of the instrument is single-precision floating point? Is there any way to make ModScan32 read properly? I would be very grateful if someone who knows a lot about this could give me some guidance.
The data type displayed can be changed; for something like your cumulative value, it is usually a 32-bit floating-point number
It is a 32-bit floating-point number; I switched to hexadecimal mode to read it, and then converted the hexadecimal value into a decimal floating-point number, and the result was correct. Is the problem with the instrument or with the reading software when such questions arise?
This is probably a problem with your software; I used to use one that could display floating-point numbers directly
I use the ModScan32 software for reading, and this software supports floating-point reading.
If there is another scenario, namely when the numbers are too long, it is recommended that you change the unit; if the original value is in KG, convert it to T – that will also work
I’ve tried this method – I changed KG to T – but it had no actual effect. For example, if the gauge displays 35288.789T, the value read by ModScan is also expressed in scientific notation: 3.52e+004. Similarly, when the gauge shows 352.88789T, ModScan defaults the digits after the decimal point to 0, showing a value of 352. So changing the unit has no practical effect. Another issue is that real-time reading isn’t possible. For example, if the value is 352, then every time 2 is added, a new value is read, such as 354, 356, and so on. If the value is a four-digit number, like 3528, then every time 16 is added, a new value is read, such as 3544, 3560. If the value is a five-digit number, like 35288, then every time 256 is added, a new value is read, such as 35544, 35800. That’s also a problem.