On 06/09/2012 10:23 AM, Kevin Reynolds wrote:
I'm trying to figure out which adapter I
should get to attach my wyse 60 to the console of a microvax III (3900).
I know I need a MMJ jack to DB25 male cable, but there are a few flavors. At first
glance it appears that I either need H8571-D or H8575-D, however its possible I ned
H8575-E.
Someone know which one to purchase? I have the BC16E cable required...
There are lots of flavors. Though Tony will probably blow a fuse when
reading this suggestion, figuring out the absolute perfectly correct one
No, I won't, and you won't blow a (real) fuse, or an IC, or anythjing if
you try it. One good thign abotu RS232 is that it is designed to
withstand having signals shorted or mis-connected.
is a complete waste of time...Get an MMJ adapter,
whichever one you can
find. Plug it in. If it doesn't talk, insert a null modem, and it will
talk. Simple as that.
I wouldn't quite do that. I'd grab one of thos little DB25-DB25 adapters
with LEDs to monitor the most important signals. Plug that into the
dapater first (with the adaptor conencted to the (powered-up) Microvax)
and see which line (2 or 3) it's transmitting on. One will be driven, the
otehr won't be. Then if it's driving pin 2, you need a null-modem.
I have solved many RS232 problems with little more than that.
Be sure to disable flow control on the terminal.
Again, I'm usually a purist to a fault, but where async serial is
concerned, if the GOAL is to get it talking, do what I said above...if
the goal is to spend two hours diving into the (unbelievably poor) RS232
standard, and then figuring out your mix of vendors' creative
interpretations of that standard, then figure out how to make it all
The worst thing I had to handle was an HP RS232 interface that correctly
(as per the standard) did the half-duplex turnaround with the control
lines. Problem is, almost nothing else does that...
talk, then go get exactly what you need and plug it
in...I've already
gotten the OS halfway installed by that point. I spent years agonizing
and being anal-retentive over "which one is DTE, which is DCE" etc etc
and just said "screw this, I want to BOOT the damn thing!"...and have
never looked back. ;)
Most of the time I look of odiities in the interface (many printers put a
busy/ready line on pin 11 for soem unknown reason), then use the LED
monitor thing to see if it's a DTE or DCE. 99%+ of the time the cable I
then wire works first time.
If you have any sort of MicroVAXen, you should keep a few MMJ adapters
of various flavors around anyway and if you have any sort of random
non-PeeCee computers, you should have a handful of null modems, gender
changers, DE9<->DB25 adapters, etc etc. You will use them all the time,
if you don't already.
The things I keep around are :
PC/AT (DE9) to DB25 adapter
DB25 socket to DB25 socket null modem with the flow control lines looped
back -- that is 4-5 and 6-8-20 on each conenctor (not connected between
the ends), 2/3 crossed over between the connectors and 7 wired straight
through
DB25 socket to DB25 socket null modem with the flow control lines crossed
over between the ends. That is 2 crossed with 3, 4 corssed with 5, 6
strapepd to 8 on each conenctor and crossed with 20 (from the other
conenctor) and 7 wired straight through
A universal gender cable. I've not seen this commerically, it's easy to
make. It's a couple of feet of 25 way IDC cable with a DB25 plugn and a
DB25 socket crimped on near each end (4 conenctors total). Does away with
the need for gender changers
The LED monitoring adapter I mentioned.
An assortemt of conenctors, multicore cable and a soldering iron for the
permanent job.
I do have a breakout box, adn even a datacomms tester. They are very
useful -- when I need them -- but most of the time the above bits get the
job done and are quicker.
-tony