Model T Serial Cable

From Tandy Tech
Revision as of 20:11, 10 August 2020 by Bkw (talk | contribs) (→‎Ideal Cables)
Jump to navigation Jump to search

Summary

The ideal cable to go from a PC to a Model 100, 102, 200, or 600, would be described as "9F/25M serial null-modem full-handshake".

That is an uncommon configuration to find in a single cable without needing adapters or needing to build it yourself custom.

The serial ports on Models 100-600 are wired DTE, the same as a com port on a PC, but with a female connector, unlike any pc.

This is a backwards configuration from everything else today. It has been suggested that maybe this is actually the original standard, and IBM came along later and changed it by putting male connectors on their PCs (probably to distinguish them from the printer port), but the standard today is that DTE ports are male. A female 25 pin port is either a parallel printer port or a DCE port on a modem.

That means that usually you always need some kind of adapter between a PC and a M100/102/200/600, because none of the normal cables you will have lying around will have the right combination of wiring and connectors.

The easiest way to connect with parts you are most likely to already have lying around, is to use a common 9F/25M Modem Cable combined with a 9M/F Null-Modem Adapter.

Ideal Cables

These cables are wired null-modem, have all the connections for hardware flow-control, and the right physical connectors on both ends, all in one factory-molded piece. You don't need any null-modem adapters or gender-changer adapters.

DCD+DSR<-->DTR
No RI
DCD+DSR<-->DTR
S+PG
No RI
DCD+DSR<-->DTR
S+PG
No RI
Includes nuts (removable) on the 9-pin plug screws, so you can screw a usb-serial adapter together to the cable, no matter whether the usb-serial adapter has screws or nuts.
No DCD
No RI

Software-Flow-Control-Only Ideal Cables

These cables actually work fine for everything(*). They are "less-ideal" only because the RTS/CTS hardware flow control lines are self-satisfied (aka shorted, faked, looped-back), or missing, or wired in some non-standard way like connecting DSR/DTR to CTS. But they have the correct physical plugs, and correct TX/RX wiring, and so they work fine for software flow-control.

And software flow-control is the only thing any of the old software ever used. The system rom doesn't even contain anything that accesses the RTS/CTS lines, not in BASIC nor TELCOM.

(*) The exception to "everything": The hardware in Models 100-600 can do RTS/CTS. The pins on the DB25 connector are wired up to the UART. But to use those signals, you have to manipulate the UART registers yourself from a machine language program. The only software I know of that does this to date is HTERM. So these cables are NOT suitable for HTERM.

This combination of connectors and wiring is sometimes called a "Serial Printer" cable, as opposed to a modem or null-modem cable.

DCD<-->RTS+CTS
RI<-->RI
DCD<-->RTS+CTS
RI<-->RI
DCD<-->RTS+CTS
No RI
DCD<-->RTS+CTS
No RI
DTR<-->DCD+RTS+CTS
No RI
DTR<-->DCD+RTS+CTS
No RI
DCD<-->RTS
DSR+CTS<-->DTR
No RI
This is a very unusual type of cable. If you don't have an HP or IBM plotter, I would not recommend getting this. But, strictly for the TX/RX and the physical connectors, as long as the software is ignoring RTS/CTS and DSR/DTR, it does work, so if you do have an HP or IBM plotter, then you could use this for both your plotter and your M100.

USB-Serial Adaters

Any one will work well enough. But some considerations are:

Models based on FTDI chips are generally better than the ones based on Prolific chips.

The serial cables all have screws in the plugs, so if you get a usb-serial adapter that has nuts (instead of screws) then the serial cable can be locked onto the usb-serial adapter with the screws.

legend

For all the cable wiring notes above, the notes indicate how the cable differs from a canonical RS-232 DTE-to-DTE null-modem reference.
Any signal that is not mentioned, is wired according to the reference.
Unless otherwise noted, the indicated wiring is symmetrical, IE the indicated connections are the same on both ends of the cable. IE, if TX or RX is not mentioned, then TX on one end of the cable is connected to RX on the other end of the cable.

S+PG: The cable Shield (& connector shell) is connected to Protective Ground or "frame ground" (pin 1 on the DB25 connector, no pin on the DB9 just the connector shell)

RI<-->RI: Ring Iindicator is connected to Ring Indicator

DB25 pin 22 (RI) is connected to DE9 pin 9 (RI)

DCD<-->RTS+CTS: Request To Ssend is connected to Clear T Send on one end, and both are connected to Data Carrier Detect on the other end.

DB25 pins 4 (RTS) & 5 (CTS) are connected to each other, and to DE9 pin 1 (DCD).
DE9 pins 7 (RTS) & 8 (CTS) are connected to each other, and to DB25 pin 8 (DCD).

DCD+DSR<-->DTR: Data Carrier Detect is connected to D Set Ready on one end, and both are connected to D Terminal Rready on the other end.

DB25 pins 8 (DCD) & 6 (DSR) are connected to each other, and to DE9 pin 4 (DTR).
DE9 pins 1 (DCD) & 6 (DSR) are connected to each other, and to DB25 pin 20 (DTR).