Log4OM¶
Log4OM connects to RimuDAX over TCI. One connection carries the frequency and mode, the spots and the CW messages.
This page is for Windows.
You do not need a COM port or RimuCAT
Log4OM talks to RimuDAX directly. You do not need a virtual COM port tool or a RimuCAT port for Log4OM.
What Log4OM gets over TCI¶
- Frequency and mode
- Log4OM follows the slice, and a change in Log4OM tunes the slice.
- Spots
- Spots from Log4OM's cluster appear on the panadapter in RimuSDR. Clicking a spot in RimuSDR tells Log4OM which spot you clicked.
- CW
- CW messages and macros from Log4OM go out through the radio's CW keyer.
Step 1 - RimuSDR¶
-
Start RimuSDR and connect to the radio.
-
Set the slice to DAX channel
1.With TCI, the DAX channel only selects the slice. Port
50001reaches DAX channel 1.
Step 2 - RimuDAX¶
-
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.
Step 3 - Log4OM CAT interface¶
-
Go to Settings > Program configuration > CAT interface.
-
Set CAT Engine to TCIProtocol.
-
Turn on CAT auto-start.
-
On the TCI tab, set ADDRESS to
localhostand Port to50001.
Step 4 - Spots on the panadapter¶
-
In the CAT interface settings, turn on Send cluster spot to radio interface.
-
Restart CAT.
Log4OM sends spots only when a logbook database is open.
A spot from Log4OM stays on the panadapter for 30 minutes. At most 200 program spots are on the radio at once; the oldest goes first. Spots from RimuSDR's own spot sources are never changed.
Step 5 - CW¶
-
Go to Settings > Program configuration > CW Keyer interface.
-
Select TCI Protocol.
Log4OM's stop key, and closing Log4OM, stop the CW at once. A callsign that you correct while it is being sent goes out corrected, if the correction arrives before the radio sends those characters.
Step 6 - Check that it works¶
-
In Log4OM, make sure that the frequency and mode of the slice are shown.
-
In RimuDAX, make sure that the Clients section shows one client, on port
50001.The status line then shows
TCI: 1 client on 50001-50008.
Test results¶
We tested Log4OM 2.42.1.0 on Windows: frequency and mode, spots, spot clicks, and CW macros.
Troubleshooting¶
- Log4OM does not connect
- Check that RimuDAX is running and connected to the radio. Check that the
TCI tab has
localhostand port50001, and that CAT is started. - No spots on the panadapter
- Check that Send cluster spot to radio interface is on, that you restarted CAT, and that a logbook database is open.
- CW does not go out
- Check that the CW Keyer interface is set to TCI Protocol. Terminal mode
(
cw_terminal) is not supported: the transmitter drops when the text ends.
For other problems, see Using TCI.