Log4OM

JA9HWD

Maybe use Hamlib's "Rigctld".
I think you should start it from the command prompt, connect to the rig, and connect with Log4OM's "TCP Connection".

JA9HWD

here is an example of adding 'F/H mode' to my FT8 qso's. Dave k4em Regarding "comment", Log4OM2 should not be processing anything. You are probably entering comments in the WSJT-X log dialog. This will continue unless you delete it. Or it's in the continuous display settings related to JT...

JA9HWD

Is it possible that there is no search target because the eQSL.cc account profile you are trying to acquire does not match the eQSL.cc QTH nickname specified in the Log4OM user configuration?

JA9HWD

Confirmed! something changed in FLDigi we will look into it I see. I didn't know about it because I couldn't read manuals with automatic translation until recently. Callsigns can be sent from Log4OM to fldigi, but I thought there was no function to send callsigns from fldigi to Log4OM. I think it w...

JA9HWD

Thank you but in this case the issue was caused by me not turning on GridTracker along with WS-jTX, Omnirig and Log4OM. I had configured all of these apps to work together and when working together they work fine. But with one of them not running, this kind off issue can come up. So this issue is n...

JA9HWD

I have browsed through multiple topics of trouble with lookups to QRZ.com. Many of the answers were about being a HAM member of QRZ.com and not an XML subscriber. However, most of the problems seem to be caused by fast input of callsigns using UDP from other apps such as WSJT-X. The person confirmin...

JA9HWD

Found the mistake. For whatever reasons the Locator wasn't set correctly (nothing has been changed in the settings). So the synchronisation failed. 73, Stefan It means that it was rejected because the QTH of the profile registered in LoTW does not match. Thank you for the report. I'm glad you were ...

JA9HWD

I think this phenomenon is caused by the same problem as the topic below.
https://forum.log4om.com/viewtopic.php?t=9057

JA9HWD

This has been happening since version 2.27.1.0. At the time, I reported this on Facebook's Log4OM Enthusiasts forum, but no one took it seriously. To avoid this problem, I set the settings so that UDP transfer and TQSL interactive mode are not used. Now there are no problems except when the LoTW ser...

JA9HWD

Here is a video clip showing how Log4OM seems to look up the call sign every time the VFO is turned. https://e.pcloud.link/publink/show?code=XZMe39Zsno8VbTANs4zyMpoYqpVjJXgDJhV In my case, there is no lookup when I operate the VFO dial, and there is no flickering in the marked area. I'm using flrig.

Search found 30 matches

Re: CAT control of TS-890 using IP & HamLib unsuccessful

Re: Comment field populates with old data

Re: EQSL download update records with cards

Re: FLDigi Callsign NOT sending to Log4OM

Re: User Name field not being populated from QRZ

Re: Log4OM2 does not search QRZ.com

Re: LotW

Re: User Name field not being populated from QRZ

Re: V2.32.1.0 Stalls during shutdown

Re: Log4OM Call Sign Lookup Behavior when changing frequency