The altia argument to altia_open is NULL.

The altia_input argument to altia_register_input is NULL.

The altia_output argument to altia_register_output is NULL.

Some of the analog output expiration states have not been configured. This board requires that if any of the expiration states have been configured then all the states must be configured, and the "Set analog outputs when a watchdog timer expires" must be enabled.

This board only supports resetting the analog outputs to zero when the watchdog expires.

Analog input channels are not supported by this board.

All analog input channels must have the same input range for this board.

Analog output channels are not supported by this board.

An attempt was made to write an analog output value that is Not-a-Number (NaN).

The requested analog output is locked. If you need access to this channel, use the generic version of this driver.

All analog output channels must have the same output range for this board.

The analog-to-digital converter on the HIL board is currently in use by another operation.

Cannot open and initialize the ARCNET board.

The ARCNET transmission failed due to excessive NAKs.

The given ARCNET node ID is out of bounds (0-255).

The ARCNET message cannot be sent because there is no node on the network with the given target node ID.

The argument list for the model is too big.

The autopilot argument to val_open is NULL.

The autopilot is not valid. It may not have been made active during normal simulation in the VAL Initialize block and thus may be uninitialized.

The autopilot type argument to val_open is NULL.

A backing store is not supported.

The barometer is not responding. The device may have been damaged.

The baud rate exceeds the maximum baud rate set when the stream was created.

The beep argument to beep_open is NULL.

A beep was attempted but it failed for some reason. It is possible that permission was denied.

The specified beep frequency is out of the acceptable range. See the documentation for valid beep frequencies.

The reconfiguration_begin_control function has not been called.

The qtimer_begin_resolution function has not been called successfully.

The bipolar PWM configuration may only be configured on the even PWM channels for this card. See the card's documentation for details.

Block delete refused.

Block insert refused.

The HIL board is already opened by another process. The board does not support access from more than one process at the same time.

The board argument passed to the board-specific HIL driver is NULL. This situation should never occur unless the user is calling the board-specific driver directly or memory has been corrupted.

The board identifier argument passed to the board-specific HIL driver is NULL. This situation should never occur unless the user is calling the board-specific driver directly or memory has been corrupted.

The board is in use by another process and the board-specific driver does not support multi-process access to the card.

An operating system specific kernel-level driver for the specified card could not be found. The card or driver may not be installed. The kernel-level driver is the driver that gets installed when the operating system detects the hardware. Check Device Manager to see if the card is present or recognized by the operating system. Also verify that you have selected the correct card in the HIL Initialize block or hil_open function.

The border type selected for the operation is not supported by the current operation.

The buffer argument is NULL. It should be a valid pointer.

The specified buffer mode is not supported.

For a read operation, the buffer has overflowed. For a write operation, there is no more data left in the buffer. The sampling frequency is too fast for the rate at which data is being read from or written to the buffer. For HIL Timebase blocks or HIL tasks, oversampling has occurred. For Stream blocks, the hardware FIFO overflowed.

The supplied buffer is too small for the data requested.

An operation is already in progress.

The specified byte order is not supported. For example, VAX and Cray byte ordering is not supported.

Sensor calibration failed for some reason. Try running the model again.

The camera is already in use by another application.

The specified virtual name for the camera has not been assigned to an actual device.

The CAN bus identifier is too large for the standard frame format. Use the flexible=1 option on the URI to allow extended CAN FD frames if your CAN device supports it.

The listening socket was unable to accept a client connection.

Unable to access game controller.

The timeouts cannot be added because both sides are absolute timeouts.

The type of DSM protocol cannot be auto-detected for external remotes.

It was not possible to bind the socket to the given port. Check that the port number is valid and not in use.

The communication protocol, such as UDP, could not be configured for broadcasting.

The parameter cannot be changed at the present time.

Unable to close the connection.

An error occurred while attempting to stop and close the PA10.

Cannot compress.

It was not possible to connect to the specified URI.

It was not possible to connect to the license manager.

It was not possible to connect to the specified PLC. It is likely unreachable.

A character was encountered that cannot be converted.

Cannot copy RAM to ROM.

Unable to create a force feedback effect. The device may be out of memory for effects or the effect is not supported.

Unable to create a window for the force feedback game controller.

It was not possible to create the preferences node. You may not have sufficient privileges.

Failed to create a temporary file.

The preferences value could not be deleted. It may not exist, or you may not have sufficient privileges.

The values of a preferences node could not be enumerated.

The operation failed because the socket manager/driver could not be found.

It was not possible to get the buffer size.

Unable to get the properties of the camera. This may indicate a hardware issue.

Unable to get the state of the game controller.

Unable to get the state of the mouse.

It was not possible to get the maximum packet size.

The preferences value could not be retrieved. You may not have sufficient privileges.

The process affinity could not be determined.

The timer resolution could not be retrieved. Stack or memory corruption is likely.

Unable to get the current high-resolution time.

It was not possible to indicate closure of the connection to the remote peer.

The OpenVR cannot be properly initialized due to an error.

The PA10 cannot be properly initialized due to an error.

It was not possible to initialize the socket library.

Unable to set the linker options for a connection.

It was not possible to listen on the specified connection.

Unable to negotiate protocol data unit (PDU) size.

Cannot obtain a lock to gain exclusive access to a critical section of code.

An attempt to get the driver directory failed.

Unable to open the EtherCAT device specified. Make sure the XML configuration and IP address specified are correct

Unable to open license file. Make sure that the file exists and you have permission to read the license file. Mapped network drives are not accessible with elevated privileges. Use the full UNC path, such as "\\server\licenses\john-doe.qlic", instead.

Unable to poll a connection.

Unable to poll the game controller.

It is not possible to quantize to so few colors.

It is not possible to quantize to so many colors.

An error occurred while attempting to read the state of the SCHUNK gripper.

Failed to read a temporary file.

Unable to receive data over a connection.

The encoder cannot be reset to a non-zero value on this device.

Failed to seek on a temporary file.

Variables cannot be selected after a visualization task has already been started.

Unable to send data over a connection.

Unable to set the flags of a file descriptor or socket.

Unable to set the parameters of a force feedback effect. The parameters may be incorrect or unsupported by the device.

Unable to set the cooperation level of the force feedback game controller.

Unable to set data format of game controller.

Cannot set the port unreachable option to disable reporting ICMP Port Unreachable messages for UDP datagrams

The position of the stream cannot be set.

The preferences value could not be set. You may not have sufficient privileges.

The timer resolution could not be set. The user does not have permission.

Unable to shut down send and/or receives on the connection.

Unable to download or start a force feedback effect. The device may be out of memory.

Failed to launch an interrupt thread

The Quanser license manager could not be started.

The PLC could not be started.

The QUARC Target Manager could not be started.

The XMLRPC client cannot be started.

The XMLRPC server cannot be started.

Unable to stop a force feedback effect.

The Quanser license manager could not be stopped.

The PLC canot be stopped.

The QUARC Target Manager could not be stopped.

The timeouts cannot be subtracted because the left-hand side is relative and the right hand side is absolute.

Suspension is not allowed at this point.

An attempt to switch models failed due to a communication failure.

The XMLRPC client cannot establish communication with ROS master.

Failed to write to a temporary file. There may not be enough disk space.

The CANPCI device failed to receive a CAN message.

Initialization of the CANPCI driver failed.

The CANPCI channel specified is invalid.

Parameters supplied to a CANPCI driver function are invalid.

The specified CANPCI could not be found.

The CANPCI device failed to send a CAN message.

Failed to start the CANPCI card(s).

The card argument to hil_open is NULL.

The card identifier argument to hil_open is NULL.

The card location pointer passed as an argument is NULL. A valid pointer to a t_card_location object must be passed to the hil_get_exclusive_access and hil_release_exclusive_access functions.

The card is not valid. It may not have been made active during normal simulation in the HIL Initialize block and thus may be uninitialized.

The card specific option specified is not recognized.

The card specific option specified is recognized, but is not supported by this board.

The value of a card specific option specified is invalid.

The value of a card specific option specified is not recognized.

The card type argument to hil_open is NULL.

Failed to capture video.

CCIR601 sampling is not implemented yet.

The CDATA termination sequence ']]>' is not allowed within XML content.

Change notifications are not supported on the specified file system.

The channel is a listening channel so it cannot be used to send and receive data.

The channel is not a listening channel so it cannot be used to accept connections.

The CIGI Host could not be opened.

The corresponding Circular Buffer Initialize could not be found. Make sure that a Circular Buffer Initialize block is present in the model.

The clock frequency is invalid for the specified clock, or the clock may be unavailable. Try using a different clock frequency (usually slower) or a different clock.

An attempt was made to set the clock frequency to a value that is Not-a-Number (NaN).

The clock frequency specified is negative or zero. The clock frequency must be positive.

The clock frequency is too high for the specified clock. Try using a different clock. Hardware clocks are generally faster than the system clocks.

The clock frequency is too low for the specified clock. Try using a different clock. System clocks are preferable for low frequencies so that hardware clocks remain available for higher frequency operations.

The specified clock mode is not supported by this board.

The specified clock is not supported by the board-specific HIL driver for this board.

The specified clock is not a watchdog timer on this board.

The clock period is too high for the specified clock. Try using a different clock. Hardware clocks are generally faster than the system clocks.

The clock period is too low for the specified clock. Try using a different clock. System clocks are preferable for long periods so that hardware clocks remain available for operations requiring a shorter period.

There are too many color components.

The specified color conversion is not supported.

The color quantization mode change was invalid.

Complex numbers are not currently supported.

The compressed image is too large to fit in the destination. If you are using the Image Compress block then make the output dimension larger.

The specified counter is used as both an encoder and a PWM output channel.

A digital channel was specified as both an input and an output. Digital channels cannot be programmed as an input and an output at the same time.

The special purpose function (e.g. PWM, Encoder, SPI, I2C, UART) pins are already configured for Digital I/O. Please remove the appropriate Digital I/O channels inside the HIL Initialize block in order to use the specified function. Refer to the device help page for pinout diagrams.

The specified digital IO is configured for a special purpose (e.g. PWM, Encoder, SPI, I2C, UART). Therefore it cannot be used as the specified function. Refer to the device documentation for precedents and limitations of the generic digital IO.

An incoming connection was indicated, but was subsequently terminated by the remote peer prior to accepting the call.

The connection has not been bound. This error typically occurs with UDP client sockets whenever a receive operation is attempted prior to the first send operation. UDP client sockets are implicitly bound to the UDP port by the first send operation. Hence, a send must always be done first after a UDP client connection is established.

The remote peer refused the connection, most likely because no server application was listening for connections

The connection was reset. The remote peer may have exited without closing the connection.

The connection has been shut down.

The specified continuous threshold exceeds the peak threshold.

Roomba stream is corrupted.

The file is corrupt or is not the expected format.

The specified bitfile is invalid or corrupt.

Counter parameter is illegal in current operation mode. The counter may already be in use by another operation such as providing a timebase.

A GPIO is in use by another application. Some applications on Linux-based systems use the old sysfs (/sys/class/gpio) file system for GPIO. If a GPIO is exported it cannot be used by QUARC. Try rebooting the target.

Compilation of CUDA PTX code failed. The CUDA PTX source is invalid or the JIT PTX compilation library was not found.

The CUDA context passed to an API call is already in use by another thread.

Cannot communicate with analog output.

DAQmx was unable to attach the specified analog input to the analog input task.

DAQmx was unable to attach the specified analog output to the National Instruments analog output task.

DAQmx was unable to attach the specified digital lines to the National Instruments task.

DAQmx was unable to attach the specified channel to the National Instruments encoder input task.

DAQmx was unable to attach the specified counter channel to the PWM output task.

DAQmx was unable to clear or release a National Instruments task. Try restarting MATLAB.

DAQmx was unable to create a new task. The resource may already be in use by another block.

DAQmx was unable to obtain the name of the PWM channel attached to the PWM output task.

Error setting the hardware timing for the time-base block.

DAQmx was unable to start the National Instruments device task. Make sure the device is not already open. If no devices are open, try restarting MATLAB.

Either the configuration is invalid, or a sample edge was missed before executing the wait.

DAQmx failed to change the source for the encoder count direction.

DAQmx failed to change the counter output terminal.

DAQmx was unable to set the counter timebase rate.

DAQmx failed to reset the device.

DAQmx failed to execute the National Instruments analog input task.

DAQmx failed to execute the digital read task.

