Depth Finder Problem

[Shakespeare]

I have a Garmin GPSMAP440S. Ocassionally, when running through heavy chop, the depthfinder gets "confused" and starts blinking the last known good depth. No problem with that in itself but the unit never recovers after I get back into stable water. I haven't had much time to fuss with it except to tinker with the transducer angle. The only way I've been able to recover from this "depth lockup" is to reboot the unit. That's a real PITA. *004*

Anybody else experience this and have you been able to resolve the issue?

[Dave]

I have a Garmin GPSMAP440S. Ocassionally, when running through heavy chop, the depthfinder gets "confused" and starts blinking the last known good depth. No problem with that in itself but the unit never recovers after I get back into stable water. I haven't had much time to fuss with it except to tinker with the transducer angle. The only way I've been able to recover from this "depth lockup" is to reboot the unit. That's a real PITA. *004*

Anybody else experience this and have you been able to resolve the issue?

I can't help you with the Garmin, but my Hum transducer reading often goes bonkers when I back down on a spot to settle the skiff over offshore structure... takes a while to get itself right again, even after moving forward for a period of time. I've tried several things to try and figure out what the cause of this is but have yet to solve the anomaly. Rebooting the unit doesn't even resolve the problem for me and I'm on my second transducer and both do the same thing. Fortunately, it typically only lasts several seconds or a very few minutes.

Only thing I can think of that you might try is to look for a software update, and/or try and reinstall the most current software version.

Dave

[workinprogress]

I have a Garmin 545s, and I also have problems with it losing depth in a chop or at higher speeds. My unit doesn't immediately pick back up when I slow down or hit smoother water, but it has never required rebooting to regain the depth reading. There is some lag time, usually between 15 and 30 seconds, before it begins to register depth after I hit conditions at which it would normally register with no problems.

[Harry]

540s same thing here, but only once in a great while

[Insideout]

545s Same issue. I am going to try setting it deeper. I think the hull design tends to channel air right to it. I will be doing some research.
My $150.00 Humming bird never had this problem even at 40 mph.

[Tparkin]

I've noticed that on my GPSmap498, if I have it on the sonar page I can hit the up range button, scroll to auto, hit enter and it will normally pick back up in seconds. If I just let it sit it may take a while for it to "catch back up." Mine won't read at speeds over 20mph...I assume it's due to the turbulance at the transducer on a flatbottom boat.

[LittleJerry]

Hey Shakes,
I have the Garmin GPSMAP440S also, like everyone else at high speeds it does go (Mom the cable is OUT!) But like Harry as soon as I I get down to lower speeds it comes back. Rarely every needed a reboot. I would contact the GPS Store down in Ocean Isle. They are really helpful.

http://www.thegpsstore.com/

[Redfish]

My Garmin 498 is a PITA too. I don't know if it's the unit or, like everyone says, just the flat-bottom boat. I've had the boat over a year and I still keep trying to tweak it to get it to read in a chop. It will read at WOT, but get a little chop and it goes haywire. Sometimes it takes a bit to find the bottom even after I let the boat come to a complete rest. There has been a time or two when I had to reboot, but most of the time it will right itself once all the air quits bubbling up.

[seacrets]

I have a 250 and at more shallow depths when I'm running hard, I have to slow down just to get a good depth reading. They make outstanding GPS products, however in my opinion, their depth finders could be better

[NOTHING ELSE MATTERS]

Looks like the problem is the transducer and not the head unit. Try to angle a little more, but most importand lower the ducer so the bottom of it is at least 1/4" to 3/8" below the bottom. Mine(Raymarine) said in the instructions to set it 1/8" below and i did it at 3/8" and have no problem.
On another note, i took the Grady out today for a bay test to check all out and i did the airbone thingie(whole boat out of the water) and my Garmin GPS registered a speed of 228 miles per hour :eek:, as soos as i landed the display was showing still 228 miles i tried quickly take a pic with my iphone but it was gone(the 228) and changed to my normal speed *006*

[gi joe]

Same here, I have the 540S, and it gives erroneous readings from time to time. Usually fixes itself after several seconds, but last time out, it took a couple of minutes. I wish I had my Furuno back:eek:

[Shakespeare]

Guys... I appreciate all the advice. Good feedback! *Cheers*

I've also Googled my problem and scoured the Internet a little to find out that this anomaly happens from time to time to various Garmin owners. The suggested causes have ranged from corroded pins on the connectors, too much gain on the transducer, improper angle on the transducer, and so on.

The latest firmware update was March '09. I've never updated the firmware so that's probably a good thing to do regardless. I'll have to pick up the SD card, pc iinterface and all that to make that happen. In the interum, I'll go through all the mounting and cables to see if there's a small bug in that. If I manage to straighten it out, I'll post up.

Thanks!