Timeline for Slow i2cdetect command response after running a program using the pigpio library
Current License: CC BY-SA 4.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 14, 2019 at 7:03 | history | bumped | CommunityBot | This question has answers that may be good or bad; the system has marked it active so that they can be reviewed. | |
| Feb 9, 2019 at 20:02 | history | bumped | CommunityBot | This question has answers that may be good or bad; the system has marked it active so that they can be reviewed. | |
| Jun 23, 2018 at 15:27 | answer | added | joan | timeline score: 1 | |
| Jun 23, 2018 at 15:15 | history | edited | joan | CC BY-SA 4.0 |
formatting
|
| Jun 23, 2018 at 15:09 | history | edited | Farad'n | CC BY-SA 4.0 |
added 1802 characters in body
|
| Jun 23, 2018 at 15:06 | comment | added | Farad'n | Correction:My error. This occured after running a gpio blink LEDs sequentially program using gpioRead() and gpioWrite() not i2cReadByte() and i2cWriteByte(). | |
| Jun 23, 2018 at 13:29 | comment | added | joan | Could you edit the question and include the pigpio program? | |
| Jun 23, 2018 at 12:51 | history | asked | Farad'n | CC BY-SA 4.0 |