Grove Pi+ CO2 MH-Z16 sensor - raspberry-pi

I am using a Raspberry Pi 3 B model with a Grove Pi+ (1.2.2 firmware), and Raspbian for Robots Image.
I have plugged in the CO2 MH-Z16 sensor in RPISER port, and I am trying
to execute the code that is available in Dexter's Github
I am getting the following issues:
First time I tried the code, it was working but it was getting very strange results, always out of range and strange temperatures.
It calls the sensor every 18 second.
Now, when I plugged-in the sensor in de RPISER port (with the rpi on), the raspberry pi get frozen. If I tried to restart it, it is not restarting until the sensor is plugged out the rpi. I do not know what is going on, and how to solve this issue. Sometimes, the rpi does not get frozen but the mouse and the keyboard suddenly stop working. If I try to restart the rpi whith the sensor, the rpi is not restarting, it get stucks.
Can I use this sensor in another port?
Any help or any hint?


Oh yes update your firmware. I also took a long time..
https://www.dexterindustries.com/GrovePi/get-started-with-the-grovepi/updating-firmware/

Related

How to get game code to send 5v signal from raspberry pi

I have a bit of a niche question, we have a game designer who has made a small game to run on a raspberry pi, this has been coded in 'gdevelop'.
Is there any way to get this code to send a 5v signal from the raspberry pi, we need a certain point of the game to send a 5v signal to trip a relay.
I don't currently have the code for the game but will hopefully receive it soon.
If this isn't possibly, would we be able to set the raspberry pi up to recognise the controller inputs, track them and send the signal upon the correct sequence of movements inputted simultaneously to running this game code.
The developer has said he plans to save the game as a windows exe on the pi with auto run enabled so one the pi is reset the game automatically starts up and sits waiting the input to begin.
Many thanks in advance and let me know if you need further information!

No GPS on Raspberry Pi LineageOS 18.1

UPDATED See edit!
I have installed LineageOS 18.1 for Raspberry Pi 4 (which is an awesome piece of software) and everything seems to be working correctly.
With the exception of GPS. I have an A9G connected to the Pi. It is connected to the first Pi's UART and I can see the data coming on ttyAMA0.
:/ # microcom -s 9600 /dev/ttyAMA0
$GNGGA,092800.998,4955.7547,N,00900.2330,E,0,0,,102.0,M,48.0,M,,*5E
$GPGSA,A,1,,,,,,,,,,,,,,,*1E
$BDGSA,A,1,,,,,,,,,,,,,,,*0F
$GPGSV,1,1,00*79
$BDGSV,1,1,00*68
$GNRMC,092800.998,V,4955.7547,N,00900.2330,E,0.000,0.00,211021,,,N*55
$GNVTG,0.00,T,,M,0.000,N,0.000,K,N*2C
$GNGGA,092801.998,4955.7547,N,00900.2330,E,0,0,,102.0,M,48.0,M,,*5F
$GPGSA,A,1,,,,,,,,,,,,,,,*1E
$BDGSA,A,1,,,,,,,,,,,,,,,*0F
$GPGSV,1,1,00*79
$BDGSV,1,1,00*68
$GNRMC,092801.998,V,4955.7547,N,00900.2330,E,0.000,0.00,211021,,,N*54
$GNVTG,0.00,T,,M,0.000,N,0.000,K,N*2C
$GNGGA,092802.998,4955.7547,N,00900.2330,E,0,0,,102.0,M,48.0,M,,*5C
I changed the GPS receiver to use ttyAMA0 in /vendor/build.prop
# GPS ro.kernel.android.gps=ttyAMA0
I also trying with adding
ro.kernel.android.gpsttybaud = 9600
or
ro.kernel.android.gps.speed = 9600
But not a single App can receive GPS data.
I have the feeling I am missing something very simple but essential.
Any help very appreciated
EDIT
Ok, I am a step further. The first problem was apparently, what a bummer, a permission issue.
I adjusted it in the file: /vendor/ueventd.rc
From:
/dev/ttyAMA0 0660 bluetooth bluetooth
To:
/dev/ttyAMA0 0660 system radio
Now it seems that the data is being received and correctly interpreted. But when I open a GPS testing App, the signal is flickering. It almost like if something else is reading from ttyACM0.
Is it possible?
just to clarify what I mean with "flickering", please take a look at https://cloud.sobi.pro/f/68f0398aea1549918376/

