[Date Prev][Date Next] [Chronological] [Thread] [Top]

RE: BS 4.1.2 Failed to Write to Printer



 
The units need a tech to perform the rework.  And that should happen back in McKinney or at Diebold.  The unit base needs to be taken apart to access to the 40 wire printer cable.
 
Not all the units in the field will have this incorrect cable configuration.  But I can't tell you which ones do and which ones don't.  The only way to determine that is to either run two sequential reports or examine the cable configuration.  If you happen to be in the field with one or more of these new Diebold demo units (SN 1000xx), please run the report test and reply back to Barney Lucas with the test results (regardless of whether they are positive or negative), the unit serial number, and your location.
 
For the time being, the units can still be used in the field by using the workaround that was discovered.  The first report printing will not have a problem, but on the second report printing (for those units with the incorrect cable) you'll get a message stating "Failed to Write to Printer/ Retry?"  At that point, lift the paper release lever on the printer mechanism, set that lever back down again, and hit retry.  You'll then get your printout.
 
If this is completely unacceptable, you can always FedEx the unit back to McKinney and we'll turn it around the same day we receive it.  Or if there are numerous units on site that need the rework, then we could have a technician fly out to your location and perform the rework to the cable.  If we can personally courier RFP responses weekly, then why not cables.  Regardless of the rework location, the units on site would have to be tested first to assess the needs.
 
Ian
-----Original Message-----
From: owner-bugtrack@dieboldes.com [mailto:owner-bugtrack@dieboldes.com]On Behalf Of Steve Knecht
Sent: October 25, 2001 10:40 AM
To: bugtrack@dieboldes.com
Subject: Re: BS 4.1.2 Failed to Write to Printer

Do units need to be returned or can you do a cable upgrade in the field?
----- Original Message -----
Sent: Thursday, October 25, 2001 7:41 AM
Subject: RE: BS 4.1.2 Failed to Write to Printer

This issue has already been addressed by Diebold.  It had to do with a delivery from a cable vendor that had two styles of cables.  The process that allowed the incorrect cables through Diebold's material receiving and into their production line was examined and corrected.  This was not taken lightly.
 
It was dealt with prior to the Johnston County order production start.
 
Ian
-----Original Message-----
From: owner-bugtrack@dieboldes.com [mailto:owner-bugtrack@dieboldes.com]On Behalf Of Steve Knecht
Sent: October 24, 2001 6:33 PM
To: bugtrack@dieboldes.com
Cc: Frank Kaplan
Subject: Re: BS 4.1.2 Failed to Write to Printer

Then this needs to get to Dean/Diebold ASAP.  You are manufacturing for Johnson are you not?
----- Original Message -----
From: Larry Dix
Sent: Wednesday, October 24, 2001 1:51 PM
Subject: RE: BS 4.1.2 Failed to Write to Printer

This appears to be a hardware issue.  I can see the smile on Ken’s & Tab’s faces.

 

I can recreate the printer problem using 4.0.11 on a new Diebold TS.  I can NOT recreate the problem in 4.0.11 on an old unit.  The same scenario holds true for 4.1.2, it can be recreated on a new unit but not the old.

 

Larry J. Dix

Vice President of Operations

Global Election Systems

 

-----Original Message-----
From: owner-bugtrack@dieboldes.com [mailto:owner-bugtrack@dieboldes.com]On Behalf Of Jeff Hintz
Sent: Wednesday, October 24, 2001 2:07 PM
To: bugtrack@dieboldes.com
Subject: RE: BS 4.1.2 Failed to Write to Printer

 

Does it have something to do with the size of the report or the database???

 

I am doing a small 1 race election with version 4.1.2, and I have no problems printing reports.  Zero Report, Election Report, Post-Election reports.

 

Just a guess.

 

Jeff

-----Original Message----- 
From: owner-bugtrack@dieboldes.com [mailto:owner-bugtrack@dieboldes.com]On Behalf Of Larry Dix
Sent: Wednesday, October 24, 2001 1:57 PM
To: bugtrack@dieboldes.com
Subject: RE: BS 4.1.2 Failed to Write to Printer

When the error message comes up on the screen, lift the little grey paper release lever on the right hand side of the printer.  Put back down and retry the printer.  It works here every time.  Do the proper solution, but a work around.

 

 

Larry J. Dix

Vice President of Operations

Global Election Systems

 

-----Original Message-----
From: owner-bugtrack@dieboldes.com [mailto:owner-bugtrack@dieboldes.com]On Behalf Of Steve Knecht
Sent: Wednesday, October 24, 2001 1:41 PM
To: Bugtrack@dieboldes.com
Subject: BS 4.1.2 Failed to Write to Printer

 

Date: Tue, 23 Oct 2001 14:46:26 -0700
To: bugtrack@dieboldes.com
From: Deborah Seiler <deborahseiler@attglobal.net>
Subject: BS 4.1.2 Printing Error

During CA certification, I upgraded Deborah's unit to 4.1.2 at the
beginning of demo.  During demonstration we set unit to Election
mode.  Then went to print a zero report.  Got a "Failed to write to
Printer" message.  (Same as Don/Jeff reported the other day).

I didn't take notes, but I believe that was the
message.  This is the same message I got and reported last night on my
unit, when running 4.1.2.

I immediately reloaded 4.1.1.7, set for election and printed report.  We
then brought unit back to Deborah's house after the demo.  I reloaded
4.1.2, set it for election and printed Zero report OK.  Then went to print
totals report and got same "failed" message.  It is inconsistent (at least
to me so far), but frequent and replicable on both our units at various times.  The only
thing that seems consistent is the "first time" use of the printer in each
of these functions.  This seems to render this version unusable to some
degree in production.

Steve Knecht
Global Election Systems
415-893-9941 office   415-893-9951 fax
415-225-6591 cell