Yaesu’s closed network — why your hotspot can’t get in, and how people get in anyway.
Every other system documented on this site is open. XLX, URF, mrefd, YSF, FCS, DVSwitch, MMDVM — you can read the source, build the server, and stand up a reflector on a Raspberry Pi in an afternoon. Wires-X is not one of those systems. It is Yaesu’s proprietary internet linking network, it runs on Yaesu’s servers, and it requires Yaesu’s hardware.
So why cover it here at all? Because sooner or later you will hear someone on a Wires-X net say they are coming in on a hotspot — which, as you are about to see, should be impossible. Understanding what is actually happening on the other side of that link is worth the page.
WIRES stands for Wide-coverage Internet Repeater Enhancement System. A local node station connects to the internet and acts as an RF access point; users reach the node over the air, and the node carries their audio to the wider network. Yaesu built it around C4FM, so digital voice is repeated end-to-end without transcoding loss, and it also carries analog FM.
The system has two core objects, and the vocabulary matters:
To run a node you need one of the following: a Yaesu HRI-200 interface box connected to a PC and a Yaesu radio, or a compatible Yaesu radio running in PDN mode (Portable Digital Node) plugged into a PC by USB. The node software is Windows-only. Yaesu manages and operates the Wires-X servers that tie it all together.
The catch that defines everything else on this page: a radio in PDN mode cannot host a room. Only an HRI-200 node can open a room. PDN gets you in the door as a visitor, not as a landlord.
Before any of this works, there is a gate. A Wires-X node must be registered with Yaesu, and Yaesu issues the IDs. You fill out a member registration form, agree to the WIRES-X Server End-User License Agreement, and wait — registration typically takes two to three business days. When it completes, Yaesu emails you your Node ID and your Room ID.
Note what you are actually registering. The form asks for the HRI-200 serial number, or the RADIO ID of the transceiver serving as the node — a five-character alphanumeric string unique to that individual radio. You are not registering a call sign with a coordinating body, the way you would request a DMR ID from RadioID.net. You are registering a piece of Yaesu hardware that you bought, and Yaesu is granting your purchase permission to speak to its servers.
The license agreement is explicit about what that means. Yaesu assigns a server ID to the purchaser on application, and reserves the right to refuse access to the server if you fail to comply with the terms, modify the WIRES-X software or the HRI-200, use the software for purposes other than intended, or if Yaesu determines you are no longer eligible to use the system.
That clause is the whole story. Modifying the software is grounds for revocation. This is why nobody has written an open-source Wires-X client, and why the only bridge anyone has ever built into a Wires-X room is a radio transmitting across an air gap. The kludge you are about to see is not laziness — it is the only door that was left unlocked.
This is the single most misunderstood point in all of System Fusion, so it is worth stating plainly:
You cannot connect to a Wires-X room with a Pi-Star hotspot. Not with a ZUMspot, not with a JumboSpot, not with an OpenSpot. Hotspots connect to YSF and FCS reflectors. Those are different, independent networks that have nothing to do with Yaesu the company.
YSF, FCS, Wires-X, and IMRS are four separate networking systems. A station on one can only talk to stations on the same system — unless someone has deliberately bridged them. There are no YSF rooms, and there are no Wires-X reflectors. The words are not interchangeable.
Despite the acronym, YSF is not “Yaesu System Fusion” in any corporate sense. It is an open-source reflector network built by hams around the C4FM modulation, entirely independent of Yaesu. That naming collision is responsible for a great deal of confusion.
CQ-UK (Wires-X room 27793) is the work of two men. Stuart Priestley, M0SGS (SK), created the room in 2017 and built it into one of the busiest on the network. Ernie Pratt, GM7KBK, hosts it today and runs the infrastructure around it — the CQ-UK DMR server, the reflectors, and the help site at cq-uk.co.uk. Between them the room became a genuine multi-mode hub, where Fusion, DMR, D-STAR, and analog FM all meet.
Stuart has since become a Silent Key. The room he built is still running, still busy, and still the answer people give when a newcomer asks how to reach a Wires-X room from a hotspot. There are worse things to leave behind.
CQ-UK is also the best worked example of the problem this page is about, because getting a door open into it from the outside took real effort.
Here is the part that surprises people. The bridge between the open world and a Wires-X room is not software. There is no protocol to link into — Yaesu never published one. You cannot write a program that connects to a Wires-X room.
What you can do is walk in the back door: put a real Yaesu radio inside the room, and point a hotspot at that radio.
The room operator runs a Yaesu radio (an FTM-100D or similar) in PDN mode, sitting in the room like any other node. A Pi-Star hotspot is set up on the same frequency, connected to the room’s YSF reflector. The two talk to each other over the air — RF, not IP. Audio from the reflector comes out of the hotspot, goes into the Yaesu node radio, and into the room. Traffic in the room transmits out of the node radio, is heard by the hotspot, and goes back onto the reflector.
That is it. A Yaesu radio physically bolted onto the open network, held together with duct tape and stubbornness. The operator of CQ-UK sells the MMDVM board he uses for exactly this, describing it as a must-have for anyone wanting to link Wires-X directly to a YSF reflector.
It works, but nobody gets there on the first evening. The honest account, from operators who have built these bridges:
Remote Gateway=0 gives them YSF → Wires-X, and Remote Gateway=1 gives them Wires-X → YSF — but never both directions at once. Getting a clean full-duplex bridge takes patience.Both Wires-X and YSF use five-digit IDs — deliberately, so hotspot software can reuse the Wires-X control commands in Yaesu radios. But the numbers do not match.
| Network | America Link | CQ-UK |
|---|---|---|
| Wires-X room | 21080 | 27793 |
| YSF reflector | 89804 | 23501 |
| FCS reflector | FCS003-90 | FCS23535 |
Search Wires-X on your FT2D for “CQ-UK” and you may get several hits, while Yaesu’s official room list returns one. That is because your hotspot is showing you YSF reflectors, not Wires-X rooms. Same name, different network, different number.
This is the subtle one. Besides being a network, Wires-X is also the radio-to-gateway control protocol — the thing that lets you browse and select rooms from the face of your radio. The open-source YSF Gateway deliberately implements Yaesu’s Wires-X commands so your radio can list and pick reflectors.
Which means your Pi-Star hotspot speaks the Wires-X protocol to your FT-70 while connecting to a YSF reflector that has nothing to do with Yaesu’s Wires-X network. Two different meanings of one word, in the same QSO. Most of the confusion in System Fusion traces back to exactly this.
You cannot reach a Wires-X room with your hotspot. But if the room owner has gone to the trouble of building a bridge, you can reach it indirectly by connecting to the room’s YSF or FCS reflector. Most of the popular rooms have done this, and many have gone further — CQ-UK publishes doors from DMR, C4FM, YSF, FCS, NXDN, P25, and even Zello and Teamspeak.
Find the reflector, not the room. The reflector’s tethered Yaesu radio will carry you the rest of the way.