StClass:
STCLASS_OK No error
STCLASS_ERROR_COMM
Error of the CSCWCOMM.DLL
StCode:
2000FE06 COMM_INVALID_PROTOCOL Reason:
The COMM reports an invalid specification for the protocol.
If the error occurs with the use of LPT, then the parallel port does not meet the requirements for the selected transfer mode.
Application:
Use the protocol type from the COMM.H definition file when calling "CscV24Init". Measure:
If the error occurs with the use of LPT, then you have to check the port configuration (e.g. for the printers TH97 and ND97 the parallel port is to be configured for ECP in the BIOS.
2000FE07 COMM_WRITE_CANCELED Reason:
A COMM WRITE command is cancelled by the user. No entry is made in the error log. 2000FE08 COMM_WRITE_TIMEOUT
Reason:
A COMM WRITE command could not be executed in the specified monitoring time. Application:
Repeat the command if necessary. Measure:
COMM mutiplexer
2000FE09 COMM_READ_TIMEOUT Reason:
A COMM READ command could not be executed in the specified monitoring time. - Line connection, power supply not okay.
- Device faulty.
- Software configuration faulty. Application:
Repeat the command if necessary. Measure:
Check the line connection, power supply.
Check device (selftest, light-emitting diode, test program). 2000FE0A COMM_READ_CANCELED
Reason:
A COMM READ command is cancelled by the user. No entry is made in the error log. 2000FE0B COMM_PARITY_ERROR
Reason:
The COMM driver reports a parity error. The received data block is invalid. Measure:
If the error recurs, check the hardware. 2000FE0C COMM_GENERAL_FAILURE
Reason:
The COMM driver reports a general error. Measure:
Check the hardware and report the error log of this entry to Service. 2000FE0F COMM_PROTOCOL_VIOLATION
Reason:
The peripheral device did not answer in a specified monitoring time as expected. Reasons may be: a) Peripheral not attached or switched off
b) Peripheral was switched off while a connection was open c) Cable or peripheral hardware problem
Application:
Close the device and open it again. Measure:
COMM mutiplexer
2000FE13 COMM_CHAN_NOT_INITIALIZED Reason:
The channel was not initialized. Application:
Check the application program. Measure:
Initialize the channel before using it. 2000FE14 COMM_ACCESS_DENIED
Reason:
Access to port denied. The parallel port is already assigned exclusively by an appropriate driver command (e.g. IOCTL_PAR_CSC_SELECT_ECP_RESERVE).
Measure:
Fix the configuration or application error. 2000FE16 COMM_BREAK
Reason:
The COMM driver reports a break. Measure:
If the error recurs, check the hardware. 2000FE7A COMM_OVERRUN_ERROR
Reason:
The COMM driver reports a overrun error. Measure:
Check the hardware and report the error log of this entry to Service. 2000FE7B COMM_FRAMING_ERROR
Reason:
The COMM driver reports a framing error. Measure:
COMM mutiplexer
2000FE85 COMM_DRIVER_OPEN_FAILED Reason:
The COMM driver could not be opened. Measure:
Check serial device entry in Registry/CSC.INI. Check if additional COMM drivers are installed (e.g. "ROCKET.SYS"). Check COMM Hardware.
2000FE89 COMM_INVALID_PTXDATA Reason:
The pointer "pTxData" is illegal. Application:
Transfer a legal pointer to the multiplexer in the application program. 2000FE8B COMM_INVALID_OPEN_SPEC
Reason:
The called function is invalid for the used CscCommOpen specification. Application:
Use the definition in the COMM.H definition file. 2000FE8C COMM_NO_STX
Reason:
The peripheral device does not return an STX. Application:
Repeat the command and if necessary initialize the device again beforehand. Measure:
Check the hardware. 2000FE8D COMM_NO_ETX
Reason:
The peripheral device does not return an ETX. Application:
Repeat the command and if necessary initialize the device again beforehand. Measure:
COMM mutiplexer
2000FE8E COMM_INVALID_BLK_LEN Reason:
The expected block length does not agree with the transmitted block length. Application:
Repeat the command and if necessary initialize the device again beforehand. Measure:
Check the hardware.
2000FE8F COMM_INVALID_BLK_ID Reason:
The block ID is invalid. Application:
Repeat the command and if necessary initialize the device again beforehand. Measure:
Check the hardware.
2000FE90 COMM_INVALID_DEV_ID Reason:
The received device ID does not agree with the transmitted device ID. Application:
Repeat the command and if necessary initialize the device again beforehand. Measure:
Check the hardware.
2000FE91 COMM_INVALID_COMMAND Reason:
The received command specification does not agree with the transmitted command specification. Application:
Repeat the command and if necessary initialize the device again beforehand. Measure:
COMM mutiplexer
2000FE92 COMM_INVALID_ACK_TYPE Reason:
The received acknowledge type is invalid (only ACK and NAK are valid). Application:
Repeat the command and if necessary initialize the device again beforehand. Measure:
Check the hardware.
2000FE93 COMM_MAX_TX_RETRIES Reason:
The maximum number of repeat transmissions has been reached. Application:
Repeat the command and if necessary initialize the device again beforehand. Measure:
Check the hardware.
2000FE94 COMM_MAX_RX_RETRIES Reason:
The maximum number of receive repeats has been reached. Application:
Repeat the command and if necessary initialize the device again beforehand. Measure:
Check the hardware.
2000FE95 COMM_PROTOCOL_TX_TIMEOUT Reason:
The total protocol monitoring time during transmission has been exceeded. Application:
Repeat the command and if necessary initialize the device again beforehand. Measure:
COMM mutiplexer
2000FE96 COMM_PROTOCOL_RX_TIMEOUT Reason:
The total protocol monitoring time during receive has been exceeded. Application:
Repeat the command and if necessary initialize the device again beforehand. Measure:
Check the hardware.
2000FE97 COMM_PROTOCOL_POLL_TIMEOUT Reason:
The busy time transmitted from the peripheral device is exceeded. Application:
Repeat the command and if necessary initialize the device again beforehand. Measure:
Check the hardware.
2000FE98 COMM_PROTOCOL_CANCELED Reason:
The protocol was cancelled. Application:
Repeat the command and if necessary initialize the device again beforehand. Measure:
Check the application program. 2000FE9C COMM_INVALID_TXDATA_LEN
Reason:
The length in TxData is 0 (zero). Application:
Specify a legal length.
2000FE9D COMM_CSCISO_DLL_NOT_FOUND Reason:
The CSCWISO.DLL could not be found in the PATH (normally <CSCROOT>\DLL). Measure:
COMM mutiplexer
2000FE9E COMM_CSCISO_DLL_OPEN_FAILED Reason:
The CSCWISO.DLL could not be opened. Measure:
Report the error log of this entry to Service. 2000FE9F COMM_CSCUSB_DLL_NOT_FOUND
Reason:
The CSCWUSB.DLL could not be found in the PATH (normally <CSCROOT>\DLL). Measure:
Check whether CSCWUSB.DLL is in the PATH (normally <CSCROOT>\DLL). 2000FEA0 COMM_CSCUSB_DLL_OPEN_FAILED
Reason:
The CSCWUSB.DLL could not be opened. Measure:
Report the error log of this entry to Service. 2000FEB0 COMM_INVALID_DRIVER_CONF
Reason:
A configured driver (COM, CH, LPT) gets not the state running. Measure:
Report the error log of this entry to Service. 2000FEE0 COMM_P2_TX_NO_RESP_ON_ENQ
Reason:
The command could not be transmitted because the peripheral device did not answer. Measure:
Check the hardware.
2000FEE1 COMM_P2_TX_INVALID_RESP_ON_ENQ Reason:
The command could not be transmitted because the peripheral device did not answer as expected. Application:
COMM mutiplexer
2000FEE2 COMM_P2_TX_NAK_RECEIVED Reason:
The command could not be transmitted because the peripheral device announced that it is busy. Application:
Repeat the command and if necessary initialize the device again beforehand. Measure:
Check the hardware if necessary.
2000FEE3 COMM_P2_TX_NO_VALID_RESP_ON_TEXT Reason:
The command could not be completely transmitted because the peripheral device did not answer as expected.
Application:
Initialize the device and repeat the transaction. Measure:
Check the hardware.
2000FEE4 COMM_P2_TX_MAX_RETRIES Reason:
The command could not be completely transmitted because the maximum number of repeat transmissions has been reached.
Application:
Initialize the device and repeat the transaction. Measure:
Check the hardware.
2000FEE5 COMM_P2_TX_ABORTED Reason:
The command could not be completely transmitted because the device asked for the termination of the transmission.
Application:
Repeat the command and if necessary initialize the device again beforehand. Measure:
COMM mutiplexer
2000FEE6 COMM_P2_RX_CMD_TIMEOUT Reason:
The peripheral device did not answer in the specified monitoring time of the command. Application:
Repeat the command and if necessary initialize the device again beforehand. Measure:
Check the hardware.
2000FEE7 COMM_P2_RX_ISO_TIMEOUT Reason:
The response of the device has not been completely received because one of the internal protocol monitoring times has been exceeded.
Application:
Initialize the device and repeat the transaction. Measure:
Check the hardware.
2000FEE8 COMM_P2_RX_INVALID_HEADER Reason:
The header of the response is invalid. Application:
Repeat the command and if necessary initialize the device again beforehand. Measure:
Check the hardware.
2000FEE9 COMM_P2_RX_INVALID_DEVICE_ID Reason:
The received device ID does not agree with the transmitted device ID. Application:
Repeat the command and if necessary initialize the device again beforehand Measure:
COMM mutiplexer
2000FEEA COMM_P2_RX_INVALID_CMD_ID Reason:
The received command ID does not agree with the transmitted device ID. Application:
Repeat the command and if necessary initialize the device again beforehand. Measure:
Check the hardware.
2000FEEB COMM_P2_RX_INVALID_CMD_SPEC Reason:
The received command specification does not agree with the transmitted command specification. Application:
Repeat the command and if necessary initialize the device again beforehand Measure:
Check the hardware.
2000FEEC COMM_P2_RX_CRC_ERROR Reason:
The response of the device has not been completely received because one of the transmission blocks could not be received without faults.
Application:
Initialize the device and repeat the transaction Measure:
Check the hardware.
2000FEED COMM_P2_NO_CMD_ACTIVE Reason:
A cancel command has been called while no command was active. Application:
Call the cancel command only when a cancelable command is active. 2000FEEF COMM_P2_CMD_NOT_CANCABLE
Reason:
A cancel command has been called while a not cancelable command was active. Application:
COMM mutiplexer
2000FEF0 COMM_P2_CMD_STILL_ACTIVE Reason:
The command could not be executed because another command was still active Application:
Repeat the command and if necessary initialize the device again beforehand. 2000FEF1 COMM_P2_CMD_CANCELLED
Reason:
The command was aborted by the user. No entry will be made in the error log. 2000FEF2 COMM_P2_CANCEL_STILL_ACTIVE
Reason:
The command could not be executed because a cancel command was still active. Application:
Repeat the command and if necessary initialize the device again beforehand. 2000FEF3 COMM_P2_CANCEL_NOT_SUCCESSFUL
Reason:
A cancel command could not be executed. Application:
Repeat the cancel command.
2000FEF4 COMM_P2_TX_CANCEL_TIMEOUT Reason:
The command could not be cancelled because an internal monitoring time has been exceeded. Application:
Initialize the device and repeat the transaction. Measure:
Check the hardware.
2000FEF5 COMM_P2_SYNCHRONISATION_ERROR Reason:
Internal error within the CSCWISO.DLL. Measure:
IEEE 1394
StClass:
STCLASS_OK No error
STCLASS_ERROR_1394 Error of the CSCW1394.DLL
StCode:
2000FE09 I1394_READ_TIMEOUT Reason:
A IEEE 1394 read command could not be executed in the specified monitoring time. Application:
Repeat the command if necessary. Measure:
Check the hardware if necessary. 2000FE0A I1394_READ_CANCELED
Reason:
A IEEE 1394 read command is cancelled by the user. No entry is made in the error log. 2000FE89 I1394_INVALID_PDATA
Reason:
The pointer "pData" is illegal. Application:
Transfer a legal pointer to the device handler in the application program. 2000FE9C I1394_INVALID_DATASIZE
Reason:
The length in DataSize is 0 (zero). Application:
IEEE 1394
2000FE9D I1394_TS_DLL_NOT_FOUND Reason:
The I1394_TS.DLL could not be found in the PATH. Normally <CSCROOT>\DLL. Measure:
Check whether I1394_TS.DLL is in the PATH. Normally <CSCROOT>\DLL. 2000FE9E I1394_TS_DLL_OPEN_FAILED
Reason:
The I1394_TS.DLL could not be opened. Measure:
Report the error log of this entry to Service. 2000FE9F I1394_UB_DLL_NOT_FOUND
Reason:
The I1394_UB.DLL could not be found in the PATH. Normally <CSCROOT>\DLL. Measure:
Check whether I1394_UB.DLL is in the PATH. Normally <CSCROOT>\DLL. 2000FEA0 I1394_UB_DLL_OPEN_FAILED
Reason:
The I1394_UB.DLL could not be opened. Measure:
Report the error log of this entry to Service. 200A0020 I1394_ERROR_TIMEOUT
Reason:
Internal driver error: Driver responded timeout status. Application:
Repeat the command if necessary. Measure:
IEEE 1394
200A0100 I1394_ERROR_NO_MEMORY Reason:
Internal driver error: Out of memory. Application:
Repeat the command if necessary. Measure:
Check the hardware if necessary.
200A0210 I1394_ERROR_INVALID_DEVICE_STATE Reason:
Internal driver error: Device is not in working state. Application:
Repeat the command if necessary. Measure:
Check the hardware if necessary.
200A0300 I1394_ERROR_INVALID_PARAMETER Reason:
Internal driver error: Invalid parameter. Application:
Repeat the command if necessary. Measure:
Check the hardware if necessary.
200A0305 I1394_ERROR_INVALID_BUFFER_SIZE Reason:
Internal driver error: Size of buffer is invalid. Application:
Repeat the command if necessary. Measure:
IEEE 1394
200A8001 I1394_ERROR_DEVICE_NOT_FOUND Reason:
Internal driver error: Device not found. Application:
Repeat the command if necessary. Measure:
Check the hardware if necessary.
200A8010 I1394_ERROR_NO_SUCH_DEV_INSTANCE Reason:
Internal driver error: No such device instance. The IEEE 1394 driver could not be opened. Application:
Repeat the command if necessary. Measure:
Check device entry in Registry. Check if IEEE 1394 drivers are installed. Check IEEE 1394 Hardware. Check the hardware if necessary.
200B0100 I1394_ERROR_ABORTED Reason:
Internal driver error: The operation was cancelled/aborted by the miniport because it could not be performed (for example there is a critical hardware error that halted the adapter, or the miniport is unloading).
Application:
Repeat the command if necessary. Measure:
Check the hardware if necessary. 200B0200 I1394_ERROR_ADAPTER
Reason:
Internal driver error: A non-critical error occurred on the adapter that caused the request to fail. The error affected only this operation and the adapter is otherwise functioning normally.
Application:
Repeat the command if necessary. Measure:
IEEE 1394
200B0250 I1394_ERROR_ALREADY_OPEN Reason:
Internal driver error: The application has already opened the specified adapter. Application:
Repeat the command if necessary. Measure:
Check the hardware if necessary. 200B0270 I1394_ERROR_BR_LIMIT
Reason:
Internal driver error: The operation was cancelled because more bus resets occurred than the operation could tolerate.
Application:
Repeat the command if necessary. Measure:
Check the hardware if necessary. 200B0300 I1394_ERROR_BUS_RESET
Reason:
Internal driver error: The operation was cancelled because a 1394 bus reset took place. For example a queued asynchronous transaction must be failed because the target NodeID might not be the same after the bus reset.
Application:
Repeat the command if necessary. Measure:
Check the hardware if necessary. 200B0350 I1394_ERROR_CONFLICT
Reason:
Internal driver error: The operation could not be completed because there was a conflict. Application:
Repeat the command if necessary. Measure:
IEEE 1394
200B0370 I1394_ERROR_CRC Reason:
Internal driver error. Application:
Repeat the command if necessary. Measure:
Check the hardware if necessary. 200B0400 I1394_CRITICAL_ADAPTER_ERROR
Reason:
Internal driver error: A critical error occurred on the adapter that caused the request to fail. The adapter is not fully functional and the class driver should take corrective actions (closing an isochronous channel, resetting the adapter etc).
Application:
Repeat the command if necessary. Measure:
Check the hardware if necessary. 200B0500 I1394_ERROR_DEVICE_BUSY
Reason:
Internal driver error: The operation requested failed because the local adapter is busy. Application:
Repeat the command if necessary. Measure:
Check the hardware if necessary. 200B0572 I1394_ERROR_DMA
Reason:
Internal driver error. Application:
Repeat the command if necessary. Measure:
IEEE 1394
200B0600 I1394_DRIVER_INTERNAL_ERROR Reason:
Internal driver error: The driver detected a bug in its execution logic (through assertions or sanity checks), and could not complete the operation.
Application:
Repeat the command if necessary. Measure:
Check the hardware if necessary.
200B0639 I1394_ERROR_DUPLICATE_CHANNEL Reason:
Internal driver error: The isochronous channel number is already in use. Application:
Repeat the command if necessary. Measure:
Check the hardware if necessary. 200B0645 I1394_ERROR_FIFO_OVERRUN
Reason:
Internal driver error: An isochronous operation failed because of a FIFO overrun. Application:
Repeat the command if necessary. Measure:
Check the hardware if necessary. 200B0658 I1394_ERROR_FIFO_UNDERRUN
Reason:
Internal driver error: An isochronous operation failed because of a FIFO underrun. Application:
Repeat the command if necessary. Measure:
IEEE 1394
200B0671 I1394_ERROR_GAP_COUNT Reason:
Internal driver error: The class driver detected that not all the self?ID packets that were transmitted after the last bus reset contained the same value in their gap_count field.
Application:
Repeat the command if necessary. Measure:
Check the hardware if necessary.
200B06B2 I1394_ERROR_INCORRECT_RESPONSE Reason:
Internal driver error: An outgoing response packet is not valid. Application:
Repeat the command if necessary. Measure:
Check the hardware if necessary.
200B0700 I1394_ERROR_INSUFFICIENT_RESOURCES Reason:
Internal driver error: An operation failed due to some lack of resources other than memory. Application:
Repeat the command if necessary. Measure:
Check the hardware if necessary.
200B0900 I1394_ERROR_INVALID_CHANNEL_TYPE Reason:
Internal driver error: The operation requested is not applicable to the channel type. Application:
Repeat the command if necessary. Measure:
IEEE 1394
200B0A00 I1394_ERROR_INVALID_CHANNEL_STATE Reason:
Internal driver error: The operation requested is not possible at the channel's current operating state.
Application:
Repeat the command if necessary. Measure:
Check the hardware if necessary. 200B0C00 I1394_ERROR_INVALID_HANDLE
Reason:
Internal driver error: The miniport adapter handle passed to the miniport does not identify one of its adapters.
Application:
Repeat the command if necessary. Measure:
Check the hardware if necessary.
200B0D00 I1394_ERROR_INVALID_ISOCHRONOUS_BUFFERS Reason:
Internal driver error: A validation check on a number of isochronous buffers failed. Application:
Repeat the command if necessary. Measure:
Check the hardware if necessary. 200B0D47 I1394_ERROR_INVALID_OFFSET
Reason:
Internal driver error: The 1394 address space offset specified was above the highest 1394 offset (0xFFFFFFFFFFFF), or the address range specified spanned the highest 1394 offset.
Application:
Repeat the command if necessary. Measure:
IEEE 1394
200B0F00 I1394_ERROR_INVALID_REQUEST Reason:
Internal driver error: The request passed to the miniport was invalid, and there was no other more specific error status for this operation.
Application:
Repeat the command if necessary. Measure:
Check the hardware if necessary.
200B0F50 I1394_ERROR_INVALID_RESPONSE Reason:
Internal driver error: An response packet was received that was invalid for the corresponding transaction request, or the class driver detected that an outgoing response is not complying with the rules set by the standard with regards to header information (destination NodeID, transaction code, data length).
Application:
Repeat the command if necessary. Measure:
Check the hardware if necessary. 200B0F73 I1394_ERROR_LOCK_FAILED
Reason:
Internal driver error. Application:
Repeat the command if necessary. Measure:
Check the hardware if necessary. 200B1070 I1394_ERROR_NOT_FOUND
Reason:
Internal driver error: The requested item was not found.