Yes I did try that. It appears that what is required is to add another station to TSQL and attach the AX2 callsign to this station.
Then when you go to this config it is set to the other station which picks up the AX2 callsign to sign the adi files with.
Then moving back to normal is changing the station back to the normal station.
I have set this up but not tried it.
Alan
LOTW Upload Failure
Re: LOTW Upload Failure
Strange...
Your error message does mention that the certificate is under the VK2MET account, and the call is AX2MET.
When configuring L4OM for upload, make sure you have the correct callsign at the proper place. If uploading using the xport then TQSL, it means TQSL is properly configured for AX2MET. So the problem is in L4OM config.
It looks like the password is not the issue, but it may be worth to have a look at that too...
Your error message does mention that the certificate is under the VK2MET account, and the call is AX2MET.
When configuring L4OM for upload, make sure you have the correct callsign at the proper place. If uploading using the xport then TQSL, it means TQSL is properly configured for AX2MET. So the problem is in L4OM config.
It looks like the password is not the issue, but it may be worth to have a look at that too...
Thanks + 73
Paul F6EXV
Paul F6EXV
