Error Codes (Robotics Module)

LabVIEW 2011 Robotics Module Help

Edition Date: June 2011

Part Number: 372983B-01

»View Product Info

The Robotics VIs can return the following error codes. Refer to the KnowledgeBase for more information about correcting errors in LabVIEW.

Code	Description
–310253	You cannot run the robotics simulator on a real-time target. Remove any code that initializes a simulated Starter Kit robot before you deploy this VI to the RT target.
–310252	The robot sensor or actuator is invalid. Make sure you use the appropriate initialization VI from the Starter Kit palette to begin communicating with the robot.
–310251	The interface with the Starter Kit FPGA is invalid. Make sure you use the appropriate initialization VI from the Starter Kit palette to begin communicating with the robot.
–310207	The converter VI cannot export the output file correctly.
–310206	This VI supports exporting to .lvsg and .ive file formats only.
–310205	The Input Path control is empty. You must specify the path to the file you want to load and convert.
–310204	The converter VI cannot load the file at the Input Path correctly. Make sure the file is not corrupt and try to load it again.
–310203	This VI supports input files of only .dae, .lvsg, and *.ive file formats.
–310202	The Input Path control is empty. You must specify the path to the file you want to load and convert.
–310201	The simulation step size must be greater than 0. National Instruments recommends step sizes of 5 to 20 ms.
–310200	The manifest file does not exist at the path you specified. Make sure you specify a valid path to a manifest file.
–310199	The simulator cannot find an .stl file that the manifest file references. To correct this error, use the Offline Configuration VIs to read and modify the path to the .stl file in the manifest file.
–310198	The component ID you specified does not correspond to any components in the manifest file for this simulation instance.
–310197	The obstacle ID you specified does not correspond to any obstacles in the manifest file for this simulation instance.
–310196	The robot ID you specified does not correspond to any robots in the manifest file for this simulation instance.
–310195	The input manifest file is not valid. Use the Robotics Environment Simulator Wizard or the VIs on the Offline Configuration palette to generate valid manifest files.
–310194	The actuator ID you specified does not correspond to any actuators associated with the robot ID in the manifest file for this simulation instance.
–310193	The sensor ID you specified does not correspond to any sensors associated with the robot ID in the manifest file for this simulation instance.
–310192	The robotics simulator is already running another simulation program. You can run only one simulation program at a time.
–310191	The robotics simulator is not correctly initialized. Make sure the Start Simulator Service VI runs before any initialization driver VIs for simulated sensors or actuators.
−310132	The type of the input sentence does not match the Parse GPS Sentence VI polymorphic instance you selected. Make sure you select the correct polymorphic instance for the type of the sentence you want to parse.
−310131	The input sentence contains formatting that makes the sentence invalid. For example, an NMEA sentence must begin with $, contain an * followed by a valid checksum, and be less than 83 characters in length.
−310130	The input text contains none of the GPS data points the Get GPS Data VI returns.
−310120	No available headings for travel exist because obstacles within the distance threshold of the vehicle block all possible headings.
−310085	The wheel radius is invalid. The radius must be a positive, non-zero value.
−310084	You cannot replace wheels in a built-in steering frame, such as a differential steering frame, because different wheel types are inconsistent with the definition of that steering frame type.
−310083	The motor communication session is invalid. Use the Initialize Motor Communication VI to generate a valid LabVIEW class object.
−310082	The steering frame is invalid. Steering frames must contain at least one wheel.
−310081	You cannot remove wheels from the built-in steering frame, such as a differential steering frame, because fewer wheels are inconsistent with the definition of that steering frame type.
−310080	You cannot add wheels to a built-in steering frame, such as a differential steering frame, because additional wheels are inconsistent with the definition of that steering frame type.
−310044	The transform is formatted incorrectly. A valid transform is a 4-by-4 matrix with a last row in the form of [0 0 0 1].
−310043	The dynamic parameters you specified are not within the range of valid values. For example, the mass of a link cannot be a negative value. Make sure the values you specify are valid.
−310042	The kinematic parameters you specified are not within the range of valid values. Make sure the values you specify are valid.
−310041	The number of elements in the joint position, joint velocity, or joint acceleration array is not equal to the number of links in the serial arm. Make sure the number of elements in the array matches the number of links in the arm.
−310040	LabVIEW cannot converge to a solution in the number of steps you specified. Make sure that the serial arm can achieve the transform you desire.
−310021	The map contains nodes that are not compatible with the AD* VIs. Use the A* VI instead or update the map to use supported nodes.
−310020	No valid paths exist between the start reference and the goal reference.
−310004	The cell costs in the occupancy grid must all be greater than or equal to 0. Make sure all values in the occupancy grid array input are greater than or equal to 0.
−310003	You cannot set a cell or edge cost to be less than 0. Set the cost to a value greater than or equal to 0.
−310002	The x- and y-coordinates you specified refer to a cell outside of the occupancy grid map. Make sure you specify coordinates for a cell within the map.
−310001	The reference to the map node you specified is null or does not refer to a valid node.
−310000	The coordinate sizes of the two nodes do not match. Make sure you specify node coordinates with the same number of dimensions.
310000	LabVIEW ignored the request because the start node and end node specified for the edge are the same node.
310001	You set a cell or edge cost to 0, which might yield unexpected results in path planning applications. Set costs to values greater than 0 to help prevent unexpected results.
310002	One or more cell costs in the occupancy grid is 0, which might yield unexpected results in path planning applications. Set costs to values greater than 0 to help prevent unexpected results.
310080	LabVIEW coerced the steering angle of the wheel to meet the kinematic constraints of the wheel.
310081	The type of wheel used for this operation does not match the expected type. LabVIEW might return incomplete or unexpected values if the wheel does not contain expected data.
310130	The input text contained some but not all of the GPS data points the Get GPS Data VI returns.
310131	The input sentence contains an unexpected value. For example, the GGA polymorphic instance of the Parse GPS Sentence VI expects readings of height above mean sea level to be specified in meters.
310132	The sentence index of the input sentence is greater than the number of sentences the input sentence specifies is possible.
310250	You cannot write to a digital I/O line on a simulated robot.
310251	You cannot read the state of a digital I/O line on a simulated robot.
310252	You cannot write to a pulse width modulation (PWM) line on a simulated robot.
310253	You cannot write to an analog output line on a simulated robot.
310254	You cannot read the state of an analog input line on a simulated robot.