Something we may need to discuss ... if it hasn’t already been brought up ...

Quote:

---

Originally Posted by JohnN

Steve, I'm wondering if you ever got the DI working again while the HW transducer was installed? My DI stopped as well, presumably as a result of the update. I am stuck with the new HW transducer because it's a thru-hull model, and the old one was destroyed during its removal (the HB epoxy is serious stuff).

---

Hi John. I missed your question and just came across this when Wayne bumped this thread again. My apologies.

I never did get the DI working with the HW transducer installed (and various settings adjusted for it). Between the DI not working, and the SI/DI frequencies not maintaining their setting adjustments when the unit is power-cycled, I gave up playing with this process. I switched back to the older high speed transducer and left the selected transducer and settings stock. I was notified that there is a new update available, so I may play with this stuff again.

Hope things worked out for you...

Back to the top

My setup is a Helix 12 G2N at the console, a Helix 9 G2N at the bow, and a Helix 12 G3N at the bow connected to a MEGA 360, all networked. I upgraded to the HW transducer on my console G2N unit earlier this year. After upgrading, I was experiencing two issues on my console G2N. First, my DI stopped working - just a black screen. Second, when my 360 transducer was out of the water my console G2N would constantly interrupt me to say that the 360 was disconnected. When I confirmed that it should turn off the transducer it wouldn't stop the alerts. Those alerts would also switch the unit away from my side imaging screen for some reason. I had to manually connect and disconnect the 360 transducer via the network source menu to stop the alerts.

Great news: I updated my console G2N to 2.280. This solved both problems described above. It also seemed to improve the resolution on my side imaging, which was slightly degraded in my opinion by the previous update. I can confirm also that the connected transducer setting (for the HW) remains intact in the shut down/power up cycle (I never had an issue with it, but saw others who said they did). I was regretting the HW transducer a bit, but now I'm a happy fisherman.

Back to the top

Back to the top

Back to the top

Back to the top

Back to the top----

Back to the top

Wayne,

THANKS!!!! I had not seen this before. Just read the whole thing. This should maybe be a sticky?

Quote:

---

Originally Posted by Wayne P.

Back to the top

---

Good morning. I've finally had a chance to get back to the boat stored in the garage. I had removed the HW transducer during last year's fishing season because of the problem with the down imaging. It's good to see that the 2.28 firmware has dealt with that. The start and end DI frequencies for the Built In HW: MSI+ transducer for the 2.28 firmware has been reduced from what it was in the 2.18 firmware (455 khz 420/520 down from the previous 435/535).

The selected transducer choice does remain after a reboot, as it always did, but I'm finding that the new firmware still does not retain the frequency changes that are done in the Settings menu. Any DI / SI frequency changes that are made to match the default transducer settings are not retained after a reboot, and return to the stock values provided by the HW: MSI+ selected transducer.

It's nice to see that they have resolved the down imaging issue with the update. I'll give it a go again for this year.

Back to the top

TTT

TTT

TTT

ttt

ttt

Back to the top

I just bought a helix 10 si g2n and the transducer was not working right on the right side. I got a new transducer that is HW and now I don't have down image. From reading the post I am not sure if I need a new Y cable or need to do a software update. Currently running 2.180 and the y cable I ran with the old transducer. Thanks for the help

Quote:

---

Originally Posted by Todd axtell

I just bought a helix 10 si g2n and the transducer was not working right on the right side. I got a new transducer that is HW and now I don't have down image. From reading the post I am not sure if I need a new Y cable or need to do a software update. Currently running 2.180 and the y cable I ran with the old transducer. Thanks for the help

---

How many pins are in the Y cable plug that connects to the display?

Do you know how to properly use a HW CHIRP MEGA SI+ transducer with your unit?

I have 6 pins on the Y cable. Set the menu to built in HW. That's about it as far as knowledge

6 pins is the current SIDB Y cable.

To use a SI transducer and HW 2D transducer you need a Connected Transducer setting of Built-in HW+MSI

If you choose Built-in HW, you don't get SI or DI, only 2D.

yes it is set for built in Hw msi. My SI image is great but no down image. Using a xp 9 20 t for a shoot thru if that makes a difference?

Quote:

---

Originally Posted by Todd axtell

yes it is set for built in Hw msi. My SI image is great but no down image. Using a xp 9 20 t for a shoot thru if that makes a difference?

---

The XP 9 20 is a 83/200 kHz transducer and is not HW CHIRP so you have no need to select any Connected Transducer involving HW.

If you don't have DI, you may have a faulty Y cable, faulty DI piezo in the SI transducer, or a faulty display.

Do a Restore Defaults and check.
Then on the water, remove the Y cable and only connect the SI transducer to the display to see if you get DI.

Thanks Wayne!! I will unhook the y cable and give that a try. Down image worked with the old transducer so I am thinking it is a bad transducer.

... Just in case anyone missed this

ttt

ttt

ttt

ttt

Thanks Wayne. You are awesome. Just read this entire stream and you rock!! You help a lot of us, wish you were my dad! BTW my shit is working great!

ttt

ttt

ttt

ttt

Wayne, this seems to be a thread that you want to keep active. As the moderator, I can change the title of the thread to something more indicative of what the thread is really discussing. The current title doesn't indicate at all what the thread discusses.

If you think this is a good idea, let me know what you think it should be renamed to.

Quote:

---

Originally Posted by SLYDoggie

Wayne, this seems to be a thread that you want to keep active. As the moderator, I can change the title of the thread to something more indicative of what the thread is really discussing. The current title doesn't indicate at all what the thread discusses.

If you think this is a good idea, let me know what you think it should be renamed to.

---

The subject matter comes up occasionally just like the post by fatswarcat yesterday and that thread covers frequencies when using a non-standard transducer. It would help to be in a sticky topic so those that know about can reference it without doing an extensive topic search if it is not continually being "to the top" (aka ttt) to make it easier to find.

I am used to searching for it with the "something" title by rnvinc, but maybe a post title of Frequency Settings To Match a Transducer.

I also think it would be a good idea for the title to be changed to something more relevant to a search input someone might enter ... and then stickied ...

Rickie