IVI Swtch Class Error Codes

If an error occurs as the result of an IVI call, the type of error is indicated by the numerical range of the error number. First display the error number in hexadecimal format, then look it up in the following tables.

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

BFFA2000 are IVI Swtch class error codes and can be interpreted in the following table

BFFA4000 are Pickering specific errors interpreted at this link location


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 occurred 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.
How did we do?
0 out of 0 people found this helpful.