Lesson #3 on why Baud/s != Bit/s
-
Lesson #3 on why Baud/s != Bit/s
Lots of serial protocols use stuff bits at the data link layer. The data itself is the clock and if there is no change in the data, the clock is lost. So they after every 4 or so consecutive 0s it adds a fictitious 1 to make sure the recipient's clock is synchronized.
-
Lesson #3 on why Baud/s != Bit/s
Lots of serial protocols use stuff bits at the data link layer. The data itself is the clock and if there is no change in the data, the clock is lost. So they after every 4 or so consecutive 0s it adds a fictitious 1 to make sure the recipient's clock is synchronized.
Doesn't USB use manchester encoding like ethernet? So you have a consistent clock frequency it's just weather the data edge is before or after the midpoint.
-
Doesn't USB use manchester encoding like ethernet? So you have a consistent clock frequency it's just weather the data edge is before or after the midpoint.
Beats me. I just know that serial protocols do all kindsa fun stuff at the data link layer to maintain data integrity. Stuff bits, optional parity bits, weird timing changes.
-
Doesn't USB use manchester encoding like ethernet? So you have a consistent clock frequency it's just weather the data edge is before or after the midpoint.
Hello from Manchester!
