Pickering IVI Driver - Explanation of errors and how to fix them

BFFA1000 are IVI error codes and can be interpreted in the table at this link location
BFFA2000 are IVI Switch class error codes and can be interpreted in the table at this link location


Pickering specific errors - BFFA4000 range



Core driver error codes:

These error codes happen when calling functions, that manipulate device. Manipulation with device is executed by core driver. In case operation fails (e.g. hardware failure of device) one of these codes is returned.

0xbffa4000
IVI_SPECIFIC_ERROR_BASE
This is a fundamental failure of the IVI driver to find the IVI sub-system software. Check that the National Instruments ICP software package has been installed.

0xbffa4001
PI40IV_ERROR_BAD_SESSION
No card present with specified number
Driver tries to access card that is not opened or is not there at all.
This error may appear while initializing card when wrong resource string is given to initialize function.

0xbffa4002
PI40IV_ERROR_NO_INFO
Card information unobtainable
This error is indicating hardware problem of the card. Try to work with card using different means (e.g. soft front panel). If this error occurs contact support@pickeringtest.com.

0xbffa4003
PI40IV_ERROR_CARD_DISABLED
Card disabled
Operations on the cards were disabled due to a hardware problem. Try to work with card using different means (e.g. soft front panel). If this error occurs contact support@pickeringtest.com.

0xbffa4004
PI40IV_ERROR_BAD_SUB
Invalid sub-unit number
Driver tries to access sub-unit on card that is non-existent.
This error should not appear, if it does please contact support@pickeringtest.com.

0xbffa4005
PI40IV_ERROR_BAD_CHANNEL
Invalid channel number
Driver tries to operate channel of sub-unit on card that is non-existent.
This error should not appear, if it does please contact support@pickeringtest.com.

0xbffa4006
PI40IV_ERROR_NO_CAL_DATA
Target has no calibration data
This error appears when pi40iv specific driver functions pi40iv_ReadCal and pi40iv_WriteCal are used with card that doesn't support calibration. Note that only certain types of resistor cards (e.g. 40-290) support reading and writing calibration data.

0xbffa4008
PI40IV_ERROR_MUX_ILLEGAL
Illegal MUX data
This error appears when pi40iv specific driver function pi40iv_SetOutputSub is used on single-multiplexer sub-unit with wrong data. Non-zero write data is illegal for MUX sub-unit.  In order to operate MUX sub-unit, use IVI compliant pi40iv_Connect or pi40iv specific pi40iv_SetOutputBit.

0xbffa4009
PI40IV_ERROR_EXCESS_CLOSURE
Closure limit exceeded
The high switch density attained in certain System 40/45/50 cards, particularly high-density matrix types, necessitates close packing of relays and airflow is quite restricted. If excessive numbers of relays were energized for a prolonged period overheating could occur. To guard against this danger the software driver places a limit on the number of crosspoints that can be energized simultaneously.

0xbffa400c
PI40IV_ERROR_FAILED_INIT
Cannot open a Pickering card with this resource name
This error occurs when using initialization function. Resource string is corrupted and/or location of card is wrong.
Make sure format of your resource string is in format PXIbus::device[::INSTR] for local PXI connection and TCPIP[board]::host address::bus.device[::INSTR] for connection on LXI card. Bus and device is a pair that describes location of card in system. When format is right and this error still occurs, bus and device pair is wrong.

0xbffa400d
PI40IV_ERROR_READ_FAIL
Failed to read from hardware
Operation on card failed, because sub-operation read failed.
This error indicates hardware problem of the card. Try to work with card using different means (e.g. soft front panel). If this fails, contact support@pickeringtest.com.

0xbffa400e
PI40IV_ERROR_WRITE_FAIL
Failed to read from hardware
Operation on card failed, because sub-operation write failed.
This error indicates hardware problem of the card. Try to work with card using different means (e.g. soft front panel). If this fails, contact support@pickeringtest.com.

0xbffa400f
PI40IV_ERROR_VISA_OP
VISA operation failed
Card failed to response to VISA operation.
This error happens when hardware of the card that is responsible for communication with computer is damaged. Try to work with card using different means (e.g. soft front panel). If this fails, contact support@pickeringtest.com.

0xbffa4010
PI40IV_ERROR_VISA_VERSION
Incompatible VISA version
VISA version is not compatible with IVI driver. This error may also indicate insufficient version of (VISA) kernel driver.
Update drivers to compatible versions. See readme files to find out which versions are compatible. Usually updating to the most recent version of VISA and/or kernel driver will solve this problem. For more information refer to our software driver download web page

