Re: Integration with other software via inbound connections
|
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
|
