Wiki source code of Решение проблем
Last modified by UT2UK on 2026/11/16 15:04
Show last authors
| author | version | line-number | content |
|---|---|---|---|
| 1 | {{velocity}} | ||
| 2 | $xwiki.ssx.use("Main.DocStyle")$xwiki.jsx.use("Main.DocStyle") | ||
| 3 | {{/velocity}} | ||
| 4 | |||
| 5 | (% class="eax" %) | ||
| 6 | ((( | ||
| 7 | (% class="eax-back" %) | ||
| 8 | [[← EAX control user guide>>Main.ERMAK-TT.Руководство пользователя EAX control.WebHome]] | ||
| 9 | |||
| 10 | (% class="eax-pagehead" %) | ||
| 11 | ((( | ||
| 12 | (% class="eax-pagehead-title" %) | ||
| 13 | Troubleshooting | ||
| 14 | |||
| 15 | (% class="eax-pagehead-text" %) | ||
| 16 | Find what you see and open the fix. Also here: the router, choosing the IP address and operating from a remote QTH. | ||
| 17 | ))) | ||
| 18 | |||
| 19 | == Find the fix in 2 questions == | ||
| 20 | |||
| 21 | (% class="eax-wizard" %) | ||
| 22 | ((( | ||
| 23 | (% class="eax-wq" id="wq1" %) | ||
| 24 | ((( | ||
| 25 | What does EAX show after you click the connect button? | ||
| 26 | |||
| 27 | * [[“Unable connect to remote Rig”>>||anchor="noconnect"]] | ||
| 28 | * [[Speed is 0 or “Lost connection with Rig”>>||anchor="nosound"]] | ||
| 29 | * [[Speed is there, but the audio drops out>>||anchor="choppy"]] | ||
| 30 | * [[“Unable to configure audio card”>>||anchor="audiocard"]] | ||
| 31 | * [[Everything works in EAX>>||anchor="wq2"]] | ||
| 32 | ))) | ||
| 33 | |||
| 34 | (% class="eax-wq" id="wq2" %) | ||
| 35 | ((( | ||
| 36 | EAX is fine. What about the digital mode program? | ||
| 37 | |||
| 38 | * [[JTDX sees no signal or the transceiver does not transmit>>||anchor="digital"]] | ||
| 39 | * [[I operate away from home, from a remote QTH>>||anchor="remote"]] | ||
| 40 | ))) | ||
| 41 | ))) | ||
| 42 | |||
| 43 | == What do you see? == | ||
| 44 | |||
| 45 | (% class="eax-symptoms" %) | ||
| 46 | ((( | ||
| 47 | (% class="eax-symptom" %) | ||
| 48 | ((( | ||
| 49 | [[EAX does not connect>>||anchor="noconnect"]] | ||
| 50 | |||
| 51 | The message “Unable connect to remote Rig”. | ||
| 52 | ))) | ||
| 53 | |||
| 54 | (% class="eax-symptom" %) | ||
| 55 | ((( | ||
| 56 | [[Connected, but no audio>>||anchor="nosound"]] | ||
| 57 | |||
| 58 | Speed is 0. A few seconds later — “Lost connection with Rig”. | ||
| 59 | ))) | ||
| 60 | |||
| 61 | (% class="eax-symptom" %) | ||
| 62 | ((( | ||
| 63 | [[The audio drops out>>||anchor="choppy"]] | ||
| 64 | |||
| 65 | Clicks, gurgling, gaps. | ||
| 66 | ))) | ||
| 67 | |||
| 68 | (% class="eax-symptom" %) | ||
| 69 | ((( | ||
| 70 | [[JTDX sees no signal or the transceiver does not transmit>>||anchor="digital"]] | ||
| 71 | |||
| 72 | Everything works in EAX, but not in the digital mode program. | ||
| 73 | ))) | ||
| 74 | |||
| 75 | (% class="eax-symptom" %) | ||
| 76 | ((( | ||
| 77 | [[Sound card error>>||anchor="audiocard"]] | ||
| 78 | |||
| 79 | The message “Unable to configure audio card”. | ||
| 80 | ))) | ||
| 81 | |||
| 82 | (% class="eax-symptom" %) | ||
| 83 | ((( | ||
| 84 | [[I need to operate from a remote QTH>>||anchor="remote"]] | ||
| 85 | |||
| 86 | The rig is at the home QTH, you are at the cottage or on holiday. | ||
| 87 | ))) | ||
| 88 | |||
| 89 | (% class="eax-symptom" %) | ||
| 90 | ((( | ||
| 91 | [[Other EAX messages>>||anchor="messages"]] | ||
| 92 | |||
| 93 | “Application is already running”, white window and others. | ||
| 94 | ))) | ||
| 95 | ))) | ||
| 96 | |||
| 97 | {{id name="noconnect"/}} | ||
| 98 | |||
| 99 | == EAX does not connect == | ||
| 100 | |||
| 101 | (% class="eax-cause" %) | ||
| 102 | ((( | ||
| 103 | Wrong address | ||
| 104 | |||
| 105 | Check the URL field. You need the transceiver IP address, a colon and port **4002**. Example: **192.168.1.50:4002**. | ||
| 106 | ))) | ||
| 107 | |||
| 108 | (% class="eax-cause" %) | ||
| 109 | ((( | ||
| 110 | The computer does not see the transceiver on the network | ||
| 111 | |||
| 112 | 1. Make sure the transceiver is on and connected to the router. | ||
| 113 | 1. Check the connection with **ping** (see below). | ||
| 114 | 1. If there are no replies, the problem is in the network or router. See [[Router>>||anchor="router"]]. | ||
| 115 | ))) | ||
| 116 | |||
| 117 | (% class="eax-cause" %) | ||
| 118 | ((( | ||
| 119 | The EAX interface is disabled on the transceiver | ||
| 120 | |||
| 121 | Enable EAX in the transceiver remote connection settings. | ||
| 122 | ))) | ||
| 123 | |||
| 124 | {{expand title="How to check the connection (ping)" expanded="false"}} | ||
| 125 | Windows: press **Win+R**, type **cmd**, press **Enter**. Linux: open a terminal. Type your transceiver address: | ||
| 126 | |||
| 127 | {{code language="none"}} | ||
| 128 | ping 192.168.1.50 | ||
| 129 | {{/code}} | ||
| 130 | |||
| 131 | Lines “Reply from…” or “bytes from…” — the network works. “Request timed out” or “Destination Host Unreachable” — the computer does not see the transceiver. | ||
| 132 | {{/expand}} | ||
| 133 | |||
| 134 | {{id name="nosound"/}} | ||
| 135 | |||
| 136 | == Connected, but no audio == | ||
| 137 | |||
| 138 | The connect button is lit, but Speed is zero. EAX has reached the transceiver, but the audio from the transceiver does not get to the computer. | ||
| 139 | |||
| 140 | (% class="eax-cause" %) | ||
| 141 | ((( | ||
| 142 | Cause 1. Wrong IP address in EAX settings | ||
| 143 | |||
| 144 | **This is the most common problem, especially on Windows.** When connecting, EAX tells the transceiver the computer address from the **Local IP address** field. The transceiver sends audio only to that address. | ||
| 145 | |||
| 146 | A computer often has several addresses: Ethernet, Wi-Fi, VPN, virtual adapters. If the wrong one is selected, the audio goes nowhere. | ||
| 147 | ))) | ||
| 148 | |||
| 149 | (% class="eax-figure" %) | ||
| 150 | ((( | ||
| 151 | [[image:ip_choice_en.png]] | ||
| 152 | ))) | ||
| 153 | |||
| 154 | 1. Disconnect from the transceiver. | ||
| 155 | 1. Open EAX settings [[image:Main.ERMAK-TT.Руководство пользователя EAX control.WebHome@ic_settings.png]]. | ||
| 156 | 1. In the **Local IP address** field select the address whose first three numbers match the transceiver address. | ||
| 157 | 1. Click **OK** and connect again. | ||
| 158 | |||
| 159 | (% class="eax-check" %) | ||
| 160 | ((( | ||
| 161 | Check: Speed is above zero, the L and R meters move. | ||
| 162 | ))) | ||
| 163 | |||
| 164 | (% class="eax-note" %) | ||
| 165 | ((( | ||
| 166 | On first start the field shows **127.0.0.1** — audio does not work with it. A laptop that connects sometimes over Wi-Fi and sometimes by cable gets different addresses — check the field after changing the connection. | ||
| 167 | ))) | ||
| 168 | |||
| 169 | {{expand title="How to find the computer IP address" expanded="false"}} | ||
| 170 | Windows: **Win+R** → **cmd** → **Enter**, then type **ipconfig**. You need the **IPv4 Address** line of the Ethernet or Wireless adapter. | ||
| 171 | |||
| 172 | Linux: type **ip -4 addr** in a terminal. | ||
| 173 | {{/expand}} | ||
| 174 | |||
| 175 | (% class="eax-cause" %) | ||
| 176 | ((( | ||
| 177 | Cause 2. A firewall blocks the audio | ||
| 178 | |||
| 179 | The audio arrives at the computer over UDP on port **16742**. A firewall may block it. | ||
| 180 | ))) | ||
| 181 | |||
| 182 | **Windows:** | ||
| 183 | |||
| 184 | 1. On the first connection Windows asks about network access. Click **Allow access** and tick **Private networks**. | ||
| 185 | 1. If you clicked Cancel: **Control Panel → Windows Defender Firewall → Allow an app through firewall**. Find **eax** and tick **Private**. | ||
| 186 | 1. Your network type must be **Private**, not Public: **Settings → Network & Internet → network properties**. | ||
| 187 | 1. If your antivirus has its own firewall (Kaspersky, ESET and others), allow EAX there too. | ||
| 188 | |||
| 189 | {{expand title="Linux: open the port in the firewall" expanded="false"}} | ||
| 190 | Fedora: | ||
| 191 | |||
| 192 | {{code language="bash"}} | ||
| 193 | sudo firewall-cmd --permanent --add-port=16742/udp | ||
| 194 | sudo firewall-cmd --reload | ||
| 195 | {{/code}} | ||
| 196 | |||
| 197 | Ubuntu (if ufw is enabled): | ||
| 198 | |||
| 199 | {{code language="bash"}} | ||
| 200 | sudo ufw allow 16742/udp | ||
| 201 | {{/code}} | ||
| 202 | {{/expand}} | ||
| 203 | |||
| 204 | (% class="eax-cause" %) | ||
| 205 | ((( | ||
| 206 | Cause 3. A VPN is on | ||
| 207 | |||
| 208 | Some VPNs send all traffic into the tunnel, and the home network becomes unreachable. Turn off the VPN or allow local network access in it (Allow LAN). | ||
| 209 | ))) | ||
| 210 | |||
| 211 | {{id name="router"/}} | ||
| 212 | |||
| 213 | == Router == | ||
| 214 | |||
| 215 | (% class="eax-figure" %) | ||
| 216 | ((( | ||
| 217 | [[image:router_en.png]] | ||
| 218 | ))) | ||
| 219 | |||
| 220 | **Guest network.** Devices on the guest Wi-Fi network do not see the main network. Connect the computer and the transceiver to the main network. | ||
| 221 | |||
| 222 | **Client isolation** (AP Isolation, Client Isolation). This Wi-Fi option stops devices from talking to each other. Turn it off in the router settings. | ||
| 223 | |||
| 224 | **Two networks: regular and 5G** (for example “Home” and “Home_5G”). Usually this is one network and EAX works. If there is no connection, put both devices on the network with the same name. | ||
| 225 | |||
| 226 | **A mesh system or Wi-Fi extender** sometimes creates a separate network. Check that the first three numbers of the transceiver and computer addresses match. | ||
| 227 | |||
| 228 | {{id name="choppy"/}} | ||
| 229 | |||
| 230 | == The audio drops out == | ||
| 231 | |||
| 232 | Audio flows over the network continuously, and weak Wi-Fi breaks it up. | ||
| 233 | |||
| 234 | 1. If possible, connect the computer or the transceiver by cable. | ||
| 235 | 1. Increase **RX buffer** in EAX settings: **x4** or **x8**. | ||
| 236 | 1. Close programs that load the network heavily (downloads, video). | ||
| 237 | |||
| 238 | {{id name="digital"/}} | ||
| 239 | |||
| 240 | == JTDX sees no signal or the transceiver does not transmit == | ||
| 241 | |||
| 242 | If the L and R meters move in EAX but JTDX sees no signal, the wrong input is selected in JTDX. If the transceiver goes to transmit but the M meter in EAX does not move, the wrong output is selected. | ||
| 243 | |||
| 244 | Correct devices: [[JTDX and WSJT-X setup>>Main.ERMAK-TT.Руководство пользователя EAX control.Настройка JTDX и WSJT-X.WebHome]]. | ||
| 245 | |||
| 246 | If the transceiver goes to transmit but there is no power, select the **EAX** source on the transceiver in the [[TX settings window>>Main.ERMAK-TT.Руководство пользователя ЕРМАК-ТТ.TX settings.WebHome]]. | ||
| 247 | |||
| 248 | {{id name="audiocard"/}} | ||
| 249 | |||
| 250 | == Sound card error == | ||
| 251 | |||
| 252 | The message “Unable to configure audio card” means that EAX cannot open an audio device. | ||
| 253 | |||
| 254 | 1. In EAX settings select all three devices: EAX Output, EAX Input and Audio device. | ||
| 255 | 1. Close programs that may use these devices. | ||
| 256 | 1. Linux: check that the virtual cards are present — **aplay -l** must show Loopback lines. | ||
| 257 | 1. Close EAX and start it again. | ||
| 258 | |||
| 259 | {{id name="remote"/}} | ||
| 260 | |||
| 261 | == Operating from a remote QTH == | ||
| 262 | |||
| 263 | The transceiver is at your home QTH, and you are at the cottage, on holiday or at work. There are two ways to connect EAX to the transceiver over the Internet. | ||
| 264 | |||
| 265 | (% class="eax-figure" %) | ||
| 266 | ((( | ||
| 267 | [[image:remote_en.png]] | ||
| 268 | ))) | ||
| 269 | |||
| 270 | (% class="eax-split" %) | ||
| 271 | ((( | ||
| 272 | (% class="eax-card" %) | ||
| 273 | ((( | ||
| 274 | Option 1. Port forwarding | ||
| 275 | |||
| 276 | Works if both the home and the remote Internet have a **public (external) IP address**. Only router settings are needed. | ||
| 277 | ))) | ||
| 278 | |||
| 279 | (% class="eax-card" %) | ||
| 280 | ((( | ||
| 281 | Option 2. VPN | ||
| 282 | |||
| 283 | Always works, also without a public IP: mobile Internet, hotel, provider with CGNAT. Safer: no ports are open to the whole Internet. | ||
| 284 | ))) | ||
| 285 | ))) | ||
| 286 | |||
| 287 | === Option 1. Port forwarding === | ||
| 288 | |||
| 289 | **On the home QTH router** (where the transceiver is) forward to the transceiver IP address: | ||
| 290 | |||
| 291 | |=Port|=Protocol|=Purpose | ||
| 292 | |4002|TCP|EAX connection to the transceiver | ||
| 293 | |1277|UDP|transmit audio from the computer | ||
| 294 | |||
| 295 | **On the remote QTH router** (where the computer is) forward to the computer IP address: | ||
| 296 | |||
| 297 | |=Port|=Protocol|=Purpose | ||
| 298 | |16742|UDP|receive audio from the transceiver (Local UDP port field in EAX) | ||
| 299 | |||
| 300 | **In EAX:** | ||
| 301 | |||
| 302 | 1. In the URL field type the public IP address of the home router and port 4002, for example **203.0.113.10:4002**. | ||
| 303 | 1. Open settings. In the **Local IP address** field type manually the **public** IP address of the remote router. The transceiver will send audio exactly there. | ||
| 304 | 1. Click **OK** and connect. | ||
| 305 | |||
| 306 | (% class="eax-check" %) | ||
| 307 | ((( | ||
| 308 | Check: Speed is above zero. If the first number is 0, the UDP 16742 forwarding on the remote router does not work or the wrong address is in Local IP address. | ||
| 309 | ))) | ||
| 310 | |||
| 311 | {{expand title="How to find the public IP address and whether it is really public" expanded="false"}} | ||
| 312 | Open an IP check site in your browser — it shows the external address. Compare it with the WAN address in the router settings. If they match, the IP is public and forwarding works. If not (the router shows an address like 10.x.x.x or 100.64–100.127.x.x), the provider uses CGNAT and you need a VPN. | ||
| 313 | |||
| 314 | If the external address changes (dynamic IP), set up DDNS in the home router and type the name in the URL field, for example **myqth.example.net:4002**. | ||
| 315 | {{/expand}} | ||
| 316 | |||
| 317 | (% class="eax-warn" %) | ||
| 318 | ((( | ||
| 319 | An open port 4002 is visible to the whole Internet: anyone who knows the address can connect to the transceiver. If the router can do it, allow forwarding only from your remote QTH address. Or enable forwarding only while you operate. | ||
| 320 | ))) | ||
| 321 | |||
| 322 | === Option 2. VPN === | ||
| 323 | |||
| 324 | A VPN connects the computer to the home network as if you were in your shack. WireGuard, OpenVPN, ZeroTier, Tailscale or a VPN server built into the router will do. | ||
| 325 | |||
| 326 | 1. Connect the computer to the home QTH VPN. | ||
| 327 | 1. In the URL field enter the transceiver address on the home network, for example **192.168.1.50:4002**. | ||
| 328 | 1. In the **Local IP address** field select the address of the computer VPN adapter. | ||
| 329 | |||
| 330 | No port forwarding is needed. | ||
| 331 | |||
| 332 | {{id name="messages"/}} | ||
| 333 | |||
| 334 | == Other messages == | ||
| 335 | |||
| 336 | **Application is already running.** EAX is already running. On Windows look for the EAX icon next to the clock. | ||
| 337 | |||
| 338 | **Lost connection with Rig.** No audio has arrived from the transceiver for a few seconds. See [[Connected, but no audio>>||anchor="nosound"]]. | ||
| 339 | |||
| 340 | **Reconnecting in N s...** The connection dropped, EAX reconnects by itself. If this happens often, check the network. | ||
| 341 | |||
| 342 | **White window on Windows.** Install the [[OpenCL, OpenGL and Vulkan Compatibility Pack>>https://apps.microsoft.com/detail/9nqpsl29bfff]]. | ||
| 343 | |||
| 344 | == Nothing helped == | ||
| 345 | |||
| 346 | 1. Close EAX. | ||
| 347 | 1. Start EAX with a log: Windows — **eax.exe -L debug -l eax.log** in the program folder, Linux — **eax -L debug -l ~~/eax.log**. | ||
| 348 | 1. Reproduce the problem. | ||
| 349 | 1. Send the log file to the developers with a description: what you did and what you saw. | ||
| 350 | ))) |