Telematic messaging server: Partial write failure field type conflict with input field payload.MessageFrame.value.PersonalSafetyMessage.id

[dan-du-car]

Summary

Collect PSM data from v2xhub, and stream it into the telematic tool. This data is eventually saved into influxDB. The influxDB creates fields and assigns data types based on the data values received. In the PSM message, payload.MessageFrame.value.PersonalSafetyMessage.id field was initially a float/number value, and influxDB created a number field type. However, payload.MessageFrame.value.PersonalSafetyMessage.id was randmonly generated 4 octet, it could populate characters in the payload.MessageFrame.value.PersonalSafetyMessage.id field beside numbers. This causes issue with influxDB when trying to save characters into a number field, see below:

Version

4.3.0 (Current)

Expected Behavior

No exception should occur when save PSM data

Actual Behavior

Failure to save a PSM due to issue with certain fields in the PSM.

Steps to Reproduce the Actual Behavior

1. Setup v2xhub and enable Pedestrian and TelematicBridge plugin.
2. Enable telematic tools in the cloud
3. Create event and assign the v2xhub unit to the event
4. Select and confirm Pedestrian topics on topic management page for this event

Related Work

No response