Re: Printer Communications Problem

["Steve Landess" <steve_landess@xxxxxxxxxxx>]

Chuck - there is a command to print the addresses of twinax devices:

PRTDEVADR CTLD(XXXXXXX)

Works for both local workstation controllers and remote controllers, IIRC.

Steve Landess
Austin, Texas
(512) 423-0935

----- Original Message -----
From: "Chuck Lewis" <clewis@iquest.net>
To: "'Midrange Systems Technical Discussion'" <midrange-l@midrange.com>
Sent: Thursday, February 06, 2003 11:12 AM
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
>
>
> -----Original Message-----
> From: Lou Schmaus Sent: Thursday, February 06, 2003 11:37 AM
>
>  Chuck,
>
> I can think of a couple of things to check:
>
> 1. Make sure the address of the printer wasn't changed accidentally, and
it
> auto-configged under a new name. this sounds like the most likely given
the
> symptoms you're describing.
>
> 2.   Make sure the address of the printer isn't the same as the address of
> any of the other devices on the same line.
>
> 3. Try plugging in ONLY the printer, directly to the wall jack. I've seen
> cases where twisted-pair daisy-chaining does weird things like this. If
> possible, use real twinax for the daisy-chain to the terminal, not
> twisted-pair.
>
> HTH,
> --------------------------
> Lou Schmaus
> MIS Director
> Apparel Distribution, Inc.
> lou@appareld.com
>
>
>
>
> _______________________________________________
> 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.
>