I was also getting the same error. But now it is working for me.
First you install I2S microphone as shown here: https://learn.adafruit.com/adafruit-i2s-mems-microphone-breakout/raspberry-pi-wiring-and-test
After that while you are installing I2S amplifier go to the detailed installation section and skip the first 2 steps and start from "Create asound.conf ...
Using the answers from Dirk, I have got both my 2.8" TFT and RFID-RC522 working.
I have set dtoverlay=spi1-1cs in /boot/config.txt giving me:
$ ls /dev/spi*
I connected the TFT as normal and then assigned the RFID pins as follows:
RFID Pi Pin Pin Name
SDA 37 GPIO26 (dtparam sets this as CE0)
SCK 40 SPI1 ...
The 300-line script (direct link) is extensible, and for complex projects you'll likely have to modify it.
You can run your existing project through strace and look through the output to identify which files it accesses outside of /tmp. If you find various directories that pyserial or other components are writing to you'll have to set them up for temporary ...
If you want to have two different addresses you need to configure them with jumpers :
This board/chip uses I2C 7-bit addresses between 0x70-0x77,
selectable with jumpers https://www.adafruit.com/product/1912.
If a jumper is shorted with solder on the display, that sets the address
I figured it out with a little help:
Circuit Python doesn't work with this sht21.py, because it is smbus based. So here it is:
I used the multiplexer code from this homepage but this is all I needed
# TCA9548A I2C multiplexer
# I2C Address: 70 through 77
# Channel: 0 - 7
# class for the I2C switch
I used sudo bash to enter commands as sudo and found python3 temphumlogger2.py had same error. Within this sudo bash window I followed the CircuitPython instructions here to install all the modules again. After that temphumlogger.py now runs with and without sudo when I log in as pi.
As per comments I think I installed things as user instead of sudo.
You could create a simple python script that runs on startup with Cron. That script would display whatever you want for a small amount of time and then end. This would effectively tell you when your Pi's done with booting or if it still is.
You can enter this to edit crontab: crontab -e. Select Nano or any editor you're comfortable with and add a line like ...
The OP noted in a comment that she/he would be better supported with this way:
I would be better off continuing to use the RPi.GPIO interface for the kiln element pins for the sake of future compatibility/more elegant code even though I'm importing two input/output interfaces.
There are a few ways of doing this:
Normally if it's only a few connectors then DuPont cables are used. These are short cables (about 15-20cm is the longest I have) With ether male (sordid metal) pins or female (plastic block with metal grips in it) ends on them Care needs to be taken as some of the cheap ones are thing and do not push in to the breadboard ...
You can change pretty much everything desktop-related with this command:
That will let you change font sizes for GTK GUIs, as well as the font size for the title bar (window border), as well as icon theme, gtk theme, mouse cursor, window border color, etc.
Then to shrink the taskbar/panel, right-click --> Panel Settings --> Height --> set to ...
There are too many potential problems with the set up.
First of all you need to confirm your cobbler is correctly attached to the Pi and the breadboard.
Using a volt meter do you read 3V3 between a 3V3 column and a ground column on the breadboard?
Do you read 5V between a 5V column and a ground column on the breadboard?
If so try connecting the pin 18 ...
You need to look at a wiki to see how hobby servos are controlled. Also look up the meaning of PWM.
Basically they expect a series of pulses at about 50 Hz. That means they expect a series of pulses at about 50 per second.
Each pulse has a length. The length determines the angle the servo is meant to go to.
Generally a pulse of length 1500 µs means go ...
If you get any readings at all it is probably wired properly.
I suggest you try my DHT Python script.
Leave the module with the name DHT.py and then issue the following commands in the same directory.
python DHT.py x
Where x is the (Broadcom) number of the GPIO connected to the DHT22 data line.
Does the following turn on and off your relay accordingly?
import RPi.GPIO as GPIO
RELAIS_1_GPIO = 18
Setting a GPIO pin has a latching behavior. That is when you set it, it stays that same value until you tell it otherwise. So in your if statement, just add an else clause to reset it low if the value read is <=600:
if touch > 600:
print("moisture: " + str(touch))
OBSERVATION: I do not see a line of code / instruction to pull the GPIO back to low. If the observation is correct and this instruction is executed:
How would the line GPIO return to a low state?
Under what condition do you expect the GPIO to return to the low state?
What happens if the instructions is changed to:
I assume that you are using Raspbian so you should use a systemd Unit file to start the program. Because you can run it manual from the command line you are also able to run it with a Unit file. You can set the same conditions than running from a command line. Start with this simple Unit file. Create it with:
rpi ~$ sudo systemctl edit --force --full my....
The problem might be the SD PIN. I would try to run the speaker test:
while adjusting the voltage according to the given parameters:
to see if ...
Possibly the driver you are using is not the correct one for the screen, I had the same problem and changing the driver from SSD1306 to SH1106, and it worked correctly.
I installed the module as a normal user without sudo, so it was installed to that user's home directory and not the system. Running the script as root via sudo then meant that installation was not in the import path.
Whilst historically I've used the built in ntpd GPS drivers, these have become increasingly dated and buggy with newer hardware. More recently I've therefore moved from 127.127.20.0 to the shared memory driver 127.172.28.0.
This allows you to keep gpsd running (so you need to remove the "service gpsd stop" from rc.local), and gives potentially much better ...
The problem was a faulty speaker bonnet, as a new one worked fine. I sent it back to Adafruit, requested a diagnosis of the problem, and will update the answer if I receive one.
I also tried on a new Raspberry Pi and confirm that the bonnet and speaker set work OK when stacking the bonnet on top of the Power-over-Ethernet pins, without clipping the latter.
Your question is unclear, and so is the wiring. One can only guess from the colours what is supposed to be what.
All Gnd pins on the Pi are connected (and to the ground plane). The same is not true of the breadboard, but it is unclear what you expect to be connected. If you expect the power rails on both sides of the breadboard to be connected YOU will have ...
If you scroll down that page you linked to, in the learn section there a quite a few projects that use that board with the raspberry pi. One of them includes these instructions:
PAM8302 Audio Amplifier:
GPIO #1 (3V) on the Pi connects to VIN on the PAM8302. GPIO #9
connects to GND on the PAM8302. The +Postive and -Negative connections
are wired ...