On 16 June 2014 09:29, Lee Hambley <[email protected]> wrote: > Thanks Will, confirms what I thought I'd understood from reading, apparently > i2c is a trademark and most people refer to it as TWI (Two Wire Interface).
I've never heard it called that before :) > When speaking about faster, I don't know that it really matters, does it? > I'll be controlling a shift register for colour coding some RGB LEDs, and > reading from an accelerometer... I don't expect that to need much bandwidth, > really! It really just depends on what your hardware does, and what bandwidth you need. >> (sparks, electric motors etc.) then you might get interference on the >> SPI/I2C bus, program and design your hardware accordingly. > > Thanks mate, good to know > , does that more or less boil down to "don't put noisy components next to > data busses"? How do the problems manifest, mangled bits, protocol errors > and nonsense values, or does it fail to work under some circumstances? Yep, and get your ground planes right, shielding, and use filter capacitors: http://en.wikipedia.org/wiki/Filter_capacitor Will -- You received this message because you are subscribed to the Google Groups "NWRUG" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/nwrug-members. For more options, visit https://groups.google.com/d/optout.
