In the Groove page, Beaglebone (mine) and Raspberry PI have a red cross on them, due to SW lack of library (I suppose).
Now I’m trying to write a python library to read/write to the sensor with my Beaglebone (Black Wireless) with I2C functions.
I’m not lucky at the moment since I try to write on it (e.g. set the led on) but it doesn’t turn it on or I can’t read the firmware version on it.
The sensor works because I tried it with UDOO/Arduino board and its sketch.
Unfortunately, the libraries we have for the Multichannel Gas Sensor aren’t working great.
We do have plans for providing a stable library in the future but we don’t have yet time estimates on it.
On the other side of things, I’m kind of confused as to whether you’re using a BeagleBone or a Raspberry Pi.
Let me quote:
Can you clarify us this aspect?
That’d would help us.
Moving on to the next, can you tell us the reason you are using the -r option for the i2cdetect command?
I quote from linux.die.net:
“-r” command option
Use SMBus “read byte” commands for probing (by default, the command used is the one believed to be the safest for each address). Not recommended. This is known to lock SMBus on various write-only chips (most notably clock chips at address 0x69).
Getting UU when i2cdetecting means that the I2C address(es) is/are already being used by some other bit of software.
Sorry I got confused in the first thread. I own a BeagleBone Black Wireless at the moment, not a RasPI even if the I2C library I found from other sensors works well with BBBW too. (For example I can read RTC DS3231 or a BMP180).
About -r option, I was following some guides on the Web in ordero to check sensor signal. (like this one).
Note that the gas sensor is correctly added on 0x04 and it’s not kernel-reserved.
Fortunately my 0x04 address is free even I read it’s a risky address to talk with sensors.