All products Decision layer Data collection Trip Counting Module
Active safety and control
Engine and thermal management

MetaTrack CAN bus telematics and vehicle tracking

It reads beyond location.

CAN bus telematics that reads the engine, not just the location

MetaTrack
150+CAN parameters, led by fuel, tonnage and fault codes
4GData link to MetaFMS; stored on the unit outside coverage
9–36 VSupply range for 12 V and 24 V vehicles
MetaFMSMap, reports and alarms in one panel

Knowing the location is not managing the operation

Most fleets know where their vehicles are, but not what they are doing. Fuel, idling, engine hours, AdBlue and fault code data are generated on board but never reach the office. When the data stays in the field, decisions rest on guesswork.

Idling

The engine is running but no work is being done. Unnecessary idling adds to fuel costs and, without vehicle idling time tracking, its source is hard to pin down.

Invisible data

Fuel use, engine hours, temperature, RPM, AdBlue, tonnage and fault data exist in the vehicle but not at the office. The site ends up being run by phone.

Unplanned downtime

When a fault code or critical vehicle data is noticed too late, the vehicle ends up stranded. The result is unplanned downtime and higher maintenance costs.

Tracking on paper

Trips, routes and working hours become estimates. Without a view of past routes and work zones, the operation is hard to control.

Scattered data

If data from different vehicle types is not gathered in one system, performance cannot be compared across the fleet.

How CAN bus vehicle tracking works

MetaTrack V2 is the CAN bus GPS tracker fitted to the vehicle. It reads the vehicle's own data bus, adds the position and sends everything to MetaFMS, where reports and alarms are produced.

Sample interface: model, plate, fuel level, total distance and engine temperature on a MetaFMS vehicle panel
Sample interface: the live fleet map, with vehicles listed as active, idling, parked or offline
Sample interface: device cards showing streaming, silent and offline units, with device faults below
Sample interface: fleet status and vehicles needing attention in fleet analytics
  1. Sample interface: model, plate, fuel level, total distance and engine temperature on a MetaFMS vehicle panel

    Reads the vehicle's data

    The unit reads engine and operating data from the vehicle's CAN bus / SAE J1939 line. Which items can be read depends on the vehicle's CAN structure.

  2. Sample interface: the live fleet map, with vehicles listed as active, idling, parked or offline

    Adds the position

    The GPS position is added to the same data, so every engine reading is tied to a location. Where the vehicle is and what it is doing appear together.

  3. Sample interface: device cards showing streaming, silent and offline units, with device faults below

    Sends it over 4G

    Data is transferred over 4G to the MetaFMS server. Where there is no coverage, data is kept on the unit and sent automatically once the connection returns.

  4. Sample interface: fleet status and vehicles needing attention in fleet analytics

    Becomes a decision in the panel

    Users follow the live map, reports and alarms in the MetaFMS web panel. Reports and alarms require MetaFMS.

Screens are from the MetaFMS test panel running on simulated data; names, addresses and coordinates have been blurred.

Eight data items read from the CAN bus

MetaTrack V2 reads these items from the vehicle's CAN bus and brings them into MetaFMS. Each one has a job: maintenance intervals, fuel analysis, engine health or the load carried.

Speed
64km/h
Engine speed
2,311rpm
Fuel level
48%
Engine temperature
89°C
Total distance
121,237km
Tonnage
18.5t
Average oil pressure (today)
374.8kPa
Engine hours (today)
1.70h

Values are examples from the MetaFMS test panel (simulated data): the first six from the vehicle’s live position card, oil pressure and engine hours from the daily CAN cards on the vehicle page. They are not live data, and the items available depend on each vehicle’s CAN structure. Tonnage is the vehicle's own CAN data and has a margin of error.

Location, engine data and reports in one panel

MetaTrack V2 collects the data and MetaFMS turns it into reports. Every feature below is used through the MetaFMS panel.

Trip Counting ModuleCounts every trip from the loading site to the dumping site, automaticallyOpen the feature page ›

One vehicle’s idling and consumption for one day

Distance travelled
49 km
Fuel used
31.7 L
Engine running time
2.0 hours
Idling time
0.9 hours
Idling as a share of running time
45%
Consumption
15.8 L/h (0.65 L/km)

Figures are one day of data for a single vehicle from the MetaFMS test panel (Fleet Analytics › Efficiency, simulated data). They should not be read as a fleet average or an expected result.

From the panel

The vehicle's live position full screen, with speed, engine speed, fuel level, engine temperature, total distance and load.
Speeding events across the fleet are listed as they happen, each with a link to its route.
On the vehicle page, speeding events are listed with the measured speed and the limit; the event detail opens on the map.
A speeding event is summarised with peak, threshold, duration and distance; its route is shown on the map.
On the vehicle page, CAN data as daily, weekly or monthly averages, with the day's status strip below.

Where it works

An excavator loads a tipper truck on a construction site, with a wheel loader and a concrete mixer nearby

Earthworks and construction

Trucks and excavators are tracked in the same list, with site entries, exits and time worked inside the zone reported.

