V2X for mining and autonomous haulage.
A surface mine is an unusually good environment for cooperative communication and an unusually bad one for optical perception. Dust, night operation, extreme gradients, engineered berms and machines whose blind areas are a consequence of their size — all of it defeats sensing and none of it defeats a broadcast position.
It is also an environment with its own hazard framework, its own regulator and its own equipment standards, none of which came from the automotive world. This page sets cooperative V2X messaging inside that framework rather than beside it, and is explicit about the ceiling: V2X is a communication layer that complements an autonomous haulage system, a proximity-detection system and a private site network. It replaces none of them.
Mining did not wait for V2X. It has its own hazard model, and it is a good one.
Anyone proposing cooperative communication for a mine site has to start from the control framework the sector already runs on, not from a road-safety brochure.
The Earth Moving Equipment Safety Round Table maintains a vehicle-interaction performance requirement, EMESRT PR-5A, which enumerates surface vehicle-interaction scenarios and sorts defensive controls into nine levels. The lower levels are organisational — site requirements, segregation, operating procedures, authority to operate, fitness to operate, operating compliance. The upper three are technical, and they are where communication technology enters:
- Level 7 — operator awareness. The operator is made aware that another machine or person is present.
- Level 8 — advisory controls. The system advises the operator that an interaction is developing.
- Level 9 — intervention controls. The system acts on the machine, taking control from the operator.
EMESRT worked with the International Council on Mining and Metals from 2018 on the vehicle-interaction programme, and the machine-side interface that makes Level 9 practical — a standard protocol between a proximity-detection system and the original equipment manufacturer's machine — is standardised as ISO 21815. That is the integration boundary a communication layer has to respect: the detection system talks to the machine through a defined interface, and the machine's own safety functions decide what happens.
Read that hierarchy carefully, because it sets the honest ceiling for V2X in mining. Cooperative messaging is an excellent source of Level 7 and Level 8 information and a plausible input to Level 9. It is not itself an intervention control, and it does not replace the levels below it.
Haul roads defeat sensors in ways an open highway does not.
A surface mine is an unusually favourable environment for cooperative awareness and an unusually hostile one for optical perception: dust and blast fume, night operation, extreme gradients, berms and windrows that block line of sight by design, ramps with switchbacks, and vehicles whose stopping distance is measured in tens of metres. A haul truck's blind area is not a design flaw to be sensed away — it is a consequence of the machine being four metres above the road.
The pattern that makes cooperative messaging useful is the same one it exploits on public roads: a machine that broadcasts its own state does not have to be seen to be known about. A light vehicle in a haul truck's blind area is invisible to a camera and obvious to a receiver.
| Scenario | What cooperation contributes | EMESRT level |
|---|---|---|
| Haul-road interaction, truck and light vehicle | Continuous position, speed and heading from every participant, independent of line of sight | 7 to 8 |
| Blind corners, switchbacks and berm-obscured approaches | Non-line-of-sight awareness before the geometry allows detection | 7 to 8 |
| Pit intersections and haul-road junctions | Approach awareness and, where a controller exists, right-of-way information | 7 to 8 |
| Loading zones: shovel, excavator and truck spotting | Machine state and intent during the spot-and-load cycle, where reversing dominates | 7 to 8 |
| Dumping and tip-head operations | Edge and queue awareness, and coordination between successive trucks | 7 to 8 |
| Mixed autonomous and manned fleets | An explicit, authenticated declaration of what a machine is and what it is about to do, rather than an inference | 7 to 9 |
| Convoy and sequenced haulage | Sequence and gap coordination between machines under one operator's rules | 7 to 8 |
| Disabled equipment and maintenance interventions | Event notification with a validity area, the same shape as a stationary-vehicle warning | 7 |
| Geofenced hazard zones: blasting, high wall, wet areas | Zone information distributed to every machine that enters the area | 7 to 8 |
| Infrastructure-assisted perception at fixed hazards | A fixed sensor node sharing detected objects with approaching machines | 7 to 8 |
| Personnel on foot near machines | A worn or carried device broadcasting presence, the industrial analogue of vulnerable-road-user awareness | 7 to 8 |
Cooperative positioning — using received messages and infrastructure references to improve on a machine's own satellite fix — is a reasonable objective in a pit, where multipath off high walls degrades positioning exactly where accuracy matters most. It is an area of active work rather than a settled capability, and is described here as the former.
Five differences, and each one changes the architecture.
| Dimension | Public road | Mine site |
|---|---|---|
| Spectrum | A designated ITS band under a national allocation — in India, 5875–5925 MHz proposed, with an on-board-unit licence exemption over part of it | No public ITS entitlement follows a machine onto private land. Site radio is whatever the operator is licensed or permitted to run, commonly a private cellular network |
| Trust | A national or regional PKI the vehicle must be admitted to | No national scheme to join. The site operator is effectively its own policy authority, enrolling its own fleet |
| Population | Open, anonymous and unbounded; pseudonymity is a requirement | Closed, enumerated and employed. Accountability is usually wanted; pseudonymity usually is not |
| Rules | Road traffic law, national type approval | The operator's own traffic management plan, plus the applicable mine-safety regime |
| Environment | Automotive temperature, shock and ingress | Continuous vibration, dust ingress, wash-down, and machines in service for decades |
The trust column is the one that surprises people. On a public road, the hard problem is admitting strangers safely and anonymously. On a mine site the population is known, so enrolment is easy — and the interesting questions move to credential lifecycle on machines that are rebuilt rather than replaced, to contractor vehicles that come and go, and to what happens when a device is pulled from a decommissioned machine. The enrolment-and-authorisation split still applies; the policy sitting on top of it is written by the operator rather than by a regulator.
On connectivity, the industry's centre of gravity is private LTE and 5G, which carries dispatch, fleet management, telemetry and autonomous-equipment traffic. Direct device-to-device sidelink is a different tool for a different job: peer-to-peer, low-latency, and available when the wide-area network is degraded or a machine is in a radio shadow. Whether a given site needs one, the other or both is a site-specific question about coverage, latency and what the safety case depends on — and this site does not assert a general answer to it.
Stated plainly, because the category error here is expensive.
Cooperative communication is a layer that carries authenticated statements between machines and infrastructure. On a mine site it is not a replacement for:
- the autonomous haulage system — perception, planning, control and its own safety argument;
- on-board perception sensors, which remain the only source of truth about unequipped objects;
- the fleet-management and dispatch system that decides what each machine is doing;
- the private cellular or radio network that carries site operations;
- the proximity-detection and collision-avoidance system certified for the site, and its machine interface; or
- the levels of the EMESRT hierarchy below Level 7, which remain where most of the risk reduction actually comes from.
It complements all of them, and its distinctive contribution is narrow and real: an authenticated, low-latency, non-line-of-sight statement of where a machine is and what it intends, available to every participant rather than only to the central system. Everything else on this page follows from that one property.
Endpoint engineering, not site autonomy.
The work Ambimat takes on is the endpoint and its integration: on-board and roadside or fixed-node hardware and its customisation for an environment, embedded software, the device-side security and credential path, and integration with the systems a customer already runs. V2X hardware design →
Ambimat does not operate mine sites or mine networks, is not an autonomous-haulage supplier, and does not integrate site autonomy programmes end to end. Where a machine interface such as ISO 21815 or a certified collision-avoidance system is in scope, that is the equipment manufacturer's and the safety supplier's territory; the communication endpoint is the part that gets engineered here.
Two hardware notes carry over from the public-road platforms and are worth stating in an industrial context, because they are frequently assumed the other way: the on-board development platform has no vehicle data bus interface and no lidar, radar or camera hardware. Machine data and perception come from the customer's own systems through an agreed integration, not from the unit. The published specification →
Where this fits.
V2X use cases
The full catalogue, and the three environments this is one of.
Message sets
The awareness and event messages an industrial profile would start from.
V2X PKI
Enrolment, authorisation and what changes when the operator writes the policy.
AmbiOBU
The on-board development platform and exactly what it does and does not carry.
V2X hardware design
Customising an endpoint for an environment that is not a passenger car.
V2V
The direct vehicle-to-vehicle mechanism the haul-road cases rest on.
Questions this page answers.
Is V2X used in mining?
Cooperative vehicle-to-vehicle and vehicle-to-infrastructure messaging maps onto mining's vehicle-interaction problem well, and the message sets transfer. What does not transfer is the regulatory context: a mine site has no public ITS spectrum entitlement and no national V2X trust framework to join, so site connectivity is typically a private network the operator is licensed to run, and the operator writes its own credential policy.
What is EMESRT PR-5A?
A vehicle-interaction performance requirement maintained by the Earth Moving Equipment Safety Round Table. It enumerates surface vehicle-interaction scenarios and sorts defensive controls into nine levels, from site requirements and segregation at the bottom through to operator awareness at level 7, advisory controls at level 8 and intervention controls at level 9. Cooperative messaging is a source of level 7 and level 8 information and a plausible input to level 9; it is not itself an intervention control.
Does V2X replace an autonomous haulage system?
No. It replaces neither the autonomous haulage system, nor on-board perception sensors, nor the fleet-management and dispatch system, nor the private cellular network, nor a certified proximity-detection and collision-avoidance system and its machine interface. Its distinctive contribution is narrow: an authenticated, low-latency, non-line-of-sight statement of where a machine is and what it intends, available to every participant rather than only to the central system.
What is ISO 21815?
The standard covering the interface between a proximity-detection system and the machine, developed so that intervention control at the top of the EMESRT hierarchy can be implemented consistently across equipment manufacturers. It is the integration boundary a communication layer has to respect: the detection system talks to the machine through a defined interface, and the machine's own safety functions decide what happens.
Last updated 2026-09-07 · Technical reference maintained by Ambimat Electronics, Ahmedabad, India. Corrections: neel.shah@ambimat.com