RE: Printer Communications Problem

["Chuck Lewis" <clewis@xxxxxxxxxx>]

Lou,

The remote site(s) are on a Frame Relay network with Perle 494 control units
with an Ethernet card, via TCP/IP.

There is no need to "save the configuration" on these devices, at least that
I've ever seen, unlike IBM models that I have used in the past.

Baluns are the same too.

And they checked the config on the terminal and it matches up and has
nothing that should cause a problem. I'm going to have them disconnect the
terminal from the mix to be SURE, as someone earlier suggested.

The most fun I ever had along the lines you mention is back in the twin-ax
cable days and the FUN of putting THOSE connectors on. They had that little
white "insulating sleeve" that was of a cardboard makeup and latter plastic.
Well we bought crimp tool and our maintenance departments electrician made
them up for us. Key on this one part was making sure you kept the little
"dot" that was on it, consistent. Well he religiously did this. It was
MONTHS after our last addition and we were doing a new device add. All of a
sudden devices start dropping on the one run. No sense to the order, etc. We
beat our heads against the wall and finally our CE, who was in on something
else, said he'd look at it. Guess what ? We had gotten some of the
connectors in and the manufacturer had messed up on that little dot. And
this caused a reverse polarity problem. What a nightmare. My friend in
maintenance and I HATED twin-ax, but we could never get the OK to replace it
with twisted-pair because "what we have, works"...

Thanks,

Chuck

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

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


_______________________________________________
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@midrange.com
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@midrange.com
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.