开云体育

I tested transmitting from my new zBit into a tinySA with 50 dB of attenuators in between. First the good news, the 2nd and 3rd harmonics seem ok (43 dBc down or more). But I also see spurs at carrier +-2 MHz, and a 2 MHz, that seem to be a higher level than 43 dB below carrier. These 2 MHz sideband spurs were still visible when testing output on multiple other bands, from 40M to 12M. I don't see such 2 MHz spurs when testing my other transceivers, so they don't seem to be from the tinySA. Wierd measurement error? Or is my zBitx bad? Or could this be a hardware design or software issue. Or inter-mod from one of the digital circuit clocks or IO or display, requiring more shielding. I also hear noise on the audio, even with no antenna connected, pulsing at about 3 or 4 Hz. Ideas? Potential solutions? Thanks and 73, Ron, n6ywu

I purchased the rig in the pic from eBay about a year ago. The best I can remember it is a version of the Bit-X but not sure. I haven’t used it other than som RX because it didn’t have a manual and operation isn’t obvious to me. Is there a manual on the web? sorry my first post was questions but that’s alli have until I start making contacts. Pic attached. 73, Jerry NE4L

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

Sbitx - antenna switch - swr/power coupler - antenna Previously radio showed power and 1.0 swr on 15, 20, and 40 meters with similar readings on the off board meter. As of this morning swr on the radio and the off board meter show high SFR 2 to 3:1. Removed the radio from the antenna line and replaced it with an antenna analyzer, it shows a perfect 1:1. Another radio shows 1:1 on the radio and the off board meter. Previously, maybe a month ago I had the same problem, spent time chasing down the antenna to no avail. Then one day all was well with no intervention at or in the radio. All bands that were workable for the antenna show the same behavior today. Trouble shooting help welcomed. Tim

After letting my zBITX sit unattended in Receive Mode for a while, the main RasPi CPU crashes. I have never timed it because I'm not just sitting there watching it. But it seems like it only takes about an hour or so to crash. I am not able to get a SSH connection to the main CPU at that time. The display CPU is still running at that time. While the device is warm whenever this occurs, I do not think that it is a thermal issue because if I disconnect and reconnect the power it reboots and runs fine. I have never stopped the sbitx application to see if something else on the RasPi could be causing it. I have SSH and VNC enabled, but I am not using either of those connections. I do not have anything else running on the RasPi. So, I really do not think that it is some other RasPi appllication. I think that it is probably a sbitx application memory leak. Don't see how something like a character array overflow would occur after just sitting there unattended for that period - nothing is being done on the GUI during that time. This crashing occurred whenever I had version 3.021 installed, And it is still occurring with version 3.052 installed. If you are running on batteries, the batteries may be depleted before this crash occurs. You will never see it. I am using a 7.5vdc power supply. 72, Jody - K3JZD

I just received my zBitx, and have read the manual as well as been following this group for the past couple months. I hope to use this rig primarily on CW and perhaps a little FT8. I am aware of some serious CW issues having been noted on this group. What is the current state of usability in CW? Is there a best firmware to be using? I prefer to use an external paddle with the internal keyer and sidetone, but will a straight key or keyboard CW be better for now? Or do I just need to wait for a fix? I will power the rig with 18650 cells in the attached holder. What is the best way to turn off the rig? Remove the cells? I know that can corrupt SD cards… 73, Steve AK0M

Hi all, from what I've understood about the timing issues with CW on zbitx, it seems that the CPU load is at least part of the problem. I personally would love an option to switch off the waterfall (either in menu or set options), because I only need it when searching for signals, but not when I have found one. Apart from that, I wonder why the binary is compiled with debug symbols and no optimization at all. I exchanged the "gcc -g" with a "gcc -O3" in the build script, and the CPU load decreased from 60-70% to 45-55% running FT8, so there is quite some optimization that can be done. Interestingly the CPU load is quite higher on CW, which is 65-70% optimized and 75-80% original (unoptimized). I guess this might be due to polling the key's GPIOs instead of handling them via interrupt (which would make the code more difficult of course). Is there a reason why the build script is not using optimization? (for development side "-g" is perfectly understandable, but for "production" side?) Maybe compiler optimization could at least contribute to the puzzle pieces for optimizing CW response. vy73, Peter DL4PIT