¿ªÔÆÌåÓý

Date

Re: sBitx Developer¡¯s Edition (v1) ¡ª how to protect the RPi4?

 

Evan, since I have two RPi4s with damaged SDA and SCL GPIO pins and another with a damaged GPIO4 (TX) pin I think I should put 3.3 volt Zeners on those lines, with series 330 ohm resistors. I assume the LC changes won¡¯t be significant enough to interfere with the edge detection for the I2C bus. The best place would be at the exposed right angle bend in the 40-pin brass connector J2 mounted on the digital board. A cut there would allow for a series resistor insertion, and there is an adjacent ground plane on the digital board for the Zener diodes. Incidentally the WM8731 codec pins, 19 RLINEIN and 20 LLINEIN already have 3.9V Zeners! I wonder how delicate those inputs are.
Jack
N6LN


Re: Sbitx V2

 

Thanks Ashhar, I have the Baofeng speaker mic and I need to shout a little to get any output, Maybe I just have a dud.I would still Like a different mic
Jeff KA8SBI


Sbitx manual

 

The sbitx quick manual is on .


WSJT-x 2.6.1 and uBitx on Raspberry Pi #ubitx

 

I'm running WSJT-X on a Raspberry Pi 4, 4Gb, running 32 bit "Raspbian GNU/Linux 11 (bullseye)" that is fully patched and up to date.
Radio is a uBitx v6.1 with a Signalink interface, using the Yaesu FT-817 settings in WSJT-X.

WSJT-X version 2.5.4 works fine, no errors.

Version 2.6.1 (installed with "dpkg -i wsjtx_2.6.1_armhf.deb") gives a hamlib Protocol error.

I've upgraded hamlib to version 4.5.4 as indicated by the WSJT-X release notes.

Downgrading back to 2.5.4 ("dpkg -i wsjtx_2.5.4_armhf.deb") and everything works fine again, even with hamlib 4.5.4 still installed.

Has anyone gotten WSJT-X 2.6.1 to work with the uBitx from a Raspberry Pi?

Thank you,

-Dj

Error:

Hamlib error:?? 2:rig_get_mode: elapsed=610ms
? 2:rig.c(2542):rig_get_mode returning(0)
?1:rig.c(1375):rig_open returning(0)
?1:rig.c(2884):rig_get_vfo entered
rig_get_vfo: cache check age=15460ms
rig_get_vfo: cache miss age=15460ms
/home/wc4h/Downloads/wsjtx-2.6.1/hamlib-prefix/src/hamlib/src/rig.c(2926) trace
ft817_get_vfo: called
ft817_read_eeprom: called
write_block(): TX 5 bytes, method=1
0000??? 00 54 00 00 bb????????????????????????????????????? .T...????????? ?
read_block_generic called, direct=1
read_block_generic(): Timed out 3.3035 seconds after 0 chars, direct=1
Protocol error
)
?1:rig_get_vfo: elapsed=3009ms
?1:rig.c(2947):rig_get_vfo returning(-8) Protocol error

Protocol error
Protocol error
?while testing getting current VFO


Re: V2 serial numbers

 

We will maintain backward compatibility well into the future with the current version of hardware. This is good enough for us to do almost anything on HF.
We have 25KHz of baseband bandwidth which is all we need. The rest is just clever software.
- f


On Mon, Apr 17, 2023, 8:37 PM Petr Ourednik <indians@...> wrote:

Farhan,

I hope that you are working on new version of software only / refactoring code ¡­not on new version of hardware platform, hihi.?


- P


Re: Sbitx V2

 

Jeff,
It just looks good, frankly. It has the same panasonic element inside it. Don't fall for the HF Signals sales pitch :-D
- f

On Mon, Apr 17, 2023, 11:31 PM Jeff Wysong via <ka8sbi=[email protected]> wrote:
I seen a vid of a recently purchased ubitx with a nicer mic. It loos like the one in the sbitx. the guy in the vid had good drive and output without modding the rig or mic. Can I get that newer mic for my ubitx?

Jeff KA8SBI


Re: Sbitx V2

 

