About Baud

Protocol specifications describe bytes in tables. Tables are precise, but they hide the thing that actually makes protocols click: time. Which bit leaves first? When does the receiver look at the wire? Which header field is read before which?

Baud turns those tables into short motion pieces. You see a UART character leave the wire least-significant bit first, a TCP header arrive and light up field by field, and a handshake play out between two machines. Every number on screen is computed, not typed in: the checksums and CRCs in the examples are real.

Each protocol is described once as data: a list of fields, bits and messages with English and Japanese text. A small renderer turns that description into an SVG for any moment in time. The server draws the finished diagram so the page is readable without JavaScript; in the browser a player moves time forward and swaps the picture.

The diagrams and explanations are original. They follow the public specifications listed on each protocol page (RFCs, ISO, NXP, MMA, OASIS and others). Example data is made up, except for well-known constants such as the MPU-6050 WHO_AM_I register.

No user data is collected or stored.