About Raspberry Pi 3 Power Consumption - raspberry-pi

I'm just bought a new Raspberry Pi 3 (and also 5V,2.5A Power Supply). And I'm totally a fresher to this so before to start using it I have some few question about its power.
I'm now connect my Pi with:
1. 1 Screen Monitor (Powered with another Power Supply) connecting through HDMI.
2. 1 Keyboard (USB port).
3. 1 Mouse (USB port).
4. 1 External Drive WD My Passport Ultra (with 3.0 USB cable) (USB port).
My question is does my Pi have enough power to handle all this above mentioned devices and if it is, can I use one more USB port for another device such as WD Passport and GPIO for a radiator fan ?.
Thank you for all your helps.

When your Pi will have not enough power for all peripherals you will see small yellow flash on screen. Then you should upgrade your power supply.

Related

Bidirectionally communicate a Roomba robot other than a Create model with raspberry pi

I've been trying to communicate different models of Roomba vacuum robots, 9xx and 6xx series, with a raspberry using the sci port of the roomba with no success. The sequence of steps have been:
connect pins 3 (rxd), 4 (txd), and 6 (ground) of the roomba port (5v) with a sparkfun logic level converter.
connect the output (3.3v) from the logic level converter to the gpio of the raspberry pi. Roomba Rxd to rpi txd, roomba txd to pi rxd, ground to ground.
connect rpi 5v to logic level converter HV and at the same time LV to gpio pin 1 (3.3v) for feeding high and low voltage required by the logic level converter.
disable serial console of the rpi
enable serial port hardware of the rpi
install and then open minicom in the rpi using this command
minicom -b 115200 -o -D /dev/serial0
place the roomba in the charging dock
I would now expect to read information about the charging process of the roomba in the minicom console but that's not happening.
Anyone knows if any of those steps is wrong?
My goals are to been able to read robots bump sensors in first place and then control movements of the robot from a pc using the rpi in between.
Thanks for any help.
Check this webseite. it's explaining exactly how to connect the roomba to the raspberry using an logic level converter
https://domoticproject.com/roomberry-surveillance-robot-roomba-raspberry-pi-zero-w-camera/

How can I connecti Raspberry pi 4 to pixhawk?

I want to create a connection between pixhawk and raspberry pi 4 model B.
When I connect the Pixhawk to the usb port of raspberry via micro-usb, I can send commands to the pixhawk with the drone-kit scripts on raspberry.
However, when I connect the telemtry2 port to raspberry's 14th and 15th GPIO pins (rx-tx) in pixhawks, the same script gives a heartbeat error.
I have done the configuration of uart pins with rasp-config. The /boot/config.txt file is as follows. Also, when connecting from usb, I use the connection string value "/ dev / ttyACM0" and "/ dev / serial0" when the UART pins are connected.
Via mission planner:
SERIAL 2 PROTOCOL = 2 , SERIAL2 BAUD = 921
I followed this link: https://ardupilot.org/dev/docs/raspberry-pi-via-mavlink.html
Since there is no GPS installed, I set the GPS and compass control values ​​to 0 on the mission planner. That's why the pixhawk is in arm state. (blue light)
Thank you..
Have you set the following parameters?
MAV_1_CONFIG = TELEM 2 (MAV_1_CONFIG is often used to map the TELEM 2 port)
MAV_1_MODE = Onboard
SER_TEL2_BAUD = 921600 (921600 or higher recommended for applications like log streaming or FastRTPS)
Reference:
https://docs.px4.io/master/en/companion_computer/pixhawk_companion.html#companion-computer-setup
there is an easy way to connect raspberry pi with cube autopilot. the companion board lychee
https://dronee.aero/pages/lychee

Raspberry Pi 4b v1.1 k8s cluster USB hub power supply

