In other words, the relay service will eliminate the need for a Static IP address. This method will pass your RTCM3 corrections from your base to your rover.
However....I do not foresee it will be able to do everything that can be done if you have your own Static IP. With your own Static IP, you have full control of your base remotely as if you had a 6 mile long Bluetooth connection to your base. Using TCP Direct, I can Start, Stop, Download, and reprogram my base from anywhere on earth. There are times that I can be deep in the woods, collect a point with RTK that is not feasible to return to, sit down on a log, Stop and Download the base, send to DPOS, and get that wonderful confidence level of seeing my static solution match the RTK solution. I can then restart the base, and continue on.
I am pretty sure that the RTK Relay service will not be bidirectional. If it is at all possible to be so, then let this stand as a challenge to the engineers.... to make it so.
However....I do not foresee it will be able to do everything that can be done if you have your own Static IP. With your own Static IP, you have full control of your base remotely as if you had a 6 mile long Bluetooth connection to your base. Using TCP Direct, I can Start, Stop, Download, and reprogram my base from anywhere on earth. There are times that I can be deep in the woods, collect a point with RTK that is not feasible to return to, sit down on a log, Stop and Download the base, send to DPOS, and get that wonderful confidence level of seeing my static solution match the RTK solution. I can then restart the base, and continue on.
I am pretty sure that the RTK Relay service will not be bidirectional. If it is at all possible to be so, then let this stand as a challenge to the engineers.... to make it so.