National Instruments NI-DNET User Manual Download Page 75

Page: 75 / 86

Appendix D

Hardware Specifications

National Instruments Corporation

D-3

NI-DNET User Manual

Port Characteristics

Bus power .............................................. 0 to 30 V, 40 mA typical,

100 mA maximum

CAN-H, CAN-L..................................... –8 to +18 V, DC or peak, CATI

Safety

The NI-CAN hardware meets the requirements of the following standards
for safety and electrical equipment for measurement, control, and
laboratory use:

•

EN 61010-1, IEC 61010-1

•

UL 3111-1, UL 61010B-1

•

CAN/CSA C22.2 No. 1010.1

Note

For UL and other safety certifications, refer to the product label, or visit

ni.com/hardref.nsf

, search by model number or product line, and click the

appropriate link in the Certification column.

Pollution Degree .................................... 2

Maximum altitude .................................. 2,000 m

Indoor use only.

Electromagnetic Compatibility

Electrical emissions................................ EN 55011 Class A at 10 m FCC

Part 15A above 1 GHz

Electrical immunity................................ Evaluated to EN 61326:1997

+A2:2001, Table 1

CE, C-Tick, and FCC Part 15 (Class A) Compliant

Note

For EMC compliance, operate this device with shielded cabling.

Summary of Contents for NI-DNET

Page 1: ...DeviceNet T NI DNET TM User Manual NI DNET User Manual May 2004 Edition Part Number 370375B 01 ...

Page 2: ...9 741 31 30 Greece 30 2 10 42 96 427 India 91 80 51190000 Israel 972 0 3 6393737 Italy 39 02 413091 Japan 81 3 5472 2970 Korea 82 02 3451 3400 Malaysia 603 9131 0918 Mexico 001 800 010 0793 Netherlands 31 0 348 433 466 New Zealand 0800 553 322 Norway 47 0 66 90 76 60 Poland 48 22 3390150 Portugal 351 210 311 210 Russia 7 095 783 68 51 Singapore 65 6226 5886 Slovenia 386 3 425 4200 South Africa 27 ...

Page 3: ...installation operation or maintenance instructions owner s modification of the product owner s abuse misuse or negligent acts and power failure or surges fire flood accident actions of third parties or other events outside reasonable control Copyright Under the copyright laws this publication may not be reproduced or transmitted in any form electronic or mechanical including photocopying recording...

Page 4: ...nge Protocol 1 3 LabVIEW Real Time RT Configuration 1 3 Tools 1 3 NI Spy 1 4 SimpleWho 1 4 NI DNET Objects 1 4 Interface Object 1 5 Explicit Messaging Object 1 5 I O Object 1 6 Example 1 6 Using NI CAN with NI DNET 1 7 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 Progr...

Page 5: ...d Packet Rate 4 1 Strobed I O 4 2 Polled I O 4 3 Cyclic I O 4 6 Change of State COS I O 4 7 Automatic EPR Feature 4 7 Using I O Data in Your Application 4 8 Accessing I O Members in LabVIEW 4 10 Accessing I O Members in C 4 11 Using Explicit Messaging Services 4 12 Get and Set Attributes in a Remote DeviceNet Device 4 12 Other Explicit Messaging Services 4 13 Handling Multiple Devices 4 14 Configu...

Page 6: ...cifications B 6 Cable Lengths B 6 Maximum Number of Devices B 6 Cable Termination B 7 Cabling Example B 8 Appendix C 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 ...

Page 7: ...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 Use the NI DNET Programmer Reference Manual for specific information about each NI DNET function and object First Time NI DNET Users Experienced NI DNET Users NI DNET Programmer Reference Manual Fun...

Page 8: ... word or value that you must supply monospace Text in this font denotes text or characters that you should enter from the keyboard sections of code programming examples and syntax examples This font is also used for the proper names of disk drives paths directories programs subprograms subroutines device names functions operations variables filenames and extensions Related Documentation The follow...

Page 9: ...About This Manual National Instruments Corporation xi NI DNET User Manual LabVIEW online reference ODVA website www odva org Microsoft Win32 Software Development Kit SDK online help ...

Page 10: ...ithin your Windows Programs menu under National Instruments Measurement Automation For information about the NI DNET software within MAX consult the MAX online help A reference is in the MAX Help menu under Help Topics NI DNET View help for items in the MAX Configuration tree by using the built in MAX help pane If this help pane is not shown on the far right select the Show Hide button in the uppe...

Page 11: ... MAX is not configured to search for new devices on startup To search for the new hardware press F5 To verify installation of your DeviceNet hardware right click the DeviceNet card then select Self test If the self test passes the card icon shows a checkmark 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 Troubles...

Page 12: ...I DeviceNet card and use the NI DNET APIs to develop real time applications For example you can control a network of DeviceNet devices as a master and write your control algorithm in LabVIEW When you install the NI DNET software the installer checks for the presence of the LabVIEW RT module If LabVIEW RT exists the NI DNET installer copies components for LabVIEW RT to your Windows system As with a...

Page 13: ...This tool is not a complete network management or configuration tool It provides read only information about the DeviceNet devices connected to your National Instruments DeviceNet interface To launch SimpleWho right click the DeviceNet interface such as DNET0 in MAX and select SimpleWho For more information on the SimpleWho tool refer to the NI DNET help file in MAX This help file can be opened us...

Page 14: ...l attributes in remote DeviceNet devices For complete information on each NI DNET object including its driver attributes and supported functions services refer to your NI DNET Programmer Reference Manual Interface Object The Interface Object represents a DeviceNet interface physical DeviceNet port on your DeviceNet board Since this interface acts as a device on the DeviceNet network much like any ...

Page 15: ...Specification This means that you can use polled strobed and COS cyclic I O connections simultaneously for a given device As specified by the DeviceNet Specification only one master slave I O connection of a given type can be used for each device MAC ID For example you cannot open two polled I O connections for the same device Use the I O Object to do the following Read data from the most recent m...

Page 16: ...ion of sections of the DeviceNet Specification yourself such as custom configuration tools NI CAN uses the same software infrastructure as NI DNET so both APIs can be used with the same 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 ref...

Page 17: ... same manner as your original installation CD or ni com download Within the installer select both NI DNET and NI CAN components in the feature tree When you right click a port in MAX and select Properties the resulting Interface selection uses the syntax CANx or DNETx based on your protocol selection Regardless of which protocol is selected the number x is the only relevant identifier with respect...

Page 18: ...l DeviceNet devices PCMCIA CAN hardware is a 16 bit Type II PC Card that is software configurable and compliant with the PCMCIA standards for 16 bit PC cards With a PCMCIA CAN card you can make your PC compatible notebook with PCMCIA slots communicate with and control DeviceNet devices The PCI CAN PXI 8461 or PCMCIA CAN in your DeviceNet kit is fully compliant with the DeviceNet Specification All ...

Page 19: ...tware Hardware in CAN kits is referenced as Series 2 Hardware in DeviceNet kits is referenced as Series 1 Series 2 CAN cards cannot be used with the NI DNET software NI CAN only The features of Series 2 CAN cards are specifically designed for CAN applications and provide no distinct advantages for DeviceNet For more information on Series 2 hardware refer to the hardware overview in the NI CAN Hard...

Page 20: ...ntrols and examples NI DNET functions and controls are available in the LabVIEW palettes In LabVIEW 7 1 or later the NI DNET palette is located within the top level NI Measurements palette In earlier LabVIEW versions the NI DNET palette is located at the top level The reference for each NI DNET function is provided in the NI DNET Programmer Reference Manual To access the reference for a function f...

Page 21: ...ation for NI DNET it is automatically linked with nidnet lib the link library for LabWindows CVI When NI DNET is installed the installation program checks to see which compatible C compiler you are using with LabWindows CVI Microsoft or Borland and copies an appropriate nidnet lib for that compiler Microsoft Visual Basic To create an NI DNET application in Visual Basic add the nidnet bas file to y...

Page 22: ...on from C to the C language 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 examples subfolder of the MS Visual C folder Each example is in a separate folder A c file with the same name as the example contains a descripti...

Page 23: ... folder Each example is in a separate folder A c file with the same name as the example contains a description the example in comments at the top of the code Other Programming Languages You can directly access NI DNET from any programming environment that allows you to request addresses of functions that a dynamic link library DLL exports The functions used to access a DLL in this manner are provi...

Page 24: ...S _NCFUNC_ PncOpenDnetIO NCTYPE_STRING ObjName NCTYPE_OBJH_P ObjHandlePtr static NCTYPE_STATUS _NCFUNC_ PncCloseObject NCTYPE_OBJH ObjHandle static NCTYPE_STATUS _NCFUNC_ PncReadDnetIO NCTYPE_OBJH ObjHandle NCTYPE_UINT32 SizeofData NCTYPE_ANY_P Data PncOpenDnetIO NCTYPE_STATUS _NCFUNC_ NCTYPE_STRING NCTYPE_OBJH_P GetProcAddress NidnetLib LPCSTR ncOpenDnetIO PncCloseObject NCTYPE_STATUS _NCFUNC_ NC...

Page 25: ...NET0 MyObjh if status 0 printf ncOpenDnetIO failed 4 Free nican dll Before exiting your application you need to free nican dll with the following command FreeLibrary NidnetLib 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 describ...

Page 26: ...aging EM objects required for your application 3 Call ncSetDriverAttr if needed Start communication Your DeviceNet Application Write output data Wait for available input data Read input data Get or Set DeviceNet Attribute Open Close any new I O or EM connection if the interface PollMode is not equal to NC_POLL_AUTO Stop communication Yes No 1 Close I O and EM objects 2 Close the Interface object S...

Page 27: ...Intf function with the Opcode parameter set to Start The following optional steps can be done before you start communication For an I O Object if it is not acceptable to send output data of all zeros call ncWriteDnetIO to provide valid output values for the initial transmission For an I O Object if your application is multitasking call the ncCreateNotification or ncCreateOccurrence function with t...

Page 28: ... 3 To set the value of an attribute in a remote DeviceNet device call the ncSetDnetAttribute function 4 To invoke other explicit message services in a remote DeviceNet device use the ncWriteDnetExplMsg function to write the service request the ncWaitForState function to wait for the service response and the ncReadDnetExplMsg function to read the service response 5 Loop back to step 2 as needed Add...

Page 29: ...ules apply to the I O Object and the Explicit Messaging Object As long as all the configuration attributes are the same any object can be opened multiple times You can enable only one notification or wait through ncWaitForState ncCreateNotification or ncCreateOccurrence functions for an object no matter how many handles you have opened for that particular object For example if you are running two ...

Page 30: ...ll NI DNET functions wired together are skipped except for ncCloseObject The ncCloseObject function executes regardless of whether an error occurred thus ensuring that all NI DNET objects are closed properly when execution stops due to an error Depending on how you want to handle errors you can wire the Error in and Error out terminals together per object group a single open close pair per device ...

Page 31: ...very 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 For more information on status checking refer to the ncStatusToString function in the NI DNET Programmer Reference Manual ...

Page 32: ...l I O communication Within your NI DNET application the ncOpenDnetIO function configures the timing for I O connections in which your application communicates as master As you read this section you might want to refer to the description of the ncOpenDnetIO function in the NI DNET Programmer Reference Manual Expected Packet Rate Each DeviceNet I O connection contains an attribute called the expecte...

Page 33: ...sfer data at the rate of this single strobe command message the ExpPacketRate of each strobed I O connection must be set to the same value The common ExpPacketRate for all strobed I O connections should provide enough time for the strobe command and each strobed slave s response You must also allow time for other I O messages and explicit messages to occur in the ExpPacketRate time frame If you do...

Page 34: ...andle I O connections that require similar response rates With scanned I O the master knows that all strobe and poll commands go out at the same time Therefore the master does not need to manage individual timers thus optimizing processing overhead Scanned I O also provides overall consistency If a given DeviceNet system uses only scanned I O you know that all higher level control algorithms can e...

Page 35: ... device 30 respond well within 20 ms the common ExpPacketRate would need to be at least 52 ms This situation can often be avoided using a special case of scanned polling called background polling To configure background polling you first set the PollMode parameter of ncOpenDnetIntf to Scanned Then for each polled I O connection you configure ncOpenDnetIO with ConnectionType set to Poll you must se...

Page 36: ... ms 35 ms 100 ms and 700 ms respectively Each device responds to its poll command within 1 ms but measures data at a different rate such as a pushbutton for 10 ms and a temperature sensor for 700 ms You could group these into a foreground rate of 10 ms and a background rate of 700 ms but then much DeviceNet bandwidth would be wasted polling the 35 ms and 100 ms devices at the foreground rate For t...

Page 37: ...onnections essentially use the same timing scheme as individually polled I O connections Each cyclic I O connection sends its data at the configured ExpPacketRate The main difference is that cyclic I O data is transferred from slave to master rather than from master to slave In the DeviceNet Specification a poll command message is exactly the same as a cyclic output message master to slave data Si...

Page 38: ... thus dramatically impairing overall DeviceNet performance This problem is demonstrated in Figure 4 5 Figure 4 5 Congestion Due to Back to Back COS I O This problem can be prevented if you increase the MAC ID of the frequently changing COS I O device If the COS device has a higher MAC ID than other devices it cannot preclude their I O messages You can also prevent back to back COS I O messages if ...

Page 39: ...is the only master in your DeviceNet system The BaudRate parameter of ncOpenDnetIntf determines the time taken for each message The InputLength and OutputLength parameters of each ncOpenDnetIO determine the time needed for each I O message NI DNET assumes that each strobed polled I O device can respond to its command within 2 ms NI DNET sets aside a fixed amount of time for explicit messages This ...

Page 40: ...ssembly often shown as a table with byte bit offsets and a listing of the attribute in the device that each member represents often shown as class instance and attribute identifiers For standard device profiles the I O assemblies are documented in the device profile s specification and the actual attributes are documented in the individual object specifications Attribute documentation includes the...

Page 41: ...wo functions to convert between LabVIEW data types and DeviceNet data types ncConvertForDnetWrite and ncConvertFromDnetRead These functions are used to access individual members of an I O assembly using normal LabVIEW controls and indicators The following steps show an example of how you can use ncConvertForDnetWrite to access the Basic Speed Control Output Assembly described in the previous secti...

Page 42: ... You can use the front panel control that appears to change Speed Reference 11 Using the NI DNET palette place ncWriteDnetIO into your diagram 12 Wire the DnetData out terminal from the previous Convert into the Data terminal of ncWriteDnetIO For more information on the ncConvertForDnetWrite and ncConvertFromDnetRead functions refer to the NI DNET Programmer Reference Manual For information on Lab...

Page 43: ...iteDnetIO objh sizeof OutputAsm OutputAsm 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 You use ncOpenDnetExplMsg to configure ...

Page 44: ... pass the address of that variable as the Attr parameter of the ncGetDnetAttribute or ncSetDnetAttribute function For LabVIEW the attribute s DeviceNet data type determines the corresponding LabVIEW data type to use with the ncConvertForDnetWrite or ncConvertFromDnetRead functions The ncConvertFromDnetRead function converts a DeviceNet attribute read using ncGetDnetAttribute into an appropriate La...

Page 45: ... any object but its actual data format is defined in the specification for the Identity Object The error codes that can be returned in the service response Error codes that are common to all services can be found in Appendix H DeviceNet Error Codes in the DeviceNet Specification manual but many error codes are specific to the service object or vendor As with the ncGetDnetAttribute and ncSetDnetAtt...

Page 46: ...l open calls but instead all open calls are combined into a concise loop Object Handles If you use an array to store configuration parameters for ncOpenDnetIO you can use this same scheme to store the ObjHandle returned by ncOpenDnetIO Within the For loop used for ncOpenDnetIO you can store the resulting ObjHandle into an array of object handles Throughout your code you can index into this array t...

Page 47: ... together If your application uses different control code for different DeviceNet devices you might want to split your application into multiple tasks You can easily write a multitasking application by creating a notification for the NI DNET Read Avail state This notification occurs when either input data is available to synchronize your code with each device s I O messages or an error occurs In t...

Page 48: ...any manufacturers of industrial automation equipment began to consider other applications of CAN technology Automotive and industrial device networks showed many similarities including the transition away from dedicated signal lines low cost resistance to harsh environments and excellent real time capabilities In response to these similarities Allen Bradley developed DeviceNet an industrial networ...

Page 49: ...ted 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 The following paragraphs briefly describe object oriented modeling and how these concepts are used within the DeviceNet Specification In object oriented...

Page 50: ...ome contexts it might also refer to a class Each class defines a set of attributes which represent its externally visible characteristics The set of attributes defined by a class is common to all instances within that class For the class square attributes could include length of each side and color For the class circle attributes could include radius and color Each class also defines a set of serv...

Page 51: ... use the Reset service on instance one of the Identity Object the device resets to its power on state Another class of object contained in every DeviceNet device is the Connection Object Each instance of the Connection Object represents a communication path to one or more devices Attributes of each Connection Object instance include the maximum number of bytes produced on the connection the maximu...

Page 52: ...Net 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 Explicit messaging connections provide a general purpose communication path used to execute servi...

Page 53: ...If the instance ID is one or greater the service is directed to a specific instance within the class Service Data Data bytes specific to the Service Code The number and format of these data bytes is defined by the specification for the service Table A 3 Explicit Message Response Field Description Service Code This number indicates success or failure for execution of the service If this number is t...

Page 54: ...ation path for the exchange of physical input output sensor actuator data as well as other control oriented data I O connections are useful for transferring data at regular intervals Since many DeviceNet devices do not begin their normal operation until an I O connection is established explicit messaging is often used for configuration and initialization For example for a device with an analog inp...

Page 55: ...ich supports polled I O connections Polled I O is typically used for devices which provide both input and output data such as position controllers and modular I O devices Figure A 3 shows an example of four polled slave devices Figure A 3 Polled I O Example Bit Strobed I O The bit strobed I O connection is designed to move small amounts of input data from the slave to its master Strobed I O is typ...

Page 56: ...ave s strobe response contains from 0 to 8 bytes of input data Figure A 4 shows an example of four strobed slave devices Figure A 4 Strobed I O Example Change of State and Cyclic I O The change of state COS and cyclic I O connections both use the same underlying communication mechanisms Both transmit data at a fixed interval called the expected packet rate EPR Since COS and cyclic I O connections ...

Page 57: ...ed COS I O can be configured to send output data from master to slave Although master to slave COS output is seldom used it can be useful for things like front panel pushbuttons which are sent to a slave s discrete outputs such as LEDs and simple motors COS I O messages can contain any amount of data When using COS cyclic I O connections you can configure the device that receives data to send an a...

Page 58: ...going data to its proper location within the device Output assemblies receive an output message from an I O connection and distribute its contents to multiple attributes within the slave 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 Master MAC ID 1 Slave MAC ID 9 Slave MAC ID 11 Slave...

Page 59: ... a single input assembly consisting of a single byte Figure A 7 shows an example of a Presence Sensing instance and its input assembly Figure A 7 Input Assembly for Photoeye or Limit Switch Attributes Instance Attributes Instance Attributes Instance Output Assembly Associated with an Output Message Such as a Poll Command Input Assembly Associated with an Input Message Such as a Poll Response 0 0 0...

Page 60: ...t the same behavior Use the same object model certain instances are required Contain the same input and output assemblies Contain the same set of configurable attributes In addition to required features most device profiles define a variety of optional features When an optional feature is supported by a vendor it must be supported as defined by the DeviceNet Specification Device profiles also allo...

Page 61: ...rminal connector The PCMCIA CAN bus powered cable also has a DB 9 D SUB connector The 5 pin Combicon style pluggable screw terminal follows the pinout required by the DeviceNet Specification Figure B 1 shows the pinout for this connector Figure B 1 Pinout for 5 Pin Combicon Style Pluggable Screw Terminal CAN_H and CAN_L are signal lines that carry the data on the DeviceNet network These signals sh...

Page 62: ... terminal are connected directly to the corresponding pins on the 9 pin D SUB following the pinout in Figure B 3 Figure B 2 PCMCIA CAN Bus Powered Cable The 9 pin D SUB follows the pinout recommended by CiA Draft Standard 102 Figure B 3 shows the pinout for this connector Figure B 3 Pinout for 9 Pin D SUB Connector J 2 J 1 V C _ L S H C _ H V 1 2 3 4 5 6 7 8 9 No Connection CAN_L V No Connection O...

Page 63: ...hown in Table B 1 You should take these requirements into account when determining the requirements of the bus power supply for the system 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 Figure B 4 PCI CAN Power Source Jumper Table B 1 Power Requirements for the DeviceNet Physical Layer for Bus Powered Versio...

Page 64: ...et interface is being used in a system where bus power is not available the jumper may be set in the INT position In this position the physical layer is powered by the host computer or internally The physical layer is still optically isolated Figure B 5 shows how to configure your jumpers for internal or external power supplies Figure B 5 Power Source Jumpers For port one of the PXI 8461 power is ...

Page 65: ...s position for the DeviceNet interface to be compliant with the DeviceNet Specification Connecting pins 2 and 3 of a jumper configures the PXI 8461 physical layer to be powered internally from the board In this configuration the 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...

Page 66: ...iled cable length requirements can be found in the DeviceNet Specification Table B 2 lists the DeviceNet cable length specifications Maximum Number of Devices The maximum number of devices that you can connect to a DeviceNet port depends on the electrical characteristics of the devices on the network If all of the devices on the network meet the DeviceNet specifications 64 devices may be connected...

Page 67: ... termination resistor If multiple devices are placed along the cable only the devices on the ends of the cable should have termination resistors Refer to Figure B 7 for an example of where termination resistors should be placed in a system with more than two devices Figure B 7 Termination Resistor Placement The termination resistors on a cable should match the nominal impedance of the cable Device...

Page 68: ...ample of a cable to connect two DeviceNet devices Figure B 8 Cabling Example 9 Pin D Sub 9 Pin D Sub CAN_H CAN_L GND V V V V 5 Pin Combicon 5 Pin Combicon Pin 7 Pin 4 Pin 7 Pin 4 Pin 2 Pin 2 Pin 5 Pin 3 Pin 9 Pin 5 Pin 3 Pin 1 Pin 2 Pin 2 Pin 5 Pin 3 Pin 9 Pin 5 Pin 3 Pin 1 120 Ω 120 Ω Power Connector ...

Page 69: ...u can test your CAN cards by choosing Tools NI CAN Test all Local NI CAN Cards from the menu or you can right click on an CAN card and choose Self Test If the Self Test fails refer to the Troubleshooting Self Test Failures section of this appendix Missing CAN Card If you have a CAN card installed but no CAN card appears in the configuration section of MAX under Devices and Interfaces you need to s...

Page 70: ...refer to the documentation for your Windows operating system for instructions on how to use the Device Manager to reserve memory resources for legacy boards After the conflict has been resolved run the Self Test again Interrupt Resource Conflict This error occurs if the interrupt resource assigned to a CAN card conflicts with the interrupt resources being used by other devices in the system Resour...

Page 71: ...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 Which CAN hardware for DeviceNet does the NI DNET software support The NI DNET software for supports Port 1 Series 1 High Speed HS cards Although you can use 2 port CAN cards only the top port can be used with NI DNET For m...

Page 72: ... To do so right click the PCMCIA CAN card in MAX and choose Properties Assign resource values that do not conflict with other device resources for either the Interrupt Request IRQ or the Memory Range Initially all NI PCMCIA CAN cards will have the same resources assigned If you have more than one PCMCIA CAN card installed the Self Test will fail You must change the resources of one of the cards ma...

Page 73: ...ombicon style pluggable DeviceNet screw terminal high speed CAN only Operating environment Ambient temperature 0 to 55 C Relative humidity 10 to 90 noncondensing Storage environment Ambient temperature 20 to 70 C Relative humidity 5 to 90 noncondensing PCMCIA CAN Series Dimensions 8 56 by 5 40 by 0 5 cm 3 4 by 2 1 by 0 4 in Power requirement 500 mA typical I O connector Cable with 9 pin D SUB and ...

