Update: WXScheduler 2.9.9 is available. The 2.9.9 installer is here. Here’s what has changed with 2.9.9: WXscheduler v2.9.9 updates: Several fixes related to missing automation delays that are required for properly updating Wires-X Settings. WXscheduler v2.9.8 updates: – Now restoring Wires-X app to the Desktop only when Wires-X is currently minimized and WXscheduler is about to perform automated Wires-X Settings updates. – If the Wires-X app was minimized at the start of automated Wires-X updates, then the Wires-X app will Read more…
Category: WiRES-X
In this post we discuss how the operation of WiRES-X can be customized through the use of the Windows Registry. Okay, here’s a bit of a WiRES-X secret. Many of the settings which cannot normally be changed, can be changed. These include the call sign, location, etc. In fact, it is possible to use an HRI-200 with one node number with a different node number. This is necessary should one be running a room and need to switch to a Read more…
If you want to set up an HRI-200 on Starlink, AT&T, or use you phone as a hotspot, there’s a problem. You need to open incoming ports and that can’t be done in many cases. The answer is to use a VPN to tunnel past your ISP to the raw Internet. One solution for some carriers is to use the PDN mode which does not require incoming ports to be open. But that may still not work. The other problem Read more…
This post addresses a WiRES-X node that constantly leaves and rejoins a room. This type of problem is almost always the result of a networking issue. When certain networking problem occur the HRI-200 software will wack out (a technical term). Once the software has been wacked out, it will continue to cycle in and out of whatever room it is connected to. Restarting the WiRES-X software usually solves the problem. Router problems: 1. Turn off UPnP. It should Read more…
Many people have reported Fusion repeater lock-ups that required the repeater to be shut down (power removed) and rebooted. I’ve had repeater lock happen as well with an HRI-200 directly connected to the DR2X. In this particular case I believe the event was triggered by sending a number of commands from the radio (such as the GM mode) which resulted in a race condition within the firmware. I have previously observed that invalid data (I.e., with a lot of bit Read more…
I use VyprVPN from GoldenFrog. It is necessary to turn of NAT for your account. That means that each VPN connection is a raw connection straight to the Internet. YOU HAVE NO PROTECTION OTHER THAN WHAT YOU PROVIDE!!! (The same company will rent you a VPN that you can host on your own cloud provider where you can control port forwarding – but I suspect this is well beyond most folks.) I’ve been using this solution for over a Read more…
What’s the difference between using an HRI-200 and directly connecting to the radio? 1. It is the only option for connecting a repeater to WiRES-X.2. It uses UDP communications sent directly to the Room. So network communications are very efficient.PDN uses TCP instead of UDP. (Why use UDP? UDP is simple. If anything gets lost, it is dropped. Good for real-time communications. If a packet is missed with TCP, it will keep retrying up to a limit which is not Read more…
When a WiRES-X node keeps going online then offline, this type of problem is almost always the result of a networking issue. A networking problem will occur and will wack out the HRI-200 software. Once the software has been wacked out, it will continue to cycle in and out of whatever room it is connected to. Restarting the WiRES-X software usually solves the problem. Router problems:1. Turn off UPnP. It should never be used!!!!!!2. Turn off all quality of service Read more…
If you’re having problems with USB problems when using WiRES-X with or without other programs, read on. The WiRES-X software is pretty good at identifying the HRI-200 vs. connecting directly to the radio. Windows, however, is very bad at managing USB ports. The WiRES-X software makes two USB connections: One as a virtual COM port and the other as a sound device. Windows is also very bad at managing sound devices. Virtual COM ports can be identified by the port Read more…
A problem exits with YSF/MMDVM hotspots bridging to WiRES-X rooms. Here’s what happens. A user has a hotspot and accesses it using a Fusion HT. They use the WiRES-X control mode to change the hotspot to different YSF Reflectors. Let’s say the user wants to access MNWis (Room #21,493): They enter the number of the YSF Reflector, “US MNWis 21493”, which is 37,624. The hotspot switches to US MNWis 21493 which is bridged to WiRES-X Room # 21,493. The user Read more…