No names in log #1062
Replies: 5 comments 2 replies
|
There are two things you can try. In QLog disable QSY Wiping in rig control and see if that helps. If that doesn't get it try to disable the 'Clear DX call after QSO' QLog allows you to enter details in the net log panel (POTA, SOTA, Comments etc). But if the frequency changes it could be wiped and I've seen it where WSJT will clear the callsign before QLog processes the UDP message. |
|
Well it wasn't the QSY Wiping. But where do I find that Additional features window? I've looked all through the Settings but can't find it. |
|
Sorry, neither of those ideas worked. |
|
Can I assume that QLog is getting the WSJTX Band Activity and QSO's via UDP Port 2237, setup in the Network tab of QLog settings? Maybe QLog needs a separate UDP inbound port for QSO's? Just a idea. |
|
QLog does listen on port 2237 for the WSJT logging information. It also operates with FLDigi already as well.
The port on the Network Tab is for QLog to rebroadcast the information to other applications.
What version of WSJT are you using? I use the WSJT Improved version and it does store the callbook lookup information. But I can help you figure it out if I know the version.
… On Jun 7, 2026, at 8:29 PM, Alan ***@***.***> wrote:
Can I assume that QLog is getting the WSJTX Band Activity and QSO's via UDP Port 2237, setup in the Network tab of QLog settings? Maybe QLog needs a separate UDP inbound port for QSO's? Just a idea.
QLog is the only logging software that I have ever had this problem with. I've used Log4om for a really long time. I've tried ACLog, Log4ym, Station Master, HRD Logbook. None of them had this problem, and all of them had a dedicated UDP port for logging QSO's. QLog is, IMO, much nicer than all of those.
Also need a way for other software's to forward UDP QSO's into QLog, like VarAC, Fldigi, and N1MM,
—
Reply to this email directly, view it on GitHub <#1062?email_source=notifications&email_token=AUEEMXUD5IBMX6JWXEATH3D46YJHPA5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCNZSGEZTSMRVUZZGKYLTN5XKOY3PNVWWK3TUUVSXMZLOOSWGM33PORSXEX3DNRUWG2Y#discussioncomment-17213925>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AUEEMXTYLN76DFUFGAD2HU346YJHPAVCNFSM6AAAAACZ6CZWEOVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTOMRRGM4TENI>.
Triage notifications, keep track of coding agent tasks and review pull requests on the go with GitHub Mobile for iOS <https://github.com/notifications/mobile/ios/AUEEMXW7HC2EYBL7TLYURIT46YJHPA5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCNZSGEZTSMRVUZZGKYLTN5XKOY3PNVWWK3TUUVSXMZLOOSVGM33PORSXEX3JN5ZQ> and Android <https://github.com/notifications/mobile/android/AUEEMXQDHUKEVMYCE3QMOR346YJHPA5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCNZSGEZTSMRVUZZGKYLTN5XKOY3PNVWWK3TUUVSXMZLOOSXGM33PORSXEX3BNZSHE33JMQ>. Download it today!
You are receiving this because you commented.
|
|
I'm running the latest WSJTX v3.1.0 win64 improved plus, and the latest QLog v0.51.0. The port on the Network tab also feeds the WSJTX window in QLog. I have it set to Multicast 224.0..0.1 Port 2237 same as WSJTX and GT. If I change it to something else I get no new spots in the window. Also, thanks for all the help! |
|
After a lot of research and testing on this issue, I found out that Log4om will automatically search QRZ for every new QSO and fill in any missing info such as name, grid, etc. Some of the other logging software's that I've tried got their new QSO's via forwarding from Log4om, which may be why the name field was filled in. More research and testing is needed. |
Uh oh!
There was an error while loading. Please reload this page.
When I complete a QSO in WSJTX the new QSO is logged into both QLog and Log4om. The entry in Log4om is complete, the entry in QLog is always missing the 'Name'. I have to use the 'Update from Callbook' to fill in the missing name. WSJTX sends the QSO to Log3om via UDP Port 2236, but how does QLog receive the QSO from WSJTX?
All reactions