- Joined
- Jan 10, 2019
- Messages
- 1,220
I don't own one of these units, and don't know Yuriy, but I do have a background in electrical engineering and software. Everything he's saying is exactly correct. I don't see anything in his responses that is exaggerated or played down; he's just stating facts. He has no control over whatever signal processing is done upstream of his product. It's just the nature of any digital-based sensor, that there will always be a potential one LSB (Least Significant Digit) bobble.
There's the scale itself, a sensor, and possibly inboard signal processing. The key thing to understand is how digital values are handled. If the sensor sees a scale reading of 1.999999", it will be outputting a reading of 1.999. If the sensor in the scale sees a shift of only one millionth of an inch, the output will change to 2.000. So, to the user, it may appear that the reading is "jumping all over the place", when in fact it's only changing by one millionth of an inch. That said, if it's jumping far more, then as Yuriy suggests, that may be due to a problem within the sensor assembly itself. The easy way to find out is to swap the X and Y sensor cables on the display to see if the problem follows the sensor, or doesn't. That's the "divide and conquer" method of troubleshooting.
There's the scale itself, a sensor, and possibly inboard signal processing. The key thing to understand is how digital values are handled. If the sensor sees a scale reading of 1.999999", it will be outputting a reading of 1.999. If the sensor in the scale sees a shift of only one millionth of an inch, the output will change to 2.000. So, to the user, it may appear that the reading is "jumping all over the place", when in fact it's only changing by one millionth of an inch. That said, if it's jumping far more, then as Yuriy suggests, that may be due to a problem within the sensor assembly itself. The easy way to find out is to swap the X and Y sensor cables on the display to see if the problem follows the sensor, or doesn't. That's the "divide and conquer" method of troubleshooting.
Last edited: