开云体育

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

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

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

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

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

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?

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

After working with Unix/Linux systems for a lifetime, i know that bad stuff will happen if you just disconnect the power on a regular basis. I still feel a twitch in my fingers if I don’t run sync; sync; sync; before a shutdown or halt command ;) I’ve forked Farhan’s code and added a button on the UI to shut down the Pi Zero: https://github.com/khkremer/zbitx.git https://github.com/khkremer/zbitxfrontpanel.git The "Shutdown" function is behind the "Menu" button. After selecting it and confirming, wait until the LED on the Pi Zero (which you can see through the covered USB connector) stop to blink. I moved the confirmation button a bit up so that it’s harder to fat finger the shutdown with an unintentional double tap on the shutdown button. de Karl Heinz - K5KHK

I know there are are a fair amount of new people here who may not know about some tools that I've developed. Here is one that can make it easier for you to calibrate your hardware. https://github.com/drexjj/sbitx/wiki/sBitx-Hardware-Calibration#zbitx-model -JJ

My SBitX was on at home in FT8 mode, I was 30 miles remote with my ZBitX, made two contacts from the remote location with FT8. Both ZBitX contacts show up in my SBitX log! The ZBitX has not been powered on since I got home. Can anyone explain what and how this this happened? Tim W1WCI

Is there any estimate on when the sBitx v4 and the zBitx will be available for purchase?

ALAMOGORDO AMATEUR RADIO CLUB'S 39TH ANNUAL HAMFEST ARRL SANCTIONED 30 Aug 2025 Otero County Fair grounds (in Alamogordo NM) 7am to 3pm-ish Admission: Free!!! Vendors can set up day before 3 to 7pm Pre-register for Tables and prize tickets. Tables are $15.00 ea (if you have your own table and chairs $6.00 each table space) Electrical at most of the table locations but not all. Pre-register so we can get a good table count. Prize drawing tickets postmarked before 23 August $8.00 (pick up at event) If you cannot make it, tickets will be added to Main Prize drawing. Prize tickets at the door $10.00 Tickets postmarked before 23 August will be eligible for a pre-registration prize $50.00 cash. 1st Prize winner responsible for shipping or pick up at event. 2025 Prize list 1st FT710 AESS 2nd FTM-150R 3rd Mini 1.3 OLED Zumspot 4th DM-30TR There is a $1.00 Ticket drawing for a FT-4XR Looking for folks and groups to give presentations, let us know what ya can do Other Door prizes from Amateur Radio Related and local vendors, drawn throughout the event. Plenty of parking, RV's welcome, no hook ups but there is a dump station on site ARRL License testing will be conducted at 9am-ish. Please Bring a photo ID or 2 other forms of ID. FRN must be provided. FRN can be established by registering with FCC Check K5LRW website, for latest changes www.qsl.net/k5lrw/hamfest.htm Pre-register by Mail: Contact Hamfest Committee Chair Alamogordo Amateur Radio Club Rusty KI5RUS rjaskolo@... HAMFEST 2025 575-491-3631 call or text 12 Main St#383 Or Rick KB7SQF rick@... La Luz NM, 88337 Hamfest Committee member E-mail_____________________________ Ph#_________________________ Name______________________________ Call_________________________ Address________________________________City__________________St/zip__________________ Make Checks payable to AARC and include your callsign on Check Prize Tickets Before 23 Aug. at $8.00 x______=$__________ Tables at $15.00 x________=$________ your own $6.00x_____=$________ Dinner(pay as you go) How many?_____________(Location TBA) Testing or upgrading : Technician / General / Extra (Circle one)

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