I seen a vid of a recently purchased ubitx with a nicer mic. It loos like the one in the sbitx. the guy in the vid had good drive and output without modding the rig or mic. Can I get that newer mic for my ubitx?

Jeff KA8SBI


Re: Bring the BITX40 Kit or similar SSB transceiver kit back

 

Once you get it built and have used it for a while, report back and let us know what the performance is like. Thinking about getting one.

Max KG4PID


On Monday, April 17, 2023, 12:11:01 PM CDT, Doug W <dougwilner@...> wrote:

On Sat, Jan 7, 2023 at 12:30 AM, Sunil Lakhani wrote:
We are in process of bringing back easy bitx version 1 and 2 and a new 2 bander kit for 20mt and 40mt by February.
Best of 73s?
Sunil vu3sua


I just receive Sunil's Easy Bitx kit in the mail today.? It exceeds my expectations.? The kitting and packaging alone is worth the cost of the kit.? Sunil has a great manual on his site and the components for each step are individually packed and clearly labeled with the step on each bag.? Sunil's communication during the order process with great.? He quickly answered my questions and asked a few to make sure I got exactly what I wanted.? I'll try to post some pictures after I inventory everything if there is interest.? In addition to my HFSignals kits, I've been meaning to scratch build a BITX for years and never got to it.? This kit is a perfect in between.
?
--


Re: Bring the BITX40 Kit or similar SSB transceiver kit back

 

On Sat, Jan 7, 2023 at 12:30 AM, Sunil Lakhani wrote:
We are in process of bringing back easy bitx version 1 and 2 and a new 2 bander kit for 20mt and 40mt by February.
Best of 73s?
Sunil vu3sua


I just receive Sunil's Easy Bitx kit in the mail today.? It exceeds my expectations.? The kitting and packaging alone is worth the cost of the kit.? Sunil has a great manual on his site and the components for each step are individually packed and clearly labeled with the step on each bag.? Sunil's communication during the order process with great.? He quickly answered my questions and asked a few to make sure I got exactly what I wanted.? I'll try to post some pictures after I inventory everything if there is interest.? In addition to my HFSignals kits, I've been meaning to scratch build a BITX for years and never got to it.? This kit is a perfect in between.
?
--


Re: V2 serial numbers

 

Farhan,

I hope that you are working on new version of software only / refactoring code ¡­not on new version of hardware platform, hihi.?


- P


Re: V2 serial numbers

 

Darrell,
We have tested the radio long enough. The best thing about the SDR is that it is all in software. I am already working on the next version, refactoring the code.
The boxes will be picked?up tomorrow, I am told.
- f


On Mon, Apr 17, 2023, 6:23 PM Darrell Davis KT4WX <kt4wx@...> wrote:
Hello Ashhar:

I agree with the other gentlemen.? Do not rush and make mistakes.? Instead, take your time.? A good radio is well worth the wait.? And I get to be on the ground floor of Version 2.? Thank you for all you do for the amateur radio community, specifically those of us who enjoy building and experimenting.

73
Darrell Davis KT4WX


sBitx V2 Question About Frequency Readout Display

 

Re: sBitx V2 Question About Frequency Readout Display

I saw a picture of the new sBitx V2 and the Frequency Display looks really small.

Does anyone know what the approximate size of the frequency readout ?

Frank


Re: sBitx Developer¡¯s Edition (v1) ¡ª how to protect the RPi4?

 

Thanks Evan. 3.3v zeners did occur to me, ?Incidentally I did have Zeners across the finals and still one of them shorted. It¡¯s strange.?

Jack
N6LN


Re: sBitx Developer¡¯s Edition (v1) ¡ª how to protect the RPi4?

 

John,

I have been thinking along the same lines to protect the most expensive component in the sBITX.? Here is what I found in a search on the internet:


I like this one, as it has both current and voltage limiting in the suggestion:


This solution uses a 3.3 volt Zener for voltage protection and a 330 ohm resistor for current limiting.? The disadvantage is any delays the resistor could add to the turn on or off of the external circuit, like in TX/RX transitions.

