{"action":"created","issue":{"url":"https://api.github.com/repos/joan2937/pigpio/issues/25","labels_url":"https://api.github.com/repos/joan2937/pigpio/issues/25/labels{/name}","comments_url":"https://api.github.com/repos/joan2937/pigpio/issues/25/comments","events_url":"https://api.github.com/repos/joan2937/pigpio/issues/25/events","html_url":"https://github.com/joan2937/pigpio/issues/25","id":108321952,"number":25,"title":"Interrupt - Edge Falling - Problem","user":{"login":"rhowitt","id":6017870,"avatar_url":"https://avatars.githubusercontent.com/u/6017870?v=3","gravatar_id":"","url":"https://api.github.com/users/rhowitt","html_url":"https://github.com/rhowitt","followers_url":"https://api.github.com/users/rhowitt/followers","following_url":"https://api.github.com/users/rhowitt/following{/other_user}","gists_url":"https://api.github.com/users/rhowitt/gists{/gist_id}","starred_url":"https://api.github.com/users/rhowitt/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/rhowitt/subscriptions","organizations_url":"https://api.github.com/users/rhowitt/orgs","repos_url":"https://api.github.com/users/rhowitt/repos","events_url":"https://api.github.com/users/rhowitt/events{/privacy}","received_events_url":"https://api.github.com/users/rhowitt/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"milestone":null,"comments":5,"created_at":"2015-09-25T13:00:50Z","updated_at":"2015-10-20T11:10:11Z","closed_at":"2015-10-02T08:09:13Z","body":"We are using  the PIGPIO python library on a raspberry pi 2 using python 2.7.\r\n\r\nOur project has a Raspberry Pi hooked into another PCB that has a micro controller and gpio expander (SX1506).  Both the micro controller and SX1506 send interrupts to the raspberry pi via the Pis GPIO (BCM 12 and 26 ).  The interrupt is to be sensed by the Pi on a falling edge ( 1->0 ).\r\n\r\nWe found that if those pins are high (1) when the Pi is turned on, PIGPIO will not create an interrupt the first time the pin goes from 1 -> 0.  Once the pin on the  GPIO has transitioned from 0 back to 1, PIGPIO will create an interrupt the next time the pin goes from 1 -> 0.\r\n\r\nIn the code the GPIO pins are set as an Input, and to start a subroutine procedure when the pin senses a falling edged.\r\n\r\nIs there some intialization of the GPIO I am missing?\r\n\r\n"},"comment":{"url":"https://api.github.com/repos/joan2937/pigpio/issues/comments/149529739","html_url":"https://github.com/joan2937/pigpio/issues/25#issuecomment-149529739","issue_url":"https://api.github.com/repos/joan2937/pigpio/issues/25","id":149529739,"user":{"login":"rhowitt","id":6017870,"avatar_url":"https://avatars.githubusercontent.com/u/6017870?v=3","gravatar_id":"","url":"https://api.github.com/users/rhowitt","html_url":"https://github.com/rhowitt","followers_url":"https://api.github.com/users/rhowitt/followers","following_url":"https://api.github.com/users/rhowitt/following{/other_user}","gists_url":"https://api.github.com/users/rhowitt/gists{/gist_id}","starred_url":"https://api.github.com/users/rhowitt/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/rhowitt/subscriptions","organizations_url":"https://api.github.com/users/rhowitt/orgs","repos_url":"https://api.github.com/users/rhowitt/repos","events_url":"https://api.github.com/users/rhowitt/events{/privacy}","received_events_url":"https://api.github.com/users/rhowitt/received_events","type":"User","site_admin":false},"created_at":"2015-10-20T11:10:11Z","updated_at":"2015-10-20T11:10:11Z","body":"New Problem. It is not with pigpio, but hope you can shed some light.  This one has to do with I2C.  Same project as above.  The system has the following devices on the I2C bus 2 LCD (20 char x 4 lines ) , Humidity, pressure , SX1506 ( gpio expansion ) and the pcb micro.  The I2C bus is at baudrate=100000. There have been strange characters on the LCD , the humidity probe has random errors, and there are random errors with the sx1506 and the pcb micro.  We know the Adafruit's LCD which is using the I2C backback is a heavy user of the I2C. When it is writting to the LCD, it looks like there are about 2000 messages per second.( we put an I2C analyzer on the bus ).  \r\n\r\nWe are wondering if the python drivers (SMBUS ) for the I2C bus has a timing problem and if so is there a baudrate value that would minimize or eliminate the errors?  Or should we be using a different driver? \r\n"}}