0xbffa4011
PI40IV_ERROR_SUB_TYPE
Function call incompatible with sub-unit
Driver uses function, that is incompatible with sub-unit it is used with.
This error should not appear, if it does please contact support@pickeringtest.com.

0xbffa4012
PI40IV_ERROR_BAD_ROW
Matrix row value out-of-range
Matrix operation tries to operate crosspoint on nonexistant row.
This error should not appear, if it does please contact support@pickeringtest.com.

0xbffa4013
PI40IV_ERROR_BAD_COLUMN
Matrix column value out-of-range
Matrix operation tries to operate crosspoint on nonexistent column.
This error should not appear, if it does please contact support@pickeringtest.com.

0xbffa4016
PI40IV_ERROR_BAD_CAL_INDEX
Calibration index value out-of-range
This error appears when pi40iv specific driver functions pi40iv_ReadCal and pi40iv_WriteCal are used. Index parameter of the function points at nonexistent calibration value. Number of calibration values is the same as size of sub-unit. Only certain types of resistor cards (e.g. 40-290) support reading and writing calibration data.

0xbffa401b
PI40IV_ERROR_STATE_CORRUPT
Cannot execute due to corrupt sub-unit state
For unknown reason, sub-unit of a card is corrupted. All operations are inhibited on such sub-unit.
Usually closing and initializing card should clear corrupted state, if not, this may indicate hardware fault on card.

0xbffa401c
PI40IV_ERROR_NO_SETUP_MODEL_INFO
Failed to receive setup information about "Model"
Check the Option string in the InitWithOptions call, it should have a statement Model:xx-xxxx-xxxx, where xx-xxxx-xxx is the card model number and must match an entry in the pi40iv.ini file.

0xbffa401d
PI40IV_ERROR_EEPROM_WRITE_TMO
Timeout writing to EEPROM
Operation of writing into card's EEPROM (e.g. writing calibration values) timeout. This error indicates some problems with access to card's onboard EEPROM used to store various information about card.
This error indicates hardware problem of the card. Try to work with card using different means (e.g. soft front panel). If this fails, contact support@pickeringtest.com.

0xbffa401f
PI40IV_ERROR_BAD_POT
Unrecognized pot number requested
This error should not appear, if it does please contact support@pickeringtest.com.

0xbffa4020
PI40IV_ERROR_MATRIXR_ILLEGAL
Invalid write pattern for MATRIXR sub-unit
Illegal use of pi40iv specific function pi40iv_SetOutputSub on RF matrix sub-unit.
RF matrix is a sub-unit that has special internal construction to make RF performance of unit as good as possible. Because of this construction, it is impossible to connect two crosspoints on one1 row or column (in other words each row and column can have maximum one interconnection active at the same time). If data array given to pi40iv_SetOutputSub contains configuration that contradicts this rule, this error is returned..

0xbffa4021
PI40IV_ERROR_MISSING_CHANNEL
Attempted operation on non-existent channel
This error should not appear, if it does please contact support@pickeringtest.com.

0xbffa4022
PI40IV_ERROR_CARD_INACCESSIBLE
Card cannot be accessed (failed/removed/unpowered)
Card was removed from system or unpowered. If this is not the case, this may indicate hardware problem of the card and/or chassis it is placed in.

0xbffa4028
PI40IV_ERROR_CORE_DRIVER_UNKNOWN
Unspecified core driver error
Core (pilpxi) driver error that occurred was not recognized. This is probably due incompatibility in IVI and core driver. Updating software may change this error code into some proper error code.

Status error codes:

These error codes are result of calling pi40iv_CheckStatusCallback. This callback can be called directly using pi40iv_CheckStatus. It is also called indirectly when changing various IVI systems (e.g. specificaly appointed inner variables) etc. Some of them are very similar to core driver errors.

0xbffa4029
PI40IV_ERROR_STAT_NO_CARD
No Pickering card open on the session
Driver tries to access card that is not opened or is not there at all.
This error should not appear, if it does please contact support@pickeringtest.com.

0xbffa402a
PI40IV_ERROR_STAT_WRONG_DRIVER
Card requires later driver version
Version of driver is insufficient to manipulate the card.
Update drivers to compatible versions. See readme files to find out which versions are compatible. Usually updating to the most recent version of VISA and/or kernel driver will solve this problem. For more information refer to our software driver download web page

