RE: Printer Communications Problem

["Lou Schmaus" <lschmaus@xxxxxxxxxxx>]

Chuck,

You said this was a remote site. Are you using a 5494 or some other remote
controller for twinax support? You had said they site went down temporarily,
and then when it came back up, the printer didn't work. Could the remote
controller have 'forgotten' about the printer?

Also, are the baluns you're using exactly the same, using the same pinouts?
I am ashamed to admit I've spent many man-days over the years trying to
troubleshoot weird stuff like this, when the problem was a mis-matched set
of baluns. :-)

--------------------------
Lou Schmaus
MIS Director
Apparel Distribution, Inc.
lou@appareld.com

-----Original Message-----
From: midrange-l-bounces@midrange.com
[mailto:midrange-l-bounces@midrange.com]On Behalf Of Chuck Lewis
Sent: Thursday, February 06, 2003 12:12 PM
To: 'Midrange Systems Technical Discussion'
Subject: RE: Printer Communications Problem


Lou,

Had them double check the printer address thinking maybe I did not save it
when I set it (although since I did that here before I went there yesterday
I SHOULD have noticed that when I got there <BG>). I had tried deleting the
device and let it auto configure but nothing.

And I wrote a program the will print out a layout, sample below:

Date   2/06/03   Devices Attached to Control Unit xxxxxRMT     Page    1
Report CI500RT                                                 Time 11:53:47
Device             Device     Loc Swt
Name    Cat Class  Type/Model Adr Set  Description      Device Status

xxE06    *DSP *RMT   3486-BA   00   0  "xxxxxxxxx"       ACTIVE  "User"

xxE07    *DSP *RMT   3486-BA   01   1  "xxxxxxxxx"       ACTIVE  "User"
xxEPRT02 *PRT *RMT  *IPD-0     03   3  "xxxxxxxxx"       ACTIVE/WRITER

xxE09    *DSP *RMT   3486-BA   06   6  "xxxxxxxxx"         SIGNON DISPLAY

                                         ====  ====

Of course this is "compressed" and "edited" and looks MUCH better complete
and printed out :-)

I beginning to wonder about a wrong setting on the terminal (i.e. shared
address, etc.), flakey "t-connector" or balun problem...

I have them checking.

Thanks

Chuck