IC2ing
Ic2
find the addresses connected to IC2 via this "scanner" script
//Written by Nick Gammon
// Date: 20th April 2011
#include <Wire.h>
void setup() {
Serial.begin (115200);
// Leonardo: wait for serial port to connect
while (!Serial) { }
Serial.println ();
Serial.println ("I2C scanner. Scanning ...");
byte count = 0;
Wire.begin();
for (byte i = 1; i < 120; i++) {
Wire.beginTransmission (i);
if (Wire.endTransmission () == 0)
{
Serial.print ("Found address: ");
Serial.print (i, DEC);
Serial.print (" (0x");
Serial.print (i, HEX);
Serial.println (")");
count++;
delay (1); // maybe unneeded?
} // end of good response
} // end of for loop
Serial.println ("Done.");
Serial.print ("Found ");
Serial.print (count, DEC);
Serial.println (" device(s).");
} // end of setup
void loop() {}
==============================
==============================================================================================
in order of complexity:
CAN = complex
I2C = moderately complex
SPI = so simple I can understand it
UART
For I2C I can tell you that it's a one-to-many connection with in-band addressing in the messages.
For SPI it's a one-to-one connection with only one slave ever being selected at a time (unless the master is transmit only).
For CAN you'll have to wait for "Mike B" to turn up
but if you want a bit of "light reading" just search out all his previous posts
and you will get some idea why there only seems to be one person on this entire message system
that understands CAN enough to be able to explain it to others!
BTW almost all AVRs can do SPI and I2C (sometimes on Tiny's this involves using a thing called USI though)
but only a few specialist AVRs have CAN built in
(as you probably know it's mainly an automotive protocol -
it's what most modern cars use inside to wire all the functions together)
----------------------------------------------------------------------------------------------
Serial is an umbrella word for all that is "Time Division Multiplexed", to use an expensive term.
It means that the data is sent spread over time, most often one single bit after another.
All the protocols you're naming are serial protocols.
UART, for Universal Asynchronous Receiver Transmitter, is one of the most used serial protocols.
It's almost as old as I am, and very simple.
Most controllers have a hardware UART on board.
It uses a single data line for transmitting and one for receiving data.
Most often 8-bit data is transferred, as follows: 1 start bit(low level), 8 data bits and 1 stop bit(high level).
The low level start bit and high level stop bit mean that there's always a high to low transition to start the communication.
That's what describes UART. No voltage level, so you can have it at 3.3 V or 5 V, whichever your microcontroller uses.
Note that the microcontrollers which want to communicate via UART have to agree on the transmission speed, the bit-rate,
as they only have the start bit's falling edge to synchronize. That's called asynchronous communication.
For long distance communication (That doesn't have to be hundreds of meters)
the 5 V UART is not very reliable, that's why it's converted to a higher voltage,
typically +12 V for a "0" and -12 V for a "1". The data format remains the same.
Then you have RS-232 (which you actually should call EIA-232, but nobody does.)
The timing dependency is one of the big drawbacks of UART,
and the solution is USART, for Universal Synchronous/Asynchronous Receiver Transmitter.
This can do UART, but also a synchronous protocol.
In synchronous there's not only data, but also a clock transmitted.
With each bit a clock pulse tells the receiver it should latch that bit.
Synchronous protocols either need a higher bandwidth, like in the case of Manchester encoding,
or an extra wire for the clock, like SPI and I2C.
SPI (Serial Peripheral Interface) is another very simple serial protocol.
A master sends a clock signal, and upon each clock pulse it shifts
one bit out to the slave, and
one bit in, coming from the slave.
Signal names are therefore SCK for clock, MOSI for Master Out Slave In, and MISO for Master In Slave Out.
By using SS (Slave Select) signals the master can control more than 1 slave on the bus.
There are two ways to connect multiple slave devices to one master, one is mentioned above i.e. using slave select,
and other is daisy chaining, it uses less hardware pins(select lines), but software gets complicated.
I2C (Inter-Integrated Circuit, pronounced "I squared C") is also a synchronous protocol,
and it's the first we see which has some "intelligence" in it;
the other ones dumbly shifted bits in and out, and that was that.
I2C uses only 2 wires, one for the clock (SCL) and one for the data (SDA).
That means that master and slave send data over the same wire, again controlled by the master who creates the clock signal.
I2C doesn't use separate Slave Selects to select a particular device, but has addressing.
The first byte sent by the master holds a 7 bit address (so that you can use 127 devices on the bus) and a read/write bit,
indicating whether the next byte(s) will also come from the master of should come from the slave.
After each byte receiver must send a "0" to acknowledge the reception of the byte,
which the master latches with a 9th clock pulse. If the master wants to write a byte the same process repeats:
the master puts bit after bit on the bus and each time gives a clock pulse to signal that the data is ready to be read.
If the master wants to receive data it only generates the clock pulses. The slave has to take care that
the next bit is ready when the clock pulse is given. This protocol is patented by NXP(formerly Phillips),
to save licensing cost, Atmel using the word TWI(2-wire interface)
which exactly same as I2C, so any AVR device will not have I2C but it will have TWI.
Two or more signals on the same wire may cause conflicts, and you would have a problem if one device sends a "1" while the other sends a "0".
Therefore the bus is wired-OR'd: two resistors pull the bus to a high level, and the devices only send low levels.
If they want to send a high level they simply release the bus.
TTL (Transistor Transistor Logic) is not a protocol. It's an older technology for digital logic,
but the name is often used to refer to the 5 V supply voltage,
often incorrectly referring to what should be called UART.
==============================================================================================
find the addresses connected to IC2 via this "scanner" script
//Written by Nick Gammon
// Date: 20th April 2011
#include <Wire.h>
void setup() {
Serial.begin (115200);
// Leonardo: wait for serial port to connect
while (!Serial) { }
Serial.println ();
Serial.println ("I2C scanner. Scanning ...");
byte count = 0;
Wire.begin();
for (byte i = 1; i < 120; i++) {
Wire.beginTransmission (i);
if (Wire.endTransmission () == 0)
{
Serial.print ("Found address: ");
Serial.print (i, DEC);
Serial.print (" (0x");
Serial.print (i, HEX);
Serial.println (")");
count++;
delay (1); // maybe unneeded?
} // end of good response
} // end of for loop
Serial.println ("Done.");
Serial.print ("Found ");
Serial.print (count, DEC);
Serial.println (" device(s).");
} // end of setup
void loop() {}
==============================
==============================================================================================
in order of complexity:
CAN = complex
I2C = moderately complex
SPI = so simple I can understand it
UART
For I2C I can tell you that it's a one-to-many connection with in-band addressing in the messages.
For SPI it's a one-to-one connection with only one slave ever being selected at a time (unless the master is transmit only).
For CAN you'll have to wait for "Mike B" to turn up
but if you want a bit of "light reading" just search out all his previous posts
and you will get some idea why there only seems to be one person on this entire message system
that understands CAN enough to be able to explain it to others!
BTW almost all AVRs can do SPI and I2C (sometimes on Tiny's this involves using a thing called USI though)
but only a few specialist AVRs have CAN built in
(as you probably know it's mainly an automotive protocol -
it's what most modern cars use inside to wire all the functions together)
----------------------------------------------------------------------------------------------
Serial is an umbrella word for all that is "Time Division Multiplexed", to use an expensive term.
It means that the data is sent spread over time, most often one single bit after another.
All the protocols you're naming are serial protocols.
UART, for Universal Asynchronous Receiver Transmitter, is one of the most used serial protocols.
It's almost as old as I am, and very simple.
Most controllers have a hardware UART on board.
It uses a single data line for transmitting and one for receiving data.
Most often 8-bit data is transferred, as follows: 1 start bit(low level), 8 data bits and 1 stop bit(high level).
The low level start bit and high level stop bit mean that there's always a high to low transition to start the communication.
That's what describes UART. No voltage level, so you can have it at 3.3 V or 5 V, whichever your microcontroller uses.
Note that the microcontrollers which want to communicate via UART have to agree on the transmission speed, the bit-rate,
as they only have the start bit's falling edge to synchronize. That's called asynchronous communication.
For long distance communication (That doesn't have to be hundreds of meters)
the 5 V UART is not very reliable, that's why it's converted to a higher voltage,
typically +12 V for a "0" and -12 V for a "1". The data format remains the same.
Then you have RS-232 (which you actually should call EIA-232, but nobody does.)
The timing dependency is one of the big drawbacks of UART,
and the solution is USART, for Universal Synchronous/Asynchronous Receiver Transmitter.
This can do UART, but also a synchronous protocol.
In synchronous there's not only data, but also a clock transmitted.
With each bit a clock pulse tells the receiver it should latch that bit.
Synchronous protocols either need a higher bandwidth, like in the case of Manchester encoding,
or an extra wire for the clock, like SPI and I2C.
SPI (Serial Peripheral Interface) is another very simple serial protocol.
A master sends a clock signal, and upon each clock pulse it shifts
one bit out to the slave, and
one bit in, coming from the slave.
Signal names are therefore SCK for clock, MOSI for Master Out Slave In, and MISO for Master In Slave Out.
By using SS (Slave Select) signals the master can control more than 1 slave on the bus.
There are two ways to connect multiple slave devices to one master, one is mentioned above i.e. using slave select,
and other is daisy chaining, it uses less hardware pins(select lines), but software gets complicated.
I2C (Inter-Integrated Circuit, pronounced "I squared C") is also a synchronous protocol,
and it's the first we see which has some "intelligence" in it;
the other ones dumbly shifted bits in and out, and that was that.
I2C uses only 2 wires, one for the clock (SCL) and one for the data (SDA).
That means that master and slave send data over the same wire, again controlled by the master who creates the clock signal.
I2C doesn't use separate Slave Selects to select a particular device, but has addressing.
The first byte sent by the master holds a 7 bit address (so that you can use 127 devices on the bus) and a read/write bit,
indicating whether the next byte(s) will also come from the master of should come from the slave.
After each byte receiver must send a "0" to acknowledge the reception of the byte,
which the master latches with a 9th clock pulse. If the master wants to write a byte the same process repeats:
the master puts bit after bit on the bus and each time gives a clock pulse to signal that the data is ready to be read.
If the master wants to receive data it only generates the clock pulses. The slave has to take care that
the next bit is ready when the clock pulse is given. This protocol is patented by NXP(formerly Phillips),
to save licensing cost, Atmel using the word TWI(2-wire interface)
which exactly same as I2C, so any AVR device will not have I2C but it will have TWI.
Two or more signals on the same wire may cause conflicts, and you would have a problem if one device sends a "1" while the other sends a "0".
Therefore the bus is wired-OR'd: two resistors pull the bus to a high level, and the devices only send low levels.
If they want to send a high level they simply release the bus.
TTL (Transistor Transistor Logic) is not a protocol. It's an older technology for digital logic,
but the name is often used to refer to the 5 V supply voltage,
often incorrectly referring to what should be called UART.
==============================================================================================
Comments
Post a Comment