DAQmx failed to execute the National Instruments encoder input task.

DAQmx was unable to configure implicit timing for the PWM output task.

DAQmx failed to output the requested analog value.

DAQmx failed to output the requested digital values.

DAQmx failed to output the requested PWM values.

Using a numeric board identifier for NI cards is not supported on this system. Please use the device name instead.

The datagram received was too large for the buffer provided in the receive operation.

The DCT coefficient out of range.

A deadlock situation would have occurred.

The Denso Read block has timed out since no data was received. Check that the IP settings of your PC are correct and that the PC is connected to the Denso controller.

Cannot perform the operation. Object is being destroyed.

Device was disconnected, this can be caused by outside intervention, by internal firmware error or due to insufficient power.

The device driver appears to be incompatible with the device.

Device initialization failed.

I/O device failure.

The device is not connected. If the device was connected then somehow that connection has been lost.

Device is in recovery mode and might require firmware update.

Some of the digital output expiration states have not been configured. This board requires that if any of the expiration states have been configured then all the states must be configured, and the "Set digital outputs when a watchdog timer expires" must be enabled.

This board only supports resetting the digital outputs to tri-state when the watchdog expires.

This board does not support setting the expiration state of all digital outputs. Set digital outputs which are not controlled by the watchdog to 3 (no change).

This board only supports resetting the digital outputs to zero when the watchdog expires.

This board does not support tristating the digital outputs when the watchdog expires. The digital outputs may only be set high or low on watchdog expiration.

Digital input channels are not supported by this board.

The specified digital input channels are not initialized. This board requires that all the channels which will be used for digital inputs should be configured on the HIL Initialize block's "Digital Inputs" tab. Set the "Digital input channels" field to all the digital channels that will be used as digital inputs on the board.

Digital output channels are not supported by this board.

The requested digital output is locked. If you need access to this line, use the generic version of this driver.

The specified digital output channels are not initialized. This board requires that all the channels which will be used for digital outputs should be configured on the HIL Initialize block's "Digital Outputs" tab. Set the "Digital output channels" field to all the digital channels that will be used as digital outputs on the board.

Unable to use DirectX. Make sure DirectX 10.0 or above is installed.

The display is not in graphics mode. Re-open the display in graphics mode.

The display is not in text mode. Re-open the display in text mode.

A division by zero occurred.

A DMA buffer lock failed.

An attempt was made to set a double property to a value that is Not-a-Number (NaN).

Download sequence failed.

The DPC connection has been closed at the peer.

The Draganfly X6 autopilot message failed the CRC check.

The board-specific HIL driver passed an invalid parameter to the operating system specific kernel-level driver for the board. The board-specific HIL driver is likely not compatible with the operating system specific kernel-level driver for the board. Make sure both are up-to-date and compatible versions.

The hil_get_exclusive_access or hil_release_exclusive_access function is present in the driver while the other one is not. These functions are optional, but if one is included in the driver then both must be included.

A hardware driver is missing the open and/or close function.

The HIL driver timed out trying to communicate with the card. The card may not be working or the version of the driver may not be compatible with the version of the card.

The selected serial port does not support the data-terminal-ready (DTR) and data-set-ready (DSR) lines. Set the dsr option on the URI to 'off'.

An XML element has more than one attribute with the same name.

The specified duty cycle is negative and negative duty cycles are not supported by this board.

The specified duty cycle is more than 100% (i.e. greater than 1.0).

Could not communicate with Dynamixel OpenManipulator X.

Could not change parameters of a write group for the Dynamixel OpenManipulator X.

Could not create a read group for the Dynamixel OpenManipulator X.

Could not create a write group for the Dynamixel OpenManipulator X.

Could not open the Dynamixel OpenManipulator X device.

Could not start the Dynamixel OpenManipulator X control loop.

The Dynamixel OpenManipulator X failed to initialize. Make sure the Dynamixel OpenManipulator X is plugged in and powered.

The position PID or feedforward gains for the Dynamixel OpenManipulator X device is out of range.

The goal Position for the Dynamixel OpenManipulator X device is out of range.

The goal PWM for the Dynamixel OpenManipulator X device is out of range.

The profile velocity or acceleration parameters for the Dynamixel OpenManipulator X device is out of range.

Failed to access the NI ELVIS III top board EEPROM during initialization. Try power cycle the ELVIS III. If the error persists, then the problem is likely a hardware fault.

The top board attached to the NI ELVIS III is not compatbile with the driver, make sure the correct top board is attached that matches the board type as selected in HIL Initialize.

The NI ELVIS III top board is not powered, the top board must be powered before this board can be used.

The laser emitter on the depth camera cannot be disabled.

The image is empty. Empty images are not currently supported.

The stream was closed before the first character was read. This error is used internally and should never be returned to the user.

A read from the EMS failed.

A write to the EMS failed.

An attempt was made to set the encoder filter frequency to a value that is Not-a-Number (NaN).

Counter input channels are not supported by this board.

An error has occurred reading an encoder input. Make sure the encoder is connected reliably, there are no ground loops and signal noise is minimized.

The selected quadrature decoding is not available for this board.

End of input stream encountered before tag name.

End of input stream encountered within tag name.

The end of the input was expected. There is too much input data.

The ending quote for a string was expected.

The environment variable could not be found.

An error message corresponding to the given error code could not be found.

An EtherCAT slave did not respond as expected within the timeout interval.

The EtherCAT datagram to be sent is too large. Check the XML description.

A null pointer was specified instead of a valid EtherCAT device.

Invalid ByteSize field specified for EtherCAT process image.

An EtherCAT master is already running on the given MAC address. Stop the existing EtherCAT master first.

The corresponding EtherCAT Master could not be found. Make sure that an EtherCAT Master block is present in the model.

An EtherCAT packet that was sent was lost and never returned. The slave device was not ready.

The EtherCAT device does not have a synchronization client.

An EtherCAT telegram that was sent within a packet was not present in the packet when the packet returned. Data corruption has occurred!

The Validate/Data field in an initialization command for an EtherCAT device contains data of a different size than the Data or DataLength field.

The Validate/DataMask field in an initialization command for an EtherCAT device contains data of a different size than the Data or DataLength field.

Exclusive access to this card has already been granted to another process. Only one process may have exclusive access to the card at one time. Try again later.

Exclusive access to this card was not granted to the process which is attempting to release it. Exclusive access can only be released by the process with exclusive access, and only from the same open handle.

Failed to parse an integer value in a string. Format is incorrect.

Failed to parse a real value in a string. Format is incorrect.

Could not create a callback for the Novint Falcon.

Novint Falcon error.

Could not open the Novint Falcon device.

Could not start the Novint Falcon control loop.

The Novint Falcon failed to initialize. Make sure the Falcon is plugged in and powered.

The requested feature was omitted at compile time.

The file already exists and cannot be overwritten. Delete the file first.

The model specified is not executable.

The file could not be found.

An error occurred reading from a file.

A physical I/O error occurred trying to access the file system.

The file has become too large for the given file format.

An error occurred writing to a file. There may not be enough disk space.

The mask size specified for the filter is not supported. Many filter operations only support 3x3 or 5x5 mask sizes. The mask should also be smaller than the image.

Missing "uri" option. Filter protocols require a "uri" option in their URI to identify the underlying communication protocol.

An attempt to close a Force Dimension haptic device failed.

The Force Dimension haptic device has not been calibrated. Ensure that the device is properly calibrated before use.

An attempt to open a Force Dimension haptic device failed. Ensure that the Force Dimension device is powered on and has been calibrated.

An attempt to read from the Force Dimension haptic device failed.

An attempt to write to the Force Dimension haptic device failed.

The force/torque sensor appears to be disconnected.

The FPGA is already running.

Operation could not be performed because the FPGA is busy. Stop all the activities on the FPGA before requesting this operation.

Operation could not be performed because the FPGA is busy operating in FPGA Interface C API mode. Stop all the activities on the FPGA before requesting this operation.

Operation could not be performed because the FPGA is busy operating in Emulation mode. Stop all the activities on the FPGA before requesting this operation.

Operation could not be performed because the FPGA is busy operating in FPGA Interface mode. Stop all the activities on the FPGA before requesting this operation.

Operation could not be performed because the FPGA is busy operating in Interactive mode. Stop all the activities on the FPGA before requesting this operation.

The chassis is in Scan Interface programming mode. In order to run FPGA VIs, you must go to the chassis properties page, select FPGA programming mode, and deploy settings.

Fractional sampling is not implemented yet.

A framing error occurred

The function is not supported.

Function refused by CPU (Unknown error).

The specified game controller could not be found. A Host Force Feedback Game Controller block for the game controller is required in the same diagram to use the other Force Feedback blocks. There should only be one Host Force Feedback Game Controller block per game controller. Also ensure that the Host Force Feedback Game Controller block comes before the other Force Feedback blocks in the sorted (execution) order.

An error occurred while attempting to close the GenICam camera.

The requested GenICam camera cannot be found.

The requested GenICam camera nodemap cannot be acquired.

An error occurred while attempting to get features from the GenICam camera.

An error occurred while attempting to grab an image using the GenICam camera.

An error occurred while attempting to initialize the GenICam camera.

An error occurred while attempting to read nodes from the GenICam camera.

Cannot set GenICam camera acquisition mode.

Cannot set GenICam camera analog controls to desired value.

Cannot set GenICam camera image to the desired size.

Cannot set GenICam camera image to the desired pixel format.

An error occurred while attempting to write nodes to the GenICam camera.

A timeout occurred while attempting to grab an image using the GenICam camera.

A read of the GPS device failed.

Failed to grab image from v4l2 video input.

The watchdog timer period (a.k.a., timeout interval) is too high. The gumstix watchdog timer may be programmed with any integer value between 1 and 255 seconds.

The watchdog timer period (a.k.a., timeout interval) is too low. The gumstix watchdog timer may be programmed with any integer value between 1 and 255 seconds.

The specified hardware clock is already in use for another operation and the board-specific HIL driver for this board does not permit sharing of the hardware clock.

The hardware appears to have failed. It is either not responding, or not responding as expected. Try powering down and back up.

The selected serial port does not support hardware flow control. Set the flow option on the URI to 'none' or 'software' (if supported).

The hil_acquire_exclusive_access function and Exclusive access to device option on the HIL Initialize block are not supported by this particular card.

The HIL function requires at least one channel to be specified.

Two or more digital outputs were specified with output values that conflict with one another. Refer to the device documentation for limitations.

Support for the given board type does not appear to be installed. Verify that you have selected the correct card in the HIL Initialize block or hil_open function.

The hil_get_double_property function and HIL Get Property block are not supported by this particular card.

The hil_get_integer_property function and HIL Get Property block are not supported by this particular card.

The hil_get_string_property function and HIL Get Property block are not supported by this particular card.

The combination of directions specified for the digital channels are not compatible with the capabilities of this particular card. Some cards have digital channels organized into ports for which all channels in a port must have the same direction. Check the documentation for the card.

One of the digital states specified was not a valid state. Valid modes are 0 (low), 1 (high), 2 (tristate) or 3 (no change).

The specified signature does not match the signature of the bitfile. If the bitfile has been recompiled, regenerate the C API and rebuild the application.

Either the supplied resource name is invalid as a RIO resource name, or the device was not found. Use MAX to find the proper resource name for the intended device.

The hil_monitor_create_interrupt_reader function and HIL Interrupt block are not supported by this particular card.

The hil_monitor_delete function is not supported by this particular card. If the hil_monitor_create_interrupt_reader function is supported then the hil_monitor_stop function MUST be supported. Contact the device manufacturer.

The hil_monitor_read_interrupt function is not supported by this particular card.

The hil_monitor_start function is not supported by this particular card. If the hil_monitor_create_interrupt_reader function is supported then the hil_monitor_stop function MUST be supported. Contact the device manufacturer.

The hil_monitor_stop function is not supported by this particular card. If the hil_monitor_create_interrupt_reader function is supported then the hil_monitor_stop function MUST be supported. Contact the device manufacturer.

The specified virtual name for the HIL card has not been assigned to an actual device.

The hil_poll_interrupt function and HIL Poll Interrupt block are not supported by this particular card.

The hil_read_analog_buffer function and HIL Read Analog Buffer block are not supported by this particular card.

The hil_read_analog_codes function and HIL Read Analog Codes block are not supported by this particular card.

The hil_read_analog function in C or MATLAB and HIL Read Analog block in QUARC are not supported by this particular card.

