Search found 167 matches
- 07 Sep 2019, 14:40
- Forum: Software Integration
- Topic: WSJT-X logging without 3rd party software
- Replies: 1
- Views: 5166
WSJT-X logging without 3rd party software
For those who want to log WSJT-X QSOs in Log4OM without using JTAlert or GridTracker as a "repeater" in between: WSJT-X 2.1.0: Settings > Reporting > Secondary UDP Server (deprecated): Activate "Enable logged contact ADIF broadcast". Note server IP address and port number. Log4OM...
- 22 Jun 2019, 18:46
- Forum: User Support
- Topic: Select config at startup
- Replies: 3
- Views: 2910
Re: Select config at startup
I'm using shortcuts for each of my 4 configurations. Here is an example: C:\PortableApps\Log4OM\LogOMUI.exe CONFIG=c65a98bc-22ed-4194-a673-5a962a1e3371 No double quotes needed since there are no spaces in the path. But this one also works: "C:\PortableApps\Log4OM\LogOMUI.exe" CONFIG=c65a98...
- 18 Nov 2018, 16:17
- Forum: Italian language forum
- Topic: Omnirig
- Replies: 3
- Views: 10501
Re: Omnirig
Giovanni, OmniRig 2.0 is working fine here, although serving 1 rig only. Did you try to debug the communication using the OmniRig Client available at http://www.dxatlas.com/OmniRig/ ? OmniRig 2.0 comes as replacement for a previously installed OmniRig exe file but does not register OmniRig as COM ob...
- 30 Jul 2018, 11:12
- Forum: User Support
- Topic: Missing country on some qso v1.32.
- Replies: 16
- Views: 9133
Re: Missing country on some qso v1.33.1.0
Sample log entry sent by GridTracker to Log4OM (taken from the Communicator log): 2018-07-29 12:35:51.0318 DEBUG: TCPManagement: Incoming QSO from TCP Connection (ADD) <BAND:3>12m <CALL:6>SP6ECQ <FREQ:9>24.915831 <MODE:3>FT8 <QSO_DATE:8>20180729 <TIME_ON:6>123100 <QSO_DATE_OFF:8>20180729 <TIME_OFF:6...
- 23 Jul 2018, 19:28
- Forum: User Support
- Topic: Missing country on some qso v1.32.
- Replies: 16
- Views: 9133
Re: Missing country on some qso v1.32.
Using WSJT-X and GridTracker. Same problem here since I started using Log4OM's communicator. In my opinion, country info is not part of the log entries forwarded to Log4OM. Rather I would expect Log4OM to populate the "country" field in the same way as when importing an ADIF file. 73, Mark...
- 05 Jun 2018, 18:22
- Forum: Software Integration
- Topic: GridTracker V1.18.0530
- Replies: 7
- Views: 7144
Re: GridTracker V1.18.0604
Yes, logging is working again!
73, Markus HB9BRJ
73, Markus HB9BRJ
- 04 Jun 2018, 04:54
- Forum: Software Integration
- Topic: GridTracker V1.18.0530
- Replies: 7
- Views: 7144
Re: GridTracker V1.18.0530
Yes I did:
- 03 Jun 2018, 13:08
- Forum: Software Integration
- Topic: GridTracker V1.18.0530
- Replies: 7
- Views: 7144
GridTracker V1.18.0530
Since upgrading GridTracker to version 1.18.0530, no more log entries are received by Log4OM. I did not change any settings. Log4OM Communicator as well as GridTracker ports are 2236 as they were before. The communicator's activity log is attached. Anybody else having this problem?
73, Markus HB9BRJ
73, Markus HB9BRJ
- 12 May 2018, 07:11
- Forum: General discussions
- Topic: GridTracker
- Replies: 3
- Views: 5523
Re: GridTracker
When launching the GridTracker-Installer.1.18.0511 from my file manager, nothing happened. Then I launched it from a command prompt, which brought up a warning that Windows (W10 1803) would not let me run this program, probably because it's brand new. A click on "More info", then "Run...
- 29 Apr 2018, 17:16
- Forum: User Support
- Topic: WSJT-X Log Entry Missed
- Replies: 3
- Views: 2877
ADIF Import: Date range only
TQSL has a nice feature: When importing an ADIF log, a date range can be specified. Since ADIF is the most popular exchange format, it would make sense to add this feature to Log4OM as well.
73, Markus HB9BRJ
73, Markus HB9BRJ
