开云体育

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

so 16. 3. 2024 v?11:56 odesílatel Juanma - EA3IFV <juanma.merino@...> napsal:

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

pá 15. 3. 2024 v?19:07 odesílatel Juanma - EA3IFV <juanma.merino@...> napsal:

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,

What exactly does it mean? "TCI: Cluster to Rig not working,"

- 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.

Regards

Ladislav

?t 14. 3. 2024 v?13:29 odesílatel Juanma - EA3IFV <juanma.merino@...> napsal:

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.?

How to reproduce: Connect to cluster:?dxcluster.hb9vqq.ch:7300 enter username, enter a wrong password.

With this I'm now officially using Qlog and everything seems to be working very well.?

TCI: Cluster to Rig not working, happy to help debugging it if you tell me how, not urgent in any case since other software like SDC is taking care of that in my case.

Regards,?

Juanma - EA3IFV

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

út 12. 3. 2024 v?22:02 odesílatel Juanma - EA3IFV <juanma.merino@...> napsal:

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

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

pá 15. 3. 2024 v?19:07 odesílatel Juanma - EA3IFV <juanma.merino@...> napsal:

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,

What exactly does it mean? "TCI: Cluster to Rig not working,"

- 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.

Regards

Ladislav

?t 14. 3. 2024 v?13:29 odesílatel Juanma - EA3IFV <juanma.merino@...> napsal:

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.?

How to reproduce: Connect to cluster:?dxcluster.hb9vqq.ch:7300 enter username, enter a wrong password.

With this I'm now officially using Qlog and everything seems to be working very well.?

TCI: Cluster to Rig not working, happy to help debugging it if you tell me how, not urgent in any case since other software like SDC is taking care of that in my case.

Regards,?

Juanma - EA3IFV

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

út 12. 3. 2024 v?22:02 odesílatel Juanma - EA3IFV <juanma.merino@...> napsal:

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

Juanma,

What exactly does it mean? "TCI: Cluster to Rig not working,"

- 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.

Regards

Ladislav

?t 14. 3. 2024 v?13:29 odesílatel Juanma - EA3IFV <juanma.merino@...> napsal:

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.?

How to reproduce: Connect to cluster:?dxcluster.hb9vqq.ch:7300 enter username, enter a wrong password.

With this I'm now officially using Qlog and everything seems to be working very well.?

TCI: Cluster to Rig not working, happy to help debugging it if you tell me how, not urgent in any case since other software like SDC is taking care of that in my case.

Regards,?

Juanma - EA3IFV

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

út 12. 3. 2024 v?22:02 odesílatel Juanma - EA3IFV <juanma.merino@...> napsal:

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

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

út 12. 3. 2024 v?22:02 odesílatel Juanma - EA3IFV <juanma.merino@...> napsal:

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

Hi Juanma,

Many thanks for your feedback.

TCI was implemented without using a real rig, so I only estimated everything using the simulator. I assume that it will still need to be fine-tuned. I don't know if you use the "Spot to Rig" function. So I'm not sure if the spots are sent and displayed correctly. Otherwise, my answers to your questions are below.

Regards

Ladislav

ne 10. 3. 2024 v?17:05 odesílatel Juanma - EA3IFV <juanma.merino@...> napsal:

Hi,?

I installed Qlog 0.33.1 yesterday after realizing that TCI is now supported. It is working fine with my SunSDR2 Pro and Expert SDR 2 1.3.1.

I love the look and feel and user experience so far.?

Minor issues found, probably my fault:

1.- Importing ADI file from Log4OM contains DXCC that are not counted in awards. For instance 6O1OO (Somalia), is there, confirmed by QSL and Lotw but QLog Awards is not counting it and shows and non worked. VP8PJ was classified as Falkland Is. instead of South Orkney but editing?the QSO manually did the trick. I think I have a similar issue with Marquesas Is. Nothing serious in any case.

if QSOs are not counted in awards, then it is necessary to verify. It would be best if you send me a specific QSO in ADI format as it looked before import.

VP8PJ was classified as Falkland Is. instead of South Orkney:

Unfortunately, It is correct. I looked in the CTY file, which is the source of the DXCC Entity information, and VP8PJ was deleted on Feb 15, 2024. See detail

if you don't want DXCC to be recalculated when importing to QLog, you need to define this in the Import dialog.

What I miss:

I miss (or maybe is there but I haven't found the?way) the ability to log QSOs from other software (JTDX/WSJTX, JTAlert, Gridtracker or N1MM). Is there any option that creates a listener on QLog to send QSO data and log them?

WSJTX is supported and tested. You can define listen port and other options. See

You can forward the packet to JTAlert too.

N1MM - the question is what support means in this case. If you want to receive messages from N1MM, then QSO can be exported and imported. Why have 2 log applications running? By the way, N1MM provides very little information via the messages.

I think everything?else is just perfect and very promising. Not sure how can I help given my bad development skills but I'll be happy to take a look to the mailing list from time to time and keep testing new releases.

Everyone can contribute their ideas, help with translations (if necessary). QLog should be a community project. Even a well-thought-out and well-specified problem and its solution provide help for the project.

?

Regards,

Juanma - EA3IFV