I was looking at qLog as a potential solution for me for a cross platform situation.? I bounce around devices I use to operate from.? I use Flex Radios so I am not having to directly link to radios an all, so I operate quite often from one of 4 devices (3 Macs and a windows laptop).? I would like to store my logfile in my dropbox folder so the logfile will follow me around between devices.? I don't see a way right off to specify the location of the log file(s).? On my Mac I honestly haven't been able to locate where it is stored.? Is there a way to specify where the data files are stored?
So far I really like the software although I have only spent a hour or so with it.? I like the filter options in the DXCluster.? I think many loggers really miss the mark with that.??
73's
Michael, AA5SH
|
Attention MacOS users - CVE-2024-3094 (XZ backdoor)
Attention MacOS users: QLog was affected by CVE-2024-3094 (XZ backdoor). I have prepared a new package that fixes this issue. Please download from QLog releases section (QLog-0.34.0-2_MacOs_dmg.zip)
|
Hello Jose,
plase, see my response
If you want to play with the database, the database is stored in the same directory as the backup ().
I would not recommend you to perform any changes in the internal database without knowledge of the internal processes in QLog.
Regards Ladislav
What is the path of the database in Linux? and Windows ???
I need to create some databases to differents callsigns for activities..
|
What is the path and name of database in Windows and Linux ??
?
I need to create a differents databases for activations.
73
EA5SW
|
What is the path of the database in Linux? and Windows ???
I need to create some databases to differents callsigns for activities..
|
What is the path of the database in Linux? and Windows ???
I need to create some databases to differents callsigns for activities..
|
Let me inform you that a new QLog release v0.34.0 is finished.
Changelog:
- [NEW] - Rotator Widget - Azimuth by Clicking
- [NEW] - Rotator Widget - QSO button provides Short/Long Path (issue #330)
- [NEW] - Equipment Menu - Added Keep Options between application restart (issue #331)
- Fixed TCI - Thetis Connection issue (issue #327)
- Fixed TCI - Spots To Rig are not displayed (issue #328)
- Fixed Bandmap unintentionally emits frequency labels (issue #333)
- Fixed Failing to load grid square for G and EI SOTA summits (issue #336)
- Fixed HRDLog On-Air message is not sent (issue #337)
- Fixed Offline Map - Improved Path drawing
?
Changelog:
|
Re: HRDlog On-Air message - Not sending
Hello Adam,
Unfortunately, I found an error that I had introduced there during the migration to the new Rig architecture. I will fix it.
Regards
Ladislav
|
HRDlog On-Air message - Not sending
Hi Ladislav
I must be doing something wrong. I have ticked the box here File→ Settings→ Sync & QSL→ HRDLog
The upload code has been included along with my call sign in the required fields. But I can not get the 'On Air" icon to show up on my QRZ page using the script generated from HRDlog.net site.
The feature works from LOG4OM
Cheers
VK4IM Adam
|
Hi Adam,
Yes, it makes sense. I'll add it.
Regards Ladislav
ne 17. 3. 2024 v?8:37 odesílatel Adam VK4IM < vk4im0438@...> napsal:
Hi
When a call sign is entered into the call sign field QLog reports the short path distance in the Info box. This information is sent to the rotator control panel. By clicking the "QSO" button in the rotator control panel, the antenna will rotate to the short path for that station.
Is it possible to offer both short path and long path options in the rotator control box as not every contact is via the short path?
73
Adam VK4IM
|
Hi
When a call sign is entered into the call sign field QLog reports the short path distance in the Info box. This information is sent to the rotator control panel. By clicking the "QSO" button in the rotator control panel, the antenna will rotate to the short path for that station.
Is it possible to offer both short path and long path options in the rotator control box as not every contact is via the short path?
73
Adam VK4IM
|
Re: Integration with other software via inbound connections
Use blue or red which may work on both black and white themes. Black is a bad idea because expertsdr default background is black or dark Grey. .?
El sáb, 16 mar 2024, 18:00, ok1mlg < ok1mlg@...> escribió: Many thanks for sending the log from SDC. It was very helpful. It confirms my assumption. Just one additional question. I assume that the Spots were black. The Thetis theme is dark. Is it readable to have a dark theme with black Callsings? Please, could you send me a screenshot of what it looks like?
Regards Ladislav
Hi Ladislav,
?
I can try recompiling it but the last time I
compiled?something?I used?Borland C and the Euro was not yet a
currency.
?
I've been comparing the spot format from with those sent by QLog. I think this?will provide you the information
you need.?
?
These
are spots sent from SDC and properly shown on the panorama
spot:CE0YHF,CW,50313000,4278190080,CE0YHF;
spot:W2GGI,CW,28400000,4278190080,W2GGI;
spot:CA4WLD,CW,28497000,4278190080,CA4WLD;
spot:command ,CW,0,4278190080,command ;
spot:de ,CW,0,4278190080,de ;
spot:KE5RJJ,CW,14320000,4278190080,KE5RJJ;
spot:LU3HV,CW,28500000,4278190080,LU3HV;
?
And these are spots sent by Qlog and not shown in the
panorama
SPOT:J38R,LSB,7180000,2012390,;
MODULATION:0,LSB;
VFO:0,0,7180000;
SPOT:CE3QY,USB,14255000,2012390,;
SPOT:N4WFU,LSB,7128000,15790320,;
SPOT:N4WFU,LSB,7128000,15790320,;
?
Regards,?
On Fri, Mar 15, 2024 at 8:22?PM ok1mlg < ok1mlg@...> wrote: Unfortunately, I think it's a QLog issue. I analyzed your screenshot and QLog code and I think I misunderstood the SPOT command specification. It seems that the information about the color is being sent incorrectly, and as you can see, even your SW that you are using is sending this information incorrectly
I'm not sure if you are able to recompile QLog from source, but the fix is probably simple. Please let me know if you can recompile QLog, I would send you the patch for testing.
Regards Ladislav
Hi, I can see the messages in the TCI inbound debug log of the ExpertSDR2, so it is not a Qlog problem.? Other software is sending spots in the same way and they aren't there?neither.? I'll dig deeper. For now you can consider it a false positive bug :-)
Regards,
On Fri, Mar 15, 2024 at 3:15?PM ok1mlg < ok1mlg@...> wrote: Juanma, - have you enabled this feature and no spots are displayed?
- Does mode is incorrectly detected?
Keep in mind, according to the QLog wiki, only "filtered" DX spots are
sent to the rig. If you have enabled the DXC filter, then QLog sends to
the rig only those spots that match your filter criteria. In other words, only QSOs that are displayed on the Bandmap are sent to the rig.
Hi Ladislav and all,?
1) There are good reasons to accept ADIF from other software in the days of JTAlert, Gridtracker and other companion software to JTDX/WSJT-X, but don't worry I managed to get it to work. I explain below.? 2) N1MM, understood. It is not a priority and a manual import of ADIF after a contest is acceptable.?
I wanted to make Qlog work with JTDX?+ JTALERT but I had some issues using UDP forward (unicast) so I could fix it enabling multicast on all three softwares (JTDX, JTAlert and Qlog) and now everything is working great.?
I've published a blog post in case it helps other Qlog users. Feel free to use the content on the Wiki if you think that will be helpful for others.?
I take the opportunity to report a small bug. Qlog 0.33.1 - Software closes after failed cluster authentication.?
On Wed, Mar 13, 2024 at 4:13?PM ok1mlg < ok1mlg@...> wrote: Juanma,
QLog already accepts QSO Log records from WSJT-X and can also forward packets from WSJT-X via QLog to the 3rd party software.
I thought about the integration of N1MM, but did not implement it because there are several things
1) As I wrote, currently I see no reason to receive messages from another log via another format that imports ADIF
2) Unfortunately, the N1MM UDP message format is not well-specified. There is a sample message, but it does not contain the specification of field values. With all respect to the N1MM authors, they have done a lot of work, probably most users cannot imagine how much work they have done, but when specifying the protocol, it is necessary to specify the field values as well. What does RadioInterfaced, IsRunQSO, etc. mean? What values can contain?
3) The N1MM UDP message contains only a very small amount of information.
4) It is possible to export from N1MM and import to QLog
Based on these points, I made a decision that QLog will not accept these N1MM online messages now.
I'm always writing. Everything can change, but currently there are other priorities in Qlog development.
Regards Ladislav
Hi all,
Following from the previous thread and how to integrate N1MM by accepting UDP messages sent from that software to Qlog, I've been reviewing the Wiki and I can see the documentation for the "Notifications" option in the setup is to send out/forward udp packets from Qlog to other software.? My doubt is, Is there a feature to listen to and parse inbound UDP packets? That is how other loggers integrate with different?software for qso logging purposes. Not just N1MM but JTAlert, GridTracker, JTDX/WSJT-X, all work that way (in some cases these other loggers also parse in real-time the third party log but I think UDP listeners are more convenient than log file parsing.?
For instance, I see there's an integration developed for WSJT-X that allows to see within Qlog stations calling CQ, but I'm not sure is that integration allows WSJT-X to log the QSO on Qlog once completed if the qso has been initiated and completed from WSJT-X and not from within Qlog.?
I think an important improvement that will increase Qlog adoption is the possibility to receive and parse different types of messages via UDP.?
Regards, Juanma - EA3IFV
|
Re: Problem with OmniRig V2.1
Hi Latislav,
This release now works as expected with OmniRig V2.
Many thanks for the quick turnaround on this fix.
As FYI Hamlib for the FT2000 still doesn't work, no problem for me, just letting you know.
--
73's de Dave, G8FXM
|
Re: Integration with other software via inbound connections
Many thanks for sending the log from SDC. It was very helpful. It confirms my assumption. Just one additional question. I assume that the Spots were black. The Thetis theme is dark. Is it readable to have a dark theme with black Callsings? Please, could you send me a screenshot of what it looks like?
Regards Ladislav
Hi Ladislav,
?
I can try recompiling it but the last time I
compiled?something?I used?Borland C and the Euro was not yet a
currency.
?
I've been comparing the spot format from with those sent by QLog. I think this?will provide you the information
you need.?
?
These
are spots sent from SDC and properly shown on the panorama
spot:CE0YHF,CW,50313000,4278190080,CE0YHF;
spot:W2GGI,CW,28400000,4278190080,W2GGI;
spot:CA4WLD,CW,28497000,4278190080,CA4WLD;
spot:command ,CW,0,4278190080,command ;
spot:de ,CW,0,4278190080,de ;
spot:KE5RJJ,CW,14320000,4278190080,KE5RJJ;
spot:LU3HV,CW,28500000,4278190080,LU3HV;
?
And these are spots sent by Qlog and not shown in the
panorama
SPOT:J38R,LSB,7180000,2012390,;
MODULATION:0,LSB;
VFO:0,0,7180000;
SPOT:CE3QY,USB,14255000,2012390,;
SPOT:N4WFU,LSB,7128000,15790320,;
SPOT:N4WFU,LSB,7128000,15790320,;
?
Regards,?
On Fri, Mar 15, 2024 at 8:22?PM ok1mlg < ok1mlg@...> wrote: Unfortunately, I think it's a QLog issue. I analyzed your screenshot and QLog code and I think I misunderstood the SPOT command specification. It seems that the information about the color is being sent incorrectly, and as you can see, even your SW that you are using is sending this information incorrectly
I'm not sure if you are able to recompile QLog from source, but the fix is probably simple. Please let me know if you can recompile QLog, I would send you the patch for testing.
Regards Ladislav
Hi, I can see the messages in the TCI inbound debug log of the ExpertSDR2, so it is not a Qlog problem.? Other software is sending spots in the same way and they aren't there?neither.? I'll dig deeper. For now you can consider it a false positive bug :-)
Regards,
On Fri, Mar 15, 2024 at 3:15?PM ok1mlg < ok1mlg@...> wrote: Juanma, - have you enabled this feature and no spots are displayed?
- Does mode is incorrectly detected?
Keep in mind, according to the QLog wiki, only "filtered" DX spots are
sent to the rig. If you have enabled the DXC filter, then QLog sends to
the rig only those spots that match your filter criteria. In other words, only QSOs that are displayed on the Bandmap are sent to the rig.
Hi Ladislav and all,?
1) There are good reasons to accept ADIF from other software in the days of JTAlert, Gridtracker and other companion software to JTDX/WSJT-X, but don't worry I managed to get it to work. I explain below.? 2) N1MM, understood. It is not a priority and a manual import of ADIF after a contest is acceptable.?
I wanted to make Qlog work with JTDX?+ JTALERT but I had some issues using UDP forward (unicast) so I could fix it enabling multicast on all three softwares (JTDX, JTAlert and Qlog) and now everything is working great.?
I've published a blog post in case it helps other Qlog users. Feel free to use the content on the Wiki if you think that will be helpful for others.?
I take the opportunity to report a small bug. Qlog 0.33.1 - Software closes after failed cluster authentication.?
On Wed, Mar 13, 2024 at 4:13?PM ok1mlg < ok1mlg@...> wrote: Juanma,
QLog already accepts QSO Log records from WSJT-X and can also forward packets from WSJT-X via QLog to the 3rd party software.
I thought about the integration of N1MM, but did not implement it because there are several things
1) As I wrote, currently I see no reason to receive messages from another log via another format that imports ADIF
2) Unfortunately, the N1MM UDP message format is not well-specified. There is a sample message, but it does not contain the specification of field values. With all respect to the N1MM authors, they have done a lot of work, probably most users cannot imagine how much work they have done, but when specifying the protocol, it is necessary to specify the field values as well. What does RadioInterfaced, IsRunQSO, etc. mean? What values can contain?
3) The N1MM UDP message contains only a very small amount of information.
4) It is possible to export from N1MM and import to QLog
Based on these points, I made a decision that QLog will not accept these N1MM online messages now.
I'm always writing. Everything can change, but currently there are other priorities in Qlog development.
Regards Ladislav
Hi all,
Following from the previous thread and how to integrate N1MM by accepting UDP messages sent from that software to Qlog, I've been reviewing the Wiki and I can see the documentation for the "Notifications" option in the setup is to send out/forward udp packets from Qlog to other software.? My doubt is, Is there a feature to listen to and parse inbound UDP packets? That is how other loggers integrate with different?software for qso logging purposes. Not just N1MM but JTAlert, GridTracker, JTDX/WSJT-X, all work that way (in some cases these other loggers also parse in real-time the third party log but I think UDP listeners are more convenient than log file parsing.?
For instance, I see there's an integration developed for WSJT-X that allows to see within Qlog stations calling CQ, but I'm not sure is that integration allows WSJT-X to log the QSO on Qlog once completed if the qso has been initiated and completed from WSJT-X and not from within Qlog.?
I think an important improvement that will increase Qlog adoption is the possibility to receive and parse different types of messages via UDP.?
Regards, Juanma - EA3IFV
|
Re: Problem with OmniRig V2.1
Dave,
a new installation package fixes the issue. You can find the package in the QLog's Release section.
just make sure the omnirig doesn't take too long to start. This can be achieved by reducing the number of loaded INI files. Otherwise, QLog reports that the connection to Rig cannot be established. You can also optimize it by starting Omnirig manually before QLog.
I hope it will work now.
Regards Ladislav
so 16. 3. 2024 v?11:39 odesílatel Dave, G8FXM < webmaster@...> napsal:
Many thanks Latislav.
--
73's de Dave, G8FXM
|
Re: Integration with other software via inbound connections
Hi Ladislav,
?
I can try recompiling it but the last time I
compiled?something?I used?Borland C and the Euro was not yet a
currency.
?
I've been comparing the spot format from with those sent by QLog. I think this?will provide you the information
you need.?
?
These
are spots sent from SDC and properly shown on the panorama
spot:CE0YHF,CW,50313000,4278190080,CE0YHF;
spot:W2GGI,CW,28400000,4278190080,W2GGI;
spot:CA4WLD,CW,28497000,4278190080,CA4WLD;
spot:command ,CW,0,4278190080,command ;
spot:de ,CW,0,4278190080,de ;
spot:KE5RJJ,CW,14320000,4278190080,KE5RJJ;
spot:LU3HV,CW,28500000,4278190080,LU3HV;
?
And these are spots sent by Qlog and not shown in the
panorama
SPOT:J38R,LSB,7180000,2012390,;
MODULATION:0,LSB;
VFO:0,0,7180000;
SPOT:CE3QY,USB,14255000,2012390,;
SPOT:N4WFU,LSB,7128000,15790320,;
SPOT:N4WFU,LSB,7128000,15790320,;
?
Regards,?
On Fri, Mar 15, 2024 at 8:22?PM ok1mlg < ok1mlg@...> wrote: Unfortunately, I think it's a QLog issue. I analyzed your screenshot and QLog code and I think I misunderstood the SPOT command specification. It seems that the information about the color is being sent incorrectly, and as you can see, even your SW that you are using is sending this information incorrectly
I'm not sure if you are able to recompile QLog from source, but the fix is probably simple. Please let me know if you can recompile QLog, I would send you the patch for testing.
Regards Ladislav
Hi, I can see the messages in the TCI inbound debug log of the ExpertSDR2, so it is not a Qlog problem.? Other software is sending spots in the same way and they aren't there?neither.? I'll dig deeper. For now you can consider it a false positive bug :-)
Regards,
On Fri, Mar 15, 2024 at 3:15?PM ok1mlg < ok1mlg@...> wrote: Juanma, - have you enabled this feature and no spots are displayed?
- Does mode is incorrectly detected?
Keep in mind, according to the QLog wiki, only "filtered" DX spots are
sent to the rig. If you have enabled the DXC filter, then QLog sends to
the rig only those spots that match your filter criteria. In other words, only QSOs that are displayed on the Bandmap are sent to the rig.
Hi Ladislav and all,?
1) There are good reasons to accept ADIF from other software in the days of JTAlert, Gridtracker and other companion software to JTDX/WSJT-X, but don't worry I managed to get it to work. I explain below.? 2) N1MM, understood. It is not a priority and a manual import of ADIF after a contest is acceptable.?
I wanted to make Qlog work with JTDX?+ JTALERT but I had some issues using UDP forward (unicast) so I could fix it enabling multicast on all three softwares (JTDX, JTAlert and Qlog) and now everything is working great.?
I've published a blog post in case it helps other Qlog users. Feel free to use the content on the Wiki if you think that will be helpful for others.?
I take the opportunity to report a small bug. Qlog 0.33.1 - Software closes after failed cluster authentication.?
On Wed, Mar 13, 2024 at 4:13?PM ok1mlg < ok1mlg@...> wrote: Juanma,
QLog already accepts QSO Log records from WSJT-X and can also forward packets from WSJT-X via QLog to the 3rd party software.
I thought about the integration of N1MM, but did not implement it because there are several things
1) As I wrote, currently I see no reason to receive messages from another log via another format that imports ADIF
2) Unfortunately, the N1MM UDP message format is not well-specified. There is a sample message, but it does not contain the specification of field values. With all respect to the N1MM authors, they have done a lot of work, probably most users cannot imagine how much work they have done, but when specifying the protocol, it is necessary to specify the field values as well. What does RadioInterfaced, IsRunQSO, etc. mean? What values can contain?
3) The N1MM UDP message contains only a very small amount of information.
4) It is possible to export from N1MM and import to QLog
Based on these points, I made a decision that QLog will not accept these N1MM online messages now.
I'm always writing. Everything can change, but currently there are other priorities in Qlog development.
Regards Ladislav
Hi all,
Following from the previous thread and how to integrate N1MM by accepting UDP messages sent from that software to Qlog, I've been reviewing the Wiki and I can see the documentation for the "Notifications" option in the setup is to send out/forward udp packets from Qlog to other software.? My doubt is, Is there a feature to listen to and parse inbound UDP packets? That is how other loggers integrate with different?software for qso logging purposes. Not just N1MM but JTAlert, GridTracker, JTDX/WSJT-X, all work that way (in some cases these other loggers also parse in real-time the third party log but I think UDP listeners are more convenient than log file parsing.?
For instance, I see there's an integration developed for WSJT-X that allows to see within Qlog stations calling CQ, but I'm not sure is that integration allows WSJT-X to log the QSO on Qlog once completed if the qso has been initiated and completed from WSJT-X and not from within Qlog.?
I think an important improvement that will increase Qlog adoption is the possibility to receive and parse different types of messages via UDP.?
Regards, Juanma - EA3IFV
|
Re: Problem with OmniRig V2.1
Many thanks Latislav.
--
73's de Dave, G8FXM
|
Re: Problem with OmniRig V2.1
Dave,
I did some research and found out that this is a QLog issue. To be precise, it's not an issue in the source code, but it is an issue in the process of preparing the QLog package for Windows - I compiled it against the wrong version of the QT library on Windows platform.
I will try to release a new exe file by the end of the day.
Regards Ladislav
pá 15. 3. 2024 v?22:42 odesílatel Dave, G8FXM < webmaster@...> napsal:
Hi Latislav,
I have;
- Launched Omnirig before QLog
- Attempted to connect the Rig from QLog.
However the problem persists.
I can connect to OmniRig using the OmniRig Client successfully.
Please let me know how I can assist in debugging this issue?
--
73's de Dave, G8FXM
|
Re: Problem with OmniRig V2.1
Hi Latislav, I have;
- Launched Omnirig before QLog
- Attempted to connect the Rig from QLog.
However the problem persists. I can connect to OmniRig using the OmniRig Client successfully. Please let me know how I can assist in debugging this issue? -- 73's de Dave, G8FXM
|
Re: Problem with OmniRig V2.1
Hi Dave, I apologize for the inconvenience. Unfortunately, it seems the solution isn't working as expected. When I attempted it, I did not see this issue. Please, could you perform the following sequence?
- Launch Omnirig before QLog
- Attempt to connect the Rig from QLog.
Kindly let me know the outcome of these steps. If the issue persists, I can provide instructions for generating a debug log, which may help me diagnose the problem more accurately.
Regards Ladislav
pá 15. 3. 2024 v?20:06 odesílatel Dave, G8FXM < webmaster@...> napsal:
I'm having a problem connecting the latest version QLog to OmniRig v2.1.
9 times out of 10 connection attempt cause QLog to crash i.e. close unexpectedly. On the odd occasion it doesn't crash, connection hangs.
Anyone else seeing this issue?
--
73' s de Dave, G8FXM
|
Jose - EA5SW
Dave, G8FXM