Printable View
Occasionally my console units depth readout jumps way up; like from 16' to 42'. After 4 or 8 seconds it corrects itself. Everything else looks like it should. I have depth source set to 2D which is Y cabled to thru hull (high speed running).
1st Question Is it a good idea to use thru hull as depth source?
2nd What is causing depth readout jumps?
There are many reports across the forums dealing with HELIX MEGA and SOLIX erratic depth issues ...
While there has been no definitive fix found yet - there are several possible things to try ...
*Increase Surface Clutter to 7-8 ...
*Decrease 2d Sensitivity..
*Set Max Depth under the Sonar tab to just over water depth ...
*Turn Off 2d CHIRP to use fixed frequency 2d ...
I have heard whispers that HB may be working on a software fix ...
Rickie
Been having the same problem and have tried all the settings possible. Seams that the digital read out is the only thing wrong as the graft is right. Seams to happen when I get a second return on hard bottom and the digital reads the second return. I suspect that the adjustments don't help as I think the data for the digital read out and recordings for Auto Chart Live is used before the setting take effect. HB CS doesn't know how that works but they know they have a problem. Let's hope for a fix. Don
I get it when running split scrren SI and DI combined. Let everbody know if HB fixes it with a new update sometime I hope.
Yes, please do. I have the same problem. Talked to H'bird one day this week. They want me to send it in for repair.
Well let us know if that fixes anything. I have 3 of them on my boat and transducers on the trolling motor and another 2D on a mount on the bow, plus transducers in the transom and all networked. They all do it. Don
Thank you for your response. I posted here first because I knew you would have the lowdown. From what I have now read elsewhere ; HB BETTER get it fixed...Quote:
Originally Posted by rnvinc
just curious if this may be influenced by an offset--i.e. keel for tm application. Was clearly the problem on my old core unit when it started giving erroneous depth returns, then would correct. etc. Worked fine w/o an offset entered. Sent it in three times, finally they said I was unique in that they had never heard of the problem exc for me. That was not correct