Four roads, one contract
It doesn't matter if the data comes from a phone, a tracker, your own system or the vehicle manufacturer: it goes in the same way and preserves where it came from.
Same vehicle. Visible origin.
A reading of the phone is not presented as a measurement of the engine.
Explanatory outline. The connection and its scope are validated for each case.
The four ways in
Which one is implemented first depends on your operation, not on a imposed order. Starting with one does not force you to migrate later.
Dromivia
The driver's phone as a source of position and events, without hardware installed. Useful for starting or for third-party vehicles.
See DromiviaGateway of protocols
Reception of GPS, OBD and CAN trackers for their native protocols, with their own basis and credentials and only the required ports open.
Find my equipmentAPI platform
Direct delivery from your own system or from another telematics platform, with the same observation contract.
See APIManufacturer's data
Incorporation of vehicles with factory telemetry, without installing additional hardware where it already exists.
Consult availabilityNormalize without erasing from where the data came from
A read odimeter of the vehicle bus, a GPS estimate and a hand-written reading are different. Standardization makes them comparable; it does not make them equivalent.
Each observation conserves
- · Origin from which it came
- · Original unit when it helps to audit
- · Precision declared by the source
- · Time of origin and time of reception, separated
If two sources report the same
Priority is defined by sign and window of validity. Contradutory signals are maintained with their origin and an explicit selection policy.
What never happens: to add twice the same kilometres or to generate two trips by mixing two flows of the same vehicle.
Capacity matrix
We publish the status by capacity instead of a list of logos. Protocol compatibility does not amount to commercial integration, accuracy, safe channel or support of all fields.
| Capacity | State | Status |
|---|---|---|
| Position and tourLatitude, length, speed and course with time of origin and reception. | Supported | Common contract for the four roads |
| Engine readingOdometer, hours, fuel and failure codes from the vehicle bus. | Validation | By combination of model, protocol and firmware |
| Reconciliation after fallRecovery of missing positions per cursor with overlap. | Validation | It requires prolonged drop and restart test. |
| Detection of collisionEnergy-differentiated impact events, with reconstruction. | Validation | According to device; not inherited from protocol |
| Expansion sensorsTemperature, door opening and driver identification. | Planned | By specific accessory and harness |
| Writing to the deviceRemote locking, cutting or configuration commands. | Limited | Only protocols with strong authentication |
The detailed matrix is published by combination of manufacturer, model, protocol, firmware and effectively tested fields. They are not published as their own capabilities, inherited figures from the documentation of a protocol or a third party chamber.
Does the tracker you already have serve?
2,159 models of 103 brands enter through the gateway without changing the hardware installed. Search yours by brand, model or protocol.
Preguntas frecuentes
Tell us what hardware you have.
With the brand, the model and the protocol we can tell you which fields come in and which should be validated.