RTK solution restarts when enabling/disabling position output

I’m running ReachView v2.9.1

When enabling or disabling position output the RTK solution is restarted.

Is it necessary to restart the RTK calculation? I regulating enable and disable comms to test my application. It would be nice if this did not trigger a restart of the RTK calculation.

Well, it’s always been that way for rover settings. For now, we don’t have an easy way to get over this.

Okay. That’s fine. Thanks for letting me know.

1 Like

This topic was automatically closed after 100 days. New replies are no longer allowed.