开云体育

Done

Before I spend any more time building out code modules for the sbitx, I’d like to know - is that product “never to be sold again” or simply delayed? While I enjoy spending days modifying my own radio, I need to know if it’s going to around in the future. VA3CGF

Just got my zBitx today. Powered up, and the nice screen pops right up. It says "Waiting for the zBitx to start..." and no other response. Been waiting a long time, but no joy. Tried power down and restart - same result. Any advice would be appreciated. 73 Dave, VE3WI

On N8ME's v0.2, I am able to switch between two color "themes" for day and night (Red) by adding a hardware switch to the Arduino's analog pin A7 and an "If..Else" statement in display.cpp to select between two groups of colors. (I also made those variables not constants.) All colors change depending on the switch position correctly EXCEPT the VFO colors*. Since the VFO display goes through some code to determine which VFO is active, changing the colors is more complicated. *If the VFO related color variables are defined outside of my If..Else function, you get those defined VFO colors. However, if those same variables are defined inside the function, they do not work and the VFO colors are black. Maybe its a scope or extern problem. I don't know. :) The hardware switch wiring is just adding a 20k pull-up resistor between A7 and +5v on the CONTROLS header and the switch goes between A7 and GND. (I will include pics). Apparently A6 and A7 do not have internal pull-ups if I understand right. If N8ME is OK with it, should I post my version and see if anyone wants to take a crack at getting the VFO colors to change with the switch?

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

Hello to the group -- I am receiving a fatal error on update for my sbitx developer edition "oled.h no such file or directory" Need help to fix this so I can upgrade my radio. Thanks -- Rick W7RNB

Hi to the group, I finally got my Sbitx DE up to 4.2 and it works fine but I have two issue 1). Low Voltage power warning when the PS is 14.1 Vdc 2). The display is about 1/2 the brightness it was on the factory software and the brightness control is set at max (31) Need input -- please Rick W7RNB

I tried to activate SPLIT using the on-screen keypad (in CW). Neither pressing the button nor turning the VFO knob with the selected SPLIT button turned SPLIT ON. Did I forget to do something?

Well today is 4 weeks so hopefully my zBitx will ship in the next few days....I've ordered all the support hardware (batteries, BNC coax, etc). I already have lots of other support since I own a KX2. Looking so forward to playing with this radio. I have a friend who has the sBitx (big brother) and I was quite impressed with it. -- "POWER, WE DON'T NEED NO STICKIN' POWER" - EVERY KX2 OWNER Always respect the airwaves, 73 de KI7PBR, Gary

HF Signals : Order Tracker Your Order #3869 Current status : Awaiting processing -------- Wish others would post order #'s if they really mean anything.

So I recently received my Zbitx and I think I have a problem. The receive is terrible. I can’t make out anything on it even trying the WWV freqs I can’t hear anything but a sort of “chuh chuh chuh” sound that’s continuous. I’ve adjusted the IF and volume as well as bandwidth but it makes no difference. If there something I’m missing or did I receive a faulty unit? Any and all help is appreciated. Video attached to show sound being heard.

