Serial Peripheral Interface (SPI) vs Two-Wire Interface (TWI, I²C) wire length

Question

I'm using Arduino DUE to read data from an IMU(inertial measurement unit) sensor (MIKROE-1577, MPU-6000)

This IMU sensor supports both Serial Peripheral Interface (SPI) and Two-Wire Interface (TWI, I²C). According to the datasheet,

• 400kHz Fast Mode I2C for communicating with all registers
• 1MHz SPI serial interface for communicating with all registers (MPU-6000 only)
• 20MHz SPI serial interface for reading sensor and interrupt registers (MPU-6000 only)

Note that the Arduino DUE can set the SPI clock using setClockDivider() and I generated 1MHz, 4MHz, 8MHz clock frequency.

My situation; I have to make a long wire to place this IMU sensor on a table.

I prefer to use SPI because it is faster than TWI.

But if I set the SPI clock frequency to 4 MHz or 8 MHz, I noticed that the SPI signals become a sawtooth wave, not like a pulse wave, if the wire gets longer.

I really want to read the IMU data with an SPI clock of 8 MHz. How can I calculate the wires' length, which doesn't distort the waveform strongly, if I want to set the SPI clock frequency to 8 MHz?

Also, in contrast, if I choose the 400kHz Fast Mode I2C, how long can I extend the wires?

Answer 1

The limiting factor is the capacitance of the interconnecting wires. A pair of wires has a capacitance between them, measured in \$Fm^{-1}\$. Therefore, as your wire length goes up, the capacitance goes up. This means that, to a first approximation, you can think of the wire and the driver as an RC filter, so your nice square pulses no longer look like squares. You might be able to calculate the wire length, but there are a lot of variables, so a definite answer is unlikely. Some suggestions:

1. Think about using other protocols rather than SPI or I2C, which are designed for short distance PCB connections.
2. Use as low a frequency as possible for your application.
3. Use as high a drive as possible. There may be a "strength" register setting for the SPI driver, or for I2C use as low as possible value for the pull-up resistors.
4. Do some local processing where the IMU is, so you don't need the full data bandwidth back to the central controller.

Overall, a good engineering problem to be solved - lots of contradictory requirements, so spend a bit of time actually specifying your system, and then identify where you have problems. For example, do you need to read out at 8 MHz, or is 100 kHz enough?