The hil_read_analog_write_analog_buffer function and HIL Read Analog Write Analog Buffer block are not supported by this particular card.

The hil_read_analog_write_analog function and HIL Read Analog Write Analog block are not supported by this particular card.

The hil_read_buffer function and HIL Read Buffer block are not supported by this particular card.

The hil_read_digital_buffer function and HIL Read Digital Buffer block are not supported by this particular card.

The hil_read_digital function in C or MATLAB and HIL Read Digital block in QUARC are not supported by this particular card.

The hil_read_digital_write_digital_buffer function and HIL Read Digital Write Digital Buffer block are not supported by this particular card.

The hil_read_digital_write_digital function and HIL Read Digital Write Digital block are not supported by this particular card.

The hil_read_encoder_buffer function and HIL Read Encoder Buffer block are not supported by this particular card.

The hil_read_encoder function in C or MATLAB and HIL Read Encoder block in QUARC are not supported by this particular card.

The hil_read_encoder_write_pwm_buffer function and HIL Read Encoder Write PWM Buffer block are not supported by this particular card.

The hil_read_encoder_write_pwm function and HIL Read Encoder Write PWM block are not supported by this particular card.

The hil_read function in C or MATLAB and HIL Read block in QUARC are not supported by this particular card.

The hil_read_other_buffer function and HIL Read Other Buffer block are not supported by this particular card.

The hil_read_other function in C or MATLAB and HIL Read Other block in QUARC are not supported by this particular card.

The hil_read_other_write_other_buffer function and HIL Read Other Write Other Buffer block are not supported by this particular card.

The hil_read_other_write_other function and HIL Read Write Other block are not supported by this particular card.

The hil_read_write_buffer function and HIL Read Write Buffer block are not supported by this particular card. Try using a more specific function or block.

The hil_read_write function and HIL Read Write block are not supported by this particular card. Try using a more specific function or block.

The hil_release_exclusive_access function and Exclusive access to device option on the HIL Initialize block are not supported by this particular card.

The hil_set_analog_input_configuration function is not supported by this particular card.

The hil_set_analog_input_ranges function is not supported by this particular card. It may be necessary to uncheck the two "Set analog input parameters..." options in the HIL Initialize block.

The hil_set_analog_output_ranges function is not supported by this particular card. It may be necessary to uncheck the two "Set analog output parameters..." options in the HIL Initialize block.

The hil_set_analog_termination_state function is not supported by this particular card.

The hil_set_card_specific_options function is not supported by this particular card. It may be necessary to uncheck the two "Set clock parameters..." options in the HIL Initialize block.

The hil_set_clock_frequency function is not supported by this particular card.

The hil_set_clock_mode function is not supported by this particular card.

The hil_set_digital_directions function is not supported by this particular card. Set the "Digital input channels" and "Digital output channels" parameters in the HIL Initialize block to empty matrices: [].

The hil_set_digital_output_configuration function is not supported by this particular card.

The hil_set_digital_termination_state function is not supported by this particular card.

The hil_set_double_property function and HIL Set Property block are not supported by this particular card.

The hil_set_encoder_counts function and HIL Set Encoder Counts block are not supported by this particular card. It may be necessary to uncheck the two "Set initial encoder counts..." options in the HIL Initialize block.

The hil_set_encoder_filter_frequency function is not supported by this particular card. It may be necessary to set the "Encoder filter frequency" parameter in the HIL Initialize block to an empty matrix: [].

The hil_set_encoder_quadrature_mode function is not supported by this particular card. It may be necessary to set the "Encoder quadrature" parameter in the HIL Initialize block to an empty matrix: [].

The hil_set_integer_property function and HIL Set Property block are not supported by this particular card.

The hil_set_other_termination_state function is not supported by this particular card.

The hil_set_pwm_configuration function is not supported by this particular card.

The hil_set_pwm_deadband function is not supported by this particular card.

The hil_set_pwm_duty_cycle function is not supported by this particular card. It may be necessary to uncheck the two "Set PWM output parameters..." options in the HIL Initialize block.

The hil_set_pwm_frequency function is not supported by this particular card. It may be necessary to uncheck the two "Set PWM output parameters..." options in the HIL Initialize block.

The hil_set_pwm_mode function is not supported by this particular card. It may be necessary to uncheck the two "Set PWM output parameters..." options in the HIL Initialize block.

The hil_set_pwm_termination_state function is not supported by this particular card.

The hil_set_string_property function and HIL Set Property block are not supported by this particular card.

The hil_task_create_analog_reader_analog_writer function and HIL Read Analog Write Analog Timebase block are not supported by this particular card.

The hil_task_create_analog_reader function and HIL Read Analog Timebase block are not supported by this particular card.

The hil_task_create_analog_writer function and HIL Write Analog Timebase block are not supported by this particular card.

The hil_task_create_digital_reader_digital_writer function and HIL Read Digital Write Digital Timebase block are not supported by this particular card.

The hil_task_create_digital_reader function and HIL Read Digital Timebase block are not supported by this particular card.

The hil_task_create_digital_writer function that HIL Write Digital Timebase block are not supported by this particular card.

The hil_task_create_encoder_reader function and HIL Read Encoder Timebase block are not supported by this particular card.

The hil_task_create_encoder_reader_pwm_writer function and HIL Read Encoder Write PWM Timebase block are not supported by this particular card.

The hil_task_create_other_reader function and HIL Read Other Timebase block are not supported by this particular card.

The hil_task_create_other_reader_other_writer function and HIL Read Other Write Other Timebase block are not supported by this particular card.

The hil_task_create_other_writer function and HIL Write Other Timebase block are not supported by this particular card.

The hil_task_create_pwm_writer function and HIL Write PWM Timebase block are not supported by this particular card.

The hil_task_create_reader function and HIL Read Timebase block are not supported by this particular card. Try one of the more specific functions or blocks.

The hil_task_create_reader_writer function and HIL Read Write Timebase block are not supported by this particular card. Try one of the more specific functions or blocks.

The hil_task_create_writer function and HIL Write Timebase block are not supported by this particular card. Try one of the more specific functions or blocks.

The hil_task_delete function is not supported by this particular card. If one of the hil_task_create... functions is supported then the hil_task_delete function MUST be supported! In this case, contact the driver manufacturer.

The hil_task_flush function is not supported by this particular card. If one of the hil_task_write... functions is supported then the hil_task_flush function MUST be supported! In this case, contact the driver manufacturer.

The hil_task_get_buffer_overflows function is not supported by this particular card.

The hil_task_read_analog function is not supported by this particular card.

The hil_task_read_analog_write_analog function is not supported by this particular card.

The hil_task_read_digital function is not supported by this particular card.

The hil_task_read_digital_write_digital function is not supported by this particular card.

The hil_task_read_encoder function is not supported by this particular card.

The hil_task_read_encoder_write_pwm function is not supported by this particular card.

The hil_task_read function is not supported by this particular card. Try one of the more specific functions.

The hil_task_read_other function is not supported by this particular card.

The hil_task_read_other_write_other function is not supported by this particular card.

The hil_task_read_write function is not supported by this particular card. Try one of the more specific functions.

The hil_task_set_buffer_overflow_mode function is not supported by this particular card.

The hil_task_start function is not supported by this particular card. If one of the hil_task_create... functions is supported then the hil_task_start function MUST be supported! In this case, contact the driver manufacturer.

The hil_task_stop function is not supported by this particular card. If one of the hil_task_create... functions is supported then the hil_task_stop function MUST be supported! In this case, contact the driver manufacturer.

The hil_task_write_analog function is not supported by this particular card.

The hil_task_write_digital function is not supported by this particular card.

The hil_task_write function is not supported by this particular card. Try one of the more specific functions.

The hil_task_write_other function is not supported by this particular card.

The hil_task_write_pwm function is not supported by this particular card.

The FPGA bitfile could not be read. Make sure the FPGA bitfile is actually installed on the target.

The hil_watchdog_clear function is not supported by this particular card.

The hil_watchdog_is_expired function is not supported by this particular card.

The hil_watchdog_reload function is not supported by this particular card.

The hil_watchdog_set_analog_expiration_state function is not supported by this particular card.

The hil_watchdog_set_digital_expiration_state function is not supported by this particular card.

The hil_watchdog_set_other_expiration_state function is not supported by this particular card.

The hil_watchdog_set_pwm_expiration_state function is not supported by this particular card.

The hil_watchdog_start function is not supported by this particular card.

The hil_watchdog_stop function is not supported by this particular card.

The hil_write_analog_buffer function and HIL Write Analog Buffer block are not supported by this particular card.

The hil_write_analog_codes function and HIL Write Analog Codes block are not supported by this particular card.

The hil_write_analog function in C or MATLAB and HIL Write Analog block in QUARC are not supported by this particular card. You might need to change a board specific option to enable it.

The hil_write_buffer function and HIL Write Buffer block are not supported by this particular card. Try using one of the more specific functions or blocks.

The hil_write_digital_buffer function and HIL Write Digital Buffer block are not supported by this particular card.

The hil_write_digital function in C or MATLAB and HIL Write Digital block in QUARC are not supported by this particular card.

The hil_write function in C or MATLAB and HIL Write block in QUARC are not supported by this particular card.

The hil_write_other_buffer function and HIL Write Other Buffer block are not supported by this particular card.

The hil_write_other function in C or MATLAB and HIL Write Other block in QUARC are not supported by this particular card.

The hil_write_pwm_buffer function and HIL Write PWM Buffer block are not supported by this particular card.

The hil_write_pwm function in C or MATLAB and HIL Write PWM block in QUARC are not supported by this particular card. You might need to change a board specific option to enable it.

The hil_write_termination_states function is not supported by this particular card.

The HiQ firmware build number does not match the HiQ driver build number. Make sure your HiQ driver version is compatible with the HiQ hardware.

The HiQ thread failed to receive any data from the HiQ board.

The specified HiQ report type is unknown. Ensure that the selected HiQ report or mode is valid.

The host is too busy to accept a connection at this point in time. Try again later.

The pipe URI contains a hostname. Specifying a hostname is not supported on this target, because pipes may not be used to communicate between computers on the selected target.

The specified host could not be found.

The host was shut down during the operation.

A Huffman code table entry was missing.

The Huffman code size table overflowed.

The HyMotion-11000 could not be opened. Make sure the Rexroth HyMotion-11000 Motion System is connected.

The specified IDCT output block size is not supported.

An illegal control character was encountered in the stream.

An illegal multi-byte character was encountered in the stream.

An illegal non-character was encountered in the stream.

An illegal surrogate character was encountered in the stream.

An illegal UTF-16 character was encountered in the stream.

The UTF-16 code unit is not a valid lead byte. It is a code unit that is only valid as a surrogate code unit.

An illegal UTF-32 character was encountered in the stream.

An illegal UTF-8 character was encountered in the stream.

The UTF-8 code unit is not a valid lead byte. It is a code unit that is only valid in the middle of a UTF-8 character.

An error occurred attempting to convert the source image.

The data type selected is not currently supported by the chosen image format.

The specified image stream could not be found. The stream type may not be supported by the camera or the stream index is too large.

The image was too big.

The image is too wide for this implementation.

The IMU is not responding properly. Please check the hardware. If necessary, the IMU may be disabled in the card-specific options, in which case the IMU outputs will be zero.

The version of the firmware image is not compatible with the driver. No changes were made.

The hardware appears to be incompatible with the board type selected.

The hardware version is incompatible with the firmware being flashed. No changes were made to the firmware.

An attempt was made to create a named pipe for a pipe that already exists and the properties of the pipe are incompatible. Be aware that under the Windows target, the pipe name "localhost" is already used by the system.

The code being downloaded or run is not compatible with the type of target referenced by the target URI. For example, 32-bit code cannot be downloaded to a 64-bit target or vice versa. In Simulink, make sure the system target file selected in the model's active configuration is compatible with the target referred to by the target URI.

The CUDA kernel launched using an incompatible texturing mode.

This error should never be returned. It is used internally by the Quanser Stream API.

This error should never be returned. It is used internally by the Quanser Stream API.

Failed to initialize v4l2 video input.

The board-specific HIL driver used an internal buffer that was too small for the operating system specific kernel-level driver for the board. The board-specific HIL driver is likely not compatible with the operating system specific kernel-level driver for the board. Make sure both are up-to-date and compatible versions.

A blocking operation was interrupted by a signal.

The interrupt operation argument to a board-specific HIL driver is NULL. This situation should never occur unless the user is calling the board-specific driver directly or memory has been corrupted.