I have two TSW T4.1 Raduino Kits, for uBITX v6, unbuilt for sale. $25.00 each or both for $45.00 + cost of USPS Priority Mail shipping, from SC, to US addresses only. PAYPAL only. Link to BITX20 Groupsio message thread referencing PDF of TSW T4.1 build instructions (scroll down to message #112110: https://web.archive.org/web/20220421175204/http://www.w0eb.com/ NOTE: - Kit DOES NOT include Teensy 4.1 (must use one with headers pins NOT installed), display (use display from uBITX v6 or purchase separately) or RTC battery. - You will need to able to use the Arduino IDE to load firmware onto the Teensy (I cannot supply the firmware so you will need to download yourself). These kits are supplied in the unopened bags they were shipped in from TSW. Dennis KG4RUL

I am not able to obtain a 'rig control (TX) when setting up QSSTV on the ZbitX (following the released user-guide). I am able to receive signals, just not able to TX. The ZbitX is unable to communicate to the QSSTV app (or vice versa) re: PTT/TX. Any ideas? I have tried 'many' different radios / rig control combinations, but nothing works. (I do have WSJTX running, and of course, FT8). BTW, a small, finned heat-sink plus a small fan seems to have solved any heat issues. Don in Austin N5CID

After a two year hiatus, I have updated my N8ME firmware for the uBitx v6 to version 0.2. Among other things, this incorporates some of the bug fixes from the VU3GAO update. The updated firmware can be downloaded or cloned from my github account. https://github.com/microenh/N8ME-ubitx The repository is designed for building and installing with VSCode and the PlatformIO extension. However, the src folder contains a src.ino file that can be used to build and install the firmware with the Arduino IDE. There is an updated PDF manual in the repository that shows how to use WSJT-X to do a frequency calibration. This is released without any warranty. Please let me know of any issues. -- 73, Mark, N8ME

My radio does not arrive till Monday! I am interested in some modes that are not installed on the radio. I want to test with DigiPi too. (YES, adding another Pi) What radio does the CAT port respond to? For Hamlib as an example. 73 KE9A

NOTE – This is focused on zBITX CW using a Straight Key. Scenario Straight Key CW is not really possible unless you send at 20+ WPM. Even then is troublesome, causing sending errors. Background - zBITX runs sBitx in a full RasPi OS install – it is not a stripped down version - A sBitx GUI is always running on the RasPi Desktop - zBITX adds and manages a second GUI running on a Touch Screen LCD - Two GUIs with dynamic Spectrum and Waterfall features require processing time - The sBitx CW is Semi Break-in, not Full Break-In - A Key-Down GPIO Input being detected switches the sBitx to Transmit Mode - No Key Down for ‘x milliseconds’ switches the sBitx back in to Receive Mode - The Back-To-Receive Mode delay time is currently settable from 0-1000 milliseconds - The Key-Down GPIO Input does not come from a GPIO IRQ (Interrupt) – it is polled. - The frequency of polling for a Key-Down GPIO Input is inconsistent. - The frequency of polling is theoretically every millisecond. But that does not happen. Concept Once in Transmit Mode, all else (except audio which runs in a separate thread), needs to be inhibited in order to allow the device to just manage CW sending . Problem Detail A GLib g_timeout_add() is used to call a ui_tick() function in sbitx_gtk,c every one millisecond (1ms). Polling for a Key-Down GPIO Input is done in this ui_tick() function. The ui_tick() function is very busy as it does a lot of other things, some of which look like they require a lot of time to process. So, it may take much more than 1ms for ui_tick() to complete. If a GLib timeout function is called again before its previous execution has completed, it does not cause any errors or unexpected behavior. The function is simply re-scheduled for the next timeout interval. This will behavior will delay the Polling for a Key-Down GPIO Input. Solution The ui_tick() function was revised to (1) Move the polling for a Key-Down GPIO Input to the top of the function, and (2) after having done that Key-Down GPIO polling, do a Return to get out of that function if we are in Transmit Mode. Result This change allows Straight Key use at very slow speeds. This change also helps with slow speed paddle keying. (however, it is just like the days of old, with nothing to look at while you are sending) This change proved my concept. BUT there are still some glitches, which are probably caused by ui_tick() getting past my “are we in transmit mode?” test and proceeding to get caught up in handling all of the other time consuming processing that takes place in the ui_tick() function. So it can be not looking whenever a Key Down occurs. So, it is not the complete answer. A copy of my revised sbitx_gtk,c is attached. Search on k3jzd to find my changes. Next Steps - Look at extending the Semi Break-In Hang Time (called “delay” in zBITX). The current limit of 1000ms (1 second) is often not enough - we pause to think a little from time to time. I’m still looking for where this 1000ms limit has been established so that I can change it to 5000 which will let the user set it to suit his style. - Look at using GPIO Pin IRQs (interrupts). I need to sort out how this works with a GPIO Input for DASH, but none that I have found for DOT. 72, Jody – K3JZD