VERY Unlikely to actually be "Baudot" That was replaced by "Murray" in about 1900, and that was replaced by ITA (CCITT) before WW2. Tom Jennings did a nice page about those codes: http://www.wps.com/projects/codes/index.html However, ITA#2 is USUALLY MIS-referred to as "Baudot" Correcting that error is as difficult as explaining that Columbus' goal was NOT "to prove that the earth was round" (already completely known; HIS goal was to try to porve that it was less than 1/3 its actual size), or how it will someday soon be to try to convince people that Steve Jobs did NOT invent personal computers, wireless phones, GUI, music players, and tablet computers.

On Sun, 20 May 2012, Chuck Guzis wrote: . . . and it is CLEARLY labelled "DB15"

On Sun, 20 May 2012, Mouse wrote: Does one count start and stop bits? In that case, 2400 bps would be 3000 Baud on the host serial port. Alexey

They measure possible signal line changes per second, as you'd expect. And yes, start and stop bits are counted. In other words, a serial port baud rate of 2400 means that each bit time is 1/2400 s. A start bit takes that long, so does each data bit, so does the stop bit(s). Yes. AFAI Kthat is also correct. Hence the use of 'baud rate' is correct of a normal serial port, it measures the time taken for each bit (be it a fata bit or a framing control bit) to be sent. -tony

On 20 May 2012 at 15:58, Mouse wrote: Well, then you get into the mess of what interface the modem has with the host. If it's an 8-bit parallel interface, the argument could be made that the baud rate was 300. But no, I was referencing the signalling used on the telco side. Two- bit symbols. --Chuck

On 21 May 2012 at 20:36, Tony Duell wrote: One could just as easily argue that the 8 lines correspond to one of 256 symbols and that the symbols change 300 times per second. I could go with your 2400 baud if the signalling rate of each line were different, however. But the fact is that they're locked to the same 300-symbol-per-second clock. --Chuck

On 5/20/2012 10:31 AM, Fred Cisin wrote: I know we won't guess from the tape, only narrow the list with the encoding, but I wanted something that would punch the code on the tape as opposed to some generic lame photo. In 20 or 40 years when someone looks at this I just don't want them to point and giggle after doing whatever passes for google then and saying I didn't try to get it right. I have this example of a portion of the tape decoded, and the code that cracked it. I took the scans which were pretty poor and compared them to the available codes. So I could have a visual reference, I added a character representation in the orientation of my tape image. also had to contend with some <num> and <letter> shift punches. I suspect this might suggest which tty it was. I've only worked with punch equipped Teletypes of various models, which don't need such shifts since they are 8 level. Same for the Telex machine we used which was a Friden machine at 8 level. I appreciate the reference to Tom Jennings. As it turns out i have an ASR33 I acquired from him so I'll try to track down a contact and ask him. thanks Jim http://i1101.photobucket.com/albums/g437/jws1971/paper-tape/page1.png ************************************** http://en.wikipedia.org/wiki/Baudot_code ************************************** International MSB Right mark=1 sp=0 T 01 5 | . * <cr>02 | . * O 03 9 | . * * <sp>04 | . * H 05 | . * * N 06 | . * * M 07 | . * * * <lf>08 L 09 | * . * R 0A 4 | * . * G 0B | * . * * I 0C 8 | * . * P 0D 0 | * . * * C 0E | * . * * V 0F | * . * * * E 10 3 | * . Z 11 | * . * D 12 | * . * B 13 | * . * * S 14 | * . * Y 15 6 | * . * * F 16 | * . * * X 17 | * . * * * A 18 | * * . W 19 2 | * * . * J 1A | * * . * # 1B | * * . * * U 1C 7 | * * . * Q 1D 1 | * * . * * K 1E | * * . * * let 1F | * * . * * *

In article <4FB96BB8.8080402 at jwsss.com>, jim s <jws at jwsss.com> writes: This got me wondering.... Surely there is software out there that takes images of paper tape and "dumps" the codes? Is there something similar for punched cards as well? -- "The Direct3D Graphics Pipeline" free book <http://tinyurl.com/d3d-pipeline> The Computer Graphics Museum <http://computergraphicsmuseum.org> The Terminals Wiki <http://terminals.classiccmp.org> Legalize Adulthood! (my blog) <http://legalizeadulthood.wordpress.com>

On Mon, May 21, 2012 at 11:54 AM, Richard <legalize at xmission.com> wrote: I started to write one years ago (beginning with scanning the punch cards with a colored background to make the holes stand out) and did get edge and orientation detection working, but the per-card handling time on the scanner lead me to drop work on the project. If you were scanning a short stack of cards, it wasn't so bad, but a 3 foot deck? You'd spend a lot of time just getting the cards in and out of the scanner. My code wasn't anything magical - it used Tom Boutell's GD library to imported a monochrome GIF of a scan of the *back* of the card (to eliminate "noise" from the printing on most cards) then did a fairly uninspired search for the outer boundaries, then did an estimation of where the holes ought to be (based on the discovered dimensions of the edges) and did a simple (3x3) kernel sum of the targeted coordinate and if it was mostly "white", it was a zero, mostly black, a one. You couldn't skew the cards 45 degrees and expect it to work, but it was resilient enough to work with a little skew. -ethan