Deterministic Communication Error Codes

Deterministic communication protocols can return the following error codes. Refer to the KnowledgeBase for more information about correcting errors in LabVIEW.

Code Description
−40635 The network speed you configured does not match the actual network speed. This can happen if your network adapter is slower than the network speed you specified or if another adapter, hub, or switch has downgraded the actual network speed.
−40634 The node that owns the associated variable cannot use the "Data Received" timing source, or the node that owns the associated variable can use only the "Data Sent" timing source.
-40633 The requested error cannot be ignored because a full or partial shutdown of the node and/or network has been initiated.
-40632 LabVIEW has detected a valid packet that does not follow NI's deterministic protocol on the network. LabVIEW will shut down the node/network.
-40631 An already deployed configuration for one or more network nodes does not match the configuration of this node.
-40630 The network transmission violated the requested timing. Refer to the "Avoid Jitter" topic and other timing topics in the LabVIEW Help for information on what may have caused the error and how you can avoid it.
-40629 Resource allocation/creation/configuration failed because the existing resource is configured with different parameters. LabVIEW generates this error when you attempt to recreate a particular resource, such as a channel, with, for example, a different buffer size.
-40627 Read failed after three retries because new data was placed into the buffer.
-40626 The clock synchronization algorithm failed because a certain amount of cycle start packets have been missed.The deterministic communication engine must be restarted before additional write network transactions can occur.
-40618 The reference is invalid.
-40616 The deterministic communication engine is unable to locate a device with a specified MAC address.
-40615 LabVIEW cannot instantiate the requested device in a specified mode because there is already a device initialized in deterministic mode.
-40613 The specified subchannel is out of range. Refer to the LabVIEW Help for more information about supported ranges for channel subchannels.
-40612 You have attempted one of the following illegal operations: allocation of a write terminal on a channel that another node owns; allocation of a shared memory variable on a non-shared memory channel; creation of a read or write terminal on a shared memory channel.
-40611 An item with the specified index has already been configured.
-40609 The item offset is outside of the range you specified during channel initialization time.
-40608 One of the following occurred: 1) Message being written to the deterministic-communication engine exceeds the maximum size configured when the channel or terminal was created. 2) Buffer allocated for reading is smaller than the message size.
-40606 A timing source with the same name already exists for the deterministic-communication engine.
-40603 Files for the deterministic-communication engine are not installed properly.
-40602 Deterministic-communication engine ran out of allocated resources.
-40601 The deterministic-communication engine failed to initialize hardware.
-40600 The deterministic communication engine failed to allocate enough memory while performing the requested operation.
40620 One of the following conditions occurred: 1) This slot-based variable has already been read within this network cycle. 2) This shared-memory-based variable has never been instantiated by the owner.
40621 The source node is still online, but no new data has been received for more than one network cycle because no new data has been written to the channel on the source node.
40622 No new data has been received for more than one network cycle because the source node is offline.
40623 One of the values received from the source node was not read and was overwritten.
40624 One of the values was overwritten before it was sent. LabVIEW returns this warning for non-shared memory variables that have been written more than once in a single network cycle.
40625 No data was sent from this channel in the previous network cycle because a write operation was delayed beyond a preconfigured threshold. An interrupt probably caused the delay.
40626 Clock synchronization algorithm failed because a sufficient number of cycle-start packets were missed. No additional write network transactions are allowed until the deterministic-communication engine is restarted.
40628 Attempted read operation at least twice before it succeeded due to new data being placed into the buffer.
40630 Network transmission violated requested timing. Refer to the "Avoid Jitter" topic and other timing topics in the LabVIEW Help for more information about what might have caused this error and how to avoid it.
40631 A deployed configuration for one or more network nodes does not match the configuration for this node.
40632 Detected a valid packet on the network that does not conform to the National Instruments deterministic protocol. The node or network will be shut down.