Talk:Bit stuffing

There was also an article called "Bitstuffing" which I've redirected here. Lukus 06:44, 18 October 2005 (UTC)

Bit stuffing vs. Padding
''Bit stuffing is used for various purposes, such as for bringing bit streams that do not necessarily have the same or rationally related bit rates up to a common rate, or to fill buffers or frames. The location of the stuffing bits is communicated to the receiving end of the data link, where these extra bits are removed to return the bit streams to their original bit rates or form. Bit stuffing may be used to synchronize several channels before multiplexing or to rate-match two single channels to each other.'' I only know the above as "padding". "Bit stuffing", according to my Data Communications lecture, is the process described afterwards, which involves making sure reserved codewords do not occur within the data field. --KagamiNoMiko 21:16, 13 December 2006 (UTC)

Receiver Losing Count?
...and if that time is too long, the receiver can lose count. I seriously doubt that that is the issue unless it's just using a 3-bit counter. More likely, the issue is that the receiver can get out of sync with the transmitter if the clocks aren't exactly synchronized. Stefanv (talk) 16:00, 18 December 2012 (UTC)
 * You're correct, and I reworked the page. Let me know what you think. Number774 (talk) 15:30, 27 February 2013 (UTC)

Not all SDLC implementations utilize an NRZI encoding scheme at the physical level
I've worked a lot with NEMA TS2 traffic cabinets. They use an SDLC network for communications among devices within the cabinet. NEMA TS2 uses the RS-485 standard at the physical level and has separate clock and data signals. Therefore, I think the zero bit insertion section of this article is misleading. SDLC can be implemented different ways physically. In the case of NEMA TS2 traffic cabinets, zero bit insertion is really only useful for flag detection and does nothing for synchronization. Oilyraincloud (talk) 19:17, 22 July 2014 (UTC)