I just installed Qlog and am trying to get it to connect to my rig, an Icom 7300 using Hamlib.? No matter how many different combinations I try, I can¡¯t get it to work and always get some error.? I can¡¯t find anything on the net about how to set it up really. The documentation is very general with no specifics how to¡¯s or examples so I¡¯m stuck.? Below is my setup.? In WSJTX, on the radio tab, for the Rig selection, I have FLRig FLRig and everything works fine with it.? So I¡¯m very confused as to why QRLog isn¡¯t working with the same selection. If anyone has any ideas or could point me in the right direction I would much appreciate it. Thanks.
I just installed Qlog and am trying to get it to connect to my rig, an Icom 7300 using Hamlib.? No matter how many different combinations I try, I can¡¯t get it to work and always get some error.? I can¡¯t find anything on the net about how to set it up really. The documentation is very general with no specifics how to¡¯s or examples so I¡¯m stuck.? Below is my setup.? In WSJTX, on the radio tab, for the Rig selection, I have FLRig FLRig and everything works fine with it.? So I¡¯m very confused as to why QRLog isn¡¯t working with the same selection. If anyone has any ideas or could point me in the right direction I would much appreciate it. Thanks.
I'm not a Linux whiz, so I feel it's best I leave well enough alone. QLog is working great, and it's no big issue to press a preset on the DCU-3, instead of clicking an icon.?
Could you please send me a screenshot of the popup that appears for point 1?
'''
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.
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 ;-)
Please, could you verify if the ttyUSB0 port is not shared with some other application under Linux (or your RIG setting does not contain ttyUSB0 port)?
QLog accesses HAMLIB devices both under Win and under Linux.The only difference may be in the Hamlib version, but according to the screenshot you have at least the same driver version.
A good practice under Linux is to use USB port path to Device-ID file because ttyUSBx ports can be assigned randomly.?
Example: my IC7300 has always Device-ID path /dev/serial/by-id/usb-Silicon_Labs_CP2102_USB_to_UART_Bridge_Controller_IC-7300_03018006-if00-port0
Unfortunately, currently there is only one reliable way to share QSOs - export/import QSOs.All the others (folder relinking and sharing, etc.) can lead to unexpected errors.
But I am making some changes so that at least the database itself can be shared without side effects.
Regards
Ladislav
?t 19. 9. 2024 v?13:29 odes¨ªlatel Michael Morgan via <cmorgan13=[email protected]> napsal:
On my Mac and Windows I actually redirect the data folder to my Dropbox using symbolic links.? I only use it on one computer at a time and insure it is ok.? But I use commands similar to this once I copied the folder over.
That takes care of database.? For the settings they are in a different location.? Once I got my layout¡¯s and what not the way I like it I just copied over the preference file to each of my Macs.? I just had to re-add my passwords.? But it got me a starting point on each of them once I tweaked my layout the way I like it on my primary Mac.
Here are where all the paths should be set on the various OSs:
Michael, AA5SH
On Sep 19, 2024, at 6:01?AM, WW4DX via <WW4DX=[email protected]> wrote:
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.
QLog does not upload the QSO to LoTW directly. Instead, the TQSL utility is used for this purpose. The upload itself is managed by TQSL, but QLog has an internal timeout for executing external utilities. I will try to modify this timeout.
2) QRZ upload.
Unfortunately, it is a limitation of QRZ. API supports one-by-one upload only. I asked the QRZ's support about the batch upload, because it was mentioned in the specification that it is possible to use it but it didn't work and instead of it being fixed, it was deleted from the specification.
3) It can be related to the internal timeout from point 1.
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 ;-)
On my Mac and Windows I actually redirect the data folder to my Dropbox using symbolic links. ?I only use it on one computer at a time and insure it is ok. ?But I use commands similar to this once I copied the folder over.
That takes care of database. ?For the settings they are in a different location. ?Once I got my layout¡¯s and what not the way I like it I just copied over the preference file to each of my Macs. ?I just had to re-add my passwords. ?But it got me a starting point on each of them once I tweaked my layout the way I like it on my primary Mac.
Here are where all the paths should be set on the various OSs:
On Sep 19, 2024, at 6:01?AM, WW4DX via groups.io <WW4DX@...> wrote:
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.
I would also find this useful in a similar way that CQRLog allows the use of an external MySQL database as an alternative to the integral SQLlight dB. You coul then set up separate QSO tables for the different callsigns you may own as well as share the database across multiple machines.
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.
I'm not sure its a fault of QLog though because if I switch on the rotator and radio BEFORE switching on the computer it works. But if I do it the other way round it glitches
I'm a newby with Linux so I may be wrong but it's worth trying. Also I had to add myself the the tty and dialout group within Linux.
Cheers Adam, VK4IM
19 Sept 2024 18:16:49 WW4DX via groups.io <WW4DX@...>:
I prefer to set the width manually and have it stay that way rather than having it automatically adjust to the content. I hope other users like that concept and approve of the change if you make it.
El dom, 15 sept 2024 09:59, ok1mlg via <ok1mlg=[email protected]> escribi¨®:
Here I would say that it is not an issue but a feature.
With each table update, the width of all columns is evaluated and set according to the longest item in the given column. If this shouldn't change and depends on the operator, it's a simple change. I'll try to change it and we'll see how many people on the other side will be unhappy.
That's an interesting side effect. It shows that a developer can never anticipate everything down to the last detail. Thanks for sharing your experience.
so 14. 9. 2024 v?14:26 odes¨ªlatel Michael Morgan via <cmorgan13=[email protected]> napsal:
Ok I found my answer.? I had enabled 'QSO Wiping' on my Rig setup for some reason and in WSJT-X I had 'Fake It' enabled for Split.? So when I would transmit it changed the frequency and wiped the QSO data.??
Here I would say that it is not an issue but a feature.
With each table update, the width of all columns is evaluated and set according to the longest item in the given column. If this shouldn't change and depends on the operator, it's a simple change. I'll try to change it and we'll see how many people on the other side will be unhappy.
Ok I found my answer.? I had enabled 'QSO Wiping' on my Rig setup for some reason and in WSJT-X I had 'Fake It' enabled for Split.? So when I would transmit it changed the frequency and wiped the QSO data.??