|
Interesting phenomena with the newest release when using with the Yaesu FTDX101MP.
?
Never experienced this before, however now when I click on a DX spot, and the rig switches to the band and frequency, often the sideband (USB / LSB) is not correct for the band. For example, if I click on a spot from 20 meters, it often switches the rig over to LSB. On 40 meters often to USB. If I clink that spot several times, Qlog finally switches to the correct sideband.
?
Did not behave like this prior to the update, I haven’t changed any settings after the update and the FTDX101MP continues to operate fine with AC Log.
?
73? ?WW4DX
M Harrison
|
What OS are you using? ?I am not expierencing the same here with MacOS and my Flex 6400. ?I just bounced around a few spots and it seems to work as expected. ?Seems like maybe a HamLib issue but not 100% sure.
73
toggle quoted message
Show quoted text
On Aug 31, 2024, at 2:33?AM, WW4DX via groups.io <WW4DX@...> wrote:
[Edited Message Follows]
Interesting phenomena with the newest release when using with the Yaesu FTDX101MP. ?
Never experienced this before, however now when I click on a DX spot, and the rig switches to the band and frequency, often the sideband (USB / LSB) is not correct for the band. For example, if I click on a spot from 20 meters, it often switches the rig over to LSB. On 40 meters often to USB. If I clink that spot several times, Qlog finally switches to the correct sideband. ?
Did not behave like this prior to the update, I haven’t changed any settings after the update and the FTDX101MP continues to operate fine with AC Log. ?
73? ?WW4DX M Harrison
|
|
|
After more testing I have discovered that the rig switches to the wrong sideband ONLY when bands are being changed.
?
Example. If the rig is on 20m USB, and I click on a DX spot that is on 20m. All is fine. However if my rig is on 20m USB, and I click on a 40m spot, the rig switches to the 40m band, however the rig remains on USB. If I then re-click the same spot several times, the rig eventually changes to LSB.
?
I have rechecked all the equipment setting against the setting I use in AC Log. They are exactly the same. AC Log does not have this issue, neither did I prior to the upgrade.
?
Is it possible to downgrade to the previous version of QLog without loosing my current setting?
?
Thanks
WW4DX
?
?
|
UPDATE..
?
I just installed QLog on a PC running Win 10. Connected my Yaesu FTDX101MP via a USB cable. Setup the Rig Control, without any issues. QLog is seeing and controlling my transceiver.?
?
Experiencing the same exact problem as when using QLog in Linux Mint. Wrong sideband is selected using the DX Spot window, if changing bands.
?
If I'm on 20 meters USB and select a DX Spot that is on 20 meters all is fine. However if I'm on 20 meters and select a spot that is on 40, 75, or 160, the rig switches to the correct band, however USB instead of LSB being selected.?
?
Rig operates fine with AC Log using Linux Mint (WINE) or AC Log in Windows 10. The correct sideband is always selected.?
?
Did not have this issue prior to the 0.38 upgrade..
?
Possible to downgrade back to 0.37???
?
Thanks
WW4DX
?
|
I am sorry but an easy downgrade is not possible for this release because there were database changes that caused database schema migration and revert is not possible.
I am investigating why this could happen.
Regards Ladislav
UPDATE..
?
I just installed QLog on a PC running Win 10. Connected my Yaesu FTDX101MP via a USB cable. Setup the Rig Control, without any issues. QLog is seeing and controlling my transceiver.?
?
Experiencing the same exact problem as when using QLog in Linux Mint. Wrong sideband is selected using the DX Spot window, if changing bands.
?
If I'm on 20 meters USB and select a DX Spot that is on 20 meters all is fine. However if I'm on 20 meters and select a spot that is on 40, 75, or 160, the rig switches to the correct band, however USB instead of LSB being selected.?
?
Rig operates fine with AC Log using Linux Mint (WINE) or AC Log in Windows 10. The correct sideband is always selected.?
?
Did not have this issue prior to the 0.38 upgrade..
?
Possible to downgrade back to 0.37???
?
Thanks
WW4DX
?
|
Can you please send me an example of a spot for which it does not work for you? Is it a PHONE spot? Can you send an example of what the spot had in COMMENTS?
I am sorry but an easy downgrade is not possible for this release because there were database changes that caused database schema migration and revert is not possible.
I am investigating why this could happen.
Regards Ladislav
UPDATE..
?
I just installed QLog on a PC running Win 10. Connected my Yaesu FTDX101MP via a USB cable. Setup the Rig Control, without any issues. QLog is seeing and controlling my transceiver.?
?
Experiencing the same exact problem as when using QLog in Linux Mint. Wrong sideband is selected using the DX Spot window, if changing bands.
?
If I'm on 20 meters USB and select a DX Spot that is on 20 meters all is fine. However if I'm on 20 meters and select a spot that is on 40, 75, or 160, the rig switches to the correct band, however USB instead of LSB being selected.?
?
Rig operates fine with AC Log using Linux Mint (WINE) or AC Log in Windows 10. The correct sideband is always selected.?
?
Did not have this issue prior to the 0.38 upgrade..
?
Possible to downgrade back to 0.37???
?
Thanks
WW4DX
?
|
?
?
?
Transceiver is on 20M USB.
?
?
?
?
Spot I clicked on is GX8DD/P 09:26:07AM 7.195 PHONE
?
?
?
?
Transceiver switches to 40 meters, but remains on USB..
?
?
?
?
?
If rapidly re-click on the spot, 4 or 5 times, the rig finally switches over to LSB.
?
?
?
?
?
Previously with build 0.37, a double click on the spot would set everything on the rig correctly.
?
Also works as expected in AC Log in Linux and Win 10.
?
?
?
|
|
|
|
|
Please, could you try to set the option as described below?
"It is in the CW setting section, CW Mode, and is called CW FREQ DISPLAY
By default it is in "PITCH OFFSET" but if it is set to "DIRECT FREQ"
there is no longer any frequency modification when changing the radio
mode. What you saw in the video, when changing from LSB to USB was not a QLOG
thing, it was because of this option. I also saw that it was changing
through the screen of the radio itself."
please, could you also check if your rig does not contain other such "improvements"
Regards Ladislav
|
Mine is set to "Pitch Offset".?
?
As for other improvements I don't follow you.
?
Worked as expected with 0.37, and the transceiver continues to work perfect with AC Log in both Linux and Win10.
?
I'm stumped...?
|
BTW, I have made no menu changes to any setting of the FTDX101MP in months. So I'm confident it's not a setting error with the radio, since it worked perfectly in 0.37
?
|
I know that you wrote it workrf under 0.37 and with AC Log but I'm looking for an issue. What I can tell you is that no changes have been made to the code for recognizing and setting the mode from DX Spot. But QLog is event-driven software. It is possible that it behaves differently on your PC than on others. I have to find out why. But since I don't have FT rig for testing, I need to eliminate all possible other factors.
Have you tried changing the settings? What was the result
[Edited Message Follows]
Mine is set to "Pitch Offset".?
?
As for other improvements I don't follow you.
?
Worked as expected with 0.37, and the transceiver continues to work perfect with AC Log in both Linux and Win10.
?
I'm stumped...?
|
BTW It seems that ACLog uses a different Rig interface, therefore that information is not needed for QLog. po 2. 9. 2024 v?13:31 odesílatel Ladislav Foldyna < ok1mlg@...> napsal:
I know that you wrote it workrf under 0.37 and with AC Log but I'm looking for an issue. What I can tell you is that no changes have been made to the code for recognizing and setting the mode from DX Spot. But QLog is event-driven software. It is possible that it behaves differently on your PC than on others. I have to find out why. But since I don't have FT rig for testing, I need to eliminate all possible other factors.
Have you tried changing the settings? What was the result
[Edited Message Follows]
Mine is set to "Pitch Offset".?
?
As for other improvements I don't follow you.
?
Worked as expected with 0.37, and the transceiver continues to work perfect with AC Log in both Linux and Win10.
?
I'm stumped...?
|
Changed to "DIRECT FREQ".?
?
Power cycled rig.? Rebooted PC.?
?
Same result.
?
Thanks
?
|
I can just multiple click the spot until it changes to the correct mode.??
?
I'll keep up with the updates, and maybe something will fix it.
?
Thanks for all you do....
?
WW4DX
|
I wonder if this is a Hamlib bug - but doesn't make sense if it worked previously.? I see where the latest Hamlib shows the updates for a few months ago for the 101.? But one thing maybe to try is to raise your update frequency from 100ms to like 500ms to just see if something is colliding or something.
|
I sure did raise it to 500ms yesterday. ? Same problem. ?Changed it back for to 100ms.?
Thanks!
|
100ms is also unusual for me. Although Hamlib doesn't handle it this quickly, the setting hasn't changed, as Mark mentioned.
Mark, are you using flatpak or deb package? We could try to debug directly via the trace file, but it requires your cooperation and patience.Is it possible to send you a private email with instructions on how to generate a trace file?
I sure did raise it to 500ms yesterday. ? Same problem.? Changed it back for to 100ms.?
Thanks!
|
WW4DX