Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!csd4.milw.wisc.edu!leah!rpi!pawl!shadow From: shadow@pawl.rpi.edu (Deven T. Corzine) Newsgroups: comp.sys.amiga Subject: Re: "baud" == "bits"/"second" Message-ID: Date: 10 Jul 89 20:38:21 GMT References: <19246@louie.udel.EDU> Sender: usenet@rpi.edu Organization: Rensselaer Polytechnic Institute, Troy, NY Lines: 31 In-reply-to: denbeste%bbn.com@mitvma.mit.edu's message of 8 Jul 89 01:35:49 GMT In article <19246@louie.udel.EDU> denbeste%bbn.com@mitvma.mit.edu (Steven Den Beste) writes: > Well, with bits, bauds, and bytes flying around 2400 baud and > 2400 bps is escentialy the same thing. "2400 baud modem" is technically incorrect, but so entrenched as to be unworthwhile to worry about. Just accept the common usage of "baud" as meaning "bits per seconds" and leave it at that. > That is, if a random sample of survayed bits do indeed subscribe > to a well respected baud, and we are talking ten bits per character > (seven, around two paraty bits, wraped by one stop bit) [...] No. Generally, you will have 1 start bit, either 7 data bits and 1 parity bit, or 8 data bits, and 1 stop bit. [1+7+1+1=10, 1+8+1=10] You COULD have a different configuration, but it is quite rare. Old teletype terminals ran at 110 baud, using 1 start bit, 7 data bits, 1 parity bit, and 2 stop bits, (because of the slow speed of the print head) yielding 11 bits per character, and a throughput of an even 10 characters per second. A 2400 "baud" modem uses 10 bpc for 240 cps, exactly. It is 2400 bps, but the data stream is cut to 1920 bps. (or 1680 with parity checking) This all applies to asynchronous modems, which need the start and stop bits for synchronization and error detection. Synchronous modems are a different situation. Deven -- shadow@[128.113.10.2] Deven T. Corzine (518) 272-5847 shadow@[128.113.10.201] 2346 15th St. Pi-Rho America deven@rpitsmts.bitnet Troy, NY 12180-2306 <> "Simple things should be simple and complex things should be possible." - A.K.