Skip to main content
12 events
when toggle format what by license comment
Jun 18 at 1:53 comment added Kartman The soldering on the pins looks very suspect. You can see the solder has not filled the hole.
Jun 17 at 16:12 comment added winny @PMF Sorry I missed that part. OP is fumbling in the dark.
Jun 17 at 13:10 comment added PMF What is the exact output of i2cdetect -y 1? Just nothing detected or an error message? Did you enable the I2C bus?
Jun 17 at 13:04 comment added PMF @winny If the OP has no multimeter, I doubt he has an oscilloscope.
Jun 17 at 8:47 comment added winny Good, then problem lies elsewhere. If you probe the I2C with a logic analyzer/oscilloscope, do you see any activity when you run i2cdetect?
Jun 17 at 8:04 comment added Kaizad Wadia Yes I have checked that it is the correct and only bus as far as I see. I am pretty sure the sensor should as it normally does for others and I would need the channel to use in my code, which doesn't work right now either because it can't detect the sensor.
Jun 17 at 8:02 comment added Kaizad Wadia Thanks for the responses! @winny I don't but the raspberry pi has inbuilt pullup resistors for i2c so I wouldn't think it's a problem there.
Jun 17 at 7:27 comment added Justme So it does not show up in i2cdetect scan. Do you use correct I2C bus number if there are several? Has the pins been set up for I2C use? Should the chip show up in the i2cdetect scan? Not all chips respond to dummy reads as the chip I2C protocol might require register address to respond and i2cdetect does not do that.
Jun 17 at 7:27 comment added winny Do you have I2C pull-up resistors somewhere?
Jun 17 at 7:10 history edited Kaizad Wadia CC BY-SA 4.0
added 22 characters in body
S Jun 17 at 7:08 review First questions
Jun 17 at 8:13
S Jun 17 at 7:08 history asked Kaizad Wadia CC BY-SA 4.0