NI-IndCom for DeviceNet 2.1 or later adds NI-DNET compatible LabVIEW VIs that work on NI PCI-8532, NI PXI-8532, and NI 9882, while also maintaining older project based NI-IndCom for DeviceNet 2.0.x features for NI PCI-8532 and NI PXI-8532. To achieve this compatibility still requires the steps outlined in the example to be performed.
The table below provides which hardware was created for DNET and DeviceNet:
*These versions reflect the versions of the software that we can use for the purposes of this guide
Unlike NI-DNET, NI-IndCom for DeviceNet 2.1 or later does not support C based languages. DeviceNet slave mode has been added to NI-IndCom for DeviceNet 2.2 or later.
NI-DNET Configurator is no longer available. However the NI-DNET Analyzer abilities have been transferred to a very powerful Monitor example utility. This utility can be found at <LabVIEW Version>\examples\NI-Industrial Communications for DeviceNet\Utilities\Monitor.
The NI-IndCom for DeviceNet 2.1 software offers a project based EDS file import to find and test connected slaves easily. Please see the section titled importing EDS files.
The NI-IndCom for DeviceNet 2.1 or later API uses a LabVIEW Library (.lvlib) to include all new DeviceNet VIs. This design enables us to use the same VI names for the new API so you can install the NI-DNET and NI-IndCom for DeviceNet software side by side. Also, you can run the NI-DNET VIs and NI-IndCom for DeviceNet VIs in parallel on the same host machine or RT target. However, if you want to run NI-DNET applications on 8532 or 9882 hardware, you must replace the old NI-DNET VIs with corresponding new VIs provided by NI-IndCom for DeviceNet 2.1 or later.
National Instruments recommends conducting this migration in a LabVIEW project. Before you start make a copy of your original code and save it. If the NI-DNET application is not in a LabVIEW project yet, create a new LabVIEW project and add the copy of your original application Main VI into this project. Save the project. Make sure only the project window is opened and all VIs are closed. Then open the project Dependencies and right-click the vi.lib folder and choose Arrange By » Path. In your project window, if you right-click the project name and choose View » Full Path, the window will show the path of every dependency. Now go ahead and replace every NI-DNET VI and every custom Control (.ctl) in Dependencies » vi.lib tree with the corresponding new VI and control in folder <vi.lib>\DeviceNet\VIAPI.
When NI-DNET VI’s or Ctl’s listed in the table below are shown in the Dependencies » vi.lib tree, replace those VIs with the corresponding NI-IndCom for DeviceNet VIs. An example of this is provided below this list:
There are several examples included with NI-Industrial Communications for DeviceNet. In Example Finder, you can go to Hardware Input and Output » NI-Industrial Communications » Legacy Examples. Here you can find examples on how to use an imported EDS file in your project. You can only import EDS files for use with the PCI/PXI-8532.
KnowledgeBase 6JHCG3EG: Why Can’t I Install NI-DNET 1.6.x Support for LabVIEW 2013 and Above?
Drivers and Updates: NI-Industrial Communications for DeviceNet Driver Support
Collaborate with other users in our discussion forums
A valid service agreement may be required, and support options vary by country.