The problem is that the time reported by the receiver before time sync is nonsense, as the unit does not carry a battery-backed RTC clock. So any diagnostics (like CPU temperature) we get from the unit before it gets a fix carries wrong time and that’s also a problem. We access the unit either via API or SSH to collect the diagnostics. We need to be able to “force” the robot’s local time to the unit right after startup. The robot runs a local NTP server that can be used for this. But the firmware restrictions in M+ do not allow us to do it.
I agree.
And that’s the problem. You want to have RTK → you want to have Internet → you need to get it over Wifi (not good!) or do a harakiri over the wire to point the unit to a relay NTRIP server on the robot (Add default route to the usb1 device, too). Things could be so simple had there been the other default route and a customizable DNS server…