Results 1 to 12 of 12

Hybrid View

Previous Post Previous Post   Next Post Next Post
  1. Member Wayne P.'s Avatar
    Join Date
    Jan 2010
    Location
    Charlottesville, VA
    Posts
    31,878
    #1
    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.
    Wayne Purdum
    Charlottesville, Va.
    Helix 12 MEGA SI+ G4N, Helix 15 MEGA SI+ GPS G4N
    SOLIX 12 SI/G3, Helix 8 MEGA SI+ G4N, Ultrex 80/Advanced, MEGA360,
    MEGA LIVE, LIVE TL, MEGA LIVE 2, Xplore 10

  2. Testing
  3. Member
    Join Date
    Dec 2010
    Location
    Hot Springs Village
    Posts
    4,369
    #2
    Quote Originally Posted by Wayne P. View Post
    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.
    2024 Skeeter ZXR20
    2024 Yamaha SHO 250