What happened to Raspberry Pi 2- and 3- Model A?
Basically they never got arround to making them.
Is there a major distinguishable difference between A and B models independent of the generation?
The "B" models have the USB hub with Ethernet chip while the "A" models do not. Therefore A models only have a single USB port and no Ethernet port. A models ...
You are running Raspbian Stretch and use /etc/rc.local. I don't have followed your attempts to find the error in detail but it seems you presume old style sequential behavior of rc.local for SysV init system. But you cannot do it since Raspbian Jessie, the predecessor of Raspbian Stretch. Since then SysV including rc.local is emulated by systemd that works ...
Python is included with the Raspbian distribution, and you won't need to install it separately. There are two versions of Python that are in current use, and both are included with Raspbian. The Raspberry Pi Organization has an introductory page for new Python users that you should read as it explains some of the basics.
See How can you recover your password? which explains how to reset the password.
HOWEVER if someone has modified the password there is no way of knowing what else was done.
Either restore from your backup OR do a fresh install - you should have given up on Jessie a year ago - it is unsupported!
The VERY FIRST thing I do on ANY installation is change the ...
You don't want to relaunch your program like that - every time you do, you fork the process. See fork bomb.
If you construct your program so that you have a block of code you can re-run when the button is pressed, that would work much better.
from gpiozero import Button
btn = Button(17)
print("button was pressed")
If you read the documentation, there are two mistakes in your code. First, just use import l293d. Second, use motor1 = l293d.DC(22, 18, 16)
There isn't a motor attribute, but there is a DC attribute for DC motors.
This runs on my system.
jay@gotham:~/python$ python3 test.py
[l293d]: Can't import RPi.GPIO; test mode has been enabled:
The approved answer did not work for me with Stretch. If it does work it will give you an older version. I tried a lot of different things to get the latest version and this was the only one I found that worked. From the instructions on this page https://www.rabbitmq.com/install-debian.html
curl -s https://packagecloud.io/install/repositories/rabbitmq/...
L4 through L7 appear to be surface-mount common-mode chokes on the HDMI output's TMDS pairs. It may also be possible to bypass a missing choke by bridging each processor-side pad (right side of photo in question) to its corresponding connector-side pad (left) with thin wire or component lead trimmings, at the expense of the HDMI output being less reliable ...
Turns out it was some sort of OS glitch or incompatibility. I ran the following commands overnight and it fixed the problem
sudo umount /dev/sda1 # /dev/sda1 is the name of my external drive partition
sudo fsck -Cy /dev/sda1
It appears that VMware are working on a bare-metal hypervisor (ESXi) for 64-bit Arm processors, as they have showed off on their VMworld US shindig in Las Vegas (August 2018).
It seems that soon we will be able to cluster multiple Raspberry Pi 3 model B+ (arm64), into a normal working virtualization solutions as wee see today with x86.
Strange I2C behaviour ... sorry for the title, I don't know how to
Well, in the last couple of months playing with a couple of I2C devices, I have been in the same trouble as yours. First，a more specific title could be "A Intermittently Unreliable I2C Device Address Detection Problem".
Accidentally from then I got strange results ...
Sorry about digging up an old thread, but I came across it while looking for ideas on setting up my own ILI9488 on a Pi, and I've got a solid hunch on this problem.
I have not tried this, but have seen this issue with other display controllers (ILI9341). There is an BGR/RGB parameter which sets the colour order. It looks like you have a blue/red swap issue (...
Finally - as of November 2018 - there is a Raspberry Pi 3 Model A+; which the Foundation states is
[...] one of our most frequently requested “missing” products.
By the way, the Foundation also points out
[...] that the 3+ platform is the final iteration of the “classic” Raspberry Pi: whatever we do next will of necessity be less of an evolution, ...
There is no need to modify the wiringPi source code to read or write multiple bytes.
wiringPi provides a simple wrapper around a few I2C/SMBus commands. If the commands are not sufficient you can use the underlying C read/write calls.
When you call wiringPiI2CSetup the return value is the standard Linux filehandle, say fd.
To write multiple bytes use ...
The "load" ( light bulb) is connected to GPIO - output pin - and source of power for it. If the load power source / supply is "HIGH" , say 3,3V and the initial state of the GPIO is also "HIGH" there will be practically no current flow between GPIO pin and device power, hence the "light bulb" will be off. Setting the GPIO to "LOW" / ground you create ...
You would obviously need more Ethernet ports to make an Ethernet switch, at least one. The only available interfaces are USB, even the Ethernet port on the board is connected to the USB controller internally. With USB2, you have about 30MB/s available bandwidth. Each packet passing from one side to the other has to pass the USB twice, on the way in and out. ...
If you completely remove the shield, and connect pin 8 to pin 10 on the Pi, can you get characters echoed back?
How are you writing to the port? Through /dev/ttyX ? Which terminal emulator? Minicom? Make sure it is not in local echo mode and that whatever you type comes back. Then disconnect the link from 8 to 10 and confirm the echo stops. Until you can ...
You can use USB pendrives as much as you have free USB slots. If you want to keep programs and data on different storrages you can follow Debian - Recommended Partitioning Scheme.
For new users, personal Debian boxes, home systems, and other single-user setups, a single / partition (plus swap) is probably the easiest, simplest way to go.
Milliways and Dirk are correct, import* was the problem. I should have realized that both GPIO Zero and Tkinter have a Button class, so one was overwriting the other and causing the error.
Thank you for the help!
First, try to do a clean install with this image -- the image provided by the company that manufactured the touchscreen, preloaded with the driver you need. Use Etcher, and follow the steps here, using the image above. Don't forget to "sudo apt-get update" and "sudo apt-get upgrade."
If that fails,
Do a clean install of Raspbian (if you don't have any ...
If two devices are compatible to the point they can share the same driver, the driver usually gets the name of the first device it was implemented for. Additionally, in your case the driver specifically states
We can't determine type by probing.
Simply put, there is no way for the driver to tell whether you got a DS1307 or a DS3231.
You can't access the data directory locally, nextcloud will complain if you change the permissions or add files directly as an anti tampering measure. To do what you describe you'll need to use webdav and mount nextcloud as a webdav share on the pi and then you'll be able to save files straight to it via that folder.
The number of relays is an open ended question.You can have as many relays as your configuration allows you to have. If you are using expansion boards that is your limit. If you are using SPI controlled relays then probably the max amount the SPI addressing allows you to have.
You can connect two Pi's together but you will need to write software to control ...