These errors are mainly of interest for developers of the CapiSuite core. If you're a user, you normally won't need them.
These values are only warnings and may appear in the extensive CapiSuite log in messages from the CAPI.
0000 - No error, request accepted
0001 - NCPI not supported by current protocol, NCPI ignored
0002 - Flags not supported by current protocol, flags ignored
0003 - Alert already sent by another application
These errors may appear when the application starts and mostly indicate problems with your driver installation.
1001 - Too many applications.
1002 - Logical Block size too small; must be at least 128 bytes.
1003 - Buffer exceeds 64 kbytes.
1004 - Message buffer size too small, must be at least 1024 bytes.
1005 - Max. number of logical connections not supported.
1006 - reserved (unknown error).
1007 - The message could not be accepted because of an internal busy condition.
1008 - OS Resource error (out of memory?).
1009 - CAPI not installed.
100A - Controller does not support external equipment.
100B - Controller does only support external equipment.
These errors are really internal: they're raised if the application calls CAPI in a wrong way. If they occur, it's usually a bug which you should tell the CapiSuite developers.
1101 - Illegal application number.
1102 - Illegal command or subcommand, or message length less than 12 octets.
1103 - The message could not be accepted because of a queue full condition.
1104 - Queue is empty.
1105 - Queue overflow: a message was lost!!
1106 - Unknown notification parameter.
1107 - The message could not be accepted because on an internal busy condition.
1108 - OS resource error (out of memory?).
1109 - CAPI not installed.
110A - Controller does not support external equipment.
110B - Controller does only support external equipment.
The errors described here are issued when the application tries to use a ressource which isn't available. These are mostly also bugs in the application. Please tell us.
2001 - Message not supported in current state
2002 - Illegal Controller / PLCI / NCCI
2003 - Out of PLCI
2004 - Out of NCCI
2005 - Out of LISTEN
2007 - llegal message parameter coding
The errors described here are issued when the application tries to request a service in a wrong way. Again, these are mostly bugs you should tell us.
3001 - B1 protocol not supported
3002 - B2 protocol not supported
3003 - B3 protocol not supported
3004 - B1 protocol parameter not supported
3005 - B2 protocol parameter not supported
3006 - B3 protocol parameter not supported
3007 - B protocol combination not supported
3008 - NCPI not supported
3009 - CIP Value unknown
300A - Flags not supported (reserved bits)
300B - Facility not supported
300C - Data length not supported by current protocol
300D - Reset procedure not supported by current protocol