I've always thought that it is hard to understand how SPI works, after watching this video it is clear to me that things can be understood much more easier if they are explained in a fun way, just like this guy did, thank you!
Final project for my final class for college before getting my degree is building a temperature sensor system with an Xmega board, a UART LCD display screen and a TWI compatible temp sensor. It is a two week project and i am starting it 2 days before last day of term. I got a job lined up pending graduation. Wish my luck, brethren. Hopefully next week i'll be an engineer.
I think he need to give more detail on the protocol. This is an amazing explanation on I2c, specially on the roll of the the pullup resistors. In many tutorial I have seen nobody explain it, may be because they do not know it. Excellent tutorial!
Thank you for this - I'm trying to get my head around I2C for an enhancement to an existing project (sending data to a PIC) and I have no idea where to start! This is an excellent introduction - thank you.
Thank you for this video. You explained it well. You are a great teacher. I am eagerly waiting for more videos regarding this topic. Wish you all the best.
Loved the South Park pun on Mr.Slave. The word “mister” was originally a different pronunciation of the word “master”. So Mr.Slave actually means “Master Slave” :-)
Hi, this video is very good! But maybe there is some thing missed in the data example. After the slave address is put on the bus by master, then the register address in the i2c slave device should be put on i2c bus, then the data should be put on the i2c bus by slave or master depending on read or write operation. What I mean is the register address in the i2c slave address is missed in your example.
Hnm, i dont agree with the uncommonness of repeated start conditions, almost every register based i2c device uses it to not loose the bus between the initial write (what register do i want to address) and the next read for the data.
In general, I2C communication is the mutual communication between ICs and ICs on the board. If there is IC and IC communication between boards, what are the advantages and disadvantages? How stable is the communication?
Your vidieo is so good for me! Thank you! Plz talk more about the timing. Star edge timing, ack timing, stop tim.... And reading frame. I have use i2c to make my project recently but there a problem, that 2 slave is not synchronous about timing or whatever idk how to say the detail. Both of them has 400kB bandwidth, but master cant talk with them on a same bus. I have to create new i2c IO in software and it seem to be waisted i2c's ability.
how i2c handles "no true scottsman" problem with multiple masters, would probably make a good video. Its such a common logical problem that applies to everything from philosophy to multi-threading to hardware. I like that most of your videos are focus on the applied tech, in the weeds at 4am, how do i do this. giving an overview and getting down into the design choices and compromises that i2c makes to do multiple masters, I think would make a good vid. mr. slave agrees.
Great videos, i have a doubt though. After pulling SDA low for ACK why does the line go through a clock pulse before sending the next data? Is it part of the I2C structure?
If I have a DHT22 connected to an esp8266, for example, how long of a cable can I use before the data becomes goofy? 22 gauge wires 5 mm apart from each other is about 0.1pF/cm, so 10 cm of wire would have 1pF of capacitance on the cable.
ADC is used to transfer some kind of analog signal, such as analog voltage, to digital format, then this kind of digital data can be transfered via I2C to micro comtroller. So that your code can recogonize it.
In general, I2C communication is the mutual communication between ICs and ICs on the board. If there is IC and IC communication between boards, what are the advantages and disadvantages? How stable is the communication?
Between boards have similar advantages and disadvantages. The comms should be OK unless there's a significant distance or lots of noise on the line. However it won't be as good as a differential signal interface.
Interesting. I'm looking to put a BMP280, GPS and accellerometer on a Pi Pico. I2C looks the most promising way of doing it. I just have to figure out how.
Hi Dejan, This is a great explanation of the concept of connecting I2C items on the same board. I am very new to doing anything at all with electronics but my current project uses the MPU6050 module and I want to add a distance measuring module into the project too + powering some servos with the PCA9685 that also uses the I2C protocol. I have the MPU6050 actuating 4 x servos at the moment on an Arduino Uno with regular breadboard and external power supply. The code seems to stop working after a few minutes and I am struggling to find a fault that would cause this. QUESTION: You show an Arduino Mega in your wiring diagram... is that because you anticipate the code will be a bit heavy for the Uno? I am wondering if limited Uno memory is the issue I have with the MPU6050 at the moment - and if I should consider using a Mega for this module as i want to add other I2C items..?
For something like this application, uno would be fine. Mega is really used for things like IO needs. Maybe if you need a bunch of analog or digital pins, mega is good to use. Hope you got to explore electronics more!
I think we just addressed a slave here but not a register within a slave. I mean a slave can have multiple registers that you may want to write/read to.
is it possible that two slaves can pull the bus low . i understand the Device address will target a particular device but inadvertently is it possible more than one slave can pull the bus low
Sir, I need CAN from you.. I have subscribed your channel with notification... Please..please Do a video on CAN..with same manner as you used in this video... #ApriciateYourWork.. #GreatVideo..
great video, but would love it if you shifted away from master/slave terminology, main/secondary has the same initials and understanding without using insensitive language
this is the i2c gold standard on youtube. thanks!
absolutely. Thanks a lot
I've always thought that it is hard to understand how SPI works, after watching this video it is clear to me that things can be understood much more easier if they are explained in a fun way, just like this guy did, thank you!
This comment should've been posted under another video of yours, but still thank you
Great video, and great southpark reference at 12:19
Final project for my final class for college before getting my degree is building a temperature sensor system with an Xmega board, a UART LCD display screen and a TWI compatible temp sensor. It is a two week project and i am starting it 2 days before last day of term. I got a job lined up pending graduation. Wish my luck, brethren. Hopefully next week i'll be an engineer.
how did it go?
Best explanation of I2C I have seen yet . . . thanks for sharing!
Such a great teacher that explains everything very clearly! Thanks for the vids
You do a great job explaining this concept on I2C. Thanks a million
Nothing like a South Park reference in a video about I2C lol
I think he need to give more detail on the protocol. This is an amazing explanation on I2c, specially on the roll of the the pullup resistors. In many tutorial I have seen nobody explain it, may be because they do not know it. Excellent tutorial!
If it's possible, can you do a video about can bus ?
Best explanation of pull up resistor I've seen...
Great video on this topic! The best I have seen so far.
Very clear and articulate. Thanks for the crash course. +1 for South Park reference
Been trying to get a handle on this for a few days...This did it clearly. Thank you!
Who else is ADDICTED to NANDLAND??
best i2c explanation on youtube, you are a beast, thank you :D
Thank you for this - I'm trying to get my head around I2C for an enhancement to an existing project (sending data to a PIC) and I have no idea where to start!
This is an excellent introduction - thank you.
I like the way that you use to explain
Thank you for this video. You explained it well. You are a great teacher. I am eagerly waiting for more videos regarding this topic. Wish you all the best.
You are very clear to the point. Thank you for the good explanation.
Explained in a very clear way thanks from italy
Nice information, love from India.
Thank you. You do a great job simplifying a complicated concept.
This helped me in my project in electronics
I'm watching this literally the morning before an important exam to get some last minute details haha
Loved the South Park pun on Mr.Slave. The word “mister” was originally a different pronunciation of the word “master”. So Mr.Slave actually means “Master Slave” :-)
Great video! Would you also consider making a tutorial on the CAN bus? (As other commentators have pointed out!)
Your explanation is very clear,thank you!
Excellent presentation ❤❤
Wonderful !!! clearly explained om understandable way.
Nice introduction to the video 😊. Grabbed my attention.
incredible video - very concise and helpful. thanks!
08:00 hahaah I know this feeling so well! :D wonderful video!
"Mr. Slave" 🤣🤣
I could tell you were holding back the chuckles for that South Park reference lol
Thank you! Great explanation
Great explanation, please do one about I3C. Thanks!
thank you very much! an awesome vid and awesome explanation =)
Golden! Great video!
12:19 Mr Slave!! South Park reference
Hi, this video is very good! But maybe there is some thing missed in the data example. After the slave address is put on the bus by master, then the register address in the i2c slave device should be put on i2c bus, then the data should be put on the i2c bus by slave or master depending on read or write operation.
What I mean is the register address in the i2c slave address is missed in your example.
Hnm, i dont agree with the uncommonness of repeated start conditions, almost every register based i2c device uses it to not loose the bus between the initial write (what register do i want to address) and the next read for the data.
Thanks for pointing that out!
In general, I2C communication is the mutual communication between ICs and ICs on the board. If there is IC and IC communication between boards, what are the advantages and disadvantages? How stable is the communication?
so useful and clear
do you know how to make a Verilog HDL with using LCD 16x2 I2C to show monitoring voltages and current?
Good teacher.
5:38 Good reference to Taxi Driver!
Thank you so much , please do a video about CAN bus
Thank you ,very interesting explanation
Your vidieo is so good for me! Thank you!
Plz talk more about the timing.
Star edge timing, ack timing, stop tim.... And reading frame.
I have use i2c to make my project recently but there a problem, that 2 slave is not synchronous about timing or whatever idk how to say the detail.
Both of them has 400kB bandwidth, but master cant talk with them on a same bus. I have to create new i2c IO in software and it seem to be waisted i2c's ability.
Great explanation :)
thanks, well presented
how i2c handles "no true scottsman" problem with multiple masters, would probably make a good video.
Its such a common logical problem that applies to everything from philosophy to multi-threading to hardware.
I like that most of your videos are focus on the applied tech, in the weeds at 4am, how do i do this.
giving an overview and getting down into the design choices and compromises that i2c makes to do multiple masters, I think would make a good vid.
mr. slave agrees.
damn you just saved me from a paaaaaainful exam tomorrowww
When I'm thinking "oh man, I've definitely seen this guy somewhere." then Doug DeMuro posts new video.
Oh
THIIIIIISSSSSS is the new XILINX ULTRASCALE FPGA.... :)
Great video, thanks!
nice explanation . helpful
Thank you so much sir!
Great video!
Distance. I did not hear you discuss how far this bus can be transmitted?
Could a microcontroller i2c slave write to i2c eeprom? For example the attiny441 lists only an i2c slave interface.
You explain this so easy and clear. Thank you ! And you are very handsome!
Great videos, i have a doubt though. After pulling SDA low for ACK why does the line go through a clock pulse before sending the next data? Is it part of the I2C structure?
So would the 7 address bits + the R/W bit be considered the "header?" is that the correct term?
So an 8-bit header, and 8-bit data section?
If I have a DHT22 connected to an esp8266, for example, how long of a cable can I use before the data becomes goofy? 22 gauge wires 5 mm apart from each other is about 0.1pF/cm, so 10 cm of wire would have 1pF of capacitance on the cable.
So with a Maximum of 400 Kilo-Bits per second, does that specification require a clock with a maximum frequency of 400,000 Hz or .4 MHz?
How often are pull-up resistors actually used, though? And why not set your master pins to be open-drain with a pullup as an alternative?
The pull-up resistors are required. They're always used. You need something to pull the CLK and DATA lines up to 3.3V.
Hi I understood the way u explianed thank u. I have one question is there any chance I2C work for 5Mbps
who sends the acknowledge bit when master reads the data?
10:40 the data are valid when the clock is transitioning HIGH, not low
hello, in 2:20, we use ADC to digitalizing the data for the µC but the I²C use digital data, so why we need to digitalizing.
ADC is used to transfer some kind of analog signal, such as analog voltage, to digital format, then this kind of digital data can be transfered via I2C to micro comtroller. So that your code can recogonize it.
@@futurelu623 thank you.
thank you very much
In general, I2C communication is the mutual communication between ICs and ICs on the board. If there is IC and IC communication between boards, what are the advantages and disadvantages? How stable is the communication?
Between boards have similar advantages and disadvantages. The comms should be OK unless there's a significant distance or lots of noise on the line. However it won't be as good as a differential signal interface.
Interesting. I'm looking to put a BMP280, GPS and accellerometer on a Pi Pico. I2C looks the most promising way of doing it. I just have to figure out how.
Hi Dejan, This is a great explanation of the concept of connecting I2C items on the same board. I am very new to doing anything at all with electronics but my current project uses the MPU6050 module and I want to add a distance measuring module into the project too + powering some servos with the PCA9685 that also uses the I2C protocol.
I have the MPU6050 actuating 4 x servos at the moment on an Arduino Uno with regular breadboard and external power supply. The code seems to stop working after a few minutes and I am struggling to find a fault that would cause this.
QUESTION:
You show an Arduino Mega in your wiring diagram... is that because you anticipate the code will be a bit heavy for the Uno?
I am wondering if limited Uno memory is the issue I have with the MPU6050 at the moment - and if I should consider using a Mega for this module as i want to add other I2C items..?
For something like this application, uno would be fine. Mega is really used for things like IO needs. Maybe if you need a bunch of analog or digital pins, mega is good to use. Hope you got to explore electronics more!
I think we just addressed a slave here but not a register within a slave. I mean a slave can have multiple registers that you may want to write/read to.
Where is the next video on implementation?
Спасибо)
Thanks for assuring me that my 3v3 device will not blow up if connected to 5V IO (pull up to 3v3).
Good video but it seems you forgot register address in your diagram.
names of 2 pins????
you explain very well despite my ver bad understanding on basic electric circuitrey. Do you happen to have any videos on that? c:
exit full screen ... hit like and subscribe and then return back to the explanation ♥
could you write the code step by step?
keep it up pls
when both lines are low then it is a read/write condition!
is it possible that two slaves can pull the bus low . i understand the Device address will target a particular device but inadvertently is it possible more than one slave can pull the bus low
I remember making this in Minecraft once
*cough, my drunk ass though he was Toby Maguire for a split second. Just share it.
No, you are not mirrored.
You are welcome.
Sir,
I need CAN from you..
I have subscribed your channel with notification...
Please..please Do a video on CAN..with same manner as you used in this video...
#ApriciateYourWork..
#GreatVideo..
At one point I have stuck at your video that "where is register address?"...
Please clear my doubt..
The only thing that would make this video better is to speak in Mr Garrison's voice for the second half. lol
i love you
you defined half duplex wrong. half duplex is the fact that data transmission happens in one directed at a time per carrier
Nice one also check the playlists: ruclips.net/p/PLyp1I7W35-q1su6Nvbvd09mEgT-CWz0MD
Mr slave and sir Master
Mr.Slave :)
you are a fucking god
hahaha Mr Slave "jesus christ"
great video, but would love it if you shifted away from master/slave terminology, main/secondary has the same initials and understanding without using insensitive language
Ist comment
Damn it! I'm late again!
Mr. slave🤭😅😅😅😅😅
Bro please dont give example as slave