some observations and suggestions
5
Not really looking for any bug fixes or new features, just some observations and suggestions. Qlog 0.37.2 (built from source, yes I need to upgrade) O/S Manjaro Linux KDE HP Laptop 8th gen i7 with 32 gb RAM, 1Tb NVMe SSD Log about 70K contacts 1. The LoTW upload timeout is very short, am on a slow sat link here and after maybe 5 seconds I get a pop up saying LoTW is not responding, something like 15-30 seconds would be better to allow for slower links? Though seems this might have actually been fixed in some later builds? Just an observation. 2. Clublog, EQSL and LoTW uploads are great, and fast. However QRZ (and HRDlog) remains a "one at a time" affair. And I'm guessing that's a limitation on their API? Would it be possible to have some way to export an ADIF for QRZ and then mark the queue as done? I'd like to retain some way to know whats been uploaded and what hasn't. LoTW, EQSL and CLublog are all bulk which is cool. Or if QRZ at least could be uploaded in real time? Am less worried about HRDLog. I try to do QRZ every other day but sometimes take a very long time for say 400-500 QSO. 3. If I do a largish upload to LoTW (say over 200) I nearly always get a pop up from TQSL saying am I sure I want to re-upload a QSO that has already been uploaded. It's nearly always just one QSO (but today was 3), and doesn't seem to do this for smaller uploads. So I usually click the box saying yes do it again (just in case) and in the meantime I get QLOG saying TQSL is taking too long ;-) Again, the timeout thing seems to be fixed since I wrote this. 4. When I do a LoTW download and matching it seems it doesn't match anything that's double logged (dupes). When I did a download today it said it could not match about 8 QSO. I checked and they were all logged twice (for whatever reason). Not a big deal but it might confuse some people. Maybe I just weed out the dupes properly ;-) thanks again for all your work on this 73 Phill C21TS / FK1TS / 3D2TS
|
Rotor Control Error in Linux only
6
Hy-Gain DCU-3. Works perfectly with QLog in Win10. Settings 4800, 8,N,1 Com 8 In Linux Mint 21.2 Victoria base: Ubuntu 22.04 jammy get error. Settings 4800 8,N,1 ttyUSB0 Have tried with Flow Control None, Software. Hardware. Rig Control working fine in both Win10 and Linux. Win10 Settings Linux Settings
|
Data sharing
4
I have dual boot PC with multiple hard drives. One of the HD¡¯s has Linux Mint, and another has Windoze 10. I use Linux 90% of the time. I have QLog installed on both Linux and Windoze 10. Is there a way to > share< my Qlog configuration settings, and logbook data between the 2 operating systems? I¡¯m currently sharing the log data of AC Log (installed with WINE on Linux, and a normal installation in Windoze) by using a separate USB connected drive that is accessible by both operating systems. WW4DX
|
QSO Table Column Width Does Not Stick
4
Hi Ladislav I notice when I set the column widths in the QSO table, the columns do not stay as intended (or as set). My observation is that that any text contained in the field affects the width of the column after entering a QSO into the log and pressing enter. I'm not sure this should happen given that most people will want specific fields to display at a specific width to suit their operating style and screen size The same problem occurs both within a Windows 11 install and also on Linux Mint, so I don't think its operating system specific. Refer screen grabs below for reference Cheers Adam, VK4IM
|
WSJT-X
4
I've noticed one oddity since 0.38 when I engage in a contact with a station on WSJT-X I see the callsign lookup in qLog like before but then it clears away if I have never worked the station before, but if I have worked them it keeps the lookup like I think it did before. Hope that makes sense. Michael, AA5SH
|
Several questions/comments
11
Hi, I installed QLog since I was looking for a logger on Linux. I installed the latest flatpack version (v0.38). It's running on an AMD Ryzen 7 4800U with Radeon Graphics and 32GB RAM. Linux flavor is Tuxedo OS 3 v22.04 (jammy). Installation was straightforward, setup as well. I exported one of my logs from my current logger into an ADIF file which I imported into QLog. Took a while but all data showed up. It now holds some 300k Qs. I expect others to have more. 1. Start up now is slow: Can loading the complete log at start-up be made an option or is it relying on having all data in memory while running? 2. When entering a callsign in the callsign field, it "hangs" for a short while to display all previous contacts and until it moves to the RST field. I have no radio connected yet but would this behavior influence the start of the CW transmission? 3. Wenn hitting Ctrl-N, it takes a while until the reload is done and a new callsign can be entered. That's why I'm asking for the option in 1) -> It would make working in a pile-up a not very easy task. 4. When getting to the RST field, the cursor sits behing the numbers. As I'm the guy handing out real reports (except during contests), I need to go back, delete and enter the right value and move on to the next field. Any chance to preselect the S value in order to be able to correct the value in one hit and move on? 5. Stats (Logbook/Statistics): Some real nice stats, some are displayed really fast but the "Show on map" Graph Type takes an extremely high amount of time. If you resize the window, it will again take extremely long. That's why I indicated my PC setup. Am I on the low side of resources needed? It's all SSD, BTW. 6. Filter by Band is fine, I'm also looking for a Filter by Mode. Did I miss it or could it by done? There's usually not running going on on this PC as I'm using it only to surf the Internet and do my emails. Sri if I missed some answers to my questions in the wiki but I did not see them, That would be my bad. 73 Norby
|
Release 0.38.0 bug????
34
Interesting phenomena with the newest release when using with the Yaesu FTDX101MP. Never experienced this before, however now when I click on a DX spot, and the rig switches to the band and frequency, often the sideband (USB / LSB) is not correct for the band. For example, if I click on a spot from 20 meters, it often switches the rig over to LSB. On 40 meters often to USB. If I clink that spot several times, Qlog finally switches to the correct sideband. Did not behave like this prior to the update, I haven¡¯t changed any settings after the update and the FTDX101MP continues to operate fine with AC Log. 73 WW4DX M Harrison
|
QLog Service Functionality Suggestion
4
I have a suggestion for the "Service" finctionality of QLog. Not being a programmer, I am not even sure this is possible, but if it is, it would be very welcome addition to QLog. The Service functionality currently has 5 logbook sites from which to choose. In my case I use all five. In order to update all five sites, and download any QSL's, my normal routine is thus; 1) Service > LoTW > QSL's Download > Close > Show Selection . Upload > OK > Close, 8 mouse clicks. Then I run the same routine for eQSL, another 8 mouse clicks. I then run a 6 mouse click routine each for ClubLog, HRDLog, and QRZ. All in all 32 mouse clicks. This is a bit excessive. Would it be possible, in the Settings Menu, to select which books you use and therefore those would be displayed in a single drop-down under Service, and all five sections could simply give an indication of completion rather than another button to press. This would certainly decrease the amount of windows and mouse clicks. I hope this is clear but if not I can explain further. DE: Mike, K3SNO
|
Release 0.38.0
6
Let me inform you that a new QLog release v0.38.0 is finished. Changelog: - [NEW] - Logbook - Added Send DX Spot to the QSO Context Menu - [NEW] - DX Filter - Added Dedup Time/Freq difference setting (@aa5sh) - [NEW] - Rig Setting - Added RTS/DTR PTT Type support (issue #353) - [NEW] - Bandmap - Scrollbar position is saved per band (issue #415) - [NEW] - New Contact - Added a dynamic value completer for SIG field (issue #425) - [NEW] - Awards - Added SOTA/POTA/WWFF (@aa5sh issue #311) - [NEW] - Awards - Added Not-Worked Filter - [NEW] - New Contact - Added Long Path Azimuth info - [NEW] - POTA Fields allow a comma-delimited list of one or more POTA Refs - [NEW] - WSJTX tunes freq/mode like Rig if rig is disconnected - [CHANGED] - Alert Widget is a Dock Widget (issue #399) - [CHANGED] - QLog adds more information from callbook for WSJTX QSOs (issues #403 #405 #420) - [CHANGED] - File Open dialogs are not a native dialog under Linux (issue #427) - [CHANGED] - Profiles transferred to DB - [CHANGED] - LOV last_dates transferred to DB - [CHANGED] - DX Cluster - Login Callsign is always the base Callsign - [REMOVED] - Setting DXCC Date - Fix for MacOS Layout Geometry Restore (@aa5sh) - Fixed TQSL does not block GUI thread - Fixed MacOS build process (@aa5sh) Changelog: https://github.com/foldynl/QLog/releases/tag/v0.38.0
|
Logbook Profiles
2
I have a few different callsigns (RSL's), is it possible to segregate logs dependant on callsign used similar the the profile feature of CQRLog or log into different SQL databases/tables? -- 73'd de Dave, G8FXM
|
#featurerequest
6
#featurerequest
Amazing logging program!!!! Any way to display the long path in the info screen?
|
Poll - Using Callbook's QTH information for Digi modes - last 3 day
Hello, If you want to influence QLog, you have the last 3 days to accept or reject a feature request. The poll is open until 23/8, and the question is: Should QLog use Callbook's QTH information and save it when using external QSO sources (WSJTX, FLDigi, etc.) when matching the callsign and partially matching the gridsquare (e.g., JN70 from QSO and JN70AA from the callbook)? Github link here. Regards Ladislav
|
Multiple call signs in alert
3
#featurerequest
Hi, Is it possible to add multiple call signs to one alert? If not, it could be useful for award hunting, current dx expeditions hunting etc. etc. -- ___ Slav, EI6KW, SP3RXO https://www.hamqth.com/ei6kw
|
Antenna Follows Band
#featurerequest
Hi In settings under the equipment section it is possible to enter antenna profiles. Thank you. When entering contacts in the main window there is an option to select the antenna in use under the "My Station" tab. My request is as follows: Please provide an option (check box) to allow the antenna to follow the radio. Having a check box to "Opt In" will allow greater scope for operator efficiency. To clarify: When the radio is on 10m then the antenna in "My Station" automatically follows and reads the correct antenna from the "Antenna Profiles" section in setup. The same occurs when changing to any other band. 73 Adam VK4IM
|
#featurerequest SWL and USERDEF fields options
8
#featurerequest
Hi all, this is my first post in QLog mailing list. I've just trying it and it looks very well. I'd like to ask for a couple of features to take into account for future releases, if it was possible: - SWL check (or whatever seemly) in a QSO info - USERDEF fields support Thanks in advance and congratulations for your work.
|
Release 0.37.2
Let me inform you that a new QLog release v0.37.2 is finished. Changelog: - Fixed Field QSL Send Via should be retained (issue #413) - Fixed Set rotator position fails if azimuth > 180 (issue #417) - Fixed Windows State/Size does not save in case of fullscreen (issue #418) - Fixed Significant rounding during azimuth calculation (issue #422) - Updated Simplified Chinese translation - Updated Spanish translation - Added Italian translation (thx IK1VQY) Changelog: https://github.com/foldynl/QLog/releases/tag/v0.37.2
|
Distance unit (km/miles)
8
Hi .... How do I set it up to use km in the 'Distance', at the moment it show miles.... 73" OZ1CT Ben
|
TCI connection to my Thetis
4
Hi Ladislav I am trying to get Qlog to connect to my Anvelina SDR running TCI, I use Thetis and have set it up as you can see in picture but when I try to "Connect RIG" it give me this error: any hint from you what I do wrong ??? 73" oz1ct Ben
|
Problem memorizing the qth FT8 mode
7
Ladislav good afternoon, I realized, only now, that when I make a QSO the qth field is decoded, but not reported in the log See attached image to understand better 73 Robert IU2NUB (how can I complete all the QSOs already registered?)
|
Primary and secondary callbook info
6
In the setup we can set primery and scondary callbook for callsign querry. It's fine and working good. But it could be fine to have displayed info from which callbook, primary or secondary, data comming. Just short text, e.g. qrz or hamqth. Slav, EI6KW / SP3RXO
|