Hi all, 

Has anyone else run into this issue with using the WSJT-X / GridTracker when logging FT8 in real time to DXKeeper?

User Defined Defaults for VK2FIG's station are the G5RV antenna (UDF 0) and TS-180S radio (UDF 1).  For the first QSO of the day, these defaults are not applied, and these need correcting. (The same happens with other UDFs.) Up until today, after correcting the first QSO, all subsequent QSOs for the day were ok.

Today saw similar behaviour. But after leaving the radio and coming back to it later, the next QSO had the defaults wrong, and it appears that various QSOs (but not all) over the last few days are now also wrong. Now no defaults seem to stick for any QSOs. We used the Advanced editing option to fix all of these at the end of the day.

We don't know where the problem is occurring, as there appear to be two interfaces, viz. WSJT-X to GridTracker (?) and GridTracker to DXKeeper, noting that there may be hidden virtual interfaces that we don't know about.

Does anyone have any suggestions about how to make the DXKeeper defaults stick under these conditions?

73,

Mike VK2IG 

I do not use GridTracker so this is just a guess but it seems as
if Grid Tracker is supplying incorrect data for some/all QSOs.
DXKeeper does not apply its defaults if an external application
includes those fields in the external UDP or DDE "log data" command.

Does anyone have any suggestions about how to make the DXKeeper defaults stick under these conditions?

Stop using Grid Tracker and log directly from WSJTX.

73,

... Joe, W4TV

On 2022-11-30 4:30 AM, Mike Dower wrote:

Hi all,
Has anyone else run into this issue with using the WSJT-X / GridTracker when logging FT8 in real time to DXKeeper?
User Defined Defaults for VK2FIG's station are the G5RV antenna (UDF 0) and TS-180S radio (UDF 1).  For the first QSO of the day, these defaults are not applied, and these need correcting. (The same happens with other UDFs.) Up until today, after correcting the first QSO, all subsequent QSOs for the day were ok.
Today saw similar behaviour. But after leaving the radio and coming back to it later, the next QSO had the defaults wrong, and it appears that various QSOs (but not all) over the last few days are now also wrong. Now no defaults seem to stick for any QSOs. We used the Advanced editing option to fix all of these at the end of the day.
We don't know where the problem is occurring, as there appear to be two interfaces, viz. WSJT-X to GridTracker (?) and GridTracker to DXKeeper, noting that there may be hidden virtual interfaces that we don't know about.
Does anyone have any suggestions about how to make the DXKeeper defaults stick under these conditions?
73,
Mike VK2IG

+ AA6YQ comments below

Has anyone else run into this issue with using the WSJT-X / GridTracker when logging FT8 in real time to DXKeeper?

User Defined Defaults for VK2FIG's station are the G5RV antenna (UDF 0) and TS-180S radio (UDF 1). For the first QSO of the day, these defaults are not applied, and these need correcting. (The same happens with other UDFs.) Up until today, after correcting the first QSO, all subsequent QSOs for the day were ok.

Today saw similar behaviour. But after leaving the radio and coming back to it later, the next QSO had the defaults wrong, and it appears that various QSOs (but not all) over the last few days are now also wrong. Now no defaults seem to stick for any QSOs. We used the Advanced editing option to fix all of these at the end of the day.

We don't know where the problem is occurring, as there appear to be two interfaces, viz. WSJT-X to GridTracker (?) and GridTracker to DXKeeper, noting that there may be hidden virtual interfaces that we don't know about.

Does anyone have any suggestions about how to make the DXKeeper defaults stick under these conditions?

+ There is no interoperation between DXLab and GridTracker.

+ As far as I know, DXLab provides all of the functionality that GridTracker provides.

73,

Dave, AA6YQ

--

+ AA6YQ comments below

 

Grid Tracker can send WJTX QSOs to DX Keeper.

+ You can log QSOs directly from WSJT-X to DXLab without any intermediary; see

