🚀 go-pugleaf

> We are running Opscan 10's and have observed a problem since they were
> first installed--more often on one of the machines than on the other.
> Once in awhile, the machine neglects to print on the form, e.g., batch
> number, serial number, date.  It is sporadic enough that it can be
> called unreproducible and doesn't appear to be related to the particular
> application being run.  It can happen within a 20-sheet job or more
> frequently in a larger job--but not with any type of regularity.  We've
> tried adjusting the sensors and have swapped computers between the two
> machines.  The problem pretty well stays with the one machine.

> Has anyone else observed this problem on an Opscan?  Any suggestions
> about what's causing the problem?  We're not getting any quick solutions
> from NCS (the problem has been around for 9 months now).

>           Dan Precht
>           Computing & Network Services
>           University of Alberta

Dan,

2 things:

1.)  We at Williams have an Opscan 5 with transport and had a similar problem.
     A service call to NCS was placed and they in turn replaced something
     called the "printer assy" or "print bd assy" (I'm trying to read my
     receipt).  The part number is 317-010-015.  The printer has been working
     fine since.

2.)  If not that mechanism, are you sure that the mis-printing is not due
     to the failing of an edit check?  Is the record still being written to
     a file?

feel free to call or e-mail.

Doug Rydell                   (413) 597-2083
Programmer/Analyst            DOUGLAS.A.RYDELL@WILLIAMA  (BITNET)
Center for Computing          DOUGLAS.A.RYDELL@WILLIAMS.EDU  (INTERNET)
Williams College
Williamstown MA 01267