| ??? 03/20/07 12:56 Read: times |
#135382 - IIC "in the box" Responding to: ???'s previous message |
I have done that in many cases and never had a problem. I have always include parity in the messages and, as far as I know that has, so far, been not necessary. I will, however continye to do so. The IIC 'built ib' ACK/NAK gives a verty simeple response mechanism to parity error.
One word to the wise; DO use uc with HW IIC, In the days before HW IIC the overhead of a bitbanger did force me to abandon IIC comms in a case where otherwise all was just fine till the last detail of the project was implemented. Erik Per, hvis du behoever mere, en snabel 'a' til mig Erik |
| Topic | Author | Date |
| off board i2c | 01/01/70 00:00 | |
| what are the circumstances? | 01/01/70 00:00 | |
| circumstances | 01/01/70 00:00 | |
| Haven't NXP... | 01/01/70 00:00 | |
| NXP Buffer dirvers | 01/01/70 00:00 | |
| NXP i2c buffers | 01/01/70 00:00 | |
| IIC "in the box" | 01/01/70 00:00 | |
| Long Distance I2C | 01/01/70 00:00 | |
| IIC and distance | 01/01/70 00:00 | |
| i2c | 01/01/70 00:00 | |
| Please inform us about your results! | 01/01/70 00:00 | |
Yes, of course! | 01/01/70 00:00 | |
| checksums | 01/01/70 00:00 | |
| if you can't checksum .. | 01/01/70 00:00 | |
| Long distance I2C | 01/01/70 00:00 |