YAESU WiRES-X

So, VoIP + Radio always was a fascinating subject for me and continues to intrigue me and I keep asking what else can be done on this platform. YAESU have done a phenomenal job at bringing together the digital +analog world together into the internet world to enable radio enthusiasts like you and I to have long / short distance QSO, CQ through our base station, HT and through the internet to across the world. When I first heard about WiRES-X, I was a bit overwhelmed by the idea of implementing it in my shack as a “Node” (sysop) service. However, I must say, they have done a great job of simplifying the whole set up to absolutely bare bones. I was able to get my radio hooked up to WiRES-X and up and running in 1/2 hour. No kidding. The only step that took a day or two was waiting for my website registration to go thru – but, that is basically nothing.

YAESU has a product called, “HRI-200” a small footprint hardware device that drives a WiRES-X station. WiRES is an acronym for “Wide Coverage Internet Repeater Enhancement System”. More information can be found in their website. Simply put, I can communicate with someone sitting in Japan from right here in Minneapolis through my HT, that passes through my radio antenna to my radio, then into my WiRES-X device, through my PC and out through the internet; and finally reach the person I am trying to QSO in Japan. While this workflow might seem daunting and complicated; in reality, this is all handled seamlessly and simply by the YAESU HRI-200 WiRES-X platform. I will have a short video of this soon and will publish it here.

Hi,
I also try to establish communications via HRI-200 on my Yaesu FT857D and an analog Kenwood porto. I get connection with the Wires-X network ok, but everytime after abt 30-35 seconds I get an error message : “socket communication timeout” and I get disconnected. What could be wrong here?
Regards, Hans T. Hoekstra PD2HTJ

I too am having this issue…. “Error: Socket Communication Timeout.” happens consistantly… I can connect to the various ‘chat rooms’ but after 30 seconds or so, I get disconnected and this error pops up. Ideas??? Winxp, FTM-100, HRI-200.

Get a Raspberry PI and a DV4Mini and connect to a reflector via C4FM using something like a FT2D or FTM0400. This way you will not need Wires-X and no dedicated windows box. You can still use Digital C4FM without a wires-x.
Example: https://www.youtube.com/watch?v=dOCOOg7mnp4

Has anyone figured out what is causing the socket timeout issue? Just got mine and set it up. Having two issues:

1. Socket timeout after about 30-60 seconds of no activity in a room–when folks are talking it stays connected.
2. When I connect to a room everything seems to work audio wise (when folks are talking)—but it says that I’m “not in the room”

There are so many combinations to things that there may not be a single answer but wanted to share what worked. I went into Windows firewall, The Wires-X application didn’t have complete access so I checked both Public and Private networks…I also went into advanced settings and allowed any network traffic to get through in this app, not just TCP. I restarted the software and got into the rooms and was not disconnected….

Regarding the socket time out issue – I have them intermittently, maybe a couple of times a day. My HRI-200 is the latest firmware to date (4/15/2017) connected to my DR1X repeater (firmware 1.10Q), using the current / latest Wires-X application. The PC I am using is connected with an Ethernet connection to my firewall (Juniper SRX240), using my Comcast Internet connection to join. I figured out how to do port mapping over static NAT to get things working, since my commercial firewall doesn’t do destination NAT exactly the same way that consumer hardware is assumed to do by Yaesu. Because this is UDP communication, the sockets don’t have ‘reliable’ transport, and if a packet is lost or missed here or there, the higher layers of the OSI model are responsible for recovering from this. The socket timeout error is apparently the result of how Yaesu’s developers decided to deal with whatever it is that isn’t happening… It isn’t likely that Yaesu will have much of an answer for this, as there are too many variables in the path for UDP sockets in this application to isolate the problem. I’d be willing to set up some Wireshark captures to see if there’s a way to detect this, but wouldn’t even know where to start with contacting Yaesu on how / where to send those packet captures to trace this. Even then, there would be an equivalent, coordinated collection needed to be done in other places to determine whether or not this is simply a packet loss issue, or if there is some other software application components that have some defect in how they are processing data to / from the socket. The Internet is an interesting and wild place. UDP aren’t guaranteed to arrive in the sequence they were sent (or at all, for that matter), but it is still the best basic way to do streaming media (like voice on wires-X). To turn on and use some of the more robust streaming media protocols and leverage QoS is probably beyond the basics of understanding of most amateur radio personnel at current state. All that being said, I wonder how much compute resources the wires-X applications should require. I run a ‘server’ style computer mounted in the same rack as my repeater. It is an older, 1RU PC with the Intel Atom D525 processor and 4 GB of RAM running Windows 10 Home 64-bit from a 256 GB SSD drive. CPU across any of the four threads doesn’t seem to be significantly taxed by the Wires-X app…. Oh the mysteries of wires-X

What worked from me on the socket error message on my node software, was to go in to the fire wall setting in windows and make sure the wires software can pass through the firewall. My fault was I install the software more than one time . So both boxes where not checked in windows firewall settings. Checked both boxes and my socket error is gone. Running Windows7

I had socket error problem. To fix it make sure the HRI200 is the only device using your internet, dv4mini, dvap etc hang the ports and even if wires-x port checkek shows ok it can still hang. Once HRI200 is up and running then start dvaps etc and all should be ok.

I also started to have this same problem (socket error message) also and keeps getting disconnected,everything was running smooth and dandy and one day out of the blue i started to get disconnected and the socket error message started to pop up,so i will try the thinks that i read above and see what happens…..de kb5zcs……