stratboogie
Member
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!
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!
