开云体育

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

The Pi zBitx process is locking when I select an FT8 station

 

Ok.
?
  • I managed to get the WiFi going, which updated the time. Now I'm seeing decodes in the FT8 screen I wasn't seeing before.
  • I ran the update for the firmware on the pi from the HDMI screen.
  • I updated the pico, and it is showing 1.04 firmware for the interface.
So now, I'm in FT8, looking at decodes, and followed the example in the "Working FT8" video. I tapped on the decodes with my finger, then turned the encoder, which showed a white outline around the decodes, moving from entry to entry.
?
The problem is, when I choose a decode to work, and press the encoder to grab the callsign and start to work the station,?the radio process in the Pi locks up tight. I can't get the process going again without simply rebooting. But this doesn't fix the problem. It only repeats. When I select a decode by tapping, turning the encoder, and pushing the encoder to engage the switch, the radio process locks up. The interface part run by the pico continues just fine, but the waterfall stops, and the signals stop decoding. I can move the selection to another decode, because that's farmed by the pico, but if I press the encoder at that point, nothing happens, because the radio process is still hung.
?
If I have the HDMI output showing on my monitor when I press the encoder, the radio process stops displaying there, too. Unfortunately, while I had a good pointing device to get the WiFi going, that mouse is no longer causing the pointer on the screen to move. I can't try selecting another from the Bluetooth stack, because? I can't point to it, and my knowledge of Linux is shaky enough that while I can move the focus from window to window, I don't remember how to bring up the Pi menu or select anything without a mouse. I just need to get a new keyboard/pointing device, so I can fix part of that problem.
?
Just as an aside, I never managed to get that USB-A > microUSB adapter supplied with the unit to work. The dongle I put in that adapter never seemed to be tightly held, and I doubted it was making proper contact. I had a different USB-A > microUSB adapter, which allowed me to access the radio at all.?
?
Getting a tad frustrated. I'll probably take a break for a while at this point.
?
73,
Gwen, NG3P
 

Additional info.
?
I managed to get a Bluetooth keyboard/trackpad device connected to the zBitX, and it works fine. With that set up using a borrowed keyboard/trackpad, I used the HDMI screen and Pi process window to operate FT8. Unlike the screen on the zBitX and selecting a station to work, if I clicked on it with the mouse, it worked normally. The callsign was selected, and transmission began. I got two contacts operating this way until my batteries were down to 6.1 volts and the power on 15m was down to around 1 watt. (Drive is set to 100.) I have an 8-pack of 18650 cells and a 4-bank charger on its way, so I'll have better access to power.
?
The point is, running through the HDMI screen and pointing device, I was able to select stations and operate. Only the selection on the zBitX screen is locking up when selecting a station using the encoder. This hopefully narrows things down a bit, and maybe it's just something I'm doing wrong. I'm going to re-watch the YouTube video on "Working FT8" and see if I'm missing something in that process.
?
73,
Gwen, NG3P
?
 

开云体育

Similar behavior here, one additional note. Logged contacts show on the HDMI screen, but log is blank on the radio if viewed before the radio is locked up.
Sent from me and my iPad

On Mar 28, 2025, at 3:54?PM, Gwen Patton via groups.io <ardrhi@...> wrote:

?
Additional info.
?
I managed to get a Bluetooth keyboard/trackpad device connected to the zBitX, and it works fine. With that set up using a borrowed keyboard/trackpad, I used the HDMI screen and Pi process window to operate FT8. Unlike the screen on the zBitX and selecting a station to work, if I clicked on it with the mouse, it worked normally. The callsign was selected, and transmission began. I got two contacts operating this way until my batteries were down to 6.1 volts and the power on 15m was down to around 1 watt. (Drive is set to 100.) I have an 8-pack of 18650 cells and a 4-bank charger on its way, so I'll have better access to power.
?
The point is, running through the HDMI screen and pointing device, I was able to select stations and operate. Only the selection on the zBitX screen is locking up when selecting a station using the encoder. This hopefully narrows things down a bit, and maybe it's just something I'm doing wrong. I'm going to re-watch the YouTube video on "Working FT8" and see if I'm missing something in that process.
?
73,
Gwen, NG3P
?
 

?I have added this issue to the Github bug report page. It is issue #6.
?
73,
Gwen, NG3P
 

开云体育

The joys of bringing out a new product!

Gordon kx4z?



On Mar 28, 2025, at 18:45, Gwen Patton via groups.io <ardrhi@...> wrote:

?
?I have added this issue to the Github bug report page. It is issue #6.
?
73,
Gwen, NG3P
 

Wouldn't miss it for the world, Gordon! I just got a 9v PD trigger cable that works perfectly, and I got an 8-pack of 18650 cells and a 4-place charger. 3300mAh and 4.2 volts. And I find that the hand mike for my KX3 *does* work perfectly in it!

Now, if I could only operate FT8 properly!


-=-=-=-=-=-=-=-=-
73,
Gwen, NG3P

1 - 6 of 6