https://www.dxlabsuite.com/dxlabwiki/GettingStartedwithK1JTyModesDirect

 

You can also select other loggers.

+ That's irrelevant to DXLab users.

 

I sometimes run WSJTX on a Linux machine, as well as a Win/DXLabs setup.

 

I use Grid Tracker on Linux (JT Alert is Windows only), and WSJTX QSO's go to my Win PC which hosts DXLabs over my LAN. I believe it is via DDE.

+ If you're running DXLab, what purpose is GridTracker serving other than consuming resources on your Linux system?

# More AA6YQ comments below

+ You can log QSOs directly from WSJT-X to DXLab without any intermediary; see

https://www.dxlabsuite.com/dxlabwiki/GettingStartedwithK1JTyModesDirect

# The correct URL is

https://www.dxlabsuite.com/dxlabwiki/GettingStartedwithK1JTModesDirect

     73,

          Dave, AA6YQ

 

 

--

# more AA6YQ commens below

+ If you're running DXLab, what purpose is GridTracker serving other than consuming resources on your Linux system?

 

it performs the functions of JTAlert to indicate needed DX, state, grid etc. 

# SpotCollector does all of that, and immediately updates your realtime award tracking when you log a new QSO.

 

I keep the linux machine set for example 6m; DXabs moves from band to band, mode to mode etc

# SpotCollector can simultaneously monitor multiple sources of spots - four DX Cluster nodes, the DX Summit web cluster, local instances of WSJT-X - for all of the bands and modes on which you are pursuing DXCC, IOTA, Marathon, VUCC, WAS, WAZ, and WPX awards.

       73,

              Dave, AA6YQ

On 2022-11-30 5:21 PM, d_ziolkowski wrote:

I use Grid Tracker on Linux (JT Alert is Windows only), and WSJTX
QSO's go to my Win PC which hosts DXLabs over my LAN. I believe it is
via DDE.

DDE is a proprietary Microsoft "in memory" protocol. Anything "cross
machine" or "via network" would need to be either TCP or UDP.

73,

... Joe, W4TV

On 2022-11-30 5:21 PM, d_ziolkowski wrote:

Dave-
Grid Tracker can send WJTX QSOs to DX Keeper. You can also select other
loggers.
I sometimes run WSJTX on a Linux machine, as well as a Win/DXLabs setup.
I use Grid Tracker on Linux (JT Alert is Windows only), and WSJTX QSO's go
to my Win PC which hosts DXLabs over my LAN. I believe it is via DDE.
Works fine for me, I think it is just sending the WSJT X generated ADIF
record. If that is the case perhaps the DEFAULTS are overwritten or not
generated in this case.
Dan KC2STA
On Wed, Nov 30, 2022 at 4:08 PM Dave AA6YQ <aa6yq@...> wrote:

+ AA6YQ comments below

Has anyone else run into this issue with using the WSJT-X / GridTracker
when logging FT8 in real time to DXKeeper?

User Defined Defaults for VK2FIG's station are the G5RV antenna (UDF 0)
and TS-180S radio (UDF 1). For the first QSO of the day, these defaults
are not applied, and these need correcting. (The same happens with other
UDFs.) Up until today, after correcting the first QSO, all subsequent QSOs
for the day were ok.

Today saw similar behaviour. But after leaving the radio and coming back
to it later, the next QSO had the defaults wrong, and it appears that
various QSOs (but not all) over the last few days are now also wrong. Now
no defaults seem to stick for any QSOs. We used the Advanced editing option
to fix all of these at the end of the day.

We don't know where the problem is occurring, as there appear to be two
interfaces, viz. WSJT-X to GridTracker (?) and GridTracker to DXKeeper,
noting that there may be hidden virtual interfaces that we don't know about.

Does anyone have any suggestions about how to make the DXKeeper defaults
stick under these conditions?

+ There is no interoperation between DXLab and GridTracker.

+ As far as I know, DXLab provides all of the functionality that
GridTracker provides.

73,

Dave, AA6YQ