TTL Serial Communication Protocol Explained | Part 3

[@SuperElephant]

This video was so condensed with knowledge that was truly reduced into bite size for human consumption. From zero to hero, thanks a ton!

[@programmingelectronics]

Awesome! Knowledge treats :)

[@sourcepathload]

Awesome job! I am a BAS technician and have been troubleshooting MSTP (serial comms) "data frame errors" i captured on a Picoscope. This video has helped me to better understand what node may be the one causing the network issues on my site. Big thanks!

[@programmingelectronics]

Glad it helped!

[@carlosbah4623]

Really enjoyed this lesson. Good teacher. ¡gracias por compartir!

[@earthianprithviwasi]

Thank you so much sir, finally I know this topic vividly.

[@programmingelectronics]

Thanks a ton for watching!!

[@Dreamer66617]

great this helped me understand my USB to TTL so i can flash my SB8285 wifi chip

[@ahmadjaradat3011]

Awesome job!

[@JaydenLawson]

Great tutorial! Thank you

[@programmingelectronics]

Glad it was helpful! Thanks so much for watching!

[@cristinocanga]

Really good content

[@programmingelectronics]

Thank you!

[@DodgyBrothersEngineering]

Little bit confused by you saying the 0 on the left is the least significant bit. In binary 0 on the left (128,64,32,16,8,4,2,1) would represent the highest value, so how can it be the least significant? OK just double checked 01000111 = G, so 1 on the right would be the least significant bit, looks like you just stuck the pointer in the wrong spot, since you are feeding them into the serial starting at 111... which is in line with what you are saying.

[@programmingelectronics]

That arrow location is confusing! We were trying to just high light the entire byte but clearly it seems like we are pointing to the MSB when we are talking about the LSB. Thanks for the catch!

[@davidzwitser]

Great video! The only thing that is still unclear to me, is how the sender and receiver agree on how big the different parts of the packet should be?

[@programmingelectronics]

Such a great question David! Basically, both side need to agree on it ahead of time - i.e. Both sides have been predetermine/designed for a specific size. Sort of like... I wouldn't bring a Portuguese translator with me to Germany. I would bring a German translator with me to Germany.

[@davidzwitser]

@@programmingelectronics Aah okay! So kinda like the baud rate, but then hardcoded into the UART?

[@programmingelectronics]

​@@davidzwitser Yes, that is the way I understand it. I also believe most UARTs are configurable, and can adjusted for different data bits, etc.

[@joshuapitong899]

Thank you.😊🥰

[@programmingelectronics]

Thanks Joshua!

[@DodgyBrothersEngineering]

Another great video... Is there a reason why you would ever want to be feeding in less than 8 bits? You said the data packet can be from 5 to 9, why would you ever want to feed in 5?

[@EngMazen]

You are living in a complex world, not all engines are sharing the same vision. Therefore, some chips vendors design their chips in a such strange way, I mean they design the protocol to accept 5-9 bits data. Or some times, you use the uart interface with your own custom chip(fpga for example) then you have the freedom to implement whatever you want, let say you make data bit to be 5 for speed constraints

[@duyha2454]

Thank you

[@programmingelectronics]

Thanks for watching!

[@chakreshjoshi4302]

Thanks

[@programmingelectronics]

Thanks for watching!

[@sunilchampaneri3208]

👌

[@programmingelectronics]

Thanks!

[@krishnawa_]

Learn something new

[@programmingelectronics]

Awesome! Thanks for watching!