RE: 4224 works on V4R4 and malfunctions on V5R1

Jerry, this is probably the first thing you checked, but I wasted several
days once with a similar problem that came down to making sure the pins were
not being pushed out of the twinax connector.  Everything looked ok before
trying to connect twinax to the brick, but one of the pins pushed in when
trying to screw down the cable end.  With the twinax disconnected from the
brick, try pushing the pins and see if one is loose.  (It's always the
low-tech bits that get overlooked....) 

hth,

Eric DeLong
Sally Beauty Company
MIS-Project Manager (BSG)
940-898-7863 or ext. 1863



-----Original Message-----
From: Jerome Draper [mailto:jdraper@trilosoft.com]
Sent: Wednesday, January 22, 2003 4:12 PM
To: Midrange Systems Technical Discussion
Subject: Re: 4224 works on V4R4 and malfunctions on V5R1


We are cabled direct from the brick to one 4224 and then daisychained to the
other 4224.

Jerry

----- Original Message -----
From: Steve Richter <srichter@autocoder.com>
To: Midrange Systems Technical Discussion <midrange-l@midrange.com>
Sent: Wednesday, January 22, 2003 2:06 PM
Subject: RE: 4224 works on V4R4 and malfunctions on V5R1


> Jerry, Do you cable direct from the brick on the back of the as400 to the
> printer using twinax cable, no baluns, patch panel wiring?  Whenever I
have
> trouble with twinax devices I always try to factor out any faulty wiring.
> If not, can you cable direct from the brick to the printer with twinax
> cable?
>
> Steve
>
> -----Original Message-----
> From: midrange-l-bounces@midrange.com
> [mailto:midrange-l-bounces@midrange.com]On Behalf Of Jerome Draper
> Sent: Wednesday, January 22, 2003 3:51 PM
> To: Midrange Systems Technical Discussion
> Subject: Re: 4224 works on V4R4 and malfunctions on V5R1
>
>
> Yeah, it seems that if the controllers are the same type the results
should
> be the same.  I'm wondering if it's the speed of the controller or if the
> port on the brick isn't bad.
>
> Jerry
>
> ----- Original Message -----
> From: Philipp Rusch <Philipp.Rusch@rusch-edv.de>
> To: Midrange Systems Technical Discussion <midrange-l@midrange.com>
> Sent: Wednesday, January 22, 2003 12:32 PM
> Subject: Re: 4224 works on V4R4 and malfunctions on V5R1
>
>
> > Twinax has been improved in speed with newer controllers, they now do
> > 2 Mbit instead of 1 MBit as before. That data area mentioned in other
> posts
> > controls stepping down of the speed back to the old level.
> > I seem to remember that the old controllers were also only capable of
> polling
> > one port after the other, leaving only one port active at a time.
> > The newer ones are able to poll several (two ?) ports simultanously,
> > this causes troubles if your are using twinax-to-RJ45 multiplexers, for
> instance.
> > It's strange that this should happen, when both controllers in your
> machines
> > seem to be of same type.
> >
> > HTH, regards from Germany, Philipp Rusch
> >
> > Jerome Draper schrieb:
> >
> > > I have two 4224 *IPDS printers hooked up to a V4R2 machine and they
work
> > > fine.  I move them to a new V5R1 machine and they hardly print at all.
> > > Funny scratching by the print head and sporadic print lines but never
> > > anything close to a full report.  For example, they won't print a
> standard
> > > report from QPRINT.  Put them back ont he V4R2 machine and all is
fine.
> > >
> > > Anyone seen this?  PTF?
> > >
> > > TIA,
> > >
> > > Jerry
> > >
> > > Jerome Draper, Trilobyte Software Systems, since 1976
> > > Network and Connectivity Specialist -- Mac's, LAN's, PC's, and iSeries
> > > Representing Synapse, Nlynx, Perle, CLI, Intermate and Others .....
> > > (415) 457-3431 - (415) 258-1658fax - http://www.trilosoft.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.cgi/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.
> >
> > _______________________________________________
> > 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.cgi/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.
> >
> >
>
> _______________________________________________
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing lis
t
> To post a message email: MIDRANGE-L@midrange.com
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo.cgi/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.
>
>
> _______________________________________________
> 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.cgi/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.
>
>

_______________________________________________
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.cgi/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.