Log4OM

Is the file correctly created on windows folder? Can you open it normally?

Checking and fixing if there is something wrong, next beta

We have created a small introduction on how JT applications works with other programs, like Log4OM. The document will explain how UDP works in simple words, allowing users to understand how to interconnect applications.
Hope this helps

https://www.log4om.com/resources/

if you enable DEBUG MODE in log4om help menu you should be able to see what JT message contains (from program log in help menu) when it's sent to Log4OM...
just send a QSO and check what is contained in the log file, and eventually share that with us

Sorry, i'm missing the point... the decimal separator in some countries is "." and the thousand separator is comma "," Other countries have this configuration inverted, so "thousand separator" is "." and decimal separator is comma ",". In this case t...

was quite complex, as the "id code" needed to be replaced with a potentially "duplicable" short description...
i hope the fix works well, please take some time to test it by downloading latest beta version, if possible

Basically because there are no "info" about existance of a secondary callsign on QRZ.COM, so Log4OM needs to make 2 different calls, one to "full callsign" and one to "simple one", slowing down the process. I can eventually handle this situation, but whis will possibly ...

That's something coming from the very beginning of the project...
never reworked so far... i'll add to the list

Please give a look here:
https://www.log4om.com/l4ong/usermanual ... ith_JT.pdf

Search found 2469 matches

Re: FTP problem from Log4OM

Re: Incorrect 'Nearest METAR station' and METAR not loading.

Re: Ability to assign VFO offset to Omnirig Radio

Working with JT

Re: WSJT-X log time always 00:00:00

Re: 3cm fake news !!!

Re: Select profile by name instead of hex id

Re: L4OM ignores QRZ Callsign lookup with country prefix

Re: Select profile by name instead of hex id

Re: I want to be a "dumb" user