01
Telemetry drops out
The data come with pauses or require re-transmission on separate sections of the route.
Mobile radio client
Communication and data transmission for mobile equipment
We design wireless communication for equipment that transmits telemetry, tasks, video or technological data in motion. Together we check the application, onboard client, antenna, power supply, radio layer and route. Final acceptance is carried out on a real machine and working speed according to pre-agreed criteria.
Machine → onboard client → radio layer → core → application → route test
The machine is part of the radio system
Connectivity for mobile equipment is designed around the application and route. Onboard clients, antennas, cables, mounting locations, power supply, vibration, vehicle speed, and RF network behavior all affect performance. We validate the design on actual equipment or a representative test rig.
- Permissible gap is set by the working application
- Antenna and mounting location are checked on a specific machine
- Acceptance is carried out along the route and at operating speed
Signs that a solution is needed
Where the connection with equipment in motion is broken
02
The client takes too long to roam
The application session is interrupted when moving between the coverage areas.
03
The signal is strong, but the application fails
Even with adequate signal strength, interference, retransmissions, channel overload, roaming, the wired path, or client behavior can increase latency and packet loss.
04
Equipment cannot withstand the environment
Vibration, dust, temperature, power and installation affect the stability of the onboard unit.
Mobile asset
Each element affects the radio channel.
01
Route and speed
Test operating routes, stops, turns, and the speed at which equipment crosses coverage areas.
02
Onboard client
Access point selection algorithms, supported bands, security, and drivers determine roaming behavior.
03
Antenna and Cable
Check antenna patterns, mounting locations, cable losses, and shielding on the actual vehicle.
04
Power supply and vibration
Power supply, mounts, and equipment ratings must suit actual operating conditions.
05
Requirements of the application
Telemetry, video, and control have different latency and loss limits.
Scenarios
Scenarios for open-pit mine, warehouse, port and other mobile equipment
Mining equipment
Dump trucks, excavators and service machines on changing geography.
Warehouse AGV and forklift trucks
Onboard terminals and automated routes inside the warehouse and yard.
Port equipment
Cranes, loaders, tractors, and other client equipment in outdoor areas.
Locomotives and special transport
Data transmission along a long or repeated route.
Architecture
Connectivity architecture for mobile equipment
Application
Telemetry, dispatching, video or process control.
Onboard node
An industrial client device, local switching, power supply, and enclosure.
Antenna system
Antennas, cables, mount and installation location.
Radio layer
Wi‑Fi, mesh, private LTE or other transport according to the task conditions.
Management
Monitoring, transition events, logging and operation.
Choice of technology
Radio layer is selected by application and route
| Mechanism | What it does | What we check |
|---|---|---|
| Wi‑Fi client | Connects the machine to the controller WLAN with a wide choice of infrastructure. | Client roaming algorithm, security, ranges and compatibility. |
| Industrial mesh | Supports distributed topology and mobile nodes in suitable scenarios. | Routing, number of wireless hops, capacity, and topology changes. |
| Private LTE | It forms a mobile environment in a large area. | Frequencies, devices, latency, economics and integration. |
| Radio modem | Solves specialized data transfer with a given profile. | Protocol, band, range, interference, and regulatory requirements. |
Stages of the project
The field scenario is more important than the laboratory number
- 01
Describe the application
We record data composition, traffic profile, allowable gap impact and critical operations.
- 02
Map the route
We analyze geography, working speed, stops, reversals, existing coverage and the path to the core.
- 03
Inspect the vehicle or machine
Review power supply, vibration, mounting locations, antennas, cables, interfaces, and enclosure requirements.
- 04
We design the solution and prepare a pilot
Choose the client, radio layer and transport, set the configuration and test program.
- 05
We run the pilot
Check compatibility on a test rig, then test actual equipment along a representative route.
- 06
We implement and accept
We scale the confirmed solution and record the results of route and applied tests.
Results
Onboard and network component package
- 01Application Requirements and Communication Parameters Matrix
- 02Scheme of routes and required coverage areas
- 03Specification for onboard client devices, antennas, and mounts
- 04Radio layer configuration and monitoring
- 05Program and protocol of route tests
Acceptance
We test on actual equipment
| Criterion | How to check | Where we document |
|---|---|---|
| Route | Drive the agreed route at operating speed. | Coverage and transition events log. |
| Application | Transmission of real or representative traffic. | Loss, delay and continuity of the session. |
| Onboard node | Verification of power supply, fastening and signal quality in machine operation modes. | Installation report and photographs. |
What affects a mobile equipment connectivity project
01
Timeframes
The duration depends on the number of types of machines, the availability of equipment for inspection and installation, the length and variability of routes, the composition of applications, the state of the radio network, the need for bench inspection and pilot, as well as windows for field tests at working speed.
02
Cost
Cost depends on equipment numbers and installation variants, onboard client devices, antennas and cables, power supply and enclosures, RF and backbone changes, integrations, pilots, site visits, and route test scope. Rollout is estimated after the pilot configuration is validated.
03
Support and SLA
In SLA, we document the supported models and versions, controlled events of the onboard node and network, the order of equipment replacement, changes of the antenna or firmware, repeated tests, reaction time and escalation. A change in the route or type of machine is considered to be a controlled change.
Questions and answers
Frequently asked questions about the solution
01Can onboard client datasheets guarantee roaming performance?
No. Actual roaming depends on the RF environment, network settings, security, vehicle speed, antenna, firmware, and client algorithm. Datasheet figures apply only under the manufacturer’s stated conditions. We validate performance with the operating route and application. The test program records the client model, configuration, speed, route, traffic profile, and acceptance criteria.
02Does mobile equipment always need mesh?
No. Depending on the route, application, site, and available client devices, options include a controller-managed WLAN, industrial mesh, private LTE, or a dedicated radio modem. Calculations and, where risk warrants it, a pilot validate the selection. We compare capacity, latency and packet loss limits, spectrum conditions, onboard equipment, backhaul to the core, and the operating model.
03Why is bench testing insufficient?
A test rig can verify power supply, interfaces, basic compatibility, and configuration. It cannot reproduce the vehicle body, antenna mounting location, shielding, vibration, speed, terrain, and actual RF environment. Final acceptance therefore uses actual equipment and operating routes. The test program and project scope define bench and field checks in advance.
04When should Wi‑Fi or private LTE be selected?
We compare site size and terrain, traffic profiles, latency and packet loss limits, vehicle speed, available spectrum, onboard device compatibility, integration, and total cost of ownership. Range or a standard name alone does not determine selection. Private LTE additionally requires checks of spectrum availability, applicable permissions, and terminal compatibility.
05How is an antenna selected and positioned on a vehicle?
We consider frequency band, antenna pattern, enclosure and mounts, height, cable loss, vibration, washing, climate, and installation safety. Placement must be checked on the specific vehicle rather than copied from another model without verification. We assess the location together with cable routing, mounts, maintenance access, and performance along the route.
06What is checked in the onboard power supply and installation?
Checks cover power supply range and quality, voltage transients, protection, grounding under the agreed design, mounts, connectors, cables, enclosures, and maintenance access. Requirements depend on the vehicle and selected equipment documentation. The installation design is agreed for the specific machine model, mounting location, and operating conditions.
07What happens when you change the route, machine or firmware?
Changes may affect coverage, roaming, antenna arrangements, and application behavior. Before broad deployment, we assess the risk, check the new configuration, and repeat affected route tests. Support procedures may include change control. Retesting depends on the change, application criticality, and agreed acceptance criteria.
08What data are needed for a preliminary assessment?
Provide a route diagram, operating speeds, equipment types and models, onboard data and applications, acceptable effects of connection loss, existing RF network details, power supply, mounting locations, and machine counts by type. These inputs help define the survey, vehicle inspection, pilot, and route tests before a configuration is selected.
The next step
Review equipment routes and application requirements
Send the route diagram, equipment types, operating speeds, data, onboard device models, and acceptable effects of connection loss. The Connectum team will identify the checks needed before design and define a suitable pilot.
Material prepared by Connectum technical team · updated: August 2026