|
Hi all
OK here's the 1_00_016 version, containing 8 bug fixes only (things that seemed wrong with 1_00_015):
- Bug fix: Was returning to the last saved band frequency after a sent message
- Bug fix: Power/SWR meter not shown in message memory transmissions
- Bug fix: Sideband selection and CW-R selection not properly cached, leading to wrong sideband reception
- Bug fix: dot, double-dot and underline of top left (VFO A/B) character not shown when WSJT-X transmits
- Bug fix: Power/SWR meter menu update interval parameter not working?properly
- Bug fix: Attempted fix for what seems to be a new extra dits affecting Iambic B
- Bug fix: Battery icon showed incorrectly, during standalone beacon mode (should not be shown)
- Bug fix: WSPR beacon display not cleared properly between waiting stage and running stage
Feedback welcomed as usual!
73 Hans G0UPL
|
Funny, I just loaded _015 a few minutes ago and noticed the extra dit in Iambic B. So far so good! Thanks!
--
72/73 de Steve, K9NUD
|
|
|
New CW bug found.? In Mode B with autospace engaged, a periodic interrupt disables the internal keyer for a few seconds. It's repeatable and it only occurs with autospace engaged.?
Perhaps others can confirm.
Paul, W9AC?
|
Hi Paul
Probably we're getting into more obscure territory thankfully. I don't know many (any!) people that use auto space. I will have a look at it. But it will certainly bother a lot less people than iambic not working or B putting in extra dits.?
73 Hans G0UPL
On Sat, Feb 10, 2024, 5:23?PM Paul Christensen < w9ac@...> wrote: New CW bug found.? In Mode B with autospace engaged, a periodic interrupt disables the internal keyer for a few seconds. It's repeatable and it only occurs with autospace engaged.?
Perhaps others can confirm.
Paul, W9AC?
|
Hans,
Yes, there's certainly no rush for an autospace fix but I wanted to bring it to your attention to include on your QMX bug list.
Paul, W9AC
|
RE: The CW "I" emanating when "E" is intended in Iambic B mode.
I can confirm this has been fixed in 016 firmware release!
Thank you Hans for your dedication!!!
side note: I really love what I'll call the "warm CW sound" of the QMX sidetone! The sidetone coming from my Yaesu FT-DX10 is OK but a tad harsh. The QMX side tone is much nicer to listen to IMHO.
73
Roy - KI0ER
|
Understood, Paul. Definitely we all want everything that claims to be in the firmware, to work properly. And semi QSK too, is also waiting for my attention.?
Any news anyone, on 016 for the latest observed keying anomalies?
73 Hans G0UPL
On Sat, Feb 10, 2024, 5:53?PM Paul Christensen < w9ac@...> wrote: Hans,
Yes, there's certainly no rush for an autospace fix but I wanted to bring it to your attention to include on your QMX bug list.
Paul, W9AC
|
Hans, one FYI on updating from 015 to 016 firmware ...
When going from 015 to 016 I did not see a factory reset, and so didn't have to reset any configuration parameters (such as VFO frequency separator, comma or dot and others). It just worked and kept my settings (which I liked).
It may be intentional, but it made me wonder if someone going from a pre-015 firmware to 016 will get the necessary Factory Reset invoked for them. I suspect your firmware update process has logic to determine when the factory reset is required. But thought I'd point this out ... just in case it needs your attention.
73?
Roy - KI0ER
|
Hi Hans. No extra dits now even with weighting at the default 500. Thank you much ... Ron
Understood, Paul. Definitely we all want everything that claims to be in the firmware, to work properly. And semi QSK too, is also waiting for my attention.?
Any news anyone, on 016 for the latest observed keying anomalies?
73 Hans G0UPL
On Sat, Feb 10, 2024, 5:53?PM Paul Christensen < w9ac@...> wrote: Hans,
Yes, there's certainly no rush for an autospace fix but I wanted to bring it to your attention to include on your QMX bug list.
Paul, W9AC
|
Hi Roy?
Hans, one FYI on updating from 015 to 016 firmware ...
When going from 015 to 016 I did not see a factory reset, and so didn't have to reset any configuration parameters (such as VFO frequency separator, comma or dot and others). It just worked and kept my settings (which I liked).
It may be intentional, but it made me wonder if someone going from a pre-015 firmware to 016 will get the necessary Factory Reset invoked for them. I suspect your firmware update process has logic to determine when the factory reset is required. But thought I'd point this out ... just in case it needs your attention.
The firmware EEPROM contents have a key which locks them to the firmware version. If someone went from any version before 015, suddenly to 016, it will automatically do a factory reset which just wipes and rewrites suitable EEPROM content.?
Even if you now went back to say 013, it would do a factory reset automatically. And then if you went forward to 016 it would do factory reset again.?
Basically every time the EEPROM contents key doesn't match the firmware version, when you power up it does a factory reset to keep you in sync.
So everything's fine :-)
73 Hans G0UPL
|
Hi Hans. No extra dits now even with weighting at the default 500. Thank you much ...
That's VERY good news...
73 Hans G0UPL
|
Oye oye oye!
After a good hour and a half of working the 30m band, I can say that all seems to be good CW wise! Yaayy :-)
Worked with 600 and 700 weight, and 22-25wpm, Iambic B, single lever paddle.
Thanks!
After the last QSO, I noticed that the PWR bar remained half-full on the screen, even there was no carrier. I shortly pressed the keyer paddle and it cleared up normally after release. Update interval is 60 and hang time 35.
Regards,
YO3GFH
op. Adrian
|
Thanks Hans, the iambic B now seems great, no hint of funny behaviour or extra dits.? The only other problem I'm having is that after a few minutes of QSO the 'G' comes on the screen and disables the tx .? Is that to do with the GPS protection and should I have the GPS protection disabled for cw?? The G goes off after a few seconds but as soon as I send a dah it comes back (it will send dits at that point).? The only way to clear it properly is to turn the power off and on.? It did happen a couple of time when I was playing with 0015 too.??
73 Peter, GM0EUL.
|
Peter,
The G coming on suggests RF getting in on the keyer input.
73
John
G4YTJ
|
Hi Peter
Yes as John said. It's an RF issue. It isn't resulted to the new firmware version. Common mode stuff again probably. If you turn GPS Protection off that will stop it though that's treating the symptoms not the cause. If you aren't planning to use GPS you have nothing to lose though.?
73 Hans G0UPL
On Sat, Feb 10, 2024, 7:47?PM Peter GM0EUL < gm0eul@...> wrote: Thanks Hans, the iambic B now seems great, no hint of funny behaviour or extra dits.? The only other problem I'm having is that after a few minutes of QSO the 'G' comes on the screen and disables the tx .? Is that to do with the GPS protection and should I have the GPS protection disabled for cw?? The G goes off after a few seconds but as soon as I send a dah it comes back (it will send dits at that point).? The only way to clear it properly is to turn the power off and on.? It did happen a couple of time when I was playing with 0015 too.??
73 Peter, GM0EUL.
|
Ok, thanks John, Hans.? If the G thing is just an RF issue I can manage it and I'll disable GPS protection for now.? CW is now completely usable and seems faultless to me.
73
Peter, GM0EUL
|
Positive feedback :-)
+ Keyer working smoothly, even mode B
+ message memories working as expected
+ power/swr meter and settings working fine, also during message playback
+ DIGI mode with LSB working (for LSB-monitoring of SSB signals)
THANK YOU
73 Willy, oe1wyc, oe3wyc
|
016 is a big improvement.? Thanks!
One thing I noticed is that if I power off and on again, the CW speed gets reset.
At power on, is it possible to have the CW speed set to the speed that was selected when the rig was turned off?
73, Mike KK7ER
|
Hi Mike.?
I'm not experiencing that issue at all. My CW speed is set to 22 wpm, and after several power cycles (I'm on 016 now), it has stayed at 22.
I'd suggest doing a manual factory reset (even though the firmware does that for you when required). I experienced an issue after upgrading, but I don't recall what it was specifically, and a manually triggered factory reset cleared up the issue.
73
Roy?
|
K9NUD-Steve
Paul Christensen
Ronald Taylor
Peter GM0EUL