In use Driver, Vehicle and Fleet

OBD Telematics

Name: OBD Telematics
Brand: EntropyWork

Know your vehicle's real condition before a fault reaches the service.

Current status: Our own MCU-based board.

Talk to us about this product Pilot programme

Today and with EntropyWork

Drag the slider to compare today with EntropyWork.

Today

Faults surface only at the service

Tracked only by GPS or driver reports.

With EntropyWork

Vehicle data at the center instantly

Plugs into the OBD-II socket; fault codes, fuel and speed are monitored.

Schematic illustration; values shown are examples.

The situation today

Fleets today mostly monitor vehicle data through driver reports, dashboard and odometer checks, fuel receipts, periodic service records or only a GPS tracking device. What falls short:

Speed and location are known, but the vehicle's own data (RPM, accelerator pedal, fault status) is not.
A fault is not noticed until the vehicle comes in for service.
Fuel consumption cannot be measured per driver and per vehicle.
Risky driving events such as harsh braking and sudden acceleration are not recorded.

How it works, in four steps

Pick a step to follow the data from the field to the center.

Step 01

OBD-II socket

Plug and play

Step 02

CAN / J1939

Vehicle data is read

Step 03

GSM / 4G

Sent to the center

Step 04

Web panel

Fault codes and consumption

Operating principle

The device plugs into the vehicle's OBD-II socket; it takes power and data from the same connection.
Data read from the vehicle ECU over the CAN bus is collected on the device.
The data is sent to the center through the GSM module.
When there is no connection, the data is kept on the device and sent when the connection returns.

Key features

Plug and play
GSM / 4G connectivity
GPS location matching
API integration
Remote updates
2-year warranty

All features

Speed, engine RPM, accelerator pedal position, fuel consumption
Harsh braking and sudden acceleration
Fault codes (DTC), GPS location
Engine temperature, battery voltage, odometer
Keeping data on the device when there is no connection
Plug-and-play design

Details

Only confirmed values are listed.

Technical specifications

Technical specifications
Feature	Value / Status
Hardware	Our own design, MCU-based board
Power	From the OBD socket, 12/24V compatible
Communication	GSM/4G
Vehicle protocols	OBD-II/CAN (passenger and light commercial vehicles, including minibuses); J1939 (buses and heavy vehicles)
Accuracy	Because speed and fuel data are taken directly from the vehicle ECU, it relies on the vehicle's own ECU data

System components

System components
Component	Function
OBD device	Our own design, an MCU-based board; plugs into the OBD-II socket.
GSM/4G module	Sends the data to the center.
Center and web panel	Collects the data and presents per-vehicle status, events, faults and reports.
API	Data transfer to other systems.

Integration

It works matched with the Driver Analysis System (Product 7). It can be integrated with fleet tracking software and other systems via API.

Outputs and reporting

Per-vehicle live status on the web panel
Event list
Fault (DTC) alarm
Fuel, speed and driving reports
Data transfer to other systems via API

Installation and support

Installation

It is plug-and-play; installation takes a few minutes. In vehicles that require a wired connection, the time may be slightly longer.

Installation time varies by product and site.

Support, maintenance and warranty

Remote update is supported.
Maintenance is performed in case of failure or annually.
The warranty period is 2 years.

Areas of use

Fleet operators
Minibus, bus and heavy vehicle operators

Talk to us about this product

Fill in the form; the product name is added for you.

Prefer e-mail? info@entropywork.com

Full name

Organization

Phone (optional)

Topic

Your message

I agree that the information I send is processed to respond to this request.

Personal data notice (KVKK, Turkish) · Your data is processed under this notice.

required