Until we know the cause, it is hard to come up with the best design.? If we could be sure it is voltage, then a Zener to protect any voltages over 3.3 volts would be enough.? The problem is that it could be current, causing the failure.? The GPIO pins are rated for only 16ma.? If, in oscillation, the equivalent impedance of a capacitor is 50ohms, the current required would exceed the Raspberry Pi rating.? This might be a good simulation exercise to see the average current draw on the TX pin.? I do not know how this would happen on the bit-banged I2C lines.??

The other possibility would be induced voltage on the 3.3volt power rail picked up by the relatively long I2C run for the RTC.? Maybe that should be done with a shielded cable.

The above are guesses and should not be implemented without further research.? We have seen at least two owners of the sBITX DE that have experienced RPi failures.? Each of them has had more than one RPi fail.? Out of 150 shipped, that is still a tiny percentage.? We can track the v2 failures to see if it might be a layout issue rather than a fundamental design issue.? The two systems are different enough in design that the feedback possibility should change.

73
Evan
AC9TU


Re: V2 serial numbers

 

Hello Ashhar:

I agree with the other gentlemen.? Do not rush and make mistakes.? Instead, take your time.? A good radio is well worth the wait.? And I get to be on the ground floor of Version 2.? Thank you for all you do for the amateur radio community, specifically those of us who enjoy building and experimenting.

73
Darrell Davis KT4WX


Re: About ATiny85 code

 

Sorry to come back to this topic again, but the pin 5 is not the I2C SDA? This LOW/HIGH changes would not create some noise in the I2C communication?

I created a PR removing such code:


Rafael

On 4/16/23 22:09, Ashhar Farhan wrote:
Ah,? a good spot. I wanted to check how fast the adc works. If you see, the pin 5 is being flipped on each iteration of the loop. So, I connected the pin5 to an oscilloscope to measure the time periods.
It is cruft. It needs to be removed.
- f

On Mon, Apr 17, 2023, 12:11 AM Rafael Diniz <rafael@...> wrote:

Hi Ashhar and all,

What does it mean this part of the code of the ATtiny85, I don't
get it:

--
?? if(flag == 1){
???? digitalWrite(5, LOW);
???? flag = 0;
?? }
?? else {
???? digitalWrite(5, HIGH);
???? flag = 1;
?? }
--

The example from Nicholas Zambetti does not have this:




Cheers,
Rafael







Re: About ATiny85 code

 

No problem, there are also "off-the-shelf" ones. I'll choose one and test.

tks!

On 4/17/23 11:29, Ashhar Farhan wrote:
I built one with an Arduino nano, a 10uf cap and two resistors. Not sure where I saw the circuit diagram.
- f

On Mon, Apr 17, 2023, 1:57 PM Rafael Diniz <rafael@...> wrote:

Thanks Ashhar, there is what I thought. Btw, which "burner" do you
use
to write the firmware to the ATTiny85?

Rafael

On 4/16/23 22:09, Ashhar Farhan wrote:
> Ah,? a good spot. I wanted to check how fast the adc works. If you
> see, the pin 5 is being flipped on each iteration of the loop.
So, I
> connected the pin5 to an oscilloscope to measure the time periods.
> It is cruft. It needs to be removed.
> - f
>
> On Mon, Apr 17, 2023, 12:11 AM Rafael Diniz
<rafael@...>
> wrote:
>
>? ? ?Hi Ashhar and all,
>
>? ? ?What does it mean this part of the code of the ATtiny85, I don't
>? ? ?get it:
>
>? ? ?--
>? ? ??? if(flag == 1){
>? ? ????? digitalWrite(5, LOW);
>? ? ????? flag = 0;
>? ? ??? }
>? ? ??? else {
>? ? ????? digitalWrite(5, HIGH);
>? ? ????? flag = 1;
>? ? ??? }
>? ? ?--
>
>? ? ?The example from Nicholas Zambetti does not have this:
>
>

>
>
>? ? ?Cheers,
>? ? ?Rafael
>
>
>
>
>
>
>






Re: About ATiny85 code

 

I built one with an Arduino nano, a 10uf cap and two resistors. Not sure where I saw the circuit diagram.
- f

