Gordon and everyone -
You might be right. I don't have a zbitx, but looking in the zbitx repository, sbitx_gtk.c has code around line #4301 that looks like where the change worked on the sbitx. Looks like there have been some changes to ui_tick() and I can't say if this will be effective - but I would try it!
Good luck.
--
Mike KB2ML
|
Ron it looks like ui_tick does not have the improvements that we have mostly added to everybody’s code to make CW work that were proposed by Johnshoy
?
?
if my understanding is correct, that oversight should be corrected.
?
?
Gordon kx4z?
?
?
|
You might want to look at the Winkeyer by Hamcrafters.? This can
take a string of characters from a host system, read them into an
internal buffer, and handle correct output timing.
Gerry Sherman
On 2025-03-31 01:11, Ron, N6YWU via
groups.io wrote:
toggle quoted message
Show quoted text
If the current source code posted is up-to-date, I don't
think an external keyer will help. ?
?
The pin connected to the key input is being polled within a
GUI process by code in sbitx_gtk.c .
?Normal processes running on a loaded non-real-time Linux
kernel on a single-core Raspberry Pi can have maybe up to 20
milliseconds or more latency when polled without interrupt
handlers or kernel mods. ?This is a bit too long for decent CW
keying at common WPM speeds. ?The key input handling could
perhaps better be done in an interrupt routine, or using
pigpio time-stamps to de-jitter the timing. ?Or possibly with
some real-time kernel modifications to the standard Raspberry
Pi Linux distribution.
?
73, Ron,
N6YWU
|
If the current source code posted is up-to-date, I don't think an external keyer will help. ?
?
The pin connected to the key input is being polled within a GUI process by code in sbitx_gtk.c . ?Normal processes running on a loaded non-real-time Linux kernel on a single-core Raspberry Pi can have maybe up to 20 milliseconds or more latency when polled without interrupt handlers or kernel mods. ?This is a bit too long for decent CW keying at common WPM speeds. ?The key input handling could perhaps better be done in an interrupt routine, or using pigpio time-stamps to de-jitter the timing. ?Or possibly with some real-time kernel modifications to the standard Raspberry Pi Linux distribution.
?
73, Ron, N6YWU
|
Purchasing has been paused while they catch-up from the flood of orders they had in the initial release?
Hi friends,
?I’m new to these forums and I’m having problems navigating this app; I really don’t know where things are. Please, if anybody could point me in the right direction on how to purchase the Zbitx? A link would be helpful.?
thank you so much,
asis?
|
Hi friends,
?I’m new to these forums and I’m having problems navigating this app; I really don’t know where things are. Please, if anybody could point me in the right direction on how to purchase the Zbitx? A link would be helpful.?
thank you so much,
asis?
|
Hi Dean,
?
You may boot the rig from the USB pendrive if you change the boot order in your Pi.
?
In the terminal session, you may run "sudo raspi-config", and in the "advanced settings" you may change the boot order so that USB is tried before SD.
In my case, I had to update the rpi-eeprom package (otherwise the raspi-config complained: "no eeprom bin file found for version 2023-01-11").
?
In that way you may test if the new version solves your issues without disassembling the rig.
You may even replace the content of the SD card, when running from the pendrive.
?
73,
Wojtek
?
PS I described that procedure in /g/BITX20/message/116658
|
Gyula,
?
Here is my plan. I am going to burn a new image on a new 32G card.
?
Open the sBitx and remove the card in the Pi
?
Replace the new card with sb64p3 into the Pi
?
Restart rig
?
How does that sound?
?
Dean
|
|
|
./update gives 3.021, not 3.05
|
I ran into this issue as well. See issue #2. I also am still having a difficulty getting FT8 to use the decode selected by clicking the encoder. Something?is definitely better because it is no longer locking the radio process on my zBitX when the encoder is used to select a decode, instead, it does absolutely nothing at all.
See new issue #1 on Github.
We're homing in on it, it's very close to working right! (At least on my radio. Of course, Finagle's First Law, "The perversity of the Universe tends to the maximum.", means that it's somehow possible for it to be working JUST FINE on someone else's radio, but MINE wants to be SPECIAL and isn't working.)
-=-=-=-=-=-=-=-=- 73, Gwen, NG3P
|
Using sBitx v3 with various firmwares without disassembling (also upgrading to 64 bit version)
I wanted to check the 64 bit version without disassembling my sBitx v3. It was possible via changing the boot order. The procedure is quite simple.
Just run "raspi-config" utility (in the terminal session and via "sudo"). Then in the advanced options you may set the boot order so that the USB disk is tried before the SD card.
With that I could boot my sBitx v3 from the 64-bit version installed (with dd) on the USB pendrive.
After successful testing, I could backup the original SD card. I have done it via dd, sending the output to the file on my server (mounted via sshfs).
I made a separate copy of the whole /home/pi/sbitx to recover the hardware calibration and my settings.
Finally I could install the 64 bit version with:
?
$ sudo bash
# wget -O - | dd of=/dev/mmcblk0 bs=4M status=progress
?
(172.19.1.1 is the IP of my server, where I have started an ad-hoc http server running "python3 -m http.server" in a directory where sb64p3.img was downloaded.)
After that I could mount the /dev/mmcblk0p2 partition and copy the saved configuration files.
The whole testing and installation was possible without disassembling the sBitx v3.
?
73,
Wojtek SP5DAA
?
|
Re: ZBitx hangs on startup
Updated RPI and then was able to update zBitx SW.
All is well now.
Tnx,
Tom KT4XN
toggle quoted message
Show quoted text
Can you past the error or warning you got when you attempted to do the update ?
On Sat, Mar 29, 2025, 7:52?PM Tom Crowley KT4XN 1738 via
<crowleytj= [email protected]> wrote:
Ashhar, the ./update did not work.? Wha tis the best way to reinstall zBitx SW on the RPI?
Tnx,
Tom KT4XN
The image didnt come through. Can you mail it to be directly?
On Fri, Mar 28, 2025, 2:12 AM Tom Crowley KT4XN 1738 via <crowleytj= [email protected]> wrote:
Ashhar, with a monitor, keyboard and mouse plugged in.? The zBitx screen image remains the same (no change during boot-up).? The monitor shows a normal startup with a window showing what may be an issue.? Rebooted the machine and the zBitx window did not change,
however the monitor showed a normal reboot.? Unable to kill the zBitx program using the normal tools.??
|
Re: sbitx v3 no output after upgrading to 64bit
Yes. I have backed up and restored from the 32 bit sd card. I just tried it again this morning with the same results.
|
Dean,
I'm just writing to encourage you that I've had the v2 hardware device since April 2023, which I started using since mid-November 2023 (with v3.0 alpha version). Currently, the 64-bit v4.4 firmware is the latest and I've made nearly 10 thousand QSOs in mostly digital modes with an antenna sized for 7 MHz and usable well on 7-14-21 MHz without an antenna tuner.
I'm writing all this because there is a possibility, if you're interested, don't give up and you'll learn a lot of new information.
--
Gyula HA3HZ
|
To switch from 32-bit to 64-bit you will need:
a new uSD card of good quality, 32GB,
a USB stick, so that you can transfer copies from one OS to another, later copy the daily variables here.
a lot of patience, so that if you are unfamiliar with Debian, then do everything in order.
Yes and read, you will find how to do it in the wiki, if not, then ask.
?
--
Gyula HA3HZ
|
I just found the info in the manual that was just released.?
Barrel connector is 5.5 x 2.1 mm.?
Battery needs to provide 3 amps.?
?
|
I see, so you have the v3.0 alpha version in the firmware on your device.
Since development is almost complete on the 32-bit version, it is worth switching to the 64-bit Image if you want to use the device.
Unfortunately, there are many bugs in the initial versions and the fixes are completed on the 64-bit version, they are implemented there.
For the 64-bit transition, read this and this and do it all if you want to install the current version.
- ELF ??
the wiki ??
--
Gyula HA3HZ
|
... It is worth switching to the 64-bit OS, because the development is happening here. The current Image contains most of the programs needed for radio broadcasting, which you can implement with this device. You only need to fill in the characteristics of your station and use it. Important! the 64-bit Image was released with sbitx v4.2 and you can read the latest developments in the Github JJ wiki, what you need to do. First you need to download the ELF Image, which the description tells you how to do.
I'm back, start the device with the uSD card that came with the delivery and start the File Manager instead of sbitx. Insert a USB stick to which you copy the contents of the /sbitx/data folder. This must be done because the hardware-specific data is here and is also needed for the 64-bit OS.
--
Gyula HA3HZ
|
|
|
Gwen Patton
Sam Hanie
Charlie, W4CLV
HA3HZ