Gnimu protocol
The Gnimu protocol defines how Gnimu devices stream telemetry over Bluetooth Low Energy (BLE). Every device sends the same fixed-layout frame and uses the same BLE identifiers, so an app set up for one Gnimu device works with all of them.
A device fills in the parts of the frame it has and marks the rest as not valid. The frame has blocks for:
- GNSS: position, altitude, speed, heading, accuracies, fix and satellites.
- IMU: accelerations and rotation rates, in the car’s axes.
- Vehicle: RPM, throttle, speeds, temperatures, pressures, gear and more.
- Power: supply voltage, battery charge and charging.
Every field has a published offset, type and scale, so one table is enough to read any Gnimu device, in a Gnimu app or in any app that maps fields by byte offset, such as AutoX Data Logger’s custom BLE sensor.
In progress. Version 1 is complete enough to implement, with reference implementations in C++, Python and Swift and test vectors, but it may still change. Gnimu-CAN sends it, and the Gnimu firmware can be built to send it.
License
The specification and reference code are under the Apache License 2.0, so you can implement the protocol in any software, open or closed source.