Page 1 of 2
Automatic upload on new QSO not working?
Posted: 04 Aug 2014, 15:59
by WR3Y
I have auto updates enabled and the Automatic upload on new QSO checked in the External logs tab menus. EQSL, HRD log, ClubLog and LOTW , HamQTH do not update my QSO even though I have the correct passwords and user IDs loaded. What am I doing wrong?
thanks
Rob
WR3Y
Re: Automatic upload on new QSO not working?
Posted: 04 Aug 2014, 16:35
by DF5WW
Have to edit ..... Hamqth upload works here ... all latest QSO´which are logged in L4O are uploaded. Maybe wrong username or password ??
Re: Automatic upload on new QSO not working?
Posted: 04 Aug 2014, 17:53
by G4POP
WR3Y wrote:I have auto updates enabled and the Automatic upload on new QSO checked in the External logs tab menus. EQSL, HRD log, ClubLog and LOTW , HamQTH do not update my QSO even though I have the correct passwords and user IDs loaded. What am I doing wrong?
thanks
Rob
WR3Y
Are you saying that when you log a QSO in Log4om that the QSO's are not being uploaded to any of the online logs (HRDLog, EQSL, HamQTH, QRZ, and Clublog)
Re: Automatic upload on new QSO not working?
Posted: 07 Aug 2014, 17:09
by WR3Y
Terry,
I upgraded to the new version. Only my contacts to eQSL and maybe QTH.com and Clublog are being uploaded, but None to LOTW, HRDnet or QRZ(no API code). If I right click and hit upload/Update to HRDlog.net for example from my logbook nothing happens either. I did that to Clublog and only one of the two new QSO's I tried - did update. Strange?
At the very bottom of my screen HRDLog ON AIR is not connected it is a red dot.
Perhaps Communicator is the problem? I set it up with admin privileges, but it doesn't seem correct. It is running. Super cluster is running. Only TCP Connection to Log4OM is green, not FIDigi inbound or outbound (red dots). I can not find a file to put in the Adif polling box., same thing for FIDIG files? It seems most of my Log4OM files are under ve7cc folder for some reason. I don't see anything similar in my documents.
I just want my log to auto update to all the services and my QRZ page to have "Live on the air" logbook.
Thanks for any help you can give me.
Rob
WR3Y
Re: Automatic upload on new QSO not working?
Posted: 07 Aug 2014, 17:15
by G4POP
Rob,
I will record a video explaining what is required, either later this evening or tomorrow because the Q&A gets tedious on the forum
Btw LOTW is not and never has been an automatic upload
As for FLDigi page 169 onward of the latest user guide explains in detail - We no longer pole the ADIF file we now use XML/RPC as detailed in the user guide
Re: Automatic upload on new QSO not working?
Posted: 07 Aug 2014, 17:36
by WR3Y
Ok that would be great. Thank you very much!
Rob
Re: Automatic upload on new QSO not working?
Posted: 08 Aug 2014, 15:54
by G4POP
Rob,
I have just uploaded a video covering the automatic upload of QSO's to on line log books to YouTube, here is the link
http://youtu.be/TNIfz8lDuuQ
Re: Automatic upload on new QSO not working?
Posted: 08 Aug 2014, 17:37
by WR3Y
Terry thanks so much! Great video! That answers all my questions! I didn't know the box was for the code and not the password under HRD external log settings!
Rob
WR3Y
Re: Automatic upload on new QSO not working?
Posted: 09 Aug 2014, 20:30
by WR3Y
Auto uploads work great, but I can't upload to LOTW. I have to do it manually with the TQSL program separately. When I try to use LOG4OM I get an error message that the file is not in this path, but I am using the default path.
Says operation completed with errors:
TQSL file not found on this path
c:\ProgramFiles\trustedQSL\tqsl.exe. Exiting
I never used the private sign pass. Works fine when I upload manually with TQSL.
Do I need to put the certificate somewhere for LOG4OM to see it?
Thanks
Rob
Re: Automatic upload on new QSO not working?
Posted: 10 Aug 2014, 01:11
by DF5WW
Hi Rob, ist the path you find in Log4OM "Settings/External Logs" the same wher the TQSL exe ist stored on your HDD ??? Must be the same. I have installed TQSL in another folder "D:/Hamradio/Trustedqsl/tqsl.exe and have set the path in L4o to that folder. Works perfect.
The certificate must only seen by TQSL.exe and not by Log4OM. I
