Share
These are the error code definitions from BUSAPI.H. For the most up-to-date listing of error-codes, see the current BUSAPI.H file, which is supplied with the API software.
BusTools Low Level Device Driver error return constants | ||
Error | Code | Description |
BTD_OK | 0 | success |
BTD_ERR_PARAM | 1 | invalid parameter |
BTD_ERR_NOACCESS | 2 | unable to map/access adapter |
BTD_ERR_INUSE | 3 | adapter already in use |
BTD_ERR_BADADDR | 4 | invalid address |
BTD_ERR_NODETECT | 5 | I/O or Config register ID invalid, board detect fail |
BTD_ERR_BADCFG | 6 | board jumper configuration invalid or not supported |
BTD_ERR_NOTSETUP | 7 | adapter has not been setup |
BTD_ERR_FPGALOAD | 8 | FPGA load failure |
BTD_ERR_WRITEFAIL | 9 | not used |
BTD_ERR_NOMEMORY | 10 | error allocating memory in SW version |
BTD_ERR_BADADDRMAP | 12 | bad initial mapping of address |
BTD_ERR_BADEXTMEM | 13 | bad extended memory mapping |
BTD_ERR_BADBOARDTYPE | 14 | Unknown board type |
BTD_ERR_BADWCS | 15 | Verify failure reading Writable Control Store |
BTD_NO_PCI_SERVICES | 16 | PCI services not available or not installed |
BTD_NO_PCI_CARRIER | 17 | Cannot locate IP-1553 PCI carrier |
BTD_NO_PLATFORM | 18 | Platform specified unknown or not supported |
BTD_BAD_MANUFACTURER | 19 | IP ID PROM Manufacturer code not 0x79 |
BTD_BAD_MODEL | 20 | IP ID PROM Model number not 0x05(MF) or 0x08(SF) |
BTD_BAD_SERIAL_PROM | 21 | IP Serial PROM needs update, no support for this version |
BTD_NEW_SERIAL_PROM | 22 | Serial PROM too new, not supported by this software |
BTD_CHAN_NOT_PRESENT | 23 | Channel not present (on multi-channel board) |
BTD_NO_SUPPORT | 24 | Bus/Carrier/OS combination not supported by API |
BTD_BAD_HW_INTERRUPT | 25 | Hardware interrupt number bad or not defined in registery |
BTD_FPGA_NOT_CLEAR | 26 | The FPGA configuration failed to clear |
BTD_NEW_PCCARD_FW | 27 | PCC-1553 firmware is too new for this version of the API |
BTD_OLD_PCCARD_FW | 28 | PCC-1553 firmware is too old, use the JAM Player to update it |
BTD_BAD_CONF_FILE | 29 | Unable to open ceidev.conf |
BTD_NO_DRV_MOD | 30 | No Driver Module found |
BTD_IOCTL_DEV_ERR | 31 | Error in ioctl get device |
BTD_IOCTL_SET_REG | 32 | Error in ioctl set region |
BTD_IOCTL_REG_SIZE | 33 | Error in getting ioclt region size |
BTD_IOCTL_GET_REG | 34 | Error in ioctl get region |
BTD_BAD_SIZE | 35 | Region size is 0 |
BTD_BAD_PROC_ID | 36 | Unable to set process ID |
BTD_HASH_ERR | 37 | Unable to setup hash table |
BTD_NO_HASH_ENTRY | 38 | No hash table entry found |
BTD_WRONG_BOARD | 39 | Wrong board type for command |
BTD_MODE_MISMATCH | 40 | IPD1553 mismatch in the mode. |
BTD_IRIG_NO_LOW_PEAK | 41 | No lower peak on IRIG DAC calibration |
BTD_IRIG_NO_HIGH_PEAK | 42 | No upper peak on IRIG DAC calibration |
BTD_IRIG_LEVEL_ERR | 43 | Delta between MAX and MIN DAC peak values less than required |
BTD_IRIG_NO_SIGNAL | 44 | No IRIG Signal Detected |
Error return codes from LOWLEVEL routines | ||
Error | Code | Description |
BTD_ERR_NOWINRT | 50 | WinRT driver not loaded/started |
BTD_ERR_BADREGISTER | 51 | WinRT parameters don't match registry |
BTD_ERR_BADOPEN | 52 | WinRT device open failed |
BTD_UNKNOWN_BUS | 53 | Bus is not PCI, ISA or VME |
BTD_BAD_LL_VERSION | 54 | Unsupported lowlevel driver installed |
BTD_BAD_INT_EVENT | 55 | Unable to create interrupt event |
BTD_ISR_SETUP_ERROR | 56 | Error setting up the ISR driver |
BTD_CREATE_ISR_THREAD | 57 | Error creating the ISR thread |
BTD_NO_REGIONS_TO_MAP | 58 | No regions requested in call to vbtMapBoardAddresses |
Error return codes from BusTools API routines | ||
Error | Code | Description |
API_SUCCESS | 0 | No error detected |
API_CONTINUE | 101 | API function should continue execution normally |
API_RETURN_SUCCESS | 102 | API function should return immediately with API_SUCCESS |
API_NEVER_CALL_AGAIN | 103 | User function is never to be called again |
API_BUSTOOLS_INT_USED | 170 | Interrupt on card already in use |
API_BUSTOOLS_INITED | 201 | This card has already been init'ed |
API_BUSTOOLS_NOTINITED | 202 | BusTools API not initialized |
API_BUSTOOLS_BADCARDNUM | 203 | Bad card number specified |
API_BUSTOOLS_BADINTTYPE | 204 | Bad interrupt type for registering callback |
API_BUSTOOLS_BADBUFSIZE | 205 | Bad buffer size for registering callback |
API_BUSTOOLS_BADCOUPLING | 206 | Bad coupling specified in BusTools_SetVoltage |
API_BUSTOOLS_BADVOLTAGE | 207 | Bad voltage specified in BusTools_SetVoltage |
API_BUSTOOLS_BADSEGNUM | 208 | Bad segment number specified |
API_BUSTOOLS_EVENBCOUNT | 209 | Even byte count required for this routine |
API_BUSTOOLS_BADMEMORY | 210 | BusTools Board Dual-Port Memory Self-Test Failed |
API_BUSTOOLS_TOO_MANY | 211 | Too many user interrupt functions registered |
API_BUSTOOLS_FIFO_BAD | 212 | User API_INT_FIFO structure corrupted or bad entry |
API_BUSTOOLS_NO_OBJECT | 213 | Error creating event object or thread |
API_BUSTOOLS_BAD_REGS | 214 | Register File Memory Self-Test failed |
API_BUSTOOLS_NO_FILE | 215 | Could not open the specified file |
API_BUSTOOLS_NO_MEMORY | 216 | BusTools_MemoryAlloc request overflows first 64 Kw of board memory |
API_HW_IQPTR_ERROR | 217 | Hardware Interrupt Pointer register error. |
API_BIT_FAIL_PRI | 218 | BIT failure/data error detected on primary bus |
API_BIT_FAIL_SEC | 219 | BIT failure/data error detected on secondary bus |
API_BUSTOOLS_FIFO_DUP | 220 | Specified API_INT_FIFO structure is already in use.V4.35.ajh |
API_HARDWARE_NOSUPPORT | 225 | Function not supported by current hardware |
API_OUTDATED_FIRMWARE | 226 | Firmware version no longer supported, contact factory for upgrade |
API_NO_OS_SUPPORT | 227 | Function not supported by underlying Operating System |
API_NO_BUILD_SUPPORT | 228 | Function not supported by API as built |
API_CHANNEL_OPEN_OTHER | 229 | Board or channel already opened as another cardnum |
API_BUSTOOLS_BAD_ALIGN | 230 | API structures are not properly aligned |
API_SINGLE_FUNCTION_ERR | 231 | You have attempted to start multiple functions on a single function board |
API_CANT_LOAD_USER_DLL | 232 | Cannot load specified user DLL |
API_EI_BADMSGTYPE | 252 | Bad message type specified in EbufWrite |
API_EI_ILLERRORNO | 253 | Error injection buffer num > number of buffers avail |
API_EI_ILLERRORADDR | 254 | Illegal error buffer address |
API_BAD_ADDR_TYPE | 271 | Bad address type for BusTools_GetAddr() |
API_BC_NOTINITED | 301 | BC_Init not yet called |
API_BC_INITED | 302 | BC_Init already called |
API_BC_RUNNING | 303 | BC simulation currently running |
API_BC_NOTRUNNING | 304 | BC simulation not currently running |
API_BC_MEMORY_OFLOW | 305 | BC memory overflow |
API_BC_ILLEGAL_MBLOCK | 306 | BC illegal mem block number specified |
API_BC_MBLOCK_NOMATCH | 307 | BC specified addr is not a BC message block |
API_BC_MBUF_NOT_ALLOC | 308 | BC message buffers have not been allocated |
API_BC_MBUF_ALLOCD | 309 | BC message buffers already allocated |
API_BC_ILLEGAL_NEXT | 310 | BC illegal next message number |
API_BC_ILLEGAL_PREV | 311 | BC illegal prev message number |
API_BC_ILLEGAL_BRANCH | 312 | BC illegal branch message number |
API_BC_MESS1_COND | 313 | BC first message in buffer is conditional |
API_BC_BAD_COND_ADDR | 314 | BC bad address value in conditional message |
API_BC_BADTIMEOUT1 | 315 | BC illegal "No Response" timeout |
API_BC_BADTIMEOUT2 | 316 | BC illegal "Late Response" timeout |
API_BC_BADFREQUENCY | 317 | BC illegal minor frame frequency |
API_BC_HALTERROR | 318 | BC error detected during stop, bus is probably unterminated |
API_BC_BOTHBUFFERS | 323 | BC cannot specify both buffers |
API_BC_BOTHBUSES | 324 | BC cannot specify both buses |
API_BC_MCODE4_UPDATE | 325 | not used |
API_BC_UPDATEMESSTYPE | 326 | BC message update must operate on a message (not branch) |
API_BC_ILLEGALMESSAGE | 327 | BC message in memory is not legal |
API_BC_ILLEGALTARGET | 328 | BC branch data message number not legal |
API_BC_NOTMESSAGE | 329 | BC msg is not a proper 1553-type message |
API_BC_NOTNOOP | 330 | BC msg is not a proper noop-type message |
API_BC_APERIODIC_RUNNING | 331 | BC Aperiodics still running, cannot start new msg list |
API_BC_APERIODIC_TIMEOUT | 332 | BC Aperiodic messages did not complete in time |
API_BC_CANT_NOOP | 333 | BC cannot noop or un-noop a noop message |
API_BC_MINOR_OFLOW | 334 | BC message processing has overflowed specified Minor Frame time. Bus simulation may not be accurate. Ensure that the bus is properly terminated. |
API_BC_READ_TIMEOUT | 335 | RT timeout when attempting to read data. |
API_BC_READ_NODATA | 336 | No RT data in int queue |
API_BM_NOTINITED | 401 | BM_Init or BM_MessageAlloc not called |
API_BM_INITED | 402 | BM_Init already called |
API_BM_RUNNING | 403 | BM simulation currently running |
API_BM_NOTRUNNING | 404 | BM simulation not currently running |
API_BM_MEMORY_OFLOW | 405 | BM memory overflow |
API_BM_CBUF_EXISTS | 406 | BM subunit already defined |
API_BM_CBUF_NOTDEFINED | 407 | BM subunit not yet defined |
API_BM_ILLEGAL_ADDR | 408 | BM illegal address specified |
API_BM_ILLEGAL_SUBADDR | 409 | BM illegal subaddress specified |
API_BM_ILLEGAL_TRANREC | 410 | BM illegal trans/rec flag specified |
API_BM_ILLEGAL_MBUFID | 411 | BM illegal mbuf_id for specified subunit |
API_BM_MBUF_NOMATCH | 412 | BM no match for specified address |
API_BM_WRAP_AROUND | 413 | BM API message buffer has overflowed, data has been lost |
API_BM_ILLEGAL_MESSAGE | 414 | BM illegal message type in HW buffer |
API_BM_MSG_ALLOC_CALLED | 415 | BM_MessageAlloc has already been called |
API_BM_HW_WRAP_AROUND | 416 | BM HW message buffer has overflowed, data has been lost |
API_BM_POINTER_REG_BAD | 417 | BM HW pointer register contents invalid |
API_BM_READ_TIMEOUT | 418 | RT timeout when attempting to read data. |
API_BM_READ_NODATA | 419 | No BM data in int queue |
API_RT_NOTINITED | 501 | RT_Init not yet called |
API_RT_INITED | 502 | RT_Init already called |
API_RT_RUNNING | 503 | RT simulation currently running |
API_RT_NOTRUNNING | 504 | RT simulation not currently running |
API_RT_MEMORY_OFLOW | 505 | RT memory overflow |
API_RT_CBUF_EXISTS | 506 | RT subunit MBUFs already allocated |
API_RT_CBUF_NOTDEFINED | 507 | RT subunit not yet defined |
API_RT_ILLEGAL_ADDR | 508 | RT illegal address specified |
API_RT_ILLEGAL_SUBADDR | 509 | RT illegal subaddress specified |
API_RT_ILLEGAL_TRANREC | 510 | RT illegal trans/rec flag specified |
API_RT_ILLEGAL_MBUFID | 511 | RT illegal mbuf_id for specified subunit |
API_RT_TOOMANY_MBUFS | 512 | not used |
API_RT_CBUF_BROAD | 513 | RT 31 is broadcast only |
API_RT_CBUF_NOTBROAD | 514 | specified rt address is non-bro only |
API_RT_MBUF_NOMATCH | 515 | RT message buffer not found at specified address |
API_RT_BROADCAST_DISABLE | 516 | RT 31 Broadcast is disabled |
API_RT_SELF_TEST_MODE | 517 | RT Self Test Wrap-Around Mode selected, normal operation inhibited |
API_RT_READ_TIMEOUT | 518 | RT timeout when attempting to read data. |
API_RT_READ_NODATA | 519 | No RT data in int queue |
API_LOW_MINOR_OFLOW | 605 | BC minor frame overflow 16-bit windows only |
API_LV_BADARRAY | 700 | LabView array structure not correctly setup |
API_NO_LV_SUPPORT | 701 | Function not supported in LabView |
API_PLAYBACK_INIT_ERROR | 801 | Error initializing Playback |
API_PLAYBACK_BAD_THREAD | 802 | Attempt to create thread failed |
API_PLAYBACK_BAD_FILE | 803 | File open failed |
API_PLAYBACK_BAD_EVENT | 804 | Event creation error |
API_PLAYBACK_BUF_EMPTY | 805 | Playback Buffer empty |
API_PLAYBACK_BAD_EXIT | 806 | Unexpected Exit from Playback |
API_PLAYBACK_BAD_MEMORY | 807 | Unable to allocate memory on Host |
API_PLAYBACK_DISK_READ | 808 | Disk read Error during playback |
API_PLAYBACK_RUNNING | 809 | Playback is already running |
API_PLAYBACK_BAD_ALLOC | 810 | Failure to allocate enough BusTools Memory for PB |
API_TIMETAG_BAD_DISPLAY | 901 | Unknown or unsupported Time Tag display format |
API_TIMETAG_BAD_INIT | 902 | Unknown Time Tag Initialization method |
API_TIMETAG_BAD_MODE | 903 | Unknown Time Tag Operating Mode |
API_TIMETAG_NO_DLL | 904 | DLL containing BusTools_TimeTagGet() could not be loaded |
API_TIMETAG_NO_FUNCTION | 905 | Could not get the address of the BusTools_TimeTagGet() function |
API_TIMETAG_USER_ERROR | 906 | User function BusTools_TimeTagGet() returned an error |
API_TIMETAG_WRITE_ERROR | 907 | Cannot write to time tag load register when in API_TM_IRIG mode |
API_IRIG_NO_SIGNAL | 908 | No external IRIG signal present |