Ricoh FAQ

Ricoh Employees and partners provide support via the Open Printing forums at: Forum: http://forums.openprinting.org/list.php?30 Printers from the Ricoh family and OEMs

You may also call your designated Ricoh Representative for support.

A complete list of supported Ricoh devices and corresponding PPD Files can be found at: http://www.openprinting.org/printer_list.cgi?make=Ricoh

Fundamentally all Ricoh devices that support PCL XL or PostScript should work, Not all Ricoh Devices support these Print Languages. Please consult your device specification. A quick check of supported languages can be made by printing the device configuration page.

If the device does support PCL-XL (PCL6) or PS your first step should be to look up your printer on openprinting.org. If it is listed, download the PostScript or PCL-XL PPD file (depending if you have the PostScript add-on installed or not) and set up your print queue with it. Note that you will need a recent foomatic-rip from openprinting.org (also for PostScript) and GhostScript in case of a PCL-XL printer.

If your printer is not listed on openprinting.org, look for a PS PPD file on the printer's driver CD (PostScript printers only). You may also have success with a PPD file designed for an earlier version of the same device. Finally, you can use the “Generic PostScript printer” or “Generic PCL-6/XL printer” PPD's on openprinting.org.

If you have any questions or concerns about which PPD to use for your device please post you question to the openprinting.org support forums, often Ricoh can provide a pre-release PPD file for your use, often before they are published to openprinting.org.

I single device can exist with multiple brand names. A specific model will function equally well regardless of the brand. The only technical difference is the sticker on the front and the name of the device.

For information about supported devices by Ricoh, see above.

For most Ricoh printers, supported printer languages are listed on the printer configuration page.

To print out configuration page:

• If your machine has a scanner with a control panel, push “User Tools / Counter” button, then click “Printer Features”, and select “Config. Page”.
• If your machine is a printer, push “Menu”, then “List/Test Print” and select “Config. Page”.

“Printer Language” is listed in the top section (System Reference) of the configuration page.

Also See FAQ "Does the Ricoh ... work?"

1. If your printer supports Postscript 3, you can download and extract the .PPD files from Windows XP driver.

2. If your printer supports Postscript, use Generic PostScript driver.

3. If your printer supports PCL-XL, use Generic PCL6/PCL XL driver.

4. If your printer supports PCL 5c, use Generic PCL 5c driver

5. If your printer supports PCL 5e, use Generic PCL 5e driver.

6. If the printer feature you need is not supported by Generic driver, post a question on Ricoh family forum

UserCodes in the Ricoh sense allow the user to send a job to the printer and have the printer track the print to a specific device configured code. These codes are configured in the printer in advance.

In some environments, printers are configured in a way that forces the user to send jobs with UserCodes or they cannot print. This is designed to allow the tracking of printed documents. This if often the case on Color and Black / White combination devices, where they want to allow Black / White printing, but track Color. If the printer is set to restrict based on user codes, and you send it a job without one, the printer will discard the job, with “Authentication Error”

There are three approaches to specify a UserCode.

• Save as default print preference (applies to every job you print)  lpoptions -l printername -o UserCode=xxx

*) When run as root, default settings of the print queue apply to all users and the preferences are stored in /etc/cups/lpoptions
*) When run as a regular user, default settings of the print queue apply to only that user and the preferences are stored in ~/.cups/lpoptions

• Hard code UserCode in the driver PPD file.
  Three sample user codes (1001, 1002 and 1003) are built into each PPD file. To replace a sample user code with your own, you can edit the PPD file manually, or run a simple shell command. > cat ricohppdfile.ppd | sed “s/1001/1234/g” > newricohppdfile.ppd This command replaces user code “1001” with “1234” and generates new PPD file newricohppdfile.ppd. You can then create printer queue with the generated PPD file.

• Specify the option when printing from command line  -o UserCode=xxxx

UserCode can be used in conjunction with JobType=LockedPrint/SamplePrint/DocServer. If you do not plan to use those features, leave JobType=Normal, LockedPrintPassword=None and DocServerPassword=None.

You MUST also install the latest foomatic-rip if you are using PCL-XL (pxlmono) driver, and your dirstribution is older than RHEL 5, SLED/S 11, Fedora Core 5, SUSE professional 10.2, Mandriva 2006.

To install the latest foomatic-rip, follow step 4 on http://www.openprinting.org/cups-doc.html

Locked Print jobs are print jobs that are submitted with a password. The printer will not print the job until operator releases it from the printer control panel. Locked Print differs from User Codes, by not printing the job until the user enters the password. User codes do not wait for user intervention for a print job with valid code. User codes can be used in conjunction with Locked Print.

