[GreenKeys] Asr33: How are BREAK encoded ?
Eric
epvgk at limpoc.com
Tue Feb 21 10:44:52 EST 2017
It is probably incorrectly interpreting the null character as a break actually.
On February 21, 2017 3:31:43 AM PST, Julien Scrofani <julien.scrofani at gmail.com> wrote:
>Hi guys,
>
>Thank you for your responses.
>
>The start and stop units are not parts of the punched code on the tape,
>right ?
>How then, when I read the tape, does the adapter convert these
>sequences
>into BREAK sequences ?
>
>Julien
>
>Le mar. 21 févr. 2017 à 05:05, Jones, Douglas W
><douglas-w-jones at uiowa.edu>
>a écrit :
>
>> From: Julien Scrofani [julien.scrofani at gmail.com] Monday, February
>20,
>> 2017 2:09 PM
>>
>>
>>
>> > I taped several BREAK sequences with the tty puncher, pressing my
>finger
>> more or less time on the key. The punched codes differ a lot (see
>pic).
>> When I read the tape, toward my terminal via the usb current loop
>adapter,
>> all BREAK are correctly converted.
>>
>> Are they coded with several bits patterns ? If not, how are they
>> interpreted correctly by the adapter ?
>>
>>
>>
>> The adapter recognizes break by the lack of a stop bit at the end of
>the
>> character, not by the bit pattern.
>>
>>
>>
>> Doug Jones
>>
>> jones at cs.uiowa.edu
More information about the GreenKeys
mailing list