RIG Control

[PY2AD]

Updates have been released, but the basics still work poorly.

RIG Control:

I have an FT-950, and if I use the Hamlib that comes with the program, when changing bands, the radio first goes to VFO-B, then back to VFO-A. This happens with every band change.

If I use FLRIG, every time I turn on FLRIG and Qlog, it completely messes up the radio's configuration.

If I use Omnirig, I lose several functions on the Qlog screen, such as power and TX indicator.

Is there any way to add this to the list of improvements?

PS. Windows 10

[foldynl]

Is there any way to add this to the list of improvements?

It may be more of a request for Hamlib. I looked into the situation there a bit and found this.

Hamlib/Hamlib#1576

It should be noted that it is primarily up to the owners of this rig to investigate the issue and prepare a fix for QLog. It is not feasible for me to debug individual rigs and their behavior when I do not own the rig. However, if a fix becomes available, is properly tested, and does not break other rigs, I will be happy to include it in QLog.

[PY2AD]

I understand, but if I knew how to solve this issue, I wouldn't even come here asking for help. I would do it myself.

Your theory that the radio owners should solve the problems is somewhat nonsensical.
We just want to use the program... if I knew how to solve the problems, I would make my own logging program.

It is the developer's responsibility to resolve user issues.

[foldynl]

I understand your frustration, but I have to clarify one important point.

QLog uses external rig-control backends such as Hamlib, FLRIG, and OmniRig. If a specific rig behaves incorrectly through one of those backends, I usually cannot diagnose or fix it without having access to that exact rig and a way to reproduce the issue. In this case I do not own an FT-950, so any fix would need help from someone who can test with that rig.

I am not saying that users must become developers. But for rig-specific problems, it is necessary that users who own the affected rig invest at least some time into investigating the issue and provide actionable feedback: what exactly they tried, which settings they used, and whether the same configuration works correctly with other software. Without this kind of feedback from users who can actually test the FT-950, the issue will not resolve itself.

For the Hamlib case, this looks related to an existing Hamlib issue: Hamlib/Hamlib#1576 Did you test it ?

If the problem is in QLog and we can identify what QLog sends incorrectly, I will fix it. If the problem is in Hamlib, FLRIG, or OmniRig, it needs to be fixed there first, or someone needs to provide a tested workaround that does not break other radios.