I2C vs SPI

[@hugodavid2244]

En conclusión, SPI es más rápido que I2C, pero SPI necesita más pines (y si quieres conectar más Slaves en modo SPI, necesitarás un pin exclusivo para cada uno, lo que es una desventaja). I2C solo necesita 2 pines (el reloj y el de datos), y con esos dos pines puedes conectar todos los Salves que quieras sin la necesidad de más pines. Usos recomendados: -I2C: recomendado para la recolección de datos de muchos sensores a la vez. -SPI: recomendado para manejar grandes cantidades de datos en el menor tiempo posible (como el SD reader, pantallas led, displays, etc), pero la cantidad de Slaves debe de ser baja.

[@ArjanvanVught]

I2C has a limitation for the clock speed : 400 KHz. Where SPI can go in 10’s MHz. Also it is important how the OLED library is optimized for updating the display. Both applies for Arduino and Raspberry Pi. Where the Raspberry Pi might support higher SPI clock speed then the Arduino does.

[@jumblework]

Thanks for your complementing commentary. I just made this video from a simple question and test, "which bus is more suitable for my Arduino project ?". Usually Arduino works on tiny 16MHz clock or less. So in such situation, it's might be tough to get satisfing performance with multi tasked Arduino, even if the library will be more optimized. Sometimes, Arduino stumbles just by 115.2kpbs serial communication, if there are other task on programming.

[@dekus80]

This OLED does not have 400kHz limitation. In my project with STM32 (costs same price as avr :) ) and 1.3 OLED with software i2c (I had to use pins wo hw i2c) full screen (128x64) update speed is 12ms. You can calculate that it's much more than 400kHz. And it is 83Hz fps. P.s. I don't use any third party libraries. P.P.S.And it's fun to watch which slideshow on the screen faster :).

[@dekus80]

Arjan van Vught AVR has 8MHz SPI. With hw 4MHz SPI and sw d/c line on 128x64 LCD I had 120fps. I can't belive how it could be turned into such a slideshow. :)))). Arduino :))l

[@kcassoen]

damn background musics jazzy

[@jumblework]

Thank you.

[@seanocansey2956]

The big difference between SPI and I2C is that SPI is *able* to be ran at much higher speeds. With a 16MHz arduino or an even faster microcontroller, you really begin to see a difference.

[@jumblework]

Thank you for comment and information :-)

[@user-75333]

ロシアからのご挨拶、 そしてビデオをありがとう！

[@jumblework]

Спасибо за ваш комментарий

[@NikolayAgopyan]

Amazingly useful information, thank you!

[@jumblework]

I appreciate your comment and evaluation !

[@AnimilesYT]

As far as I know: SPI is faster, but requires a slave selection line for each slave, which might not be practical when there are a lot of things to connect to. I2C is slower, but you don't need as many wires. Just a single two-wire bus going to all devices is good enough. If, for instance, you want 20 of those screens for a project, then SPI would be a challenge since most microcontrollers don't offer that many pins. So you'd have to use something else to expand the amount of slave selection pins. I2C should work perfectly fine.

[@jumblework]

Thankful and appreciate for your comment!

[@Dancopymus]

For I2C or SPI, is the Arduino code the same? Thanks

[@toto99303]

awesome testing! thank you!

[@inibapakbudi]

Thanks for share this valuable information to us.

[@jumblework]

Thank you for comment.

[@fiveseven808]

this video is awesome!!!!! i can't believe there aren't more likes on it! thank you very much for this comparison! i need to know if there's anything I can do to improve i2c speed on my OLED display using a raspberry pi. I think I will try an SPI display now!

[@jumblework]

Thank you for your comment. I had been struggled for I2C, because its response is slow. I noticed that SPI has higher baud rate. So I got it and checked it out. Now, I use this display in my own follow focus project. Also, watch my arduino project. If you like. kzbin.info/aero/PLsEOJw3kP-w33jLU8DBLKqJhKVCbry85f

[@mohammedal-alaw6249]

Awsome work in my opinion!! :)

[@lexander9686]

It sure is ابو ابراهيم

[@TINTIN-fg7wv]

Excellent comparison... Thanks for sharing

[@jumblework]

Thank you. I will be glad if it helps you.

[@RTOHIO]

Have you done anything comparable with ESP32? I'm trying to convert, but not having much luck with displays

[@mellee3436]

The scl and SDA are not 4 and 5. If that's what your issue is. Ive had the small oleds working using the Adafruit ssd1306 library and esp32. I'm no genius by the way.

[@tommymagic869]

Good work mate!

[@jumblework]

Thanks!

[@Nikita_Pro89]

good job, thanks!)))

[@МаксимВолодимирович-с2х]

Good work! Thank You!

[@jumblework]

you're welcome!

[@mckryall]

I believe you're using I2C in slow mode. I'm not sure if fast I2C is as fast as SPI, but I believe I've used that driver chip (128x64, SSD1306?)

[@jumblework]

Thank you for a comment. Truly, I2C has "fast mode" and it can be used on u8glib, I think. But don't watch this with strict eyes, please. This video was made from a simple question that which bus is more proper for Arduino. And as my conclusion, there are no big differences on its spec, as long as I use "Arduino".

[@danielaesmaili2391]

nice set of test

[@jumblework]

appreciate for your evaluation.

[@agaldoo]

Use the esp32. It has 240 mhz clock

[@BenM0]

awesome!! thanks for sharing

[@jumblework]

Thanks for a comment. I'm glad if this video would be useful.

[@TheEtbetween]

Wow thanks always wonder what advantages was, I guess SPI is faster

[@jumblework]

Thanks. But these are just simple test. Actual speed will depend on your items, settings, library, I think.

[@nikilragav]

Try setting your i2c data rate to 1Mbps

[@jacobdavis000]

Another music video from India.

[@mohammedal-alaw6249]

unfortunatlly for the anti-allising affect of your filmming camera showed if you want to reduce it you can use an action camera and it would In Shaa ALLAH Disappear

[@jumblework]

Thanks you for comment. You may avoid from it by changing resolution of player setting. Or it maybe an un-ideal "bokeh" which is caused by lack of my focusing technique. Although, I don't want to use small sensor camera as much as possible, sorry.

[@MrSasha3050]

Прикольно

[@jumblework]

Спасибо

[@billleonard2015]

Too much reading. Text in the middle of the screen, text in the subtitle. Distracting electronic organ.

[@forgeteverythingyouknow5413]

Too much negativity, only seeing or making up problems... bothering everyone else with your own shite. that's how you write. That's how you come across. Impersonal, unfriendly, negative, and all the while thinking this is good. No. Your reply sucks as much as how badly you see mine back to you. This guy did great work. He's a person. He's not your bitch. You don't get to just hammer someone and walk away as though you did a good thing. You didn't.