Skip to content

Conversation

@armallen
Copy link
Contributor

@armallen armallen commented Jul 9, 2025

Description

API compatibility

Does this change introduce a API compatibility risk?

API compatibility plan

If the above is "Yes", please detail the compatibility (or migration) plan:

JIRA Reference

https://swift-nav.atlassian.net/browse/BOARD-XXXX

desc: Chain and type of flag.

- MSG_SSR_FLAG_HIGH_LEVEL:
- MSG_SSR_FLAG_HIGH_LEVEL_DEP_A:
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

MSG_SSR_FLAG_HIGH_LEVEL becomes MSG_SSR_FLAG_HIGH_LEVEL_DEP_A

Comment on lines +46 to +50
short_desc: Deprecated
desc: Deprecated.
public: false
replaced_by:
- MSG_SSR_FLAG_HIGH_LEVEL
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ensure deprecation is explicit

- 3: Not monitored

- MSG_SSR_FLAG_HIGH_LEVEL:
id: 0x0BBA
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

New message id: 3002

Comment on lines 205 to 210
- atmo_corr_time:
type: GPSTimeSec
desc: GNSS reference time of the correction associated to the flag.
desc: GNSS reference time of the atmospheric correction associated to the flag.
- sat_corr_time:
type: GPSTimeSec
desc: GNSS reference time of the satellite correction associated to the flag.
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Message stores two correction time:

  • one for sat corr
  • one for atmo (iono + tropo) corr

preamble: "0x55"
msg_type: "0x0BBA"
sender: "0x0042"
length: 37
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

6 more bits compared with deprecated message (GPSTimeSec is u32 + u16)

@armallen armallen force-pushed the armallen/new-high-level-message branch from 568b7d4 to 03fda3b Compare July 17, 2025 14:31
@sonarqubecloud
Copy link

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants