On Wed, Dec 21, 2022 at 11:51 AM Jim Anderson <[email protected]> wrote:
> I’ve run into this before with the 200 – I don’t remember if it was CTS or > DSR or both that it wants to see asserted, but it definitely does behave > differently from the 100 and 102. If you don’t have one or both of those > lines high, the 200 appears to freeze up if you attempt serial > communication using TELCOM (ctrl-Break recovers). The 100 and 102 (at > least in TELCOM) don’t seem to care. > > > > There’s no real harm in jumpering both of these signals high if your wifi > modem isn’t actively asserting either of them. In a DB9 you would jumper 7 > (RTS) to 8 (CTS) and 4 (DTR) to 6 (DSR). In a DB25 those would correspond > with 4 to 5 and 20 to 6. > > > > > Agree... one of my few Model T pet peeves... this is the "cable check"... uh... feature. Don't know what they were thinking. A given cable either works or it doesn't... in what universe is it a feature to do a sanity check on lines that aren't actually involved in communication on the Model T? And then if there is an issue, don't give a clear error message, just lock up. Just weird, I don't know what the engineers were thinking. TS-DOS, TEENY do it as well unless you're running a version with the feature disabled. Maybe Radio Shack and the 3rd party vendors wanted people to buy better or proprietary cables (from them)? Since the main result of the feature is that 3-wire cables don't work without looping back. -- John.
