What's new in 0.2.3
Android: DENM cause code decoding
The app now decodes the ETSI EN 302 637-3 UPER payload of every DENM packet to extract causeCode and subCauseCode from the SituationContainer.
Before: Every DENM appeared as a generic "Gefahrenmeldung / Hazard warning" regardless of the actual reported event.
After: The log list and detail sheet show the specific event type:
| causeCode | Label |
|---|---|
| 1 | Traffic condition |
| 2 | Accident |
| 3 | Roadworks |
| 14 | Wrong-way driver |
| 26 | Slow vehicle |
| 27 | Dangerous end of queue |
| 91 | Vehicle breakdown |
| 94 | Stationary vehicle |
| 95 | Emergency vehicle approaching |
| 97 | Collision risk |
| … | (all 22 standard ETSI cause codes) |
Unknown / proprietary cause codes (e.g. OEM extensions) are displayed as "Code N" instead of crashing or being silently dropped.
The parser follows the EN 302 637-3 v1.3.x schema:
- ManagementContainer without extension bit (v1.2.x-compatible)
- SituationContainer with extension bit (v1.3.x)
- AltitudeValue 20 bits, RelevanceDistance 3 bits, RelevanceTrafficDirection 2 bits
- Verified empirically against a real-world capture (556 frames, 13 DENMs from a passenger car performing a stationary-vehicle warning)
Bridge / Windows / Linux
No changes since v0.2.2. The bridge binaries (its-g5-bridge.exe, its-g5-setup.exe, .deb) are the same as in v0.2.1/v0.2.2.
Downloads
| File | Platform | Description |
|---|---|---|
V2X2MAP-0.2.3.apk |
Android 7+ | Sideload via ADB or file manager |
its-g5-bridge.exe |
Windows 10/11 | USB→MQTT bridge + dashboard (double-click) |
its-g5-setup.exe |
Windows 10/11 | First-time setup wizard + firmware flash |
v2x2map-bridge_0.2.3_all.deb |
Debian / Ubuntu | sudo dpkg -i v2x2map-bridge_0.2.3_all.deb |