In short
Read the weight from the indicator over a serial port, usually RS-232. Its text format differs between manufacturers, so get the protocol manual and match the settings on both ends. WeighHub delivers it two ways: a boot-start Windows agent, or an ESP32 device it ships. It records, never measures.
The question sounds technical, but it is really an operational one: how do we stop the number passing through a person before it is recorded? Solve that, and more than half your discrepancy and fraud problems close with it.
What actually comes out of the indicator
A weighbridge indicator does not send “a weight” in any structured sense — it sends a line of text, repeated several times a second, carrying the figure and some characters describing its state: is the reading stable? is the scale at zero? what unit is it in?
The format of that line differs between manufacturers, and there is no universal standard. So the first thing to ask for is the indicator's protocol manual — the page describing the line it emits. Without it, connecting is guesswork.
The port: where the data leaves
- RS-232 (serial): by far the most common on indicators. Needs a specific cable, and usually a USB adapter if the PC has no serial port.
- RS-485: tolerates much longer runs — the right choice when the control room is far from the indicator.
- Ethernet: available on newer indicators, and the easiest to work with when present.
Before anything else, confirm your indicator has an output at all. Some budget models only drive the display. In that case the options are replacing the indicator — far cheaper than replacing the weighbridge — or continuing with manual entry and everything that follows from it.
Settings that must match
Both ends — indicator and software — have to agree, or the data arrives as gibberish. The most common combination in practice is 9600 baud with 8 data bits, no parity, one stop bit, but that is not a rule: check your manual, as some use other values.
There is a second setting inside the indicator that matters just as much: does it transmit continuously or on request? Continuous is simpler to work with, because the software can read the latest stable value whenever it needs it.
Reading is not enough — you need a stable capture
This is the step most often skipped, and the cause of the most irritating errors. The indicator sends dozens of readings a second, and they fluctuate while the vehicle settles. If the system records the instantaneous value, it can record an intermediate figure that never was the real weight.
A good system does not take the last line that arrived. It waits until several consecutive readings agree on the same value within a short window, and discards truncated or malformed lines caused by noise. That is the difference between a reliable reading and a nearly-right one.
Why connections fail
- Mismatched settings — strange characters instead of digits. Check the baud rate and the rest.
- The cable. Not all serial cables are wired alike; some indicators need a particular arrangement. Excessive length on RS-232 is a recurring cause of lost data.
- A poor USB adapter. One of the most common causes and least obvious: it works, then drops out at random. Adapters with well-known chipsets are markedly more stable.
- Electrical noise. A data cable run alongside power cables, or near welding equipment, picks up interference that cuts lines in half. The fix: a separate route, shielded cable and proper earthing.
- Units. If the indicator transmits in a different unit from the one the software expects, figures appear divided or multiplied. Fix it in the indicator's settings or in the system's unit configuration.
What about the internet?
The link between indicator and computer is entirely local and has nothing to do with the internet. Sending tickets to a cloud system does need a connection — and the right design is one where weighing does not stop when it drops: the reading is captured, stored locally, and synced when the network returns.
Ask any system this exact question when evaluating it: what happens if the internet drops mid-weighing? The answer tells you a great deal.
Practical steps
- Confirm the indicator has a data output, and obtain the protocol manual.
- Decide the port type and the distance to the control room, and pick the cable accordingly.
- Match the settings on both ends, and enable continuous transmission if available.
- Read the raw stream first and confirm lines arrive complete and undistorted.
- Enable stable capture before recording, then verify ten weighings against the display by hand.
- Separate the data cable route from power cables, and check the earthing.
After that, not one number passes through anyone's hands before it is recorded — and that alone changes oversight on site more than any procedure.