0xbffa402b
PI40IV_ERROR_STAT_EEPROM_ERR
Error interpreting card EEPROM data

Data read from eeprom on card was corrupted. This error indicates some problems with access to card's onboard EEPROM used to store various information about card.
This error indicates hardware problem of the card. Try to work with card using different means (e.g. soft front panel). If this fails, contact support@pickeringtest.com.

0xbffa402c
PI40IV_ERROR_STAT_DISABLED
Card is disabled
Operations on the cards were disabled due to a hardware problem. Try to work with card using different means (e.g. soft front panel). If this fails, contact support@pickeringtest.com.

0xbffa402d
PI40IV_ERROR_STAT_NO_SUB
Card has no sub-unit with specified number
Driver tries to access sub-unit on card that is non-existent.
This error should not appear, if it does please contact support@pickeringtest.com.

0xbffa402e
PI40IV_ERROR_STAT_BUSY
Busy (card or sub-unit)
When operating card, there is need for brief pause that relays need for debouncing etc. (for Pickering card it is typically 200 s). This status error indicates, driver is trying to manipulate card, but card is still in process of last command.

If this status code appears, use functions pi40iv_IsDebounced() or pi40iv_WaitForDebounce(). This may happen in multi-threaded operations that work with single card and sometimes this happens when manipulating card right after initialization.

0xbffa402f
PI40IV_ERROR_STAT_HW_FAULT
Hardware fault (eg. defective serial loop)
This error is indicating hardware problem of the card. Try to work with card using different means (e.g. soft front panel). If this fails, contact support@pickeringtest.com.

0xbffa4030
PI40IV_ERROR_STAT_PARITY_ERROR
9050 Parity Error
This error happens when hardware of the card that is responsible for communication with computer is damaged. Try to work with card using different means (e.g. soft front panel). If this fails, contact support@pickeringtest.com.

0xbffa4034
PI40IV_ERROR_STAT_CORRUPTED
Sub-unit logical state is corrupted
For unknown reason, sub-unit of a card is corrupted. All operations are inhibited on such sub-unit.
Usually closing and initializing card should clear corrupted state. If not, this may indicate hardware fault on card.

0xbffa4035
PI40IV_ERROR_STAT_CARD_INACCESSIBLE
Card cannot be accessed (failed/removed/unpowered)
Card was removed from system or unpowered. If this is not the case, this may indicate hardware problem of the card and/or chassis it is placed in.

0xbffa4038
PI40IV_ERROR_STAT_OK
No error
Status check revealed no problem with the card.

Pickering IVI driver specific errors

Most of these errors have something to do with initialization of driver session. These are often caused by wrong option string or outdated data file defining Pickering cards.

0xbffa4039
PI40IV_ERROR_INI_MODULE_NOT_FOUND
Module not found in pi40iv.ini
The model number specified in the option string in the InitWithOptions call does not exist in the data file defining Pickering cards. First check that the text in the option string is correct, check that an identical entry exists in pi40iv.ini located in the installation folder for the Pickering driver, normally:
C:\Program Files\IVI\Drivers\pi40iv

If the card does not exist in the ini file, check the software download website to see if there is a newer pi40iv.ini file containing the required card definition, if not then contact support@pickeringtest.com for an update to the file.

0xbffa403a
PI40IV_ERROR_INI_FORMAT_VERSION
Wrong format version of pi40iv.ini
Format of pi40iv.ini file is incompatible with IVI driver.
In past format of data file describing Pickering cards changed. This error means, driver can't read this data file. Updating driver and/or data file to the most recent version will solve this problem. You can download both at software download website.

0xbffa403b
PI40IV_ERROR_INI_FILE_NOT_FOUND
pi40iv.ini not found
This error indicates, data file pi40iv.ini is missing.
This data file is usually located in folder C:\Program Files\IVI\Drivers\pi40iv. This depends on version of software installed in computer. To solve this problem, place pi40iv.ini in said folder. The safer method would be to reinstall IVI driver. Installation will place data file into proper folder.

0xbffa403c
PI40IV_ERROR_INI_MFG_NO
Wrong manufacturer number
Section of data file describing Pickering cards that describes manufacturer number is wrong.
pi40iv.ini contains a line that describes manufacturer number (mfg_no = 10B5). This line is not recognized or the number is wrong. The most probable cause is corruption of pi40iv.ini. It is recommended to replace it with recent version from software download website or reinstall IVI driver.

