RemoteTx Manual
remotetx.net

EasyConnect troubleshooting

  • EasyConnect must be running on the same computer as the browser, with Enable radio link ticked. The pill should say Radio link: ws://127.0.0.1:12700 (waiting).
  • If Chrome asked about access to devices on your local network and you said no, allow it in the site settings (the padlock icon next to the address) and click EC again.
  • If you changed the radio-link port in EasyConnect, right-click EC and set the same address.
  • Check the radio page is one of the supported radios.

N1MM or WSJT-X can't connect#

  • The CAT pill must be green: CAT: 127.0.0.1:12500. If it says stopped, click Start. If the log says TCP listen failed, another program is using the port: change CAT TCP port and Apply & restart, and use the same port in the logger.
  • In WSJT-X, type 127.0.0.1:12500 (not localhost).
  • For a logger on another computer, set CAT TCP host to 0.0.0.0 and allow EasyConnect through the firewall.

The logger connects but the radio doesn't follow#

  • Check the Radio link pill shows the radio. Without the link, EasyConnect only changes its own Radio state.
  • Watch the log: commands from the logger (→) should be followed by W → radio (cat): … lines.
  • On the FT-710 and FT-991A, knob changes reach the logger within about a second (the VFO is polled).

A COM-port logger doesn't connect#

  • Check the com0com pair: EasyConnect uses one side (e.g. COM10), the logger the other (COM11).
  • The COM 1 pill shows (finding speed…) until the program talks. If it never locks, pick the program's baud rate instead of Auto.
  • The log says the port closed: another program has opened the same side of the pair.

A command shows as UNKNOWN#

Your logger uses a command EasyConnect doesn't implement yet. Most loggers carry on regardless. Click Save… to keep a copy of the log when reporting it, so the command can be added.

HRD Logbook doesn't show the radio's frequency#

  • The HRD pill must show HRD: 127.0.0.1:7809. If it says off, tick Enable HRD Rig Control server and Apply & restart.
  • If the log says HRD server listen failed … is HRD Rig Control running?, close HRD Rig Control (it uses the same port) and click Apply & restart.
  • In HRD Logbook, the rig connection must point to 127.0.0.1 port 7809. Once it connects, the pill shows (1).
  • The radio must be linked (EC on). Without the link, HRD Logbook only sees EasyConnect's own Radio state.

FT8 decodes don't reach the logger#

  • In RemoteTx, EC must be on, and the FT8 tab open. EasyConnect's FT8 pill should say client linked.
  • On the FT8 tab, a Logger off chip means both FT8 paths are off in EasyConnect: tick Send the RemoteTX FT8 client to loggers as WSJT-X and Apply & restart.
  • UDP Server and port must match what the logger listens on (HRD: its WSJT-X settings; usually 127.0.0.1:2237).

The logger's double-click doesn't call the station#

  • Tick Accept UDP requests.
  • Logger on another PC: allow EasyConnect through the firewall, and if HRD uses a multicast address, tick Also hear requests sent to the multicast group.
  • The log should show ← Reply "…" → FT8 client. If there's no first UDP message from … line at all, the logger's packets aren't reaching this computer.

QSOs are logged twice in HRD#

Both paths are sending to the same log. Use either the WSJT-X UDP path or N1MM Logger+ Broadcasts, not both.

© RemoteTx® · remotetx.net · Manual built 2026 · Updated 2026-11-19