Question with the 14 M360 2DDI Y

[woppercatcher]

I have two Helix 12 G4 MDI+ units at the bow along with Mega Live, Mega 360 and Target Lock. On one Helix I only have an Ethernet cable and power which runs my Mega Live and I subscribe to the other Helix for 2D sonar. On the other Helix I have the Y cable with my Ultrex Quest built in duel spectrum transducer and Mega 360 connected. For some reason I get interference and or cross talk on both the 2D and Mega 360. I didn't get this with my old Ultrex which had the built in MDI+ transducer.

I'm not sure why but when I only turn on the Helix with the Mega Live there is a sonar tab and it still shows the MDI+ transducer even though there is no actual transducer connected and I've reset to factory defaults twice. When I power up both units, on the Helix I use Mega 360 and map I go to the sonar tab and I select HW: MEGA 360 as the connected transducer. On the Helix I run the Mega Live I subscribe to the 2D on the Mega 360 Helix. Before yesterday I was selecting the HW: MEGA 360 on this unit as well.

Another weird thing is on both of these units the MDI+ transducer is still there even though it doesn't exist.

So, I'm not sure at this point what to do to hopefully clean up the interference/cross talk. On the Mega Live Helix with not connected transducer should I select as the connected transducer the default High Wide which I believe is the Ultrex/Quest default and on the Mega 360 Helix use the HW: MEGA 360?

Note, I tried to split these up and run the 2D on the Mega Live Helix and Mega 360 on the other Helix but then I get the pulse rings from the Mega 360 on my Mega Live. Again, I didn't have this issue with my old Ultrex and before the latest updates which Humminbird replaced my Mega Live transducer for.

Thanks

[Wayne P.]

Helix units do not detect a transducer unless it is the MEGA 360. When the M360 is detected, all the Connected Transducer choices are deleted and another set is added that involve the M360, you select what you have connected (default is the M360 alone). Whatever is shown in the Connected Transducer menu is either the unit default setting or what you selected. If you don't have a transducer connected to the unit's transducer port, it makes no difference what the setting is, there is no source for 2D/DI/SI/Temp unless it is from a networked source and that selection is done in the Network Source menu.

If you don't have a transducer of any type connected to a unit's transducer port, Sonar should be turned OFF on that unit. It can get sonar data from another source when done that way including MEGA LIVE.

MEGA 360 and a MDI or a MSI transducer (Humminbird or Minnkota) should be connected to the same unit via the Y cable so the sonar piezos are pinged in a sequence (eliminates cross-talk between M360 and DI).
Then with a MEGA LIVE also networked, the Interference Rejection setting/function fixes cross-talk between M360/DI and MLIVE.

[woppercatcher]

Helix units do not detect a transducer unless it is the MEGA 360. When the M360 is detected, all the Connected Transducer choices are deleted and another set is added that involve the M360, you select what you have connected (default is the M360 alone). Whatever is shown in the Connected Transducer menu is either the unit default setting or what you selected. If you don't have a transducer connected to the unit's transducer port, it makes no difference what the setting is, there is no source for 2D/DI/SI/Temp unless it is from a networked source and that selection is done in the Network Source menu.

If you don't have a transducer of any type connected to a unit's transducer port, Sonar should be turned OFF on that unit. It can get sonar data from another source when done that way including MEGA LIVE.

MEGA 360 and a MDI or a MSI transducer (Humminbird or Minnkota) should be connected to the same unit via the Y cable so the sonar piezos are pinged in a sequence (eliminates cross-talk between M360 and DI).
Then with a MEGA LIVE also networked, the Interference Rejection setting/function fixes cross-talk between M360/DI and MLIVE.

-
Thanks Wayne! I'm not getting any interference on my Mega Live or 360 interference/cross talk/pulses. My Ultrex Quest only has the duel spectrum 2D transducer which I have connected to my Y cable along with my Mega 360 so are you saying this combination won't work? On that Helix I have a list of transducers including MDI+ Built in MDI+ Mega 360 HW: Mega 360 and others. I chose the HW: MEGA 360 on that unit. On my Helix where I don't have a transducer connected I subscribe to the 2D on the unit with the Y cable and there is a list of connected transducers you can select which I don't believe I had before or to be honest didn't pay attention too. Do I select a transducer on that unit and if so which one? I seem to get the interference when I press the trolling motor button on both the Mega 360 and 2D sometimes worse than others. Another weird thing is when in say 15-20 feet of water everything seems fine but when I get deeper the interference gets worse and the Mega 360 is almost useless.

