Most common applications still use this speed, as it is quite sufficient for transferring data from sensors and to simple displays. The original I2C bus had a maximum speed of 100 KHz. The maximum distance of reliable transmission decreases as the speed increases, at the slowest speed (100 Kbaud or a clock rate of 100 KHz) the maximum distance is about a metre. I2C can only be used over short distances, after all, it was originally meant to communicate between integrated circuits on the same printed circuit board. It is not particularly fast, although for most of its intended uses it is plenty fast enough. I2C does have several limitations however. Many displays and sensors interface to their host controller using I2C. I2C is used with microcontrollers like the Arduino and with microcomputers like the Raspberry Pi. It is also called “IIC” or ‘I squared C”. I2C is an abbreviation for “Inter-Integrated Circuit”. Times have changed, Phillips is now NXP and I2C has become a communication standard that is supported by virtually every major semiconductor manufacturer. It was originally developed by Phillips in 1982 to allow integrated circuits within television receivers to communicate with one another. I2C is a serial protocol used on a low-speed 2-wire interface. In future articles we will see how we can build our own I2C devices, how to interface a Raspberry Pi and an Arduino using I2C and how to do some advanced I2C configurations, including using multiple masters on one I2C bus. This will be the first of four articles on I2C. We’ll also see how it can be used to exchange information between two Arduinos and how it can be used to allows one Arduino to control another one. Today we will correct that and learn more about I2C.

Although we have used many I2C sensors and displays in previous articles we have not actually looked into how I2C works and how it can be used to communicate between microcontrollers.

Looking up wire library