0xbffa403d
PI40IV_NO_SETUP_MODEL_INFO
Failed to receive setup information about "Model"
The model number specified in the option string in the InitWithOptions call does not contain a valid model string.

First check that the text in the option string is correct, check that an identical entry exists in pi40iv.ini located in the installation folder for the Pickering driver, normally: C:\Program Files\IVI\Drivers\pi40iv

If the card does not exist in the ini file, check the software download website to see if there is a newer pi40iv.ini file containing the required card definition, if not then contact support@pickeringtest.com for an update to the file.

0xbffa403e
PI40IV_ERROR_READING_REGISTRY
Failed to read INI file path from windows registry
Register key that contain path to pi40iv.ini is not readable.
This register key initializes when installing several products like NI VISA or Pickering IVI driver. Reinstalling products should solve this problem. Register key that is necessary for IVI driver to initialize is "HKEY_LOCAL_MACHINE\SOFTWARE\IVI"

0xbffa403f
PI40IV_ERROR_WRONG_CARD_VALUES
Card indicating other size than INI file values
Model of card for driver to initialize is different from model passed in option string. When card is initialized, Model sting is passed through option string, so that driver can find information about card in data file. When this error occurs, information about card's structure doesn't correspond with real card's structure.

Make sure, model string is right. Note that some cards have more configuration for one Pickering model. In this case, model string has to contain complete configuration. For example 40-560-021-115x16 is typical model that also contains configuration. Configuration of card must be the same as the model configuration, of course.

0xbffa4040
PI40IV_ERROR_DRIVER_SETUP_OPTION2
Wrong config parameter in driver setup option string
Config string passed in option string was in wrong format.

Some cards can be configured during initialization (for example 40-613-002). Config string has strict rules to it and this error indicates these rules were breached. Config string is specific for each type of configurable card. Refer to section of special card types to get more information.

0xbffa4041
PI40IV_ERROR_RESISTOR_VALUE_EXC
Resistance value exceeded card possibilities
Requested resistance is too high for resistance card. This error occurs when calling pi40iv specific function pi40iv_SetResistance.


ClientBridge errors


When IVI driver communicates with kernel driver in LXI, it uses communication library called ClientBridge. Most of the errors here concern communication problems with LXI over network

0xbffa4042
PI40IV_ERROR_PICMLX_CLI_NOT_INIT
picmlx: library not initialized

In past client bridge libraries needed to be initialized before using them.
This system changed and this error is deprecated and cannot happen.


0xbffa4043
PI40IV_ERROR_PICMLX_CLI_INVALID_SESSION
Client: Invalid session ID

ClientBridge session passed into one of ClientBridge functions was invalid.

This error should not appear, if it does please contact support@pickeringtest.com.


0xbffa4044
PI40IV_ERROR_PICMLX_CLI_HOST_UNAVAILABLE
Client: Destination host is unavailable

Hostname or IP address passed into ClientBridge connection function can't be contacted.

This error can happen when initializing LXI module or card. The most probable problem is wrong IP address or hostname in LXI resource string. This error also occurs when LXI cannot be contacted, either it is network problem or LXI is not functioning properly.


0xbffa404c
PI40IV_ERROR_PICMLX_CLI_ECHOD_DATA
Client: Received corrupted data in EchoDirect function

EchoDirect is ClientBridge system to query LXI device for communication information.
This is error in past ClientBridge releases, in recent version are all EchoDirect errors represented by PI40IV_ERROR_PICMLX_CLI_DIRECTECHO_FAILED


0xbffa404d
PI40IV_ERROR_PICMLX_CLI_ECHOD_HOST
Client: Echo direct request timeout

EchoDirect is ClientBridge system to query LXI device for communication information.
This is error in past ClientBridge releases, in recent version are all EchoDirect errors represented by PI40IV_ERROR_PICMLX_CLI_DIRECTECHO_FAILED


0xbffa404e
PI40IV_ERROR_PICMLX_CLI_ECHOD_RECV
Client: Can't receive data in EchoDirect function

EchoDirect is ClientBridge system to query LXI device for communication information.
This is error in past ClientBridge releases, in recent version are all EchoDirect errors represented by PI40IV_ERROR_PICMLX_CLI_DIRECTECHO_FAILED


0xbffa404f
PI40IV_ERROR_PICMLX_CLI_ECHOD_CREATE
Client: Can't create echo direct socket

