On Jan 29, 2014, at 5:17 PM, Kyle Owen <kylevowen at gmail.com> wrote:
...
When I talk to my PDPs, I tend to use minicom at 9600 7E2 or 8N2 depending
on if I'm sending ASCII or binary data. 7E2 works fine with every program
I've tried. My notes say that trying 8N2 with CHECKMO II resulted in
garbled characters on the receiving end. Maybe the chess program was
managing to parse the incoming characters alright, but it certainly wasn't
being received by minicom without switching to 7E2.
Perhaps my issues have not been the parity but rather the data
length...more to investigate!
Most likely, yes. The correct setting would be 8N1 or 7E1 for all speeds above 110. For
110, you?d want 2. If you set it for 2 stop bits, it will transmit 10% slower which is
fine, but it may also expect 2 stop bits on receive and get overrun by the incoming data
stream because it?s coming with one stop bit.
The ?1.5 stop bits? notion applies to 5 bit codes for some speeds. In fact, the actual
stop length depended on speed and machine, and might in fact be 1 bit time for some. Then
to confuse things even more, the Selectric when connected with a UART, at 134.5 bps,
required some odd stop length I think, but I don?t remember the details. (Those machine
also use any number of code tables, none of which are ASCII. RSTS supported them for a
while, V5 to V8 or so.)
paul