-
Notifications
You must be signed in to change notification settings - Fork 0
Test RTCM Message Count Progression
Note: BSM Message Count Progression Events can be configured to enable aggregation using the rtcm.message.count.progression.aggregateEvents configuration setting, or the ENABLE_AGGREGATE_RTCM_MESSAGE_COUNT_PROGRESSION environment variable. If aggregation is enabled, events will be delayed by up to the configured aggregation.interval, which is 60 seconds by default.
Disable aggregation to reproduce the test output below.
If aggregation is enabled, events are output to:
topic.CmRtcmMessageCountProgressionEventAggregation
If aggregation is disabled, events are output to:
topic.CmRtcmMessageCountProgressionEvents
Three RTCM Messages:
- Reference message
- A message with incremented message count relative to (1), but the same data
- A message with the same message count ad (2) with differenct coordinates
RTCM-MessageCountProgression-invalid.csv
Two events because message count shouldn't be incremented for identical messages, and message count should be incremented for differing data.
2 events
different message count, same data:
{
"eventGeneratedAt": 1767923198877,
"eventType": "RtcmMessageCountProgression",
"intersectionID": -1,
"roadRegulatorID": -1,
"source": "172.18.0.1",
"stationId": 2432,
"messageType": "RTCM",
"dataFrame": "MSG_RTCMcorrections",
"change": [
],
"messageCountA": 82,
"messageCountB": 83,
"timestampA": 1767923196478,
"timestampB": 1767923197472
}same message count, different data:
{
"eventGeneratedAt": 1767923199849,
"eventType": "RtcmMessageCountProgression",
"intersectionID": -1,
"roadRegulatorID": -1,
"source": "172.18.0.1",
"stationId": 2432,
"messageType": "RTCM",
"dataFrame": "MSG_RTCMcorrections",
"change": [
"coordinates",
"longitude",
"latitude",
"elevation"
],
"messageCountA": 83,
"messageCountB": 83,
"timestampA": 1767923197472,
"timestampB": 1767923198483
}Two RTCM messages with different message counts, and differing contents.
RTCM-MessageCountProgression-valid.csv
No events because both message count and message contents differ.
No events, as expected