I've been on here complaining in the past about my shoot through high speed transducer in the bilge not reading consistently. Wayne and others have consulted me plenty about this. Basically I lose depth (and therefore ranging on sonar and DI) at my console units frequently. I have 2 Helix 10s Gen 1 at console. One of them is a SI unit which receives the info from the transom HDSI transducer and high speed shoot through in bilge. Sometimes it works and sometimes it doesn't display depth/range. Sometimes it shares depth correctly to the unit immediately beside it. However, this is rarely. I tolerate it not sharing the depth to the one beside it because I only use other unit for mapping. Well I just got back from a five day trip to Lake Barkley/Ky Lake. For the FIRST TIME EVER the SI unit correctly gave the depth ALL THE TIME. Not a single time was I required to restart to have it start giving me the correct depth again. I spend the vast majority of my time a Lake Cumberland which is a much deeper lake. The deepest water I was in last week at Barkley may have been 45 feet in the main channel.
I've had this boat 2 years and it's never been right. I'm too chicken to try busting the shoot through out of bilge fiberglass because I'm scared I'll make something worse. And I've never been 100% convinced the shoot through is the issue in the first place (I replaced Y cable and that didn't fix it btw). Last week I was getting proper depth reading at all speeds all the time. Still not sharing correctly to the unit beside it, but working on the unit I use for 2D, Di, and SI.
Why did it always work at Barkley? Was it because it's a shallower place?
I'll set my Max Depth to 100 feet but it still will go to 1.9 and stay there many times a day. I suppose I could set it shallower than that considering I never really need to know anything that deep. But the depth and ranging working nonstop was just wonderful and I'd love for it to always be that way. I'll bet you $100 when I go to deep Cumberland this weekend it will go back to doing that same ch?t.
Any comments or suggestions?