Keyboard Shortcuts
ctrl + shift + ? :
Show all keyboard shortcuts
ctrl + g :
Navigate to a group
ctrl + shift + f :
Find
ctrl + / :
Quick actions
esc to dismiss
Likes
- Qlog
- Messages
Search
Re: New User QSO Upload Question - RESOLVED
Please note that if you operate a different grid than usual, you can still upload QSOs to the different services by selecting the appropriate Grid in the upload window for each one. ("My Gridsquare" drop-down list) Diego Carratini El mi¨¦, 22 ene 2025 10:49, Tim Rife via <lists=[email protected]> escribi¨®:
|
|||
Re: New User QSO Upload Question - RESOLVED
Thanks to both Ladislav and Diego for where to look.? I did have a grid square mismatch between WSJT-X (4 character square in the settings) and QLog (6 character square in the station profile setup).? When I edited the QSO from WSJT-X and changed the My Station Grid Square to the 6 character square to match the station setup in QLog, I was able to see the QSO in the upload queue.? So, lesson learned, make sure qrid squares match exactly.
?
Thanks again and 73,
?
Tim
KK9T |
|||
Re: New User QSO Upload Question
Thanks Ladislav and Diego.?
?
I do, in fact, have a 4 digit grid set up in WSJT-X and a 6 digit in QLog.? I will snyc those and try again and if it works, will let everyone know.
?
Just for completeness, the system is Linux Mint 22 and WSJT-X 2.7.0 RC3 which I installed via flatpak.
?
73
?
Tim
KK9T |
|||
Re: New User QSO Upload Question
Hi, Diego Carratini El mi¨¦, 22 ene 2025 07:29, ok1mlg via <ok1mlg=[email protected]> escribi¨®:
|
|||
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 st 22. 1. 2025 v?8:54 odes¨ªlatel Tim Rife via <lists=[email protected]> napsal:
|
|||
Re: First time on Qlog
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. st 22. 1. 2025 v?8:54 odes¨ªlatel Bill via <K4AJ=[email protected]> napsal:
|
|||
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,
?
On Sat, Jan 18, 2025 at 4:45?AM Slav, EI6KW via <sp3rxo=[email protected]> wrote:
|
|||
Re: Cluster and LOTW
Grazie, fatto. 73 Il lun 20 gen 2025, 13:59 ok1mlg via <ok1mlg=[email protected]> ha scritto:
|
|||
Re: Cluster and LOTW
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:
|
|||
Re: 24 hour clock?
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 |
|||
Re: 24 hour clock?
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
|
|||
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 |
to navigate to use esc to dismiss