The interrupt vector required by the board is in use by another device and the board-specific HIL driver does not support sharing of the interrupt vector.

A real-time object could not be created. The INtime real-time kernel may not be running. Use the INtime Status icon in the system tray to start the INtime kernel.

The address contains an invalid hexadecimal digit.

The specified algorithm hint is not supported.

The alignment type is invalid.

The maximum allocation chunk is invalid.

An invalid Altia handle was passed as an argument. Once an Altia connection has been closed using altia_close the Altia handle is invalid.

An invalid event name was passed to an altia function.

An invalid t_altia_input handle was passed as an argument.

An invalid t_altia_output handle was passed as an argument.

One of the analog input channels that was specified is not a valid channel number. Channel numbers typically range from 0 to one less than the number of channels.

One of the configurations specified for an analog input channel is not valid for the selected hardware.

One of the ranges specified for an analog input channel is not valid for the selected hardware.

One of the analog output channels that was specified is not a valid channel number. Channel numbers typically range from 0 to one less than the number of channels.

One of the ranges specified for an analog output channel is not valid for the selected hardware.

One of the arguments is invalid.

Invalid array element separator when parsing.

The given t_autopilot handle is not a valid autopilot.

The given base is invalid and cannot be used to convert the integer to a string.

An invalid beep handle was passed as an argument. Once an beep handle has been closed using beep_close the beep handle is invalid.

Invalid block number.

Invalid block size.

Invalid block type.

An invalid board handle was passed as an argument to the board-specific HIL driver. Once a card has been closed using hil_close the board handle is invalid.

The board identifier is not valid. The zero-based index of the board is typically used as the board identifier, although NI boards may also be identified by their name in MAX.

Version information retrieved from the HIL board does not match the driver. It may be necessary to update the QUARC software to get the latest drivers.

An invalid buffer handle was passed to a board-specific HIL driver function.

The buffer mode is invalid.

The specified buffer size is not valid. It may be out of an acceptable range.

The byte count contains an invalid hexadecimal digit.

The calibration data appears to be invalid.

The property value specified is not supported by the camera. Check that the value corresponds with the camera selected.

The given t_card handle is not a valid card. In some Simulink versions, this error can arise when a HIL Initialize block is not in the same subsystem as a HIL Timebase block, due to Simulink incorrectly determining the execution order. In this case, try putting the two HIL blocks in the same subsystem.

The given t_channel handle is not valid.

The PWM output channels are not ordered correctly for the bipolar PWM output. Bipolar PWM outputs require that both the primary and secondary channel be written at the same time, and that the secondary channel be specified in the channel order immediately after the primary channel.

The checksum is invalid. The data may have been corrupted.

The checksum contains an invalid hexadecimal digit.

Invalid object. A CIGI host object cannot be used after it has been closed.

The circular buffer is invalid. A circular buffer may not be used after it has been closed.

The component ID is invalid.

An invalid condition effect type was passed to the game_controller_add_condition_force_effect function.

The connection is not valid. A connection cannot be used after it has been closed.

The crop request is invalid.

The CUDA context has not been initialized. This may indicate version mismatches.

Invalid DAC index.

Invalid DAC value.

The data contains an invalid hexadecimal digit.

Invalid data size received.

The specified data type is not supported.

The mode option specified for a deflate URI is invalid.

The handle to the device is invalid.

Invalid DHT index.

One of the digital input channels that was specified is not a valid channel number. Channel numbers typically range from 0 to one less than the number of channels.

One of the digital output channels that was specified is not a valid channel number. Channel numbers typically range from 0 to one less than the number of channels.

The dimensions exceed the maximum dimensions specified.

The name of the document type is invalid.

The document type definition is not terminated properly.

The DOM named node map is null or otherwise invalid.

The DOM node is NULL or otherwise invalid.

The DOM node list is null or otherwise invalid.

The DPC object is not valid. A DPC object cannot be used after it has been closed.

Invalid DQT index.

Invalid dsr option. Supported values are "off", "on" or "handshake".

One of the encoder filter frequencies specified was not a valid frequency. The frequency is out of range or negative.

One of the encoder input channels that was specified is not a valid channel number. Channel numbers typically range from 0 to one less than the number of channels.

One of the encoder quadrature modes specified was not a valid mode. Valid modes are 0, 1, 2 or 4.

The end-of-file record has a non-zero byte count.

An escape sequence in a quoted string is invalid.

Invalid Ado field (physical address offset) in an initialization or cyclic command for an EtherCAT device.

Invalid Adp field (physical address page) in an initialization or cyclic command for an EtherCAT device.

Invalid BeforeSlave field in an initialization command for an EtherCAT device.

Invalid Cmd field in an initialization or cyclic command for an EtherCAT device.

Invalid Cnt field (working counter value) in an initialization command for an EtherCAT device.

The EtherCAT process image either could not be created or is not large enough for one of the cyclic command specified in the XML.

Invalid DataLength field in an initialization or cyclic command for an EtherCAT device.

The telegrams within an EtherCAT packet do not fit within the EtherCAT frame. Packet is corrupted!

Invalid Data field in an initialization command for an EtherCAT device.

Invalid InputOffs field (offset at which a cyclic command reads from the process image) in the cyclic commands for an EtherCAT device.

Invalid Addr field (logical address) in an initialization or cyclic command for EtherCAT device.

Invalid Count field in the mailbox states description for EtherCAT master.

EtherCAT master cannot be set to the state requested. The state is not valid for the master.

Invalid OutputOffs field (offset at which a cyclic command writes to the process image) in the cyclic commands for an EtherCAT device.

Invalid Requires field in an initialization command for an EtherCAT device.

Invalid Retries field in an initialization command for an EtherCAT device.

Invalid PhysAddr field (physical address) in the information section (Info) for an EtherCAT slave.

Invalid Source Mac address field for the EtherCAT device.

Invalid StartAddr field in the mailbox states description for an EtherCAT master.

Invalid State field (slave state) in the cyclic commands for an EtherCAT device.

An EtherCAT telegram received from a slave was a different size than the telegram originally sent. Telegram is corrupted!

Invalid Validate/Timeout field in an initialization command for an EtherCAT device.

Invalid Transition field in an initialization command for an EtherCAT device.

Invalid Validate/Data field in an initialization command for an EtherCAT device.

Invalid Validate/DataMask field in an initialization command for an EtherCAT device.

The file handle is not valid. An attempt was made to use a file that is not open.

The mode option specified for a file URI is invalid.

The share mode option specified for a file URI is invalid.

The file type is wrong.

Invalid first character of tag name.

Invalid flash file format.

Invalid flow control option. Supported values are "none", "hw", "sw".

An invalid axis number was specified for a force feedback effect. Axes numbers must range from 0 to 5, corresponding to x, y, z, Rx, Ry and Rz axes respectively.

The given force feedback effect is invalid and does not belong to the game controller specified. The effect may not be supported by the game controller. Also, once an effect has been removed it cannot be used.

An invalid restriction on a format specifier was specified.

The specified game controller is invalid.

The OpenGL or DirectX graphics context is invalid.

The host passed as an argument is invalid. It is likely NULL, indicating the host may not be not connected or listening.

A Host block appears to be incompatible with the current version of QUARC because it has sent invalid data. It may be necessary to rebuild the model.

The Huffman table definition is invalid.

Invalid object. A HyMotion-11000 object cannot be used after it has been closed.

The I2C channel has entered an unexpected state.

Could not configure the I2C timing registers to the specified clock frequency. Please try using a different I2C clock frequency.

Invalid dimension for image data

The specified image does not exist.

The input colorspace is invalid.

The interface code received is not valid. The DPC object should be closed.

An invalid interrupt operation handle was passed as an argument to the board-specific HIL driver. Once a monitor has been deleted using hil_monitor_delete the interrupt operation handle is invalid.

One of the interrupt sources that was specified is not a valid interrupt source. Interrupt sources are typically divided into ranges according to functionality. Refer to the documentation for your card.

Invalid IplImage structure.

The IPv6 address is invalid or incomplete. On Linux systems, the zone identifier must be used by clients to identify the network interface (e.g. eth0) through which a link local address is connecting e.g. tcpip6://[fe80::abcd:beef:1234:5678%eth0]:18000

The JPEG colorspace is invalid.

The JSON is invalid. JSON values must be objects, arrays, numbers, strings, true, false or null.

Invalid Kinect sensor.

Invalid object. A KUKA robot object cannot be used after it has been closed.

A library call was made when the library is not in the proper state. Call sequence is likely invalid.

The Quanser product does not have a valid license for the requested operation. For example, you may be trying to run more than one model at a time when you are only licensed for one, or your license may have expired. Run qc_get_loaded_models to see the models currently loaded and qc_stop_model to stop a model. To configure licensing use the Configure License utility found under Start Menu/All Programs/Quanser for your product. Contact Quanser if you think your license may have expired or it does not suit your current needs.

The license file is invalid. Choose a different license file.

The Configure Licensing tool can only generate a build file snippet for a network client license. Specify the -c option but not the -m option (client not server/manager) when configuring the license.

The extended linear address record has a byte count other than 2.

The log object is not valid. A log object cannot be used after it has been closed.

The macro does not match any of the standard macro names or the name of an environment variable.

The marker length is invalid.

The sampling factors are too large for an interleaved scan.

The media type is not supported, either because parameters such as the frame rate are invalid or there is no codec for that media type.

The method code received is not valid. The DPC object should be closed.

Invalid object. A Kinova MICO robot object cannot be used after it has been closed.

An invalid monitor handle was passed as an argument to a HIL function.

The mutex is not valid. A mutex cannot be used after it has been destroyed.

Invalid object. A NEES object cannot be used after it has been closed.

The initialization string is invalid. A single string containing items separated by newlines (\n) is expected.

Invalid NMEA checksum

Invalid NMEA message

Invalid number of conditions for a condition force effect. There may be one condition for all axes or one condition for each axis.

The number of samples requested in the read or write operation must be greater than zero.

The number of samples in the task buffer must be greater than zero.

An invalid operation handle was passed as an argument to the board-specific HIL driver. Once a task has been deleted using hil_task_delete the operation handle is invalid.

One of the other input channels that was specified is not a valid channel number. Channel numbers are typically divided into ranges according to functionality. Refer to the documentation for your card.

One of the other output channels that was specified is not a valid channel number. Channel numbers are typically divided into ranges according to functionality. Refer to the documentation for your card.

The packet format is invalid.

Invalid parity option. Supported values are "none", "even", "odd", "mark", "space".

Invalid password.

The peer access was invalid. It may not be enabled or may have already been enabled.

Invalid "peer" option was specified. Valid values for the "peer" option are "one", "any", "broadcast" or "manual".

An invalid periodic effect type was passed to the game_controller_add_periodic_force_effect function.

The name of the XML processing instruction target is invalid.

The PLC returned an invalid answer.

The memory pool code is invalid.

The specified data precision is not supported.

The root node specified for preferences was invalid.

The process was assigned an affinity that does not correspond to an existing CPU.

The progressive image parameters are invalid.

The progressive image parameters at the scan script entry are invalid.

One of the PWM output alignments specified is not a valid configuration. Configurations must be 0 (leading-edge-aligned), 1 (trailing-edge-aligned) or 2 (center-aligned)

One of the PWM output configurations specified is not a valid configuration. Configurations must be in the range from 0 to 2 inclusive (0=independent, 1=complementary, 2=bipolar)

One of the PWM deadbands specified is negative. Deadband values must be non-negative.

One of the PWM output channels that was specified is not a valid channel number. Channel numbers typically range from 0 to one less than the number of channels.

One of the PWM output polarities specified is not a valid configuration. Configurations must be 1 (active high) or 0 (active low)

The version of the Intel RealSense API expected does not match the version that is installed. The versions must match exactly.

Reconfiguration instance is not valid. It may have been closed already or never opened successfully.

The record type contains an invalid hexadecimal digit.

The Roomba object is not valid. A Roomba object cannot be used after it has been closed.

Roomba demo number must be 1 to 11.

Roomba digital output must be 0 to 7.

Roomba low side driver number must be 0 to 7.

Roomba duty cycle must be 0 to 128.

Roomba event no must be 1 to 22.

Roomba LED bits must be 0 to 10.

Roomba mode number must be 1 to 3.

The note number of Roomba song must be 31 to 127.

The number of Roomba sensor packets requested must be 0 to 43

