Few issues with new XL system

[stratboogie]

Overall, very pleased with the system but I did have a few issues that I would like to get addressed:

1. Past 300 feet or so the PBG kept throwing a PBG missing multi beam depth data. Is there a depth limitation on this? The 3d was working fine.
I turned off one unit to try and reset the 3d/PBG issue and that caused some other issues such as position data and I had an error for the rest of the day of "position jumped". What would cause that and how do I clear the error without rebooting the whole system?
I have a DFF-UHD, b175HW and a b175M. Each of the XL's has a 175 connected to it. I noticed that the unit that had the HW hooked to it put the sounder into standby mode (along with the side scan) itself. When I turned it back out of standby mode it would not lock on bottom. I had to again reboot the machine. Any reason why this would happen?
When I boot my machine(s) on , the 3d is not in standby mode. How can I assure all of the ducers are in standby mode when booting? I dont want to burn up a ducer by accident.

Thanks!

 

[Sparky Wire]

DFF3D normal operations depths are 30ft to about 1000ft depending on the installation. Speed does matter and so does turbulence and noise. GPS Jumping is related to something with your GPS source and many things like placing your GPS near Starlink or in your radar beam can cause issues like that. You shouldn't need to ever reboot. Under the data sources menu you should check what the current and preferred source is and see which device is dropping out or giving GPS jumps. The DFF3D should be put in stby mode when not in use by the operator. It doesn't go to Stby by itself automatically. The newer internal sounders for XL just now added a feature to go to STBY when the unit is turned off but any external sounders would require you continue to manage the transmission ON/OFF manually as needed.