<?XML Version="1.0">
<nidocument>
<nicomment>
LabVIEW error file
</nicomment>
<nierror code="-1074388991">
NI-CAN:  (Hex 0xBFF62001) The timeout of a wait or notification function expired before any desired state occurred.  Solutions: Increase value of Timeout parameter; Verify your cable connections and operation of remote devices.
</nierror>
<nierror code="-1074388990">
NI-CAN:  (Hex 0xBFF62002) An internal error occurred in the NI-CAN driver.  A description is located in the file NicanErr.txt in your Windows folder (usually C:\Windows).  Solutions:  Email or fax the NicanErr.txt file to National Instruments for technical support.
</nierror>
<nierror code="-1074388989">
NI-CAN:  (Hex 0xBFF62003) There is a basic syntax error in the ObjName parameter.  Solutions: Verify that the name does not contain invalid characters, and that it uses the syntax specified for the Open function.
</nierror>
<nierror code="-1074388988">
NI-CAN:  (Hex 0xBFF62004) A function parameter is invalid.  Solutions: Read the function description and verify that you provide a valid value for each parameter.
</nierror>
<nierror code="-1074388987">
NI-CAN:  (Hex 0xBFF62005) The value of one or more attributes is invalid. This error can occur for Set Attribute (one value bad) or Config/Open (one or more values bad).  Solutions: Consult the object description to verify the values of each attribute.
</nierror>
<nierror code="-1074388986">
NI-CAN:  (Hex 0xBFF62006) The object is already open in another application.  Solutions: Ensure that only one application at a time uses an object , and that you close all objects prior to exiting your application (don't use LabVIEW toolbar's Abort button).
</nierror>
<nierror code="-1074388985">
NI-CAN:  (Hex 0xBFF62007) You attempted to set a configuration attribute while the object is running.  Solutions: Configure attributes prior to opening the object; Stop and restart communication as needed so that you can update configuration attributes.
</nierror>
<nierror code="-1074388984">
NI-CAN:  (Hex 0xBFF62008) Write queue overflow.  Solutions: Increase the length of the write queue; Wait for Write Success state prior to calling Write; To transmit recent data only, set the write queue length to zero.
</nierror>
<nierror code="-1074388982">
NI-CAN:  (Hex 0xBFF6200A) A known feature is not supported.  Solutions: Refer to the descriptions in the manual to determine which feature is unsupported.
</nierror>
<nierror code="-1074388981">
NI-CAN:  (Hex 0xBFF6200B) CAN bus problems caused all communications to stop.  This error corresponds to CAN Bus Off state.  Solutions: Verify that cabling is correct, devices are connected and operational, and proper bus power is applied.
</nierror>
<nierror code="-1074388978">
NI-CAN:  (Hex 0xBFF6200E) You called Read DeviceNet Explicit Message before the response arrived. Solution: Wait for the Read Avail state prior to calling read; Make sure you call Write DeviceNet Explicit Message before calling read (every response requires a request).
</nierror>
<nierror code="-1074388977">
NI-CAN:  (Hex 0xBFF6200F) The DeviceNet duplicate MAC ID check failed for the Interface Object.  Solution: Using a Who utility, determine an unused MAC ID in your DeviceNet system, and use that MAC ID for Open DeviceNet Interface.
</nierror>
<nierror code="-1074388976">
NI-CAN:  (Hex 0xBFF62010) Error initializing DeviceNet device.  Miscellaneous device init error.  Solution: Verify that the configuration specified in Open functions matches the capabilities of your device.
</nierror>
<nierror code="-1074388975">
NI-CAN:  (Hex 0xBFF62011) DeviceNet device not found.  A connection could not be established with the MAC ID specified in the Open function.  Solutions: Use a Who utility to verify that the device exists at the expected MAC ID; Verify that cabling is correct.
</nierror>
<nierror code="-1074388974">
NI-CAN:  (Hex 0xBFF62012) DeviceNet message fragments received out of sequence.  Fragmentation breaks a large message into smaller fragments for network transmission.  Solutions: Verify that cabling is correct; Contact device manufacturer (bug in device).
</nierror>
<nierror code="-1074388972">
NI-CAN:  (Hex 0xBFF62014) Error response received from remote DeviceNet device.  Indicates that Get / Set Dnet Attribute failed in the device.  Solutions: Using DeviceError, refer to the error codes in the DeviceNet Specification or to documentation from the device vendor.
</nierror>
<nierror code="-1074388969">
NI-CAN:  (Hex 0xBFF62017) This attribute's value must be provided prior to the Open.  Solutions: Set the attribute using the Config function before the Open, and do not set the attribute at any later time.
</nierror>
<nierror code="-1074388959">
NI-CAN:  (Hex 0xBFF62021) The watchdog timeout for a CAN Object expired, indicating that data was not received at the rate expected.  Solutions: Verify your cable connections and operation of remote devices; Increase the Period of the CAN Object.
</nierror>
<nierror code="-1074388957">
NI-CAN:  (Hex 0xBFF62023) The Interface name is invalid or unknown.  Solutions: Use the configuration utility to verify that the name is assigned to a specific port.
</nierror>
<nierror code="-1074388956">
NI-CAN:  (Hex 0xBFF62024) The object handle (ObjHandle) is invalid.  Solutions: Verify that the Open function succeeded;  Verify that you do not close the handle in another thread of execution (such as with ncReset).
</nierror>
<nierror code="-1074388954">
NI-CAN:  (Hex 0xBFF62026) The DeviceNet Interface Object is already open with a different Poll Mode.  Solutions: Change all Poll Mode parameters to match; Stop communication with Operate Dnet Interface before trying to add I/O connections.
</nierror>
<nierror code="-1074388952">
NI-CAN:  (Hex 0xBFF62028) Read queue overflow.  Solutions: Use Read Mult notification and function to read multiple frames at a time; Increase the length of the read queue; To receive recent data only, set read queue length to zero.
</nierror>
<nierror code="-1074388949">
NI-CAN:  (Hex 0xBFF6202B) CAN bus problems (stuff error) caused all communications to stop.  This error corresponds to CAN Bus Off state.  Solutions: Verify that cabling is correct, devices are connected and operational, and proper bus power is applied.
</nierror>
<nierror code="-1074388947">
NI-CAN:  (Hex 0xBFF6202D) Exceeded resource limit for queues in shared memory between firmware/driver. The ncReadMult function is not allowed. Solutions: Decrease queue lengths in objects; Set read queue length to at least 2; Decrease number of CAN Objects.
</nierror>
<nierror code="-1074388944">
NI-CAN:  (Hex 0xBFF62030) Error initializing DeviceNet device.  Unsupported ConnectionType.  For example, if the device supports only Strobed I/O, and you configure Polled I/O, this error occurs.  Solution: Refer to the device documentation for valid connection types.
</nierror>
<nierror code="-1074388941">
NI-CAN:  (Hex 0xBFF62033) DeviceNet Interface Object not yet open.  Solution: Open the DeviceNet Interface Object before opening any other objects (I/O or Explicit Messaging).
</nierror>
<nierror code="-1074388927">
NI-CAN:  (Hex 0xBFF62041) The connection to the DeviceNet device timed out.  The device is no longer responding to messages sent by NI-DNET.  Solutions: Increase the value of ExpPacketRate in Open Dnet IO; Use a Who utility to verify that the device is operational.
</nierror>
<nierror code="-1074388925">
NI-CAN:  (Hex 0xBFF62043) The CAN Object name is invalid or unknown.  Solutions: Verify that you use the syntax specified in the NI-CAN documentation.
</nierror>
<nierror code="-1074388922">
NI-CAN:  (Hex 0xBFF62046) You tried to open a DeviceNet COS I/O connection with a Cyclic I/O connection already open for that device.  Solutions: COS and Cyclic connections are mutually exclusive, so you can only open one type for a given device.
</nierror>
<nierror code="-1074388920">
NI-CAN:  (Hex 0xBFF62048) Overflow in the CAN communication chip.  This error occurs when frames are received back-to-back for long periods.  Solutions: Set Net Interface mask and comparators to filter out frames; Reduce overall bus traffic.
</nierror>
<nierror code="-1074388917">
NI-CAN:  (Hex 0xBFF6204B) CAN bus problems (bad frame format) caused all communications to stop.  This error corresponds to CAN Bus Off state.  Solutions: Verify that cabling is correct, devices are connected and operational, and that proper bus power is applied.
</nierror>
<nierror code="-1074388915">
NI-CAN:  (Hex 0xBFF6204D) Exceeded resource limit for DeviceNet I/O tables.  Solutions: Decrease the number of I/O connections used; Decrease the InputLength or OutputLength used for a given I/O Object (255 max).
</nierror>
<nierror code="-1074388912">
NI-CAN:  (Hex 0xBFF62050) Error initializing DeviceNet device.  Unsupported InputLength.  InputLength must match the produced_connection_size attribute in the device's I/O Connection Object.  Exception: For Strobed I/O as a slave, InputLength must be 1.
</nierror>
<nierror code="-1074388888">
NI-CAN:  (Hex 0xBFF62068) Intermediate receive queue overflow.  This queue holds frames as they are transferred from the CAN chip into object read queues.  Solutions: Set Net Interface mask and comparators to filter out frames; Reduce overall bus traffic.
</nierror>
<nierror code="-1074388885">
NI-CAN:  (Hex 0xBFF6206B) CAN bus problems (no ack) caused all communications to stop.  This error corresponds to CAN Bus Off state.  Solutions: Verify that cabling is correct, devices are connected and operational, and proper bus power is applied.
</nierror>
<nierror code="-1074388883">
NI-CAN:  (Hex 0xBFF6206D) Exceeded limit for length of Write DeviceNet Explicit Message.    The maximum length of an explicit message request is 240 service data bytes.  Solutions: Decrease the length of the explicit message request.
</nierror>
<nierror code="-1074388880">
NI-CAN:  (Hex 0xBFF62070) Error initializing DeviceNet device.  Unsupported OutputLength.  OutputLength must match the consumed_connection_size attribute in the device's I/O Connection Object.  Exception: For Strobed I/O as a master, OutputLength must be 1.
</nierror>
<nierror code="-1074388856">
NI-CAN:  (Hex 0xBFF62088) Overflow in timed transmit list.  This list holds frames for pending timed transmissions (Write of Net Interface with timestamp).  Solutions: Increase the length of the timed transmit list; Wait for timed frames to transmit before Write.
</nierror>
<nierror code="-1074388853">
NI-CAN:  (Hex 0xBFF6208B) CAN bus problems (tx 1, rx 0) caused all communications to stop.  This error corresponds to CAN Bus Off state.  Solutions: Verify that cabling is correct, devices are connected and operational, and that proper bus power is applied.
</nierror>
<nierror code="-1074388851">
NI-CAN:  (Hex 0xBFF6208D) Exceeded limit for length of Read DeviceNet Explicit Message. The maximum length of an explicit message response is 240 service data bytes. Larger responses are discarded.  Solutions: Configure the device to return a smaller response.
</nierror>
<nierror code="-1074388848">
NI-CAN:  (Hex 0xBFF62090) Error initializing DeviceNet device. Unsupported ExpPacketRate. Solutions: Some devices place lower/upper limits on EPR; If EPR is small, increase it; If EPR is large, decrease it.
</nierror>
<nierror code="-1074388831">
NI-CAN:  (Hex 0xBFF620A1) Too many CAN Objects with short Periods. The combined periods of all CAN Objects cannot be accurately maintained. Solutions: Decrease the number of CAN Objects; Increase the Period of one or more CAN Objects.
</nierror>
<nierror code="-1074388821">
NI-CAN:  (Hex 0xBFF620AB) CAN bus problems (tx 0, rx 1) caused all communications to stop.  This error corresponds to CAN Bus Off state. Solutions: Verify that cabling is correct, devices are connected and operational, and proper bus power is applied.
</nierror>
<nierror code="-1074388819">
NI-CAN:  (Hex 0xBFF620AD) You called Write DeviceNet Explicit Message before the response arrived for a previous write.  Only one explicit message can be pending.  Solutions: Finish the write/wait/read sequence before writing another explicit message request.
</nierror>
<nierror code="-1074388816">
NI-CAN:  (Hex 0xBFF620B0) Error initializing DeviceNet device. Vendor ID of device differs from your driver attribute. Solutions: If you replaced the device, use the new vendor ID as driver attr; If you no longer want to verify, remove the Set Driver Attr call.
</nierror>
<nierror code="-1074388789">
NI-CAN:  (Hex 0xBFF620CB) CAN bus problems (bad CRC) caused all communications to stop. This error corresponds to CAN Bus Off state. Solutions: Verify that cabling is correct, devices are connected and operational, and proper bus power is applied.
</nierror>
<nierror code="-1074388787">
NI-CAN:  (Hex 0xBFF620CD) Exceeded resource limit for RTSI signals.  Solutions: Decrease the number of RTSI signals used; Refer to your User Manual for information regarding valid RTSI signals for your CAN card.
</nierror>
<nierror code="-1074388784">
NI-CAN:  (Hex 0xBFF620D0) Error initializing DeviceNet device. Device Type of device differs from your driver attribute. Solutions: If you replaced the device, use the new device type as driver attr; If you no longer want to verify, remove the Set Driver Attr call.
</nierror>
<nierror code="-1074388752">
NI-CAN:  (Hex 0xBFF620F0) Error initializing DeviceNet device. Product Code of device differs from your driver attribute.  Solutions: If you replaced the device, use the new product code as driver attr; If you no longer want to verify, remove the Set Driver Attr call.
</nierror>
<nierror code="-1074388736">
NI-CAN:  (Hex 0xBFF62100) Exceeded limit for total number of objects. Solution: Decrease number of CAN Objects that receive data by using the Network Interface to receive frames.
</nierror>
<nierror code="-1074388735">
NI-CAN:  (Hex 0xBFF62101) CAN chip supports at most 12 of the following CAN Objects: Tx By Response (Std or Xtd ID), Rx Xtd ID. Solutions: Set Tx By Response attributes to false; Config all Tx Xtd before Rx Xtd; Don't use Net Intf to receive Xtd frames (CompXtd=None).
</nierror>
<nierror code="-1074388734">
NI-CAN:  (Hex 0xBFF62102) A duration (time) that you submitted is too large or too small.  Solutions: Read the function description to determine whether to increase or decrease the duration.
</nierror>
<nierror code="-1074388733">
NI-CAN:  (Hex 0xBFF62103) The CAN card's firmware no longer responds to commands from the PC's driver, usually due to frequent CAN or timer interrupts. Solutions: Refer to ncAction for hints on handling high-traffic; Decrease the total number of objects in use.
</nierror>
<nierror code="-1074388732">
NI-CAN:  (Hex 0xBFF62104) The attribute ID (or operation code) that you provided is invalid. Solutions: Read the function description and verify that you provide a valid attribute ID (or operation code).
</nierror>
<nierror code="-1074388731">
NI-CAN:  (Hex 0xBFF62105) The size or length that you provided is invalid (too small or large), and the operation could not continue. Solutions: Read the function description and verify that you provide a valid size (or length).
</nierror>
<nierror code="-1074388730">
NI-CAN:  (Hex 0xBFF62106) The length that you provided for the timed transmit list is invalid. Solutions: Decrease the length that you provide as the attribute for timed transmit length.
</nierror>
<nierror code="-1074388729">
NI-CAN:  (Hex 0xBFF62107) You tried to create 2 or more notifications in different threads of execution.  Solutions: Create only one notification for each object; Cancel notification (ncCreateNotification with DesiredState=0) prior to calling ncCloseObject.
</nierror>
<nierror code="-1074388728">
NI-CAN:  (Hex 0xBFF62108) The NI-CAN and NI-DNET functions cannot be used simultaneously on the same CAN card (even 2-port cards).  Solution: Use 2 or more CAN cards, with NI-CAN on one card, and NI-DNET on the other.
</nierror>
<nierror code="-1074388726">
NI-CAN:  (Hex 0xBFF6210A) The language interface for NI-CAN cannot find a required DLL (such as NICAN.DLL).  Solution: Uninstall NI-CAN and re-install.
</nierror>
<nierror code="-1074388725">
NI-CAN:  (Hex 0xBFF6210B) The language interface for NI-CAN cannot find a required function in NICAN.DLL.  Solution: Uninstall NI-CAN and re-install.
</nierror>
<nierror code="-1074388724">
NI-CAN:  (Hex 0xBFF6210C) The language interface for NI-CAN cannot acquire a required resource (i.e. mutex).  Solution: Uninstall NI-CAN and re-install.
</nierror>
<nierror code="1073094662">
NI-CAN:  (Hex 0x3FF62006) The object is already open, but you are allowed to use a duplicate handle.  Solutions: Ensure that only one application at a time uses an object , and that you close all objects prior to exiting your application (don't use LabVIEW toolbar's Abort button).
</nierror>
<nierror code="1073094665">
NI-CAN:  (Hex 0x3FF62009) The data returned from this Read matches the data returned from the previous call to Read.  Solutions: If you merely want the most recent data, ignore this warning; For new data, wait for Read Avail state before calling Read.
</nierror>
<nierror code="1073094667">
NI-CAN:  (Hex 0x3FF6200B) CAN bus problems detected, but communication is proceeding. This warning corresponds to CAN Error Passive state. Solutions: Verify that cabling is correct, devices are connected and operational, and that proper bus power is applied.
</nierror>
<nierror code="1073094668">
NI-CAN:  (Hex 0x3FF6200C) Low-speed CAN transceiver warning.  A fault exists on the bus, but communication continues.  Solutions: Verify that cabling is correct.
</nierror>
<nierror code="1073094677">
NI-CAN:  (Hex 0x3FF62015) User's notification function never returned. Object was closed regardless. Solutions: Remove long loops or other time-consuming code from the function used with Create Notification.
</nierror>
<nierror code="1073094699">
NI-CAN:  (Hex 0x3FF6202B) CAN bus problems detected (stuff error), but communication is proceeding. This warning corresponds to CAN Error Passive state. Solutions: Verify that cabling is correct, devices are connected and operational, and proper bus power is applied.
</nierror>
<nierror code="1073094701">
NI-CAN:  (Hex 0x3FF6202D) Exceeded resource limit for queues in shared memory between firmware/driver. Read or write queue performance is reduced. Solutions: Decrease queue lengths in objects; Decrease the total number of objects.
</nierror>
<nierror code="1073094731">
NI-CAN:  (Hex 0x3FF6204B) CAN bus problems detected (bad frame format), but communication is proceeding. This warning corresponds to CAN Error Passive state. Solutions: Verify that cabling is correct, devices are connected and operational, and that proper bus power is applied.
</nierror>
<nierror code="1073094763">
NI-CAN:  (Hex 0x3FF6206B) CAN bus problems detected (no ack), but communication is proceeding. This warning corresponds to CAN Error Passive state. Solutions: Verify that cabling is correct, devices are connected and operational, and proper bus power is applied.
</nierror>
<nierror code="1073094795">
NI-CAN:  (Hex 0x3FF6208B) CAN bus problems detected (tx 1, rx 0), but communication is proceeding. This warning corresponds to CAN Error Passive state. Solutions: Verify that cabling is correct, devices are connected and operational, and proper bus power is applied.
</nierror>
<nierror code="1073094827">
NI-CAN:  (Hex 0x3FF620AB) CAN bus problems detected (tx 0, rx 1), but communication is proceeding. This warning corresponds to CAN Error Passive state. Solutions: Verify that cabling is correct, devices are connected and operational, and proper bus power is applied.
</nierror>
<nierror code="1073094859">
NI-CAN:  (Hex 0x3FF620CB) CAN bus problems detected (bad CRC), but communication is proceeding. This warning corresponds to CAN Error Passive state. Solutions: Verify that cabling is correct, devices are connected and operational, and proper bus power is applied.
</nierror>
<nierror code="1073094917">
NI-CAN:  (Hex 0x3FF62105) The size or length that you provided is invalid (too small or large), but the operation continued successfully. Solutions: Read the function description and verify that you provide a valid size (or length).
</nierror>
<nierror code="1073094921">
NI-CAN:  (Hex 0x3FF62109) The combined periods of all CAN Objects result in timing that is too fast.  Each CAN Object requires 1ms of overhead.  Solutions: Decrease number of CAN Objects (use Net Interface for all receiving) ; Increase CAN Object periods.
</nierror>
</nidocument>