EchoDirect is ClientBridge system to query LXI device for communication information.
This is error in past ClientBridge releases, in recent version are all EchoDirect errors represented by PI40IV_ERROR_PICMLX_CLI_DIRECTECHO_FAILED


0xbffa4050
PI40IV_ERROR_PICMLX_CLI_SESSION
Client: Session can not be NULL!

NULL parameter passed to ClientBridge function as session.
This is error in past ClientBridge releases, in recent version this error is represented by PI40IV_ERROR_PICMLX_CLI_INVALID_SESSION


0xbffa4051
PI40IV_ERROR_PICMLX_CLI_CONNECT
Client: Can't connect to remote host

ClientBridge connection function failed when connecting to LXI. This error appears when secondary problem caused driver to failed to initialize because connecting to LXI failed. In this case, LXI IP address or hostname should be ok, but other problems prevent connection (such as wrong connection port or network problems).

This error indicates problem of the LXI. Try to work with LXI using different means (e.g. soft front panel). If this fails, contact support@pickeringtest.com.


0xbffa4052
PI40IV_ERROR_PICMLX_CLI_RECV_FAILED
Client: Can't receive data

ClientBridge failed to read data packet from LXI. This error indicates failure in communication with LXI.

This problem may appear due to network latency or similar temporary state of network or LXI. If this error persist, contact support@pickeringtest.com.


0xbffa4053
PI40IV_ERROR_PICMLX_CLI_RECV_DATA
Client: Received corrupted data

ClientBridge received corrupted data packet from LXI. This error indicates failure in communication with LXI.

This problem may appear due to network latency or similar temporary state of network or LXI. If this error persist, contact support@pickeringtest.com.


0xbffa4054
PI40IV_ERROR_PICMLX_CLI_SEND_FAILED
Client: Can't send data

ClientBridge failed to send data packet to LXI. This error indicates failure in communication with LXI.

This problem may appear due to network latency or similar temporary state of network or LXI. If this error persist, contact support@pickeringtest.com.


0xbffa4055
PI40IV_ERROR_PICMLX_CLI_FUNC_NOT_LOCAL
Client: function is not supported on local system

When connection is done to local PXI system, driver attempts to call function, that is not possible on local system.

This error should not appear, if it does please contact support@pickeringtest.com.


0xbffa4056
PI40IV_ERROR_PICMLX_CLI_NOT_CONNECTED
Client: not connected

ClientBridge attempted to call function that works with LXI without previous connection to it.

This error should not appear, if it does please contact support@pickeringtest.com.


0xbffa4057
PI40IV_ERROR_PICMLX_CLI_PARAM_SIZE
Client: parametr is NULL or size is invalid

Driver attempted to call ClientBridge function with wrong parameter.

This should not happen when calling IVI class functions. When using pi40iv specific functions, this indicates improper use of the function.


0xbffa4059
PI40IV_ERROR_PICMLX_SRV_INVALID_FID
Server: Invalid function ID

Data packet from ClientBridge contains wrong identifier.

This error indicates incompatibility between ClientBridge libraries and LXI firmware. Try to update ClientBridge to most recent version. If problem persists, contact support@pickeringtest.com to get proper release of ClientBridge libraries.


0xbffa405a
PI40IV_ERROR_PICMLX_SRV_RPC_DATA
Server: RPC data are corrupted

LXI received corrupted data packet from ClientBridge. This error indicates failure in communication with LXI.

This problem may appear due to network latency or similar temporary state of network or LXI. If this error persist, contact support@pickeringtest.com.


0xbffa405b
PI40IV_ERROR_PICMLX_SRV_INVALID_CARDID
Server: Invalid card ID.

LXI received request to operate card, the identifier of the card is invalid.

This error should not appear, if it does please contact support@pickeringtest.com.


0xbffa405c
PI40IV_ERROR_PICMLX_SRV_INVALID_ADDRESS
Server: Address of a card is invalid

Bus/device pair presented in resource string is not corresponding with card in LXI.

This error should not appear, if it does please contact support@pickeringtest.com.


0xbffa405d
PI40IV_ERROR_PICMLX_SRV_OPEN_CARD
Server: The card is used

Card, that driver is trying to initialize, is already opened by different client.

Note: when initializing card, client locks it and no-one else can open the card until closed by the client. This still applies even if different sort of driver access the card (for example kernel driver or java applet SFP).


