but not clear as to which fields are updated with the "Update info" method. The Update infor process updates any EMPTY field in the QSO record from information published by the on line lookup service selected by the Log4OM user (QRZ/HamQTH) However if the information for an empty field is not avail...

w9mdb wrote: ↑

21 Jul 2019, 04:16

Try port 23 instead of 7373.

Seems 7323 works much better here too but 23 has problems.

Mike

Then you should contact the cluster provider

Install a new download on the new computer but do not run it. Then copy all of the files and folders in the C:\Users\g4poparrl.net\AppData\Roaming\LogOM directory to the same directory on the new computer Copy the .sql logbook database across to the same location on the new computer as the old compu...

I am sorry but I fail to see the issue it works fine for me! This is my login script // use <callsign> command to send your callsign to the server. <DELAY> <callsign> sh/mydx/70 I always use one delay because so servers are slow but as you can see from the screen shot it works 100% Untitled.jpg BTW ...

You need to ensure that the information about Station ID (Location) is correct in the Log4OM options/External logs form, it should match the station location in the TQSL program.


Also be aware that special characters are not acceptable like !"£$%^&*_-)({}[]:@~#<>/\

You should also be aware that no cluster provider sends the mode as a field only the occasional mode added to the notes field by a spotter. The mode is selected by your regional band plan which you can freely modify. I must warn you that you will chase your tail because these FT8 spots do not confor...

That information is not available if you want to see the SQLite record number you need to us an SQLite manager and check with that.

However for what purpose do you need this number?

<DELAY> adds 1 second delay

<DELAY>
<DELAY>
<DELAY>
Three on separate lines adds 3 secconds

Seems the server address has changed, perhaps ask SOTA MT and let us know what the answer is?