Home

DeviceNet Master (Scanner)

1. MM ID Figure 2 1 Installing a SmartStack Module in an OCS PAGE 10 19 APR 2002 SUP0462 01 CH 2 2 2 Connectors 2 2 1 DeviceNet I O Connector CAN A The DeviceNet I O connector CAN A is located next to the RS 232 serial port It consists of a 5 pin removable screw terminal with the following terminal descriptions Table 2 2 DeviceNet I O Connector Pinout Pin Signal Description DeviceNet Port CAN A Factory Reserved MAINTENANCE h MM GO 0 001DNT002 N A N A Figure 2 2 DNT450 Connectors Figure 2 3 DeviceNet I O Connector As Viewed from Front of Module CAN_L BLUE CAN_H WHITE SHIELD V RED V BLACK A user supplied 1210 14W 1 resistor is needed for termination at EACH END of the network cabling Refer to the DeviceNet cabling specifications for proper location of the terminating resistor SUP0462 01 19 APR 2002 PAGE 11 CH 2 2 3 LED Indicators The DNT450 provides two bi color Red Green diagnostic LEDs on its front panel These LEDs are located on the same side of the module as the Devicenet port and the RS232 port The network status LED is nearest to the edge of the module N A N A RS 232 Port TX RX LEDs Module Status Network Status for DNT450 001DNT001 Figure 2 5 LEDs Table 2 3 Module Status LED MS Module Status LED is There is no power applied to the module Dev
2. To see a summary of I O devices select Network I O Summary This option is used to display a summary of the inputs ls and Als and outputs Qs and AQs of every node on the network configuration It also displays reference addresses To zoom the network view in and out select View then Net Zoom In or Net Zoom Out When done with the configuration utility click on the close icon The X icon in the upper right corner of the utility screen This will close down the utility and save the configuration for downloading to the OCS NOTE The module configuration is actually stored in the OCS that it is running on If the DNT450 module is placed on a different OCS then that OCS will have to be configured with the module and network configuration again This also means however that DNT450 modules can be swapped on a given OCS unit without the need to reprogram anything since the configuration stays with the OCS and not the DNT450 SUP0462 01 19 APR 2002 PAGE 35 CH 7 CHAPTER 7 DEVELOPING USER SOFTWARE 7 1 Software Support for the Polled Connection When using the Polled Connection all inputs from and outputs to the DNT450 are handled by normal ladder programming techniques to set appropriate data values and read any resulting data values Inputs from the DNT450 and the DeviceNet nodes can be read from the PLC s l and Al registers Outputs to the DNT450 and the DeviceNet nodes are placed in the PLC s Q and AQ re
3. It is possible on smaller networks that there could be a simultaneous Polled Response Message pending from each and every node on the network The primary purpose of this technique is to more fully utilize the DeviceNet bandwidth SUP0462 01 19 APR 2002 PAGE 19 CH 3 e The most significant byte of register AI6 contains Fault Data Byte 1 This byte takes on different meanings depending on the fault code e if the fault code is Polled Consumption Size Error this entry displays the consumption size as reported by the specified node e if the fault code is Polled Production Size Error this entry displays the production size as reported by the specified node e if the fault code is Polled Scan Time both bytes of this word 16 bit WORD value reports the actual polled scan time for this node in milliseconds e all other fault codes not used e The least significant byte of register AI6 contains Fault Data Byte 2 This byte takes on different meanings depending on the fault code e if fault code is Polled Consumption Size Error this entry displays the consumption size as indicated by the DNT450 s configuration file for the specified node e if fault code is Polled Production Size Error this entry displays the production size as indicated by the DNT450 s configuration file for the specified node e if the fault code is Polled Scan Time both bytes of this word 16 bit WORD value reports the actual polled scan time for this node e all o
4. DeviceNet node The user is provided a single node window into the fault table PAGE 18 19 APR 2002 SUP0462 01 CH 3 There are three command bits Q registers to allow control over the fault table and the entry being displayed Setting Q3 causes the first node with a fault to be displayed Setting Q4 causes the next node with a fault to be displayed If the node being displayed is the last node with a fault then the first node with a fault will be displayed Setting Q5 causes all entries in the fault table to be cleared Unpredictable results may occur if more than one of command bit Q3 Q4 or Q5 is simultaneously set The user is also provided two Al registers that are used to display fault information about the indicated node Each of these registers are broken into two bytes as indicated below e The least significant byte of register AI5 contains the Node Address of the fault data displayed in the next 3 bytes e The most significant byte of register AI5 contains the Fault Code that exists for the node indicated by the addressed node The fault code can have the following values 0 None Polled Scan Time 2 Timeout waiting for an Explicit Fragmented Acknowledge Response Message 3 Timeout waiting for an Allocate Explicit Connection Response Message 4 Timeout waiting for an Allocate Polled connection Response Message 5 Timeout waiting for a Get Polled Consumption Size Response Message 6 Timeout waiting for a Get Polled Pr
5. Explicit Response Message 11 Unable to Establish an Explicit Connection 12 Unable to Establish a Polled Connection 13 Polled Consumption Size Error 14 Polled Production Size Error AI6 MSB Fault Table Byte 3 Fault Data 1 e if the fault code is Polled consumption size error this entry displays the consumption size as reported by the specified node e if the fault code is Polled production size error this entry displays the production size as reported by the specified node e if the fault code is Polled scan time both bytes of this word 16 bit WORD value reports the actual polled scan time for this node in milliseconds AI6 LSB Fault Table Byte 4 Fault Data 2 e if fault code is Polled consumption size error this entry displays the consumption size as indicated by the DNT450 s configuration file for the specified node e if fault code is Polled production size error this entry displays the production size as indicated by the DNT450 s configuration file for the specified node e if the fault code is Polled scan time both bytes of this word 16 bit WORD value reports the actual polled scan time for this node Note Many DeviceNet nodes also provide additional diagnostic data within their individual data assemblies PAGE 24 19 APR 2002 SUP0462 01 CH 4 NOTES SUP0462 01 19 APR 2002 PAGE 25 CH 5 CHAPTER 5 EXPLICIT MESSAGING USING DNT450 5 1 General The DNT450 supports both POLLED and EXPLICIT connectio
6. al gt oo o PAGE 22 19 APR 2002 SUP0462 01 CH 4 Q1 Stop DeviceNet Scanning Setting this bit causes the DNT450 to close or release all connections between itself and all DeviceNet nodes No further communications will occur between the DNT450 and the DeviceNet nodes until the Stop DeviceNet Scanning bit is cleared While the scanning is stopped the DeviceNet Scanning is Stopped bit l2 bit will be set Q3 Display the first node with a fault Displays the fault data for the lowest addressed node that has an entry in the fault table Q4 Display the next node with a fault Displays the next node Q5 Clear all fault codes Clears all entries in the fault table l1 Someone is Off Line This status bit indicated that one or more configured nodes are not on line l2 DeviceNet Scanning is Stopped This status bit indicates that the DeviceNet scanning is stopped as a result of the bit Q1 Stop DeviceNet Scanning having been set by the PLC AI1 On Line Status of Nodes 00 15 AI2 On Line Status of Nodes 16 31 AI3 On Line Status of Nodes 32 47 AI4 On Line Status of Nodes 48 63 These four Al registers collectively contain 64 individual status bits One bit is assigned to each of the 64 possible DeviceNet node addresses Status bits for nodes O through 15 are mapped into the first Al register Status bits for nodes 16 through 31 are mapped into the second Al register Status bits for nodes 32 through 47 are mapped int
7. inactivity timer each time it receives a polled request message from the DNT450 If the timer expires the node will enter the timed out state effectively taking itself off line Specify the node s Minimum Polled Scan Time This is the minimum amount of time that the DNT450 will wait between sending polled requests to the node In effect this is the minimum time between consecutive scans to the node Once the system is running the actual polled scan time can be displayed through the fault table facility in real time Specify the node s Maximum Polled Response Time This is the maximum time that the DNT450 will wait for a polled response from the node If this timer expires the node is taken off line Then at the next opportunity the DNT450 will attempt to reconnect to the node Specify the node s Maximum Explicit Response Time This is the maximum time that the DNT450 will wait for an explicit response from the node If this timer expires the node is taken off line Then at the next opportunity the DNT450 will attempt to reconnect to the node SUP0462 01 19 APR 2002 PAGE 17 CH 3 Specify the node s Input Data Assembly This item specifies the input data assembly for data received from the node See section 3 6 for more details Specify the node s Output Data Assembly This item specifies the output data assembly for data being sent to the node See section 3 6 for more details Specify the node s Polled Delay Time Some o
8. locate the transmit buffer at R101 the receive buffer at R51 we will also allocate 20 bytes to the receive buffer BYTE REGISTER TRANSMIT O0 Ri01LSB_ MACID Node Address Im 1 Ri01MSB Service Code Set Attribute Single 16 3 Ri02MSB 00 i A R103LSB Instance ID Polled Connection 5 gt Ri03MSB 00 i 6 R104LSB Attribute Expected Packet Rate 07 8 Ri05LSB_ DataValueHighByte Io AQ2 Number of Bytes to Transmit 9 5 3 How to Interpret Explicit Response Messages The normal expected response from an Explicit Message is the Acknowledge Message BYTE EXAMPLE Rien Joana Pr 0 Numberof optional Data n ptional Data Previously sent Service Code 0x10 0x80 Xx Xx Opti Xx Opti Xx Note The Most Significant Bit in the Service Code byte is used as a Response Bit indicating that the command was properly received Service Code 0x10 Response Bit 0x80 0x90 If any extra data needs to be returned that data will be placed into subsequent bytes Note The number of bytes received value is the number of bytes of the message placed in the receive buffer including the two bytes devoted to the number of bytes received SUP0462 01 19 APR 2002 PAGE 27 CH 5 5 4 Explicit Message Errors In the case that an Explicit Message requests a function that cannot be performed by the referenced node an Explicit Error Message will be returned An Explicit Error Message takes the followin
9. to the Configure l O dialog box with the selected slot showing that the DeviceNet Master module has been added It is vital that the module and slot match that of the OCS Mismatched configurations cause an IO Module Mismatch Error during the power on diagnostics of the OCS If the OCS that is to be configured is available and connected to one of the COM ports the Auto Config button can be used Using this option will cause Cscape to read the OCS and display the modules that are connected to the OCS Note When using Auto Config the user needs to make sure that the SmartStack modules to be used e g DNT450 are connected to the OCS prior to using Auto Config 6 2 2 Configure the Module First double click on the DeviceNet module in the I O configuration screen Figure 5 4 or click on the config button next to the DeviceNet module The following screen will appear VO Man bl chr Su Bieri fe bidet HEIKE A9 Diea igi Dron him rd Tra Gang Tri Hope ot Fieguia Megas Pers H FE re TS SO GE FRE TE k Pen foe To San Mo FEE Po Le Cancel fen Figure 6 4 Module Configuration SUP0462 01 19 APR 2002 PAGE 31 CH 6 Now click on the Module Setup tab Select the Configure button The DeviceNet network configuration utility will then open up The first dialog that will appear is the Network Properties dialog This dialog allows the user to set the starting Reference Addresses of the registers and Baud Rate of
10. EJ HORNER APG User Manual for the HE800DNT450 DeviceNet Master Scanner First Edition 19 April 2002 SUP0462 01 SUP0462 01 19 APR 2002 PAGE 3 PREFACE This manual explains how to use the Horner APG s DeviceNet Master Scanner Copyright C 2002 Horner APG LLC 640 North Sherman Drive Indianapolis Indiana 46201 All rights reserved No part of this publication may be reproduced transmitted transcribed stored in a retrieval system or translated into any language or computer language in any form by any means electronic mechanical magnetic optical chemical manual or otherwise without the prior agreement and written permission of Horner APG LLC All software described in this document or media is also copyrighted material subject to the terms and conditions of the Horner Software License Agreement Information in this document is subject to change without notice and does not represent a commitment on the part of Horner APG LLC DeviceNet is a trademark of Open DeviceNet Vendors Association ODVA Windows and Windows 95 are trademarks of Microsoft Corporation SmartStack Cscape and CsCAN are trademarks of Horner APG LLC For user manual updates contact Horner APG Technical Support Division at 317 916 4274 or visit our website at www heapg com PAGE 4 19 APR 2002 SUP0462 01 LIMITED WARRANTY AND LIMITATION OF LIABILITY Horner APG LLC HE warrants to the original purchaser that the DeviceNe
11. Explicit Messages non n cnn nn nc nn nn n nn cnn nan cannnnns 25 5 3 How to Interpret Explicit Response Messages 26 5 4 Explicit Message Errors ocooonncccccccnnncccnonononnccnnnncnnnnnnnnncnnnnnnn nan nn nn nan nn nn nnnnn rn nn nn narnia 27 CHAPTER 6 CONFIGURATION nan n rca nn nnnn nan nannn rra ninnnnnininns 29 JANE an nord 29 6 2 G nfiguration marine 29 6 2 1 Select the Module to be Configured nn 29 6 2 2 Configure the Module 30 6 2 3 Creating the network CONfigUratiON oooonnnnnnnnnnnnnnccnnnnccnnnnnronccnnnnconnnnn nan cnnnncnnnnnns 32 CHAPTER 7 DEVELOPING USER GOETWARE nn 35 7 1 Software Support for the Polled Connecti0N ooonnnninnnccnnnnninnnnconcncnnnncnnannarnncnnnncnnanns 35 APPENDIX A DNT450 NETWORK OPERATION cooooccoccccocconccnononnconconnnnoncnnnnnnnnonnnnnaninnnnnncnns 37 NS SS 37 A 2 Establishing a Connechon nn cnn nn nro naar nn nn cnn nn rr nnnn rn narco 37 A 3 Send a Polled Message nn nn n cnn nan n nn nrn nn nr rana nr rn n cnn 37 AE EPICA NOS a te eee 37 APPENDIX B DEVICENET TIMING ocn nnnnn cnn nan n nn n naar nrinnrnnannns 39 B 1 Message Packet Timing 39 B 2 Network Scan Time versus PLC Scan Time 39 APPENDIX C DEVICENET ERROR CODE 41 PAGE 6 19 APR 2002 SUP0462 01 SUP0462 01 19 APR 2002 PAGE 7 CH 1 CHAPTER 1 INTRODUCTION 1 1 Overview The DeviceNet Scanner HE800DNT450 is an intelligent communications interface module The DNT450 allows an Operator Control Station OCS to sup
12. NDEX
13. ackets Message Size 7 Size of additional packet remainder of message size 7 1 Time for full packets Time for 8 bytes taken from table Time for additional packet Taken from table Time for full message Total for all Full Packets Time for Additional Packet B 2 Network Scan Time versus PLC Scan Time The user should not make any assumptions about the relationship between the PLC scan time and the DeviceNet Polled scan time They are totally asynchronous to each other Any relationship between the PLC scan time and the DeviceNet Polled scan time can be determined only with a strong knowledge of the program running in the PLC the DeviceNet configuration or by conducting extensive testing PAGE 40 19 APR 2002 SUP0462 01 APPENDIX B NOTES SUP0462 01 19 APR 2002 PAGE 41 APPENDIX C APPENDIX C DEVICENET ERROR CODES The following DeviceNet General Error Codes are defined within the DeviceNet specification and are supported by all DeviceNet nodes Table C 1 General Error Codes Error Code Description of error in hex 00 01 Reserved Ir Resource needed for the object to perform the Unavailable requested service were not available 03 07 Reseved The requested service was not implemented or not Supported defined for this Object Class Instance Invalid Attribute Invalid attribute data detected Value Reserved The object is already in the requested mode or state requested mode requested by t
14. attempt to establish an explicit connection using the Group 2 Only protocol If unsuccessful return 2 Attempt to establish a Polled connection If unsuccessful release the Explicit connection and return 3 Request the node s Polled Production size If unsuccessful release the Explicit and Polled connections and return 4 Compare the nodes Polled Production size to the configuration file If different release the Explicit and Polled connections and return 5 Request the node s Polled Consumption size If unsuccessful release the Explicit and Polled connections and return 6 Compare the nodes Polled Consumption size to the configuration file If different release the Explicit and Polled connections and return 7 Set the nodes Polled Expected Packet Rate If unsuccessful release the Explicit and Polled connections and return 8 Set On Line status for the node and return A 3 Send a Polled Message Read the appropriate Q and AQ data from the PLC Build a Polled Command message sequence Sent the message s over the network to the node When the Polled response from the node is received send the response data to the appropriate PLC l and Al registers and return PON gt A 4 Explicit NOPs Every few seconds the DNT450 will send an Explicit message containing a NOP to each on line node The purpose of this is to keep the nodes Explicit connection from timing out See ODVA DeviceNet Specifications Volume Chap
15. e OCS can be configured before the modules are installed or even if the OCS is not available This is a great convenience when programming must start before the hardware has been received 6 2 1 Select the Module to be Configured First invoke Cscape From the Cscape Main Menu select Controller I O Configure CPU Slot A Ensure the al correct controller is HE5000C5100 CsCAN O s Contig selected To change controllers press d Empty EMPTY See Conti CPU Slots and select the desired module B You can add an I O module to any slot but Slot 1 must not be empty comal Figure 6 1 Select the Module Slot Next double click on the empty slot in which the DNT450 module will reside or click on the Config button to the right of the slot position This invokes the Add I O Module screen Click on the Comm tab Add 1 0 Module E Mixed Digital Digitalln DigitalOut Mixed nalog Analogin Analog Out Comm Other HES0085C100 ASCII Basic Coprocessor HES00DNT450 DeviceNet Master HESODETN100 Ethernet Module HES00ETN116 Ethernet Module with 16MB flash HES80QJCM200 J1939 CAN Figure 6 2 Select the Comm tab From that dialog select the DNT450 module and click OK PAGE 30 19 APR 2002 SUP0462 01 CH 6 isi mw Eb oes EA m 7 Gmin DR d mar AS ers A tados See Hate pool am Eris EDA Figure 6 3 DNT450 Module is Added The screen returns
16. ed in the Scan List are considered to exist on the network The DNT450 needs additional information about each of the nodes in the Scan List For each node included in the Scan List Specify the node s first l register number This entry specifies the first register in the block of PLC l registers that are assigned to this node Note that this block must be part of the larger block of l registers assigned to the DNT450 above Specify the node s first Q register number This entry specifies the first register in the block of PLC Q registers that are assigned to this node Note that this block must be part of the larger block of Q registers assigned to the DNT450 above Specify the node s first AI register number This entry specifies the first register in the block of PLC AI registers that are assigned to this node Note that this block must be part of the larger block of Al registers assigned to the DNT450 above Specify the node s first AQ register number This entry specifies the first register in the block of PLC AQ registers that are assigned to this node Note that this block must be part of the larger block of AQ registers assigned to the DNT450 above Specify the node s Polled Expected Packet Rate This entry specifies the Expected Packet Rate that will be loaded into the node when a dialogue is established with the node The node uses this number multiplied by four as an inactivity timer limit value The node resets the
17. ervise a DeviceNet network Up to 63 slave devices can be connected via DeviceNet to the DNT450 Depending on baud rate and the cable type used the DeviceNet slave nodes can be located up to 1 500 feet 457 2 meters from the PLC DNT450 Polled data is mapped directly into the PLC s l Q Al and AQ registers The ladder programmer can treat the DNT450 and its attached DeviceNet nodes as a large I O module Polled data is transferred between the PLCs registers and the DeviceNet slave nodes without any user or ladder code intervention The DeviceNet specification provides two methods of establishing communications between a scanner and its nodes The first method makes use of the Unconnected Message Manager UCMM and the second is known as Group 2 Only Group 2 Only is the simplest Because of its simplicity many slave devices only support the Group 2 Only method The DNT450 allows both of these methods to be used simultaneously Any single DeviceNet slave device can be either a Group 2 Only node or a UCMM node never both A DeviceNet network can be made up of a mixture of Group 2 Only and UCMM slave devices 1 2 DNT450 Features The DNT450 supports the following DeviceNet features Baud Rates 125K 250K and 500K UCMM protocol Log on Group 2 Only protocol The Polled Connection Ladder Initiated Explicit Messaging LIEM Fragmentation on both polled and explicit connections All four Message Bod
18. g form Byte Example Word Value Number Description values in Offset from HEX example 0 Number of bytes 06 1 received 00 R1 0006 2 MACID 01 S 3 Service Code 94 R2 0x9401 4 General Error Code XX S 5 Additional Error Code xx R3 XXXX An Error is indicated by a 0x94 in the service code byte This indicates that the referenced node has detected an error and the two bytes following indicate the specifics to that error The next byte indicates the General Error Code The last byte contains an Additional Error Code to indicate additional information See appendix C for a list of and definitions of General and Additional Error Codes Many DeviceNet manufactures have defined vendor specific error codes In this case the General error code will be in the range of 0xDO to OxFF Vendor specific Object and Class errors In these cases the Additional error code can be anything Consult the documentation from the node manufacture for more details PAGE 28 19 APR 2002 SUP0462 01 CH 5 NOTES SUP0462 01 19 APR 2002 PAGE 29 CH 6 CHAPTER 6 CONFIGURATION 6 1 General Chapter Six describes the steps necessary to configure the DNT450 module and the OCS it is attached to The procedures for using Cscape software are also described 6 2 Configuration Configuration is usually completed after the modules are installed With Cscape however OCS configuration is contained with the source code CSP files Th
19. gence or otherwise shall HE or its suppliers be liable of any special consequential incidental or penal damages including but not limited to loss of profit or revenues loss of use of the products or any associated equipment damage to associated equipment cost of capital cost of substitute products facilities services or replacement power down time costs or claims of original purchaser s customers for such damages To obtain warranty service return the product to your distributor with a description of the problem proof of purchase post paid insured and in a suitable package ABOUT PROGRAMMING EXAMPLES Any example programs and program segments in this manual or provided on accompanying diskettes are included solely for illustrative purposes Due to the many variables and requirements associated with any particular installation Horner APG cannot assume responsibility or liability for actual use based on the examples and diagrams It is the sole responsibility of the system designer utilizing the DeviceNet Master Scanner to appropriately design the end system to appropriately integrate the DeviceNet Master Scanner and to make safety provisions for the end equipment as is usual and customary in industrial applications as defined in any codes or standards which apply It assumed that the system designer is familiar with PLC programming and configuration Note The programming examples shown in this manual are for illustrative purpo
20. gisters The specific registers used are a function of the configuration of the DNT450 and of the PLC Configuration Data is passed via the DeviceNet Polled Connection automatically Data is read from or written to the network devices according to the registers programmed No extra ladder programming is required to send or receive data using Polled Messages PAGE 36 19 APR 2002 SUP0462 01 CH 7 NOTES SUP0462 01 19 APR 2002 PAGE 37 APPENDIX A APPENDIX A DNT450 NETWORK OPERATION A 1 Sequence of Events The DNT450 follows a predetermined sequence of events as it attempts to communicate with all of the nodes connected to the network In an effort to maximize the available DeviceNet bandwidth the DNT450 may have message transactions in process with several different nodes at the same time Defined below is a very generalized sequence of events 1 The DNT450 steps through each node included in its scan list repeatedly 2 As each node is examined several checks are made on the status of the node These include A Is the node on line If not go to Establishing a Connection below B Is a message transaction currently in progress with the node If not go to Sending a Polled Message below A 2 Establishing a Connection There are several steps involved in the establishment of connections with DeviceNet nodes The general steps involved include 1 Attempt to establish an Explicit connection using the UCMM protocol If unsuccessful
21. he service The object can not perform the requested service in Conflict it s current mode or state Reserved E eee Attribute Not A request to modify a non modifiable attribute was Settable received Permission privilege check failed Conflict requested service The data to be transmitted is large than the allocated Large response buffer Reseved Pe The service did not supply enough data to perform the requested service Supported Too Much Data The serve supplied more data than was expected Object Does not The specified object does not exist in the device Exist Reseved The attribute data of the object was not stored prior to data the requested service failure object 1A 1E ReseredbyDeviceNet error Additional Byte for further information A parameter associated with the service was determined to be not valid 21 CF_ Reseved J 2 EE DO FF Object Class and Vendor specific Object and Class errors Service Errors PAGE 42 19 APR 2002 SUP0462 01 APPENDIX C Table C 2 Additional Error Codes Error Description of error Code in hex 01 Predefined Master Slave Connection Set allocation conflict This is returned when an Allocate_Master Slave_Connection_Set request is received and the Slave has already allocated the Predefined Master Slave Connection Set to another Master Invalid Allocation Release Choice parameter This is returned when an Allocate Release_Master Slave_Connection_Set request is received a
22. ice Green The module is operating normally Operational Device in Standb Flashing Green The module has no configuration Minor Fault Flashing Red Recoverable Fault ee The module has an unrecoverable fault Fault Device Self Flashing The module is in Self Test Testing Red Green Table 2 4 Network Status LED NSA For this state Network Status LED is Condition Off Not powered or The module may not be powered Not On line Module is not on line Module has not completed Dup_MAC_ID test Module On line and Green The module is on line and has all Connected connections in the established state Network OK Module On line DC Module has passed the Dup_MAC_ID test but Flashing Green and is on line but has not established a Not connected connection with one or more nodes One or more Connections have Timed Out E Failed communication device Device Self Test Device is in self test Red Green Device in Standb Flashing Red The module has no configuration PAGE 12 19 APR 2002 SUP0462 01 CH 2 NOTES SUP0462 01 19 APR 2002 PAGE 13 CH 3 CHAPTER 3 DEVICENET NODE DNT450 amp PLC RELATIONSHIPS 3 1 General Unless otherwise noted all numeric radixes are in decimal In a few cases the notation Oxhh is used to indicate Hexadecimal radix 3 2 Module to PLC Register Mapping The DNT450 requires the use of four blocks of PLC registers One block is defined in each of the PLCs l Al Q and AQ register space Through the u
23. isual representation of the network can be constructed within the network view screen SUP0462 01 19 APR 2002 PAGE 33 CH 6 To add a node either right click in the right window pane and select Add New Node or select the Net Edit Add New Node menu item Once a new node is visually added to the display it can now be configured in the following manner Double click on the new node and the following screen appears General Connection Details Node MAC ID Ref Addr 17 ZA RefAdd Is l Reg Size fo Y bits ZAl Reg Size o words Production Size fo y bytes Input Data Assembly 1 v Param Type None Y Type Count fo 3 Poll Scan Time fio ms Poll Delay o Expt Pkt Rate 1000 ms Parameter Node Name Nodet Spe ddi P Sat Read 5 3 0 Reg Size pp Sj bits ZAQ Reg Size jp 4 words Consumption Size fo y bytes Output Data Assembly Parameter 1 b Param Type None Y Type Count 0 Timeouts Expl Response 1000 a ms Poll Response 1000 j ms e Figure 6 7 Node connection details This window displays everything about the connection details of that node Production sizes consumption sizes l Al Q and AQ sizes and references Enter the node MAC ID The software program sets the starting reference addresses automatically but the user can change them if need be Fill inthe data assemblies There are four parameters in each assembl
24. lder slave nodes can not accept fragmented polled data packets sent at full soeed especially if the baud rate is 500KB This entry instructs the DNT450 to insert a delay between polled fragmented packets addressed to this node For most nodes this entry should be set to zero If required try a value of 100 or 200 3 8 DeviceNet Node Priority and Implications The DNT450 can carry on conversations with several DeviceNet nodes simultaneously Because of this DeviceNet Node Priorities become important Within the scheme of CAN communications there is a concept known as Arbitration If two slaves begin to transmit CAN messages simultaneously the slave with the smallest node address will win The loser must immediately stop transmitting and try again later This gives obvious priority to the slave with the lower node address This can create problems if care is not taken in the assignment of node addresses Consideration should be given to the priorities of the individual nodes In the design of most networks there are usually a few nodes that require a higher priority than the rest These nodes should be assigned the lower node addresses 3 9 Fault Table The DNT450 provides a fault table that makes available the status of each node on the network PLC registers Q3 Q4 Q5 AI5 and AI6 With respect to the base addresses set within the configuration are used to provide a user interface into the fault table The table has an entry for each
25. lies are published by the manufacturer of the DeviceNet node To properly map the DeviceNet data to or from the PLC the data assemblies for each DeviceNet node must be available and understood Consult data sheets from the DeviceNet node manufacturer for specific details on Data Assemblies From the point of view of the PLC all input is via l and Al registers and all output data is via Q and AQ registers From the point of view of the DeviceNet nodes all I O is via streams of data bytes known as Data Assemblies that they send and receive In most DeviceNet nodes the data assembly formats are fixed in others they are configurable Consult data sheets from the DeviceNet node manufacturer for details on Data Assemblies The DNT450 accepts output data from the PLC in the form of Q and or AQ registers It then translates this data into DeviceNet polled messages and sends them to the node The DNT450 receives DeviceNet polled response messages from the addressed DeviceNet node translates these DeviceNet messages and passes the data on to the PLC where they are stored in the appropriate l and or Al registers The DNT450 allows up to 4 blocks of data to be concatenated to form a data assembly Each block can be configured as either bit data or word data The number of bits or words within each block is also configurable Keep in mind that bits must be assigned in groups of 8 bits The user can configure for example that the first block will c
26. ly Specify the node s Output Data Assembly Specify the node s Polled Delay Time Each of these items are briefly discussed below Add the DNT450 to the OCS SmartStack I O Refer to Chapter Six for configuration details Specify the DNT450 s MACID This is the network address that the DNT450 will respond to All nodes on the network including the DNT450 must be configured with a unique MACID Specify the network baud rate This is the data bit rate at which all nodes on the network will operate All nodes on the network must be configured to operate with the same baud rate Specify the module s first l register number This entry specifies the first register in the block of PLC l registers that is assigned to the DNT450 module Specify the module s first Q register number This entry specifies the first register in the block of PLC Q registers that is assigned to the DNT450 module Specify the modules first Al register number This entry specifies the first register in the block of PLC AI registers that is assigned to the DNT450 module Specify the module s first AQ register number This entry specifies the first register in the block of PLC AQ registers that is assigned to the DNT450 module PAGE 16 19 APR 2002 SUP0462 01 CH 3 Scan List Before the DNT450 can communicate with any DeviceNet nodes it must be configured with a Scan List The Scan List specifies which DeviceNet nodes to query Only those nodes specifi
27. nd 1 The Slave does not support the choice specified in the Choice parameter 2 The Slave was asked to Allocate Release connection s already allocated released The Allocation Choice Release byte contained all zeros an invalid combination of bits or did not contain the Explicit Message Allocation Choice when required A Group 2 Only Server UCMM incapable received a message on the Group 2 Only Unconnected Explicit Request message port that was not an Allocate or Release message Resource required for use with the Predefined Master Slave Connection Set is not available 02 03 4 SUP0462 01 INDEX INDEX Configuration 29 Introduction 15 Configuration Network 32 Connectors DeviceNet I O CAN A 10 Data Assemblies 14 DeviceNet Error Codes 41 Message Packet Timing 39 Node Priority and Implications 17 Explicit Messages Building Explicit Messages 25 Errors 27 Interpreting Explicit Response 26 Explicit NOPs 37 Fault Table 17 Features 7 Fragmentation 13 LED Indicators 11 19 APR 2002 PAGE 43 Mapping Module to PLC 13 Node to PLC 13 Message Packets 13 Network Operation Establishing Connection 37 Sequence of Events 37 Network Timing Network Scan vs PLC Scan 39 Physical Limitations 13 Polled Messages sending 37 Register Requirements 21 SmartStack Installing and Removing 9 Software Polled Connection 35 Specifications 8 Timing DeviceNet 39 PAGE 44 19 APR 2002 SUP0462 01 I
28. ns Explicit Messaging requires a great deal of overhead in both the DNT450 and the OCS Multiple PLC scans may be required to access the required data between the OCS and the DNT450 As a result Explicit Messages should be reserved for access to infrequently needed data such as configuration or tuning parameters only The sequence below presents a general description of the process that must be executed to service an Explicit request 1 The ladder code builds an explicit request message in a group of R registers 2 The ladder code plugs the start of and length of the transmit and receive buffers into four AQ registers The transmit and receive buffers must both be located in the R register space of the OCS The ladder code then sets the Send Explicit Message command bit The DNT450 periodically checks the Send Explicit Message command bit If the Send Explicit Message command bit is set processing of the explicit request begins This command bit must remain on until success or error status is returned The four AQ registers are examined and checked for validity The DNT450 requests the PLC to send the transmit buffer The DNT450 then checks the MACID contained in the transmit buffer Several checks take place MACID out of range referenced node not configured and referenced node not On line 9 Then the message is formatted and sent to the referenced node 10 When the response message is received a check i
29. o the third Al register Status bits for nodes 48 through 63 are mapped into the fourth Al register The status bit for node 0 is placed in the least significant bit position of the first Al register with consecutively higher addressed nodes status bits being placed in the next higher bit positions Each individual status bit is set TRUE if the corresponding DeviceNet node is On Line On Line is defined as the node s Polled connection being in the Established state and the node is communicating Polled data AI5 LSB Fault Table Byte 1 Node Address This byte contains the node address of the fault data displayed in the next 3 bytes SUP0462 01 19 APR 2002 PAGE 23 CH 4 AI5 MSB Fault Table Byte 2 Fault Code This byte indicates the type of fault that exists for the node indicated by the addressed node The fault code can have the following values 0 None Polled Scan Time 2 Timeout waiting for an Explicit Fragmented Acknowledge Response Message 3 Timeout waiting for an Allocate Explicit Connection Response Message 4 Timeout waiting for an Allocate Polled connection Response Message 5 Timeout waiting for a Get Polled Consumption Size Response Message 6 Timeout waiting for a Get Polled Production Size Response Message 7 Timeout waiting for a NOP Response Message 8 Timeout waiting for a Polled Response Message 9 Timeout waiting for a Set Polled Expected Packet Rate Response Message 10 Timeout waiting for any other
30. oduction Size Response Message 7 Timeout waiting for a NOP Response Message 8 Timeout waiting for a Polled Response Message 9 Timeout waiting for a Set Polled Expected Packet Rate Response Message 10 Timeout waiting for any other Explicit Response Message 11 Unable to Establish an Explicit Connection 12 Unable to Establish a Polled Connection 13 Polled Consumption Size Error 14 Polled Production Size Error There are priorities involved with the fault code values Priorities are assigned based on the numeric value of the individual fault codes A higher number has a higher priority If a code of 5 Timeout waiting for a Get Polled Consumption Size Response Message is being displayed a lower priority code such as 2 Timeout waiting for an Explicit Fragmented Acknowledge Response Message will not displace the higher priority code However a lower priority fault code will be displaced by a higher priority code occurring Fault code type 1 Polled Scan Time is really not a fault at all Instead if there is nothing else that needs to be displayed The Polled scan time is displayed This is the time from one Polled Command Message to the next NOT the node s response time to a Polled Command Message When looking at these polled scan times keep in mind that the DNT450 will overlap Polled Command Messages In other words while waiting for a Polled Response Message from one node a Polled Command Message will be sent to another node
31. ontain 32 bits the second block might contain 7 words the third block might contain 8 bits and the forth block might contain 5 words This would result in a data assembly that contains 32 bits followed by 7 words followed by 8 bits followed by 5 words This example results in a data assembly that contains 29 bytes The user must define a data assembly for both the input and output data for each node on the network SUP0462 01 19 APR 2002 PAGE 15 CH 3 3 7 DNT450 Configuration Introduction Configuration of the DNT450 is performed using a PC running Cscape Software There are a number of steps required in order to properly configure the DNT450 DeviceNet scanner module These steps include Add the DNT450 to the OCS SmartStack I O Configuration Specify the DNT450 s MACID Specify the network baud rate Specify the module s first l register number Specify the module s first Q register number Specify the module s first Al register number Specify the module s first AQ register number For each configured node Specify the node s first l register number Specify the node s first Q register number Specify the node s first AI register number Specify the node s first AQ register number Specify the node s Polled Expected Packet Rate Specify the node s Minimum Polled Scan Time Specify the node s Maximum Polled Response Time Specify the node s Maximum Explicit Response Time Specify the node s Input Data Assemb
32. ore packets or fragments This is called fragmentation The DNT450 handles this automatically without any intervention by the user or the ladder program running in the PLC Fragmentation works differently for Polled messages than Explicit messages In the case of Polled messages each message fragment is sent to the receiving party one after the other as fast as possible In the case of large Explicit messages the sender will send only the first packet The sender then waits for an ACK message from the receiver Upon receiving the ACK the sender then transmits the next packet and waits for another ACK This process repeats until all message fragments have been sent This ACK process requires a considerable amount of time when compared to Polled messages 3 5 Physical Limitations There are physical limits on the amount of data that can be transferred between the DNT450 and the PLC This limit is 300 bytes of l and Al data and 300 bytes of Q and AQ data The smallest data item that DeviceNet can handle is one byte If an application requires only a single Q output or command bit a group of 8 Qs must be allocated The remaining 7 will be unused or wasted The same is true for bit type input data PAGE 14 19 APR 2002 SUP0462 01 CH 3 3 6 Data Assemblies For a Polled Connection the data bytes within the DeviceNet messages must be sent and received in a predetermined order This order is specified by Data Assemblies Data Assemb
33. s made to see if the allocated receive buffer is large enough to accept the response message 11 The message is then sent to the block of R registers designated as the receive buffer 12 The Explicit Transaction Complete bit is then set 13 If there were any errors detected in any of the previous steps the process is aborted and the appropriate error status bit along with the Explicit Transaction Complete bit are set NAO DAD See Chapter 4 for descriptions of all of the command status and error bits 5 2 Building Explicit Messages In the following example let s assume that we want to read the polled consumption size from the node at MACID 3 we also want to locate the transmit buffer at R101 the receive buffer at R51 and we will also allocate 20 bytes to the receive buffer BYTE REGISTER TRANSMIT NUMBER NUMBER DESCRIPTION BUFFER DATA 0 R101LSB_ MACID Node Address 1 R101 MSB Service Code Get Attribute Single 2 R102LSB_ Class ID Connection Class 3 Ri02MSB 00 i A R103LSB Instance ID Polled Connection 5 RI03MSB 00 i 6 Ri03LSB_ Attribute Consumption Size 07 PAGE 26 19 APR 2002 SUP0462 01 CH 5 REGISTER DESCRIPTION VALUE AQ1 Start of Transmit Buffer AQ2 Number of Bytes to Transmit AQ3 Start of Receive Buffer AQ4 Receive Buffer Allocation Size In the following example we want to write the polled expected packet rate to the node at MACID 3 we also want to
34. se of the Cscape the user can specify the starting register and the size of each of these four register blocks Data from the PLC to the DNT450 and to the DeviceNet nodes are passed in the Q and AQ registers Data to the PLC are passed by the DNT450 in the PLCs l and AI registers With respect to the examples in this manual the PLC register references are set to one This simplifies our examples by assuming that all of the register reference assignments start at one That is the first l Q Al and AQ registers are assigned to PLC register l1 Q1 AI1 and AQ1 Although these register assignments can be placed anywhere within the PLC register space we have made these assignments for simplicities sake 3 3 Node to PLC Register Mapping Additionally the DNT450 subdivides these register blocks providing individual sub blocks to each DeviceNet node This provides mapping between the PLC s data registers and the data to and from each individual DeviceNet node As a result each node s polled data is immediately available to the PLC ladder code by accessing the appropriate PLC register s Note that the node to PLC register assignments must be contained within the Module register definitions defined in Module to PLC Register Mapping discussed above 3 4 Message Packets and Fragmentation A DeviceNet message packet can contain from 0 to 8 bytes of data If more than 8 bytes of data are required the message must be broken up into two or m
35. ses only Proper machine operation is the sole responsibility of the system integrator SUP0462 01 19 APR 2002 PAGE 5 TABLE OF CONTENTS EEGEN 3 LIMITED WARRANTY AND LIMITATION OF LUABILITN 4 ABOUT PROGRAMMING ESXAMDLES nnne n 4 TABLE OF CONTENTS iii ae eee ne 5 CHAPTER 1 INTRODUC FION onn E A T 7 Va E e Uer H Lei DNT450 Fealures ann 7 1 3 Technical Specifications A 8 GCGHAPTER 2 INSTALLATION une aeg 9 2 1 Installing and Removing a SmartStack Module Shown with the OCS 9 2 2 CONNECIONS er ee iin 10 2 2 1 DeviceNet I O Connector CAN A 10 2 3 LED OCA A ek ee 11 CHAPTER 3 DEVICENET NODE DNT450 amp PLC RELATIONSHIPS nen 13 O E e E 13 3 2 Module to PLC Register Mappimg non ncnnnn cn rancio nn ncnnnnos 13 3 3 Node to PLC Register Mappimg nn nn cn nan crnnnnnn rra cnn 13 3 4 Message Packets and Fragmentation oooonnnncnncccnnnncinnnononnccnnnncnnnnnnn cnn cnn nn cnn nnnn nn nn cnn 13 3 5 Physical SA 13 3 6 Data Aesemblies nerian a n a a n a a an ana tara tenane are tar i 14 3 7 DNT450 Configuration Introduchon nn 15 3 8 DeviceNet Node Priority and Implications ooooccnnnnnnnnnncncccnnnnnonnnccconnccnnn cnn nnnrrrnn cnn 17 3 9 Fault Tabla Ba I EI 17 CHAPTER 4 DNT450 REGISTER REQUIREMENTS coocoococccccononccnnonnncnncnnnncnnnonnnnnnninnnnnnnnnns 21 CHAPTER 5 EXPLICIT MESSAGING USING DNT450 oooccocccccccccococccccnonccnnnnnnnncccnnnnnnnnncnnnnnos 25 en e EE 25 5 2 Building
36. t Master Scanner manufactured by HE is free from defects in material and workmanship under normal use and service The obligation of HE under this warranty shall be limited to the repair or exchange of any part or parts which may prove defective under normal use and service within two 2 years from the date of manufacture or eighteen 18 months from the date of installation by the original purchaser whichever occurs first such defect to be disclosed to the satisfaction of HE after examination by HE of the allegedly defective part or parts THIS WARRANTY IS EXPRESSLY IN LIEU OF ALL OTHER WARRANTIES EXPRESSED OR IMPLIED INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR USE AND OF ALL OTHER OBLIGATIONS OR LIABILITIES AND HE NEITHER ASSUMES NOR AUTHORIZES ANY OTHER PERSON TO ASSUME FOR HE ANY OTHER LIABILITY IN CONNECTION WITH THE SALE OF THIS DEVICENET MASTER SCANNER THIS WARRANTY SHALL NOT APPLY TO THIS DEVICENET MASTER SCANNER OR ANY PART THEREOF WHICH HAS BEEN SUBJECT TO ACCIDENT NEGLIGENCE ALTERATION ABUSE OR MISUSE HE MAKES NO WARRANTY WHATSOEVER IN RESPECT TO ACCESSORIES OR PARTS NOT SUPPLIED BY HE THE TERM ORIGINAL PURCHASER AS USED IN THIS WARRANTY SHALL BE DEEMED TO MEAN THAT PERSON FOR WHOM THE DEVICENET MASTER SCANNER IS ORIGINALLY INSTALLED THIS WARRANTY SHALL APPLY ONLY WITHIN THE BOUNDARIES OF THE CONTINENTAL UNITED STATES In no event whether as a result of breach of contract warranty tort including negli
37. ters 9 and 10 and Appendices A through F for a complete listing of DeviceNet requirements and specification PAGE 38 19 APR 2002 SUP0462 01 APPENDIX A NOTES SUP0462 01 19 APR 2002 PAGE 39 APPENDIX B APPENDIX B DEVICENET TIMING B 1 Message Packet Timing It is not easy to determine the exact transmission time of the DeviceNet Polled scan time The table below provides actual timing of single message packets for various baud rates and message sizes It must be understood that the table does not take into account the dead time between the message packets There are a number of reasons for this dead time but be assured that it does exist The best way to get an accurate handle on the DeviceNet Polled scan time is to connect a good digital oscilloscope or a DeviceNet protocol analyzer to the DeviceNet cable and observe the system s operation The amount of data to be transmitted determines the packet size and number of packets necessary The baud rate determines the amount of time necessary to transmit one packet ar LE LE LA LA LA LA LA Message sesch Klek ee message packet Eel abl lle ed lee a 125K 250K 500K Given a message of X bytes it is first necessary to determine if fragmentation is involved and if so how many packets will be sent If the size of the message X is eight 8 bytes or less use the time given in Table 8 If the size X is more than eight bytes fragmentation is required Number of Full P
38. the network The l size Al size Q size AQ size l Ref Addr Al Ref Addr Q Ref Addr and AQ Ref Addr values are values with respect to the OCS that the DNT450 is running on Select the Baud Rate drop down box to configure the baud rate for the DNT450 Once done configuring this screen then click OK Hals rk Praprertana carrer lues CPU mei r i H A wm Fc F mith Te gt Mies in iia ini hi yt KKH fia ai Su Sim J weil Wij Pia Aa fi io Eine E vera 40 Sos biz 20 Parada ft e bk S y 580 Som sect wida See h Tial mra be Se K i D 1 cde copa badea A Salt i Cece H Figure 6 5 Network properties screen The network view of the configuration utility will appear The right pane is the Network View where the user can build a visual representation of a network depicting the DNT450 Master and all slave nodes devices The nodes are configured in this view A E Edo lie Edi Ven Wet Dep pikis do ala 08 99 day y Ebo Hd 8 Fiz ep presa Fl Tan Sica ie ig Se H hd be fi Figure 6 6 Network View screen PAGE 32 19 APR 2002 SUP0462 01 CH 6 6 2 3 Creating the network configuration The DeviceNet network can now be constructed within the network view display Before constructing a network with this utility it is recommended that one should use the following method to create the network 1 Decide what baud rate the network will run at This is needed for the DNT450 module config
39. ther fault codes not used Because it is possible that higher priority faults can be generated during system power up sequences the following sequence should be followed to access the fault table 1 Allow the system to run for a few seconds 2 Clear the fault table 3 Wait a few more seconds 4 And finally access the fault table This causes the fault table to be refreshed with current data Any preexisting high priority entries are eliminated in favor of the current lower priority data PAGE 20 19 APR 2002 SUP0462 01 CH 3 NOTES SUP0462 01 19 APR 2002 CHAPTER 4 DNT450 REGISTER REQUIREMENTS PAGE 21 CH 4 The DNT450 requires a number of PLC registers to be assigned to itself The following tables define the DNT450 register requirements and definitions of these data assemblies These registers are with respect to the base addresses assigned within the configuration DNT450 REGISTER REQUIREMENTS Number of Q s EA Number of AQ s Number of P s L 6 Number of Al s Q1 Q2 Q3 Q4 Display the next node with a fault Q6 8 ASS AQI Transmit Buffer First R Number AQ2 Transmit Buffer Size In bytes Receive Buffer First R Number AQ4 Receive Buffer Size In bytes LAA ee ER l2 l3 14 Explicit Error Buffer Allocation Error 15 Explicit Error Can t get R buffer from OCS 16 l7 EE l9 l10 l11 112 Explicit Error Can t put R buffer to OCS 113 16 SAN
40. tions are subject to change without notice General Specifications Required Power e Operating a 5 l Steady State To be Determined Temperature 0 to 60 Celsius Required Power Inrush To be Determined Terminal Type Spring Clamp Removable Relative Humidity 5 to 95 Non condensing Weight 9 5 oz 270 g These specifications are subject to change without notice See ODVA DeviceNet Specification Volume 1 Section 9 3 for complete DeviceNet cabling specifications SUP0462 01 19 APR 2002 PAGE 9 CH 2 CHAPTER 2 INSTALLATION 2 1 Installing and Removing a SmartStack Module Shown with the OCS The following section describes how to install and remove a SmartStack Module Caution To function properly and avoid possible damage do not install more than four Smart Stack Modules per OCS or RCS a Installing SmartStack Modules 1 Hook the tabs Each SmartStack Module has two tabs that fit into slots located on the OCS The slots on the OCS are located on the back cover 2 Press the SmartStack Module into the locked position making sure to align the SmartStack Module fasteners with the SmartStack receptacles on the OCS b Removing SmartStack Modules 1 Using a flathead screwdriver pry up the end of the SmartStack Module opposite of tabs and swing the module out 2 Lift out the tabs of the module SmartStack Tab Fastener d Mating Pins OCS Back Cover
41. uration as well as the configuration of each individual DeviceNet node All nodes including the DNT450 must be configured for the same baud rate 2 Identify all devices nodes that are going to be a part of the network 3 Is Data Assembly information available for each DeviceNet node in the network This can be in the form of printed information in the manufactures manual or in the form of an EDS file provided by the manufacturer Note that some EDS files do not provide the nodes polled consumption and production sizes 4 Assign MACIDs node addresses to each DeviceNet node The MACIDs assigned to each node is totally arbitrary The only thing that might have an effect here is the fact that the DNT450 actually scans the nodes in order by MACID Gaps can be left in the MACID assignments to allow for future nodes to be added if desired DeviceNet provides for nodes with lower MACIDs to have a higher network priority The MACID for the DNT450 can be assigned any unused address Every node on the network must be assigned a unique MACID 5 All bit type input data must be assigned to a contiguous block of PLC l registers and all word type input data must be assigned to a contiguous block of PLC AI registers 6 Furthermore all bit type output data is required to be assigned to a contiguous block of PLC Q registers and all word type output data must be assigned to a contiguous block of PLC AQ registers When these steps are taken then a v
42. y Each parameter can be bit data bits word data words or nothing none This value is set in the parameter type drop down window The count of each parameter is set in the parameter count drop down box The parameter drop down box is used to select any of the four available parameters within an assembly for editing viewing l and Al values come together to form the production size of the node These are values going from the node onto the network to the DNT450 Q and AQ values come together to form the consumption size of the node These values are values coming from the network The DNT450 into the node Time out delay values can be set in this screen as well See section 3 7 for details on the time out delay values When done configuring a node click OK The process can then be repeated for another node and so forth until the entire network is done Note Bit data must be in groups of 8 PAGE 34 19 APR 2002 SUP0462 01 CH 6 The user can choose to press Network Auto Remap to remap the nodes in the network Caution Auto Remap reassigns the reference addresses for all nodes so that no gaps are left in the map The Auto Remap action cannot be undone and needs to be used with caution The Network baud rate and register base addresses can be set at any time by Selecting Network then Properties or by double clicking anywhere on the screen in the right window pane This will bring up the Network Properties Figure 5 5 screen again
43. y Formats under UCMM When using Polled Messaging data is read from the PLC s Q and AQ registers by the DNT450 formatted into DeviceNet packets and sent to the DeviceNet nodes As data produced by the DeviceNet nodes is received by the DNT450 it is converted into PLC register notation and stored in the PLC s l and Al registers This happens automatically without the need for block move or other ladder program intervention PAGE 8 19 APR 2002 SUP0462 01 CH 1 1 3 Technical Specifications Table 1 1 DNT450 Specifications DeviceNet Network Specifications Parameter DeviceNet Power Voltage DeviceNet Power Load DeviceNet Signal Baud Rate DeviceNet Signal Driver Fanout PLC Power Load Specifications Parameter 5Vdc LOGIC 24Vdc RELAY 24Vdc ISOLATED Environmental Specifications Parameter Operating Temperature Storage Temperature Humidity non condensing Cable Specifications Description DeviceNet Thick Cable 3082A One twisted pair for signal 18 gauge separately foil shielded One twisted pair for power 15 gauge separately foil shielded Overall foil braid shield with 18 gauge drain 8 Amps maximum power Belden DeviceNet Thin Cable 3084A One twisted pair for signal 24 gauge separately foil shielded One twisted pair for power 22 gauge separately foil shielded Overall foil braid shield with 22 gauge drain 3 amps maximum power en 125KHz 250KHz 500kHz EE 125KHz 250KHz 500kHz These specifica

DeviceNet Master (Scanner)

Contents

Download Pdf Manuals

Related Search

Related Contents