Hi Ladislav,
Any chance to real time QSO upload to HamQTH.com log?
--
___
Slav, EI6KW, SP3RXO
|
Hi Adam, on Linux Mint go to System Settings, Language and change "Time Format" to English United Kingdom, log out and then back in or reboot to be sure. Qlog will now show time as you want it. Leave language and region on English, Australia (or whatever you have them on).
?
73 Phill C21TS
?
?
 ?
|
Re: Device ID and Path for Rig/ Rotor Control
#Guide
#Tip
Certainly helped me. I had no idea about the port assignments and now have the 991 and 7300 hooked up simultaneously and can shift radios without having to disconnect, change cables, and reconnect. Michael G McGuire, K3SNO 484-703-9591 So Mote It Be.
toggle quoted message
Show quoted text
On Oct 13, 2024, at 5:11?AM, ok1mlg <ok1mlg@...> wrote:
? Perfect description. It's worth thinking about adding some kind of good-practice page to the Wiki. Can I use your text? ne 13. 10. 2024 v?6:17 odes¨ªlatel Adam VK4IM via <vk4im0438= [email protected]> napsal: Hi
?
I¡¯ll preface this post with: I¡¯m a Linux Newbie, there may be better ways to do what I will describe below. Do your research and use caution.
?
If you are like me and have recently moved to Linux, or are transitioning away from MS Windows, you would have noticed there are some differences with regards to USB ports. You can no longer use ¡°COM#¡± as an entry. It won't work.?
?
You can use ¡°ttyUSB#¡±, but as Ladislav mentioned in this post /g/qlog/message/428 ¡°It's not a very good practice to use ttyUSB# devices. These device files can change during disconnection or reboot."
?
I have found a couple of ways to determine the correct "Device ID" and "Path" to use: The Terminal Shell method (Alias: console, or command prompt) or the Graphical method.
?
Note: Both methods described below relate to Linux Mint 22 Cinnamon. It may, or may not, be the same for your flavor of Linux, but should give you a clue on where to look.
?
Terminal Shell:
?
For the purists and those wanting to learn a little about the Terminal Shell.
?
Add Yourself To The "dialout" Group
?
-
Open "Terminal" from the menu¡ right click the Linux logo in the bottom left corner and type "Terminal" in the search bar and click the "Terminal".
- Type:
- groups <your username>
<inline.0.part>
- If you do not see "dialout" listed type the following:
- sudo adduser <your username> dialout
- Enter your Administrator Password and hit enter.
- Reboot the computer for changes to take effect
Find the Device ID
?
- Open a Terminal Shell and enter "ls /dev/serial/by-id" (Without quotes)
- This will return something like the following:
- In this example ¡°usb-FTDI...¡± is my rotator controller and the ¡°USB-Silicone_Labs...¡± is my Icom IC-7300.
- In your terminal, select/ highlight the Device ID you want to use, right click and select copy
- Append the Device ID to the file path: ¡°/dev/serial/by-id/¡±.
- Like: ¡°/dev/serial/by-id/¡± PLUS ¡°³Ü²õ²ú-³§¾±±ô¾±³¦´Ç²Ô³å³¢²¹²ú²õ³å°ä±Ê2102³å±«³§µþ³å³Ù´Ç³å±«´¡¸é°Õ³åµþ°ù¾±»å²µ±ð³å°ä´Ç²Ô³Ù°ù´Ç±ô±ô±ð°ù³å±õ°ä-7300³å02027024-¾±´Ú00-±è´Ç°ù³Ù0¡±
-
You final path will look something like this:
- Paste the file name into the Port section under Rigs (or as appropriate) in your setup screen in QLOG.
-
Click ¡°Modify¡± and ¡°Save¡±
- In the Menu bar click "Equipment" and then "Connect"
- If all is correct your device should connect and keep the same path between reboots.
Graphical Method:
?
Add Yourself To The "dialout" Group
?
- Open "Users and Groups" from the menu¡ right click the Linux logo in the bottom left corner and type "Users and Groups" in the search bar and click the "Users and Groups".
- Enter your Administrator Password and hit enter
- Select the user to update
- If you do not see "dialout" listed under the "Groups" section, left click on the red highlighted area to open the "Groups" section
- Put a tick in the box for "dialout" and click OK
- Click 'X" to close and then reboot the computer for changes to take effect
Find the Device ID
?
This method may be more intuitive than the Terminal Shell method mentioned above if you are coming from MS Windows. I'd encourage you to try the Terminal Shell method as it can be quicker and easier.
?
-
Open your favorite "Files Explorer" from the menu¡ right click the Linux logo in the bottom left corner and type "Files" in the search bar and click the "Files Explorer".
- Make sure you are in the root directory. Type ¡°/¡± in the search bar at the top
- NOTE: You can mess things up while in the root directory if you change or delete things. Use caution.
<inline.5.part>
- Right click on the device you need and select properties.
- At the top under name hover over the ¡°Name¡± of the file and right click to select all.
-
Right click over the name again and select copy
- From here, refer to point 5 in the "Terminal Shell Method" under "Find the Device ID" above
Others more knowledgeable than me may chime in with alternatives or corrections which are welcome.
Hope this helps another Newbie
Cheers
Adam, VK4IM
?
|
Ah, thank you! Busy weekend, but I will try to make (and correctly log) some more QSOs.
?
?
|
No, I haven't. Mostly because I don't know where to start.
I have no idea where these settings are supposed to go. At a guess I'd say in a *.conf file like on AllStarLink, but I'm guessing.
It's something I need to study
Cheers
Adam, VK4IM
13 Oct 2024 19:21:48 ok1mlg <ok1mlg@...>:
toggle quoted message
Show quoted text
The time on the Task Bar has its own setting than the time of Linux itself.
Therefore, it is necessary to use the LC_TIME variable to control time format in QLog.
control many settings in QLog (number
format, time format, date format, sorting, GUI language etc.). There are a lot of things that would have to be set manually, and that's
why QLog uses it to help the operator's work with settings.
ne 13. 10. 2024 v?8:15 odes¨ªlatel Adam VK4IM via
<vk4im0438= [email protected]> napsal:
Hi
?
?
BUT... I'm struggling to get QLOG to show the time in 24 hour format. I do not want to see AM/PM. I'm not worried about the date, just time.
?
How can I do this... My task bar shows 24 hour time format but QLOG does not. Screen grab below.
?
I'm using Linux Mint 22 Cinnamon. What am I doing wrong?
?
(Yes, I'm new to Linux)
?
Cheers
Adam, VK4IM
?
|
JS8 is not a mode but a sub-mode. Enable MFSK mode and then JS8 is a submode of MFSK. The same as it is in the case of FT4; it is a submode of MFSK.
ne 13. 10. 2024 v?11:02 odes¨ªlatel SignalScout via <steve.owens70= [email protected]> napsal:
toggle quoted message
Show quoted text
Hello all! What a great logger this is! If I'm ever asked how I set it up, I will have to answer "accidentally". It was almost that easy. I use it under Linux Mint 21.1 with an IC-7300, WF View, WSJT-X and JS8 Call. My only cares in the world tonight are a mild backache, a somewhat underperforming vertical antenna, and I can't seem to find JS8 in the mode pulldown menu.
?
73
|
The time on the Task Bar has its own setting than the time of Linux itself. Therefore, it is necessary to use the LC_TIME variable to control time format in QLog.
control many settings in QLog (number format, time format, date format, sorting, GUI language etc.). There are a lot of things that would have to be set manually, and that's why QLog uses it to help the operator's work with settings. ne 13. 10. 2024 v?8:15 odes¨ªlatel Adam VK4IM via <vk4im0438= [email protected]> napsal:
toggle quoted message
Show quoted text
Hi
?
?
BUT... I'm struggling to get QLOG to show the time in 24 hour format. I do not want to see AM/PM. I'm not worried about the date, just time.
?
How can I do this... My task bar shows 24 hour time format but QLOG does not. Screen grab below.
?
I'm using Linux Mint 22 Cinnamon. What am I doing wrong?
?
(Yes, I'm new to Linux)
?
Cheers
Adam, VK4IM
?
|
Re: Device ID and Path for Rig/ Rotor Control
#Guide
#Tip
Please do!
If YOU think it's perfect. I'm very happy I got it correct.
Not bad for a Linux Newbie ;-)
Thanks!
Cheers
Adam, VK4IM
13 Oct 2024 19:10:54 ok1mlg <ok1mlg@...>:
toggle quoted message
Show quoted text
Perfect description. It's worth thinking about adding some kind of good-practice page to the Wiki.
Can I use your text?
ne 13. 10. 2024 v?6:17 odes¨ªlatel Adam VK4IM via
<vk4im0438= [email protected]> napsal:
Hi
?
I¡¯ll preface this post with:
I¡¯m a Linux Newbie, there may be better ways to do what I will describe below. Do your research and use caution.
?
If you are like me and have recently moved to Linux, or are transitioning away from MS Windows, you would have noticed there
are some differences with regards to USB ports. You can no longer use ¡°COM#¡± as an entry. It won't work.?
?
You can use ¡°ttyUSB#¡±, but as Ladislav mentioned in this post
/g/qlog/message/428 ¡°It's not a very good practice to use ttyUSB# devices. These device files can change during disconnection or reboot."
?
I have found a couple of ways to determine the correct "Device ID" and "Path" to use: The Terminal Shell method (Alias: console, or command prompt) or the Graphical method.
?
Note: Both methods described below relate to Linux Mint 22 Cinnamon. It may, or may not, be the same for your flavor of Linux, but should give you a clue on where to look.
?
Terminal Shell:
?
For the purists and those wanting to learn a little about the Terminal Shell.
?
Add Yourself To The "dialout" Group
?
-
Open "Terminal" from the menu¡ right click the Linux logo in the bottom left corner and type "Terminal" in the search bar and
click the "Terminal".
- Type:
- groups <your username>

- If you do not see "dialout" listed type the following:
- sudo adduser <your username> dialout
- Enter your Administrator Password and hit enter.
- Reboot the computer for changes to take effect
Find the Device ID
?
- Open a Terminal Shell and enter "ls /dev/serial/by-id" (Without quotes)
- This will return something like the following:
- In this example ¡°usb-FTDI...¡± is my rotator controller and the ¡°USB-Silicone_Labs...¡± is my Icom IC-7300.
- In your terminal, select/ highlight the Device ID you want to use, right click and select copy
- Append the Device ID to the file path: ¡°/dev/serial/by-id/¡±.
- Like: ¡°/dev/serial/by-id/¡±
PLUS ¡°³Ü²õ²ú-³§¾±±ô¾±³¦´Ç²Ô³å³¢²¹²ú²õ³å°ä±Ê2102³å±«³§µþ³å³Ù´Ç³å±«´¡¸é°Õ³åµþ°ù¾±»å²µ±ð³å°ä´Ç²Ô³Ù°ù´Ç±ô±ô±ð°ù³å±õ°ä-7300³å02027024-¾±´Ú00-±è´Ç°ù³Ù0¡±
-
You final path will look something like this:
- Paste the file name into the Port section under Rigs (or as appropriate) in your setup screen in QLOG.
-
Click ¡°Modify¡± and ¡°Save¡±
- In the Menu bar click "Equipment" and then "Connect"
- If all is correct your device should connect and keep the same path between reboots.
Graphical Method:
?
Add Yourself To The "dialout" Group
?
- Open "Users and Groups" from the menu¡
right click the Linux logo in the bottom left corner and
type "Users and Groups" in the search bar and click the
"Users and Groups".
- Enter your Administrator Password and hit enter
- Select the user to update
- If you do not see "dialout" listed under the "Groups" section, left click on the red highlighted area to open the "Groups" section
- Put a tick in the box for "dialout" and click OK
- Click 'X" to close and then reboot the computer for changes to take effect
Find the Device ID
?
This method may be more intuitive than the Terminal Shell method mentioned above if you are coming from MS Windows. I'd encourage you to try the Terminal Shell method as it can be quicker
and easier.
?
-
Open your favorite "Files Explorer" from the menu¡
right click the Linux logo in the bottom left corner and
type "Files" in the search bar and click the "Files Explorer".
- Make sure you are in the root directory. Type ¡°/¡± in the search bar at the top
- NOTE: You can mess things up while in the root directory if you change or delete things. Use caution.

- Right click on the device you need and select properties.
- At the top under name hover over the ¡°Name¡± of the file and right click to select all.
-
Right click over the name again and select copy
- From here, refer to point 5 in the "Terminal Shell Method" under "Find the Device ID" above
Others more knowledgeable than me may chime in with alternatives or corrections which are welcome.
Hope this helps another Newbie
Cheers
Adam, VK4IM
?
|
Re: Device ID and Path for Rig/ Rotor Control
#Guide
#Tip
Perfect description. It's worth thinking about adding some kind of good-practice page to the Wiki. Can I use your text? ne 13. 10. 2024 v?6:17 odes¨ªlatel Adam VK4IM via <vk4im0438= [email protected]> napsal:
toggle quoted message
Show quoted text
Hi
?
I¡¯ll preface this post with: I¡¯m a Linux Newbie, there may be better ways to do what I will describe below. Do your research and use caution.
?
If you are like me and have recently moved to Linux, or are transitioning away from MS Windows, you would have noticed there are some differences with regards to USB ports. You can no longer use ¡°COM#¡± as an entry. It won't work.?
?
You can use ¡°ttyUSB#¡±, but as Ladislav mentioned in this post /g/qlog/message/428 ¡°It's not a very good practice to use ttyUSB# devices. These device files can change during disconnection or reboot."
?
I have found a couple of ways to determine the correct "Device ID" and "Path" to use: The Terminal Shell method (Alias: console, or command prompt) or the Graphical method.
?
Note: Both methods described below relate to Linux Mint 22 Cinnamon. It may, or may not, be the same for your flavor of Linux, but should give you a clue on where to look.
?
Terminal Shell:
?
For the purists and those wanting to learn a little about the Terminal Shell.
?
Add Yourself To The "dialout" Group
?
-
Open "Terminal" from the menu¡ right click the Linux logo in the bottom left corner and type "Terminal" in the search bar and click the "Terminal".
- Type:
- groups <your username>

- If you do not see "dialout" listed type the following:
- sudo adduser <your username> dialout
- Enter your Administrator Password and hit enter.
- Reboot the computer for changes to take effect
Find the Device ID
?
- Open a Terminal Shell and enter "ls /dev/serial/by-id" (Without quotes)
- This will return something like the following:
- In this example ¡°usb-FTDI...¡± is my rotator controller and the ¡°USB-Silicone_Labs...¡± is my Icom IC-7300.
- In your terminal, select/ highlight the Device ID you want to use, right click and select copy
- Append the Device ID to the file path: ¡°/dev/serial/by-id/¡±.
- Like: ¡°/dev/serial/by-id/¡± PLUS ¡°³Ü²õ²ú-³§¾±±ô¾±³¦´Ç²Ô³å³¢²¹²ú²õ³å°ä±Ê2102³å±«³§µþ³å³Ù´Ç³å±«´¡¸é°Õ³åµþ°ù¾±»å²µ±ð³å°ä´Ç²Ô³Ù°ù´Ç±ô±ô±ð°ù³å±õ°ä-7300³å02027024-¾±´Ú00-±è´Ç°ù³Ù0¡±
-
You final path will look something like this:
- Paste the file name into the Port section under Rigs (or as appropriate) in your setup screen in QLOG.
-
Click ¡°Modify¡± and ¡°Save¡±
- In the Menu bar click "Equipment" and then "Connect"
- If all is correct your device should connect and keep the same path between reboots.
Graphical Method:
?
Add Yourself To The "dialout" Group
?
- Open "Users and Groups" from the menu¡ right click the Linux logo in the bottom left corner and type "Users and Groups" in the search bar and click the "Users and Groups".
- Enter your Administrator Password and hit enter
- Select the user to update
- If you do not see "dialout" listed under the "Groups" section, left click on the red highlighted area to open the "Groups" section
- Put a tick in the box for "dialout" and click OK
- Click 'X" to close and then reboot the computer for changes to take effect
Find the Device ID
?
This method may be more intuitive than the Terminal Shell method mentioned above if you are coming from MS Windows. I'd encourage you to try the Terminal Shell method as it can be quicker and easier.
?
-
Open your favorite "Files Explorer" from the menu¡ right click the Linux logo in the bottom left corner and type "Files" in the search bar and click the "Files Explorer".
- Make sure you are in the root directory. Type ¡°/¡± in the search bar at the top
- NOTE: You can mess things up while in the root directory if you change or delete things. Use caution.

- Right click on the device you need and select properties.
- At the top under name hover over the ¡°Name¡± of the file and right click to select all.
-
Right click over the name again and select copy
- From here, refer to point 5 in the "Terminal Shell Method" under "Find the Device ID" above
Others more knowledgeable than me may chime in with alternatives or corrections which are welcome.
Hope this helps another Newbie
Cheers
Adam, VK4IM
?
|
Hello all! What a great logger this is! If I'm ever asked how I set it up, I will have to answer "accidentally". It was almost that easy. I use it under Linux Mint 21.1 with an IC-7300, WF View, WSJT-X and JS8 Call. My only cares in the world tonight are a mild backache, a somewhat underperforming vertical antenna, and I can't seem to find JS8 in the mode pulldown menu.
?
73
|
Hi
?
?
BUT... I'm struggling to get QLOG to show the time in 24 hour format. I do not want to see AM/PM. I'm not worried about the date, just time.
?
How can I do this... My task bar shows 24 hour time format but QLOG does not. Screen grab below.
?
I'm using Linux Mint 22 Cinnamon. What am I doing wrong?
?
(Yes, I'm new to Linux)
?
Cheers
Adam, VK4IM
?
|
Device ID and Path for Rig/ Rotor Control
#Guide
#Tip
Hi
?
I¡¯ll preface this post with: I¡¯m a Linux Newbie, there may be better ways to do what I will describe below. Do your research and use caution.
?
If you are like me and have recently moved to Linux, or are transitioning away from MS Windows, you would have noticed there are some differences with regards to USB ports. You can no longer use ¡°COM#¡± as an entry. It won't work.?
?
You can use ¡°ttyUSB#¡±, but as Ladislav mentioned in this post /g/qlog/message/428 ¡°It's not a very good practice to use ttyUSB# devices. These device files can change during disconnection or reboot."
?
I have found a couple of ways to determine the correct "Device ID" and "Path" to use: The Terminal Shell method (Alias: console, or command prompt) or the Graphical method.
?
Note: Both methods described below relate to Linux Mint 22 Cinnamon. It may, or may not, be the same for your flavor of Linux, but should give you a clue on where to look.
?
Terminal Shell:
?
For the purists and those wanting to learn a little about the Terminal Shell.
?
Add Yourself To The "dialout" Group
?
-
Open "Terminal" from the menu¡ right click the Linux logo in the bottom left corner and type "Terminal" in the search bar and click the "Terminal".
- Type:
- groups <your username>

- If you do not see "dialout" listed type the following:
- sudo adduser <your username> dialout
- Enter your Administrator Password and hit enter.
- Reboot the computer for changes to take effect
Find the Device ID
?
- Open a Terminal Shell and enter "ls /dev/serial/by-id" (Without quotes)
- This will return something like the following:
- In this example ¡°usb-FTDI...¡± is my rotator controller and the ¡°USB-Silicone_Labs...¡± is my Icom IC-7300.
- In your terminal, select/ highlight the Device ID you want to use, right click and select copy
- Append the Device ID to the file path: ¡°/dev/serial/by-id/¡±.
- Like: ¡°/dev/serial/by-id/¡± PLUS ¡°³Ü²õ²ú-³§¾±±ô¾±³¦´Ç²Ô³å³¢²¹²ú²õ³å°ä±Ê2102³å±«³§µþ³å³Ù´Ç³å±«´¡¸é°Õ³åµþ°ù¾±»å²µ±ð³å°ä´Ç²Ô³Ù°ù´Ç±ô±ô±ð°ù³å±õ°ä-7300³å02027024-¾±´Ú00-±è´Ç°ù³Ù0¡±
-
You final path will look something like this:
- Paste the file name into the Port section under Rigs (or as appropriate) in your setup screen in QLOG.
-
Click ¡°Modify¡± and ¡°Save¡±
- In the Menu bar click "Equipment" and then "Connect"
- If all is correct your device should connect and keep the same path between reboots.
Graphical Method:
?
Add Yourself To The "dialout" Group
?
- Open "Users and Groups" from the menu¡ right click the Linux logo in the bottom left corner and type "Users and Groups" in the search bar and click the "Users and Groups".
- Enter your Administrator Password and hit enter
- Select the user to update
- If you do not see "dialout" listed under the "Groups" section, left click on the red highlighted area to open the "Groups" section
- Put a tick in the box for "dialout" and click OK
- Click 'X" to close and then reboot the computer for changes to take effect
Find the Device ID
?
This method may be more intuitive than the Terminal Shell method mentioned above if you are coming from MS Windows. I'd encourage you to try the Terminal Shell method as it can be quicker and easier.
?
-
Open your favorite "Files Explorer" from the menu¡ right click the Linux logo in the bottom left corner and type "Files" in the search bar and click the "Files Explorer".
- Make sure you are in the root directory. Type ¡°/¡± in the search bar at the top
- NOTE: You can mess things up while in the root directory if you change or delete things. Use caution.

- Right click on the device you need and select properties.
- At the top under name hover over the ¡°Name¡± of the file and right click to select all.
-
Right click over the name again and select copy
- From here, refer to point 5 in the "Terminal Shell Method" under "Find the Device ID" above
Others more knowledgeable than me may chime in with alternatives or corrections which are welcome.
Hope this helps another Newbie
Cheers
Adam, VK4IM
?
|
wow, so snappy now, 73K QSO and it feels so fast now, I mean it wasn't slow before but now there is no delay at all after log uploads when I click on service again.?
?
Keep up the good work.?
?
73 Phill C21TS
|
I uploaded the build for MacOS:?
Thanks for all the updates Ladislav
Michael, AA5SH
toggle quoted message
Show quoted text
Let me inform you that a new QLog release v0.39.0 is finished.
Thank you for your patience in finding and testing bugs.
Changelog:
- [NEW] - DXC - Added Full-text search - [NEW] - Select S in RST Edit when focused (issue #454) - [NEW] - Alerts - Added Member Column - [CHANGED] - HamlibDrv Rig/Rot- Added multiplatform reliable sleep - [CHANGED] - Changed Backup policy - [CHANGED] - Logbook page size - improved performance - [CHANGED] - Logbook - CTRL-A (Select All) is disabled - [CHANGED] - Awards - Bands are displayed based on the Settings (issue #452) - [CHANGED] - WSJTX - More reliable detection of CQ stations (PR #471 @aa5sh) - [CHANGED] - WSJTX - SOTA/POTA/WWFF/SIG are being added to the logged QSO (PR #463 @aa5sh) - [CHANGED] - Stats - Add a confirmation dialog for displaying over 50k QSOs on the map - [CHANGED] - New Contact - Starting QSO Timer when Rig online and WSJTX Update Callsign Status is received - [CHANGED] - Added a postponed handling for Rig soft errors (issue #472) - Fixed WSJT-X does not emit band change if rig is disconnected (issue #447) - Fixed Wrong import of ADIF file of another log program (issue #455) - Fixed WSJTX log record is stored incorrectly if it contains non-ASCII chars(issue #458) - Fixed ADIF import does not import records with old DXCC Entities (issue #459) - Fixed ADIF import incorrectly uses Station Profile parameters (issue #461) - Fixed Logbook - QSO Table Column Width Does Not Stick (issue #464) - Fixed Alerts Window displays OOB Spots (issue #469) - Fixed Field values from past QSOs are used incorrectly in case of WSJTX QSOs (#issue 470)
Changelog:
|
Let me inform you that a new QLog release v0.39.0 is finished.
Thank you for your patience in finding and testing bugs.
Changelog:
- [NEW] - DXC - Added Full-text search - [NEW] - Select S in RST Edit when focused (issue #454) - [NEW] - Alerts - Added Member Column - [CHANGED] - HamlibDrv Rig/Rot- Added multiplatform reliable sleep - [CHANGED] - Changed Backup policy - [CHANGED] - Logbook page size - improved performance - [CHANGED] - Logbook - CTRL-A (Select All) is disabled - [CHANGED] - Awards - Bands are displayed based on the Settings (issue #452) - [CHANGED] - WSJTX - More reliable detection of CQ stations (PR #471 @aa5sh) - [CHANGED] - WSJTX - SOTA/POTA/WWFF/SIG are being added to the logged QSO (PR #463 @aa5sh) - [CHANGED] - Stats - Add a confirmation dialog for displaying over 50k QSOs on the map - [CHANGED] - New Contact - Starting QSO Timer when Rig online and WSJTX Update Callsign Status is received - [CHANGED] - Added a postponed handling for Rig soft errors (issue #472) - Fixed WSJT-X does not emit band change if rig is disconnected (issue #447) - Fixed Wrong import of ADIF file of another log program (issue #455) - Fixed WSJTX log record is stored incorrectly if it contains non-ASCII chars(issue #458) - Fixed ADIF import does not import records with old DXCC Entities (issue #459) - Fixed ADIF import incorrectly uses Station Profile parameters (issue #461) - Fixed Logbook - QSO Table Column Width Does Not Stick (issue #464) - Fixed Alerts Window displays OOB Spots (issue #469) - Fixed Field values from past QSOs are used incorrectly in case of WSJTX QSOs (#issue 470)
Changelog:
|
Re: Rig control with Hamlib
Thank you for this bit of advice Ladislav. I have struggled for
some time to get CAT control of my radios working in Linux. I
would work and work to get the correct ports going, then after
shutting down they would not work again. Every thing seems to be
very stable using the method you described. I have been dabbling
in Linux for some time, but the lack of good ham radio software
has kept me away. The QLog program appears to start to change that
pattern a bit. Thanks again.
Roy KW4G
toggle quoted message
Show quoted text
On 10/2/24 2:49 AM, ok1mlg via groups.io wrote:
I can't advise you for FLDigi or
CQRLog, but I use this for IC7300 and Qlog.
Everything
worked. so not sure if it works even after
upgrading to ubuntu 24.04. I didn't test it.
Let me add a couple of notes.
- It's not a very good practice to use ttyUSB# devices.
These device files can change during disconnection or reboot.
I know that it is described in
almost all manuals but if you're
not sure what you're doing, it's better to use the Device ID
file. For ICOM, the port is:
/dev/serial/by-id/usb-Silicon_Labs_CP2102_USB_to_UART_Bridge_Controller_IC-7300_03018006-if00-port0
- You have to have a write permission to your Device ID
file. So you must be in the appropriate
group as a user.
- You didn't mention what kind of
problem you actually have. An error report or some description
of the behavior is a good starting point to someone
being able to help you.
Regards
Ladislav
I hope it is OK for me to latch onto this thread. I am
also having trouble getting Qlog to connect to my IC-7300 or
my IC-9700. I recently installed Mint22 in dual-boot mode on
my computer. I installed Qlog, but cannot get it to connect
to either radio. I also have FLRig and CQRLog installed, and
neither of them communicate with the rigs. I know I must be
doing something stupid, but I don't know what it is.
Probably not a member of the correct group or something. I
have tried every /dev/ttyUSB# that I have. I know my radio
is set for 115200 baud. I just can't figure it out. I am
pretty much a linux neophyte, but I have had rig control
working under other versions of Ubuntu.
?
Roy KW4G
--
Roy
|
Re: Rig control with Hamlib
Please disregard this message. I had botched the entry for the
port. All good now.
Roy KW4G
On 10/2/24 9:01 AM, Roy Jackson via
groups.io wrote:
Mark,
That was it. I had assigned my user to the dialout group, but I
forgot that I had to logout and log back in to make that
affective. However, now I am getting another error when trying
to connect the rig.

Thanks for any assistance you may be able to offer.
Roy KW4G
On 10/2/24 4:11 AM, Mark ZL3AB via
groups.io wrote:
If none of the software programs connect then I
suspect you don't have permission to access the serial port.
I struck the same issue and had to add myself to
the dialout group then everything worked.
To see if you are in the dialout group...
Groups username?
If you aren't then...
sudo adduser username dialout
73?
Mark ZL3AB?
I can't advise you for
FLDigi or CQRLog, but I use this for IC7300 and
Qlog.
Everything worked.
so not sure if it works even after
upgrading to ubuntu 24.04. I
didn't test it.
Let me add a couple of
notes.
- It's not a very good practice to use ttyUSB#
devices. These device files can change during
disconnection or reboot. I
know that it is described in almost all manuals
but if you're not sure what
you're doing, it's better to use the Device ID file.
For ICOM, the port is:
/dev/serial/by-id/usb-Silicon_Labs_CP2102_USB_to_UART_Bridge_Controller_IC-7300_03018006-if00-port0
- You have to have a write permission to your
Device ID file. So you
must be in the appropriate group as a user.
- You didn't mention
what kind of problem you actually have.
An error report or some description of
the behavior is a good starting point to someone
being able to help you.
Regards
Ladislav
I hope it is OK for me to latch onto this thread.
I am also having trouble getting Qlog to connect to
my IC-7300 or my IC-9700. I recently installed
Mint22 in dual-boot mode on my computer. I installed
Qlog, but cannot get it to connect to either radio.
I also have FLRig and CQRLog installed, and neither
of them communicate with the rigs. I know I must be
doing something stupid, but I don't know what it is.
Probably not a member of the correct group or
something. I have tried every /dev/ttyUSB# that I
have. I know my radio is set for 115200 baud. I just
can't figure it out. I am pretty much a linux
neophyte, but I have had rig control working under
other versions of Ubuntu.
?
Roy KW4G
--
Roy
--
Roy
|
Re: Rig control with Hamlib
Mark,
That was it. I had assigned my user to the dialout group, but I
forgot that I had to logout and log back in to make that
affective. However, now I am getting another error when trying to
connect the rig.

Thanks for any assistance you may be able to offer.
Roy KW4G
On 10/2/24 4:11 AM, Mark ZL3AB via
groups.io wrote:
If none of the software programs connect then I
suspect you don't have permission to access the serial port.
I struck the same issue and had to add myself to
the dialout group then everything worked.
To see if you are in the dialout group...
Groups username?
If you aren't then...
sudo adduser username dialout
73?
Mark ZL3AB?
I can't advise you for
FLDigi or CQRLog, but I use this for IC7300 and
Qlog.
Everything worked.
so not sure if it works even after
upgrading to ubuntu 24.04. I
didn't test it.
Let me add a couple of
notes.
- It's not a very good practice to use ttyUSB#
devices. These device files can change during
disconnection or reboot. I
know that it is described in almost all manuals
but if you're not sure what
you're doing, it's better to use the Device ID file. For
ICOM, the port is:
/dev/serial/by-id/usb-Silicon_Labs_CP2102_USB_to_UART_Bridge_Controller_IC-7300_03018006-if00-port0
- You have to have a write permission to your Device
ID file. So you must be in
the appropriate group as a user.
- You didn't mention what
kind of problem you actually have. An
error report or some description of the behavior
is a good starting point to someone being able to
help you.
Regards
Ladislav
I hope it is OK for me to latch onto this thread. I
am also having trouble getting Qlog to connect to my
IC-7300 or my IC-9700. I recently installed Mint22 in
dual-boot mode on my computer. I installed Qlog, but
cannot get it to connect to either radio. I also have
FLRig and CQRLog installed, and neither of them
communicate with the rigs. I know I must be doing
something stupid, but I don't know what it is.
Probably not a member of the correct group or
something. I have tried every /dev/ttyUSB# that I
have. I know my radio is set for 115200 baud. I just
can't figure it out. I am pretty much a linux
neophyte, but I have had rig control working under
other versions of Ubuntu.
?
Roy KW4G
--
Roy
|
Re: Rig control with Hamlib
If none of the software programs connect then I suspect you don't have permission to access the serial port.
I struck the same issue and had to add myself to the dialout group then everything worked.
To see if you are in the dialout group...
Groups username?
If you aren't then...
sudo adduser username dialout
73? Mark ZL3AB?
toggle quoted message
Show quoted text
I can't advise you for FLDigi or CQRLog, but I use this for IC7300 and Qlog.
Everything worked. so not sure if it works even after upgrading to ubuntu 24.04. I didn't test it.
Let me add a couple of notes. - It's not a very good practice to use ttyUSB# devices. These device files can change during disconnection or reboot. I know that it is described in almost all manuals but if you're not sure what you're doing, it's better to use the Device ID file. For ICOM, the port is: /dev/serial/by-id/usb-Silicon_Labs_CP2102_USB_to_UART_Bridge_Controller_IC-7300_03018006-if00-port0 - You have to have a write permission to your Device ID file. So you must be in the appropriate group as a user. - You didn't mention what kind of problem you actually have. An error report or some description of the behavior is a good starting point to someone being able to help you.
Regards Ladislav
I hope it is OK for me to latch onto this thread. I am also having trouble getting Qlog to connect to my IC-7300 or my IC-9700. I recently installed Mint22 in dual-boot mode on my computer. I installed Qlog, but cannot get it to connect to either radio. I also have FLRig and CQRLog installed, and neither of them communicate with the rigs. I know I must be doing something stupid, but I don't know what it is. Probably not a member of the correct group or something. I have tried every /dev/ttyUSB# that I have. I know my radio is set for 115200 baud. I just can't figure it out. I am pretty much a linux neophyte, but I have had rig control working under other versions of Ubuntu.
?
Roy KW4G
|
Re: Rig control with Hamlib
I can't advise you for FLDigi or CQRLog, but I use this for IC7300 and Qlog.
Everything worked. so not sure if it works even after upgrading to ubuntu 24.04. I didn't test it.
Let me add a couple of notes. - It's not a very good practice to use ttyUSB# devices. These device files can change during disconnection or reboot. I know that it is described in almost all manuals but if you're not sure what you're doing, it's better to use the Device ID file. For ICOM, the port is: /dev/serial/by-id/usb-Silicon_Labs_CP2102_USB_to_UART_Bridge_Controller_IC-7300_03018006-if00-port0 - You have to have a write permission to your Device ID file. So you must be in the appropriate group as a user. - You didn't mention what kind of problem you actually have. An error report or some description of the behavior is a good starting point to someone being able to help you.
Regards Ladislav
toggle quoted message
Show quoted text
I hope it is OK for me to latch onto this thread. I am also having trouble getting Qlog to connect to my IC-7300 or my IC-9700. I recently installed Mint22 in dual-boot mode on my computer. I installed Qlog, but cannot get it to connect to either radio. I also have FLRig and CQRLog installed, and neither of them communicate with the rigs. I know I must be doing something stupid, but I don't know what it is. Probably not a member of the correct group or something. I have tried every /dev/ttyUSB# that I have. I know my radio is set for 115200 baud. I just can't figure it out. I am pretty much a linux neophyte, but I have had rig control working under other versions of Ubuntu.
?
Roy KW4G
|