Ladislav,
Thank you so much! I changed my password from one that contains special characters, to one that does not, and now it works!
The old password contained ¡°@¡° and ¡°+¡±, so perhaps one of those two was creating the problem.?
I really appreciate your support and feedback!
Sincerest thanks,
Robert
|
Robert,
QLog uses the external TQSL utility to upload to LoTW. QLog itself does not need any password to upload ADI to LoWT. If you are asked to enter a password then it is requested by TQSL because TQSL has to unlock your private key to sign the ADIF File. Private Key password? is not a Login password. Both passwords can be the same or different. it's up to your preferences how you set it up.
On the other hand, the download is managed by QLog. Here QLog uses the password entered in QLog's settings. I tested several password options that contain special characters such as /," which could cause problems in HTTPs communication, but I did not notice any problems. This password has to be the same as you are?using during authorization to the LoTW site.
Please, verify whether the QLog Setting ->LoTW tab really contains the correct pair username/password that is used for logging in the LoTW. It is not a password for the unlocking private key of TQSL.
Maybe you can also try the option of temporarily changing the login password to "simpler", which only contains one group of characters, and see if the login is successful.
Regards Ladislav
|
Thank you for making this impressive software available. I would be very grateful if anyone could help me with the following error.?
When I try to upload or download to LotW, I get the error ¡°LoTW update failed: Incorrect Loging [sic] or password¡±. However, the login info is correct (works fine on the ARRL website, the tqsl app, and CQRLOG).
I¡¯m using the latest QLog 0.35.0 from the PPA, Ubuntu 24.04, and the real version that is packaged with 24.04. I was having the same issue with prior versions and hoped that upgrading would fix it, but it doesn¡¯t seem to have done so.?
I¡¯m not sure if this helps, but I also had trouble with tqsl from CQRLOG until I removed the quotation marks from my QTH in the string sent to the command line. Then it seemed to work fine.?
Thank you so much in advance,
Robert?
KB3CAX
|
Ladislav, ? Thank you for the information! ? -Brian ?
toggle quoted message
Show quoted text
From: [email protected] [mailto:[email protected]] On Behalf Of ok1mlg
Sent: Saturday, May 4, 2024 2:02 PM
To: [email protected]
Subject: Re: [qlog] Release 0.35 ? Your finding can be divided into the two parts. 1) Missing Name - unfortunately, there is a regression issue. In order to unify the search result from both supported callbooks QRZ and HamQTH, I used new fields as a source for Name in QRZ, which are not sent in the case of free-QRZ. Good news is that it is possible to use other fields to fix it. It will be fixed in a new release. 2) County - free-QRZ response does not contain this information. ? Let me add additional notes about free-QRZ: From : "Access to this service (Callbook Query) requires user authentication through the use of a valid username and password. While any QRZ user may login to the service, an active QRZ Logbook Data subscription is required to access most of its features. Non-subscriber access limits the data fields that are returned and is primarily intended for testing and troubleshooting purposes only." You need XML-subscription (or higher) to get all fields from QRZ. It is not a QLog policy, it is QRZ's policy.
|
Hello Brian,
Your finding can be divided into the two parts.
1) Missing Name - unfortunately, there is a regression issue. In order to unify the search result from both supported callbooks QRZ and HamQTH, I used new fields as a source for Name in QRZ, which are not sent in the case of free-QRZ. Good news is that it is possible to use other fields to fix it. It will be fixed in a new release.
2) County - free-QRZ response does not contain this information.
Let me add additional notes about free-QRZ: From :
"Access to this service (Callbook Query) requires user authentication through the use of
a valid username and password. While any QRZ user may login to
the service, an active QRZ Logbook Data subscription is required to
access most of its features. Non-subscriber access limits the data
fields that are returned and is primarily intended for testing and
troubleshooting purposes only."
You need XML-subscription (or higher) to get all fields from QRZ. It is not a QLog policy, it is QRZ's policy.
Regards Ladislav
|
thanks Ladislav,
I completely understand all your problems.
I am very sorry for your decision because the program is, obviously, still a little immature but from a future perspective extremely interesting and truly pleasant to use.
As I told you I'm too old to start the program, test, release routine again.
I'll try to "digest" the win versions in a virtual win environment, as I already do with the logger I use.
Roberto
|
Roberto,
Unfortunately, I can't help you. Maybe someone from the QLog's MacOS community can help you.? QLog 0.35 did not change password management.
I'm adding maybe another not-so-good news, but I'm thinking about stopping officially releasing DMGs for MacOS. These reasons lead me to it
1) I don't have MacOS therefore I am not able to test/support this platform. The MacOS DMG was created as a result of an experiment. From the beginning on the MacOS Intel platform there was no problem. But with the launch of Apple Silicon, people are reporting "strange" issues
2) I am able to solve Linux/Windows only. If the online map doesn't work, or other things on MacOS, someone needs to solve it and add some changes to QLog. Nothing of the sort happened yet.
3) The MacOS platform is becoming more and more closed. It
seems that QLog can no longer be translated for MacOS 14 (Apple
Silicon) because this version apparently requires Digital Signature of
the binary. However, this requires an Apple DEV subscription.
These reasons lead me to believe that it may be time to end support for
macOS. However, this does not mean that the code will become unusable
for macOS; rather, the GitHub Release Page will no longer contain a DMG
package. Unfortunately, this change means that most users won't be able
to use QLog. I would appreciate it if there were a way to continue
supporting the macOS platform in the future.
Regards Ladislav
|
Is anyone else having issues in v0.35 with the name and county not populating with a free QRZ account? I am running on Slackware 15.0 x86_64 (post 15.0 -current).
?
?
-Brian, KB3ORR
?
On 05/04/2024 3:07 AM EDT Roberto IU2NUB <iu2nub.rb@...> wrote:
?
?
Thanks Ladislav,
Osx environment
After updating to 0.35 I noticed that the setting program loses the storage of passwords for services such as EQSL, etc.
But the strangest thing is that it requests them from the password storage system of the Mac with security problems.
See attached image (in Italian)
Roberto
|
Thanks Ladislav,
Osx environment
After updating to 0.35 I noticed that the setting program loses the storage of passwords for services such as EQSL, etc.
But the strangest thing is that it requests them from the password storage system of the Mac with security problems.
See attached image (in Italian)
Roberto
|
Hello Wolfgang,
Thank you for your email. I do my best? to make changes so that it does not affect the clarity of QLog
I think Bandmap change will raise a wave of different opinions. I personally used following Bandplan document
Based on this document, I understand the gap 14070 - 14089 and 14089 - 14099 and 14099 - 14101 as reserved for DIGI modes. Therefore the QLog identifies this as the DIGI mode segment. QLog Digi mode segment is divided into FT8 segment and the rest of DIGI modes (rtty FT4 etc).
Regards Ladislav
Hi Ladislav,
Thank you very much for the new version 0.35 and your work on the software in general. The visualisation of the mode segment in the bandmap looks very good and discreet.
Where do the gaps in the blue bars in CW mode on some bands come from? In the 80m band, for example, from 3.573 kHz to 3.5750 kHz. One of these gaps can be seen in the Wiki image (20m band).
The other additions and changes are also sensible and very well done.?
73, Wolfgang
DL2KI
|
Hi Ladislav,
Thank you very much for the new version 0.35 and your work on the software in general. The visualisation of the mode segment in the bandmap looks very good and discreet.
Where do the gaps in the blue bars in CW mode on some bands come from? In the 80m band, for example, from 3.573 kHz to 3.5750 kHz. One of these gaps can be seen in the Wiki image (20m band).
The other additions and changes are also sensible and very well done.?
73, Wolfgang
DL2KI
|
Let me inform you that a new QLog release v0.35.0 is finished. Changelog: - [NEW] - Added Rot Interface PSTRotator Network - [NEW] - Added QSO/QSL Since option to eQSL Dialog - [NEW] - Bandmap - Current Mode segment visualisation - [NEW] - CW Console - Added Word/Whole mode switch - [NEW] - Added Callbook Profile Image Widget - [NEW] - ASCII conversion based on Text-Unidecode/iconv algorithm (issue #316 #350) - [NEW] - ITU/CQ Zones can be defined in Station Profile (issue #358) - [CHANGED] - Spacebar is used as a focus changer for fields where space is not allowed - [CHANGED] - Focus does not select text in the input fields - [CHANGED] - Force XCB under Linux Wayland - [CHANGED] - Bandmap - Added Callsign/Freq/Mode to tooltip (issue #355) - Fixed incorrect ADIF date format for clublog_qso_upload_date (issue #342) - Fixed The last name from Callbooks queries (issue #346) ? Changelog: WIKI:
|
Re: Importing QSOs into Qlog & LOTW
No worries Ladislav. I should have noticed that myself!?
73? Mark ZL3AB?
Hi Mark,
I'm sorry, I completely forgot one thing. I don't know how I could have forgotten about it, but there is also a simple procedure. When exporting, you just click the option to Include QSOs with Sent Status No, as shown in the image below. Regards Ladislav
st 24. 4. 2024 v?3:15 odes¨ªlatel Mark ZL3AB via <markzl3ab= [email protected]> napsal: Thanks Ladislav for the explanation.?
I had another go at this and manged to import and then upload some QSOs to LOTW.? This is the process I followed.
1. Export an ADIF file from my contest logger (in my case N1MM).
2. Import the file into Qlog.? The QSOs will appear in the QSO table.
3. Add the field LoTWs to the QSO table (you only need to do this once).? To do this:
(a) highlight a QSO in the table
(b) right click on it and select "Column Visibility"
(c) go to the "QSL & Callbook" tab
(d) tick the box for "LoTWs"
(e) close the Column Visibility box
The LotWs field should now appear at the end of the QSO table.
4.? If you have uploaded your file you should see that LotWs is set to "N" for all of your contest QSOs.
5.? Highlight the first QSO and then hold down the "shift" key and click on the last QSO for the file you up loaded.? This will highlight all the QSOs from your contest file.
6. Go to one of the QSOs and left click on the "N" in the LoTWs field. Click on the drop down button at the right of the field and you will be presented with several options.? Choose "Queued" and hit "enter". ?
This will change the LoTWs field for all the highlighted QSOs to "Queued".
7. Choose LOTW from the Service Menu and click on "Show Selection". Your contest QSOs will appear in the list (along with any other QSOs that are marked "queued".? Then upload via TQSL following the usual process..
By the way there is a typo in the LOTW wiki page.? The second paragraph says:
"For successful uploading to LoTW it is not necessary to have the utility installed..."
It should say:
For successful uploading to LoTW it is necessary to have the utility installed..."
73
Mark ZL3AB
|
Re: Importing QSOs into Qlog & LOTW
Hi Mark,
I'm sorry, I completely forgot one thing. I don't know how I could have forgotten about it, but there is also a simple procedure. When exporting, you just click the option to Include QSOs with Sent Status No, as shown in the image below. Regards Ladislav
st 24. 4. 2024 v?3:15 odes¨ªlatel Mark ZL3AB via <markzl3ab= [email protected]> napsal:
Thanks Ladislav for the explanation.?
I had another go at this and manged to import and then upload some QSOs to LOTW.? This is the process I followed.
1. Export an ADIF file from my contest logger (in my case N1MM).
2. Import the file into Qlog.? The QSOs will appear in the QSO table.
3. Add the field LoTWs to the QSO table (you only need to do this once).? To do this:
(a) highlight a QSO in the table
(b) right click on it and select "Column Visibility"
(c) go to the "QSL & Callbook" tab
(d) tick the box for "LoTWs"
(e) close the Column Visibility box
The LotWs field should now appear at the end of the QSO table.
4.? If you have uploaded your file you should see that LotWs is set to "N" for all of your contest QSOs.
5.? Highlight the first QSO and then hold down the "shift" key and click on the last QSO for the file you up loaded.? This will highlight all the QSOs from your contest file.
6. Go to one of the QSOs and left click on the "N" in the LoTWs field. Click on the drop down button at the right of the field and you will be presented with several options.? Choose "Queued" and hit "enter". ?
This will change the LoTWs field for all the highlighted QSOs to "Queued".
7. Choose LOTW from the Service Menu and click on "Show Selection". Your contest QSOs will appear in the list (along with any other QSOs that are marked "queued".? Then upload via TQSL following the usual process..
By the way there is a typo in the LOTW wiki page.? The second paragraph says:
"For successful uploading to LoTW it is not necessary to have the utility installed..."
It should say:
For successful uploading to LoTW it is necessary to have the utility installed..."
73
Mark ZL3AB
|
Re: Importing QSOs into Qlog & LOTW
Thanks Ladislav for the explanation.?
I had another go at this and manged to import and then upload some QSOs to LOTW.? This is the process I followed.
1. Export an ADIF file from my contest logger (in my case N1MM).
2. Import the file into Qlog.? The QSOs will appear in the QSO table.
3. Add the field LoTWs to the QSO table (you only need to do this once).? To do this:
(a) highlight a QSO in the table
(b) right click on it and select "Column Visibility"
(c) go to the "QSL & Callbook" tab
(d) tick the box for "LoTWs"
(e) close the Column Visibility box
The LotWs field should now appear at the end of the QSO table.
4.? If you have uploaded your file you should see that LotWs is set to "N" for all of your contest QSOs.
5.? Highlight the first QSO and then hold down the "shift" key and click on the last QSO for the file you up loaded.? This will highlight all the QSOs from your contest file.
6. Go to one of the QSOs and left click on the "N" in the LoTWs field. Click on the drop down button at the right of the field and you will be presented with several options.? Choose "Queued" and hit "enter". ?
This will change the LoTWs field for all the highlighted QSOs to "Queued".
7. Choose LOTW from the Service Menu and click on "Show Selection". Your contest QSOs will appear in the list (along with any other QSOs that are marked "queued".? Then upload via TQSL following the usual process..
By the way there is a typo in the LOTW wiki page.? The second paragraph says:
"For successful uploading to LoTW it is not necessary to have the utility installed..."
It should say:
For successful uploading to LoTW it is necessary to have the utility installed..."
73
Mark ZL3AB
|
Quick Reminder: Poll Closing Soon!
Hello,
Just dropping a quick note to remind you that QLog's poll regarding the addition of a new widget to QLog is wrapping up soon. Poll Details: - Topic: Should QLog include a widget to display QRZ/HamQTH profile images based on entered callsigns?
Poll link is Github
Polling is happening exclusively on GitHub. While you can share your
comments via email, they won't count towards the final poll results
because I can't track who has already participated in the poll on
GitHub.
Regards Ladislav
|
Re: Importing QSOs into Qlog & LOTW
Hi,
I will try to answer your questions.
1) import from N1MM. N1MM exports only a very limited number of ADIF fields. It is logical, because it is primarily a contest log where it is not expected that a lot of information would be entered.?If such an ADIF file is then imported into other applications, a lot of information is either missing or replaced by the default value. And so it is in the case of the LOTW queue parameter. This field is defined in the ADIF specification with a default value N. This means that if it is not present in the ADIF file, then it must be set to N.
Unfortunately, it is not possible to let the user choose default values for each field during import, because there are a large number of them and the process would become confusing for operators
2) Batch field update is already implemented. QLog , select QSOs and use the context menu Edit ("If more than one row is selected, these rows are changed so that the value of the edited item is used for all selected records"). Keep in mind that there is no UNDO function. So be careful and try it first on a small number of QSOs.
Regards Ladislav
?t 18. 4. 2024 v?8:20 odes¨ªlatel Mark ZL3AB via <markzl3ab= [email protected]> napsal:
Hi Adam
The logging program is N1MM logger.? It is a dedicated contest
logger so doesn't have any general logger extra like direct LOTW
uploads.?
One work around would be to upload the ADIF I export from N1MM
directly through TQSL first and then put it in Qlog, but the
additional functionality would be nice.
73
Mark
On 18/04/2024 09:24, Adam VK4IM via
wrote:
Hi Mark
Just an observation.
I wonder if this is something that needs to be set in your
logging program?
Having said that, being able to change fields ( any field) in
bulk in QLog would be a handy feature.
?Good morning
When you enter a QSO in Qlog LOTW is defaulted to "queued"
so that the QSO is automatically uploaded when you do your
next LOTW upload.
However I have discovered that when you import QSOs into
Qlog, in my case from my contest logger, the default setting
for LOTW is "no" and so those QSOs don't automatically get
uploaded to LOTW.? Therefore and unless I am missing
something, you have to manually change each QSO to "queued"
before you do your upload.
Is there a way to either choose/highlight all the imported
QSOs and make a bulk change from "no" to "queued" or perhaps
be prompted to do so when you import the QSOs?
73
Mark ZL3AB? ? ? ? ?
--
Member ZL3X The Quake Contesters
|
Re: Two callsigns sharing statistics
Hi,
it is not possible to cover all use cases and describe them in the documentation. It is not entirely clear from your description what you expect from QLog if you have a new callsign. But Qlog itself is ready. Just create new Station profiles and try experimenting a bit with Qlog.
Regards
Ladislav
toggle quoted message
Show quoted text
On Tue, Apr 16, 2024 at 01:21 PM, Juanma - EA3IFV wrote:
In case an op gets a new callsign, is there any document explaining how to have both logbooks and consider them both for cluster alerts, awards and statistics?
|
New user and very impressed
Just installed today and integrated into WSJT-Improved by DG2YCB, JTAlert as well as LotW/QRZ et.al. and I'm impressed enough to make it my main mom-contest logging program. Well done.
|
Re: Importing QSOs into Qlog & LOTW
Hi Adam
The logging program is N1MM logger.? It is a dedicated contest
logger so doesn't have any general logger extra like direct LOTW
uploads.?
One work around would be to upload the ADIF I export from N1MM
directly through TQSL first and then put it in Qlog, but the
additional functionality would be nice.
73
Mark
On 18/04/2024 09:24, Adam VK4IM via
groups.io wrote:
Hi Mark
Just an observation.
I wonder if this is something that needs to be set in your
logging program?
Having said that, being able to change fields ( any field) in
bulk in QLog would be a handy feature.
?Good morning
When you enter a QSO in Qlog LOTW is defaulted to "queued"
so that the QSO is automatically uploaded when you do your
next LOTW upload.
However I have discovered that when you import QSOs into
Qlog, in my case from my contest logger, the default setting
for LOTW is "no" and so those QSOs don't automatically get
uploaded to LOTW.? Therefore and unless I am missing
something, you have to manually change each QSO to "queued"
before you do your upload.
Is there a way to either choose/highlight all the imported
QSOs and make a bulk change from "no" to "queued" or perhaps
be prompted to do so when you import the QSOs?
73
Mark ZL3AB? ? ? ? ?
--
Member ZL3X The Quake Contesters
|