To use the LockedPrint feature with Postscript PPD files, select JobType=LockedPrint, and provide LockedPrintPassword.
DocServerPassword must be set to None (if applicable)

To use the LockedPrint feature with PCL XL PPD files, select JobType=LockedPrint, and provide a Password.

There are three approaches to specify a LockedPrintPassword.

• Save as default print preference (applies to every job you print). For Postscript PPD files, use   lpoptions -l printername -o JobType=LockedPrint -o LockedPrintPassword=xxxx For PCL XL PPD files, use-o JobType=LockedPrint -o Password=xxxx


*) When run as root, default settings of the print queue apply to all users and the preferences are stored in /etc/cups/lpoptions
*) When run as a regular user, default settings of the print queue apply to only that user and the preferences are stored in ~/.cups/lpoptions

• Hard code LockedPrintPassword in the driver PPD file.
  Three sample locked print passwords (4001, 4002 and 4003) are built into each PPD file. To replace a sample locked print password with your own, you can edit the PPD file manually, or run a simple shell command. > cat ricohppdfile.ppd | sed “s/4001/1234/g” > newricohppdfile.ppd This command replaces locked print password “4001” with “1234” and generates new PPD file newricohppdfile.ppd. You can then create printer queue with the generated PPD file.

• Specify the option when printing from command line. For Postscript PPD files, use command line. -o JobType=LockedPrint -o LockedPrintPassword=xxxx. For PCL XL PPD files, use command line. -o JobType=LockedPrint -o Password=xxxx

You need to install the latest foomatic-rip if you are using dirstributions older than RHEL 5, SLED/S 11, Fedora Core 5, SUSE professional 10.2, Mandriva 2006.

To install the latest foomatic-rip, follow step 4 on http://www.openprinting.org/cups-doc.html

SamplePrint will print one copy of the submitted job and stores the job in the printer. You can walk up to the printer, proof reading the printout and specify additional copies from control panel. SamplePrint does not require a password. SamplePrint can be used in conjunction with User code.

To use SamplePrint feature with Postscript PPD files, select JobType=SamplePrint, and leave LockedPrintPassword=None, DocServerPassword=None. (if applicable)

To use SamplePrint feature with PCL XL PPD files, select JobType=SamplePrint, and leave Password=None.

You need to install the latest foomatic-rip if you are using dirstributions older than RHEL 5, SLED/S 11, Fedora Core 5, SUSE professional 10.2, Mandriva 2006.

To install the latest foomatic-rip, follow step 4 on http://www.openprinting.org/cups-doc.html

A print job with JobType=DocServer will be stored in the printer. User can later walk up to the printer and release the job with a password.
The difference between LockedPrint and DocServer is that the DocServer job will remain in the printer after printing vs LockedPrint job will be deleted automatically after printing.

To use DocServer feature with Postscript PPD files, select JobType=DocServer, and provide a DocServerPassword. LockedPrintPassword must be set to None.

To use DocServer feature with PCL XL PPD files, select JobType=DocServer, and provide a Password.

There're three approaches to specify DocServerPassword.

• Save as default print preference (applies to every job you print). For Postscript PPD files, use   -o JobType=DocServer -o DocServerPassword=xxxxFor PCL XL PPD files, use-o JobType=DocServer -o Password=xxxx

*) When run as root, default settings of the print queue apply to all users and the preferences are stored in /etc/cups/lpoptions
*) When run as a regular user, default settings of the print queue apply to only that user and the preferences are stored in ~/.cups/lpoptions

• Hard code DocServerPassword in the driver PPD file.
  Three sample doc server passwords (3001, 3002 and 3003) are built into each PPD file. To replace a sample doc server password with your own, you can edit the PPD file manually, or run a simple shell command. > cat ricohppdfile.ppd | sed “s/3001/1234/g” > newricohppdfile.ppd This command replaces doc server password “3001” with “1234” and generates new PPD file newricohppdfile.ppd You can then create printer queue with the generated PPD file.

• Specify the option when printing from command line. For Postscript PPD files, use  -o JobType=DocServer -o DocServerPassword=xxxx. For PCL XL PPD files, use  -o JobType=DocServer -o Password=xxxx.

You also need to install the latest foomatic-rip if you are using dirstributions older than RHEL 5, SLED/S 11, Fedora Core 5, SUSE professional 10.2, Mandriva 2006.

To install the latest foomatic-rip, follow step 4 on http://www.openprinting.org/cups-doc.html

A MFP can be configured to use the following authentication methods:

UserCode, Basic Authentication, Windows Authentication, LDAP Authentication, Integration Server Authentication.

Currently, only User Code is supported in Linux driver.

