3 TZT2 units, 2 RD33’s and 1 GP33 all tied together on the nmea2000 backbone.
When you select a go to waypoint on a TZT2 the range/bearing on other TZT2’s updates immediately and the RD33 a second later. If you select a new go to everything updates again. If you select a go to waypoint on the GP33 same results, updated range/bearing across the system.
Here is where it’s weird, if you go back to the TZT2 and select a waypoint after a GP33 waypoint the other TZT2’s update range/bearing but the RD33’s keep displaying the GP33 range/bearing.
Only way to correct this that I have found is to select stop navigating on the GP33 and then delete the waypoint on the GP33 - then the system goes back to rapid updates from the last selected waypoint.
So how do I work around having a GP33 waypoint and not having to delete that waypoint to navigate to a new waypoint using another machine/location??
When you select a go to waypoint on a TZT2 the range/bearing on other TZT2’s updates immediately and the RD33 a second later. If you select a new go to everything updates again. If you select a go to waypoint on the GP33 same results, updated range/bearing across the system.
Here is where it’s weird, if you go back to the TZT2 and select a waypoint after a GP33 waypoint the other TZT2’s update range/bearing but the RD33’s keep displaying the GP33 range/bearing.
Only way to correct this that I have found is to select stop navigating on the GP33 and then delete the waypoint on the GP33 - then the system goes back to rapid updates from the last selected waypoint.
So how do I work around having a GP33 waypoint and not having to delete that waypoint to navigate to a new waypoint using another machine/location??