[Wayne P.]

Yes it should work, the setting using the Y cable for MEGA 360 and HW transducer is HW:MEGA 360==that is the second choice in the Connected Transducer menu after the MEGA 360 is detected.Have not checked to see if another choice has been added recently for Built-in HW:MEGA 360.

You cannot select a transducer in the Network Source menu, only the UNIT that has that function.
If you want 2D sonar from another networked unit, you select which UNIT is listed in the 2D column of the unit menu you are looking at.

As stated above, it makes no difference what you select in the Connected Transducer menu if no transducer is connected to the transducer port. Sonar should be OFF with no transducer connected.

This is three units networked and all three are listed as a source for 2D sonar in all three unit's Network Source menu. You select which unit you want that data from in each unit's menu.

[Wayne P.]

I've been discussing cross-talk (interference), did not read that close enough.
Are you getting RFI (interference) from a Quest motor?==not supposed to happen.

[woppercatcher]

I've been discussing cross-talk (interference), did not read that close enough.
Are you getting RFI (interference) from a Quest motor?==not supposed to happen.

I can't say for sure if this is RFI or not. When I press the trolling motor button to engage the prop it happens but not as bad on spot lock. I've tried every number on the noise filter and only number 1 seems to work. The Mega Live works fine. I'll take some pictures and post them.

Thanks

[woppercatcher]

Here are two pics. One working fine in shallow water the other deeper. B9B7A7C2-467E-4948-AB5A-E2911DA9EDA4.jpeg3D493407-7482-4AE3-A1B1-C6F2233DE5CB.jpeg

[SLYDoggie]

I can't say for sure if this is RFI or not. When I press the trolling motor button to engage the prop it happens but not as bad on spot lock. I've tried every number on the noise filter and only number 1 seems to work. The Mega Live works fine. I'll take some pictures and post them.

Thanks

This is definitely interesting. This definitely sounds like trolling motor RFI, but it could be coming from the Pulse Modulation that Minn Kota uses for speed control. If the RFI goes away when the trolling motor is at 100%, then it is probably the Pulse Modulation that is causing the RFI and not the motor itself.

Please try the 100% speed test to see if the RFI goes away and let us know.

[woppercatcher]

This is definitely interesting. This definitely sounds like trolling motor RFI, but it could be coming from the Pulse Modulation that Minn Kota uses for speed control. If the RFI goes away when the trolling motor is at 100%, then it is probably the Pulse Modulation that is causing the RFI and not the motor itself.

Please try the 100% speed test to see if the RFI goes away and let us know.

-
Actually, when I use 100% I get interference on my Mega Live for sure. On spot lock this interference happens but not as bad. It usually happens when the actual trolling motor is steering. On a side note, when I first installed the Quest I removed the Y cable and connected the built in 2D Quest transducer to my Mega Live unit and the Mega 360 to my other unit. No cross talk or interference on those two units but with the default 2D transducer selected I got horrible cross talk on my console 2D unless I selected a different transducer. I also started getting the pulse rings from my Mega 360 again on my Mega Live so that is why I went back to the Y cable.
-
I guess I could not use the 2D and just connect my Mega 360 but I like the 2D next to my Mega Live and I'm afraid I will start getting those frigging pulse rings on Mega Live again. It's so frustrating because before the last update and trolling motor change everything worked perfect. Now I have my Mega Live finally working again but my Mega 360 and 2D are not.

[Wayne P.]

Couple of things to try:

1. Set the Connected Transducer choice to MEGA 360 so HW is not pinging to see it that has any effect.

2. Set the 2D Switchfire to Max Mode so it doesn't change the Sensitivity setting automatically when the depth changes.

[woppercatcher]

Couple of things to try:

1. Set the Connected Transducer choice to MEGA 360 so HW is not pinging to see it that has any effect.

2. Set the 2D Switchfire to Max Mode so it doesn't change the Sensitivity setting automatically when the depth changes.

Thanks. I'll try both of those things

[Wayne P.]

Another thing to check is the fuse in the top of the motor if a Quest has one.