Hello Robert,
Many thanks. I do my best to make QLog useful.
I would answer your question. It is necessary to distinguish which services are designed as QSL-exchange services and which are Online Logs. And that is the case of the mentioned services. The QRZ service isn't primarily a QSL service. That means confirmation
from this service isn't officially recognized as a QSL. On the other hand,
LoTW (eQSL) and Paper QSL are valid QSL
methods. So, if you see LoWT, eQSL and Paper in the QSL tab of the QSO
Detail tab, then it should indeed be there. If you want to see if you've
uploaded a particular QSO to QRZ, then I recommend adding this column
to the QSO listing window.
Regards Ladislav
p¨¢ 16. 2. 2024 v?17:09 odes¨ªlatel Robert Bower < frrobert@...> napsal:
Good morning,
I just installed QLOG 0.32 via the Ubuntu PPA.? I got everything configured and really enjoyed using it last night.?
I used the software to upload my logs to both LOTW and QRZ.? If I then click on a log entry that has been uploaded followed by clicking on the QSL tab it shows the log has been uploaded to LOTW but there is no place for QRZ.? The tab lists paper, LOTW, and eQSL.? Is that by design or am I missing something?
Thanks
--
Thanks,
Robert
W9WRB
WRPH745
|
Good morning,
I just installed QLOG 0.32 via the Ubuntu PPA. I got everything configured and really enjoyed using it last night.
I used the software to upload my logs to both LOTW and QRZ. If I then click on a log entry that has been uploaded followed by clicking on the QSL tab it shows the log has been uploaded to LOTW but there is no place for QRZ. The tab lists paper, LOTW, and eQSL. Is that by design or am I missing something?
Thanks
--
Thanks,
Robert
W9WRB
WRPH745
|
Many thanks Ladislav,
I had a long password set, changed it to something shorter on ON4KST and all is ok again now.
--
73's de Dave, G8FXM
|
theoretically there is a limit for storing passwords, but in practice it is not justified to use strong passwords for this service, because all passwords are sent unencrypted to ON4KST . Unfortunately, as far as I know, even https is not turned on for this service.
If I'm wrong, please correct me, that the only access is unencrypted telnet and http, where you send passwords in plaintext form.
Getting back to your problem. I have tested the 25 chars (including special chars) password without any problem. Theoretical limit seems to be around 2500 chars, which is the limit of the Windows Credential Store. If you got a connection refused, it seems to be an issue with network connection. Keep in mind that QLog uses a telnet connection type for ON4KST. Try to check if the telnet port (23) is not blocked for outgoing traffic by your firewall or internet provider.
ne 11. 2. 2024 v?20:22 odes¨ªlatel Dave, G8FXM < webmaster@...> napsal:
On Sun, Feb 11, 2024 at 05:48 PM, ok1mlg wrote:
Hi Ladislav,
I removed version 0.30 and installed version 0.32 and that did the trick, it now opens normally. Many thanks.
I have another issue, I changed my ON4KST Chat password and now I cant log in through QLog, it keeps saying connection refused by host, but I can log into to ON4KST directly.
Is there any limit in QLog on password length maybe?
?
--
73'd de Dave, G8FXM
|
On Sun, Feb 11, 2024 at 05:48 PM, ok1mlg wrote:
Hi Ladislav,
I removed version 0.30 and installed version 0.32 and that did the trick, it now opens normally. Many thanks. I have another issue, I changed my ON4KST Chat password and now I cant log in through QLog, it keeps saying connection refused by host, but I can log into to ON4KST directly. Is there any limit in QLog on password length maybe? ? -- 73'd de Dave, G8FXM
|
Hello Dave,
The good news is that I CANNOT replicate it. I installed QLog in 0.30 and upgraded to 0.32 with no issue. This means that QLog is not incorrectly packed.
In your case, I would try to uninstall and install it again. You don't have to worry about your data. QLog does not delete user data when uninstalled. So, after uninstalling and installing a new version, you will see your data again.
Regards Ladislav
ne 11. 2. 2024 v?16:03 odes¨ªlatel Dave, G8FXM < webmaster@...> napsal:
I just tried installing 0.32 over my existing 0.30 version and I get this error:  Qlog doesn't work at all now, anyone know how \I recover from this? -- 73'd de Dave, G8FXM
|
I just tried installing 0.32 over my existing 0.30 version and I get this error:  Qlog doesn't work at all now, anyone know how \I recover from this? -- 73'd de Dave, G8FXM
|
Let me inform you that a new QLog release v0.32.0 is finished.
Changelog:
- [NEW] - Added Rig Interface Omnirig v1 (Windows only)
- [NEW] - Added Rig Interface Omnirig v2 (Windows only)
- [NEW] - Clublog - Added Clear Clublog and reupload QSOs
- [NEW] - Clublog - Added Real-time Insert/Update/Delete
- [CHANGED] - Clublog - Upload callsign is derived from the Current Profile Callsign
- Fixed clang linker failed issue (issue #301)
- Fixed SAT Mode U/U missing (issue #308 PR #309 thanks ea5wa)
- Fixed Multiple QSO selection. Callsigns modified by mistake (issue #310)
- Fixed Callbook query cache is not properly cleared when Callbook settings change (issue #313)
Changelog:
WIKI Changelog:
|
Re: Uploading older, un-exported QSOs
Hi Ladislav,
Thanks for your reply!
You are right the problem was the dialog filter. The newer QSOs were coming from JTDX, where I had a 4 character grid square while the SKCC QSOs had a 6 character grid square. I hadn't realized that was a select button in the upload dialog window, so I didn't think to look for my other QSOs under the other grid square! Now I know to get those aligned and also to check both grid squares for QSOs.
Thanks again, and 73,
Charlie
|
Re: Uploading older, un-exported QSOs
Hi Charlie,
The update to the external service is controlled by the ADIF field "_QSL_SENT" and filter selection in the Export dialog. QLog does not use "last upload" timestamp to determine which QSOs should be sent.
I see two possible reasons 1) Your export contains QSOs with field eqsl(lotw)_qsl_sent = 'N'. Based on ADIF, "N" value means "do not send"
2) Your selection of what to upload (dialog filter) does not match your new QSOs.
73, Ladislav
?t 1. 2. 2024 v?10:57 odes¨ªlatel Charlie Tanksley < KY4UH@...> napsal:
Hi!
I have an upload question. It looks like the eQSL and LoTW upload functionality looks at a ¡®last upload¡¯ timestamp when determining what to upload. Is it possible to have it look at the eQSLs/LoTWs field instead? When I merge my SKCC log in, those QSOs aren¡¯t getting uploaded to these services since I uploaded more recent QSOs without realizing this limitation.
Also: I¡¯m really loving QLog! It¡¯s working really well for me and is so much easier to use than some other Linux loggers. Thanks!
73,
Charlie (KY4UH)
|
Uploading older, un-exported QSOs
Hi!
I have an upload question. It looks like the eQSL and LoTW upload functionality looks at a ¡®last upload¡¯ timestamp when determining what to upload. Is it possible to have it look at the eQSLs/LoTWs field instead? When I merge my SKCC log in, those QSOs aren¡¯t getting uploaded to these services since I uploaded more recent QSOs without realizing this limitation.
Also: I¡¯m really loving QLog! It¡¯s working really well for me and is so much easier to use than some other Linux loggers. Thanks!
73,
Charlie (KY4UH)
|
Dekuji Lado !
To mne pomohlo.
55&73 Gerd
|
Hello,
You can add your incoming paper QSL by following way:
1) Find the QSO in QLog 2) Double click on the QSO 3) QSL Tab 4) Manage QSL Card 5) Import the scanned QSL card(s) and edit Received data and Status for Paper QSL
You the find the same description with pictures here -
Regards Ladislav
|
Hi there!
Can someone help me ? How can i add incoming paper QSL`s to my logbook ?
best regard 55&73 de Gerd OE3ASA
|
Happy New Year
Let me inform you that a new QLog release v0.31.0 is finished.
Changelog:
- [NEW] - DXC - Improved Mode recognition
- [NEW] - DXC - Switch Rig mode based on DXC Spot Mode (issue #217)
- [NEW] - DXC - Added Spot Country Column (issue #273)
- [NEW] - DXC - Added Menu for server management
- [NEW] - DXC - Added Auto-connect to server
- [NEW] - DXC - Added Keep QSOs Context Menu
- [NEW] - DXC - Added Clear QSO Context Menu
- [NEW] - DXC - Added support for SH/DX response parsing
- [NEW] - DXC - Added support for username, password for connection
- [CHANGED] - DXC - Commands Combo changed to function button with selectable function
- [CHANGED] - DXC - DX Spot is prepared via DXC Command Line, Remark dialog was removed
- [NEW] - Online Map - IBP station double-click tunes freq and switch Rig mode
- [NEW] - Main Window - Current profile name is shown (issue #282)
- [NEW] - Import - Details can be saved to file (issue #284)
- [NEW] - Added Simplified Chinese translation (PR #285 thank BG7JAF)
- [NEW] - New Contact - Enter saves QSO if QSO time is running (issue #293 - partial)
- [NEW] - New Contact - Callsign Enter event saves QSO if no Callbook is active - Pileup Mode (issue #293)
- [NEW] - RIG Widget - RIT/XIT are displayed with user-friendly units (issue #294)
- [CHANGED] - SAT List download - Shortened download period for SAT list from 30 to 7 days
- Fixed ADI Import is too slow (issue #270)
- Improved Import/Export Performance
- Fixed Missing Satellite Mode SX (issue #291)
- Fixed QSO Detail - Issue when Sat-Name field was always disabled
- Fixed RPM build - Installed (but unpackaged) metainfo file issue
Changelog:
WIKI Changelog:
|
QLog does not directly support printing a QSL cards. QLabels and other software do a great job and there is no need to integrate everything into QLog if you have an alternative that is specialized for this task.
|
Ok. I'll work around it.
But How can I print QSL cards with QLog?
|
I am afraid that this will not be a part of QLog, because it is a rather specific function that can be derived during the post-processing of the exported file. It also depends on what software you use for printing the QSL cards.
I'm not a specialist in GLabes, but if there are no macros, then it is necessary to filter the export through some "custom" script that will add required fields depending on the QSO data. In your case, depending on the QSLr field. This can be done either?naively with AWK or cleverly with Python.
|
Yes.
I want to print QSL card labels and it's a good practice to make the maximum available QSOs per QSL. In the attached example is 3.
If I print a QSL and I've not received yet a QSL card for those QSOs, I'll write PSE QSL in the QSL card.
If I print a QSL and I've received a QSL card for one of those QSOs, I'll write TNX QSL in the QSL card.
See images attached. We can even do it better doinf a PSE/TNX for every QSO in the QSL.
Unfortunately GLabels don't allow macros or other field value management.
I'm trying to write e python3 script to reach the goal but it's not simple for me (I'll try asking to ChatGPT :D )
It will be nice to have a solution "ready to print"... but a file well formatted for simple GLabels use is quiet a good solution.
73 de Leo IZ5FSA
|
Hi Leo,
I'm not sure if I understood that correctly. Do you want to have a field where the text will be static?
QLog exports one QSO per one CSV line. The export is done by selecting the CSV format and selecting the requested QSO columns that you want to have in this file. There is no possibility to have the pre-defined static text in this CSV (only QSO fields are possible), because you can put the static text in your GLabel template.
Please, could you send me an example, what you exactly request? Sample CSV file with your comment would be perfect.
Regards
Ladislav
|
Dave, G8FXM
Gerd
