Routing
AxleGuard matches known weigh stations to the stored route and travel direction. Drivewyze, PrePass or a compatible provider can supply station status and a carrier-specific decision after commercial onboarding; until then, the product uses a safe pull-in fallback.
In the product
What changes
Each outcome connects what the software does to the decision a planner, loader or driver can actually make.
Stored stations are ordered along the route and filtered by direction, with the trip position and station type shown to the planner.
A nearby-place search can return a scale on the other carriageway. Route and direction matching turn a point on a map into an operational stop.
The settings screen accepts the adapter URL, account identifiers and bearer credential issued during Drivewyze, PrePass or compatible-provider onboarding.
The provider contract grants access; AxleGuard supplies the connection controls, test step, cache and response contract.
When no tested provider decision is available, every route tells the planner and driver to plan to pull in.
Unknown is not bypass. The four-second timeout and safe fallback keep a provider outage from producing a dangerous optimistic answer.
How it works
The logic is visible. There is no “AI decided” step between the load and the verdict.
Important boundary
No live bypass provider was connected in the audited workspace. Drivewyze and PrePass require commercial enrolment and issued credentials. Posted signs and roadside instructions always take priority.
The carrier, vehicles and provider account are enrolled commercially.
Store the adapter URL, IDs and bearer credential in the owner-only settings.
Verify DNS, TLS, authentication and the response schema before use.
Cache short-lived decisions and plan to pull in whenever the signal is absent or invalid.
Where to test it
Related capabilities