I also had the same flickering issue. I can see it in a map program or with physics toolbox where I can see the GPS LAT LONG. It flickers between the "real" position and 0.00000 for the LAT and LONG.
I am using LineageOS17.1 on a Raspberry Pi 4
my Ultimate GPS USB is from Adafruit and is on /dev/ttyUSB0
I tried updating build.prop in both /vendor and /system with the
ro.kernel.android.gps.speed = 9600
and
ro.kernel.android.gps = ttyUSB0
The solution that I eventually used was to remove the r0.kernel... from both build.prop and use the app GPS Connector
https://play.google.com/store/apps/details?id=de.pilablu.gpsconnector&hl=en_US&gl=US
Enable in developer options under "select mock location app" you can select the GPS Connector.
You can have the GPS Connector app start at boot.
If you find a more elegant solution than using an app, please reply.

i2cdetect on Raspberry pi 4 shows different addresses everytime the command is entered

I'm working with a Raspberry Pi 4 to test different sensors. Right now I am trying to connect the DLVR-L05D-E1BD pressure sensor by All Sensors. My problem right now is that when I enter sudo i2cdetect -y 1 in the command window to find the address, I get a bunch of addresses listed which changes everytime I enter the command. This continues until every address is shown in the table.
I also found out that if I remove the power or Vs connection from the sensor (so only SDA, SCL and ground are connected to the Pi) and then enter sudo i2cdetect -y 1, I get only one address (the expected one, 28).
To make sure nothing was wrong with the Pi I connected a particle sensor (Sensirion SPS30) and managed to detect it with the same command.
My code also sometimes manages to communicate with the pressure sensor while other times I get "Remote I/O error".
I've used two different units of the same model of pressure sensors and both have the same problem.
Any help or suggestion would be highly appreciated!
EDIT: When I reboot the Pi, I still have the same problems, however after a while the addresses just keeps changing everytime I run i2cdetect, never converging at showing all addresses.

MotionEyeOS without internet

I am trying to build a small system which include a rPi and rPi Zero. rPi act as local wifi hotspot and rPi zero connect to rPi hotspot.Then I access zero camera through rPi. My diagram looks like this.
It works totally fine if I have a LAN connection. Once I remove the lan connection motionEyeOs won't stream any data. And even it disconnect from wifi and go to boot loop.
So my question, is there any way we can make motionEyeOs works with out actual internet ?.

The answer to your question: You can set link_watch="false" in /data/etc/watch.conf
But this come with a few other problems:
If your camera boots without network connection (internet), it has no time set (your videos and images could get overwritten)
If your camera boots without or looses network connection (internet), the camera does not try to reconnect and you have no other chance and have to connect a keyboard an monitor to it
A hardware clock would help for the first problem but I am still searching for a solution for the second. If you already have one, I would appreciate it, if you could help me out.

https://www.raspberrypi.org/documentation/usage/camera/raspicam/raspivid.md
This is what I use for an offline video recorder and it only needs the software and a power source..Camera also but you get the idea. Keep your image (os) small as possible as this can fill an sd card fast. If I remember right, I used 800 x 600 and it would use a gig an hour.

eInk screen is causing reboot on RaspberryPi0W

I'm trying to get to work a raspberry pi 0 W and a pervasive display eink screen together.
But, every time when the screen refresh, it reboots the pi 0. Software works great on a RPi3 but not on Rpi0w with Raspbian Lite.
Here is the soft : EpaperDisplay
Here is the screen : Screen
There is no log in /var/log/messages, neither in /var/log/syslog. Every time it reboots, it's erasing history, logs ...

If this was a software issue, you would probably see something in the logs (or you'd at least see a kernel panic message on the console in the HDMI output if you have a screen connected there).
If you have nothing in the HDMI screen when the pi crashes, I'd suspect that the display is using more power than your power supply can provide. Try with a PSU with a higher ampere rating.
If a better power supply does not help, it can be that the display sucks too much 3.3v from the raspberry pi than the zero can provide. In that case you should try feeding the display via a separate 3.3v regulator.