开云体育

ctrl + shift + ? for shortcuts
© 2025 开云体育
  1. BITX20
  2. Topics

Fixed: cw latency and wsjtx/flidigi sidetone

 

I have a minor update?to make zbitx work with wsjtx/fldigi/etc and fixed cw latency.
You have to update?just the raspberry zero.

From a terminal window, type this:
cd ~/sbitx
./update sbitx
this should do it
 

Thank you Ashhar for everything you have done for this project for us all! I appreciate it!


On Sat, Apr 12, 2025, 11:00 Ashhar Farhan via <farhanbox=gmail.com_at_groups.io_0p8dlwo6@...> wrote:

I have a minor update?to make zbitx work with wsjtx/fldigi/etc and fixed cw latency.
You have to update?just the raspberry zero.

From a terminal window, type this:
cd ~/sbitx
./update sbitx
this should do it
 

Tune no longer works.

Leo, AI5II

On Sat, Apr 12, 2025, 11:31 0p8dlwo6 via <0p8dlwo6=[email protected]> wrote:

Thank you Ashhar for everything you have done for this project for us all! I appreciate it!


On Sat, Apr 12, 2025, 11:00 Ashhar Farhan via <farhanbox=gmail.com_at_groups.io_0p8dlwo6@...> wrote:
I have a minor update?to make zbitx work with wsjtx/fldigi/etc and fixed cw latency.
You have to update?just the raspberry zero.

From a terminal window, type this:
cd ~/sbitx
./update sbitx
this should do it
 

I take that back?
Once I opened wsjt-x and? hit tune from there, the tune on the zbitx panel started working?

Leo, AI5II

On Sat, Apr 12, 2025, 11:00 Ashhar Farhan via <farhanbox=[email protected]> wrote:
I have a minor update?to make zbitx work with wsjtx/fldigi/etc and fixed cw latency.
You have to update?just the raspberry zero.

From a terminal window, type this:
cd ~/sbitx
./update sbitx
this should do it
 

First CW contact on YouTube
Thank you Ashar :)
?
Displayed log time is incorrect on this screen, but is correct when I view it via VNC. I'll open a bug report.
?
73
 

I'll be posting another video soon (sigh).
 

开云体育

Many thanks Farhan? !
Now it’s on the way to get really fun in CW ... just upgraded? v 3.052 , much much better.
?
73 & 76 , Jens / HB9JOI
?
+++

On Sat, Apr 12, 2025, 11:00 Ashhar Farhan via <farhanbox=gmail.com_at_groups.io_0p8dlwo6@...> wrote:

I have a minor update to make zbitx work with wsjtx/fldigi/etc and fixed cw latency.
You have to update just the raspberry zero.
?
From a terminal window, type this:
cd ~/sbitx
./update sbitx
this should do it
 

Even after the update to 3.052, working with straight keys isn't possible. There are a lot of dropouts. The "dits" at the beginning of the characters aren't sent, even with a delay of 500. This isn't right! The annoying noise from the speaker is now audible even at volume 0. It's annoying!
 

I agree...
 

You could just tell us in two lines of text what you found and put in a bug report on Github? ?It might be less stressful all around. ?
 

Here is a video with the latest fw installed in the zBitx. CW keying is improved but still poor. Note also the delay in returning to rx after transmitting:
?
?
73,
John AE5X
?
 

开云体育

Yes, it’s still missing dits. ?The full experience of detecting key closure and going all the way to transmit is not happening often enough per second. ? That would drive me nuts.

It seems that Eric demonstrated that the fix proposed works. I’m not clear why it’s not being used. (there may be some other factor that I’m not understanding) ?It is what I have going on all of my V2 units, and it’s a lot of fun!!


I think the problem with return to receive is AGC.
Perhaps it is being altered during transmit?

Gordon kx4z?



On Apr 13, 2025, at 16:09, John AE5X via groups.io <ae5x@...> wrote:

?
Here is a video with the latest fw installed in the zBitx. CW keying is improved but still poor. Note also the delay in returning to rx after transmitting:
?
?
73,
John AE5X
?
 

On Sun, Apr 13, 2025 at 03:17 PM, Gordon Gibby KX4Z wrote:
Yes, it’s still missing dits.
And, less frequently, dahs.
 

Sadly I'm now confirming same, it misses dits and dahs at as slow as 10WPM and regardless of in IAMBIC or IAMBIC B mode.

I field tested it today.. nevermind that the screen was near impossible to read, but CW was near impossible to send. I set the QSK to 650mS and it approached reasonable. Sometimes the memory keyer would work, other times it would abandon partway through the message 'cq pota de ve6lk k'
?
AGC was off.
?
 

On Sun, Apr 13, 2025 at 04:57 PM, Vince d'Eon VE6LK/AI7LK wrote:
but CW was near impossible to send
To Ashhar: twice now you've released firmware updates that you state "fix" the CW timing problems. Many CW ops realize that the problems remain. What is your criteria for claiming that the issues are fixed? Was the zBitx field tested at all before being offered for sale with CW issues that were truly terrible, making the mode inoperative? The reverse side of the test result card that comes with each zBitx claims that it is ready to go, on all modes.
 

Is the CW fix time-stamping the key closures in the interrupt handlers? ?If not, you will miss dits, as the code can't tell which key closed first, or if it missed a key closure, via polling of a global variable from a process running on a preemptive non-real-time kernel on a single core processor. ?Every time the Linux OS process dispatcher ticks, your code will have very long gaps in its polling loop. ?With IO pin time stamps, the code has enough information available to see whether it handled that time stamped event or not, and in the correct order. ?Making it much harder to miss dits.
?
The other way to solve the problem might be a hardware change. ?Poll the key inputs with one of the Pi Pico state machines, and have the Pico generate the dot dash timing.
?
73, Ron, n6ywu

1 - 16 of 16