0xbffa405e
PI40IV_ERROR_PICMLX_SRV_ACCESS_DENIED
Server: You haven't any rights to the card(s)

Driver tried to operate card it has no rights to.

This error should not appear, if it does please contact support@pickeringtest.com.


0xbffa405f
PI40IV_ERROR_PICMLX_SRV_NOT_SUPPORTED
Server: Function is not supported by this LXI device

Driver tries to call function that is not compatible with LXI device.

This error should not appear, if it does please contact support@pickeringtest.com.


0xbffa4060
PI40IV_ERROR_PICMLX_SRV_DEVICE_INFO
Server: Information about LXI device is not obtainable or is not all

Information about LXI is not complete or unobtainable.

This error appears when LXI is not configured properly and thus part or all configuration information is invalid. This usually indicates some problems in LXI firmware.


0xbffa4061
PI40IV_ERROR_PICMLX_SRV_OUT_OF_RESOURCES
Server: Out of resources

LXI could not allocate resources that it needs for proper functioning.

Every time someone connects to LXI, dynamic structures are alocated. This error indicates resources needed for allocation are not available. This error should not appear when normally using LXI, it may appear when extreme numbers of clients connect to LXI. Freeing resources should allow new resources to be allocated. In worst case scenario restarting LXI breaks all connections and frees all resources.


0xbffa4062
PI40IV_ERROR_PICMLX_SRV_DATA_LENGTH
Server: Required length of data is too long

Data packet from ClientBridge to LXI was corrupted (too long).

This error should not appear, if it does please contact support@pickeringtest.com.


0xbffa4064
PI40IV_ERROR_PICMLX_SRV_FUNC_NOT_IMPL
Server: Function is not impelented or it is reserved

Driver tries to call function on LXI which is not implemented.

This error should not appear, if it does please contact support@pickeringtest.com.


0xbffa4065
PI40IV_ERROR_PICMLX_SRV_CARD_USED_BYCLI
Server: The card is already used by the client

Driver session tries to open card in LXI twice.

This should be not possible in IVI driver. This error should not appear, if it does please contact support@pickeringtest.com.



0xbffa4066
PI40IV_ERROR_PICMLX_SRV_UNDEFINED
Server: Undefined error

Error received from LXI was not recognized.

This error can indicate incompatibility between ClientBridge and LXI. Normally it should not appear.


0xbffa4068
PI40IV_ERROR_PICMLX_SRV_DEVICE_LOCKED
Server: Device is locked - another client has exclusive access

LXI is locked and thus no card can be opened - initialization fails.

LXI contains mechanism for locking. This means no other connection to LXI is not allowed opening of cards. This error may appear when initializing driver session if different program locks LXI first.


0xbffa4069
PI40IV_ERROR_PIPLX_INVALID_SESSION
Session ID is not valid (deprecated)

ClientBridge session is invalid.

This error is now merged with PI40IV_ERROR_PICMLX_CLI_INVALID_SESSION


0xbffa406a
PI40IV_ERROR_PIPLX_FUNC_NOT_LOADED
piplx: Desired function isn't loaded from library

When connecting to local PXI card, driver couldn't find function in local communication library (pilpxi.dll).

ClientBridge is library for communicating with LXI, but it can also talk to local PXI card. For this, driver uses Pickering kernel driver for PXI cards - pilpxi.dll. This error means there is something wrong with pilpxi.dll, it may be corrupted, old or (in most cases) missing. Updating Pickering Interfaces PXI VPP/VISA driver should fix this problem.


0xbffa406b
PI40IV_ERROR_PIPLX_NOT_CONNECTED
piplx: You are not connected to remote host

Driver calls card operating functions prior to connecting to LXI.

This should be not possible in IVI driver. This error should not appear, if it does please contact support@pickeringtest.com.



0xbffa406c
PI40IV_ERROR_PIPLX_FUNC_NOT_LOCAL
piplx: Function is not supported on local system

LXI dedicated function is used on local PXI.

This should be not possible in IVI driver. This error should not appear, if it does please contact support@pickeringtest.com.



0xbffa406d
PI40IV_ERROR_PIPLX_NOT_INIT
piplx: library not initialized

In past client bridge libraries needed to be initialized before using them.
This system changed and this error is deprecated and cannot happen.


0xbffa406e
PI40IV_ERROR_PIPLX_PARAM_SIZE
piplx: Parametr is NULL or size is invalid

Parameter passed to function is not valid.

