In my particular case,
The NTRIP client can broadcast to 255 on a particular port
I can set the module to accept everything on the correct port.
With us, the Ntrip provider has two option
Has set up a fixed mountpiont, and when I connect to it, I get corrections from just one base station and the server can not know the location of my rover.
But if I move away and work on some other field that is distant from the above base station, this base station is no longer suitable for me.
Then I need to hook up to a server with some other mountpiont that checks the rover location, and by the location it assigns the nearest base station that sends me the corrections.
So it would be good that we can enter our location into a ntrip client that will send the server to a specified time (ms) as it was done in the Lefebure ntrip client or RTKLIB.
I changed the code, and if I changed the broadCasterIP etc. it still connects to rtk2go...
Since it's hard for me to write in English, I will set up some pictures that describe what I mean (the picture tells a thousand words)
And I repeat this is my case, maybe someone will not respond to these settings.