Keyboard Shortcuts
ctrl + shift + ? :
Show all keyboard shortcuts
ctrl + g :
Navigate to a group
ctrl + shift + f :
Find
ctrl + / :
Quick actions
esc to dismiss
Likes
Search
sBitx Starting Error
Hi JJ,
Thanks I will be making the hardware myself. I am just trying to get the digital part to work. A raspberry Pi, a screen, an audio codec from Mikroe and Si5351 Hmm, I do not understand your last question. I think I downloaded the image from the first message here : /g/BITX20/topic/98987974?p=%2C%2C%2C20%2C0%2C0%2C0%3A%3Arecentpostdate%2Fsticky%2C%2C%2C20%2C2%2C360%2C98987974 It says V2 but while running sbitx on cmd, it says v3.0 Thanks for any help |
Oh ok. Hopefully these folks can assist. I do not have familiarity with building the sBitx from scratch.??/g/BITX20/search?p=created%2C0%2C%2C1%2C2%2C0%2C0&q=homebrew?
|
It looks like a wiring error with your si-5351. ?The si-5351 is on the bit-bang I2C bus and goes to different pins in the Pi. ?Check the schematic for the connections. ? If the si-5351 and MIKROE board are both connected properly the sbitx gui will start. Dean |
To clarify Dean's statement, the audio codec and the Si5351 are on different I2C buses.? The sbitx uses a Wolfson WM8731 codec on the Raspberry Pi system I2C bus (GPIO pins 3 and 5).? The RTC and SWR/PWR sensors are on the I2Cbb bus on pins 31 and 33.? I am unsure if the MIKROE board will work with the software as it is designed for the Wolfson codec to be alone on the system I2C bus (pins 3 and 5).? Ashhar Farhan ran into issues with the codec when using one I2C bus for all three devices.
The "i2cbb.c:writing address failed at 8" is normal for the DE version, as address 8 is the SWR/PWR sensor not provided until the V2 and later sbitx from HFSignals. 73 Evan AC9TU |
Thanks Evan, I didn't have access to the source code. And I'm on travel right now
The SBITX software works perfectly with the MIKROE? prototype board and the SI-5351 module. Reference all of my other posts on the Homebrew rig. The one caveat with the proto board is you do need to swap the crystal out for a 12 MHz Crystal or you will have frequency alignment problems. I still suspect the problem is wiring. Dmoo' can you verify that the audio codec is working as I suggested in the previous response? 73, Dean |
Thank you Dean and Evan,
The codec is working. The GUI starts. The Si5351 is also working (confirmed on spectrum analyzer) I guess I should start working on the hardware part :) before worrying about the 12MHz misalignment. I really can't tell what the issue was. Maybe because I used an external PSU for the 3.3V for codec and si5351. Maybe that was the problem. Thanks. Starting excitedly with the LPF |
That could be. How are you powering the Pi? For the final build you should use a buck converter set to about 5.4 volts and power the pi through the GPIO pins.? With that, I had no problem picking off the 3.3 volts from the pi on board regulator.??
After having some stability problems with the SI-5351 clocks with Farhan:s advice I moved the? SI 5351 off of the digital board and on to the analog board and powered it with its own voltage regulator. To avoid ground loops there should be one and only one ground path to the digital board and that is going back to the input 13.4 volt supply.? So when you're done the only connection between the pi and the SI-5351 will be the I2C lines. Yes you can wait on changing out the crystal who are you work on the analog circuit. 73, Dean 73, Dean |
to navigate to use esc to dismiss