| Linux-GPIB 4.3.6 Documentation | ||
|---|---|---|
| <<< Previous | Next >>> | |
iberr is set whenever a function from the 'traditional' or 'multidevice' API fails with an error. The meaning of each possible value of iberr is summarized in the following table:
Table 1. iberr error codes
| constant | value | meaning |
|---|---|---|
| EDVR | 0 | A system call has failed. ibcnt/ibcntl will be set to the value of errno. |
| ECIC | 1 | Your interface board needs to be controller-in-charge, but is not. |
| ENOL | 2 | You have attempted to write data or command bytes, but there are no listeners currently addressed. |
| EADR | 3 | The interface board has failed to address itself properly before starting an io operation. |
| EARG | 4 | One or more arguments to the function call were invalid. |
| ESAC | 5 | The interface board needs to be system controller, but is not. |
| EABO | 6 | A read or write of data bytes has been aborted, possibly due to a timeout or reception of a device clear command. |
| ENEB | 7 | The GPIB interface board does not exist, its driver is not loaded, or it is not configured properly. |
| EDMA | 8 | Not used (DMA error), included for compatibility purposes. |
| EOIP | 10 | Function call can not proceed due to an asynchronous IO operation (ibrda(), ibwrta(), or ibcmda()) in progress. |
| ECAP | 11 | Incapable of executing function call, due the GPIB board lacking the capability, or the capability being disabled in software. |
| EFSO | 12 | File system error. ibcnt/ibcntl will be set to the value of errno. |
| EBUS | 14 | An attempt to write command bytes to the bus has timed out. |
| ESTB | 15 | One or more serial poll status bytes have been lost. This can occur due to too many status bytes accumulating (through automatic serial polling) without being read. |
| ESRQ | 16 | The serial poll request service line is stuck on. This can occur if a physical device on the bus requests service, but its GPIB address has not been opened (via ibdev() for example) by any process. Thus the automatic serial polling routines are unaware of the device's existence and will never serial poll it. |
| ETAB | 20 | This error can be returned by ibevent(), FindLstn(), or FindRQS(). See their descriptions for more information. |
If you wish to avoid using a global variable, you may instead use ThreadIberr() which returns a thread-specific value.
| <<< Previous | Home | Next >>> |
| ibcnt and ibcntl | Up | ibsta |