Error Codes
- Updated2023-02-21
- 13 minute(s) read
The DeviceNet VIs can return the following error codes. Refer to the KnowledgeBase for more information about correcting errors in LabVIEW.
| Code | Description |
|---|---|
| −2147136510 | Board self test failed (code 2). Solution: Try to reinstall the driver or switch the slot(s) of the board(s). If the error persists, contact National Instruments. |
| −2147136509 | Board self test failed (code 3). Solution: Try to reinstall the driver or switch the slot(s) of the board(s). If the error persists, contact National Instruments. |
| −2147136508 | Board self test failed (code 4). Solution: Try to reinstall the driver or switch the slot(s) of the board(s). If the error persists, contact National Instruments. |
| −2147136507 | Board self test failed (code 5). Solution: Try to reinstall the driver or switch the slot(s) of the board(s). If the error persists, contact National Instruments. |
| −2147136506 | Board self test failed (code 6). Solution: Try to reinstall the driver or switch the slot(s) of the board(s). If the error persists, contact National Instruments. |
| −2147136505 | The computer goes to the hibernation mode and the board is powered off. Solution: Prevent the computer from going to the hibernation mode by using the control panel. |
| −2147136504 | A Write queue is overflowed. Solution: Wait until queue space becomes available and try again. |
| −2147136503 | The firmware of the board does not answer a command. Solution: Stop your application and execute a self test. Try to deactivate or reactivate the driver in the Device Manager. If the problem persists, contact National Instruments. |
| −2147136502 | The operation is timeout. Solution: Specify a timeout period that is long enough to complete the operation. Or use less time to complete the operation. For example, read less data in an operation. |
| −2147136501 | A Read queue is overflowed. Solution: Reduce your data rate or call Read more frequently. |
| −2147136500 | The Read buffer is too small to hold a single frame. Solution: Provide a buffer that is large enough. |
| −2147136497 | You cannot conduct a self test because the board is in use by an application. Solution: Stop all the DeviceNet applications before executing a self test. |
| −2147136496 | Allocation of memory failed. You do not have enough memory. Solution: Add more RAM or try to use fewer resources in your applications. The resources include IO variables and function blocks. |
| −2147136495 | The maximum number of sessions is exceeded. Solution: Use fewer sessions. |
| −2147136494 | The maximum number of connection objects is exceeded. Solution: Use fewer connection objects in your sessions. |
| −2147136493 | The maximum number of interface devices is detected. Solution: Use fewer devices. |
| −2147136492 | A driver support file is missing. Solution: Try to reinstall the driver. If the error persists, contact National Instruments. |
| −2147136480 | An invalid reference has been passed to a DeviceNet function. Solution: Only pass a reference retrieved from the DeviceNet function or an I/O control name in a LabVIEW project. |
| −2147136479 | An invalid handle has been passed to a DeviceNet system function. Solution: Only pass a valid system handle. |
| −2147136478 | A device handle was expected for a DeviceNet function. Solution: Only pass a device handle. |
| −2147136477 | An interface handle was expected for a DeviceNet function. Solution: Only pass an interface handle. |
| −2147136475 | Create Timing Source VI is not supported on Windows. This VI is supported on LabVIEW Real-Time targets only. |
| −2147136399 | The transceiver value is invalid or you are trying to perform an operation that requires a different transceiver. Solution: Set a valid value. |
| −2147136398 | The baud rate value is invalid. Solution: Set a valid value. |
| −2147136397 | The baud rate value is invalid. Solution: Set a valid value. |
| −2147136396 | The bit timing value is invalid. Solution: Set a valid value. |
| −2147136395 | The baud rate setting does not match the allowed range of the transceiver. Solution: Change the setting of either the baud rate or the transceiver. |
| −2147136394 | The configured timing source is not known by this interface. Solution: Make sure that you pass a valid timing value. |
| −2147136393 | The configured synchronization source is inappropriate for the hardware. Solution: Pick an appropriate timing source for the hardware. |
| −2147136392 | The source that you connected to the Master Timebase destination is missing. When the start trigger is received, the interface verifies that a signal is present on the configured source. This check has determined that this signal is missing. Solution: Verify that your cables are configured correctly and that your timebase source is generating an appropriate waveform. |
| −2147136391 | The source that you connected to the Master Timebase destination is not generating an appropriate signal. When the start trigger is received, the interface verifies that a signal of a known frequency is present on the configured source. This check has determined that this source is generating a signal, but that the signal is not one of the supported frequencies for this hardware. Solution: Verify that your source is generating a signal at a supported frequency. |
| −2147136383 | An invalid parameter has been passed to a DeviceNet VI. For example, a null pointer is passed in. Solution: Check the input parameters and ensure they are valid. You can reference the VI description to know each parameter. |
| −2147136382 | Error occurs when you acquire the driver resource. Solution: Add more RAM or try to use fewer resources in your applications. The resources include IO variables and function blocks. |
| −2147136381 | The operation is timeout. Solution: Specify a timeout period that is long enough to complete the operation or change the operation that can be complete in less time. |
| −2147136380 | The DeviceNet hardware can not be found or has been removed. Solution: 1. Ensure the DeviceNet hardware is correctly installed. 2. Ensure you use the correct port name. Get the port name of your device by using MAX. |
| −2147136368 | The interface name given does not specify a valid and existing interface. Solution: Use a valid and existing interface port name. |
| −2147136367 | The interface name is invalid. Solution: Ensure you use a valid interface name. The name of the DeviceNet interface is an ASCII string with format "DeviceNetx", where x is a decimal number starting at one that indicates which interface is being used. For example, "DeviceNet1", "DeviceNet2", and "DeviceNet32". |
| −2147136366 | The object handle passed in is invalid. Solution: Use a correct object handle returned from the Open DeviceNet Interface VI, the Open DeviceNet Explicit Messaging VI, or the Open DeviceNet IO VI. |
| −2147136365 | The property ID is invalid for the specified object type. Solution: Ensure you use a valid property ID. |
| −2147136364 | A object handle is passed in, but the corresponding object has not been opened or has been closed. Solution: Use an object handle in the following sequence: open, use, and close. |
| −2147136363 | The interface object has not been opened before it is used. Solution: Use an object handle in the following sequence: open, use, and close. |
| −2147136362 | The I/O connection object has not been opened before it is used. Solution: Use an object handle in the following sequence: open, use, and close. |
| −2147136361 | The interface object has not been started. Solution: Start the interface before performing this operation. |
| −2147136360 | The I/O connection input length is not valid. Solution: Use a valid input length. The valid input length for Poll, COS, and Cyclic ranges from 0 to 255. The valid input length for Strobe ranges from 0 to 8. |
| −2147136359 | The I/O connection output length is not valid. Solution: Use a valid output length. The valid output length for Poll, COS, and Cyclic ranges from 0 to 255. The valid output length for Strobe is 1. |
| −2147136358 | The property is get-only and can not be set. Solution: Check the property ID and find out some properties are get-only. |
| −2147136357 | The property is set-only and can not be used to get an attribute. Solution: Check the property ID and find out some properties are set-only. |
| −2147136356 | The property size passed in is not correct. Solution: Check the manual or header file to determine the correct property size. |
| −2147136355 | The property ID and the object handle do not match. For example, the property ID is an I/O connection property, but the object handle passed in is an Explicit Messaging Object. Solution: Use appropriate property ID for the given object type. |
| −2147136354 | This error occurs when you start an EM request or response cycle before the previous cycle finished. At any given time, only one EM request or response cycle is allowed to use a DeviceNet interface port. Solution: Use the following order for the EM request or response: write EM, wait for read available, and read EM. |
| −2147136353 | This error occurs when you try to send an EM request to a slave device but an EM request or response cycle is still pending on another slave device. At any given time, an EM request or response cycle can only pend on a single slave device. Solution: The existing EM request or response cycle on a slave device must end before a new EM request or response cycle starts. |
| −2147136352 | This error occurs when you try to get an EM response from a slave device, but the EM request or response cycle is pending on another slave device. Solution: Ensure an EM request or response cycle is performed on a single slave device in the following order: write EM (Slave 1) , wait for read available, read EM (Slave 1), write EM (Slave 2), wait for read available, and write EM (Slave 2). |
| −2147136350 | The buffer size is not enough for the requested operation. Solution: Ensure the buffer is large enough for the requested operation. |
| −2147136349 | The error occurs when you try to get an EM response, but you have not sent out an request. Solution: Call the Write DeviceNet Explicit Message VI to send out an request first |
| −2147136347 | The feature requested is not supported in current version. Solution: Only use supported feature. |
| −2147136346 | The property value is invalid. Solution: Ensure the property value is in a valid range. |
| −2147136345 | You try to open two or more types of I/O connections on the same slave device. Solution: Only open one type of I/O connections on a slave device at the same time. Only one type of IO connections can be opened on a slave device at same time. |
| −2147136344 | You try to blink the port LEDs but these LEDs are busy. Solution: Stop all applications that are running on that port. Do not access the applications from MAX or from LabVIEW. |
| −2147136343 | You tried to set a queue size that is bigger than the maximum allowed. Solution: Specify an in-range queue size. |
| −2147136336 | RPC connection is timeout. Solution: Ensure you have correctly configured the ethernet connection between the host and the real-time controller. |
| −2147136335 | The operation is invalid for this DeviceNet interface. Solution: Run this operation on a suitable interface. |
| −2147136334 | The driver is not communicating with the device. Solution: Make sure you connect the device to the computer. |
| −2147136304 | An invalid configuration XML file has been deployed to the target. Solution: Ensure you use LabVIEW to produces a valid configuration file. |
| −2147136288 | The DeviceNet I/O control tag name is invalid. Solution: Enter a valid tag name. |
| −2147136285 | You change the device I/O control tag when the function block is busy. Solution: Do not change the device I/O control tag when the function block is busy. |
| −2147136284 | The EM object handle is invalid. Solution: Ensure the DeviceNet I/O control is opened successfully to make the EM object handle valid. |
| −2147136255 | The firmware receives an unknown service code. Solution: Ensure the service code is predefined. |
| −2147136254 | An object is not in a proper state when you execute some operations. Solution: Ensure the object is in a proper state. |
| −2147136253 | The firmware meets an unknown property code. Solution: Ensure the request property code is predefined. |
| −2147136252 | The user calls a service which is not available at the moment. Solution: Wait a few seconds and call this service again. |
| −2147136251 | Exceeded limit for length of Write DeviceNet Explicit Message. The maximum length of an explicit message request is 240 service data bytes. Solution: Decrease the length of the explicit message request. |
| −2147136250 | EM request data size is too large. Solution: Ensure the EM request data size is valid. |
| −2147136249 | Exceeded limit for length of Read DeviceNet Explicit Message. The maximum length of an explicit message response is 240 service data bytes. The response larger than the maximum length cannot be handled. Solution: Configure the device to return a response of a smaller size. |
| −2147136247 | A Bus Off error occurs on the bus. Solution: Clear the Bus Off error physically and wait for the firmware to recover from this error automatically. |
| −2147136224 | The EM established is timeout. Solution: Specify a timeout period that is long enough to establish the EM connection or check whether the slave is connected. |
| −2147136223 | An internal error occurs in the firmware. Solution: Try to reinstall the driver or switch the slot(s) of the board(s). If the error persists, contact National Instruments. |
| −2147136221 | The object is already open in another application. Solution: Ensure that only one application at a time uses an object , and that you close all objects prior to exiting your application |
| −2147136220 | The DeviceNet Interface Object is already open with a different Poll Mode. Or you used the automatic Poll Mode and opened an I/O connection after start. Solutions: Match all Poll Mode parameters. Or stop communication before trying to add I/O connections. |
| −2147136219 | You tried to open a DeviceNet COS I/O connection with a Cyclic I/O connection. The Cyclic I/O connection is already open for that device. Solution: COS and Cyclic connections are mutually exclusive, so you can only open one type for a given device. |
| −2147136218 | CAN bus problems caused all communications to stop. This error corresponds to Bus Off state. Solution: Verify the following issues: cabling is correct; devices are connected and operational; proper bus power is applied. |
| −2147136217 | Exceeded resource limit for DeviceNet I/O tables. Solution: Decrease the number of slave device I/O connections; Decrease the Input Length or Output Length used for a given I/O Object. |
| −2147136214 | You try to use the Write DeviceNet Explicit Message VI before a response from a previous Write arrives. Only one explicit message can be pending. Solution: Complete a Write, Wait, and Read circle before sending another Write DeviceNet Explicit Message request. |
| −2147136213 | The DeviceNet duplicate MAC ID check fails for the Interface Object. Solution: Determine an unused MAC ID in your DeviceNet system and use that MAC ID for Open DeviceNet Interface. |
| −2147136212 | Miscellaneous device initialization error. Solution: Verify that the configuration specified in Open functions matches the capabilities of your device. |
| −2147136211 | DeviceNet device does not initialize due to unsupported connection types. For example, if the device only supports Strobed I/O, but you configure Polled I/O for this device. This error occurs. Solution: Refer to the device documentation for valid connection types. |
| −2147136210 | DeviceNet device does not initialize due to unsupported Expected Packet Rate (EPR). Solution: Some devices place a lower or upper limit on the EPR. Adjust the EPR if an overflow or underflow occurs. |
| −2147136209 | DeviceNet device does not initialize because the vendor ID of the device differs from the driver attribute. Solution: If you replaced the device, use the new vendor ID as the driver attribute. If you do not want to verify the ID, do not set the driver attribute. |
| −2147136208 | DeviceNet device does not initialize because the device type of the device differs from the driver attribute. Solution: If you replaced the device, use the new device type as the driver attribute. If you do not want to verify the type, do not set the driver attribute. |
| −2147136207 | DeviceNet device does not initialize because the product code of the device differs from the driver attribute. Solution: If you replaced the device, use the new product code as the driver attribute. If you do not want to verify the code, do not set the driver attribute. |
| −2147136206 | DeviceNet device not found. A connection could not be established with the MAC ID specified in the Open function. Solution: Verify that the device exists at the expected MAC ID or verify that the cabling is correct. |
| −2147136205 | Board self test fails. Solution: Try to reinstall the driver or switch the slots of the boards. If the error persists, contact National Instruments. |
| −2147136203 | Driver fails to communicate with the device. Solution: Ensure that the device is connected. |
| −2147136202 | FPGA image version between the host and the remote target does not match. Solution: Update installation from the host to the remote target. |
| −2147136200 | The operation cannot be performed when the object has been started. Solution: Stop the object before performing this operation. |
| −2147136199 | The operation cannot be performed when the interface has been started. Solution: Stop the interface before performing this operation. |
| −2147136191 | You are trying to start an interface that does not have bus power for the transceiver. Some physical layers on DeviceNet hardware are internally powered on, but other hardware might require external power for the port to operate. This error occurs when starting an interface on hardware that requires external power but no power is detected. Solution: Supply proper voltage to your transceiver. |
| −2147136190 | The error occurs when you send out an EM request and try to get an EM response. The EM response has not arrived. Solution: Call the Wait for State VI to wait for the Read Available state before calling the Read DeviceNet Explicit Message VI to get the response. |
| −2147136188 | The error occurs when you send out an fragment EM request and receive an EM ACK, indicating the EM request is too long. Solution: Send a shorter EM request. |
| −2147136187 | The error occurs when you send out an fragment EM request and receive an EM ACK with an invalid error code. Solution: Resend the EM request. |
| −2147136186 | You can only use this property in master mode. You cannot use this property when the EM or IO is in slave mode. Solution: Check the property IDs to see that some properties are master only. |
| −2147136185 | Firmware of C Series modules is corrupted. Solution: Reinstall the firmware by following Firmware_Update_Instructions.html in the National Instruments\NI-IndCom for DeviceNet directory. |
| −2147136184 | Firmware image version is incompatible with C Series modules. Solution: Update the firmware by following Firmware_Update_Instructions.html in the National Instruments\NI-IndCom for DeviceNet directory. |
| 347137 | The connection to the DeviceNet device is timeout, so the device does not respond to messages sent by DeviceNet. Solution: Increase the value of the Expected Packet Rate in the Open DeviceNet IO VI and verify that the device is operational. |
| 347138 | The object is already open, but you are allowed to use a duplicate handle. Solution: Ensure that only one application at a time uses an object , and that you close all objects prior to exiting your application. Do not use the LabVIEW toolbar Abort button. |
| 347139 | You try to use the Write DeviceNet Explicit Message VI before a response from a previous Write arrives. Only one explicit message can be pending. Solution: Complete a Write, Wait, and Read circle before sending another Write DeviceNet Explicit Message request. |
| 347140 | The property size passed in is invalid. Solution: Use a valid property size. |
| 347184 | The slave parameters cannot be downloaded successfully. Solution: Verify the EDS file is correct and the parameter is writable for the slave device. |
| 347185 | The DeviceNet slave is not connected. Solution: Ensure the slave is connected to the network. |
| 347186 | IO data is not available. Solution: Waiting for data becomes available before reading IO data. |
| 347187 | The data length of the I/O connection does not equal the predefined output length. Solution: Ensure that the data length in the Write DeviceNet IO VI equals the output length. |
| 347188 | CAN frames are not available for reading. Solution: Wait for data to be available before reading CAN frames. |
| 347189 | Read CAN Frame queue is overflowed. Solution: Reduce your data rate or call Read CAN Frame more frequently. |