NTRIP Servers can sandbox clients that request too often. I have a fix.

[pondersome]

NTRIP Servers, rtk2go in particular, will sandbox users that request rtcm corrections too often, but the NTRIP client is hard-coded to 10hz. Sandboxed users do not get usable correction data.

I have a branch which allows the user to change the rate at which the server communication happens through a parameter. I've also added a convenience launch file to bring up all three nodes at once.

Would you like me to submit a PR?

[LauBorch]

I guess I do not get data from the server... Is this what is indicating a too high request rate?:

ntrip_ros.py-1] [INFO] [1729679208.842514723] [ntrip_client.ntrip_client_node]: Connected to http://www.sapos-ni-ntrip.de:2101/VRS_3_4G_NI
[ntrip_ros.py-1] [DEBUG] [1729679241.304787853] [ntrip_client.ntrip_client_node]: Read 0 bytes
[ntrip_ros.py-1] [DEBUG] [1729679241.404927280] [ntrip_client.ntrip_client_node]: Read 0 bytes
[ntrip_ros.py-1] [DEBUG] [1729679241.503433741] [ntrip_client.ntrip_client_node]: Read 0 bytes
[ntrip_ros.py-1] [DEBUG] [1729679241.604793467] [ntrip_client.ntrip_client_node]: Read 0 bytes
[ntrip_ros.py-1] [DEBUG] [1729679241.704850024] [ntrip_client.ntrip_client_node]: Read 0 bytes
[ntrip_ros.py-1] [WARN] [1729679241.706553061] [ntrip_client.ntrip_client_node]: Reconnecting because we received 0 bytes from the socket even though it said there was data available 5 times

My credentials work in u-center...

[pondersome]

This does not look like a sandboxing issue I've experienced. I don't have any experience with the caster you are using, but this seems more like some other kind of failure to meet the requirements of the service, even though it looks like you connected successfully. Are you sure you are sending back the NMEA data? Some NTRIP servers require that.

In case you want to try it out, my changes are here:
https://github.com/pondersome/RTK_GPS_NTRIP/tree/ntrip-rate-control

This includes a new launch file to bring up all the nodes in a coordinated fashion.

[LauBorch]

I managed to get it to work. It was indeed the missing nmea data because I was indoors.