Closed
Milestone
v14.0.0
Breaking Changes
-
GetNextQueuedMessageResponse
(part ofGetNextQueuedMessage.srv
) has a new field:string[] msg_tags
. (!160 (merged)) -
PingModem.srv
andPingTransponders.srv
timeout field is now that same:timeout_sec
and logic has been updated across package (!158 (merged)) -
Tdma*Status.msg
has the following fields added to support QoS tags (!158 (merged)):-
minimum_priority
: will be value set in tag for [this] slot -
time_to_next_dedicated_slot
: time to next un-tagged / un-restricted slot where you are guarenteed to TX if you have any data.
-
New Features / Improvements
-
GetNextQueuedMessageResponse
new field:string[] msg_tags
. (!160 (merged))-
string[] msg_tags
are the tags for the message returned in the response. - since dynamic_queues are not handled by the
message_queue_node
directly, we now use this field to validate responses, and invalid responses are ignored.
-
- added
deserialize_anymsg()
tomac_utils.py
(!160 (merged)) - changed
toggle_software_mute()
intdma_advanced_node
to a switch of typestd_msgs/Bool
and updated logic in `mac_switcher. (!158 (merged)) -
tdma*
can now calculatetime_to_next_dedicated_slot
(!158 (merged))
Bugfixes
-
TagConfig
was not settingself.exclude_queue_ids
. it was settingset.exclude_list
(typo!) and no other nodes were using that attr. - Fixes to message queue (!160 (merged)):
- dynamic queue response tag validation
- was not setting
minimum_priority
when creatingtag_config
instance. - was not passing
minimum_priority
to dynamic_queue_query call.
- set software_mute correctly in
tdma_advanced
(!161 (merged), #46 (closed))
Loading
Loading
Loading
Loading