Data length mismatches according to the script length defined in the first byte.

The Roomba sensor id is not valid. It must be a value between 7 and 42 inclusive.

Roomba song length must be 1 to 16.

Roomba song number must be 0 to 15.

Roomba stream header must be 19.

Roomba stream size must be (number of packets + number of data bytes + 3)

Roomba stream state must be 0 to 1.

The ROS property object is not valid. A ROS property object cannot be used after it has been closed.

The ROS master has responded with invalid response.

The ROS slave API request is invalid.

The ROS topic is not recognized.

The specified rounding mode is not supported.

The sampling factors are invalid.

No valid points were found in the scan.

The scan script is invalid.

The extended segment address record has a byte count other than 2.

The semaphore is not valid. A semaphore cannot be used after it has been destroyed.

The SerAccel object is not valid. A SerAccel object cannot be used after it has been closed.

An invalid operation was detected in the installation database. The installation database appears to be corrupt.

The shmem protocol is designed for communicating between a real-time model and a foreground application. To use it for communicating between two Windows applications, the "local=true" option is required on the shmem URI. For example, "shmem://mymem:1?local=true".

Socket is not valid. It may have been closed already or never created successfully.

The start linear address record has a byte count other than 4 or an address other than zero.

The start segment address record has a byte count other than 4 or an address other than zero.

The state is invalid. It may have already been unregistered.

Stop bits option has an invalid value. It must be "1", "1.5" or "2".

The stream is not valid. A stream cannot be used after it has been closed.

The character format specified for the stream is out of range.

The image stride was either too small or is not a multiple of the pixel size.

The structure size was invalid. The library may not be the same version as the caller.

An invalid task handle was passed as an argument to a HIL function.

The given thread handle is not valid.

The thread was assigned an affinity that does not correspond to an existing CPU or a CPU in the process affinity.

The timer passed as an argument is invalid.

The timer event passed as an argument is invalid.

The timer notification structure is invalid.

The specified timer period is invalid.

The specified timer resolution is invalid.

The timer semaphore passed as an argument is invalid.

The preferences value is not a string.

The Ublox object is not valid. A Ublox object cannot be used after it has been closed.

Invalid Ublox checksum

Invalid Ublox data

Invalid Ublox identifiers

Invalid Ublox message

The absolute URI is not valid.

The option for a URI is present but the value is invalid.

The port for a URI is present but the value is invalid.

The wrong data type is being used to set the value of the given variable.

The variable indicated could not be found in the scene.

The version structure does not have the right length.

The virtual array access was invalid.

An invalid visualization handle was passed to a Visualization VI or function.

Unable to open a handle to the wiimote device. The wiimote is possibly already opened by another process.

Malformed XML in the XML file.

The contents of a CDATA section were invalid. An invalid character was detected.

The XML <![CDATA[ ...]]> tag was invalid.

The value of the character reference is not a valid character for XML.

An invalid comment was specified in the XML file.

The <?xml ...?> XML declaration is not formed correctly.

The <?xml ...?> XML declaration is not terminated correctly.

Missing document type declaration <!DOCTYPE ...> in the XML file.

An XML element is invalid. An attribute name may be invalid or it is not terminated correctly.

The name of the XML element is invalid. Names must begin with a letter, underscore or colon.

The encoding information in the <?xml ...> XML declaration is not specified properly.

Invalid XML entity reference. Escape ampersands using & to put ampersands in values.

The external identifier in the document type declaration is invalid.

The XML processing instruction was invalid.

The standalone option in the <?xml ...> XML declaration is not specified properly.

The system literal associated with the external identifier in the document type declaration is invalid.

An XML tag is invalid.

The specified XML version is not supported by this XML parser.

An I/O error occurred.

An attempt was made to access a node in a list to which it did not belong, or the node does not belong to a list.

An attempt was made to access a node in a map to which it did not belong, or the node does not belong to a map.

Jaco did not send an acknowledge message when one was expected.

The joint specified for the Jaco device is outside the valid range.

The Jaco joint address is invalid.

Unable to initialize one of the Jaco joints. Make sure that the Jaco cables are properly connected, the emergency stop is released, and the Jaco power is on.

Failed to read CANbus for the Jaco. Check that the CAN cables are properly connected, the emergency stop is released, and the Jaco power is on.

A JACO read timeout expired.

Unable to complete the operation because the JACO is shutting down.

A job is already pending.

It was not possible to join the partition. Security constraints set up for partitioning do not allow it.

Cannot initialize the JR3 PCI force torque sensor.

An error occurred attempting to set the full scales for the JR3 sensor.

The kernel-mode driver can't register the board. This is usually caused by applications that fail to unlink from the system dll, or if the kernel model driver is improperly installed or registered.

The Kinect sensor is already initialized so the requested settings can no longer be configured. Set options before calling the kinect_initialize function.

The Kinect has been initialized without at least one of the requested features. Some of the features will not be available.

The corresponding Kinect Initialize could not be found. Make sure that a Kinect Initialize block is present in the model.

The Kinect sensor has not been initialized.

The type of Kinect selected is not currently supported on this target.

The KUKA robot device could not be opened. Make sure a KUKA robot is connected.

The Leap Motion device cannot be found on the system.

The dynamic link library was found, but an error occurred while loading it.

Failed to close dynamic link library or shared object.

Unable to locate the dynamic link library or shared object.

A macro was missing the closing parenthesis.

The magnetometer is not responding. The device may have been damaged.

Failed to perform a mapping or register operation.

The marker type is not supported.

The matrix is not invertible.

The matrix type of the MAT-file was not recognized. File may be corrupt.

Error from the Kinova MICO device.

Error from the Kinova MICO device: cannot perform the read operation.

Error from the Kinova MICO device: cannot perform the write operation.

The Kinova MICO firmware version could not be read. Ensure the robot arm is powered up and properly connected to the external computer.

The Kinova MICO joint and/or finger firmware version number is not supported.

The joint specified for the Kinova MICO device is outside the valid range.

The Kinova MICO serial link message is invalid.

A character in the input stream did not match the character sequence described in the format string when scanning the stream.

One of the clock frequencies specified does not match the frequency of another channel which shares the same clock resources.

One of the encoder filter frequencies specified does not match the filter frequency of the other channels. This card only allows one filter frequency to be set for all encoder channels.

One of the PWM periods specified does not match the period of the other channels. This card only allows one PWM period to be set for all PWM channels in a bank.

It is not possible to transcode due to multiple uses of the quantization table.

The sampling ratio is mismatched.

The scheduling policy for the thread must match the system scheduling policy on this target operating system.

The character format set for the stream does not match the format indicated by the byte order mark (BOM) in the stream itself.

An XML end tag does not match the corresponding start tag.

Analog input channels have been specified but not enough buffer space has been provided for the read operation.

No configurations were specified when setting the analog input configuration, even though the number of channels indicated was non-zero.

No analog input channels were specified even though the number of analog inputs is nonzero.

No analog maximums were specified when setting the analog ranges, even though the number of channels indicated was non-zero.

No analog minimums were specified when setting the analog ranges, even though the number of channels indicated was non-zero.

Analog output channels have been specified but not enough values have been provided for the write operation.

No analog output channels were specified even though the number of analog outputs is nonzero.

The CANPCI SDK does not appear to be installed or is not in the PATH. See the help for the CANPCI block for the installation requirements. Note that a reboot may be required after installing the SDK.

No clocks were specified even though the number of clocks is nonzero.

Clocks have been specified but not enough clock modes have been provided.

Digital output channels have been specified but not enough digital output configurations have been provided.

Digital input channels have been specified but not enough buffer space has been provided for the read operation.

No digital input channels were specified even though the number of digital inputs is nonzero.

Digital output channels have been specified but not enough values have has been provided for the write operation.

No digital outputs were specified even though the number of digital outputs is nonzero.

Encoder input channels have been specified but not enough encoder counts have been provided.

Encoder input channels have been specified but not enough encoder filter frequencies have been provided.

Encoder input channels have been specified but not enough buffer space has been provided for the read operation.

No encoder input channels were specified even though the number of encoder inputs is nonzero.

Encoder input channels have been specified but not enough encoder quadrature modes have been provided.

Missing end tag name e.g. </>.

Missing Ado node within an InitCmd in EtherCAT XML configuration file. The Ado node identifies the address offset and is a required field when a command other than LRD, LWR or LRW is used.

Missing Adp node within an InitCmd in EtherCAT XML configuration file. The Adp node identifies the address page and is a required field when a command other than LRD, LWR or LRW is used.

Missing Cmd node within an InitCmd in EtherCAT XML configuration file. The Cmd node identifies the EtherCAT command and is a required field.

Missing Comment node within an InitCmd in EtherCAT XML configuration file. The Comments node provides information about the command and is a required field.

Missing Config node within the EtherCAT XML configuration file. The Config node identifies the EtherCAT configuration and is required.

Missing State node within a cyclic Cmd node in EtherCAT XML configuration file. The State nodes identify the states in which the cyclic command should be sent and one is required.

Missing Data or DataLength node within an InitCmd in EtherCAT XML configuration file. Either the Data node or the DataLength node is required because they provide the data for the command.

Missing Addr node within an InitCmd in EtherCAT XML configuration file. The Addr node identifies the logical address and is a required field when a LRD, LWR or LRW command is used.

Missing Count node within the MailboxStates section of an EtherCAT XML configuration file. The Count node identifies the length of the mailbox and is required.

Missing StartAddr node within the MailboxStates section of an EtherCAT XML configuration file. The StartAddr node identifies the starting address of the mailbox and is required.

Missing Master node within the EtherCAT XML configuration file. The Master node identifies the EtherCAT master and is required.

Missing InitCmd node within the Master section of an EtherCAT XML configuration file. The InitCmd node identifies an EtherCAT initialization command for the master and is required.

Missing InitCmds section within the Master section of an EtherCAT XML configuration file. The InitCmds section includes all the EtherCAT initialization commands for the master and is required.

Missing Info node within the Master section of an EtherCAT XML configuration file. The Info node includes information about the master and is a required field.

Missing Source node within the Master section of an EtherCAT XML configuration file. The Source node identifies the Mac address to be used by the master and is a required field.

Missing ProcessImage node within the EtherCAT XML configuration file. The ProcessImage node describes the EtherCAT process image configuration and is required.

Missing Inputs node within the ProcessImage section of the EtherCAT XML configuration file. The Inputs node describes the EtherCAT input process image and is required.

Missing ByteSize node within the ProcessImage/Inputs section of the EtherCAT XML configuration file. The ByteSize node describes the size of the EtherCAT input process image and is required.

Missing Outputs node within the ProcessImage section of the EtherCAT XML configuration file. The Outputs node describes the EtherCAT output process image and is required.

Missing ByteSize node within the ProcessImage/Outputs section of the EtherCAT XML configuration file. The ByteSize node describes the size of the EtherCAT output process image and is required.

Missing Retries node within an InitCmd in EtherCAT XML configuration file. The Retries node indicates how many times the EtherCAT stack attempts to resend the command and is a required field.

Missing Slave node within the EtherCAT XML configuration file. The Slave node identifies an EtherCAT Slave and at least one is required.

Missing InitCmd node within a Slave in EtherCAT XML configuration file. The InitCmd node identifies an EtherCAT initialization command for a slave and is required.

Missing InitCmds section within a Slave in EtherCAT XML configuration file. The InitCmds section includes all the EtherCAT initialization commands for the slave and is required.

Missing Info node within a Slave in EtherCAT XML configuration file. The Info node includes information about the slave and is a required field.

Missing Name node within a Slave in EtherCAT XML configuration file. The Name node identifies the name of the slave and is required.

Missing Transition node within an InitCmd in EtherCAT XML configuration file. The Transition nodes indicate the state transitions forward to the command should be executed and is a required field.

Missing Data node within the Validate section of an InitCmd in EtherCAT XML configuration file. The Data node provides the data used to validate the response from the slaves and is a required field in the Validate section.

The HDAL software does not appear to be installed or is not in the PATH. See the help for the Novint Falcon block for the installation requirements. Note that a reboot may be required after installing the SDK.

The 5DT Data Glove SDK does not appear to be installed or is not in the PATH. See the help for the FDT Data Glove block for the installation requirements. Note that a reboot may be required after installing the SDK.

The FlyCapture SDK does not appear to be installed or is not in the PATH. See the help for the PGR Grab Image block for the installation requirements. Note that a reboot may be required after installing the SDK.

