National Instruments NI-DNET User Manual
  1. Manuals
  2. Brands
  3. National Instruments Manuals
  4. Software
  5. NI-DNET
  6. User manual
National Instruments NI-DNET User Manual

National Instruments NI-DNET User Manual

National instruments devicenet ni-dnet user manual
Hide thumbs
Table of Contents

Advertisement

Quick Links

Download this manual
DeviceNet
T
NI-DNET
TM
User Manual
NI-DNET User Manual
May 2004 Edition
Part Number 370375B-01

Advertisement

Table of Contents
loading
Need help?

Need help?

Do you have a question about the NI-DNET and is the answer not in the manual?

Questions and answers

Subscribe to Our Youtube Channel

Related Manuals for National Instruments NI-DNET

Summary of Contents for National Instruments NI-DNET

  • Page 1 DeviceNet NI-DNET User Manual NI-DNET User Manual May 2004 Edition Part Number 370375B-01...
  • Page 2 Thailand 662 992 7519, United Kingdom 44 0 1635 523545 For further support information, refer to the Technical Support and Professional Services appendix. To comment on the documentation, send email to techpubs@ni.com. © 1998–2004 National Instruments Corporation. All rights reserved.

  • Page 3: Important Information

    The reader should consult National Instruments if errors are suspected. In no event shall National Instruments be liable for any damages arising out of or related to this document or the information contained in it.

  • Page 4: Table Of Contents

    Chapter 2 NI-DNET Hardware Overview Types of Hardware...2-1 Differences Between CAN Kits and DeviceNet Kits ...2-2 Chapter 3 Developing Your Application Accessing NI-DNET from your Programming Environment...3-1 LabVIEW ...3-1 LabWindows/CVI...3-2 Microsoft Visual Basic ...3-2 Microsoft C/C++ ...3-3 Borland C/C++ ...3-3 Other Programming Languages...3-4...
  • Page 5 Contents Programming Model for NI-DNET Applications ... 3-6 Step 1. Open Objects... 3-8 Step 2. Start Communication ... 3-8 Step 3. Run Your DeviceNet Application... 3-8 Addition of Slave Connections after Communication Start ... 3-9 Step 4. Stop Communication ... 3-10 Step 5.
  • Page 6 Troubleshooting and Common Questions Troubleshooting with the Measurement & Automation Explorer (MAX) ...C-1 Troubleshooting Self Test Failures...C-2 Common Questions...C-3 Appendix D Hardware Specifications Appendix E Technical Support and Professional Services Glossary Index © National Instruments Corporation Contents NI-DNET User Manual...

  • Page 7: About This Manual

    Use the installation guide to install and configure your DeviceNet hardware and the NI-DNET software. Use this NI-DNET User Manual to learn the basics of DeviceNet and how to develop an application program. The user manual also contains information on DeviceNet hardware.

  • Page 8: Conventions

    Digital Information—Controller Area Network (CAN) for High-Speed Communication DeviceNet Specification, Version 2.0, Open DeviceNet Vendor Association CompactPCI Specification, Revision 2.0, PCI Industrial Computers Manufacturers Group PXI Hardware Specification, Revision 2.1, National Instruments Corporation PXI Software Specification, Revision 2.1, National Instruments Corporation ni.com...
  • Page 9 • • • © National Instruments Corporation LabVIEW online reference ODVA website, www.odva.org Microsoft Win32 Software Development Kit (SDK) online help About This Manual NI-DNET User Manual...

  • Page 10: Ni-Dnet Software Overview

    NI-DNET Software Overview The DeviceNet software provided with National Instruments DeviceNet hardware is called NI-DNET. This section provides an overview of the NI-DNET software. Installation and Configuration Measurement & Automation Explorer (MAX) Measurement & Automation Explorer (MAX) provides access to all of your National Instruments products.
  • Page 11 If the self-test fails, the card icon shows an X mark, and the Test Status in the right pane describes the problem. Refer to Appendix C, about resolving hardware installation problems. NI-DNET User Manual Figure 1-1. NI-DNET Cards Listed in MAX Troubleshooting and Common Questions, for information ni.com...

  • Page 12: Configure Devicenet Port

    To change the default protocol for the DeviceNet (CAN) card, right-click the card and select Protocol. In this dialog you can select either DeviceNet for NI-DNET (default), or CAN for NI-CAN. For more information, refer to the section LabVIEW Real-Time (RT) Configuration LabVIEW Real-Time (RT) combines easy-to-use LabVIEW programming with the power of real-time systems.

  • Page 13: Ni-Spy

    Chapter 1 NI-DNET Software Overview NI-Spy This tool monitors function calls to the NI-DNET APIs. This tool helps in debugging programming problems in your application. To launch this tool, open the Software branch of the MAX Configuration tree, right-click NI Spy, and select Launch NI Spy.

  • Page 14: Interface Object

    The NI-DNET device driver software provides three classes of objects: Interface Objects, Explicit Messaging Objects, and I/O Objects. You can open an instance of an NI-DNET object using one of the three open functions ( ncOpenDnetIO using the NI-DNET functions, which can be called directly from your programming environment (such as Microsoft C/C++ or LabVIEW).

  • Page 15: I/O Object

    • • Example Figure 1-2 shows an example of how NI-DNET objects can be used to communicate on a DeviceNet network. This example shows three DeviceNet devices. The first device (at MAC ID 1) is the National Instruments DeviceNet interface. The second device (at MAC ID 5) uses NI-DNET to access a polled and a COS I/O connection simultaneously.

  • Page 16: Using Ni-Can With Ni-Dnet

    CAN card. The general rule is that each CAN card can only be used for one API at a time. Use of NI-DNET is restricted to port 1 (top port) of Series 1 CAN cards. For more information on hardware provided in CAN kits, refer to...
  • Page 17 Chapter 1 NI-DNET Software Overview NI-DNET (default), or CAN for NI-CAN. When the CAN protocol is selected, you can access CAN tools in MAX, such as the Bus Monitor tool that displays CAN messages in their raw form. In order to develop NI-CAN applications, you must install NI-CAN components such as documentation and examples.

  • Page 18: Ni-Dnet Hardware Overview

    All of the DeviceNet hardware uses the Intel 386EX embedded processor to implement time-critical features provided by the NI-DNET software. The cards communicate with the NI-DNET driver through on-board shared memory and an interrupt. The DeviceNet physical communication link protocol is based on the Controller Area Network (CAN) protocol.

  • Page 19: Differences Between Can Kits And Devicenet Kits

    Manual. Hardware in CAN kits offers 1-port and 2-port variants. NI-DNET operates on one port only. If you use NI-DNET on a 2-port Series 1 CAN card, only the top port can be used. Hardware in CAN kits offer special transceivers (physical layer) such as Low-Speed/Fault-Tolerant (LS) and Single-Wire (SW).

  • Page 20: Developing Your Application

    These examples teach basic NI-DNET programming as well as advanced topics. The example help describes each example and includes a link you can use to open the VI. The NI-DNET example help is in Help»Find Examples»Hardware Input and Output»DeviceNet. © National Instruments Corporation ™...

  • Page 21: Labwindows/Cvi

    LabWindows/CVI (Microsoft or Borland), and copies an appropriate nidnet.lib Microsoft Visual Basic To create an NI-DNET application in Visual Basic, add the file to your project. This allows you to call any NI-DNET function file from your code. NI-DNET National Instruments\NI-DNET\MS Visual Basic The reference for each NI-DNET function is provided in the NI-DNET Programmer Reference Manual, which you can open from Start»All...

  • Page 22: Microsoft C/C

    #define _cplusplus #include "nidnet.h" NI-DNET functions. The reference for each NI-DNET function is provided in the NI-DNET Programmer Reference Manual, which you can open from Start»All Programs»National Instruments»NI-DNET. You can find examples for Visual C++ in the example is in a separate folder.

  • Page 23: Other Programming Languages

    #define _cplusplus #include "nidnet.h" NI-DNET functions. The reference for each NI-DNET function is provided in the NI-DNET Programmer Reference Manual, which you can open from Start»All Programs»National Instruments»NI-DNET. You can find examples for Visual C++ in the...
  • Page 24 © National Instruments Corporation Get the addresses for the NI-DNET DLL functions you will use. Your application must use the Win32 get the addresses of the NI-DNET functions your application needs. For each NI-DNET function used by your application, you must define a direct entry prototype.

  • Page 25: Programming Model For Ni-Dnet Applications

    Developing Your Application Programming Model for NI-DNET Applications The following steps provide an overview of how to use the NI-DNET functions in your application. The steps are shown in Figure 3-1 in flowchart form. The NI-DNET functions are described in detail in the NI-DNET Programmer Reference Manual.
  • Page 26 PollMode is not equal to NC_POLL_AUTO Finished? Stop communication 1. Close I/O and EM objects. 2. Close the Interface object. Figure 3-1. General Programming Steps for an NI-DNET Application Chapter 3 Developing Your Application NI-DNET User Manual...

  • Page 27: Step 1. Open Objects

    For an I/O Object, if your application is multitasking, call the ncCreateNotification parameter set to DesiredState your application when new input data is received from the remote device. For any NI-DNET object, if any of the Driver attributes needs to be changed, call ncSetDriverAttr value. The ncSetDriverAttr communication has started.

  • Page 28: Addition Of Slave Connections After Communication Start

    Automatic mode is selected. The EPR restrictions due to different values of the apply to the I/O objects. For details on these requirements, refer to ncOpenDnetIO NI-DNET Programmer Reference Manual. © National Instruments Corporation Call the function with the...

  • Page 29: Step 4. Stop Communication

    DeviceNet connections to remote devices. Use the Interface Object to call the Stop Step 5. Close Objects Before you exit your application, close all NI-DNET objects using the ncCloseObject Multiple Applications on the Same Interface The NI-DNET software allows multiple NI-DNET applications to use the same interface object simultaneously, as long as the interface configuration remains the same.

  • Page 30: Checking Status In Labview

    This status value is zero for success, greater than zero for a warning, and less than zero for an error. After every call to an NI-DNET function, your program should check to see if the return status is nonzero. If so, call the to obtain an ASCII string which describes the error/warning.
  • Page 31 Developing Your Application Your application code should check the status returned from every NI-DNET function. If an error is detected, you should close all NI-DNET handles, then exit the application. If a warning is detected, you can display a message for debugging purposes, or simply ignore the warning.

  • Page 32: Ni-Dnet Programming Techniques

    After you start communication, the embedded microprocessor on your National Instruments DeviceNet interface transmits messages at the ExpPacketRate your NI-DNET application does not need to be concerned with the timing of messages on the DeviceNet network. © National Instruments Corporation Overview.

  • Page 33: Strobed I/O

    You must also allow time for other I/O messages and explicit messages to occur in the the time needed, let NI-DNET calculate a safe value for you (refer to the section Figure 4-1 shows a timing example for four strobed devices at MAC ID 9, 11, 12, and 13.

  • Page 34: Polled I/O

    Polled I/O Polled I/O connections use a separate poll command and response message for each device. The overall scheme that NI-DNET uses to time polled I/O connections is determined by the PollMode ncOpenDnetIO The following sections describe different schemes you can use for polled I/O.
  • Page 35 Chapter 4 NI-DNET Programming Techniques • Figure 4-2 shows a scanned polling example for four polled devices at MAC ID 14, 17, 20, and 30. The shaded areas indicate other message traffic, such as the strobed I/O messages shown in Figure 4-1.
  • Page 36 NI-DNET Programming Techniques background polling maintains overall network consistency because NI-DNET evenly disperses all background poll commands among multiple foreground cycles. In other words, all background poll commands are not sent in quick succession and thus do not generate quick bursts of traffic on the network.

  • Page 37: Cyclic I/O

    I/O connections are more commonly used for input data from slave to master. For NI-DNET, this means that for cyclic I/O connections, is normally called with Just as for individually polled I/O, you should use smaller MAC IDs for smaller cyclic I/O I/O traffic is prioritized properly.

  • Page 38: Change-Of-State (Cos) I/O

    I/O connection with a larger MAC ID than the COS I/O device. Automatic EPR Feature For cyclic I/O connections, a valid your call to ExpPacketRate can be set to a large value. © National Instruments Corporation Chapter 4 ExpPacketRate ExpPacketRate InhibitTimer Back to Back...

  • Page 39: Using I/O Data In Your Application

    I/O connections (scanned I/O). After you start communication, you can use the function to determine the value calculated for value, you can then experiment with other using The following information is used by NI-DNET to calculate a safe EPR: • • • •...
  • Page 40 • • After you open an NI-DNET I/O Object and start communication, you use remote device. Both of these functions access the entire assembly as an array of bytes. In most cases, the array of bytes for an input or output assembly contains more than one value.

  • Page 41: Accessing I/O Members In Labview

    (lowest byte first), and the equivalent LabVIEW Motorola byte ordering (highest byte first). To make it easier for you to avoid these data type issues in your LabVIEW application, NI-DNET provides two functions to convert between LabVIEW data types and DeviceNet data types: ncConvertForDnetWrite functions are used to access individual members of an I/O assembly using normal LabVIEW controls and indicators.

  • Page 42: Accessing I/O Members In C

    For more information on the ncConvertFromDnetRead Reference Manual. For information on LabVIEW data types and their equivalent DeviceNet data types, refer to Chapter 1, NI-DNET Data Types, in the NI-DNET Programmer Reference Manual. Accessing I/O Members in C Since DeviceNet data types are very similar to C language data types, individual I/O members can be accessed in a straightforward manner.

  • Page 43: Using Explicit Messaging Services

    Chapter 4 NI-DNET Programming Techniques For information on NI-DNET’s C language data types and their equivalent DeviceNet data types, refer to Chapter 1, NI-DNET Data Types, of the NI-DNET Programmer Reference Manual. Using Explicit Messaging Services The NI-DNET Explicit Messaging Object represents an explicit messaging connection to a remote DeviceNet device.

  • Page 44: Other Explicit Messaging Services

    For the C programming language, the attribute’s DeviceNet data type determines the corresponding NI-DNET data type you use to declare a variable for the attribute’s value. For example, if the attribute’s DeviceNet...

  • Page 45: Handling Multiple Devices

    Chapter 4 NI-DNET Programming Techniques Specification defines the overall format of these services, in most cases their meaning and service data are object-specific or vendor-specific. Unless your device requires such services and documents them in detail, you probably do not need them for your application.

  • Page 46: Object Handles

    To create a local variable, right-click on the indicator, select Create»Local Variable, right-click on the local variable, and select Change To Read Local. For more information on local variables, refer to the LabVIEW online reference. © National Instruments Corporation ncOpenDnetIO NCTYPE_UINT32DeviceMacId; NCTYPE_CONN_TYPEConnectionType;...

  • Page 47: Main Loop

    Within a single-loop application, error handling is often done for the entire application as a whole. In the C programming language, this means that when an error is detected with any NI-DNET object, you display the error and exit the application. In LabVIEW, this means that you wire all error clusters of NI-DNET VIs together.

  • Page 48: Appendix A Devicenet Overview

    Specification and provides services to facilitate development of DeviceNet devices and tools by various vendors. Due in large part to the efforts of ODVA, hundreds of different vendors now provide DeviceNet products for a wide range of applications. © National Instruments Corporation NI-DNET User Manual...

  • Page 49: Physical Characteristics Of Devicenet

    • • • • For complete information on how to connect your National Instruments hardware onto the DeviceNet network, refer to your getting started manual. General Object Modeling Concepts The DeviceNet Specification uses object-oriented modeling to describe the behavior of different components in a device, how those components relate to one another, and how network communication takes place.

  • Page 50: Object Modeling In The Devicenet Specification

    Object Modeling in the DeviceNet Specification Figure A-2 illustrates the object modeling used within the DeviceNet Specification. © National Instruments Corporation Class Square Class Triangle Figure A-1. Classes of Geometric Shapes Appendix A...
  • Page 51 Attributes of each Connection Object instance include the maximum number of bytes produced on the connection, the maximum number of bytes consumed, and the expected rate at which data is transferred. NI-DNET User Manual Parameter Object Message...

  • Page 52: Explicit Messaging Connections

    NI-DNET functions do not directly correspond to the services defined by DeviceNet. To facilitate access to your DeviceNet network, the features provided by the NI-DNET driver are a simplification of the objects and services defined in the DeviceNet Specification. Explicit Messaging Connections Each device on the DeviceNet network supports at least one explicit messaging connection.
  • Page 53 The DeviceNet Specification defines a set of services supported in a common way by different devices. These common services include Reset, Save, Restore, Get Attribute Single, and Set Attribute Single. NI-DNET User Manual Table A-2. Explicit Message Request Description Table A-3. Explicit Message Response Description ni.com...

  • Page 54: I/O Connections

    Since these two services are used often, NI-DNET provides functions for these services: Other services defined by DeviceNet are used less often. For these services, NI-DNET provides general purpose functions to send an explicit message request ( response ( parameters which are similar to the explicit message request/response listed above.
  • Page 55 Strobed I/O is also called bit strobed I/O since the master sends a 64-bit (8-byte) message containing a single bit of output data for each strobed NI-DNET User Manual Master MAC ID = 1...
  • Page 56 (EPR). Since COS and cyclic I/O connections use the same messaging on the DeviceNet network, they are often referred to as a single I/O connection called COS/cyclic I/O. © National Instruments Corporation Master MAC ID = 1...
  • Page 57 For information on how to suppress COS/cyclic acknowledgments using NI-DNET, refer to the description of the I/O Object in the NI-DNET Programmer Reference Manual. Since COS and cyclic I/O use the same messages on the DeviceNet network, they cannot be used simultaneously for a given slave device.

  • Page 58: Assembly Objects

    Input assemblies gather multiple attributes within the slave for transmission on an I/O connection. Figure A-6 shows the operation of input and output assemblies. © National Instruments Corporation Master MAC ID = 1 Cyclic ACK...
  • Page 59 Figure A-7 shows an example of a Presence Sensing instance and its input assembly. NI-DNET User Manual Instance Attributes Figure A-6. Input and Output Assemblies Presence Sensor Instance 1...
  • Page 60 This chapter provides only a short summary of DeviceNet. For additional information, such as a list of DeviceNet products and how to purchase the DeviceNet Specification, refer to the ODVA Web site at © National Instruments Corporation Exhibit the same behavior Use the same object model (certain instances are required)

  • Page 61: Appendix B Cabling Requirements

    These signals should be connected using twisted-pair cable. The V+ and V– signals supply power to the DeviceNet physical layer. Refer to the information. © National Instruments Corporation 3 Shield 4 CAN_L Figure B-1. Pinout for 5-Pin Combicon-Style Pluggable Screw Terminal Power Supply Information for the DeviceNet Ports 5 V–...
  • Page 62 9-pin D-SUB following the pinout in Figure B-3. The 9-pin D-SUB follows the pinout recommended by CiA Draft Standard 102. Figure B-3 shows the pinout for this connector. NI-DNET User Manual Figure B-2. PCMCIA-CAN Bus-Powered Cable Optional Ground (V–) CAN_H No Connection Figure B-3.

  • Page 63: Power Supply Information For The Devicenet Ports

    For the PCI-CAN, a jumper controls the source of power for the DeviceNet physical layer. The location of this jumper is shown in Figure B-4. 1 Power Supply Jumper J6 2 Product Name © National Instruments Corporation Table B-1. Power Requirements for the DeviceNet Physical Layer for Bus-Powered Versions Characteristic...
  • Page 64 For port one of the PXI-8461, power is configured with jumper J5. The location of these jumper is shown in Figure B-6. NI-DNET User Manual a. Internal Power Mode Figure B-5. Power Source Jumpers b.
  • Page 65 V– signal serves as the reference ground for the isolated signals. The PCMCIA-CAN is shipped with the bus power version of the PCMCIA-CAN cable. An internally-powered version of the PCMCIA-CAN cable can be ordered from National Instruments. © National Instruments Corporation 3 Assembly Number 4 Product Name Figure B-6.

  • Page 66: Cable Specifications

    If all of the devices on the network meet the DeviceNet specifications, 64 devices may be connected to the network. NI-DNET User Manual Table B-2. DeviceNet Cable Length Specifications Baud Rate...

  • Page 67: Cable Termination

    DeviceNet requires a cable with a nominal impedance of 120 Ω; therefore, a 120 Ω resistor should be used at each end of the cable. Each termination resistor should each be capable of dissipating at least 0.25 W of power. © National Instruments Corporation DeviceNet DeviceNet Device...

  • Page 68: Cabling Example

    Combicon D-Sub Pin 4 Pin 7 Pin 2 Pin 2 Pin 3 Pin 5 Pin 5 Pin 9 Pin 1 Pin 3 NI-DNET User Manual CAN_H 120 Ω CAN_L V– Power Connector V– Figure B-8. Cabling Example 9-Pin 5-Pin D-Sub...

  • Page 69: Troubleshooting And Common Questions

    Troubleshooting and Common Questions This appendix describes how to troubleshoot problems with the NI-DNET software and answers some common questions. Troubleshooting with the Measurement & Automation Explorer (MAX) MAX contains configuration information for all CAN (DeviceNet) hardware installed on your system. To start MAX, double-click on the Measurement &...

  • Page 70: Troubleshooting Self Test Failures

    CAN card. The self test aborts to avoid adversely affecting your application. Before running the self test, exit all applications that use NI-DNET or NI-CAN. If you are using LabVIEW, you may need to exit LabVIEW to unload the NI-DNET driver.

  • Page 71: Common Questions

    Within MAX, open the Software branch and select NI-DNET. The version is displayed in the right pane of MAX. How many CAN cards can I configure for use with my NI-DNET software? The NI-DNET software can be configured to communicate with up to 32 CAN cards on all supported operating systems.
  • Page 72 Windows NT does not allow more than one PCMCIA card of the same type installed. Thus, you cannot use two NI PCMCIA cards in the same system. Why are some components left after the NI-DNET software is uninstalled? The uninstall program removes only items that the installation program installed.

  • Page 73: Hardware Specifications

    Dimensions... 8.56 by 5.40 by 0.5 cm Power requirement ... 500 mA typical I/O connector... Cable with 9-pin D-SUB and Operating environment © National Instruments Corporation Ambient temperature ... 0 to 55 °C Relative humidity... 10 to 90%, noncondensing Ambient temperature ... –20 to 70 °C Relative humidity...
  • Page 74 Operating environment Storage environment Functional Shock ...30 g peak, half-sine, 11ms pulse Random Vibration NI-DNET User Manual Ambient temperature ...–20 to 70 °C Relative humidity ...5 to 90%, noncondensing Ambient temperature ...0 to 55 °C Relative humidity ...10 to 90%, noncondensing Ambient temperature ...–20 to 70 °C...

  • Page 75: Electromagnetic Compatibility

    Electrical immunity... Evaluated to EN 61326:1997 CE, C-Tick, and FCC Part 15 (Class A) Compliant Note For EMC compliance, operate this device with shielded cabling. © National Instruments Corporation EN 61010-1, IEC 61010-1 UL 3111-1, UL 61010B-1 CAN/CSA C22.2 No. 1010.1...
  • Page 76 Refer to the Declaration of Conformity (DoC) for this product for any additional regulatory compliance information. To obtain the DoC for this product, visit ni.com/hardref.nsf appropriate link in the Certification column. NI-DNET User Manual , search by model number or product line, and click the ni.com...

  • Page 77: Technical Support And Professional Services

    Technical Support and Professional Services Visit the following sections of the National Instruments Web site at ni.com • • • If you searched your local office or NI corporate headquarters. Phone numbers for our worldwide offices are listed at the front of this manual. You also can visit...
  • Page 78 American National Standards Institute Application A collection of functions used by a user application to access hardware. Programming Interface Within NI-DNET, you use API functions to make calls into the NI-DNET (API) driver. ASCII American Standard Code for Information Exchange...
  • Page 79 A thermostat is a simple example of a controller. COS I/O See change-of-state I/O. cyclic I/O Master/slave I/O connection in which the slave (or master) sends data at a fixed interval. NI-DNET User Manual ni.com...
  • Page 80 Microsoft Win 32 functions used to directly access the functions of a Dynamic Link Library (DLL). Dynamic Link Library driver attributes Attributes of the NI-DNET driver software. Electronic Data Sheet. Text file that describes DeviceNet device features electronically. expected packet rate The rate (in milliseconds) at which a DeviceNet connection is expected to transfer its data.
  • Page 81 Kilobytes of memory LabVIEW Laboratory Virtual Instrument Engineering Workbench light-emitting diode local Within NI-DNET, anything that exists on the same host (personal computer) as the NI-DNET driver. meter MAC ID Media access control layer identifier. In DeviceNet, a device’s MAC ID represents its address on the DeviceNet network.
  • Page 82 Device driver and/or firmware that implement all the specifics of a National Instruments DeviceNet interface. notification Within NI-DNET, an operating system mechanism that the NI-DNET driver uses to communicate events to your application. You can think of a notification of as an API function, but in the opposite direction.
  • Page 83 A formal set of conventions or rules for the exchange of information among devices of a given network. Random-access memory remote Within NI-DNET, anything that exists in another device of the device network (not on the same host as the NI-DNET driver). resource Hardware settings used by National Instruments DeviceNet hardware,...
  • Page 84 An action performed on an instance to affect its behavior; the externally visible code of an object. Within NI-DNET, you use NI-DNET functions to execute services for objects. Also known as method and operation. strobed I/O volts Virtual Instrument Virtual device driver ©...
  • Page 85 NI-CAN hardware problem encountered, NI-CAN software problem encountered, examples (NI resources), E-1 help, technical support, E-1 installation and configuration NI-DNET cards listed in MAX (figure), 1-2 verifying through MAX, 1-1 change protocol, 1-3 configure DNET port, 1-3 instrument drivers (NI resources), E-1...
  • Page 86 Index LabVIEW Real-Time (RT) software configuration, 1-3 tools, 1-3 NI-DNET cards listed in MAX (figure), tools launched from, 1-3 Measurement & Automation Explorer (MAX). See MAX memory resource conflict, troubleshooting, missing CAN card, troubleshooting, C-1 National Instruments support and services,...

This manual is also suitable for:

Devicenet ni-dnet

Table of Contents