Recent content by f18m

hi @alexburcea , I wanted to report back after several days a good news: after I received a Raspberry Pi4 and I started using it, I never found the I2C hangup happening again. I believe it was an HW issue after all. I'm also wondering if it makes sense to change the software to use the...

Actually I was using a Raspberry Pi 1 (model B+) from 2014. I bought a Raspberry Pi4 and will install it soon... I really hope to get I2C communication stable with Raspberry Pi4... I will update. thanks for support.

Short update on this: the I2C bus lockup happened also today. I don't know how it's possible but even after several power-cycles, the I2C remains locked... at reboot the Raspberry keeps complaining: I'm not sure how's that possible. Nothing is wired on the pins of the I2C appearing on the GPIO...

Thanks, that helps a lot, my bad I didn't realize which version I bought:) Btw one suggestion: the availability of the interrupt line is not mentioned in the docs..it would be useful to mention that :) Finally I found some references to situations where I2C bus might lock up, see e.g...

Sorry I'm a bit confused. I downloaded the schematic (v3.0) from https://sequentmicrosystems.com/pages/sixteen-inputs-downloads but I cannot see anything connected between the chip U2 (it would be nice to know the part number, btw) and the GPIO11 a.k.a connector pin23 a.k.a. SPICLK... what am I...

Btw I found by chance the following thread: https://forum.sequentmicrosystems.com/index.php?threads/polling-inputs.58/ My understanding is that there is a special firmware for the 16 LV inputs board that provides a very short pulse on gpio26 (Same of the push button) to signal a change in any...

Ok thanks I will try that! Generally speaking, do you think it should be fine to poll at 1hz for several hours the I2c bus? In my experience it works for several hours (like 12-24) but then it enters this "hung" condition and requires a power cycle to restore :-(

I forgot to mention that I have a Raspberry with the 16LV digital inputs HAT currently stuck in this state where every I2C transaction is "transfer timed out". Before I power-cycle, is there any debug information I can retrieve to help understand the issue? thanks!

Hi all, I'm using this HAT: https://sequentmicrosystems.com/products/16-universal-inputs-card-for-raspberry-pi reading the input very frequently (1Hz, forever) and my application works fine for several hours. However, in a random way apparently, I get in my Python application the following...