Operations
AxleGuard can register a gateway per truck, issue a device-specific credential and ingest normalized J1939 or onboard-scale samples. Physical readings are not approved until a validation run compares them with a certified reference and records accuracy, repeatability and owner acceptance.
In the product
What changes
Each outcome connects what the software does to the decision a planner, loader or driver can actually make.
A gateway is registered against a vehicle. Its credential is shown once, stored only as a hash and can be rotated without sharing another truck’s identity.
A fleet-wide token makes one leaked device a fleet-wide problem. Per-truck credentials keep the blast radius and audit record specific.
Validation compares steer, drive and trailer readings with a certified scale or test reference. It checks group error and repeatability before approval.
A parser can accept a perfectly shaped wrong number. Commissioning tests the actual sensor, installation and conversion on the actual truck.
Every commissioning attempt remains visible with its source, samples, thresholds, evaluation and owner decision.
Deleting the failed attempt makes the final approval look cleaner and less trustworthy. The trail shows what changed between attempts.
How it works
The logic is visible. There is no “AI decided” step between the load and the verdict.
Important boundary
This is integration commissioning, not legal-for-trade scale certification. The audited workspace has demo gateways but no approved physical gateway. Retain certified scale tickets and follow the scale vendor’s calibration procedure.
Bind its identity and ingest method to one truck.
Start on level ground with empty and loaded reference checks.
Compare axle groups with the certified reference and the agreed error thresholds.
Only an owner approval moves the installation into accepted physical use.
Where to test it
Related capabilities
