710 ConsoleGet the app
// Easy & Direct Remote

Operate through the station PC

Use a simple share code over the hosted relay, or connect directly over a trusted LAN, VPN or Tailscale network. The station PC remains in control of the FT-710.

Get the station PC working locally first

The station PC is physically connected to the FT-710 by USB and supplies radio control, spectrum and audio. The remote PC is the computer you operate from.

Before testing either Remote method at the station, confirm:

  • CAT control and frequency/mode readback work
  • The main FT4222 spectrum and waterfall work
  • FT-710 receive audio reaches the selected listening device
  • The selected computer microphone reaches the radio
  • PTT keys and releases correctly

The station PC must remain powered, connected to the FT-710 and running 710 Console throughout the remote session.

Choose the connection method

Easy Remote

The quickest option across the internet. Both PCs make outbound encrypted connections to the hosted Render relay and pair with a short-lived, single-use share code.

No router port-forwarding or VPN setup is normally required.

Direct Remote

Connects directly to the station PC over a trusted local network or a network you provide, such as Tailscale, WireGuard, ZeroTier or OpenVPN.

It supports saved stations after the first pairing.

Easy Remote with a share code

  1. On the station PC, connect 710 Console to the FT-710 and confirm everything works locally.
  2. Open REMOTE and enable Relay/Easy Remote hosting.
  3. Select Generate Share Code, then copy the nine-character code.
  4. Send the code privately to the remote operator. Do not post it publicly.
  5. On the remote PC, choose the relay/share-code connection, paste the code and select Connect.
  6. Confirm control and receive operation first, then test audio and PTT.

A share code expires after five minutes and works only once. Generate a fresh code for a new pairing attempt.

Direct Remote on the same LAN

  1. On the station PC, open Remote and select Start direct hosting or enable Direct Remote.
  2. Find the station PC's current IPv4 address. In Windows Command Prompt, run ipconfig and check the active Wi-Fi or Ethernet adapter.
  3. On the remote PC, enable the Direct / VPN client option.
  4. Enter the station PC's real IPv4 address as the Host and use the port shown by 710 Console. The standard default is 47100.
  5. If this is a new remote computer, choose Pair New and complete the pairing steps below.
  6. Select the saved station and connect.

Do not enter 0.0.0.0

If the station says it is listening on 0.0.0.0:47100, that means it is accepting connections on suitable network interfaces. Enter the station PC's actual IPv4 address on the remote PC, not 0.0.0.0.

Local addresses can change

Home routers usually assign addresses using DHCP. If a Direct connection stops working after a reboot or reconnect, run ipconfig again. For a permanent setup, reserve the station PC's address in the router.

Direct Remote over VPN or Tailscale

  1. Install and configure the same trusted VPN solution on both PCs.
  2. Confirm the two PCs can reach each other through that network before opening 710 Console.
  3. Start Direct Remote hosting on the station PC.
  4. Use the station PC's VPN or Tailscale address as the Host on the remote PC.
  5. Pair the computers if required, save the station and connect.

Do not expose the Direct Remote port to the public internet with router port forwarding unless you deliberately understand and accept the security implications. A trusted LAN or VPN is the intended Direct workflow.

Pair a new Direct Remote computer

  1. Start Direct Remote hosting at the station.
  2. At the remote PC, enter the station Host/IP and port, then choose Pair New.
  3. Generate a fresh pairing code at the station and enter it at the remote PC.
  4. Confirm the remote computer appears in the station's paired-computer list.
  5. Save the station and use Connect for future sessions.

If the remote PC has an old saved pairing but the station no longer lists it, choose Forget on the remote PC, generate a fresh code and pair again.

Audio, scope and performance

Remote operation cannot repair an incomplete local setup. At the station, select the FT-710 USB receive and transmit endpoints. At the remote PC, select the microphone and speakers/headphones you actually want to use.

Control, audio and scope use separate channels. If a slower network becomes sluggish, reduce the scope presentation frame rate or use a narrower span and test again. The public 0.2.78 defaults keep waterfall sampling RF-faithful rather than inventing extra RF measurements.

Use Help → Audio check… on the affected PC for audio faults and Help → Scope check… on the station for missing spectrum data.

Transmit safety

The current public build treats Remote PTT and TUNE as station-side leases rather than ordinary network toggles. The remote sends a heartbeat while transmitting; if heartbeats stop for 500 ms—or the link, audio path, app or ownership fails—the station releases transmit locally.

Reconnection always starts in receive and a previous transmit lease is never restored. One remote operator is supported per station session.

Always confirm the radio returns to receive during initial setup. If it does not, release transmit from the station side and stop testing until the station is safely back in RX.

Troubleshooting

Easy Remote code rejected or expired

Generate a new code at the station. Codes are single-use and expire after five minutes. Check that both PCs have internet access and compatible app versions.

Direct Remote cannot connect

Confirm Direct hosting is running, then recheck the station's current LAN/VPN address and the port shown in 710 Console. Check the Windows firewall and confirm the two PCs can reach each other on that network.

Worked yesterday but fails today

The station's DHCP address may have changed. Run ipconfig again or check the current VPN/Tailscale address.

Old saved station will not connect

Forget the old entry, generate a fresh pairing code and pair again.

Control works but no audio

Confirm all four audio selections work locally at the station, then check the remote microphone/listening selections. Use Help → Audio check….

No spectrum

Run Help → Scope check… on the station PC. The remote cannot repair a missing local FT4222 path.

PTT will not stay on

The safety lease is being withheld or lost because a required connection or audio condition is unhealthy. Resolve the status shown on both PCs; do not try to defeat the watchdog.

Before emailing support

  • State whether you are using Easy Remote, Direct LAN or Direct VPN/Tailscale.
  • Say whether pairing completed and exactly what works: control, waterfall, RX audio, TX audio and PTT.
  • For Direct, include the station's current LAN/VPN address and port, but never passwords or private VPN keys.
  • Reproduce the fault, then choose Help → Report a problem… on the PC that shows it. The diagnostic report is sent with your message. For remote faults, send one from the station PC and one from the remote PC if you can, and mention both references.