TiTA-OBD
Vehicle telemetry taken from the vehicle itself.
TiTA-OBD adds direct vehicle-bus telemetry to the TiTA platform, reading data through the diagnostic port so vehicle condition sits alongside location in one record.
Why it exists
Location alone says where a vehicle is, not how it is being driven or what state it is in. Adding that usually means a second device from a second supplier with a second portal.
- ·Vehicle diagnostic data acquisition
- ·Location and movement telemetry
- ·Trip and utilisation reporting
- ·Event-based reporting rules
Installed at the vehicle diagnostic port.
Security- · Distinct device identity
- · Authenticated platform connection
- · Encrypted transport
- · Signed firmware images
- · Access-controlled remote sessions
How it fits the stack
Vehicle-bus handling is a C3F module, reusing the same identity, telemetry and update model as the rest of the platform.
About C3FVehicles appear in the same registry as gateways and sensors, with shared alerting and reporting.
About SPIEngineHardware detail
Published values are confirmed. Anything hardware-dependent that has not been verified by engineering is marked rather than estimated.
- Vehicle protocol support
- Pending verification
- Cellular bands
- Pending verification
- GNSS support
- Pending verification
- Device framework
- C3F
- Operating temperature
- Pending verification
- Radio certification
- Pending verification
Highlighted entries are hardware-dependent values awaiting engineering confirmation. They are published only once verified — ask for the current datasheet during evaluation.
Where it is applied
Fleet operations
Utilisation and driver reporting
Maintenance scheduling
Evaluating TiTA-OBD?
Ask for the current datasheet, lead time and integration detail. Anything not yet verified will be identified as such.