You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I would be nice to have a topic to publish the current connection state. This is useful when you want to check the node status in a single command. This is also useful if you want to automatize ntrip control. In case of connection error, the state could be retrived easily by other nodes.
My initial idea was to publish the node state on the diagnostics topic. It is nice when a human wants to check the node status, but lacks of reliability when another node subscribe and use this information.
So I think that the best idea would be to create a new pacakge ntrip_msgs that would contain the definition of the connection status. The ntrip client would then publish this message at regular interval.
I would be nice to have a topic to publish the current connection state. This is useful when you want to check the node status in a single command. This is also useful if you want to automatize ntrip control. In case of connection error, the state could be retrived easily by other nodes.
My initial idea was to publish the node state on the
diagnostics
topic. It is nice when a human wants to check the node status, but lacks of reliability when another node subscribe and use this information.So I think that the best idea would be to create a new pacakge
ntrip_msgs
that would contain the definition of the connection status. The ntrip client would then publish this message at regular interval.Here is a suggestion for the message type:
What do you think about it ?
The text was updated successfully, but these errors were encountered: