I am in contact with Mark. We are testing different variants of QLog. Currently it is clear that it is not the command timing from Qlog.
¨²t 3. 9. 2024 v?13:28 odes¨ªlatel Michael Morgan via <cmorgan13=
[email protected]> napsal:
I am using a Flex radio here and I am not seeing the issue either on Mac or Windows.? My son has a Yaesu 710 so I may can run up to his house this evening and test/play with it.
Michael,?
exactly this piece of code is where the potential problem is (maybe).?The bad thing about it is that I'm not able to simulate it.?I tried different CPU underclocking to see if the call order changes a behaviour (Qlog is a heavily multithreaded application).?Tested Windows/Linux...But found no issue. Qlog?works without any issue? with my IC7300.That's the bad thing, I have no idea if it's in this signal/slot order issue or if it's in Hamlib call, because Qlog sends commands very fast.?It seems that FTx users are impacted, but with different Hamlib versions (4.3, 4.5.x and even with 4.6).
I'll try to go through all the commits in release 0.38 today.?Maybe something will come to mind.?Unfortunately, there are many commits ;-(
¨²t 3. 9. 2024 v?1:42 odes¨ªlatel Michael Morgan via
??<cmorgan13=
[email protected]> napsal:
Ladislav,
I have just been looking at the code a little on this.? I think I may have traced how this is working (with the tunedx signal), I'm still trying to get my head wrapped around QT.? But it looks like QLog is setting the Mode first then the Frequency.? Wonder if it would make a difference if the frequency is changed then the mode?? Or I may not be following the code.
Michael, AA5SH
Hallo to all,
I can reproduce the behavior as described in the messages before with my rig, FT-991, under openSUSE LINUX Leap 15.6 with QLog 0.38 and 0.37.2 with Hamlib 4.6.? Hamlib 4.5.5 does not have it. So it seems to be a problem between QLog and Hamlib 4.6.
However this is not a showstopper for me. I only have to click twice if the band and mode changes.
?
73, Walter DL8FCL
