¿ªÔÆÌåÓý

Re: sBitx process no longer starts


 

¿ªÔÆÌåÓý

Isn¡¯t it so nice to have open source equipment? ? Makes it so much easier to diagnose.

I cracked this radio open for the first time today to show 4 middle school students, who were reasonably well impressed. ??

Guess what they elected to do the next time or a little ham club meets? ? They want to learn Morse code!

This puzzled me so we talked it over with an education major and she said that students of that age group love secrets. ?If I get them doing Morse code, I bet I can turn them into amateur radio operators eventually. ?They will be so pleased to be able to send secret messages!!


Gordon Gibby.?



On Aug 18, 2022, at 18:16, Steve Beckman <ssteven3sb@...> wrote:

?
Hi John;

The error message you're getting is coming from the i2cbb.c module (so great to have access to the sBitx source code!) That module is generating the error because it's finding the I2C serial data line is at a logic 0 / low voltage level when it should not be. Looking at the sBitx schematic, the Bit-Banged I2C bus communicates with the SI5351 synthesizer chip through pins 39 and 37 of the connector mating the digital daughterboard to the motherboard. Pin 39 is right on the end of the connector, so that's of note and worth a careful look. The SDA and SCL lines have to be pulled high with resistors R1 and R2, both 3.3 K Ohms, or else they can float low and cause this error.

So - possible problems:
1) Pin 39 from the digital board not mating properly with the motherboard - check that the digital board is fully inserted into the motherboard.
2) Regulator U7 on the main board not providing 3.3v to the SI5351 and the two pull-up resistors R1 and R2
3) R1 on the motherboard missing or damaged
4) SI5351 shorted / damaged

Hopefully it's just the mating of the digital daughterboard to the main motherboard - and you'll be back on the air shortly.

73; Steve, N3SB


On Thu, Aug 18, 2022 at 5:56 PM John Terrell, N6LN <N6LN@...> wrote:
I also ran raspi-config to make sure i2c was enabled. No change. I get the same error.

Join [email protected] to automatically receive all group messages.