I have several RS2 devices waiting to be implemented in the field for 24X7 operation. The task I am facing is to reboot all the devices everyday to keep the GNSS clock skew to a minimum for accurate positioning data. Is there a way to automate (through scripts/commands/API). I have imiwin and imibet tried to SSH and run various reboot commands (reboot, restart, shutdown, init 6, etc) but none of them work. could you please help me with this?
Ok I am confused, could you explain the skew in more depth.
I was under the impression Gps satellites have 4 atomic clocks each, so receiving their signal is very accurate way to tell time.
Is it the Reach clock that fluctuates?
Reach can access the internet, could it be locked to a time server to prevent this? I read that GNSS timestamps are accurate within 40ns. Ive logged the gga time vs my computer clock and its crazy close vs ntp.
If anyone could explain the issue, i find it very interesting?