Re: sBitx Mic input - assist request
Was there a mic input modification for the sBtx DE because I am getting reports of bad or distorted audio.
?
The mic element I am using was the one that came in the uBitx v3 kit.
?
Was thinking of giving a Heil headset mic with the IC element in it a try. Just have to make a adapter cable for the PTT part and not short the mic.
?
Do you guys think thats a good idea?
|
Re: sBitx v3 - problem with nonstandard callsigns
I have cloned and added my suffixed callsigns to the test: OE/SP5DAA, DE/SP5DAA, SP5DAA/2, SP5DAA/P (in ft8_lib/test/test.c)
Only SP5DAA/P is encoded and decoded correctly. Three others fail.
?
Below is one of the test cases:
Encoded [YL3JG] [DE/SP5DAA] [KO26]
Decoded [YL3JG] [<DE/SP5DAA>] [KO26]
FAIL: Condition '0 == strcmp(call_de, call_de_tx)' failed!
Encoded [YL3JG] [OE/SP5DAA] [KO26]
Decoded [YL3JG] [<OE/SP5DAA>] [KO26]
FAIL: Condition '0 == strcmp(call_de, call_de_tx)' failed!
Encoded [YL3JG] [SP5DAA/P] [KO26]
Decoded [YL3JG] [SP5DAA/P] [KO26]
Test OK
Encoded [YL3JG] [SP5DAA/2] [KO26]
Decoded [YL3JG] [<SP5DAA/2>] [KO26]
FAIL: Condition '0 == strcmp(call_de, call_de_tx)' failed!
?
?
Another case:
Encoded [DE/SP5DAA] [YL3JG] [KO26]
Decoded [<DE/SP5DAA>] [YL3JG] [KO26]
FAIL: Condition '0 == strcmp(call_to, call_to_tx)' failed!
Encoded [DE/SP5DAA] [W1A] [KO26]
Decoded [<DE/SP5DAA>] [W1A] [KO26]
FAIL: Condition '0 == strcmp(call_to, call_to_tx)' failed!
Encoded [DE/SP5DAA] [W1A/R] [KO26]
Decoded [<DE/SP5DAA>] [W1A/R] [KO26]
FAIL: Condition '0 == strcmp(call_to, call_to_tx)' failed!
Encoded [DE/SP5DAA] [W5AB] [KO26]
So it seems that this fix still does not remove the problem, especially for those travelling abroad.
?
73,
Wojtek
|
I agree with most of Ken and Lee's points.? What is not mentioned is the enormous amount of software that Ashhar Farhan used that is open source and may not be available for the "lower cost/higher performance" options.? Also, note that the sbitx and zbitx can run digital modes without adding a computer.? Most of that is possible because of the Linux base that the Raspberry Pi uses in most of its forms.? That could also go away if another processor is selected.
?
If the specs published for the zBitx are met, the closest competitor is the QMX+ from QRP-Labs.? The QMX line needs an external computer for most digital modes.? The QMX does include two more bands (160 and 6 meters) than the zBitx.? The QMX does not have a graphic touchscreen interface.? The QMX firmware is proprietary and not modifiable by the user.? The advantage of open-source SW is best exemplified by the 64-bit dev team (led by JJ W9JES) 's work.? That software is a HUGE improvement over the original get-to-market version distributed by HFSignals.? Both the zBitx and QMX+ cost the same with a case: $150.? Both specify 5 watts, with SDR-based digital filters for signal processing.? I will own both when my zBitx arrives.
?
I am one of the original 250 "lucky" users.? I am anxiously awaiting my shipment notice and receipt of the radio.
?
All good things take time.? Speculating on shortcomings before analyzing the product is wasted time and effort.
73
Evan
AC9TU
|
"If he had been much earlier in the design process, a more powerful CPU may have been a better answer, but it is not practical at this point"
Not to pick nits, but I was under the impression that after the sBitx project and it's RPi 4 computer, Farhan speculated a simpler design, based on lessons learned with the sBitx could be built based on the RPi Zero 2 w, with its half-gigabyte of RAM and a CPU shared with the RPi 3 B+ and thus was born the zBitx project and product.
?
The starting-point for the zBitx (Zero Bitx) as I recall was always the RPi Zero 2 W, if a more powerful CPU was needed, that likely would have rendered the zBitx project a failure, based on its original goals.
?
Ken, N2VIP
|
Thank you Lee for your 2? in the topic, without which we seemed to be in the dark.?
This seems like a new wave taking shape after "Add my name to the new order list"
Cheers
I think everyone needs to take a deep breath and recognize a few things. 1) This is new product, and to expect military precision for its release does not seem reasonable, especially with a smaller firm. Think of releases by Elecraft, QRPLabs, ant of course the "Big Three"; they may state a release date but really that should be taken as the beginning of a date range. 2) Asher and his group have made a couple of important additions to the zBitx based on changes to the operating plans for the rig. This benefits the end user but takes some extra time to implement. Waiting a bit longer to get a more complete product?!? This sounds like a no-brainer to me. 3) Some of the processes involved cannot be sped up by "adding another man to the job"; in fact, it may slow down the process. 4) Gordon makes an excellent point here. Asher only took on 2) above because he felt it would be advantageous to us end users at minimum disruption of the manufacturing process and minimum delay to getting them into our hands. In doing so, he made the same sort of decisions that all manufacturers make. If he had been much earlier in the design process, a more powerful CPU may have been a better answer, but it is not practical at this point. 73 de Lee KX4TT > On 03/10/2025 1:39 PM EDT Gordon Gibby KX4Z via <docvacuumtubes= [email protected]> wrote: > > > I’m somewhat incredulous that people would urge a complete redesign of a product that is potentially days away from shipping, likely already built. The only issue is how to manage upgrades, something that demonstrates some foresight! > > I don’t think you redesign a product, even changing the chip set , when it is ready to market. > Validation of such a radical change would substantially delay delivery of the product to those who have already paid for it > > My 2 cents, > Gordon kx4z >
|
I decided to go for the zBitx because I'm really intrigued by the concept of a miniaturized allband allmode trx. I have full faith in the developers that they'll create an amazing product for the community (free and open software and hardware, just like the good old days of Ham radio, the packet radio / AX.25 / that's used today).
I personally prefer to receive a well-tested device, and I'm sure the developers will deliver just that.
73, Herbert
|
Michael,
?
The first step is to verify that the Q10 Drain goes to zero when TX goes to 3 volts (or higher).? If that happens, Q10 is OK.? If not, it is bad.
?
Once Q10 works, verify that the Q9 tab (Drain) goes to 12 volts when the TX signal drives the Q10 drain low.? If that does not happen, remove Q9 and check the operation of Q101.? Do this with Q9 removed to prevent damaging both devices again.
?
Q101 drain goes to zero when TX and Q10 are off.? When TX is low, the Q101 gate should go above 5 volts to make Q101 turn on.? When Q10 turns on with the TX signal, Q101 should turn off.? If Q9 is removed, you can verify that the Drain-to-source resistance is very high with an Ohm meter.? Q101 Drain to Source resistance should be close to zero when TX and Q10 are on.
?
An alternative approach is to remove Q101 so there is no short on the 12V line during receive, Verify and replace bad parts, and then install a verified working Q101.? I built a test jig on a small copper-clad board with wires to insert into a component tester.? I hold the device with tweezers to connect each lead to a separate pad.
?
?
73
Evan
AC9TU
|
Evan, I have gotten things mostly straightened out, proper voltage to R77, 5.6v to D6, etc. I still get the 3v on Q10 for the Tx signal, but Q9 just doesn't switch. The voltages on the excel sheet match the steady receive state, but things aren't
switching when the Tx is applied. Suggestions?
toggle quoted message
Show quoted text
-------- Original message --------
From: "Evan Hand via groups.io" <elhandjr@...>
Date: 3/6/25 2:07 AM (GMT-05:00)
Subject: Re: [BITX20] reviving my sbitx v3
Michael,
?
The TX signal works (recieve at 0.15 volts, transmit at 3 volts).
?
?
The pins on Q9 are marked in this photo:
?
The gate (pin 1) of Q9 should be higher, and the tab (Pin 2 or drain) should be 0 volts when receiving and close to 12 volts on transmission.? It could be a failed Q9, Q10, Q101, or combination.? I would start with Q10, as it should pull down the gate
of Q9 to turn it on and supply the 12 volts to the driver stages.??
?
?
Q101 is a 2n7002 MOSFET.? This can not be replaced with a 2n2219.??
?
?
The above is based on not getting 12 volts on the tab of Q9.
?
73
Evan
AC9TU
?
-- Mike - K8MCB?
|
sBitx Toolbox for 64 Bit has been upgraded to v3.01.
?
This upgrade includes new and enhanced applications.
- Re-added Screen Resizer
- Updated USB headset for lower latency
- Added volume slider to voice keyer recording function
- Added update manager utility
- Added DroidStar controller (installed on v4.2 or later PI OS image)
- Fixed Screen Scaler medium and large buttons
- Added CW Detector
- Updated Toolbox launcher with new theme and UI controls
?
To get the latest update; Go to the Update menu and select Check for Updates
?
https://github.com/drexjj/sBITX-toolbox64
?
?
?
?
- JJ
?
?
|
Re: sBitx Mic input - assist request
Now I wish I hadn’t removed so many parts, Hope I can get the back in without too much difficulty! #LoveThroughHolePcbs!
toggle quoted message
Show quoted text
Yes, that is why I sent the picture.? Unfortunately, there is no tracking process for minor revisions, only the major ones, such as DE, V2, V3, and V4.? The V4 has just been announced.
?
With HFsignals, you always need to verify the schematic against the board.? My DE had some changes that have never been documented on a schematic.??
?
73
Evan
AC9TU
|
Re: sBitx Mic input - assist request
Yes, that is why I sent the picture.? Unfortunately, there is no tracking process for minor revisions, only the major ones, such as DE, V2, V3, and V4.? The V4 has just been announced.
?
With HFsignals, you always need to verify the schematic against the board.? My DE had some changes that have never been documented on a schematic.??
?
73
Evan
AC9TU
|
Re: sBitx Mic input - assist request
I just realized your picture does not have RD2 in it. Perhaps different revisions of sBitx V3 ??
|
Re: sBitx Mic input - assist request
On Mon, Mar 10, 2025 at 02:09 PM, Evan Hand wrote:
I measured my v3 mic input at 11.6 volts with a 12-volt supply, and no mic was connected.
Exactly what I would expect. Interesting that RD2 is not on the schematic. I'm befuddled as to what is happening with my PCB. I should have 11.xx v on either side of LD6. Even more so with the list of components I have removed. I might try to reinstall all and see what happens.?
?
|
Re: sBitx Mic input - assist request
Hi Rob,
?
I measured my v3 mic input at 11.6 volts with a 12-volt supply, and no mic was connected.
?
Here is the picture of the preamp area:
?
?
RD2 is not there.
?
If you want a different bias value, adjust RD2 to get whatever value you need.
?
73
Evan
AC9TU
|
Re: sBitx Mic input - assist request
Well, there ya go!? ?change that resistor to get the bias voltage you prefer and you should?be in business!! I didn't have that (to my knowledge) in any radio I have worked on, and I added resistors to get the voltage under 10 V? (a lot of electrets want it below 10V)
In order to get adequate?volume, I had to use very high output mics -- around -25 dB or -30 dB in their way of measuring it.? ?? Wish you good luck!? ?there is always something to learn -- and in this case comparing what IS to what is SUPPOSED TO BE is the trick!
Congratulations!!
Gordon KX4Z
RD2 ? I do not see this resistor on the and appears to be in parallel with C29. That would make your answer correct.
It would be great if another sBitx V3 owner could measure the Mic +ve on the tip of the mic TRS connector with mic unplugged.
?
?
|
Re: sBitx Mic input - assist request
RD2 ? I do not see this resistor on the and appears to be in parallel with C29. That would make your answer correct.
It would be great if another sBitx V3 owner could measure the Mic +ve on the tip of the mic TRS connector with mic unplugged.
?
?
|
I think everyone needs to take a deep breath and recognize a few things.
1) This is new product, and to expect military precision for its release does not seem reasonable, especially with a smaller firm. Think of releases by Elecraft, QRPLabs, ant of course the "Big Three"; they may state a release date but really that should be taken as the beginning of a date range.
2) Asher and his group have made a couple of important additions to the zBitx based on changes to the operating plans for the rig. This benefits the end user but takes some extra time to implement. Waiting a bit longer to get a more complete product?!? This sounds like a no-brainer to me.
3) Some of the processes involved cannot be sped up by "adding another man to the job"; in fact, it may slow down the process.
4) Gordon makes an excellent point here. Asher only took on 2) above because he felt it would be advantageous to us end users at minimum disruption of the manufacturing process and minimum delay to getting them into our hands. In doing so, he made the same sort of decisions that all manufacturers make. If he had been much earlier in the design process, a more powerful CPU may have been a better answer, but it is not practical at this point.
73 de Lee KX4TT
> On 03/10/2025 1:39 PM EDT Gordon Gibby KX4Z via groups.io <docvacuumtubes@...> wrote:
>
>
> I’m somewhat incredulous that people would urge a complete redesign of a product that is potentially days away from shipping, likely already built. The only issue is how to manage upgrades, something that demonstrates some foresight!
>
> I don’t think you redesign a product, even changing the chip set , when it is ready to market.
> Validation of such a radical change would substantially delay delivery of the product to those who have already paid for it
>
> My 2 cents,
> Gordon kx4z
>
|
Please don't confuse a labor of love by a fellow HAM with a large company's professional product. I am appreciative of the development of this very innovative,state of the art, product by such a dedicated team of fellow hobbyists sharing their love of the hobby with us! Nothing like it anywhere and they have always said that it is an experimental project for tinkers!
This is one reason why I wait until a product it out and vetted before ordering one.
Mike N2MS
> On 03/10/2025 1:39 PM EDT Gordon Gibby KX4Z via <docvacuumtubes=[email protected]> wrote:
>
>
> I’m somewhat incredulous that people would urge a complete redesign of a product that is potentially days away from shipping, likely already built. The only issue is how to manage upgrades, something that demonstrates some foresight!
>
> I don’t think you redesign a product, even changing the chip set , when it is ready to market.
> Validation of such a radical change would substantially delay delivery of the product to those who have already paid for it
>
> My 2 cents,
> Gordon kx4z
>
|
This is one reason why I wait until a product it out and vetted before ordering one.
Mike N2MS
toggle quoted message
Show quoted text
On 03/10/2025 1:39 PM EDT Gordon Gibby KX4Z via groups.io <docvacuumtubes@...> wrote:
I’m somewhat incredulous that people would urge a complete redesign of a product that is potentially days away from shipping, likely already built. The only issue is how to manage upgrades, something that demonstrates some foresight!
I don’t think you redesign a product, even changing the chip set , when it is ready to market.
Validation of such a radical change would substantially delay delivery of the product to those who have already paid for it
My 2 cents,
Gordon kx4z
|
I’m somewhat incredulous that people would urge a complete redesign of a product that is potentially days away from shipping, likely already built. The only issue is how to manage upgrades, something that demonstrates some foresight!
I don’t think you redesign a product, even changing the chip set , when it is ready to market. Validation of such a radical change would substantially delay delivery of the product to those who have already paid for it
My 2 cents, Gordon kx4z?
toggle quoted message
Show quoted text
On Mar 10, 2025, at 13:20, Shirley Dulcey KE1L via groups.io <mark@...> wrote:
? I sit corrected. But I wonder what the wireless in the Pico will be used for? Have to wait and see! On Mon, Mar 10, 2025 at 12:40?PM Charudatt Uplap via <charudattu= [email protected]> wrote: Guys, let's not speculate, the designer is not a fool. You already know him from his earlier offerings.
I suggest, let's wait for the rollout and then discuss.
Right now we don't know much of what's in the offering. So have patience.?
de VU2UPX?
Farhan explicitly stated the zBitx will have an RPi Pico W:
?
"Hence, the zbitx sports a new microcontroller, the Raspberry Pico W (with Wifi and Bluetooth on it!) that handles the front panel. This offloads the user interface to this microcontroller that handles the 3.5 inch TFT display. The two talk to each other over the I2C bus (Pi is the master, Pico is the slave)."
?
Clipped from yesterday's update.
?
Ken, N2VIP
|
Lee