The Force Dimension SDK does not appear to be installed or is not in the PATH. See the help for the Force Dimension Write block for the installation requirements. Note that a reboot may be required after installing the SDK.

A format specifier is missing in the option template.

A required function is missing from a driver.

Interrupt sources have been specified but not enough buffer space has been provided for the poll operation.

No interrupt sources were specified even though the number of interrupt sources is nonzero.

The Leap SDK does not appear to be installed or is not in the PATH. See the help for the Leap Motion block for the installation requirements. Note that a reboot may be required after installing the SDK.

The license file is missing. To configure licensing use the Configure License utility found under Start Menu/All Programs/Quanser for your product.

The OpenVR SDK software does not appear to be installed or is not in the PATH. See the help for the Tracker block for the installation requirements. Note that a reboot may be required after installing the SDK.

Other input channels have been specified but not enough buffer space has been provided for the read operation.

No other input channels were specified even though the number of other inputs is nonzero.

Other output channels have been specified but not enough values have been provided for the write operation.

No other output channels were specified even though the number of other outputs is nonzero.

The PCAN-Basic API does not appear to be installed or is not in the PATH. See the help for the Peak CAN block for the installation requirements. Note that a reboot may be required after installing the SDK.

No properties were specified even though the number of properties is nonzero.

Properties have been specified but no values have been provided for the operation.

PWM output channels have been specified but not enough PWM alignments have been provided.

PWM output channels have been specified but not enough PWM configurations have been provided.

PWM output channels have been specified but not enough PWM high-to-low or low-to-high deadband values have been provided.

PWM output channels have been specified but not enough PWM duty cycles have been provided.

PWM output channels have been specified but not enough PWM frequencies have been provided.

PWM output channels have been specified but not enough PWM modes have been provided.

PWM output channels have been specified but not enough values have been provided for the write operation.

No PWM output channels were specified even though the number of PWM outputs is nonzero.

PWM output channels have been specified but not enough PWM polarities have been provided.

The RealSense 2 library is not installed.

The scan script does not transmit all data.

The Schunk PowerCube software does not appear to be installed or is not in the PATH. See the help for the Schunk Gripper block for the installation requirements. Note that a reboot may be required after installing the SDK.

The Spinnaker SDK does not appear to be installed or is not in the PATH. See the help for the GenICam capture block for the installation requirements. Note that a reboot may be required after installing the SDK.

No option name was found even though a value was specified.

The option for a URI is present but there is no associated value, as expected.

The path component of the URI is missing.

The Vicon DataStream SDK does not appear to be installed or is not in the PATH. See the help for the Vicon block for the installation requirements. Note that a reboot may be required after installing the SDK.

An attribute appears in an XML element tag but there is no associated value.

The version information in the <?xml ...> XML declaration is missing.

The monitor argument to a HIL function is NULL.

More than one SPI chip select signal was chosen by setting both the frame and slave options of the URI. The current hardware does not support both at the same time. Choose one or the other.

The XML file has more than one root element.

Multiple samples for the selected task operation are not supported with decimated sampling by this board. Either set the decimation or the number of samples to 1.

The process lacks the appropriate privileges to perform the operation. Administrator privileges are required. Log in as an Administrator or run as Administrator.

The mutex was owned by another thread but that thread terminated while the lock was still held so the mutex has been abandoned. The caller now owns the mutex but should check for consistency of the shared resource.

The named mutex already exists.

The named mutex could not be found.

The Nagle algorithm is not supported for the given communication subsystem.

A different kind of object with the same name appears in the global namespace.

The length of a path or pathname component exceeds the limit.

Could not close the NEES block.

Could not communicate with the NEES daemon.

The NEES block could not be initialized.

Received invalid data from the NEES daemon.

The network subsystem has failed.

A newer version is installed. No changes have been made.

The specified PWM duty cycle is out of range. For National Instruments cards, the duty cycle should fall within the range between a minimum value of 0.1 % (0.001) and a maximum value of 99.9 % (0.999).

The specified PWM frequency is out of range. For National Instruments cards, the frequency must satisfy the following inequality: (Maximum Counter Output Frequency/Max Number of Counts) <= frequency <= (Maximum Counter Output Frequency/4).

The process does not have permission to create global shared memory. On Vista and later operating systems, creation of global shared memory requires SeCreateGlobalPrivilege. This privilege is only enabled by default for administrators, services and the local system account. Try adding the local=yes option to the URI e.g. "shmem://mymem:1?local=yes".

Device did not send an acknowledgement. Device may not be present or an error may have occurred.

You do not have a valid license for the Altia blockset. To configure licensing use the Configure License utility found under Start Menu/All Programs/Quanser for your product.

An arithmetic table was not defined.

An attempt was made to pop a cancellation handler when no cancellation handler was pushed on the stack!

No suitable codec was found to encode or decode the content.

You do not have a valid license for the Quanser Communications blockset. To configure licensing use the Configure License utility found under Start Menu/All Programs/Quanser for your product.

There is no corresponding Internet address for the given MAC address.

There is no corresponding network card for the given MAC address.

A communication protocol is being used that sends and receives data at the same time, such as SPI, and there is no data in the stream's receive buffer to receive. A send/flush operation should be done first. The send/flush will receive data at the same time as data is sent and fill the receive buffer so that data can be received.

There is no data to send. It is not possible to send zero-length arrays. If data will never be sent then configure the send options to not send data at all. Setting the enable input to false is not enough because the enable input is only intended to temporarily enable or disable transmission. If the stream is configured to send data then a valid data type must be connected even if the enable input is false.

You do not have a valid license for the Denso blockset. To configure licensing use the Configure License utility found under Start Menu/All Programs/Quanser for your product.

An attempt was made to send data when no connection has been established with a particular peer. For connectionless protocols like UDP the server-side must receive data from a peer before sending any data in order to establish a "connection".

The operation cannot be performed because no destination has been configured for the operation.

The device is not available. Check that the device is plugged in or has not been reset.

No device address was specified. See the options for the communications protocol.

You do not have a valid license for using third-party devices in normal simulation. To configure licensing use the Configure License utility found under Start Menu/All Programs/Quanser for your product.

You do not have a valid license for the Dynamic Reconfiguration blockset. To configure licensing use the Configure License utility found under Start Menu/All Programs/Quanser for your product.

You do not have a valid license for the NI ELVIS III you are using. Make sure you install QUARC with a license file that has NI ELVIS III support, and then run NI MAX to install QUARC on the NI ELVIS III.

NoError

You do not have a valid license for the EtherCAT blockset. To configure licensing use the Configure License utility found under Start Menu/All Programs/Quanser for your product.

The end of the file could not be determined.

You do not have a valid license for the Force Dimension blockset. To configure licensing use the Configure License utility found under Start Menu/All Programs/Quanser for your product.

There are no game controllers currently attached to the system.

You do not have a valid license for the GPS blockset. To configure licensing use the Configure License utility found under Start Menu/All Programs/Quanser for your product.

The connection to the HIL simulation or HIL Proxy Server was refused. If using a simulated device, make sure the simulation is running.

A Huffman table was not defined.

You do not have a valid license for the IRobot Roomba blockset. To configure licensing use the Configure License utility found under Start Menu/All Programs/Quanser for your product.

A noise error occurred

You do not have a valid license for the JR3 Force/Torque Sensor blockset. To configure licensing use the Configure License utility found under Start Menu/All Programs/Quanser for your product.

No Kinect sensor was detected with the given index or identifier.

You do not have a valid license for the KUKA robots blockset. To configure licensing use the Configure License utility found under Start Menu/All Programs/Quanser for your product.

You do not have a valid license for the Mitsubishi PA-10 blockset. To configure licensing use the Configure License utility found under Start Menu/All Programs/Quanser for your product.

The EtherCAT master puts a limit on the number of packets which may be queued for transmission. This limit has been exceeded so no more packets are available.

You do not have a valid license for the NaturalPoint OptiTrack blockset. To configure licensing use the Configure License utility found under Start Menu/All Programs/Quanser for your product.

Non-blocking mode is not supported for the given protocol.

You do not have a valid license for the Nintendo Wiimote blockset. To configure licensing use the Configure License utility found under Start Menu/All Programs/Quanser for your product.

You do not have a valid license for the Novint Falcon blockset. To configure licensing use the Configure License utility found under Start Menu/All Programs/Quanser for your product.

No password to set or clear.

The process lacks the appropriate privileges to perform the operation. If you are downloading a model then the model may be loaded on the target. Stop the model and download the code again. If you are uploading a MAT file then the host and target are likely the same machine and the operation would overwrite the MAT file with itself.

You do not have a valid license for the Phantom Desktop blockset. To configure licensing use the Configure License utility found under Start Menu/All Programs/Quanser for your product.

You do not have a valid license for the Phantom Omni blockset. To configure licensing use the Configure License utility found under Start Menu/All Programs/Quanser for your product.

You do not have a valid license for the Phantom Premium 6DOF blockset. To configure licensing use the Configure License utility found under Start Menu/All Programs/Quanser for your product.

You do not have a valid license for the Phantom Premium blockset. To configure licensing use the Configure License utility found under Start Menu/All Programs/Quanser for your product.

You do not have a valid license for the Point Grey Research Cameras blockset. To configure licensing use the Configure License utility found under Start Menu/All Programs/Quanser for your product.

You do not have a valid license for the PTI VisualEyez blockset. To configure licensing use the Configure License utility found under Start Menu/All Programs/Quanser for your product.

You do not have a valid license for the Qbot vehicle. To configure licensing use the Configure License utility found under Start Menu/All Programs/Quanser for your product.

A quantization table was not defined.

No reference scan has been set. A scan match cannot be performed.

You do not have a valid license for the Rexroth HyMotion-11000 blockset. To configure licensing use the Configure License utility found under Start Menu/All Programs/Quanser for your product.

You do not have a valid license for the myRIO or generic NI ELVIS III board. Make sure you install QUARC with a license file that has myRIO or generic NI ELVIS III board support, and then run NI MAX to install QUARC on the myRIO or NI ELVIS III.

You do not have a valid license for the Robotics blockset you are using. To configure licensing use the Configure License utility found under Start Menu/All Programs/Quanser for your product.

A communication protocol is being used that sends and receives data at the same time, such as SPI, and there is no room in the stream's receive buffer for the data that will be received during the send/flush operation.

The RPC server is unavailable so the beep cannot be sounded. This problem has been seen on laptops running Vista.

You do not have a valid license for the Schunk Gripper blockset. To configure licensing use the Configure License utility found under Start Menu/All Programs/Quanser for your product.

You do not have a valid license for the SensAble Omni blockset. To configure licensing use the Configure License utility found under Start Menu/All Programs/Quanser for your product.

You do not have a valid license for the QUARC Simulink Development Environment. To configure licensing use the Configure License utility found under Start Menu/All Programs/Quanser for your product.

The SOS marker is missing. The file structure is invalid.

There is no space left on the file system.

No SPI chip select signal was chosen using the frame or slave options of the URI. The current hardware requires that a chip select be used.

No such device or address

The SPI port specified in the URI is not available.

A component of the path isn't a directory.

The server to which a connection was attempted is not a HIL proxy server or HIL simulation.

The calling thread does not support setting the cancellation state of the thread. The thread was not created with qthread_create.

The operation is not supported because the socket is not a SOCK_STREAM socket.

The specified option or operation is not supported. It may be supported on other platforms. Please check the documentation.

The server to which a connection was attempted is not a Video3D proxy server or Video3D simulation.

The server to which a connection was attempted is not a Video proxy server or Video simulation.

You do not have a valid license for the UAV components. To configure licensing use the Configure License utility found under Start Menu/All Programs/Quanser for your product.

No Ublox message

You do not have a valid license for the Vicon blockset. To configure licensing use the Configure License utility found under Start Menu/All Programs/Quanser for your product.

You do not have a valid license for the Visualization blockset. To configure licensing use the Configure License utility found under Start Menu/All Programs/Quanser for your product.

The TrackIR head tracker failed to initialize. Make sure that TrackIR is running and the Quanser Device ID is registered. Make sure the PATH environment variable is set correctly.

The number of columns of the matrix in the file is too small for the total columns implied by the parameters.

The number of rows of the matrix in the file is too small for the total rows implied by the parameters.

NumErrors

The object was already initialized and cannot be re-initialized.

The object could not be found.

Only the I2C master mode is supported by the device being used for I2C communications. Different hardware is required for slave mode.