Trucks and excavators working in an open pit, aerial view

Mines and quarries

In a pit with no coverage, data stays on the unit and reaches the panel once the vehicle is back in range.

Concrete silos and a stair tower at a plant

Concrete and cement

The batching plant and the site are set up as zones, and vehicle entries, exits and fuel use are followed in one panel.

A concrete mixer, a tipper truck, a wheel loader and an excavator side by side

Public sector and municipalities

Different vehicle types and machinery come together in one panel, with maintenance intervals tracked from engine hours.

A truck on a highway, marked by the road camera analysis

Logistics and haulage

Idling and fuel use are reported vehicle by vehicle, and past routes can be replayed.

Storage tanks at an industrial site

Energy and industrial sites

Site equipment, generators included, is monitored from the same panel, with engine hours and fault codes in a single list.

Technical specifications

MetaTrack V2 J1939 tracker

Supply voltage
9–36 V
Vehicle data
CAN bus / SAE J1939 (CAN bus module included)
Positioning
GPS
Communication
4G, to the MetaFMS server
Without coverage
Data kept on the unit and sent automatically when the connection returns
CAN data read
More than 150 parameters, led by fuel, tonnage and fault codes; AdBlue level, engine hours, RPM, engine temperature and total distance are also read
Tonnage data
The vehicle's own CAN data; has a margin of error
Equipment
Cars, heavy vehicles, construction machinery, generators

MetaFMS platform

Access
Web panel; fault codes on mobile and desktop
Reports
Zones, efficiency, routes, idling and working time, fuel consumption, faults and maintenance
Reporting periods
Daily, weekly, monthly, custom
Permissions
Users with different permission levels
Export
Reports can be exported
Calculated engine hours
Derived from RPM where engine hours are not available on CAN

The CAN data items available depend on each vehicle's CAN structure. The supply range is the value stated in the product certificate.

Certificates

Certificates are issued per product and model. Select one to view it.

Certificates were issued under the company's previous title, Metadiag Bilişim Teknoloji Sanayi ve Ticaret Ltd. Şti.

Part of the ecosystem

Metadiag MetaTrack sits in the product family's data collection layer. Its position, speed and J1939 telematics data from the CAN bus feed the fuel, idling, maintenance and zone screens in MetaFMS, alongside data from MetaDamper, MetaVision and the Trip Counting Module. With support for generators and construction machinery, the panel covers site equipment as well as trucks.

Frequently asked questions

Do I need MetaFMS to use MetaTrack?

Yes. MetaTrack V2 collects and sends the data; the map, reports and alarms are produced in MetaFMS fleet management software. The unit is therefore always used together with MetaFMS.

Which vehicles and equipment does it work with?

It is designed for all equipment, including cars, heavy vehicles, construction machinery and generators, so a single vehicle tracking system covers the whole fleet. Each vehicle type is defined in the panel, and trucks and excavators can be followed in the same list.

Which CAN data does it read?

More than 150 CAN parameters are read. The main ones are fuel (total and instant consumption), tonnage and fault codes; AdBlue level, engine hours, engine speed (RPM), engine temperature, total distance and idling status are monitored too. Tonnage is the vehicle's own CAN data and has a margin of error. Which items can be read depends on the vehicle's CAN structure.

What happens where there is no coverage?

Data is kept on the unit and transferred to MetaFMS automatically once a connection is available.

What if the vehicle does not report engine hours on CAN?

In that case MetaFMS calculates engine hours from RPM data and shows them separately in the panel as ‘calculated engine hours’. MetaTrack can therefore serve as an engine hours tracking device on these vehicles too.

What does the idling report show?

It shows idling status and duration vehicle by vehicle, with its share of running time. For example, on the MetaFMS test panel one vehicle spent 0.9 of its 2.0 engine hours in a day idling (45%, simulated data). That is a single vehicle's data, not a fleet average.

Which certificates does MetaTrack V2 hold?

It holds Turkish Domestic Goods Certificates for hardware and software, a Technological Product Certificate and a Technological Product Experience Certificate. The hardware certificate is class B, with 87.85% domestic content; the software has 100% domestic content. Certificate numbers and dates are listed under Metadiag certificates.

Can trips be counted for mixers and tankers?

Yes. The Trip Counting Module counts trips between the loading and dumping sites; the same algorithm works for tippers, concrete mixers, water and fuel tankers. Position and CAN data come from MetaTrack.

How does MetaTrack display vehicle fault codes?

MetaTrack reads the fault codes available through the vehicle's CAN bus and sends them to MetaFMS. Codes can be viewed on mobile and desktop, while engine hours, fault codes and AdBlue data support maintenance and fault alerts.

MetaTrack measures and reports; it does not intervene in the vehicle. The CAN data items available depend on each vehicle's CAN structure. Panel values on this page are examples taken from real screens, and single-vehicle data should not be read as a fleet average.

MetaTrack

Let's start with a few pilot vehicles in your fleet

We plan the survey, installation and reporting around your site. Our team reviews your vehicles and recommends the right configuration.

Products of interest