This error is now merged with PI40IV_ERROR_PICMLX_CLI_PARAM_SIZE


0xbffa406f
PI40IV_ERROR_DRIVER_UNKNOWN
Driver error unknown or undefined

IVI driver couldn't recognize error.

This error can appear when IVI driver, ClientBridge and/or kernel driver libraries are not fully compatible. Updating drivers should clear this problem.


0xbffa4070
PI40IV_ERROR_PICMLX_CLI_BEGINTRANS
Client: Transmission wasn't initiated

ClientBridge communication system failed.

This error should not appear, if it does please contact support@pickeringtest.com.


0xbffa4071
PI40IV_ERROR_PICMLX_CLI_ENDTRANS
Client: Previous transmission wasn't ended

ClientBridge communication system failed.

This error should not appear, if it does please contact support@pickeringtest.com.


0xbffa4072
PI40IV_ERROR_PICMLX_CLI_INVALID_INDEX
Client: Invalid list item index

Indexing of internal ClientBridge object failed.

This error should not appear, if it does please contact support@pickeringtest.com.


0xbffa4073
PI40IV_ERROR_PICMLX_CLI_DIRECTECHO_FAILED
Client: Direct discovery function failed

Discovery mechanism failed for some reason.

Discovery is used to get information about connection parameters from LXI. Even though this operation may fail for numerous reasons (often system failure), typical problem is wrong IP address in LXI resource string.


0xbffa4074
Client: Broadcast discovery function failed.


0xbffa4075
Function call incompatible with card type or capabilities.


0xbffa4076
Switch pole value out of range.


0xbffa4077
Attempt to activate a non-existent capability.


pxbffa4078
Action requires hardware that is not present.


0xbffa4079
Faulty hardware.


0xbffa407a
Failed to execute (e.g. blocked by a hardware condition).


0xbffa407b
Current value out of range.


0xbffa407c
Invalid range value.


0xbffa407d
Attribute not supported.


0xbffa407e
Register number out of range.


0xbffa407f
Function couldn't be loaded from external dll.

Check that all dependencies are satisfied. This driver requires that VISA and IVI are installed.

0xbffa4080
Module not found in pi40iv.xml

This model is not described in the card definition file. Contact Pickering support.

0xbffa4081
pi40iv.xml not found

0xbffa4082
Specific driver functions cannot be simulated.

Specific functions do not support simulation mode.
0xbffa4083
Illegal operation on MATP

This matrix type does not support all connection types.




IVI-SWTCH CLASS ERRORS - BFFA2000 range




These are standard errors defined in the IVI specification, as such there is little we can add to explain most of these.

0xbffa2000
IVICLASS_ERROR_BASE
IVI SWTCH error

An error has occured which does not map to a known error.


0xbffa2001
IVISWTCH_ERROR_INVALID_SWITCH_PATH
Invalid path string

The string you have entered does not correspond to a valid switch path for this card.

Let's say we have channels ch1, ch2, ch3. Correct path looks like this: ch1->ch2,ch2->ch3. This particular error is indicating syntax error in path.


0xbffa2002
IVISWTCH_ERROR_INVALID_SCAN_LIST
Invalid Scan List string

The string you have entered does not correspond to a valid switch path for this card.

Pickering IVI switch driver doesn't support IviSwtchScanner extension group.


0xbffa2003
IVISWTCH_ERROR_RSRC_IN_USE
One of the channels is a configuration channel that is in use or is a common multiplexer channel that is in use

As a rule, IVI doesn't support any "crossing of path". In other words no configuration channel may be used by more than 1 paths.

Normally in IVI there is no "switch over" operation. In case of MUX (and change over switch, which is sort of special case of MUX), to make "switch over" operation, 2 operation must be taken. First disconnects existing connection, second connects desired position. It is prohibited to connect MUX common with 2 different channels too.


0xbffa2004
IVISWTCH_ERROR_EMPTY_SCAN_LIST
The scan list string is empty

Pickering IVI switch driver doesn't support IviSwtchScanner extension group.


0xbffa2005
IVISWTCH_ERROR_EMPTY_SWITCH_PATH
The path string is empty

Path parameter passed to SetPath function is empty. This is secondary error to IVISWTCH_ERROR_INVALID_SWITCH_PATH


0xbffa2006
IVISWTCH_ERROR_SCAN_IN_PROGRESS
The switch module is currently in scanning mode

Pickering IVI switch driver doesn't support IviSwtchScanner extension group.


