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

ntrip_client does not attempt to reconnect to ntrip server if initially unsucceessful #11

Open
vinnnyr opened this issue May 24, 2022 · 1 comment
Assignees

Comments

@vinnnyr
Copy link

vinnnyr commented May 24, 2022

If the driver does not have internet access or is otherwise unable to reach the ntrip server initially, it should try to reconnect rather than fatally exit.

Environment: ROS2, Galactic, Apt Install

Logs:

[ntrip_ros.py-2] [ERROR] [1653318828.756822754] [ntrip_client_node]: Unable to read response from server at <IP>
[ntrip_ros.py-2] [ERROR] [1653318828.760031632] [ntrip_client_node]: Exception: [Errno 110] Connection timed out
[ntrip_ros.py-2] [ERROR] [1653318828.763373159] [ntrip_client_node]: Unable to connect to NTRIP server
[ERROR] [ntrip_ros.py-2]: process has died [pid 75, exit code 1, cmd '/opt/ros/galactic/lib/ntrip_client/ntrip_ros.py --ros-args -r __node:=ntrip_client_node --params-file /tmp/launch_params_be1qi55t -r /nmea:=/nmea/sentence'].
@robbiefish robbiefish self-assigned this May 27, 2022
@tomy983
Copy link

tomy983 commented Jun 16, 2022

Hi @vinnnyr,
would you mind testing this PR #13 ?
It should handle your problems.

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

3 participants