Only the SPI master mode is supported by the device being used for SPI communications. Different hardware is required for slave mode.

The SPI device specified in the URI only supports sending and receiving the most-significant bit first.

The operation argument to a board-specific HIL driver is NULL. This situation should never occur unless the user is calling the board-specific driver directly or memory has been corrupted.

A blocking socket operation is currently in progress.

The operation is not complete. It is still pending. This error should never be returned by any function to the user.

An error occurred starting the OptiTrack camera system. Make sure they are properly connected.

An error occurred stopping the OptiTrack camera system.

An attempt to process frames from Optitrack failed. See the QUARC console for additional information.

Unable to load OptiTrack calibration file. Make sure the file path is correct or the calibration file is compatible with the Motive software version that you have installed.

The license for the Optitrack tools being used is invalid or missing. Make sure you have configured your license.

Unable to load Motive user profile file. Make sure the file path is correct.

Unable to load OptiTrack rigid body definition file. Make sure the file path is correct.

The Motive library failed to open. Make sure you have the Motive software installed and the appropriate environment variables (refer to the device help page) set correctly.

Unable to initialize the OptiTrack Point Cloud API. Make sure the proper software is installed and the path variable is set.

The rigid body ID is invalid or not found in the rigid body definition file. Valid IDs are integers ranging from 1 to 1024.

Unable to initialize the OptiTrack Rigid Body API. Make sure the proper software is installed and the path variable is set.

The number of specified OptiTrack rigid bodies exceeds the number of objects in the rigid body definition file.

The required Motive API is not available. Make sure you have the correct version of the Motive software installed. E.g. older Motive software does not support loading of user profile (.xml or .motive) file and must use trackable (.tra) file for rigid bodies definitions.

The specified rigid body definition is not supported. Currently only .xml, .motive, and .tra files are supported.

Error was returned from the underlying OS-specific layer.

This board only supports resetting the other outputs to zero when the watchdog expires.

Other input channels are not supported by this board.

Other output channels are not supported by this board.

An attempt was made to write an other output value that is Not-a-Number (NaN).

The socket does not support receiving out-of-band data in the normal stream.

Not enough memory to perform the operation.

A value is outside the valid range.

There are not enough system resources to perform the requested operation. Try rebooting, requesting fewer samples, or adding more memory to your machine.

Not enough system resources are available to perform the operation.

An overrun error occurred

Oversampling has been detected. The sampling rate is too fast and cannot be maintained.

A page fault occurred accessing one of the arguments.

A parity error occurred

The selected serial port does not support parity checking. Set the parity option on the URI to 'none'.

The value specified for the parity is not supported by the given serial port. Use a different parity setting if possible or select 'none' for no parity checking.

The partitioning scheduler is not running. Be sure to set up your system to run the partitioning scheduler before attempting to use it.

The specified partition could not be found. Make sure you have created the partition and have enabled the appropriate scheduler.

The form of the pipe URI must be pipe:name or pipe://server/name. The name cannot contain forward or backward slashes.

The given protocol does not support paths in the URI. Separate options from the hostname and port using a '?' rather than a '/', much like an HTTP query.

The Peak CAN device failed to initialize. Make sure the device is connected properly and the drivers and API have been installed.

The channel number specified for the Peak CAN device is not valid. Make sure the correct device type is selected and the channel number is valid.

The Peak CAN device failed to set the message filter. Make sure the message IDs requested are valid.

The Peak CAN device failed to write a message. Make sure you are connected to a CAN network with proper CAN bus termination resistance and that your baud rate is correct.

The protocol data unit (PDU) is too small to handle the data required.

The total data exceeds the PDU size.

The connection was closed by the peer. The stream should be closed.

The peer is not responding to the connection being shut down. The receive operation has timed out.

A peripheral device could not be found. It is possible the device is unplugged or otherwise inoperable.

An error occurred while attempting to close the PGR camera.

An error occurred while attempting to grab an image using the PGR camera.

An error occurred while attempting to initialize the PGR camera.

A timeout occurred while attempting to grab an image using the PGR camera.

Starting the camera failed because the custom image size is invalid.

The dimensions of the image are not valid. The image must have 3 dimensions.

Phantom block cannot close the device.

Phantom block cannot initialize the device.

The SensAble PHANToM library failed to open. Make sure you have the OpenHaptics and PHANToM Device Driver software installed and the system PATH is set correctly.

The specified PHANTOM Omni board could not be opened. Check that the device is powered and properly connected and that the board number is correct.

Phantom block cannot read the outputs of the device.

Phantom block cannot start the Phantom API scheduler.

Phantom API scheduler rate error.

Phantom block cannot write to inputs of the device.

The PLC is already running.

The PLC has already been stopped.

Unable to listen on the specified port. The port is already in use.

The port is unreachable. For UDP datagrams, a previous send operation resulted in an ICMP Port Unreachable message, indicating that there is likely no server listening on the UDP port.

The specified preference node could not be found.

The path for the preferences node is too long.

The preferences value contains environment variable references, which cannot be expanded.

The end of the file was encountered prematurely. The file is corrupt.

The "number written" argument to a stream_print function is NULL. It must point to an appropriately-sized integer.

The specified model process could not be stopped.

The specified model process could not be found.

The product code specified could not be found in the license file.

The property is read-only. It cannot be set.

One or more of the specified properties were not recognized by the board-specific driver.

The specified property is not supported.

The buffer for the underlying communication protocol is too small to send or receive the data requested. Try using the sndsize, rcvsize, bufsize or memsize options of the URI to increase the requisite buffer size.

Support for the given protocol type does not appear to be installed. Verify that you have entered the correct URI for the Stream blocks or stream_connect/stream_listen functions.

The persistent stream has not been configured for variable-size signals in the direction attempted.

The persistent stream has been configured for variable-size signals in the direction attempted.

The VZAnalyzer device failed to initialize. Make sure the VZAnalyzer software is installed.

The VZSoft device failed to initialize. Make sure the system is setup properly and the VZSoft software is installed.

One of the PWM output channels specified does not support the given PWM alignment.

One of the PWM output channels specified does not support the given PWM output configuration. For example, channel 7 of the QPID cannot be used in the complementary configuration as the primary channel because it is the last PWM channel. Alternatively, the given configuration may not be supported by the card at all.

An attempt was made to set the PWM deadband to a value that is Not-a-Number (NaN).

One of the PWM output channels specified does not support the given PWM deadband.

An attempt was made to set the PWM duty cycle to a value that is Not-a-Number (NaN).

Some of the PWM output expiration states have not been configured. This board requires that if any of the expiration states have been configured then all the states must be configured, and the "Set PWM outputs when a watchdog timer expires" must be enabled.

This board only supports resetting the PWM outputs to zero when the watchdog expires.

An attempt was made to set the PWM frequency to a value that is Not-a-Number (NaN).

The specified PWM mode is not supported by this board.

At least one PWM channel is in a mode that is incompatible with the other PWM channels. The current card has restrictions on the PWM modes. For example, the card may share the PWM period among all the channels so using duty cycle or time mode along with frequency or period mode is not permitted. See the card's documentation for details.

At least one PWM channel is in one-shot mode, while others are not. The current card requires that all PWM channels be configured in one-shot mode, if this mode is used, not just some of the channels.

PWM output channels are not supported by this board.

An attempt was made to write a PWM output value that is Not-a-Number (NaN).

The requested PWM output is locked. If you need access to this channel, use the generic version of this driver.

One of the PWM output channels specified does not support the given PWM polarity.

The specified Q3 ControlPaQ-FW board could not be opened. Check that the board is powered and properly connected and that the board number is correct.

Some of the analog or digital output expiration states have not been configured. The Q8-series of boards requires that all analog and digital output channels be configured to be reset on watchdog expiration, not just some of the channels.

Communication to the End Effector board has been lost or corrupted. Please turn off the arm device and check the cable connection.

Communication to the Gripper motor has been lost or corrupted. Please turn off the arm device and check the motor's cable connection.

Communication to the Yaw motor has been lost or corrupted. Please power cycle the arm and contact your local Quanser support team if the issue continues.

Communication to the Master Shoulder motor has been lost or corrupted. Please power cycle the arm and contact your local Quanser support team if the issue continues.

Communication to the Slave Shoulder motor has been lost or corrupted. Please power cycle the arm and contact your local Quanser support team if the issue continues.

Communication to the Elbow motor has been lost or corrupted. Please power cycle the arm and contact your local Quanser support team if the issue continues.

Communication to the Wrist motor has been lost or corrupted. Please power cycle the arm and contact your local Quanser support team if the issue continues.

Detected an electrical shock on the Gripper motor's circuit or insufficient power to operate the motor. Please power cycle the arm and contact your local Quanser support team if the issue continues.

Detected an electrical shock on the Yaw motor's circuit or insufficient power to operate the motor. Please power cycle the arm and contact your local Quanser support team if the issue continues.

Detected an electrical shock on the Master Shoulder motor's circuit or insufficient power to operate the motor. Please power cycle the arm and contact your local Quanser support team if the issue continues.

Detected an electrical shock on the Slave Shoulder motor's circuit or insufficient power to operate the motor. Please power cycle the arm and contact your local Quanser support team if the issue continues.

Detected an electrical shock on the Elbow motor's circuit or insufficient power to operate the motor. Please power cycle the arm and contact your local Quanser support team if the issue continues.

Detected an electrical shock on the Wrist motor's circuit or insufficient power to operate the motor. Please power cycle the arm and contact your local Quanser support team if the issue continues.

Input voltage of the Gripper motor exceeded the configured operating voltage. Please power cycle the arm and contact your local Quanser support team if the issue continues.

Input voltage of the Yaw motor exceeded the configured operating voltage. Please power cycle the arm and contact your local Quanser support team if the issue continues.

Input voltage of the Master Shoulder motor exceeded the configured operating voltage. Please power cycle the arm and contact your local Quanser support team if the issue continues.

Input voltage of the Slave Shoulder motor exceeded the configured operating voltage. Please power cycle the arm and contact your local Quanser support team if the issue continues.

Input voltage of the Elbow motor exceeded the configured operating voltage. Please power cycle the arm and contact your local Quanser support team if the issue continues.

Input voltage of the Wrist motor exceeded the configured operating voltage. Please power cycle the arm and contact your local Quanser support team if the issue continues.

Detected a malfunction of the Gripper motor's encoder. Please contact your local Quanser support team.

Detected a malfunction of the Yaw motor's encoder. Please contact your local Quanser support team.

Detected a malfunction of the Master Shoulder motor's encoder. Please contact your local Quanser support team.

Detected a malfunction of the Slave Shoulder motor's encoder. Please contact your local Quanser support team.

Detected a malfunction of the Elbow motor's encoder. Please contact your local Quanser support team.

Detected a malfunction of the Wrist motor's encoder. Please contact your local Quanser support team.

Internal temperature of the Gripper motor has exceeded the configured operating temperature. Please turn off the arm and allow the motor to cool for at least 20 minutes.

Internal temperature of the Yaw motor has exceeded the configured operating temperature. Please turn off the arm and allow the motor to cool for at least 20 minutes.

Internal temperature of the Master Shoulder motor has exceeded the configured operating temperature. Please turn off the arm and allow the motor to cool for at least 20 minutes.

Internal temperature of the Slave Shoulder motor has exceeded the configured operating temperature. Please turn off the arm and allow the motor to cool for at least 20 minutes.

Internal temperature of the Elbow motor has exceeded the configured operating temperature. Please turn off the arm and allow the motor to cool for at least 20 minutes.

Internal temperature of the Wrist motor has exceeded the configured operating temperature. Please turn off the arm and allow the motor to cool for at least 20 minutes.

Detected a persistent load that exceeded the maximum output rating of the Gripper motor. Please turn off the arm and apply a lighter load to the motor.

Detected a persistent load that exceeded the maximum output rating of the Yaw motor. Please turn off the arm and apply a lighter load to the motor.

Detected a persistent load that exceeded the maximum output rating of the Master Shoulder motor. Please turn off the arm and apply a lighter load to the motor.

Detected a persistent load that exceeded the maximum output rating of the Slave Shoulder motor. Please turn off the arm and apply a lighter load to the motor.

Detected a persistent load that exceeded the maximum output rating of the Elbow motor. Please turn off the arm and apply a lighter load to the motor.

Detected a persistent load that exceeded the maximum output rating of the Wrist motor. Please turn off the arm and apply a lighter load to the motor.

