Keyboard Shortcuts
Likes
- BITX20
- Messages
Search
Re: Z bitx poor sensitivity
toggle quoted message
Show quoted text
On May 16, 2025, at 15:37, Gordon Gibby KX4Z via groups.io <docvacuumtubes@...> wrote:
|
Re: Z bitx poor sensitivity
¿ªÔÆÌåÓýIf you¡¯re able to down between the two points that you¡¯ve got, success at -73 and failure at negative103 which are 30 DB apart, that would be a big step forward!I wonder if the digital noise from various cables, etc., in the device are harming the basic sensitivity? ? As I remember, I think this device uses a diode mixer, and those generally can have a pretty well known sensitivity. ? ?But that could be covered up by internally generated noise. Those are things that can be fixed! Thanks-? Gordon kx4z? On May 16, 2025, at 14:46, Tom via groups.io <tmoll150@...> wrote:
|
Re: Z bitx poor sensitivity
Just got my zbitx yesterday and have begun playing with it. Made a bunch of FT-8 QSO's right away on 20m last night with 2w out to a vertical, so that was interesting and pleasantly surprising.
Did some receiver testing today.
The factory Test Report card that came with the xcvr indicates a sensitivity of -105dbm.
I attached my S9 signal generator set at -103dbm (about S4) and it could not be heard on any band, even with the IF gain at 100.
With the generator set at S9 (-73dbm) it could be plainly heard on all bands with the IF gain set at 50, however, the audio heard was not
perceived to be an S9 signal. Turning the IF up to about 65 helped a lot, but the radio seems to lack audio gain as well.
The S meter on the zbitx did read approximately S9 at this setting.
?
This lack of sensitivity surprises me greatly - even my super cheap and dated technology SoftRocks easily hear better than that, as does a simple analog rig like a QCX.
Something does not seem right to me. I expected better.
The concept of this radio is really great IMO, and obviously a lot of work has already gone into its implementation, so hats off to the developer, however,
this receiver performance seems to be a serious issue to me, even at this price point. |
Re: sBitx original handheld microphone upgrade
#sBitxDevel
#sbitx_v2
#sBITX_v3
I talked about this, but I didn't post a picture, a picture always says more, so I'll post it now:
?
?
?
--
Gyula HA3HZ |
sBitx original handheld microphone upgrade
#sBitxDevel
#sbitx_v2
#sBITX_v3
Today I made a conversion of the original handheld microphone purchased with sbitx, similar to the 'Meeting MIC', which I documented in the attached file.
If I missed something, please feel free to ask, I will answer when I can.
--
Gyula HA3HZ
?
? |
Re: zBitx Power Supply
Hi Yvon!? Unfortunately not! It makes a lot of noise on the amateur band. You need to use a battery or a better quality power supply. Sorry. Yvon AE7YD via <Yvon=[email protected]> ezt ¨ªrta (id?pont: 2025. m¨¢j. 16., P 18:23):
|
Re: ZBitx Shutdown Function
#zbitx
¿ªÔÆÌåÓýI just use 'sudo shutdown' from the terminal. Assume that properly shuts off the Pi-Zero. Now, how do you shut off the Pico? Don in Austin,? N5CID
=============================================== On
5/4/2025 6:49 AM, Karl Heinz Kremer, K5KHK wrote:
|
Re: zbitx, compiler optimizations
#zbitx
¿ªÔÆÌåÓý
OK, I guess I should read that thread. I think the i2c communication must be excessive in general. ?It makes audible noise (everybody¡¯s complaining about ¡°chugging"), but I¡¯ve also found that when I have a USB ethernet adapter attached, communication there makes noise too. ?(Of course, the electrical design could be better, but I don¡¯t yet know how to pinpoint why that is happening.). (To me it sometimes sounds like hard drive seeking noises. ?;-) ?One obvious solution to do less communication is using notifications/signals: each field should notify when it has changed (only when the stored value really changed), and that should trigger the updates: those that go to the GTK UI, i2c UI update commands, and/or some network protocols. ?In Qt one uses signals: ? But I think gtk/glib has something like that too. ?? leads to?? : yep that looks like what we need. For 9p I just tried an explicit callback first (and I¡¯m not calling it from enough places yet): void notify_field_changed(const char *field_id, const char *old, const char *newval); The implementation of this function could take care of notifying the various UIs and network protocols. ?But probably it should rather emit a signal: each ¡°client¡± should subscribe for notifications. ??is something that just about everybody has to do at some point... Sbitx/zbitx is doing too much polling and timer-based refresh instead, and that is creating a lot of inefficiency. ?Especially with the excessive string comparison and conversion going on. The network protocol is important to me because I want to decouple the GUI from the radio daemon anyway. ?This daemon will eventually need to avoid using gtk/gdk at all: pure C for the core functionality. ?(Why does zbitx have to run X11 and a GTK UI under the condition that nobody is looking at it? ?Sometimes HDMI is connected, sometimes not. ?We only have 512MB, and startup time is noticeable too.) ?9p is gonna be great for that, eventually, probably. ?I have a working client on Plan 9 now, just rather buggy and incomplete compared to the GTK one. ?I just got a waterfall added to it, without taking much bandwidth (because I only send the latest line of samples at a time; too bad it¡¯s only about 440 actual pixels, despite the memory allocated to hold 1024 * history size). And later I will do a Qt client with the same protocol, for all the other platforms. ?That one can have fancier features. |
Re: zBITX Crashes - Suspect Memory Leak
#zbitx
thanks Jody,
I'll wait for your fix, but I was asking for a copy of 3.021 on an iso or img file format to test your sbitx_gtk.c file.
Idk if theres a ver 3.021 on the official github and if theres 1, idk how to compile to a fresh raspian OS.?
72 de KP4MI? |
Re: zBitx +-2 MHz transmit spurs?
Has any more work been done on finding a way to reduce or eliminate the transmit spurs that some people have found generated by their zBitx? ? The spurs appears to be the intermodulation or mixing of two of the Si5351 clock generator outputs, and can be a few MHz apart, thus not eliminated by the output filters. ?I don't want to connect my zBitx to an antenna if it's generating non-compliant levels of interference well outside the ham bands.
73, Ron, n6ywu |
Re: zBITX Crashes - Suspect Memory Leak
#zbitx
On Thu, May 15, 2025 at 04:56 PM, miguel medina wrote:
Miguel,
?
My version 3.021 sbitx_gtk.c will not run with your version 3.052 system.
?
I will be posting one for version 3.052 based on my latest discovery.?
?
I identifies a quick fix for version 3.052.
?
72,
Jody - K3JZD? ? ? |
Re: zbitx, compiler optimizations
#zbitx
Check my thread about a zBITX Memory Leak.? ?I concluded that the i2cbb.c program in sBitx version 3.052 being used in the xBITX was being swamped with send requests, resulting in a huge number of bus contentions, disconnects, and reconnects.? Odds that has contributed to the large time spent in what has been identified here as 'ic2_delay'.? ? I also identified the root cause of the huge number of send requests that are swamping the ic2 bus handling functions.? ?
?
I also think that the RasPi Zero used in the zBITX has enough horsepower to do the job.? Back when I was doing sales support for custom computerized control systems, and potential customer had spec'ed that they wanted the CPU usage to be 75% maximum, I always asked what they will do with the other 25%.? Sure, we could limit it to that, but why slow down the system for an artificial constraint.
?
Just my opinion.
?
72,
Jody - K3JZD |