| F0-02 | A fatal error has occurred. | |
| F0-02 | A core error has occurred. | |
| F0-03 | This kind of error occurs when a controller module (any) generates an error and the error number is undefined in the error message database. | |
| F0-06 | This fault occurs when the user attempts to create a new print line and the Stampa PC is in the process of a system startup. | |
| F0-07 | Register error on trace module. | |
| F0-08 | This fault will only occur at startup and it will only occur if the core parameters database has been corrupted. | |
| F0-09 | Event object creation error. | |
| F0-0A | Pipe object creation error | |
| F0-0B | Console object creation error | |
| F0-0C | Thread object creation error | |
| F0-0D | Management error in parameter file | |
| F0-0E | A memory exception can occur for any one of the reasons that follow: | |
| F0-0F | Unknown parameter | |
| F0-10 | Pipe object connection error | |
| F0-11 | Pipe object error during connection | |
| F0-12 | Unknown operation | |
| F0-13 | Unknown state | |
| F0-14 | Pipe object connection setting error | |
| F0-15 | Pipe object disconnection error | |
| F0-16 | Pipe transaction still pending | |
| F0-17 | Invalid parameter size | |
| F0-18 | Pipe transaction error | |
| F0-19 | Copy post message failed | |
| F0-1B | VPL manager creation failed | |
| F0-1C | Thread object creation error | |
| F0-1D | Missing revision for main module. | |
| F0-1E | file version not found. | |
| F0-1F | Invalid revision for main module. | |
| F0-20 | Missing revision for ACS generator module. | |
| F0-21 | Invalid revision for ACS generator module. | |
| F0-22 | Missing revision for ACS module. | |
| F0-23 | Invalid revision for ACS module. | |
| F0-24 | Missing revision for base module. | |
| F0-25 | Invalid revision for base module. | |
| F0-26 | Missing revision for BNW IPDS generator module. | |
| F0-27 | Invalid revision for BNW IPDS generator module. | |
| F0-28 | Missing revision for CES VPL module. | |
| F0-29 | Invalid revision for CES VPL module. | |
| F0-2A | Missing revision for MOD module. | |
| F0-2B | Invalid revision for MOD module. | |
| F0-2C | Missing revision for color module. | |
| F0-2D | Invalid revision for color module. | |
| F0-2E | Missing revision for core module. | |
| F0-2F | Invalid revision for core module. | |
| F0-30 | Missing revision for engine module. | |
| F0-31 | Invalid revision for engine module. | |
| F0-32 | Missing revision for IPDS input module. | |
| F0-33 | Invalid revision for IPDS input module. | |
| F0-34 | Missing revision for TCPIP API module. | |
| F0-35 | Invalid revision for TCPIP API module. | |
| F0-36 | Missing revision for IPDS output module. | |
| F0-37 | Invalid revision for IPDS output module. | |
| F0-38 | Missing revision for PPE module. | |
| F0-39 | Invalid revision for PPE module. | |
| F0-3A | Missing revision for Stampa VPL module. | |
| F0-3B | Invalid revision for Stampa VPL module. | |
| F0-3C | Missing revision for video generator module. | |
| F0-3D | Invalid revision for video generator module. | |
| F0-3D | Invalid revision for viewer generator module. | |
| F0-3E | Missing revision for viewer generator module. | |
| F0-40 | Missing revision for viewer module. | |
| F0-41 | Invalid revision for viewer module. | |
| F0-42 | Missing revision for channel API module. | |
| F0-43 | Invalid revision for channel API module. | |
| F0-44 | Missing revision for Hitachi engine module. | |
| F0-45 | Invalid revision for Hitachi engine module. | |
| F0-46 | Missing revision for RAIMPRO module. | |
| F0-47 | Invalid revision for RAIMPRO module. | |
| F0-48 | Missing revision for trace log in module. | |
| F0-49 | Invalid revision for trace log in module. | |
| F0-4A | Revision process failure | |
| F0-4B | Calibration parameter creation error | |
| F0-4C | Handle queued message exception | |
| F0-4D | Exception on adding message | |
| F0-4E | Missing revision for perf collector API module. | |
| F0-4F | Missing revision for VPL module. | |
| F0-50 | Invalid revision for VPL module. | |
| F0-51 | PPE object creation error. | |
| F0-52 | Missing revision for controller module. | |
| F0-53 | Invalid revision for controller module. | |
| F0-54 | Server pipe creation error. | |
| F0-55 | Client pipe creation error. | |
| F0-56 | The Stampa controller and/or Client has experienced an internal software error. | |
| F0-57 | Connection failure with other printer. | |
| F0-58 | Data transmission failed. | |
| F0-59 | Client server and PLM error 3: action to data master. | |
| F0-5C | Client server and PLM error 6: action to data upstream. | |
| F0-5D | Engine type differences detected. | |
| F0-5E | Client server: incompatible versions | |
| F0-5F | Client server: incompatible revisions | |
| F0-60 | Client server and PLM error 10: wrong device. | |
| F0-61 | Undefined device type. | |
| F0-62 | Undefined device type. | |
| F0-63 | No local printer in the line. | |
| F0-64 | Client server and PLM error 14: to controller. | |
| F0-65 | Client server and PLM error 15: to GUI. | |
| F0-66 | Client server and PLM error 16: to line. | |
| F0-67 | Inconsistent resolution on both printers. | |
| F0-68 | Inconsistent page length on both printers. | |
| F0-69 | Inconsistent page width on both printers. | |
| F0-6A | This fault can occur, for example, if you select a simplex line on the downstream printer when a duplex line is selected on the upstream printer. This fault can also occur if the onboard PLB ID is not correctly assigned. | |
| F0-6B | The timing signals between the controller and the PLB are out of synchronisation. This prevents the PLB from being able to control the synchronisation between devices. | |
| F0-6C | Device selection error. | |
| F0-6D | No local PLB box detected. | |
| F0-6E | Segmentation time-out. This error can occur if the print line is selected before the components of the print line are all in the ready state at power up. | |
| F0-6F | The problem occurs in the situation where an attempt is made to connect a controller which has been configured in stand alone only, with another one. | |
| F0-70 | The operator is attempting to configure a duplex feature for a simplex line. | |
| F0-72 | The duplex print line is not aligned. | |
| F0-73 | Client sever and PLM error 29: to synchro. | |
| F0-73 | Database synchronization error. | |
| F0-74 | Cannot access database. | |
| F0-75 | Cannot find database. | |
| F0-76 | Incorrect database version. | |
| F0-78 | Database update failure. | |
| F0-79 | Database update warning. | |
| F0-82 | This fault only occurs when the system is configured in duplex or multiplex mode. All engines in a print line must be configured to the same paper feed mode (i.e. pinless or pinfeed). This fault is raised if the engines are configured inconsistently (e.g. The first printer is configured pinless while the second is configured pinfeed or vice versa). | |
| F0-83 | Page tracking error. | |
| F0-84 | This fault only occurs when the tractors are not set to match the paper feed mode selected in the application. | |
| F0-85 | Get engine characteristics error. | |
| F0-86 | Inconsistent paper oversize. | |
| F0-8A | When the line has been set aligned after a print alignment using pinless paper, the printer will synchronize the top of form between the printers. The error occurs when the sensor fails to read the mark. Ensure that the registration mark sensor is clean and correctly positioned. | |
| F0-8B | Any feed & pin feed inconsistent with FULL VPA. | |
| F0-8C | Inconsistent PLB cable. | |
| F0-8D | Invalid MICR line configuration. | |
| F0-8E | Unauthorized MICR use. | |
| F0-8F | Controller version mismatch. | |
| F0-90 | Pinless alignment error. | |
| F0-91 | Stacker not available.The fault occurs when the START button is pressed and the controller cross checks the job and print line configuration. If the print line is not configured with a stacker and the selected line does not have a post-processing device selected, the fault will occur. | |
| F0-92 | This fault occurs when the START button is pressed on a duplex print line and the controller detects that the two printers are not set to the same paper speed. | |
| F0-93 | The fault occurs when the start button is pressed on a duplex print line and the controller detects that the two printers are not set to the same paper feed configuration. (i.e. pinless or pinfeed). This is a check of the internal hardware switches (different from the software check of F0-82) | |
| F0-94 | IOT type mismatch. | |
| F0-95 | Print position check ongoing. | |
| F0-96 | The fault occurs when the Print Line Manager (PLM) attempts to communicate with the FTP (File Transfer Protocol) manager and the communication fails (e.g. buffers full, invalid messages, etc.). | |
| F0-97 | This fault occurs when the Print Line Manager cannot create a log file (i.e. hard drive full, etc.). | |
| F0-98 | This fault occurs when the Print Line Manager (PLM) attempted to create a Log file and it already exists on the FTP server. The PLM notifies the user with the message that follows: | |
| F0-99 | This fault occurs when the Print Line Manager (PLM): | |
| F0-9A | MICR feature not installed. | |
| F0-9B | MICR missing licence. | |
| F0-9C | MICR housing not supported on downstream printer. | |
| F0-9D | MICR housing not supported on pinless mode. | |
| F0-9E | Two duplex printers not allowed in the line. | |
| F0-9F | Client Server and PLM error 31: to PSIP. | |
| F0-A0 | Paper motion state machine creation error. | |
| F0-A1 | Enable/disable SNMP agent error. | |
| F0-A2 | SNMP Agent Transaction Error. A communication error has occurred within the SNMP. This is an internal software communication failure. | |
| F0-A3 | The user attempts to enable SNMP, however the feature is not installed on the controller, or the feature is corrupt and the attachment cannot be made. | |
| F0-A3 | SNPM has started, but for some reason the SNMP agent cannot be contacted. | |
| F0-A4 | This occurs when the user attempts to use the SNMP feature and the controller checks the links from the controller to the remote site. The controller finds the links are not available. There are 2 links (A & B). A is always defined, B is optional to be defined. This error typically occurs when link B has been defined, but is not physically connected. | |
| F0-A5 | This occurs when the user attempts to use the SNMP feature the controller checks the ports from the controller to the remote site and the port definition is invalid. | |
| F0-A6 | This occurs when the user attempts to use the SNMP feature and the controller checks the IP address for the remote server and finds it is incorrect. The connection cannot be made. | |
| F0-A7 | This occurs when the user attempts to use the SNMP feature the controller checks the subnet mask for the remote server and finds it is incorrect. The connection cannot be made | |
| F0-A8 | This occurs when the user attempts to use the SNMP feature and the controller checks the gateway for the remote server and finds it is incorrect. The connection cannot be made | |
| F0-A9 | This occurs when the same IP address has been defined for both job communication and remote server communications and the user tries to use the two TCP/IP attachments at the same time. | |
| F0-AA | This is an internal software error. | |
| F0-AB | This fault occurs when the user attempts to use the SNMP feature and the Stampa controller checks the link(s) from the controller to the remote site. The controller finds the link(s) are not available. The link(s) are there and correctly defined, but are unavailable. | |
| F0-AC | This is an internal software error. | |
| F0-AD | Missing revision for SNMP service module. | |
| F0-AE | This fault occurs when the Stampa controller issues a communication check to the SNMP agent and fails to receive a response. | |
| F0-AF | Get controller characteristics error. | |
| F0-B0 | Missing revision for Fuji Xerox engine model. | |
| F0-B1 | This is a generic error. The fault occurs if there is a problem with the communication between the SNMP agent and the remote server, or there exists an internal error in the SNMP agent. | |
| F0-C1 | Invalid/Missing package revision. | |
| F0-C3 | SNMP feature not installed. | |
| F0-C4 | Missing revision for DAO module. | |
| F0-C5 | Invalid revision for DAO IN module. | |
| F0-C6 | Local engine initialisation failure. | |
| F0-C7 | No IOT interface PWB detected. | |
| F0-E0 | Duplicate PLB local ID. | |
| F0-E1 | Inconsistent duplex print quality. | |
| F0-E2 | Print quality not supported with current resolution. |
