Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature request: publish the current connection state #52

Open
gennartan opened this issue Aug 2, 2024 · 0 comments
Open

Feature request: publish the current connection state #52

gennartan opened this issue Aug 2, 2024 · 0 comments

Comments

@gennartan
Copy link

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:

uint8 STATUS_INITIALIZING = 0
uint8 STATUS_CONNECTED = 1
uint8 STATUS_SERVER_NOT_FOUND = 2
uint8 STATUS_BAD_MOUNTPOINT = 3
uint8 STATUS_BAD_CREDENTIALS = 4

uint8 status
string server
string mountpoint
string message

What do you think about it ?

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

No branches or pull requests

1 participant