0xbffa2007
IVISWTCH_ERROR_NO_SCAN_IN_PROGRESS
The switch module is not currently in scanning mode

Pickering IVI switch driver doesn't support IviSwtchScanner extension group.


0xbffa2008
IVISWTCH_ERROR_NO_SUCH_PATH
No explicit path exists between the two channels

This error indicates, driver tries to get information about non-existent path. This can happen when trying to disconnect channels that are not explicitly connected or when trying to retrieve path between 2 channels that are not explicitly connected.


0xbffa2009
IVISWTCH_ERROR_IS_CONFIGURATION_CHANNEL
You cannot make an explicit connection to a configuration channel

Configuration channel is used as one of channels in Connect or Disconnect functions or it is the first or the last channel in path. This is not allowed.


0xbffa200a
IVISWTCH_ERROR_NOT_A_CONFIGURATION_CHANNEL
One of the non-terminal channels in the path is not a configuration channel

Path in IVI is a string, that describes connections between two channels. The first and the last channels in every path must NOT be configuration channels. On the contrary any other channel MUST be configuration channel.


0xbffa200b
IVISWTCH_ERROR_ATTEMPT_TO_CONNECT_SOURCES
You cannot make a connection between two different sources

Every channel can be marked as source channel. It is not allowed to connect 2 different channels that are marked as source directly or indirectly.


0xbffa200c
IVISWTCH_ERROR_EXPLICIT_CONNECTION_EXISTS
An explicit connection between the channels already exists

It is not allowed to connect 2 channels using 2 different paths.


0xbffa200d
IVISWTCH_ERROR_LEG_MISSING_FIRST_CHANNEL
A leg in the path does not begin with a channel name

Leg of path is a segment of path in form: channel1->channel2. This error indicates "channel1" is corrupted or missing.


0xbffa200e
IVISWTCH_ERROR_LEG_MISSING_SECOND_CHANNEL
A leg in the path is missing the second channel

Leg of path is a segment of path in form: channel1->channel2. This error indicates "channel2" is corrupted or missing.


0xbffa200f
IVISWTCH_ERROR_CHANNEL_DUPLICATED_IN_LEG
The first and second channels in the leg are the same

Leg of path is a segment of path in form: channel1->channel2. This error indicates channel1 and channel2 be the same channel.


0xbffa2010
IVISWTCH_ERROR_CHANNEL_DUPLICATED_IN_PATH
A channel name is duplicated in the path string

It is not allowed to make paths that result in "circle". E.g. channel1->channel2,channel2->channel3,channel3->channel2,... is invalid path.


0xbffa2011
IVISWTCH_ERROR_PATH_NOT_FOUND
No path was found between the two channels

Current toplogy of channels doesn't allow 2 channels to be connected. There is error in channel names or there is not configuration channel(s) that can allow for connection.


0xbffa2012
IVISWTCH_ERROR_DISCONTINUOUS_PATH
The first channel of a leg in the path is not the same as the second channel in the previous leg

Path channel1->channel2,channel3->... is not allowed.


0xbffa2013
IVISWTCH_ERROR_CANNOT_CONNECT_DIRECTLY
The path contains a leg with two channels that cannot be directly connected

Leg of path is a segment of path in form: channel1->channel2. Ech leg represent direct connection between 2 channels.


0xbffa2014
IVISWTCH_ERROR_CHANNELS_ALREADY_CONNECTED
A leg in the path contains two channels that are already directly connected

This is another resource conflict error message. Here not only 1 configuration channel is already used, but whole leg in path is already used.


0xbffa2015
IVISWTCH_ERROR_CANNOT_CONNECT_TO_ITSELF
A channel cannot be connected to itself


0xbffa2016
IVISWTCH_ERROR_MAX_TIME_EXCEEDED
Max time exceeded

Pickering IVI switch driver doesn't support IviSwtchScanner extension group.

Need help?



Support knowledgebase

Have questions or need some help? While we enjoy talking to you, you can find technical information for our entire product range here.

Technical know-how 


Long-term support

Because we manufacture our products in-house, we are able to provide you with guaranteed long-term support and low obsolescence.

Our support


Resource center

From success stories and product literature to newsletters, find the information you need about our switching and simulation solutions.

Get the resources you need


Worldwide presence

We supply and support our products across the globe, with seven offices in the Americas, Europe and Asia as well as additional representation. 

Find a local office or agent near you