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
|
Hi.
I'm using QLog (flathub version on Debian Trixie) and I think it's a very good HamLog.
I've searched info about QSL cards facilities and I've found export dedicated function.
I'm using Glabels and I wonde if there is a way to have a field with TNX or PSE QSL.
It will be extremely useful, as it will be important having multiple QSOs with the same callsign on the same CSV record to print multi QSo labels.
Thank you for suggestions for solutions or turnarounds...
73 de Leo IZ5FSA
|
Hi Dave, nah it's a separate window, just very close and same size. I always use something separate to control the rig that can show me what's going on (ALC, Power, SWR etc) as I am sometimes not in front of the PC. But also mainly because my main rig here is an FT-891 which shows very little in the way of what's going on with the rig on the very small LCD screen. It just means I can see what's going on in one place as I mostly do FT8, and for FT8 I always do the same setup. Rig controlled by Flrig whether on Windows or Linux (I have a Win 10 PC and Manjaro laptop). JTDX etc connected to Flfig. Gridtracker connected to JTDX etc for real time log uploads. Logbook connected to Gridtracker for logging and to get callsign info etc. On Windows thats Log4OM (without Gridtracker) and Linux Qlog for now. Sounds a bit complex but it works well.
73 Phill C21TS
|
Re: Club Membership Lists
It is not important to be updated regularly (via CRON), but rather that it is published with the last update date information.
I believe it is not a good idea to add this information to the file header, as it could potentially disrupt applications that download the file. On the other hand, if you add it to the website (), the information may be lost. The best approach in this situation would be to include the last update date information on the page . The date format can be adjusted based on your preferences.
|
Re: Club Membership Lists
OK let me know your preference, location, format etc and I'll see what I can do.
Presently this file is manually created as and when I think of it. I mean to automate the file creation via a daily or weekly CRON job.
--
73'd de Dave, G8FXM
|
Re: Club Membership Lists
I don't know if you are able to change it, but one of the lists without timestamp is the UKMSG memberlist. I use this file () and there is no time information. The missing timestamp information has no impact on QLog updating process, but it would be nice to have this information somewhere.
I don't know if it is appropriate to put this information in the header of the file or to publish it elsewhere, it is not important. What is important is that the information will exist
|
Re: Club Membership Lists
Brilliant, many thanks. If there's anything I can to at my end to improve things just let me know.
--
73'd de Dave, G8FXM
|
Re: Club Membership Lists
I design QLog so that the user does not have to solve these things. QLog regularly, every 7 days, checks if there is any update in the lists on Github (https://github.com/foldynl/hamradio-membeship-lists). If there is a change, new lists are downloaded automatically when QLog is started. The Github repo is also updated once every 7 days, always on Wednesday morning.
Everything is updated automatically, but many Clubs publish data without any timestamp information , so it is not possible to find the latest update directly at the source.
|
Gerd
Phill Hardstaff
Dave, G8FXM