开云体育

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

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,

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.

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

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

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

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

Hi Ladislav, ADI import issues fixed by importing again without checking the box in the import dialog. All fine. Regarding "Spot to Rig", it is not working. Can't see any message debugging TCI input

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

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.

Thank you Ladislav Works perfect! Cheers Adam

Hi Adam, The circle map should be fixed in a new QLog v0.33.1 release together with a critical issue in rig control. Regards Ladislav pá 8. 3. 2024 v 22:35 odesílatel Adam VK4IM

Let me inform you that a hotfix QLog release v0.33.1 is finished. Changelog: - Fixed Rig Controller critical issue - Fixed Azimuthal Map issue I apologize for the inconvenience Changelog:

*Unfortunately, Critical Issue #325 <https://github.com/foldynl/QLog/issues/325> is present. The new release will be available ASAP. * I apologize for the inconvenience Regards Ladislav pá 8. 3. 2024

Thanks for your quick reply Ladislav Yes, both the online map and regular map are correct an work as expected I look forward to the next release Cheers Adam VK4IM

Hi Adam, please, see my response below. Regards Ladislav pá 8. 3. 2024 v 11:32 odesílatel Adam VK4IM <vk4im0438@...> napsal: QLog should center the circle based on the current gridsquare in

Let me inform you that a new QLog release v0.33.0 is finished. Changelog: - [NEW] - Added Rig Interface TCI - [NEW] - Callbook search can be temporarily paused - Improved DXC Mode recognition - Fixed

Hi I just installed QLog (MS WIndows) for the first time and have it working for both rig and rotor control using hamlib. Logs have been imported from LOG4OM and everything appears to be set up and

Yes, I went through a process of assessing all the major loggers on the market and felt this one was the best mix of modern design—which is very scare in this market—and features. Looking forward

Robert, I can say from my own experience that I used the comment field as an exchange, but unfortunately, it's not that convenient, especially when you need auto-increment. I understand Dave's