The gateway to global remote control from Yaesu

The SCU-LAN10 Network Interface

The SCU-LAN10, made by Yaesu, is a network interface that enables remote control of compatible transceivers such as the FT-DX101D or FT-DX10 via the Internet or local networks. It connects the transceiver to a router via USB and Ethernet to enable remote access via PC software. This facilitates remote operation so that users can use their devices regardless of location.

Integration into a complex environment using SCU-LAN10

As I used to travel a lot for work, I looked into the possibilities of controlling my entire station remotely back in 2013 and here is what I did.

First of all, the problem was that all components had to be controlled from the PC. These were for HF operation:

  • Kennwood TS-2000
  • microHAM DiGi-Keyer II
  • Expert 1K-FA power amplifier
  • Yaesu G1000 rotor with EA4TX interface
  • Antenna 3-element Ultrabeam
  • Power amplifier IJ0XX for 2m
  • DCW 2004 sequence controller for MHP-145
  • Rotor Yaesu G5600 with EA4TX interface
  • Swisslog
  • SatPC32 with SuM
  • WSJT

Automating the power amplifier, rotor and antenna

There exists PC software for the power amplifier, rotor and antenna. I have implemented the on/off switching via a NETIO socket strip. TeamViewer is used as the remote control software. I created the actual connection of the TS-2000 via Remoterig RRC-1248MKII, as well as via the external control unit RC-2000. This constellation has worked largely automatically for years: When I select a HF station from the Swisslog cluster, the beam turns in the corresponding direction, the Ultrabeam antenna adjusts itself accordingly, the power amplifier switches to the correct band and the TS-2000 is set to the correct frequency.

Complete remote control of the TS-2000

How to integrate the FT-DX10 with WIN4YAESU and Swisslog

Even when I moved the FT-DX10 into my shack, I didn't want to do without this automation. As the FT-DX10 only has one usable USB port, I use the WIN4YAESU software, which uses Com2Com to implement several virtual USB ports. Technically speaking, the FT-DX10 is connected to the computer. The Com2Com virtual USB ports are then used to control Swisslog and the Ultrabeam. Swisslog in turn controls the rotors and the FT-DX10 (Swisslog supports up to 4 transceivers). Only the automatic band selection of the 1K-FA directly via the FT-DX10 was done using a CT165 cable and ABCD band selection. Same here: If I select a HF station from the Swisslog cluster, the beam turns in the corresponding direction, the Ultrabeam antenna tunes itself accordingly, the power amplifier goes to the correct band and the FT-DX10 is set to the correct frequency.

Flexible operation of the FT-DX10

Of course, I also wanted to operate the FT-DX10 remotely. Both on the Internet (from the motorhome) and on the intranet (my shack is in a not very well heated cabin). Of course, operation from the shack itself should also be possible without any restrictions.

FT8 to TS-2000 SSB to FT-DX10

Arrived and unpacked: The SCU-LAN10 interface in detail

Now to the actual object of desire. On March 1, 2024, the time had finally come and I held the long-awaited SCU-LAN10 interface in my hands. As always with WiMo, the device was excellently packaged. The packaging contained the device itself, the DIN cable with ferrite cores and a USB cable. A connection cable for the power supply is not included - the interface gets its power from the FT-DX10 via the DIN cable. However, it is confusing that the voltage socket is a 4 mm plug and not a 4.9 mm or 5.4 mm plug. In addition, the supply voltage is specified as 10.8V.

Hidden treasures on the Yaesu homepage

No software is included with the interface. On the WiMo homepage, however, you will find the installation manuals and the operation manual - but both manuals are only available in English. The actual software is unfortunately somewhat hidden on the Yaesu homepage.

The challenges of integration

As you would expect, not everything in IT always works the way you want it to. The initial configuration and integration into my own LAN alone took me 4 hours. First error (the one in front of the monitor) - the SCU-LAN10 requires the ACC cable and the USB cable. But even after connection, the SCU-LAN10 was not ready to work in the local network at first. After many attempts and changing the fixed IP addresses, it worked and the SCU-LAN10 worked remotely on my Telekom Speedport router.

The SCU-LAN10 did not accept some IP addresses - the software could not start the transceiver - only repeated changes of IP and checking with PING led to success. However, it is interesting to note that the Speedport does not display an IP4 address.

IP address

I noticed a few things with the SCU-LAN10

  • The SCU-LAN or the configuration program does not support DHCP. The SCU-LAN is delivered with the fixed IP address 192.168.49.1 and must be reconfigured with an appropriately adapted computer.
  • The SCU-LAN requires the only USB interface of the FT-DX10. In my case, this is a no-go, as the FT-DX10's USB interface is already used for various other applications via Win4Yaesu.
  • The SCU-LAN10 user interface is fundamentally different from the FT-DX10 interface. In reality, you get a completely different transceiver.

The Win4Yaesu settings

As a first step, I connected the FT-DX10 to the PC and set the interface to COM10 with 38,400 baud. In WIN4YAESU as well - it looks like this:

Settings

The next step was to create 3 Com2Com pairs: 15/16 for Swisslog, 17/18 for UltraBeam, 19/20 for SCU-LAN10. Which then looks like this:

3rd Party Settings

Grünstadt, on May 2, 2024

Ludwig Senitsch, DH8SL

SCU-LAN10

SCU-LAN10 Network Interface

To the product

Share this post with friends!