After watching 6 videos, this one was clear, concise, wasn't 13 minutes long, didn't have awful hand-writing, and included everything I needed to know. Thanks!
Ahh, happy days of measuring one and a half start bits to work out the width of the clock/pulses to manually read the data from a remote UART. Life was such fun writing process control software in the 1980s :)
UART still lives in the hearts and motherboards of plotter devices like CNC machines and 3D printers i'm watching this video because i didn't understand how can i connect several motor drivers and a couple of probes via just three wires but it's all clear now
yeah rohde & schwarz rulezzz ;) pretty good explanation, with few precise questions left to be solved by myself, but i will figure that out soon! keep up the good work! thanks a lot
I have a question here: How do you know if it is a stop bit or a sequence of 1's as data. For example, if i need to send 0xffff, when will UART know that the data has ended?
It's usually automatic in "drivers" so you load in something and use a command like 'write "oxffff"' from instructions on the internet. The driver is something like 'Uart.h' or whatever. It's probably 300 lines in C or MicroPython and you need to write 5 lines very carefully to make it happen or you use some more advanced software doing most of it.
uart(universal asynchronous reciever transmitter) - parity(error detection) - asynchronous so both sender and reciever should transmit at same speeD(baud rate) - tx,rx are registers used in transmitting and recieving data
Nowadays UART often reaches 3 Mbps, i have even used 6 Mbps. Serious SOC have many UARTs peripherals. UART is trivial to handle on the software side. UART is ... GREAT.
The stop bit just looks like a normal "1" bit. How to distinguish a stop bit from a useful "1" bit, or a useful "1" bit from a stop bit? It is not explained in the video - I did not see the use of any prepositioned "length field" or "escape sequence". Can anyone help me with this?
@@maxint2680 Yes, that's correct: Normally in serial communications, you have to explicitly specify (i.e. configure) certain parameters, which need to match on both ends of the connection. These are the speed (baud rate - e.g. 9600), the number of data bits (7 or 8, usually), the number of stop bits (almost always 1), and the parity type (none, even, or odd). So if you know these values, you can derive the length of the frame. If you use PuTTY as a terminal program, these values can be found under "Connection -> Serial"
Depends on the type of parity - even versus odd. In even parity, the number of ones in the user bits + parity bit must be even, so if you send 1 1 1 1 and are using even parity, the parity bit would be zero. If you were using odd parity, the total number of ones would need to be odd, and 1 1 1 1 would require a one as the parity bit.
I have some confusions. 1. The LSB is indicated first in waveform but actually receiver is receiving the MSB first. 2. What kind of line coding techniques are used; it is told that NRZ-I is used but the waveforms just represent Unipolar NRZ. 3. How cannot the receiver misinterpret as the end of data if consecutive 1's is present in the data which is similar as stop bits?
1. The order of the bits (LSB or MSB) has to be agreed upon by the transmitter and receiver (and clearly must match at both ends) 2. NRZ is the most common type of line coding used 3. The transmitter and receiver must be configured to use the same baud rate, number of data bits, parity type, etc. From these two pieces of information, it is possible to derive the length of the frame (number of bits) and distinguish between a payload "1" and the stop bit.
How toes the reciever know that the stop bit is a stop bit and not a data bit? If it already has to know when the stop-bit is supposed to come, why would it even need it? I don't get it at all.
Can it be used for media(sound,image) transfer from (for e.g) a bluetooth module? What is the cost of implementing this interface in comparison with I^2C, CAN or MLBB?
My understanding is that a UART is included in most Bluetooth chips for the host-controller interface, with USB being another popular choice. Generally speaking, UART is often cheaper and easier to implement than other protocols but has lower data throughput. That said, the suitability and cost of using one protocol vs. another is a function of many things, so I couldn't really comment on that part of the question without knowing a lot more about the application, other components in the system, etc.
Typically the user data is 8 bits long. That said, UART doesn't specify how long the payload should be. I still remember when 7-bit ASCII was the norm in serial text transmission.
UART requires that both sides be configurated with the same bit rate and the number of data bits (this is fixed for all UART frames exchanged and cannot be "signaled"). So the receiver will know how long the frame is and thus can identify the stop bit.
7N1 means seven bits, no parity bit and one stop bit, whereas 8N1 means eight bits, no parity bit and one stop bit, so these settings are most likely incompatible. If one of the endpoints is a configurable terminal program (like Hyperterm, PuTTY, etc.) you should be able to configure these parameters.
After watching 6 videos, this one was clear, concise, wasn't 13 minutes long, didn't have awful hand-writing, and included everything I needed to know. Thanks!
Thanks!
Highly appreciate the efforts put in to explain everything in a concise manner. Thanks!!
Thanks!
One of the best explanation videos I have seen in a long time. A great help for my exams!
Thanks!
Ahh, happy days of measuring one and a half start bits to work out the width of the clock/pulses to manually read the data from a remote UART. Life was such fun writing process control software in the 1980s :)
When someone understands a thing he knows how to explain it clearly! Thank you :D
Thanks!
I found this video very useful. Thank you so much!!
Excellent video so very clearly explained. This is the best I have seen on this topic. Thank you for covering all the bases.
Small Correction S has value hex value as 0x53 and decimal value as 83.
Yep, that's a typo - bit pattern and diagram are correct. Thanks!
up
Short and comprehensive -- amazing video!
Thank you!
Excellent video. You clarified many doubts and I understood new concepts.
Extremely clear cut explanation!
The parity bit is more clear now. Thanks.
Thanks, parity concept explanation is really excellent.
UART still lives in the hearts and motherboards of plotter devices like CNC machines and 3D printers
i'm watching this video because i didn't understand how can i connect several motor drivers and a couple of probes via just three wires but it's all clear now
0% bull shit
0% advertisements
50% swag
50% spot on content
Thanks! Really appreciate the feedback!
Incredible explanation
yeah rohde & schwarz rulezzz ;) pretty good explanation, with few precise questions left to be solved by myself, but i will figure that out soon! keep up the good work! thanks a lot
Thanks for the feedback!
Thnku so much for such an easy explanation
This is a great introduction
I have a question here: How do you know if it is a stop bit or a sequence of 1's as data. For example, if i need to send 0xffff, when will UART know that the data has ended?
It's usually automatic in "drivers" so you load in something and use a command like 'write "oxffff"' from instructions on the internet. The driver is something like 'Uart.h' or whatever. It's probably 300 lines in C or MicroPython and you need to write 5 lines very carefully to make it happen or you use some more advanced software doing most of it.
Clear concise explanation! 😊
Thank you!
admirably explained sir enjoyed the video
😍
THANKS FOR GREAT EXPLANATION!
Neat and tidy explanation, tnx!
Thank you sir for a clear concept video. best wishes for you.
Great video, thanks for this!
Very well done. Thank you for this great explanation.
Thanks for the feedback!
uart(universal asynchronous reciever transmitter) - parity(error detection) - asynchronous so both sender and reciever should transmit at same speeD(baud rate) - tx,rx are registers used in transmitting and recieving data
Nowadays UART often reaches 3 Mbps, i have even used 6 Mbps. Serious SOC have many UARTs peripherals. UART is trivial to handle on the software side. UART is ... GREAT.
UART will always have a special place in my heart :)
Thank you!
The stop bit just looks like a normal "1" bit. How to distinguish a stop bit from a useful "1" bit, or a useful "1" bit from a stop bit? It is not explained in the video - I did not see the use of any prepositioned "length field" or "escape sequence". Can anyone help me with this?
After doing some searching, I believe the frame length is also pre-configured just like the baud rate. (Please let me know if I am wrong)
@@maxint2680 Yes, that's correct: Normally in serial communications, you have to explicitly specify (i.e. configure) certain parameters, which need to match on both ends of the connection. These are the speed (baud rate - e.g. 9600), the number of data bits (7 or 8, usually), the number of stop bits (almost always 1), and the parity type (none, even, or odd). So if you know these values, you can derive the length of the frame. If you use PuTTY as a terminal program, these values can be found under "Connection -> Serial"
@@pauldenisowski Detailed explanation. Thanks!
Excellent. To the point.
Teaching like a GOD.
No cap
thanks a lot! its very easy to understand
actually i have one doubt , inside the UART we have transmitter and receiver . will both transmitter and receiver will work at same clock frequency
In order to UART to work, but transmitter and receiver have to be configured to run at the same speed (asynchronous - no shared clock).
Thank you. Very good explained
Hii Nice explanation.Can u also add material on SM bus and JTAG
JTAG is on my longer-term list of topics, but probably won't get to it for a while.
Great explanation
i have not understand that parity bit.means if data bits are 4-1s then parity bit sould be low(0).
Depends on the type of parity - even versus odd. In even parity, the number of ones in the user bits + parity bit must be even, so if you send 1 1 1 1 and are using even parity, the parity bit would be zero. If you were using odd parity, the total number of ones would need to be odd, and 1 1 1 1 would require a one as the parity bit.
4:10 'S' is 0x53 in ascii, otherwise the video was flawless just as the other one ;)
so to go from & bit ASCII to LSB, you just have to reverse the order of the bit?
I have some confusions.
1. The LSB is indicated first in waveform but actually receiver is receiving the MSB first.
2. What kind of line coding techniques are used; it is told that NRZ-I is used but the waveforms just represent Unipolar NRZ.
3. How cannot the receiver misinterpret as the end of data if consecutive 1's is present in the data which is similar as stop bits?
1. The order of the bits (LSB or MSB) has to be agreed upon by the transmitter and receiver (and clearly must match at both ends)
2. NRZ is the most common type of line coding used
3. The transmitter and receiver must be configured to use the same baud rate, number of data bits, parity type, etc. From these two pieces of information, it is possible to derive the length of the frame (number of bits) and distinguish between a payload "1" and the stop bit.
okay but how is something like "11111111" transmitted? how does the receiver tell the data apart from the stop bit?
You are always have "start" bit for this purpose which are "0" (low level one), this is kind of something change or begin at the line.
Good video, but a minor correction! 0x52 is listed as ASCII "S" but it is actually 0x53, caused me some confusion while watching :)
(laughs) I wish I had a dollar for every person who noticed that :) You're absolutely correct - thanks!
can we have a FlexRay tutorial for the braking of M Benz
I'm working on some automotive protocol presentations that should be ready later this year :)
How toes the reciever know that the stop bit is a stop bit and not a data bit? If it already has to know when the stop-bit is supposed to come, why would it even need it? I don't get it at all.
As others have said, very good - not too long, but seems to hit the important details well!
Thanks (again!)
@@pauldenisowski 😄
we are not mention in code ,that type of method so where we use that type of method
Can it be used for media(sound,image) transfer from (for e.g) a bluetooth module? What is the cost of implementing this interface in comparison with I^2C, CAN or MLBB?
My understanding is that a UART is included in most Bluetooth chips for the host-controller interface, with USB being another popular choice. Generally speaking, UART is often cheaper and easier to implement than other protocols but has lower data throughput. That said, the suitability and cost of using one protocol vs. another is a function of many things, so I couldn't really comment on that part of the question without knowing a lot more about the application, other components in the system, etc.
Thank you.
Thanks for watching!
Nice stuff.
Thank you!
Aren't there supposed to be 8 data bits, for 8 bits equal to 1 bite?
Typically the user data is 8 bits long. That said, UART doesn't specify how long the payload should be. I still remember when 7-bit ASCII was the norm in serial text transmission.
very usefull and concise, thank you!!!
Thank you!
EPIC explanation thank you!
i have a question imagine a data with all 1's then how does the receiver identify the stop bit
UART requires that both sides be configurated with the same bit rate and the number of data bits (this is fixed for all UART frames exchanged and cannot be "signaled"). So the receiver will know how long the frame is and thus can identify the stop bit.
Best video ever
Thank you!
Very well explainded thanks !
Thanks for the feedback!
I'm facing problems with one of device , where the display required 7-n-1 setting but for the input need 8-n-1
7N1 means seven bits, no parity bit and one stop bit, whereas 8N1 means eight bits, no parity bit and one stop bit, so these settings are most likely incompatible. If one of the endpoints is a configurable terminal program (like Hyperterm, PuTTY, etc.) you should be able to configure these parameters.
hi...I want take 8bits data and 2 bits parity in design .Is it possible?
Sorry, not with "standard" UART. Is there a reason why you would want a second parity (well, error-checking) bit?
There’s a very silly error here:
ASCII for “S” = 0x53 NOT 0x52!!
Yep, must have fat-fingered that one (binary is correct). Thanks!
Awesome.
Appreciate the feedback - thanks for watching!
Very nice !
Thanks for great explanation. 0x52 should be 1010010 in binary system.
Lol - I've had about a half dozen people catch that already :) I guess I should be happy that people are watching the video that closely. Thanks!!!
4:15 its ox53
Awesome!
based
thank you
More thn basic 🙌
I'm a bit late but can I have the presentation I need it for school
i love u bro amaze
superb
For people who doesn't understand math, S is 0x53 not 0x52
Actually, it's for people who can't type :) The binary is correct :)
080 Breitenberg Ridges
033 Braun Fords
0x52 != 1010011
Thanks - you're absolutely right :)
4111 Rhianna Cape
364 Eldora Dale
0076 Evert Islands
7677 Franecki Station
Beatrice Square
Kohler Green
Hello
Hi!
Stehr Locks
Hamill Spur
Pónganle subtitulos al español :c
Si pudiera, lo haría :)
UART need 3 wires not 2!!! UART are rated in bit per second NOT baud rate!!! Two stop bits is never used for at least 60 years...
Yes, more than one stop bit is extremely rare. But I'm not sure what you mean by UART needing 3 wires - could you clarify? Thanks!
@@pauldenisowskicould be referencing a ground wire
9165 Kylee Mission
6679 Caterina Brooks
98589 Conor Trafficway
Thank you