Re: New User QSO Upload Question
Hi,
Check that the Grid Locator declared in WSJTX is the same as in QLog. This happened to me when I started, I had a 6-digit grid declared in QLog and only 4 in WSJTX
73, Diego LU1IDC
Diego Carratini
Hi,
Unfortunately your answer is too general to provide a more precise answer. At a minimum it is good to state the OS and application you are using for WSJTX, because there are many forks of this application.?
I can tell you in general that you need to see if your WSJTX QSOs do not contain any other "own" station callsign or grid. The filter in LoTW Upload filters QSOs according to the settings. Quite often it happens that the operator chooses the wrong settings for export. Keep in mind that QLog sets "own" station callsign and grid from WSJTX QSO, not from QLog's Station profile.
If this is not your case, it would be useful to send an ADI record of your WSJTX QSO and the QSOs that you are able to send to LoTW. Feel free to send me a private email if you do not want to publish these QSOs. Alternatively, you can make some test QSO records.
Regards Ladislav
Hi, new user, just set the program up yesterday.? It looks great and I am impressed with the work that went into it.
?
I do have a problem with doing QSO uploads and I am sure it is something simple.?
?
I loaded the log for my current callsign and was able to use the Service menu to upload to various services so all the user names and passwords work.? TQSL is installed and configured.? I configured WSJTX and made a couple of contacts and I see that they made their way into my logbook successfully.? However, when I try to use any of the services to upload those QSOs, they will not show up in the Show Selection for LOTW for example (or any of the services).? There is nothing to upload even though the QSO's QSL information shows them as queued.? I entered a couple of dummy qsos manually and those do show up in the Show Selection for LOTW when I look to see what is about to be uploaded.? I'm sure there is something simple I am missing here.?
?
When I open each of the QSOs, both fake ones i entered manually and real FT8 QSos, I can see no difference in the QSL tab, they all show queued.
?
Thoughts on where to look to figure this out?
?
Thanks,
?
Tim
KK9T
|
Re: New User QSO Upload Question
Hi,
Unfortunately your answer is too general to provide a more precise answer. At a minimum it is good to state the OS and application you are using for WSJTX, because there are many forks of this application.?
I can tell you in general that you need to see if your WSJTX QSOs do not contain any other "own" station callsign or grid. The filter in LoTW Upload filters QSOs according to the settings. Quite often it happens that the operator chooses the wrong settings for export. Keep in mind that QLog sets "own" station callsign and grid from WSJTX QSO, not from QLog's Station profile.
If this is not your case, it would be useful to send an ADI record of your WSJTX QSO and the QSOs that you are able to send to LoTW. Feel free to send me a private email if you do not want to publish these QSOs. Alternatively, you can make some test QSO records.
Regards Ladislav
Hi, new user, just set the program up yesterday.? It looks great and I am impressed with the work that went into it.
?
I do have a problem with doing QSO uploads and I am sure it is something simple.?
?
I loaded the log for my current callsign and was able to use the Service menu to upload to various services so all the user names and passwords work.? TQSL is installed and configured.? I configured WSJTX and made a couple of contacts and I see that they made their way into my logbook successfully.? However, when I try to use any of the services to upload those QSOs, they will not show up in the Show Selection for LOTW for example (or any of the services).? There is nothing to upload even though the QSO's QSL information shows them as queued.? I entered a couple of dummy qsos manually and those do show up in the Show Selection for LOTW when I look to see what is about to be uploaded.? I'm sure there is something simple I am missing here.?
?
When I open each of the QSOs, both fake ones i entered manually and real FT8 QSos, I can see no difference in the QSL tab, they all show queued.
?
Thoughts on where to look to figure this out?
?
Thanks,
?
Tim
KK9T
|
I will try to be patient for a while. These lists are large and sometimes take a long time to download them. It depends on your connection speed and your CPU speed.
Each time I start Qlog it gets hung up on updating SOTA and updating WWFF.? I can cancel these to get Qlog to initialize, but can I correct this behavior?
Thanks, Bill K4AJ
|
Each time I start Qlog it gets hung up on updating SOTA and updating WWFF.? I can cancel these to get Qlog to initialize, but can I correct this behavior?
Thanks, Bill K4AJ
|
New User QSO Upload Question
Hi, new user, just set the program up yesterday.? It looks great and I am impressed with the work that went into it.
?
I do have a problem with doing QSO uploads and I am sure it is something simple.?
?
I loaded the log for my current callsign and was able to use the Service menu to upload to various services so all the user names and passwords work.? TQSL is installed and configured.? I configured WSJTX and made a couple of contacts and I see that they made their way into my logbook successfully.? However, when I try to use any of the services to upload those QSOs, they will not show up in the Show Selection for LOTW for example (or any of the services).? There is nothing to upload even though the QSO's QSL information shows them as queued.? I entered a couple of dummy qsos manually and those do show up in the Show Selection for LOTW when I look to see what is about to be uploaded.? I'm sure there is something simple I am missing here.?
?
When I open each of the QSOs, both fake ones i entered manually and real FT8 QSos, I can see no difference in the QSL tab, they all show queued.
?
Thoughts on where to look to figure this out?
?
Thanks,
?
Tim
KK9T
|
Re: Filter most recent contacts on Log
Yes, I understand that function, but that's not what I want.? I just want to limit the amount of QSO loaded on the log.? For example, all contacts in last 90 days (or "whatever" days)... or Last 100 contacts, or whatever amount of contacts.
?
Regards,
?
[Edited Message Follows]
Joel, if you enter a call sign in the Callsign field of the New Qso window, then the logbook window switching to shows all previous contacts with that call sign, without having to use any filter. You can also input searched callsign into Search Callsign field of Logbook window with the same effect.
?
___
Slav, EI6KW, SP3RXO
?
?
|
toggle quoted message
Show quoted text
Hi,
it is already implemented. Just enable the LoTW Club in Settings -
Regards Ladislav
po 20. 1. 2025 v?13:34 odesílatel angelodena298 via <angelodena298= [email protected]> napsal: Hello everyone. It would be useful in view of the diffusion, the display on the spot clusters, if the call participates in the LOTW program.
Is it possible in the near future?
Thanks 73 de IT9IQQ - Angelo
|
Hi,
it is already implemented. Just enable the LoTW Club in Settings -
Regards Ladislav
po 20. 1. 2025 v?13:34 odesílatel angelodena298 via <angelodena298= [email protected]> napsal:
Hello everyone. It would be useful in view of the diffusion, the display on the spot clusters, if the call participates in the LOTW program.
Is it possible in the near future?
Thanks 73 de IT9IQQ - Angelo
|
Hello everyone. It would be useful in view of the diffusion, the display on the spot clusters, if the call participates in the LOTW program.
Is it possible in the near future?
Thanks 73 de IT9IQQ - Angelo
|
After a bit more experimenting, I like the en_SE.UTF-8 better. It uses 24h clock with the ISO date format yyyy/mm/dd instead of the dd/mm format that DK uses.
|
Thanks.? That solves my problem and makes perfect sense with the flatpak container or sandbox.? I still think it would be nice to have a preference setting though. :-) ?? 73, KB9RLW
On Saturday, January 18, 2025 at 10:15:08 AM MST, JP3REM Bill via groups.io <groups.io@...> wrote:
Kevin, your video on QLog got me over here. This is a real competitor for CQRlog for me. I really like this logger so far. I'm on Debian 12.
You said you're using the Flatpak. Flatpak applications run in a sandboxed environment, which may not inherit locale settings from the host system. To set a specific locale for a Flatpak application like QLog, you can pass environment variables when launching it or modify its Flatpak configuration.
1. Set Locale Temporarily
You can launch QLog with a custom locale by using the flatpak run command and passing the LC_* or LANG environment variables.
Example:
flatpak run --env=LC_TIME=en_DK.UTF-8 io.github.foldynl.QLog
This sets:
* LC_TIME: for 24-hour time format.
2. Set Locale Permanently for QLog
To apply these locale settings every time you launch QLog, you can modify its Flatpak environment variables:
a. Use flatpak override
Run the following command to set permanent environment variables for QLog:
flatpak override --user --env=LC_TIME=en_DK.UTF-8 io.github.foldynl.QLog
* This sets LC_TIME specifically for the QLog Flatpak.
* The --user flag ensures this change is applied only for your user account.
b. Verify the Override
To confirm the override has been set:
flatpak info --show-permissions io.github.foldynl.QLog
Look for the env section, which should now include LC_TIME.
4. Restart QLog
After setting the environment variables, restart QLog to apply the changes:
flatpak run io.github.foldynl.QLog
That worked for me to convert time to 24-hour time. You can add the following if you also want metric distance instead of miles:
--env=LC_MEASUREMENT=en_DK.UTF-8
de JP3REM
|
Kevin, your video on QLog got me over here. This is a real competitor for CQRlog for me. I really like this logger so far. I'm on Debian 12.
You said you're using the Flatpak. Flatpak applications run in a sandboxed environment, which may not inherit locale settings from the host system. To set a specific locale for a Flatpak application like QLog, you can pass environment variables when launching it or modify its Flatpak configuration.
1. Set Locale Temporarily
You can launch QLog with a custom locale by using the flatpak run command and passing the LC_* or LANG environment variables.
Example:
flatpak run --env=LC_TIME=en_DK.UTF-8 io.github.foldynl.QLog
This sets:
* LC_TIME: for 24-hour time format.
2. Set Locale Permanently for QLog
To apply these locale settings every time you launch QLog, you can modify its Flatpak environment variables:
a. Use flatpak override
Run the following command to set permanent environment variables for QLog:
flatpak override --user --env=LC_TIME=en_DK.UTF-8 io.github.foldynl.QLog
* This sets LC_TIME specifically for the QLog Flatpak.
* The --user flag ensures this change is applied only for your user account.
b. Verify the Override
To confirm the override has been set:
flatpak info --show-permissions io.github.foldynl.QLog
Look for the env section, which should now include LC_TIME.
4. Restart QLog
After setting the environment variables, restart QLog to apply the changes:
flatpak run io.github.foldynl.QLog
That worked for me to convert time to 24-hour time. You can add the following if you also want metric distance instead of miles:
--env=LC_MEASUREMENT=en_DK.UTF-8
de JP3REM
|
Re: Filter most recent contacts on Log
Joel, if you enter a call sign in the Callsign field of the New Qso window, then the logbook window switching to shows all previous contacts with that call sign, without having to use any filter. You can also input searched callsign into Search Callsign field of Logbook window with the same effect.
?
___
Slav, EI6KW, SP3RXO
|
Fixed with
?
Thank you
Kyle
|
Filter most recent contacts on Log
Is it possible to create a filter to show just the last X amount of contacts?? If I worked that station like 4 years ago I would like to show that when I first enter the call (the normal behavior), but on the Log been shown/preview when I have no callsign pending to "log it" (like Im in stand-by with no contact going on), I would like to filter either by amount of contacts, Or maybe amount of days behind today (say like in the last 90 days).
?
I setup one filter right now anything greater than Nov 1 2024, but then I will have to go and keep updating that as time moves on...
?
Is there a way to set the filter either of those ways?
?
Thanks
Joel/WE0DX
|
Hi Mike,
you already reported something similar a few months ago. /g/qlog/message/472 So it's not a new behavior but just a change in behavior that may be caused by a hamlib upgrade.
see details below.
Especially the last link shows that there is no solution for it now.
pá 17. 1. 2025 v?3:23 odesílatel Mike - K3SNO, #707 via <mcguire2003= [email protected]> napsal:
Since the update to 0.41.0 I'm having a strange issue. Nothing was
changed other than the update and now my FTDX10 does not change band and
frequency correctly. When clicking on a spot and going from 40/80m LSB
to 10-20m USB, the frequency changes correctly (at first) but the mode
does not change correctly. The third double-click causes the mode to
change correctly but the frequency Is NOW offset by the USB/LSB
difference. Then the third double-click puts the frequency right. It
does this in both directions.
Can anyone point me in a direction of assistance?
Linux Mint 21.3
QLog 0.41.0 w/ hamLib 4.6
--
V/R,
Michael G. Mcguire, K3SNO
484-703-9591
So Mote It Be
|
Since the update to 0.41.0 I'm having a strange issue. Nothing was changed other than the update and now my FTDX10 does not change band and frequency correctly. When clicking on a spot and going from 40/80m LSB to 10-20m USB, the frequency changes correctly (at first) but the mode does not change correctly. The third double-click causes the mode to change correctly but the frequency Is NOW offset by the USB/LSB difference. Then the third double-click puts the frequency right. It does this in both directions.
Can anyone point me in a direction of assistance?
Linux Mint 21.3
QLog 0.41.0 w/ hamLib 4.6
--
V/R,
Michael G. Mcguire, K3SNO
484-703-9591
So Mote It Be
|
Also, based on your postscript we are probably not setting the flags correctly on app open versus showing the sub-windows after the app is open.
Cheers
Kyle
|
Seems like this is an occurance of this issue: .
In macos QT, floating windows are considered utility windows which have the behaviour your video demonstrates. I tried to address this behaviour in 530 by setting flags to disable the hiding. I'll try to do more testing on this. At the time of the commit it seemed to work for floating windows that only had 1 panel.
Kyle
|
Michael good morning,
sorry for the delay, but I couldn't answer before.
Today I find myself in the same situation that I had before the update to 0.41.
Surely between the first email and today I had some updates of various apps.
To be safe I stopped the various apps that start in the background except "dropbox" which is essential for the use of the programs as I have all symbolic links to the data placed in the cloud, I ran qlog by itself, the result is that by clicking on any part of the screen all the icons that I opened disappear.
You can see the behavior in the short video that I attach.
I am a retired computer scientist, if you think I can be of help to you in my small skills I am available.
73 Roberto IU2NUB
?
PS. After further testing I discovered that if I close the app without closing the windows it behaves as per the video, if I open the app and then open the windows it seems that these do not disappear if I bring the focus on other windows
?
|
Bill
Joel Vazquez, WE0DX
Slav, EI6KW
Mike - K3SNO, #707