Built for sites where the network can’t be trusted
A weighbridge can’t stop because a link is down. So the platform treats each station as independent, with the central system as the place where all records come together.
The parts and how they talk
- The station. A single compiled application runs on a Raspberry Pi and runs the weighing cycle as a state machine. Every weighment goes to a local SQLite database first.
- Syncing. Stations publish transactions and receive master data updates over MQTT. They can also pull master data through a REST API. When a sync fails, the station retries automatically. Photographs follow through their own upload queue.
- The control node. A Node.js application with PostgreSQL holds master data and transactions. Images go to S3-compatible object storage and are viewed through time-limited links. The whole stack runs in Docker.
Linked stations
In a three-station group, each station records its own weight on a shared transaction. The relay handles messages that arrive out of order, so the record still comes together.
Updates
A new release is uploaded centrally, then downloaded and verified by checksum at the station. If the new version keeps crashing, the station returns to the previous one.
At the weighbridge
The station connects to the weight indicator over serial, to RFID readers, position sensors, traffic lights, cameras and a speaker. The equipment and site work are hardware by Maxim Mechatronics.
Common questions
What happens to a weighment if the network is down?
Where are photographs stored?
Can the platform run on our own server?
Check the architecture against your sites
Tell us how many weighbridges you run and how they connect. We will show you how the stations and the control node would fit.