Log4OM

Welcome

I have installed version 2.3.0.0 and there is already one error.
Please look at the picture.
There is no GRID in Log4OM V2.3 and in JTDX.
The configuration I did not change is the same as in version 2.2.0.0
Does not download data from QRZCQ (I have a premium account)
In version 2.2.0.0 the data is shown.

in the attachment log file with Log4OM

No Grid L0g4OM 2.3



Grid - Log4OM 2.2




Log file

"I didn't change any configurations in Log4OM 2.3, JTDX and JT_Alert"

what method are you using to receive callsign? JTAlert? direct from JT messages from application? rebroadcast from JTalert?

IW3HMH wrote: 03 Feb 2020, 19:26 what method are you using to receive callsign? JTAlert? direct from JT messages from application? rebroadcast from JTalert?

Hi Danielle

According to the description from JT-Alert, and with Log4OM 2.2 works without any problem.

Jan,

Its working fine for me with Log4OM V2.3.0.0. With JTDX and JTAlert.

Please post screenshots of your V2 Configurations, Connections tab. And your JTDX Settings, Reporting tab. And your JTAlert Settings, Logging, Log4OM V2 tab, and the Applications, WSJT-X/JTDX tab.

Thanks,

Doug - W7DRM

ok but not until tomorrow

W7DRM wrote: 03 Feb 2020, 21:15 Jan,

Its working fine for me with Log4OM V2.3.0.0. With JTDX and JTAlert.

Please post screenshots of your V2 Configurations, Connections tab. And your JTDX Settings, Reporting tab. And your JTAlert Settings, Logging, Log4OM V2 tab, and the Applications, WSJT-X/JTDX tab.

Thanks,

Doug - W7DRM

Welcome W7DRM

If you analyze the log file from Log4OM 2 that I sent, you will see where the error is.
In Log4OM 2.3 no data from QRZCQ.com was downloaded for a given character, while in Log4OM 2.2 the data is downloaded and there is no error.
In the afternoon, I will paste screenshots of the settings you requested.

Regards

W7DRM wrote: 03 Feb 2020, 21:15 Jan,

Its working fine for me with Log4OM V2.3.0.0. With JTDX and JTAlert.

Please post screenshots of your V2 Configurations, Connections tab. And your JTDX Settings, Reporting tab. And your JTAlert Settings, Logging, Log4OM V2 tab, and the Applications, WSJT-X/JTDX tab.

Thanks,

Doug - W7DRM

Hello, W7DRM

I attach screenshots of the Lof4OM2, JTDX and JT-Alert settings

With these settings in Log4OM 2.2 everything works as it should.
EDIT: Remote Control : Port 2241

Missing log file

I have exactly the same issue: 2.2 showed the locator from QRZ.com fine, but 2.3 is not doing this. Working with JTDX and JTAlert with no configuration changes since Log4OM 2.2.

73, Frédéric, HB9CQK

Question to the Development Team.

There is a chance that version 2.3 will have this problem removed with JT-Alert / JTDX or is it better to stay with version 2.2?
I gave all the data and screenshots what was asked and the answer is not there.
And as you can see not only I have this problem.

Regards