Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Appears to care about the high bit of a byte #5

Open
emooreatx opened this issue Sep 15, 2020 · 2 comments
Open

Appears to care about the high bit of a byte #5

emooreatx opened this issue Sep 15, 2020 · 2 comments

Comments

@emooreatx
Copy link

We tried to use the emulator with a minicomputer emulator. The ASR33 always had the high bit set, a la sticky parity, but emulators have no UART in line so outputs the raw data that would go to the ASR33.

Anything from 0x00 to 0x7F is malformed, but obviously should be treated as valid ascii for compatibility, and anything from 0x80 to 0xFF should have 0x80 subtracted before rendering to emulate an ASR33 TTY. This would be like an "enhanced teletype compatibility" mode.

@Random832
Copy link
Owner

Random832 commented Oct 2, 2020

I was inspired by this issue to write a full parity system [in a branch for now since I don't have a good way to test it] - the default behavior is as you requested, and it also should be capable of checking [or generating] any of even/odd/mark/space parity, with a command line option to select.

added commit b25d358

@emooreatx
Copy link
Author

Awesome! We will strip the emulated uart from the SEL 810 emulator and try it with the ttyemu directly. Thank you!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants