Skip to content

DXLog

DXLog connects to RimuDAX over TCI. Each DXLog radio gets its own TCI connection, and each connection reaches one slice.

This page is for Windows.

Not yet in our test results

The settings on this page come from DXLog 2.6.38 and from a beta tester's working setup. We have not yet run our own test. A beta tester uses DXLog in SO2R with RimuDAX, and RimuDAX 1.1.18 includes fixes from those reports. The first time you transmit, connect a dummy load to the radio, and make sure that you can stop the transmission from RimuSDR.

Before you start

DXLog radio Slice RimuDAX port
Radio 1 DAX channel 1 50001
Radio 2 (SO2R) DAX channel 2 50002

DXLog has no receiver setting, so each radio uses its own port. With one radio, set up only Radio 1.

Step 1 - RimuSDR

  1. Start RimuSDR and connect to the radio.

  2. Set the slice for Radio 1 to DAX channel 1.

  3. For SO2R, set the slice for Radio 2 to DAX channel 2.

Step 2 - RimuDAX

  1. Start RimuDAX. Connect it to the radio and select the RimuSDR station.

    There is no mode to select. On Windows, TCI is the only mode.

  2. Make sure that the TX button in the TX Streams section reads Enabled if DXLog must transmit.

Step 3 - DXLog interfaces

  1. Go to Options > Configure interfaces.

  2. On a free row, select the row's enable checkbox.

  3. Set the port column to WS.

    A TCP row does not work with TCI. Use WS.

  4. Set the device column to Radio1.

  5. Open the row's setup. Set Radio to TCI Radio, the address to 127.0.0.1 and the port to 50001.

  6. For SO2R, set up a second row in the same way, with Radio2 and port 50002.

  7. Click OK.

DXLog connects when it sets up its interfaces: when a log opens, when you click OK in Configure interfaces, and when you reset the interfaces. With no log open, it does not connect. If RimuDAX is not running yet, DXLog tries again every 2 seconds, so you can start RimuDAX after DXLog.

Step 4 - Check that it works

  1. In DXLog, make sure that each radio shows the frequency and mode of its slice.

  2. In RimuDAX, make sure that the Clients section shows one client for each DXLog radio, on ports 50001 and 50002.

SO2R and split

With two TCI programs or two DXLog radios on two slices, a slice that has a DAX channel is never another radio's VFO B. Split shows only while TX is on a slice with no DAX channel on the same panadapter, such as the copy that RimuSDR's SPLIT button makes.

Troubleshooting

DXLog does not connect
Check that the row is enabled, that its port column is WS, not TCP, and that a log is open. Check that RimuDAX is running and connected to the radio.
The radio keys, but there is no audio, after DXLog resets its interfaces
Update to RimuDAX 1.1.18 or later. Earlier versions could be left with no DAX TX stream after a reset.

For other problems, see Using TCI.