Timing issues remain with latest firmware for zBitx (3.051/1.06) despite claims to the contrary

Inserted characters and deleted characters are still a feature with the zBitx when loaded with the latest, greatest and most-updatest firmware (2 April).

Firmware: v3.051 and v1.06

If you don't know CW, you probably won't see/hear the problems in the video below. If you do, you will.

It is impossible to have a QSO on CW with the zBitx when using the internal keyer in either iambic mode.

Compounding the problem - but not shown here due to being on a dummy load - is the lengthy return-to-receive time...about a full second, regardless of the T/R delay dialed in.

 

.

.

World Health Organization criticises ham radio for contributing to global warming

In a statement released today, the WHO (and I don't mean Roger Daltrey) criticized ham radio's "unintentional but serious, nevertheless" contribution to the amount of CO2 being pumped annually into the Earth's atmosphere.

Director Sven Sverre, speaking from Oslo, said that, while hams are concerned with the ionosphere, we need to take note of what radio operators are doing in the name of DXpeditions and various 'OTA's.

"There is a troposphere, a stratosphere, a magnetosphere - there are spheres besides the ionosphere," said a very severe Sven Sverre.

The zBitx: Many flaws

Four days with the zBitx has been an exercise in frustration. 

Where to begin...

CW

Unusable, at least for now (30 March 2025) with v1.04 firmware. There are 3 key-type settings for CW; none work properly and all have a very lengthy return-to-receive time regardless of the T/R delay setting dialed in via the menu.

Iambic-A: I am unable to send accurate CW characters at any speed I normally use (22-26 wpm) due to inconsistent timing issues of when the radio's internal keyer inserts a dot or a dash. An "N" may come out as an "N" or as a "NE". Or a "TI" as extra dots occasionally get added to what you intended to send.

Or the opposite occurs: above 15 wpm, opposing characters of a letter are usually omitted. In other words, going from a dot to a dash (or vice versa) often results in the second character not being sent at all. An 'A' comes outs as an 'E' and an 'R' comes out as an 'A'.

I am unable to send my own callsign unless I QRS to 15 wpm or less.

Iambic-B: Operates as if each paddle of my dual-paddle key is a straight key. Depressing either side of the paddles results in a steady tone.

QMX/QMX+ now have SSB capability

A few hours ago, Hans G0UPL released beta firmware that enables SSB operation for the QMX-series of transceivers.

Furthermore, Hans is "retiring" the QSX concept since the new fw for the QMX makes that project redundant.

From Hans:

This is the beta release page for the SSB firmware for QMX/QMX+ transceivers. This is a very complex project. The beta release here is provided without warranty, for brave beta testers who wish to try out the firmware and report back on any issues found or suggested enhancements. The firmware runs on both QMX and QMX+; for convenience from now on, this page will state "QMX" but that means equivalently QMX or QMX+ unless otherwise stated.

After a period of beta testing, the firmware will be published to the regular QMX page, and the regular QMX operating manual will be updated to reflect all the changes for SSB. Eventually I will publish extensive technical documentation describing the entire system in detail. 

.

Please remember - this is beta firmware, for experimentation.

.

.

New to the radio room - a long-awaited arrival

"Every CW op should have a Ten-Tec"

Those words were spoken to me when I bought my first rig as an almost-ham in 1978 as I paid for my shiny new Century 21. The Novice ticket arrived in the mail & the Century 21 (and many hams on the other end of it) began schooling me in the art of CW.

Elecraft came onto the scene years later and my old Elmer's praise of Ten-Tec could have applied to Elecraft as well.