migs
Active member
I sent this to both Simrad and Airmar Support but neither replied to my question.
I recently replaced a faulty Airmar DST800, but now find that I am unable to enter a depth offset into the transducer from our Simrad AP28 panel (as I used to be able to do with the old DST800).
If I select a depth offset value on the AP28, the offset resets to zero after about 5s and the offset is not entered.
I can enter an offset on our B&G Triton displays, but the offset is only held locally in the display rather than being sent to the transducer so the depth shown on our OpenCPN plotter is incorrect.
Please advise how I can enter a depth offset into our new DST800.
The supplier of the DST800 did try to help with the problem but couldn’t come up with a solution. Does the forum have any suggestions?
PS. I appreciate that the DST800 is an obsolete product and that perhaps buying a DST810 transducer might have been better (offsets entered via Bluetooth?). However, replacing the faulty DST800 with the same product should have been a straightforward like-for-like swap, so I wasn’t expecting any problems…
I recently replaced a faulty Airmar DST800, but now find that I am unable to enter a depth offset into the transducer from our Simrad AP28 panel (as I used to be able to do with the old DST800).
If I select a depth offset value on the AP28, the offset resets to zero after about 5s and the offset is not entered.
I can enter an offset on our B&G Triton displays, but the offset is only held locally in the display rather than being sent to the transducer so the depth shown on our OpenCPN plotter is incorrect.
Please advise how I can enter a depth offset into our new DST800.
The supplier of the DST800 did try to help with the problem but couldn’t come up with a solution. Does the forum have any suggestions?
PS. I appreciate that the DST800 is an obsolete product and that perhaps buying a DST810 transducer might have been better (offsets entered via Bluetooth?). However, replacing the faulty DST800 with the same product should have been a straightforward like-for-like swap, so I wasn’t expecting any problems…