I'm planning on building a cluster of 5 or more rpi4b (v1.1).
Tutorial for that: Build a Raspberry Pi Cluster Computer
All is fine and dandy except for the power supply for all the units.
I have no intention of having individual cords from each unit to the wall, so I thought of a USB hub power supply with multiple ports. This would also allow me to increase the unit count in the future will less hassle.
Also, assume an ethernet cable and a small SSD drive connected via USB per unit. No screen or HID device connected.
What would be a good fit for running the cluster 24/7?
I thought of these:
IWAIVON USB Wall Charger
Anker PowerPort Speed 4 Port
Anker PowerPort 10
RavPower Prime 60W 6 Port
Assuming that every USB port in the hub will be (eventually) connected and having in mind that RaspberryPi4B v1.1 specs states that it requires a 5v/3A power supply which none of these supply, what will be a good USB hub power supply? It doesn't have to be one I listed...

Connect two raspberry Pis using USB cable or USB-serial

I'm working on a project where I need two raspberry pis to communicate and the ethernet port is not free, I'm not allowed to make any changes to the GPIO pins, and I'm forced to use the USB port due to hardware considerations. Is it possible for them to communicate using a direct USB cable, or perhaps using two USB-RS232 cables?
Thanks!
Siddharth
I would use the TTL serial pins on the GIO header. See https://elinux.org/images/1/13/Adafruit-connection.jpg
You could create your own simple null modem serial cable - consisting of 3 jumper cables.
Connect pins
6 <--> 6
8 <--> 10
10 <--> 8
If you can't use the GPIO header - you can do a USB to USB connection using USBNET. http://www.linux-usb.org/usbnet/
Is it possible for them to communicate using a direct USB cable, or perhaps using two USB-RS232 cables?
You fail to mention exactly which Raspberry Pi version(s) you are using.
Only the Raspberry PI Zero can be used as a USB Gadget.
Since USB is a master-slave(s) interface & protocol, you cannot simply connect two Raspberry PI 1/2/3 boards together using USB, because that would be a master-to-master connection.
If you look hard enough for a (passive) USB Type A (male) to Type A (male) cable, you can find them, but it's a bogus connection that will not work.
There are active USB host-to-host cables (which contain a shared gadget), but support can be an issue.
You could connect a Raspberry PI 1/2/3 to a Raspberry PI Zero by USB, so long as the Zero's USB port was configured as a USB ACM CDC gadget.
However one simple solution is your alternative of installing USB-to-RS232 adapters to each board. A null-modem cable of three wires would suffice unless you needed hardware flow-control.
An alternative solution is installing USB-to-Ethernet adapters to each board (with static IP addresses, i.e. an ad-hoc connection). This approach provides a much faster connection than an RS-232 link, and is easily utilized by applications.

Getting 'Server is at 0.0.0.0' on serial monitor - in webserver

I bought a new Arduino Ethernet Shield and hooked it to the Arduino Uno.
I am trying to set the IP address of the device to 192.168.1.177 tried File-> Examples -> Ethernet-> Webserver.
When I upload this - I get a "server is a 0.0.0.0'message in serial monitor !
My IP is set to 192.168.1.177 and setup a mac address of 0xB8, 0x27, 0xEB, 0x98, 0x46, 0x61 in the webserver code.
Appreciate any help in setting this IP address. ( I tried other combinations as well )
The Arduino Ethernet shield is mounted on the Arduino Uno, and connections are lined up .
i fix this problem by pressing firmly the shield to the board
This can manifest from many different causes. I ran into this and figured out that in my case, my the USB port + cable were not allowing sufficient power to the Ethernet chip.
I have 3 cables, 6in, 3ft, and 6ft. Only the 6" one had sufficiently low voltage drop to power the shield.
I honestly couldn't believe it, but there was a 0.1V drop between the 6in and the 6ft cables. When plugged into A USB 3.0 port with the Arduino loaded, I measured ~4.5V for the working 6in cable vs ~4.4V for the non-working 6ft cable.
I have 3 types of USB ports: 1.1, 2.0, and 3.0. Only the USB 3.0 ports provided enough power to power the shield. Thus for my case, I had to use the shortest USB cable on the 3.0 port.
When the Arduino's 5V rail was sufficiently sagging, the 3.3 Linear Regulator entered dropout mode and on all the non-working configurations I saw ~3.1V on the Ethernet shield's 3.3V rail, which is apparently sufficient to cause this symptom.