Raspberry can't read usb and the cpu is really hot - raspberry-pi

i need help for my raspberry pi B+
Yesterday my raspberry can boot and used perfectly. But just now my raspberry can't read my usb mouse and usb keyboard. And the most terrifying is raspberry cpu is really hot, i dont know what happen to my raspberry. I'm using adaptor for 5V and 1A for supplying my raspberry, and before that tragedy happen, i'm mounting my sensor, LCD 20x4 and anything else that worked perfectly. Can someone explain to me, what's going on my raspberry and what can i do to fix it? :(

I had similar problem like You.
Power Supply - I recommended 5V 2A Power Supply 2) And Network ethernet patch cable shielded (with shield or ground line).
Then try another keyboard or mouse.
As is written above login to your R-Pi via SSH.
Install HTOP : sudo apt-get install htop
And watch what is eating your CPU.

Related

How could I make the raspberry pi as a WIFI and ssh module

For a digital design course, we have to use a microcontroller as the CPU of the system. The chip we plan to use is STM32L0C8T6. We want to integrate the SSH function into a keyboard. The way we plan to do it is to connect the STM32 with a Raspberry pi zero or 2 through UART or SPI. The Pi will connect to the WIFI and connect to other hosts through SSH. An LCD display is also connected to the STM32 which will work like the monitor, displaying all things you will see when ssh, like whatever is shown in the terminal when ssh.
My question is how to build the connection between the terminal and STM32. One possible way is to dump everything in the terminal into a file and send the file back to STM32 for display. I think this will be really slow. Are there any better ideas?
The question sounds wired, and I know we could connect LCD directly to the Pi, but this is the project requirement to have to follow. The LCD has to connect to the microcontroller.
Thank you so much!!!!

cat /dev/ttyusb0 cannot allocate memory – raspbian

I need help for serial communication on raspberry pi. So, I'm using raspberry pi to read data from my solar inverter with docker and using Usb to rs232 cable for communication. The problem is after plug usb to raspberry pi I should set baud in raw mode /sudo stty -F /dev/ttyUSB0 2400 raw/ and all working good and when execute /cat /dev/ttyUSB0/ I see the data from inverter but only for 2 days and stop read data. After stop read data, I should reboot pi and again set baud and it start working again for 2 days. But when execute command /cat /dev/ttyUSB0/ when not receive data I see "Cannot allocate memory".
I am using raspbian lite os.
My question is why cannot allocate memory and how to fix it.
Thank you for help in the advance
That's screenshot

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/

Ethernet port not working on Raspberry Pi with GPIO pins connected

Raspberry Pi model: 3B
Running Raspbian OS
Recently I bought a Hyperpixel 2.1 round, which uses all of the GPIO ports. Whenever I plug the Raspberry Pi into my network switch, it is unable to connect to the network with the Hyperpixel attached. However, when I removed the Hyperpixel, the Ethernet capability came back.
I'm fairly sure it's a software issue given that there shouldn't be any problems with running all gpio pins in addition to Ethernet.
Is this a quirk with the Raspberry Pi that it doesn't like having all GPIO ports occupied as well as Ethernet? And how would I potentially go about fixing this, perhaps through command line or in the boot config?

How to comunicate the Raspberry Pi 4 with a PC (runing Gazebo) and get sensors topic on the Pi?

I have running some UUV simulator on Gazebo 9 and ROS melodic and Ubuntu 18.04 in a PC. So i like to connect the rasppbery Pi 4 with the PC (running the Gazebo UUV Simulator) and develop a node in the Rasppbery Pi that give me for example the Camera stream data on the Gazebo UUV simulator. So my question is how to communicate the PI with the PC(running the Gazebo UUV Simulator) and can get the Camera topic or any other sensor topic from the Gazebo UUV Simulator in the Pi?
Any Help Thanks
Yes, you can communicate across devices with ROS, but there are a few things that need to be done first.
You need to make sure your ROS_MASTER_URI is setup correctly. This is an environmental variable that tells ROS where to look for the roscore. By default it is set to localhost:11311. So on the Pi you'll need to do: export ROS_MASTER_URI=http://<master_ip>:<master_port>.
Next you need to make sure ROS can actually resolve names and connect. Make sure the computer has IP/Hostname info for the pi and vise-versa. For Ubuntu 18.04 do this by setting the IP/hostname for both machines in /etc/hosts. Also make sure the hostnames match up with /etc/hostname
After that you can just start up a ROS node/core on the host machine and the Pi will be able to see and interact with the topics like normal.