Page 74: ...ment Ambient temperature 0 to 55 C Relative humidity 10 to 90 noncondensing Storage environment Ambient temperature 20 to 70 C Relative humidity 5 to 95 noncondensing Tested in accordance with IEC 60068 2 1 IEC 60068 2 2 IEC 60068 2 56 Functional Shock 30 g peak half sine 11ms pulse Tested in accordance with IEC 60068 2 27 Test profile developed in accordance with MIL T 28800E Random Vibration Ope...

Page 75: ...1 UL 3111 1 UL 61010B 1 CAN CSA C22 2 No 1010 1 Note For UL and other safety certifications refer to the product label or visit ni com hardref nsf search by model number or product line and click the appropriate link in the Certification column Pollution Degree 2 Maximum altitude 2 000 m Indoor use only Electromagnetic Compatibility Electrical emissions EN 55011 Class A at 10 m FCC Part 15A above ...

Page 76: ...ing as follows Low Voltage Directive safety 73 23 EEC Electromagnetic Compatibility Directive EMC 89 336 EEC Note 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 search by model number or product line and click the appropriate link in the Certification column ...

Page 77: ...r Exchange at ni com exchange National Instruments Application Engineers make sure every question receives an answer Training and Certification Visit ni com training for self paced training eLearning virtual classrooms interactive CDs and Certification program information You also can register for instructor led hands on courses at locations around the world System Integration If you have time con...

Page 78: ...itute Application Programming Interface API A collection of functions used by a user application to access hardware Within NI DNET you use API functions to make calls into the NI DNET driver ASCII American Standard Code for Information Exchange Assembly Object Objects in DeviceNet devices which route I O message contents to from individual attributes in the device attribute The externally visible ...

Page 79: ...ge in the data is detected class A classification of things with similar qualities client In explicit messaging connections the client is the device requesting execution of the service common services Services defined by the DeviceNet specification such that they are largely interoperable connection An association between two or more devices on a network that describes when and how data is transfe...

Page 80: ...he same type direct entry Microsoft Win 32 functions used to directly access the functions of a Dynamic Link Library DLL DLL Dynamic Link Library driver attributes Attributes of the NI DNET driver software E EDS 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 transfe...

Page 81: ...rate instance A specific instance of a given class For example a blue square of 4 inches per side would be one instance of the class Squares ISO International Standards Organization K KB Kilobytes of memory L LabVIEW Laboratory Virtual Instrument Engineering Workbench LED light emitting diode local Within NI DNET anything that exists on the same host personal computer as the NI DNET driver M m met...

Page 82: ...t utility Utility used to manage configuration of DeviceNet devices network who A search of a DeviceNet network to determine information about its devices NI DNET driver 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 appl...

Page 83: ...e of the device network not on the same host as the NI DNET driver resource Hardware settings used by National Instruments DeviceNet hardware including an interrupt request level IRQ and an 8 KB physical memory range such as D0000 to D1FFF hex S s seconds scanned polling A polled I O communication scheme in which all poll commands are sent out at the same rate in quick succession sensor A device t...

Page 84: ...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 See bit strobed I O V V volts VI Virtual Instrument VxD Virtual device driver ...

Page 85: ...used in the manual x conventions related documentation x D diagnostic tools NI resources E 1 documentation conventions x how to use manual set ix NI resources E 1 related conventions x drivers NI resources E 1 E electromagnetic compatibility D 3 error message interrupt resource conflict troubleshooting C 2 memory resource conflict C 2 NI CAN hardware problem encountered C 3 NI CAN software problem...

Page 86: ...aracteristics D 3 programming examples NI resources E 1 PXI 8461 parts locator diagram figure B 5 port characteristics D 3 R related documentation x S safety specifications D 3 self test failures troubleshooting C 2 SimpleWho 1 4 software LabVIEW Real Time RT tools 1 3 LabVIEW Real Time RT configuration 1 3 software NI resources E 1 specifications CE compliance D 4 electromagnetic compatibility D ...

Search results

Summary of Contents for NI-DNET

Reviews:

Related manuals for NI-DNET

Brands by name

Popular brands

National Instruments NI-DNET, User Manual

Search results

Summary of Contents for NI-DNET

Reviews:

Related manuals for NI-DNET

Brands by name

Popular brands