FRLogger has good built in support for working with WSJT-X and virtually all of that support is applicable to JTDX. Like anything, the right settings must be used to optimize the interaction between the two programs.
This page will document settings that work. Of course there can be variations to these settings that may work equally well.
SmartSDR, your slice, and DAX must be setup correctly for JTDX to work at all.
- Mode - Use DIGU because it takes the EQ out of the path
- Slice DAX - Set the slice DAX channel - You will need know this for WSJT-X
- Filter Width - Make sure your filter is wide enough
- Input source - DAX should be selected as the input source (blue)
- TX filter - Make this wide
Settings in the DAX Control Panel must be correct for JTDX to work at all.
- TX DAX - This must be enabled (blue)
- TX Level - Set this initially to 50
- Slice DAX - Enable the matching DAX from step 2 above (blue)
- Slice DAX Level - Set this initially to 50
Setting your DAX levels for correct operation. You have two levels that need to be set correctly for SmartSDR/DAX to work correctly with JTDX:
- DAX TX Level
- DAX Slice RX Level
The best way I've found to set the DAX TX level is to actually transmit a signal from JTDX. I've reduced my power to 1 watt and used a dummy load. You want to adjust your DAX TX level using the slider in the DAX Control panel for TX Level while watching the modulation level in SmartSDR.
To do this process you will need to complete the rest of the interconnection setup so everything is talking and working. Then transmit from JTDX, (CALL CQ into a dummy load perhaps) and look at the following part of SmartSDR. Adjust your TX level using the slider in the DAX control panel to get just a touch of red on the level meter:
You need to adjust your DAX RX Slice level using the slider control in the DAX control panel until the indication on JTDX is right around 60 or so. Other levels will work just fine but try to achieve roughly 60.
Settings in the CAT Control Panel must be correct for WSJT-X to work at all.
The best way to communicate control signals between JTDX and SmartSDR is to use a TCP/IP CAT control port. You can setup any port you like and that is not in use on your system. By default the port is 5002. If you change it make a note of it as you will need it in WSJT-X setup.
Settings in JTDX must match settings you selected in slice and DAX setup.
- General Tab - This is how I personally like my settings. None of these are critical and this is only a recommendation.
- Radio Tab - Here you want to select FlexRadio 6xxx as the radio type then you must select the CAT TCP/IP port that you specified in CAT setup. Note taht PTT Method is set to CAT. You can test your CAT and PTT settings using the buttons in the bottom right.
- Radio Tab - Split Operation. Note that I ahve this set to None. In my experience this is only needed to be turned on when your radio does not have a RX/TX filter band width wide enough to transmit correctly at the high end of the band area in use. Up under SmartSDR setup one thing we did was to increase our TX bandwidth so this should not be needed.
- Reporting Tab - This area provides the link from WSJT-X to other programs such as JTAlert and FRLogger. Details on setup will be covered below.
The UDP server in JTDX is what sends out virtually all needed data that other programs can consume. The issue is that at times a bad performing program can "swallow" the broadcast over this port so other programs cannot consume it.
Earlier versions of JTAlert did this but I believe it has since been corrected. It is possible that FRLogger can swallow the broadcasts as well. I will be looking to resolve this issue. JTDX offers a secondary UDP server that can be used if programs have issues sharing the UDP broadcast.
However, with correct setup it is possible to make everything play together quite nicely. In some cases use of the alternate broadcast of ADIF data can be used to achieve logging.
JTAlert is a wonderful program that provides lots of fantastic alerting abilies to stations worked, needed and much more. But for some people they just want a simple system. Setup using JTAlert will follow this section.
Using FRLogger directly with JTDX allows for a very simple system. The setup is as follows.
- JTDX Setup Reporting Tab - Make sure the UDP server is setup as shown in the image above. If you change the port make note of it because FRLogger will need to know what that port is.
- FRLogger Setup - Please follow the sequence below to configure FRLogger to directly communicate with JTDX
Access the FRLogger configuration section using the "Gear" icon in the upper left of the main window. Select the "Online & Lookup" tab. Make sure that the port number shown in the WSJT box matches the port number shown under the UDP server in WSJT-X setup.
Access the FRLogger WSJT panel and select the "Settings" tab. Make sure that "Monitor WSJT-X" is checked. This will connect FRLogger to WSJT-X to receive the UDP broadcasts that WSJT-X sends out.
Other settings of interest on the WSJT panel "Settings" tab:
- Lookup monitored stations - This sends a request to either QRZ or HamQTH to obtain station data based on the call sign received. This is nice data to have but be aware that if things are really busy this can cause a lot of traffic. To use QRZ you must be at minimum an XML data subscriber.
- Automatically Log - This causes FRLogger to automatically log for you contacts you make in WSJT-X
- Prompt when logging - This will cause FRLogger to prompt you before logging. Since WSJT-X prompts I don't usually enable this.
- Lookup when logging - This is an alternative to the first lookup option that will only generate a lookup request for stations you log.
- Show monitored stations as pan spots - Using the FlexAPI this will post spots to your pan for stations monitored from WSJT-X
Once you have things set the way you like, SmartSDR is up and running and set to a WSJT-X frequency, WSJT-X is up and running you should begin to see decoded stations in the WSJT panel on the "Stations" tab. The data that is filled in will depend upon your lookup settings.
When you work a station in JTDX with this setup, FRLogger will display your current station in the WSJT panel. Data presented will again depend upon your lookup settings.
When the QSO is using the settings we specified in JTDX the QSO will be automatically logged. There will be no prompt.
If you want to prompt to log the QSO you will need to change the logging settings on the general tab of JTDX settings.
The setup process to run JTDX, JTAlert and FRLogger requires that the three programs all communicate. This means there is an order that needs to be followed when starting up the various pieces of software. This order assumes you have SmartSDR, DAX and CAT all configured, running and on frequency.
- JTDX - This must be started first
- JTAlert - This needs to be started next
- FRLogger - This needs to be started AFTER JTAlert
By following this startup sequence it will allow the various programs to connect to each other in the right order.
JTDX settings remain the same as documented above. The settings in JTAlert must be configured as shown below for it to connect to JTDX and allow FRLogger to connect. Access JTAlerts settings via the "Settings" menu then "Manage Settings".
On the left side, under "Applications", select WSJT-X/JTDX. Enable the rebroadcast object and specify a port.
Back in FRLogger, select the "Gear" icon for configuration and change the WSJT port on the online & lookup tab to match the port number above.
IMPORTANT I have found that when changes are made to UDP ports that it is best to restart the various pieces of software, in order. After the restart data will flow from WSJT-X into JTAlert, then into FRLogger.
Working a station in JTDX will look very similar to working a station without JTAlert. FRLogger will receive updates on the current station. Assuming you have automatically log set on in JTDX, the QSO will automatically be logged for you.
The Clock/Map panel in FRLogger can be set to automatically display decodes from JTDX. As seen below the "yellow" lines are decodes from JTDX. The intensity of the line indicates the relative signal strength. You can change the color of the lines as desired by double-clicking on the color block.