SunVTS 2.0 Test Reference Manual
  Procure somente este livro
Fazer download desta apostila em PDF

lpvitest

14

SBus printer cards have two printer ports: one for SPARCprinters(TM), and one for any parallel port printer. lpvitest verifies the functionality of SPARCprinter ports, and bpptest verifies the functionality of bidirectional parallel ports.

Printer Test Hardware and Software Requirements

The SBus Printer Card and device drivers must be installed in order to run lpvitest or bpptest. A printer must be connected to the SPARCprinter or bidirectional parallel port, and powered-up. If both a SPARCprinter and a parallel port printer are hooked up to the SBus card, you can test both ports simultaneously.
If you are testing the SPARCprinter port, be sure the magnets on the SPARCprinter paper tray are set to the correct paper size. For more information, see the SPARCprinter Installation and User's Guide and the label on the printer tray.
The lpvitest verifies that your SBus card and SPARCprinter are working properly by attempting to transfer a data pattern from the SBus card to the SPARCprinter and printing the pattern.
If the SBus card and printer are functioning properly, you can see in the SunVTS Status Window that lpvitest made a successful pass, and the pattern transmitted to the printer printed correctly.
If this test passes successfully, the SBus DMA circuitry, the SPARCprinter, and the device driver are functioning properly.

lpvitest Options

Gráfico

Figure 14-1 lpvitest

Access This field is informational only. Writeonly is the only option currently available. This indicates that the only data being transferred is going from the SBus printer card to the SPARCprinter.
Mode This option allows you to select how often to print the test image. The default setting is Fast; the available settings are:
FastPrints an image every 1 minute.
MediumPrints an image every 12 minutes.
Extended Prints an image every 30 minutes.
Image This option lets you choose which test image to print. The settings are:
DefaultA pattern of vertical lines on one page and a checkerboard pattern on another.
57fontsAn image of the 57 different fonts that the printer supports.
Userdefined You can use any rasterfile as a test image. Just place the file in
the /opt/SUNWvts/bin directory and save it as the file name u_image.
Resolution This setting defines the printer resolution of the printed test pattern. The choices are 300 or 400 dots per inch.

Note - Patterns such as the default test pattern are printed at different sizes and at different dpi resolutions. The text in the 57 fonts pattern prints in the same size, using the two different resolutions.

lpvitest Test Mode

This test only supports the offline mode of testing.

lpvitest Command Line Syntax

/opt/SUNWvts/bin/lpvitest standard_arguments -o
dev=device_name,access=writeonly|readonly,image=filename,reso=resolution,
mode=mode

Argument Explanation
dev=device_nameSpecifies the name of the device. This should be of the form
/dev/lpvi#, where # is the number of the device.
access=Choices are write-only or read-only, but just write-only is supported at this time. See Access in Section , "lpvitest Options."
image=filenameThis is the name of the file containing the test image. Possible values are:

imagefile Any file containing user-defined images. Before running SunVTS, copy the raster image file to the /opt/SUNWvts/bin directory and save it with the filename u_image. The size of the image is adjusted based on the resolution.

57fonts Contains an image of 57 fonts. The size of the image is adjusted, based on the resolution.

default The default images print on two pages, one image is a pattern of vertical lines and the other is a checkerboard.
reso=resolutionresolution is the resolution of the output in dots per inch (DPI). Possible values are 300 and 400.
mode=modemode is the print speed mode. This is the rate at which the test image is printed. Possible values are:

fast..Prints the test image at 1-minute intervals.

medium Prints the test image at 12-minute intervals.

extended Prints the test image at 30-minute intervals.

lpvitest Error Messages

The lpvitest error messages are listed below, with explanations and probable causes:
6000 Error occurred while attempting to obtain paper size

Probable_Cause(s):
a. <system_error_message> b. No tray installed
c. Printer out of paper
6001 Error occurred while attempting to fork a child
process

Probable_Cause(s):
a. <system_error_message>
6002 image in <name> raster file too big
6003 error=<number>

Probable_Cause(s):
a. <system_error_message>
8000 couldn't open <device_name>

Probable_Cause(s):
a. device does not exist b. device not configured correctly
8001 ioctl fail on <device_name>

Probable_Cause(s):
a. <system_error_message>
8002 Failed to obtain memory from malloc() system call

Probable_Cause(s):
a. system heavily loaded
8003 Couldn't open <file_name>

8004 Error occurred while reading raster file header
<value> for <device_name>

Probable_Cause(s):
a. The specified image raster file does not have the proper format
8005 Error occurred while loading image file <value> for
<device_name>

Probable_Cause(s):
a. The specified image raster file does not have the proper format
8006 Error occurred while writing to printer device

Probable_Cause(s):
a. <system_error_message>
8007 Error encountered while accessing printer device
<device_name>; Paper size: <value>,Counters: <value>, Print
Engine: <value>

8008 Error encountered while accessing printer device
<device_name>; Error code: <value>

Probable_Cause(s):
a. Error in main motor
8009 Error encountered while accessing printer device
<device_name>; Error code: <value>

Probable_Cause(s):
a. ROS out of order
8010 Error encountered while accessing printer device
<device_name>; Error code: <value>

a. Probable_Cause(s): b. FUSER out of order
8011 Error encountered while accessing printer device
<device_name>; Error code: <value>

Probable_Cause(s):
a. XERO failure
8012 Error encountered while accessing printer device
<device_name>; Error code: <value>

Probable_Cause(s):
a. Interlock open
8013 Error encountered while accessing printer device
<device_name>; Error code: <value>

Probable_Cause(s):
a. No tray installed
8014 Error encountered while accessing printer device
<device_name>; Error code: <value>

Probable_Cause(s):
a. No paper exists in selected tray
8015 Error encountered while accessing printer device
<device_name>; Error code: <value>

Probable_Cause(s):
a. Exit JAM
8016 Error encountered while accessing printer device
<device_name>; Error code: <value>

Probable_Cause(s):
a. Misfeed JAM
8017 Error encountered while accessing printer device
<device_name>; Error code: <value>

Probable_Cause(s):
a. Drum cartridge is nearly exhausted
8018 Error encountered while accessing printer device
<device_name>; Error code: <value>

Probable_Cause(s):
a. Deve module is nearly exhausted
8019 Error encountered while accessing printer device
<device_name>; Error code: <value>

Probable_Cause(s):
a. No Drum cartridge
8020 Error encountered while accessing printer device
<device_name>; Error code: <value>

Probable_Cause(s):
a. No Deve cartridge
8021 Error encountered while accessing printer device
<device_name>; Error code: <value>

Probable_Cause(s):
a. Drum cartridge exhausted
8022 Error encountered while accessing printer device
<device_name>; Error code: <value>

Probable_Cause(s):
a. Deve cartridge exhausted
8023 Timed out while accessing printer device <device_name>
8024 EIO error