Publish RTCM

[arpaterson]

Not an issue, but a suggestion.

It would be nice to be able to simply publish and consume rtcm_msgs or similar in some admittedly more obscure set ups.

One such setup is a location with no internet connection, but with

• one or more rovers (separate ROS instances with receivers),
• data link (wifi, or other data link, with some method of ROS topic bridging)
• and a local RTK reference station (another ROS instance, with another receiver and survey antenna).

With the above we can deploy at any site, without the requirement for any internet based NTRIP caster. Instead, using ROS messages to distribute RTCM. This keeps it nice and tidy, with no 'outside ROS' software or communications (eg. u-center, SNIP, which are both non-linux, or even any linux NTRIP caster).

I currently use an F9P, and don't have a Septentrio receiver to trial, unfortunately. But this receiver looks promising and I hope to obtain one soon.

[thomasemter]

Septentrio receivers have built-in NTRIP casters and are able to consume NTRIP streams. This works over the internet as well as within local networks. So you could have such a setup out of the box without taking a detour via ROS and without the need for any 'outside' software.

[arpaterson]

Septentrio receivers have built-in NTRIP casters and are able to consume NTRIP streams. This works over the internet as well as within local networks. So you could have such a setup out of the box without taking a detour via ROS and without the need for any 'outside' software.

That sounds great. Just to be perfectly clear on terminology: Do they have built in NTRIP casters (distribution server that rtcm consuming clients can connect to), or NTRIP servers (client that uploads rtcm to an NTRIP caster)?

[thomasemter]

Septentrio GNSS receivers do have both, a built-in NTRIP caster and NTRIP servers. The caster can be set up to broadcast corrections from the receiver itself (i.e., generated by the receiver’s own NTRIP server) or from any remote NTRIP server.