Difference between revisions of "Honeywell BCRU211G"
m (→Hardware Connectivity) |
m (Add video board connector signals image.) |
||
| Line 199: | Line 199: | ||
File:honeywell_bcru211g_habitat.png | File:honeywell_bcru211g_habitat.png | ||
File:honeywell_bcru221g_vcfmw.png | File:honeywell_bcru221g_vcfmw.png | ||
| + | File:bcru211g_video_board_connector_signas.jpg | ||
</gallery> | </gallery> | ||
Latest revision as of 22:37, 15 October 2024
| Honeywell BCRU211G | |
|---|---|
|
| |
| Manufacturer | Honeywell |
| Model | BCRU211G |
| Communication | |
| Interface | serial |
| Baud Rates | 300, 600, 1200 ,1800 ,2400, 4800, 9600, 19200 |
| Display | |
| Size | 12.5 inches |
| Character Modes | |
| Resolution | 80x24 |
| Firmware | |
| CPU | Motorola 6800 (MC68A00P) |
| ROM | 2x64 (D2764A) |
| RAM | 2x16K,(HM6116P) |
| Code Chart | Honeywell BCRU211G |
This is another one of the Honeywell serial terminals that were typically used with DPS mainframes, after Honeywell took over the line of GCOS-based mainframes from General Electric. Probably used with DPS8 or DPS6 mainframes with either GCOS or MULTICS (confirmation needed).
In terms of control characters, it has a lot of similarities with the VT52, but without ANSI compatibility mode, and without the GEMDOS/TOS extensions, but it also has a bunch of extra features (and quirks!).
Hardware Connectivity
The terminal is built relatively modular. The main board pulls out, as does the power supply. Both have card-edge connectors.
A typical db25 serial cable doesn't seem to work, nor does the typical null-modem cable. Instead, following pinout works:
DB25 pinout:
--------------------------------------------------------------------
\ (1 ) (2 ) (3 ) (4 ) (5 ) (6 ) (7 ) (8 ) (9 ) (10) (11) (12) (13) /
\ (14) (15) (16) (17) (18) (19) (20) (21) (22) (23) (24) (25) /
\______________________________________________________________/
1: Shield ground 6: DSR (data set ready) 11: N/C
2: TXD (transmit data) 7: Signal ground 12: DCD (2)
3: RXD (receive data) 8: DCD (data carrier detect) 13: CTS (2)
4: RTS (request to send) 9: test 14: TXD (2)
5: CTS (clear to send) 10: test 15: DCE
16: RXD (2) 21: signal quality detector
17: RX clock 22: RI (ring indicator)
18: N/C 23: data signal rate detector
19: RTS (2) 24: DTE
20: DTR 25: N/C
TXD (pin 2) has data going from the terminal to the computer at 0-5V
TXD2 (pin 14) has data going from the terminal to the computer at 0-1.5V
DB9 pinout:
-----------------------
\ (1) (2) (3) (4) (5) /
\ (6) (7) (8) (9) /
\_________________/
1: DCD 4: DTR 7: RTS
2: RXD 5: GND 8: CTS
3: TXD 6: DSR 9: RI
Wiring:
-------
DB25 DB9
-------------------------------------------------------------------
1 (shield) -> shield (the metal bit around the connector)
2 (TXD) -> 2 (RXD)
3 (RXD) + 16 (RXD2) -> 3 (TXD)
4 (RTS) -> 8 (CTS)
5 (CTS) -> 7 (RTS)
6 (DSR) + 8 (DCD) -> 4 (DTR)
7 (GND) -> 5 (GND)
20 (DTR) -> 1 (DCD) + 6 (DSR)
DIP Switch Settings
1 2 3 4 5 6 7 8 9 10 _ _ _ _ _ _ _ _ _ _ 1 | | | | | | | | | | | 0 |_|_|_|_|_|_|_|_|_|_| | | | | | | | | | | | | | | | | | | | `- beep on keypress | | | | | | | | `- screen blanking | | | | | | | `- baud rate 1 | | | | | | `- baud rate 2 | | | | | `- baud rate 3 | | | | `- bits per character? | | | `- bits per character? | | `- vertical wrap (if in the down position, | | going past line 24 wraps back to line 1, | | effectively disabling scrolling and messing | | up all sorts of stuff for most stuff expecting | | normal terminal behavior.) | `- local echo (up=off, down=on) `- Test mode (runs test loops)
Need some further testing, but I believe bits 4 and 5 switch between 7 or 8 bits per character separately for sending and receiving.
Baud Rate Configuration Switches
.---- baud rate 3 (switch 6)
/ .--- baud rate 2 (switch 7)
/ / .-- baud rate 1 (switch 8)
/ / /
0 0 0 300 baud
0 0 1 600 baud
0 1 0 1200 baud
0 1 1 1800 baud
1 0 0 2400 baud
1 0 1 4800 baud
1 1 0 9600 baud
1 1 1 19200 baud
Power Supply Pinout
- Pin 5: 12V @250mA
- Pin 6, 7: 5V @5A
- Pin 10, 11, 12, 13, 15: Common/GND
- Pin 14, 16: 15V @2A
Quirks & Features
Like the VT52 it has a 'graphics' mode, which really means, switching character set to a set of 'graphics' characters, this is where you'll find your box-drawing stuff and the like, as well as some math symbols not present in the standard ascii set.
A quirk though, is that the BRCU221G has the enter/exit graphics mode commands INVERTED from what's documented for the VT52. I don't know if that's a bug in the terminal, or in the VT52 documentation (someone ought to confirm this with a real VT52)
Another deviation from the VT52 is that \eZ also behaves differently, in that, instead of sending identifying information back to the host, it instead prints debug info on the terminal. It also has a second version of this, \ez (lower-case), which prints a shorter version of the debug info.
Cursor movement and everything else, is the same as VT52.
- Unlike the VT52, the Honeywell BCRU can change it's font brightness to a less bright color, and switch back.
- It has a single-command clear screen, akin to the equivalent in the VT52's GEMDOS/TOS extensions, but a different code.
- It has screen blanking functionality (it automatically blanks on idle if configured per dip switch, but there is also a control code you can send to force the screen to turn off)
- It has a way to force all output to the bottom or top line only (presumably for header/footers on screens/forms)
- There's a neat 'screenshot' command where it will send back everything on the screen to the host.
- It can display light-colored or normal colored fonts.
ROM Dumps
The following zip file includes dumps for both logic roms and the character rom.
It also includes a very simple bash script to view the character rom font in binary form, and a text file of the output produced by it.
File:Honeywell_BCRU221G-001_ROM_DUMPS.ZIP