ad: ProAudio-1

FTM-100DR problem getting into WIRES-X mode

Discussion in 'Digital Radio, DMR, Fusion, Wires, DSTAR' started by N4RL, Jun 19, 2018.

ad: L-HROutlet
ad: l-rl
ad: L-Geochron
ad: L-MFJ
ad: Left-3
ad: HRDLLC-2
ad: abrind-2
ad: Left-2
ad: MessiPaoloni-1
  1. N4RL

    N4RL Ham Member QRZ Page

    I recently got a FTM-100DR. I have the CT-174 MiniDIN cable connected to both the radio and to an HRI-200. The HRI-200 is also connected to my PC running Windows 10 with WIRES-X.

    I have used the radio to exchange APRS data and to talk on a few repeaters, but have not been able to get it to work as a WIRES-X node. Please help me to troubleshoot this problem as I have exhausted the possibilities I could come up with.

    Steps to reproduce the problem:
    With the radio powered on and connected to an antenna...
    and with the radio connected to a powered HRI-200...
    hold down the Dx, GM, and Power buttons until the radio power cycles.

    The radio powers back up and displays the Yaesu WIRES-X splash screen.
    The radio does not make any sound and remains on the splash screen until the sequence above is repeated (which powers the radio on in its standard operating mode).
    While the splash screen is displayed the DISP/Setup button can be pressed to hide and reveal the splash screen, but no other buttons have any visible affect.

    I expect the radio to make three beeps and then move beyond the splash screen to show the status of the WIRES-X node. I have never seen this happen on my radio, but have seen it in YouTube videos.

    Is it possible that I have a bad radio? A bad HRI-200? A bad CT-174 cable?
    Am I doing something in the wrong sequence? Do I need to connect the HRI-200 after the radio is put in WIRES-X mode?
  2. AI6AK

    AI6AK Premium Subscriber QRZ Page

    The radio needs to be powered off then power it back on holding the colored Dx and GM keys. Each time you do this cycles the radio as normal or as a node radio. Once the radio goes into WIRE-X mode start the WIRES-X program to recognize the radio. Also, make sure the cable is attached to "radio 1" of the HRI-200. I also use a FTM-100 as my node radio so your problem. is probably something really simple such as a sequence issue. Give it a try and report back.
  3. N4RL

    N4RL Ham Member QRZ Page

    Thanks for the response.

    The behavior I am seeing is that the radio never goes into WIRES-X mode. After powering it back on holding the colored Dx and GM keys, I expect the radio to make three beeps and then move beyond the splash screen to show the status of the WIRES-X node. I have never seen this happen on my radio.
  4. AI6AK

    AI6AK Premium Subscriber QRZ Page

    You said you use APRS so make sure the APRS modem is turned off before starting WIRES-X. Also, when the radio display changes from "WIRES-X" to showing the node info (Freq/HRI-200/WIRES-X displayed) it will make 5 consecutive beeps from low to high. Sounds like the radio isn't recognizing the WIRES-X program. Try rebooting the computer, turn the radio on in WIRES-X mode then restart the WIRES-X program.
    Last edited: Jun 19, 2018
  5. N4RL

    N4RL Ham Member QRZ Page

    I have verified that the APRS modem is set to OFF. I have tried every possible sequence combination of turning the radio on - starting wires-x - and rebooting. The radio remains on the WIRES-X splash screen and there is a message in the bottom left corner of the application "Transceiver Not Connect." This condition is true if I remove the CT-174 MiniDIN cable. I suspect the problem is either with the cable or the radio. I think the HRI-200 is working because I can see a log entry in the application like this:

    2018/06/21 07:37:40 Error: HRI-200 Communication device Not found.
    2018/06/21 07:37:40 Transceiver Mode: Digital/Digital
    2018/06/21 07:37:41 Number of sound devices = 5
    2018/06/21 07:37:41 Set Voice Mixer Device : Input=4 Output=0
    2018/06/21 07:37:41 Mixer input device=Microphone (2- HRI-200 A(CH1) USB Audio codec
    2018/06/21 07:37:41 Mixer output device=Speakers (2- HRI-200 A(CH1) USB Audio codec )
    2018/06/21 07:37:41 HRI-200 Audio device detected.
  6. W4ZXE

    W4ZXE Ham Member QRZ Page

    I also have the exact same issue and believe its the 10 pin cable or there is no output from Wires-X box on Rev firmware to the the radio.
  7. ZL1LAP

    ZL1LAP Ham Member QRZ Page

    I have the same problem transceiver not connect.Ihave downloaded all the Yaesu firmware again and the drivers as well. Restarted the Toshiba laptop but still no success..I will continue to watch this forum for hopefully an answer to my problem
    W8SPB and W8FFG like this.
  8. KL7ET

    KL7ET Ham Member QRZ Page

    Gentlemen, I was trying to use my FTM-100 as a PDN and was pulling my hair out trying to figure out how to get the node to function. Come to find out, putting the radio in PDN mode is not enough, as, once connecting the radio to the PC running Wires-X, you must long press the Wires-X, "X", button on the radio to sync to the Wires-X software. If the connection is broken via power outage of the laptop, or radio, then you must re-establish the connection between the software and the radio with another long press of the Wires-X, "X", button on the radio. Kinda Mickey Mouse, I know, but that's the way Yaesu decided to do it. I am not sure if this helps those with a HRI-200 or not, but it might.

    Personally I wish Yaesu would do two things:

    1) Make the Wires-X software run as a Windows Service, rather than an application, so that it would run once the PC is booted without a user logging into the PC. Make the services GUI available via typical agnostic web browser so that you can either use the GUI as a local user on the PC or remotely via another PC's browser.

    2) Make the PDN mode of the radio autonomously connect to the Wires-X software, rather than require a manual instigation.

    You see, you can either walk straight through a barn door, or you can walk all the way around the barn first before entering through the barn door. I prefer the first, more efficient, option.
    Last edited: Feb 27, 2020
  9. KA1MXL

    KA1MXL XML Subscriber QRZ Page

    Any luck ? I am having the same issue out of the blue.
    W8FFG likes this.
  10. W4EAE

    W4EAE XML Subscriber QRZ Page

    WIRES-X as a Windows Service would be step in the right direction, but offering a linux option would be even more practical. I don't know anyone who really wants a Windows computer at a repeater site. They require too much attention.

    I also wouldn't expect Yaesu to make any serious improvements on WIRES-X. They have already moved on to IMRS. All of their recent updates to repeaters and radios have gone in that direction.
    KL7ET likes this.

Share This Page

ad: Momobeam-1