Do not use the Red Hat printer configuration tool for versions older than Fedora Core 6 / Red Hat Enterprise 5.
Follow steps here to install printer

Your printer does not support Postscript. Try PCL-XL driver or post questions here: http://forums.openprinting.org/list.php?30

Use command line or CUPS web interface.

• Command line installation.
  > su
# /usr/sbin/lpadmin -p replace_with_printer_name -E -v socket://replace_with_printer_ipaddress:9100 -P replace_with_ppd_name

• CUPS web interface.
  Open http://127.0.0.1:631/printers from your browser, click “Add Printer” and follow the steps.

We do not recommend/support distribution's own printer config tools. Beware of the bug in system-config-printer

• Generally socket://printeripaddress:9100 would work.
• http://printeripaddress:631/printer would work on newer printers.

• The pxlmono(PXL) driver does not support multiple copies. You need to enable collate option in the printing dialog. If you are using command line, use “-o collate=true”.

• Check /var/log/cups/error_log.
  Make sure LogLevel is set to Debug. “LogLevel debug”.

• How to change debug level?
  Edit /etc/cups/cupsd.conf and restart CUPS(usually with # /etc/init.d/cups restart)

• Check /tmp/foomatic-rip.log.
  run “foomatic-rip -v”. If it reports version 4.0 or later, Change /etc/foomatic/filter.conf and change “# debug: 0” to “debug: 1”. If it does not report foomatic-rip version or the version is older than 4.0, change “my $debug = 0” to “my $debug = 1” in foomatic-rip to enable logging.
  # vi /usr/lib/cups/filter/foomatic-rip (or # vi /usr/lib64/cups/filter/foomatic-rip on some 64-bit systems)

• Check print spool file Set “FileDevice Yes” in /etc/cups/cupsd.conf
  Restart CUPS
  # /etc/init.d/cups restart Create a queue with Device URI “file:/tmp/myspoolfile.rip”
  Print your job, check /tmp/myspoolfile.rip

Most likely a SC (service call) code is resulted from a hardware problem. You need to call service. For example:

• SC692 - CDIC GAVD Block I2C Bus Error/Communication Error Between Engine/Board & Print Controller
• SC76 - Belt sensor error
• SC305 - PCU-side quenching lamp has come loose from bracket
• SC738 - finisher lift motor home position sensor error. Either the sensor is broken, or your finisher shift tray is pushed up too high.

• If your printer supports Postscript, you should download the full-featured Mac OS X driver from Ricoh website. UserCode feature, however, is only supported by the Mac OS X driver for the latest models (machine released in 2007 or so). If you have an older printer, you can safely use the driver for its successor model. (Just need to make sure not to mix B/W models with Color models. Printer will not be damaged, the worst could happen is you cannot control the finishers or extra paper trays.)
• If your printer supports PCL-XL, you should follow the instructions for pxlmono for Mac OS X. It includes the installation packages for PPD files, foomatic-rip and Ghostscript. To support UserCode, you need to use text editor to edit the PPD file (either from pxlmonoo Mac package or download directly from this website) and search and replace one of the sample user codes (1001, 1002 or 1003) with your own. You can then install the PPD file using printer setup tool on Mac OS X.
• if your printer only supports PCL5, you have to use the Generic PCL 5 driver from this site. You must also follow these instructions to install HPIJS, foomatic-rip and Ghostscript. If you want to use user code feature, search and post on the forum for help.

That is a bug. http://forums.linuxfoundation.org/read.php?34,1386. There're two approaches to fix it, whatever sounds easier to you.

• Download and install the latest version of foomatic-rip package.
• Download the latest PCL-XL driver again, they were updated on Dec 17, 2007, which includes a workaround for that problem.

You can post your request for Mac OS X LAN Fax drivers in the forum.

 HoldPrint, StoredPrint, StoreAndNormalPrint is not supported at the current time. Post a feature request on the forum

The features provide abilities to enter LockedPrintPassword, DocServerPassword and UserCode in the GTK+ print dialog and the CUPS1.4 web interface.

In order to use these features in GTK+ print dialog, you need to have GTK+ 2.10 or newer, Foomatic3.43.2.14 or newer. In addition, you should use the latest versions of the applications which are using the GTK+ 2.10 print dialog.

For instance, Firefox3.0 or newer, Gedit 2.22 or newer and Evince, they are pointing to the GTK+ 2.10 print dialog.

In order to use these features in CUPS1.4 web interface, you need to install CUPS1.4 and Foomatic4.0 or newer.

A Power user, Filippo has created a PPD file which supports almost all paper sizes, with the possible limitation of manual feed only. forums.linux-foundation.org/read.php . Thanks Fillippo for the devotion to make Linux Driver better!