On Mon, Apr 17, 2023, 1:57 PM Rafael Diniz <rafael@...> wrote:
Thanks Ashhar, there is what I thought. Btw, which "burner" do you use
to write the firmware to the ATTiny85?

Rafael

On 4/16/23 22:09, Ashhar Farhan wrote:
> Ah,? a good spot. I wanted to check how fast the adc works. If you
> see, the pin 5 is being flipped on each iteration of the loop. So, I
> connected the pin5 to an oscilloscope to measure the time periods.
> It is cruft. It needs to be removed.
> - f
>
> On Mon, Apr 17, 2023, 12:11 AM Rafael Diniz <rafael@...>
> wrote:
>
>? ? ?Hi Ashhar and all,
>
>? ? ?What does it mean this part of the code of the ATtiny85, I don't
>? ? ?get it:
>
>? ? ?--
>? ? ??? if(flag == 1){
>? ? ????? digitalWrite(5, LOW);
>? ? ????? flag = 0;
>? ? ??? }
>? ? ??? else {
>? ? ????? digitalWrite(5, HIGH);
>? ? ????? flag = 1;
>? ? ??? }
>? ? ?--
>
>? ? ?The example from Nicholas Zambetti does not have this:
>
>? ? ?
>
>
>? ? ?Cheers,
>? ? ?Rafael
>
>
>
>
>
>
>






Re: About ATiny85 code

 

Thanks Ashhar, there is what I thought. Btw, which "burner" do you use to write the firmware to the ATTiny85?

Rafael

On 4/16/23 22:09, Ashhar Farhan wrote:
Ah,? a good spot. I wanted to check how fast the adc works. If you see, the pin 5 is being flipped on each iteration of the loop. So, I connected the pin5 to an oscilloscope to measure the time periods.
It is cruft. It needs to be removed.
- f

On Mon, Apr 17, 2023, 12:11 AM Rafael Diniz <rafael@...> wrote:

Hi Ashhar and all,

What does it mean this part of the code of the ATtiny85, I don't
get it:

--
?? if(flag == 1){
???? digitalWrite(5, LOW);
???? flag = 0;
?? }
?? else {
???? digitalWrite(5, HIGH);
???? flag = 1;
?? }
--

The example from Nicholas Zambetti does not have this:




Cheers,
Rafael







sBitx Developer¡¯s Edition (v1) ¡ª how to protect the RPi4?

 

A few of you are probably familiar with my experiences with the DE version of the sBitx. There have been quite a number of different things happening which, by Occam¡¯s razor, are in my opinion for the most part likely explained by unexpected spurious oscillations, some of which I have actually documented. My most recent trouble was solved by putting in a new Raspberry Pi 4. The previous one toggled the PTT line when pressed (pin 23 on the digital board connector) but there was no voltage on the TX line when PTT was pressed (pin 27). Putting in a new RPi 4 solved the problem. I now have 26 volts P-P on the 2N2219a driver collectors (Q15) and now I need to install new IRFZ24N finals (one had shorted).

This is the third Raspberry Pi that has failed during normal operation. The Pi was seated in the socket, the digital board as well, and so that error can be ruled out. Two others previously had also failed, and each of those had problems with the I2C lines (bit banged, I know) communicating with the Si5351a. I use one of these now as an OctoPrint server for 3D printing, so at least that one functions even though I can¡¯t use it for the sBitx.?


At this point I have to assume that for whatever reason in my particular sBitx I run the risk in the future of damaging the TX line from a working Raspberry Pi, or the SDA/SCL lines to the Si5351a, or perhaps some other GPIO line on the Raspberry Pi. How would one protect the vulnerable lines from voltage transients? Back to back 1N4148 diodes? Bypass capacitors? Optical isolators? I am running on my 4th Raspberry Pi, the fifth if you include one with the onboard 3.3V regulator fried by an error on my part. Does anyone have any suggestions? I¡¯m awaiting the delivery of a new sBitx v2 that will hopefully be less eventful, but I have put too much effort into this Developer¡¯s Edition to leave it alone. As always, thanks everyone for your wonderful help.

Jack
N6LN