Wiki source code of Решение проблем

Last modified by UT2UK on 2026/11/16 13:24

Hide last authors
UT2UK 9.3 1 {{velocity}}
UT2UK 9.7 2 $xwiki.ssx.use("Main.DocStyle")$xwiki.jsx.use("Main.DocStyle")
UT2UK 9.3 3 {{/velocity}}
UT2UK 5.2 4
5 (% class="eax" %)
UT2UK 1.1 6 (((
UT2UK 5.2 7 (% class="eax-back" %)
UT2UK 27.3 8 [[← EAX control user guide>>Main.ERMAK-TT.Руководство пользователя EAX control.WebHome]]
UT2UK 1.1 9
UT2UK 9.2 10 (% class="eax-pagehead" %)
11 (((
12 (% class="eax-pagehead-title" %)
UT2UK 27.3 13 Troubleshooting
UT2UK 1.1 14
UT2UK 9.2 15 (% class="eax-pagehead-text" %)
UT2UK 27.3 16 Find what you see and open the fix. Also here: the router, choosing the IP address and operating from a remote QTH.
UT2UK 9.2 17 )))
18
UT2UK 27.3 19 == Find the fix in 2 questions ==
UT2UK 9.9 20
21 (% class="eax-wizard" %)
22 (((
23 (% class="eax-wq" id="wq1" %)
24 (((
UT2UK 27.3 25 What does EAX show after you click the connect button?
UT2UK 9.9 26
UT2UK 27.3 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"]]
UT2UK 9.9 32 )))
33
34 (% class="eax-wq" id="wq2" %)
35 (((
UT2UK 27.3 36 EAX is fine. What about the digital mode program?
UT2UK 9.9 37
UT2UK 27.3 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"]]
UT2UK 9.9 40 )))
41 )))
42
UT2UK 27.3 43 == What do you see? ==
UT2UK 5.2 44
45 (% class="eax-symptoms" %)
46 (((
47 (% class="eax-symptom" %)
48 (((
UT2UK 27.3 49 [[EAX does not connect>>||anchor="noconnect"]]
UT2UK 5.2 50
UT2UK 27.3 51 The message “Unable connect to remote Rig”.
UT2UK 1.1 52 )))
53
UT2UK 5.2 54 (% class="eax-symptom" %)
55 (((
UT2UK 27.3 56 [[Connected, but no audio>>||anchor="nosound"]]
UT2UK 1.1 57
UT2UK 27.3 58 Speed is 0. A few seconds later — “Lost connection with Rig”.
UT2UK 5.2 59 )))
60
61 (% class="eax-symptom" %)
UT2UK 1.1 62 (((
UT2UK 27.3 63 [[The audio drops out>>||anchor="choppy"]]
UT2UK 5.2 64
UT2UK 27.3 65 Clicks, gurgling, gaps.
UT2UK 1.1 66 )))
67
UT2UK 5.2 68 (% class="eax-symptom" %)
69 (((
UT2UK 27.3 70 [[JTDX sees no signal or the transceiver does not transmit>>||anchor="digital"]]
UT2UK 1.1 71
UT2UK 27.3 72 Everything works in EAX, but not in the digital mode program.
UT2UK 5.2 73 )))
UT2UK 1.1 74
UT2UK 5.2 75 (% class="eax-symptom" %)
76 (((
UT2UK 27.3 77 [[Sound card error>>||anchor="audiocard"]]
UT2UK 1.1 78
UT2UK 27.3 79 The message “Unable to configure audio card”.
UT2UK 5.2 80 )))
UT2UK 1.1 81
UT2UK 5.2 82 (% class="eax-symptom" %)
83 (((
UT2UK 27.3 84 [[I need to operate from a remote QTH>>||anchor="remote"]]
UT2UK 1.1 85
UT2UK 27.3 86 The rig is at the home QTH, you are at the cottage or on holiday.
UT2UK 5.2 87 )))
UT2UK 1.1 88
UT2UK 5.2 89 (% class="eax-symptom" %)
90 (((
UT2UK 27.3 91 [[Other EAX messages>>||anchor="messages"]]
UT2UK 1.1 92
UT2UK 27.3 93 “Application is already running”, white window and others.
UT2UK 5.2 94 )))
95 )))
UT2UK 1.1 96
UT2UK 5.2 97 {{id name="noconnect"/}}
UT2UK 9.3 98
UT2UK 27.3 99 == EAX does not connect ==
UT2UK 1.1 100
UT2UK 5.2 101 (% class="eax-cause" %)
102 (((
UT2UK 27.3 103 Wrong address
UT2UK 1.1 104
UT2UK 27.3 105 Check the URL field. You need the transceiver IP address, a colon and port **4002**. Example: **192.168.1.50:4002**.
UT2UK 5.2 106 )))
UT2UK 1.1 107
UT2UK 5.2 108 (% class="eax-cause" %)
109 (((
UT2UK 27.3 110 The computer does not see the transceiver on the network
UT2UK 1.1 111
UT2UK 27.3 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"]].
UT2UK 5.2 115 )))
UT2UK 1.1 116
UT2UK 5.2 117 (% class="eax-cause" %)
118 (((
UT2UK 27.3 119 The EAX interface is disabled on the transceiver
UT2UK 1.1 120
UT2UK 27.3 121 Enable EAX in the transceiver remote connection settings.
UT2UK 5.2 122 )))
UT2UK 1.1 123
UT2UK 27.3 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:
UT2UK 1.1 126
UT2UK 5.2 127 {{code language="none"}}
128 ping 192.168.1.50
129 {{/code}}
UT2UK 1.1 130
UT2UK 27.3 131 Lines “Reply from…” or “bytes from…” — the network works. “Request timed out” or “Destination Host Unreachable” — the computer does not see the transceiver.
UT2UK 5.2 132 {{/expand}}
UT2UK 1.1 133
UT2UK 5.2 134 {{id name="nosound"/}}
UT2UK 9.3 135
UT2UK 27.3 136 == Connected, but no audio ==
UT2UK 1.1 137
UT2UK 27.3 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.
UT2UK 1.1 139
UT2UK 5.2 140 (% class="eax-cause" %)
141 (((
UT2UK 27.3 142 Cause 1. Wrong IP address in EAX settings
UT2UK 1.1 143
UT2UK 27.3 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.
UT2UK 1.1 145
UT2UK 27.3 146 A computer often has several addresses: Ethernet, Wi-Fi, VPN, virtual adapters. If the wrong one is selected, the audio goes nowhere.
UT2UK 5.2 147 )))
UT2UK 1.1 148
UT2UK 5.2 149 (% class="eax-figure" %)
150 (((
UT2UK 27.3 151 [[image:ip_choice_en.png]]
UT2UK 5.2 152 )))
UT2UK 1.1 153
UT2UK 27.3 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.
UT2UK 1.1 158
UT2UK 5.2 159 (% class="eax-check" %)
UT2UK 1.1 160 (((
UT2UK 27.3 161 Check: Speed is above zero, the L and R meters move.
UT2UK 1.1 162 )))
163
UT2UK 5.2 164 (% class="eax-note" %)
165 (((
UT2UK 27.3 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.
UT2UK 5.2 167 )))
UT2UK 1.1 168
UT2UK 27.3 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.
UT2UK 27.2 171
UT2UK 27.3 172 Linux: type **ip -4 addr** in a terminal.
UT2UK 5.2 173 {{/expand}}
UT2UK 1.1 174
UT2UK 5.2 175 (% class="eax-cause" %)
176 (((
UT2UK 27.3 177 Cause 2. A firewall blocks the audio
UT2UK 5.2 178
UT2UK 27.3 179 The audio arrives at the computer over UDP on port **16742**. A firewall may block it.
UT2UK 5.2 180 )))
181
UT2UK 1.1 182 **Windows:**
183
UT2UK 27.3 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.
UT2UK 1.1 188
UT2UK 27.3 189 {{expand title="Linux: open the port in the firewall" expanded="false"}}
UT2UK 5.2 190 Fedora:
UT2UK 1.1 191
192 {{code language="bash"}}
193 sudo firewall-cmd --permanent --add-port=16742/udp
194 sudo firewall-cmd --reload
195 {{/code}}
196
UT2UK 27.3 197 Ubuntu (if ufw is enabled):
UT2UK 1.1 198
199 {{code language="bash"}}
200 sudo ufw allow 16742/udp
201 {{/code}}
UT2UK 5.2 202 {{/expand}}
UT2UK 1.1 203
UT2UK 5.2 204 (% class="eax-cause" %)
205 (((
UT2UK 27.3 206 Cause 3. A VPN is on
UT2UK 1.1 207
UT2UK 27.3 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).
UT2UK 5.2 209 )))
UT2UK 1.1 210
UT2UK 5.2 211 {{id name="router"/}}
UT2UK 9.3 212
UT2UK 27.3 213 == Router ==
UT2UK 1.1 214
UT2UK 5.2 215 (% class="eax-figure" %)
216 (((
UT2UK 27.3 217 [[image:router_en.png]]
UT2UK 5.2 218 )))
UT2UK 1.1 219
UT2UK 27.3 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.
UT2UK 1.1 221
UT2UK 27.3 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.
UT2UK 1.1 223
UT2UK 27.3 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.
UT2UK 1.1 225
UT2UK 27.3 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.
UT2UK 1.1 227
UT2UK 5.2 228 {{id name="choppy"/}}
UT2UK 9.3 229
UT2UK 27.3 230 == The audio drops out ==
UT2UK 1.1 231
UT2UK 27.3 232 Audio flows over the network continuously, and weak Wi-Fi breaks it up.
UT2UK 1.1 233
UT2UK 27.3 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).
UT2UK 1.1 237
UT2UK 5.2 238 {{id name="digital"/}}
UT2UK 9.3 239
UT2UK 27.3 240 == JTDX sees no signal or the transceiver does not transmit ==
UT2UK 1.1 241
UT2UK 27.3 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.
UT2UK 1.1 243
UT2UK 27.3 244 Correct devices: [[JTDX and WSJT-X setup>>Main.ERMAK-TT.Руководство пользователя EAX control.Настройка JTDX и WSJT-X.WebHome]].
UT2UK 1.1 245
UT2UK 27.3 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]].
UT2UK 1.1 247
UT2UK 5.2 248 {{id name="audiocard"/}}
UT2UK 9.3 249
UT2UK 27.3 250 == Sound card error ==
UT2UK 1.1 251
UT2UK 27.3 252 The message “Unable to configure audio card” means that EAX cannot open an audio device.
UT2UK 1.1 253
UT2UK 27.3 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.
UT2UK 1.1 258
UT2UK 5.2 259 {{id name="remote"/}}
UT2UK 9.3 260
UT2UK 27.3 261 == Operating from a remote QTH ==
UT2UK 5.2 262
UT2UK 27.3 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.
UT2UK 5.2 264
UT2UK 7.2 265 (% class="eax-figure" %)
266 (((
UT2UK 27.3 267 [[image:remote_en.png]]
UT2UK 7.2 268 )))
UT2UK 1.1 269
UT2UK 7.2 270 (% class="eax-split" %)
271 (((
272 (% class="eax-card" %)
273 (((
UT2UK 27.3 274 Option 1. Port forwarding
UT2UK 7.2 275
UT2UK 27.3 276 Works if both the home and the remote Internet have a **public (external) IP address**. Only router settings are needed.
UT2UK 7.2 277 )))
278
279 (% class="eax-card" %)
280 (((
UT2UK 27.3 281 Option 2. VPN
UT2UK 7.2 282
UT2UK 27.3 283 Always works, also without a public IP: mobile Internet, hotel, provider with CGNAT. Safer: no ports are open to the whole Internet.
UT2UK 7.2 284 )))
285 )))
286
UT2UK 27.3 287 === Option 1. Port forwarding ===
UT2UK 7.2 288
UT2UK 27.3 289 **On the home QTH router** (where the transceiver is) forward to the transceiver IP address:
UT2UK 7.2 290
UT2UK 27.3 291 |=Port|=Protocol|=Purpose
292 |4002|TCP|EAX connection to the transceiver
293 |1277|UDP|transmit audio from the computer
UT2UK 7.2 294
UT2UK 27.3 295 **On the remote QTH router** (where the computer is) forward to the computer IP address:
UT2UK 7.2 296
UT2UK 27.3 297 |=Port|=Protocol|=Purpose
298 |16742|UDP|receive audio from the transceiver (Local UDP port field in EAX)
UT2UK 7.2 299
UT2UK 27.3 300 **In EAX:**
UT2UK 7.2 301
UT2UK 27.3 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.
UT2UK 7.2 305
306 (% class="eax-check" %)
307 (((
UT2UK 27.3 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.
UT2UK 7.2 309 )))
310
UT2UK 27.3 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.
UT2UK 7.2 313
UT2UK 27.3 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**.
UT2UK 7.2 315 {{/expand}}
316
UT2UK 5.2 317 (% class="eax-warn" %)
UT2UK 1.1 318 (((
UT2UK 27.3 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.
UT2UK 1.1 320 )))
321
UT2UK 27.3 322 === Option 2. VPN ===
UT2UK 7.2 323
UT2UK 27.3 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.
UT2UK 7.2 325
UT2UK 27.3 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.
UT2UK 7.2 329
UT2UK 27.3 330 No port forwarding is needed.
UT2UK 7.2 331
UT2UK 5.2 332 {{id name="messages"/}}
UT2UK 9.3 333
UT2UK 27.3 334 == Other messages ==
UT2UK 1.1 335
UT2UK 27.3 336 **Application is already running.** EAX is already running. On Windows look for the EAX icon next to the clock.
UT2UK 1.1 337
UT2UK 27.3 338 **Lost connection with Rig.** No audio has arrived from the transceiver for a few seconds. See [[Connected, but no audio>>||anchor="nosound"]].
UT2UK 1.1 339
UT2UK 27.3 340 **Reconnecting in N s...** The connection dropped, EAX reconnects by itself. If this happens often, check the network.
UT2UK 1.1 341
UT2UK 27.3 342 **White window on Windows.** Install the [[OpenCL, OpenGL and Vulkan Compatibility Pack>>https://apps.microsoft.com/detail/9nqpsl29bfff]].
UT2UK 1.1 343
UT2UK 27.3 344 == Nothing helped ==
UT2UK 5.2 345
UT2UK 27.3 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.
UT2UK 5.2 350 )))