No QBus modules could be detected.

An unrecognized QBus module was found.

Variable values cannot be set until the visualization task has been started. Use the Visualization Start Task VI to start the task.

The ranging sensor could not detect the range due to an error.

The driver could not determine the chassis attached to the real-time controller.

The NI chassis currently in use is not supported by this particular driver. Check the documentation to ensure a compatible chassis is in use.

One or more of the modules in the NI chassis do not match the hardware configuration selected in the HIL Initialize. Be sure the correct modules are being used. Please correct the hardware configuration or select the proper configuration in the HIL Initialize block.

The sample time is not valid for the Sigmoid VI.

The Smooth Signal Generator does not support the amplitude entered.

The Smooth Signal Generator does not support the frequency entered.

The input array sizes should be equal and non-zero for the Smooth Signal Generator.

The module in the NI chassis required for the selected channels of analog input is missing.

The module in the NI chassis required for the selected channels of analog output is missing. Make sure these channels are not being written by the HIL Initialize block by unchecking the Initial and Final output fields of the Analog Outputs tab.

The module in the NI chassis required for the selected channels of digital input is missing.

The module in the NI chassis required for the selected channels of digital output is missing. Make sure these channels are not being written by the HIL Initialize block by unchecking the Initial and Final output fields of the Digital I/O tab.

The module in the NI chassis required for the selected channels of encoder input is missing.

One or more of the modules in the NI chassis that is required by the hardware configuration selected in the HIL Initialize is missing. Please correct the hardware configuration or select the proper configuration in the HIL Initialize block.

The module in the NI chassis required for the selected channels of other input is missing.

The module in the NI chassis required for the selected channels of other output is missing. Make sure these channels are not being written by the HIL Initialize block by unchecking the Initial and Final output fields of the Other Outputs tab.

The module in the NI chassis required for the selected channels of PWM output is missing. Make sure these channels are not being written by the HIL Initialize block by unchecking the Initial and Final output fields of the PWM Outputs tab.

One or more of the modules in the NI chassis is causing an error which prevents I/O from being performed.

An attempt was made to read from a write-only stream.

An attempt was made to read from a write-only task.

The amount of data requested in a read operation is too long. For example, you cannot read more bytes from a circular buffer than are contained in the buffer.

An attempt has been made to remove the last URI upon which the target is serving. To avoid leaving no means to connect to the target, the last URI may not be removed. The target must serve on at least one URI.

It is not possible to remove the URI associated with the current connection to the target.

The selected image resolution is not supported.

The desired resource is already in use for another operation.

A required resource was not initialized.

The program on the robostix has an invalid version information (i.e., is either too old or too new).

The ROS system is inaccessible.

There was a problem initializing ROS.

The ROS master indicates that the ROS master API was called with caller error. In general, this means that the master/slave did not attempt to execute the action.

The ROS master indicates that the ROS master API failed to complete completely. In general, this means that the master/slave attempted the action and failed, and there may have been side-effects as a result.

The ROS node is not valid. It may not have been made active during normal simulation in the ROS Initialize block and thus may be uninitialized.

The ROS system is shutdown.

Samples were lost or corrupted because the device cannot keep up. The sampling frequency is too fast or too many samples have been requested. Try fewer samples or a slower sampling frequency.

Failed to save IplImage using.

The given scale factor is not currently supported.

The scaling of the width and height is not the same. The aspect ratio will be changed, which is not currently supported.

An argument passed to a stream_scan function to store a value scanned is NULL. Arguments must contain the address of appropriately typed quantities.

An error occurred while attempting to close the SCHUNK gripper device.

Cannot halt the SCHUNK gripper device.

Cannot home the SCHUNK gripper device.

An error occurred initializing the SCHUNK gripper device.

An error occurred attempting to issue a current command to the SCHUNK gripper device.

An error occurred attempting to issue a move command to the SCHUNK gripper device.

An error occurred attempting to issue a velocity command to the SCHUNK gripper device.

The 'mode' input signal must be connected when the Control mode external parameter is set.

The specified control mode for the Schunk gripper is invalid.

The named semaphore already exists.

A semaphore's maximum count has been reached. The semaphore cannot be signaled.

The named semaphore could not be found.

The Sensoray board failed to access its EEPROM during initialization. Try unregistering the board and re-registering it. If the error persists, then the problem is likely a hardware fault.

An illegal parameter was passed to the Sensoray driver.

The Sensoray driver supports a maximum of 16 boards.

The Sensoray board has experienced an unspecified fault.

The specified sensor type is not currently supported.

The SerAccel could not be opened. Make sure the SerAccel is connected and set to binary mode.

The SerAccel could not be read.

The SerAccel could not be started.

The process cannot access the file or object because it is being used by another process.

The socket address could not be made reusable.

The socket library has not been initialized.

There are too many SOF markers. The file structure is invalid.

The SOF marker type is not supported.

Another version of the software is already installed. Please uninstall the other version first.

The selected serial port does not support software flow control. Set the flow option on the URI to 'none' or 'hardware' (if supported).

There are too many SOI markers. The file structure is invalid.

An SOS marker occurred before an SOF marker. The file structure is invalid.

Whitespace may not precede the <?xml ...> declaration in the XML file.

Sparse matrices are not currently supported.

The given buffer is too small to do a single send or receive for this protocol. The protocol uses a word length larger than the number of bytes supplied.

A receive error occured using the Serial Peripheral Interface (SPI) protocol.

A transmit error occured using the Serial Peripheral Interface (SPI) protocol.

The number of bytes being sent or received is not an integer multiple of the natural word size (1 bytes for 1-8 bits, 2 bytes for 9-16 bits and 4 bytes for 17-32 bit word lengths).

An internal stack overflowed.

An internal stack underflowed.

A stall condition was detected. Please ensure that your device is free to move and is functioning properly.

The state information is not compatible. Reconfiguration states must have the same data type and size.

The state argument is NULL. It should be a valid pointer.

The value specified for the stop bits is not supported by the given serial port. Use a different number of stop bits if possible. A value of 1 is recommended.

The stream buffer is too small to send or receive units of the given size.

The character format of the stream can only be deduced from the first bytes in the stream.

The non-blocking stream is in the process of connecting but is not yet connected. The stream_poll function or Stream Poll block must be invoked with the connect flag to complete the connection.

The string buffer passed as an argument is NULL.

The string is not null-terminated within the given size.

The string buffer is too small to hold the result.

The sum of the leading and trailing deadbands exceeds the PWM period. The deadbands cannot be so large that they exceed the PWM period.

Tags are not allowed within attribute values. Use < to put a '<' in an attribute value.

The task argument to a HIL function is NULL.

TCP/IP keep alive packets on individual socket connections does not appear to be supported.

Text matrices are not currently supported.

The selected colorization theme is incompatible with decolorization. Please choose a different theme.

Setting the thread CPU affinity is not currently available on this platform.

A Timebase block has already been registered. Only one Timebase block may be present in the model.

A Timebase block has not been registered.

The operation timed out.

Not enough data was supplied.

Too many analog input channels were specified.

Too many analog output channels were specified.

Too many clocks were specified.

Too many CUDA blocks were used with a cooperative kernel.

Too many digital input channels were specified.

Too many digital output channels were specified.

Too many encoder input channels were specified.

It is not possible to add another force feedback effect because the maximum number of force feedback effects has already been reached. Change the maximum number of force feedback effects in the Host Force Feedback Game Controller block.

No more than six axes may be specified for a game controller force effect.

Too many interrupt sources were specified.

Too many symbolic links or prefixes.

Too many other input channels were specified.

Too many other output channels were specified.

There are too many points specified for the algorithm to process. Resource or computation limits would be exceeded.

Too many processes are accessing an RTDLL.

Too many properties were specified.

Too many PWM output channels were specified.

There were too many color components to quantize.

The number of samples requested in the read or write operation is more than the number of samples being buffered by the task. Increase the buffer size for the task or read or write fewer samples.

There are too many telemetry bits set in DSHOT commands. When multiple ESC channels share a single telemetry line, only one channel may perform a telemetry request at one time.

There are too may items (>20) in multivariable read/write.

The UTF-16 character may be valid but the given length is too small to contain it.

The UTF-32 character may be valid but the given length is too small to contain it.

The UTF-8 character may be valid but the given length is too small to contain it.

It was not possible to close the operating system specific kernel-level driver. The driver handle may be invalid. For example, the device may have already been closed or memory may have been corrupted.

Unable to get CUDA function from kernel. The mangled function name is likely incorrect.

Unable to load CUDA kernel. The installed CUDA version may be incompatible with the CUDA code.

It was not possible to get exclusive access to the device. The operation has been aborted.

The underlying operating system could not open the dialog.

An operating system specific kernel-level driver for the card was found but could not be loaded. There may be a device conflict, hardware problem, or the driver may not be correctly installed.

Unable to program firmware.

The Quanser 3D Viewer could not be started.

Unexpected null character in the input stream.

Unexpected question mark in the input stream.

The specified board type is not recognized. Please install the board-specific HIL driver for this board type.

An operating system function returned an unrecognized error.

The record type is unrecognized.

An unrecoverable error occurred. The application will need to be re-run.

The audio format is not supported. This may be due to a missing audio codec on some targets.

The given serial baud rate is not supported.

Unsupported Ublox GPS data field

The I2C protocol for the selected target only supports combined write-read messages. Other combinations of read and write operations are not supported in exclusive mode.

Conversion between the two image formats selected is not currently supported.

The requested ROS protocol is not supported. Currently this node only supports TCPROS and UDPROS protocols.

The video format is not supported. This may be due to the frame rate, frame size or native video formats of the device or source.

Markup that is currently unsupported was found in the XML file.

An XML attribute value string is not terminated.

A comment in the XML file was not terminated.

An XML element was not terminated properly.

The upload sequence failed.

The hostname specified in the URI is too long.

The hostname is missing from the URI. Although a hostname is not required for all URIs, the fact that you are getting this message indicates that it is required in this circumstance.

The specified URI could not be found.

An option specified in the URI was not recognized as a valid option.

The option name for a URI is too long. Option names must not be longer than URI_MAX_OPTION_LENGTH.

The scheme specified in the URI is too long.

Cannot claim the device's USB interface. Try power cycle the device or use another USB port.

Cannot find the USB device. Make sure the device is connected and powered (if it's a powered device).

Cannot get the device's USB configuration descriptor. Try power cycle the device or use another USB port.

Cannot get device's USB endpoint. Try power cycle the device or use another USB port.

USB library cannot be initialized. Try power cycle the device or use another USB port.

Cannot open the device. Try power cycle the device or use another USB port.

The config descriptor is not compatible. Try power cycle the device or use another USB port.

Failed to close the video driver.

The specified video device could not be found.

The image format is not valid for the device.

The device does not support video capture.

The device does not support video streaming.

Unable to query the video driver for its status.

Failed to enqueue a buffer with the video driver's incoming queue.

Failed to initiate memory-mapped or user-pointer I/O for the video device.

Failed to start or stop video capture or streaming.

Failed to open the Qbot VAL driver.

The variable has already been selected in the scene. Variables cannot be selected more than once.

The requested variable could not be found.

The given variable has not been selected for animation. Use the Visualization Select Variable VI to select the variable for animation prior to starting the visualization task.

Variable-step solvers are not supported by this block.

The version object passed as a parameter is NULL.

Cannot connect to the Vicon DataStream server. Check that the host name is correct and that the Tracker software is running.

The Vicon system failed to enable the marker data stream. Make sure your system is connected and the Tracker software is running.

The Vicon system failed to enable the segment data stream. Make sure your system is connected and the Tracker software is running.

The Vicon system failed to enable the unlabeled marker data stream. Make sure your system is connected and the Tracker software is running.

The Vicon system failed to set the specified stream mode. Ensure the stream mode is valid and the Tracker software is running.

The Quanser 3D Viewer may not have exited. An unexpected error may have occurred.

The virtual array controller is confused.

Attempted to attach a mesh that is outside of the array bounds of loaded meshes.

Internal error. Failed attempted to attach a mesh to an actor because the mesh pool is not initialized.

Attempted to attach a texture that is outside of the array bounds of loaded textures.

Internal error. Failed attempted to attach a mesh to an actor because the texture pool is not initialized.

Could not create a rendering context for the requested OpenGL version (%1.1f). A different OpenGL version or updating your video drivers may resolve the issue.

An error occured creating the frame-rate timer.

Cannot create OpenGL context.