Cuda 350 delayed depth reading
 

I fished MB yesterday and my Cuda 350 took about an hour before it started reading depth. It locked on with GPS and showed my speed right away.

When it wasn't reading, the depth just flashes 0.0 and it doesn't show the bottom.

I power cycled it a few times and thought I'd be going the day w/o it.

When it did start working though, it was marking bottom and fish like a champ.

Anyone else deal with this or know why? It has happened once before, but it was only for a few minutes.

Funny that you should post this.....today while fishing I was in 55' of water and I knew that I was about to hit a shelf and immediately go to 80'. As soon as I got close to the shelf my 350 showed 9' and bounced around between that and about 25'. I had no doubt that the area I was in was a minimum of 80', its impossible for this area to be 9'. I powered the unit down, turned it on and it still showed a depth that was not correct. I ended up leaving it on straight GPS for about 2-3minutes, when I switched back to the sonar mode it showed 82'. I have no clue what caused this to happened and its never happened before so I'm as stumped as you are.

I've had this happen with my Cuda as well, I wrote it off as interference with another yakers sonar who was near me, not sure though.

Was johnny ceviche around?

Lmao.

Recent issues with my Cuda 350 too.
I've had mine for about one year and used it almost every Saturday w/o problems. <O:pLast trip, 1.5 weeks ago, my sonar showed bizarre vertical lines, a secondary bottom and no fish responses. That went on for over 15 minutes despite numerous reboots and reconnects.<O:pI had been fishing near a friend with a new sonar, so I'm going with the interference theory. I'll do more research and if I learn anything I’ll post.<O:p

I see, it's a feature. They all just have a little personality.

No problems with my 350. But, my old Fish Easy used to that sometimes. I usually wasn't with anyone else either.

Yeah the transducer from another nearby yak/boat can screw up the signal on your fish finder for sure. jorge stop following roby around and you won't have that problem.

No other fishfinders were around most of that time.

I think the small craft advisory kept a lot of people home on Saturday. During the first hour, there was hardly anyone on the water and no one was fishing.

It was the first time I've had to knock on the door for bait at the barge.

Later in the day, around 11am, I saw a party boat with about 30 guys dropping lines near the bridge & sail bay. :D

Too much:cheers1::cheers1::cheers1::cheers1::cheers1:: cheers1::cheers1:




Will cause a "blurry" signal.



Leave the Hard stuff at home.:D

sounds like a connection problem guys, been through that 100 times with the HBs...you know what to do...:reel:

Hahahahaaaaa
 

What do you think it was? The telaprompter or the microwave throwing off the readings?

Did you look around for the "little gremlins"? They like to hang around boats and the electronics on board........hard to get rid of them,even bug spray won't work.

You speak the truth Tony....

I was at La Jolla once and some explained it to me like this.....it's possible your sonar is sending a signal and before it reaches your fishfinder it gets interference from the second signal being sent. This usually happens when you are in deep water. You were in MB so I don't think you were too deep, but that is my amateurish explanation and plus I wanted to give props to Ful-rac.

You have been officially "thread jacked."

I have this unit and had this same exact problem, come to find out my transducer was not properly mounted or over time it needed to be redone, It worked only some times like you described, I re-gooped it and have had no issues since.

Jut to clarify....here are two definitions

Follow: come after somebody or something: to come after somebody or something in position, time, or sequence


Lead: To show the way to by going in advance.


Correct me if I'm wrong but Roby is usual following and not leading;)