VersaMax DeviceNet
Contents
1. 33 107 38 122 4 20 9 35 14 50 19 65 24 80 29 95 34 110 39 125 2 Always 0 3 Status Pointer Memory 8 R 10 Al 12 AQ 4 Status Pointer Offset 0 based 5 6 Always 0 The slave devices can be entered in the COMREQ in any order The NCM checks that the lengths for the four data areas sent in the PLC configuration file match the sum of the lengths sent in the COMREQ For convenience the units of length in the configuration of a Generic Communication Module match the units of length defined in the COMREQ Any bit length field must be entered as a multiple of 8 bits such as 8 16 24 etc COMREQ Data Block Word Byte Contents 1 1 2 COMREQ Command Number 1000H 2 3 aster Address 0 63 4 aster Baud Rate 0 125k 1 250k 2 500k 3 5 f NCM is Slave Length of its data in bits 0 if none 6 f NCM is Slave Length of its Al data in words 0 if none 4 7 f NCM is Slave Length of its Q data in bits 0 if none 8 f NCM is Slave Length of its AQ data in words 0 if none 5 9 10 Reserved for Master Scan Rate undocumented 0 Scan as fast as possible 6 11 12 CM Slave communication mode 0 UCMM capable 1 Group 2 Only This field is only applicable when the NCM is configured as a Slave only This field is ignored when the NCM is configured as a Master device In the Master case the CM Slave communication mode is fixed as UCMM capable 7 8 13 162. Data Packet Size 0 8 bytes with allowance for message fragmentation Duplicate Address Detection Addresses verified at power up Error Detection Correction CRC retransmission of message if validity not acknowledged by recipient VersaMax System DeviceNet Communications Modules User s Manual June 1999 GFK 1533 Bus Length The maximum length of the bus is limited by the cable type transfer rate and number and accumulated length of drop lines Individual branch lengths may not exceed 6 meters and are limited to one network node per drop However the node may be a node offering multiple ports With Thin cable the maximum bus length regardless of data rate is 100m With Thick cable used as the trunk line the maximum bus length is as shown in the following table Data Rate Bus length and drop length restrictions 500Kbps 100m bus length and branches totaling lt 39m 250Kbps 250m bus length and branches totaling lt 78m 125Kbps 500m bus length and branches totaling lt 156m GFK 1533 Chapter 2 Installation 2 9 Bus Connectors and Termination DeviceNet has two basic connection types An open connector is available with inline terminal block wiring terminations This connection type is suitable for environments without excessive humidity or vibration levels The second type uses a five pole circularly arranged connector This type provides a robust connection is more resistant to moisture and v
3. Discrete output data defaults to 0 while analog output data holds its last state GFK 1533 Chapter 3 The DeviceNet Network Interface Unit 3 7 Network Interface Unit Status Control Data Formats The master application is able to access fault information from the NIU s internal fault table which can store up to 32 faults The internal fault table operates as a First In First Out stack When fault 33 occurs fault 1 is dropped from the table These faults can include both faults provided by the I O modules and diagnostic information provided by the NIU itself Reporting Faults The NIU reports faults to the master automatically as part of its regular I O data Normally in the absence of any faults in the NIU the NIU Diagnostic Status Word is always 0 When the first fault is logged into an empty fault table the NIU updates the Diagnostic Status Word to indicate both the presence of a fault and the specified information for that fault The NIU continues to report the fault until either a power cycle occurs or a DeviceNet master requests to acknowledge the fault or clear all the faults Acknowledging Individual Faults A DeviceNet master requests to acknowledge a fault in the NIU fault table using the NIU Control Word When the NIU receives an acknowledge fault request the NIU updates the content of its Diagnostic Status Word with the Format 2 word for that fault The master can then acknowledge the Format 2 Word of the fault also using t
4. 6 Node addresses 48 55 Byte 7 Node addresses 56 63 i e a Each bit represents the status of the device corresponding to that node address For example bit 0 in byte 0 represents the status of the device with node address 0 Bit 1 in byte 0 represents the status of the device with node address 1 and so on When the NCM is configured as a Slave device the corresponding bit for the NCM address represents the status of the Slave device When the NCM is configured as a Master only the corresponding bit is 0 Bit Value Description 0 The device is NOT successfully exchanging I O data on the DeviceNet network 1 The device is successfully exchanging I O data on the DeviceNet network VersaMax System DeviceNet Communications Modules User s Manual June 1999 GFK 1533 Output Data Format Output Data is sent by the PLC CPU once each logic scan to the DeviceNet NCM for transmission to each of the slave devices The bit type discrete and word type analog data appears in the order specified by the list of slave devices in the Configuration COMREQ If the NCM is a slave itself its bit type and word type output data appears first in the respective areas All of the bit type output data specified for the slaves is combined together in the Q table and all of the word type output data is combined together in the AQ table First byte Last byte gt Bit type Output Data to Network Word type Output Data to Netw
5. Reserved 9 17 First Slave s Address 0 63 18 First Slave s I O mode 1 Poll 2 Strobe 4 COS w Ack 0xC COS w o Ack 10 19 First Slave s data length in bits 0 if none 20 First Slave s Al data length in words 0 if none 11 21 First Slave s Q data length in bits 0 if none 22 First Slave s AQ data length in words 0 if none 12 14 23 28 Second Slave s configuration 126 128 251 256 Fortieth Slave s configuration VersaMax System DeviceNet Communications Modules User s Manual June 1999 GFK 1533 Slave Communication Mode There are two possible communication modes for the NCM Slave Normally the NCM should be configured as a UCMM capable slave device This is the default communication mode and is highly recommended However if the NCM must communicate to a DeviceNet master that does not support communication with UCMM capable slave devices the Group 2 Only communication mode must be selected The Slave communication mode field is ignored when the NCM is configured as a Master only or Master Slave combination In both of these cases the NCM is always UCMM capable Slave I O Mode Slave I O mode is configurable as Polled Bit Strobed Change of State with Acknowledgement or Change of State without Acknowledgement It is possible to mix slaves with different I O modes in the same network configuration For example it may be beneficial to Bit Strobe all the input only slave devices and Poll
6. Yes transceiver powered by network Module and Network 2 10 position rotary switches 0 63 63 1 10 position rotary switch 0 2 125K 250K 500K Yes Yes Yes Yes A 1 DeviceNet Required Object Implementation Object Class Attributes Object Class Services Object Instance Attributes Object Instance Services Vendor Specific Additions Identity Object 0x01 None Supported None Supported ID Description 1 Vendor 2 Product Type 3 Product code 4 Revision 5 Status bits supported 6 Serial Number 7 Product Name 8 State DeviceNet Services Reset Get_Attribute_Single No Access Get Get Get Get Get N A Get Get Yes Yes A 2 VersaMax System DeviceNet Communications Modules User s Manual June 1999 Value Limit 326 12 OChex 1 1 001 0 2 8 9 10 11 DeviceNet NIU GFK 1533 GFK 1533 DeviceNet Required Object Implementation DeviceNet Required Object Implementation Message Router Object 0x02 Object Class Attributes Object Class Services Object Instance Attributes Object Instance Services Vendor Specific Additions DeviceNet Object 0x03 Object Class Attributes Object Class Services Object Instance Attributes Object Instance Services Vendor Specific Additions Appendix A NIU DeviceNet Statement of Compliance None Supported None Supported None Supported None Supported No None Supported None Supported None Supported None Supported
7. are fully inserted in the holes in bottom edge of the NIU Turn the latch to the locked position to secure the power supply to the top of the NIU module Removing the Power Supply from the NIU Exercise care when working around operating equipment Devices may become very hot and could cause injury Remove power Turn the latch to the unlocked position as illustrated Press the flexible panel on the lower edge of the power supply to disengage the tabs on the power supply from the holes in the carrier Pull the power supply straight off 2 2 VersaMax System DeviceNet Communications Modules User s Manual June 1999 GFK 1533 Network Interface Unit Installation Setting the Network Address Open the clear protective door by pulling upward at the indentation in the side of the NIU Use a 2 44mm 3 32in flat screwdriver to adjust the rotary switches These switches marked Node Address X10 and X1 select the tens and units digits of the network address Select any valid address in the range 0 63 U Power up in upload mode u01 T Nope 2 ADDRESS 3 X10 65 4 9 0 1 8 ZOE T 01 2 DATA RATE p Setting the Data Rate Use the switch marked Data Rate to select the network data rate 0 125K 1 250K 2 500K Upgrading the NIU Firmware 1 Connect the cable IC200CBL002 from the programming device to the port on the lefthand side o
8. for the accuracy completeness sufficiency or usefulness of the information contained herein No warranties of merchantability or fitness for purpose shall apply The following are trademarks of GE Fanuc Automation North America Inc Alarm Master Genius PowerTRAC Series Six CIMPLICITY Helpmate ProLoop Series Three CIMPLICITY 90 ADS Logicmaster PROMACRO VersaMax CIMSTAR Modelmaster Series Five VersaPro Field Control Motion Mate Series 90 VuMaster GEnet PowerMotion Series One Workmaster Copyright 1999 GE Fanuc Automation North America Inc All Rights Reserved Chapter 1 Chapter 2 Chapter 3 Chapter 4 Appendix A Appendix B Appendix C Appendix D GFK 1533 Contents MME OCU CHOM sosccseeiascasaeschccbecdetccescdsteceecisicetscactetdscdatcececsehcedecteccasecses 1 1 DeviceNet snienu Da a a a a aa Seek peat aa a a Seassesb sees 1 2 VersaMax Modules for DeviceNet NetworkS cccccccccceecccecceeesceeeseeee 1 3 Wns tall ati Oss ccssccoisssicosisscscespecoscostecascoosesoscosvssosseoiecosisots sois oosso scos viee 2 1 Preinstallation Check cccccccssccsseccvecceseceseccensceessceesecesseceesscessecesses 2 1 DeviceNet Network Interface Unit Installation 0 c eee ceecceeeeeeee 2 2 DeviceNet Network Control Module Installation 0 eee ceeeceeeeeeee 2 5 Installing the DeviceNet Cable 0 eee eesssceccessneeeeeeseeeceeseeeeessaaeees 2 8 Bus Connectors and Termination cccccccccccceccccs
9. master the NCM provides Unconnected Message Manager Proxy UCMM capability on behalf of its Group 2 Only Server slave devices The UCMM Proxy service allows a commercially available DeviceNet monitor utility to communicate with the Group 2 Only Servers owned by the NCM Multiple NCMs may be present on the same DeviceNet network The DeviceNet NCM does not supply the power needs of the network Another device usually a standalone power supply must be used for that purpose Up to 63 additional devices may also reside on the network with the NCM and the power supply Of these devices up to 40 may be slaves controlled by the DeviceNet NCM IC200BEM103 x DeviceNet 00 NETWORK MASTER net IND CONT EQ FOR HAZ LOC CLASS DIV 2GROUPS ABCD Temp Code T4A Ambient 60C CLASS ZONE 2GROUP IIC T4A CLASS ZONE 2 Ex nA IIC TAA a OC to 60C L O LISTED 7 meg C ok E157515 1 MADE INUSA nit MAT H GFK 1533 NCM Specifications 4 2 Maximum size of input and output buffers including NCM status area 1K bytes Address range of master and slave devices Largest number of slave devices when NCM 40 is master Maximum size of a slave reference type 248 bits of discrete input and ou
10. the Loss of Device fault when it has successfully reestablished a connection to a specific slave device The NCM logs an Addition of Device fault and sets the communications status bit corresponding to the slave device to 1 An Addition of Device fault is only logged if a Loss of Device fault was logged previously for the same device The network address of the added device is indicated in the Fault Location field The first byte of the Additional Fault Data will generally contain 0x02 meaning that the slave is again active Connecting to a slave device for the first time after a power cycle or reset is not an Addition of Device fault Addition of Device Loss of Device Error Codes Error Code Description 3 Timeout error This error usually occurs when a slave device loses power or otherwise is disconnected from the network 4 The Master could not establish a UCMM connection with the slave device A communication error may have occurred try again 5 The Master Slave Connection Set of the slave device is already allocated and is currently busy Another master device may have already allocated the Connection Set The Master Slave Connection Set of the NCM could not be allocated by the NCM A communication error may have occurred try again The input data length configured for the slave device does not match the data produced by the slave device F The output data length configured for the slave device do
11. the remaining slave devices Polled I O Mode Polled I O Mode specifies that a slave device will be sent a Polled request message containing the outputs to the slave device The slave devices must respond with a Polled response with the inputs from the slave device The NCM will attempt to Poll all of the slave devices configured as Polled as fast as possible Bit Strobed I O mode Bit Strobed I O Mode specifies that the NCM will send a single Bit Strobe request message that is received and acted upon by all slave devices configured for Bit Strobe I O mode Each slave will then respond with its input data This mode improves performance over the usual Polling I O mode as the NCM does not need to send an individual Poll request to each slave This mode is particularly useful for slave devices that have input data only such as sensors etc Change of State COS with Acknowledge Change of State COS with Acknowledgement Mode specifies that the NCM will not query the slave device for its input data Instead the slave device will transmit its input data only when any of the data changes state The NCM must acknowledge receipt of the COS data or the slave will continue to transmit it Change of State COS without Acknowledge Change of State COS with Acknowledge Suppressed Mode is similar to the Acknowledge Mode except that the NCM is not required to acknowledge the receipt of the COS data And thus the slave will transmit its input data o
12. 0 Information Instance type Explicit Message Polled I O ID Description 1 State 2 Instance type 3 Transport class trigger 4 Produced connection ID 5 Consumed connection ID 6 Initial comm Characteristics 7 Produced connection size 8 Consumed connection size 9 Expected packet rate 10 Undefined 11 Undefined 12 Watchdog time out action 13 Produced connection path length 14 Produced connection path 15 Consumed connection path length 16 Consumed connection path DeviceNet Services Get_Attribute_Single Yes No B 4 VersaMax System DeviceNet Communications Modules User s Manual June 1999 Max 40 Access Get Get Get Get Get Get Get Get Get Get Get Get Get Get GFK 1533 Appendix Electronic Datasheet EDS for the NIU C Module This appendix shows the initial version of the EDS file for the VersaMax DeviceNet Network Interface Unit It is included only for reference an electronic version of the EDS file is included on a diskette with each NIU IC200DBI001 DeviceNet Network Interface Unit Electronic Data Sheet File Description Section File DescText IC200DBI001 EDS File CreateDate 05 05 1999 CreateTime 10 25 00 ModDate 00 00 00 ModTime 00 00 00 Revision 1 0 Device Description Section Device VendCode 326 VendName GE Fanuc Automation ProdType 12 ProdTypeStr Communications Adapter ProdCode 1 MajRev l MinRev 100 Pro
13. 001 AA DeviceNet NIU THIS DEVICE COMPLIES WITH PART 15 OF THE FCC RULES OPERATION IS SUBJECT 7 TO THE FOLLOWING CONDITIONS 1 THIS DEVICE MAY NOT CAUSE vo NODE HARMFUL INTERFERENCE 3 ADDRESS 2 THIS DEVICE MUST ACCEPT ANY 5 x10 INTERFERENCE RECEIVED INCLUDING 5 4 INTERFERENCE THAT MAY CAUSE 0 UNDESIRED OPERATION gS THIS DIGITAL APPARATUS DOES NOT 8 XL EXCEED THE CLASS A LIMITS FOR RADIO 7 3 NOISE EMISSIONS FROM DIGITAL APPARATUS 64 SET OUT IN THE RADIO INTERFERENCE REGULATIONS OF THE CANADIAN DEPART 901 MENT OF COMMUNICATIONS FOR USE IN 2 ACONTROLLED ENVIRONMENT REFER TO DATA MANUALS FOR ENVIRONMENTAL CONDITIONS RATE ENCAD DUTIUSATION EN ATMOSPHERE CONTROLEE CONSULTER LA NOTICE SS TECHNIQUE IND CONT EQ FOR HAZ LOC CLASS DIV 2 GROUPS ABCD Temp Code T4A Ambient 60C ry e H o CAN_H i I gt SHLD MADE IN USA H o CAN_L ON 2 LISTED o fY m CE The Network Interface Unit installs on a 35mm x 7 5mm conductive DIN rail A VersaMax power supply module mounts directly on the righthand side of the NIU LEDs on the lefthand side indicate the presence of power and show the operating mode and status of the NIU Three rotary dials beneath a clear protective door are used to configure the NIU s address and data rate on the DeviceNet network The connector is used to connect the bus cable GFK 1533 3 1 NIU Specifications Number o
14. 1 Index 1 Index ESD File D 1 fault handling input data format operation 4 9 o XE NCM lt fault handling XE Error codes loss of device utput data la specifications UCMM capable slave Network address ae Network Control Module See NCM Network Interface Unit See NIU NIU configuration control data 3 11 description DeviceNet Statement of Compliance A 1 ESD file 3 5 ESD File C 1 inputs and outputs 3 1 operation specifications status data O ODVA1 2 Open DeviceNet Vendors Association 1 2 Output data 3 7 Output defaults 3 7 p Polled I O mode Power supply 1 3 Power supply installation 2 2 Profibus Trade Organization S Slave I O mode Static protection 2 1 Status data 3 9 Index 2 VersaMax System DeviceNet Communications Modules User s Manual June 1999 Terminating the bus 2 10 U Upgrading firmware 2 3 GFK 1533
15. FANUC GE Fanuc Automation Programmable Control Products VersaMax System DeviceNet Communications Modules User s Manual GFK 1533 June 1999 GFL 002 Warnings Cautions and Notes as Used in this Publication Warning notices are used in this publication to emphasize that hazardous voltages currents temperatures or other conditions that could cause personal injury exist in this equipment or may be associated with its use In situations where inattention could cause either personal injury or damage to equipment a Warning notice is used Caution notices are used where equipment might be damaged if care is not taken Note Notes merely call attention to information that is especially significant to understanding and operating the equipment This document is based on information available at the time of its publication While efforts have been made to be accurate the information contained herein does not purport to cover all details or variations in hardware or software nor to provide for every possible contingency in connection with installation operation or maintenance Features may be described herein which are not present in all hardware and software systems GE Fanuc Automation assumes no obligation of notice to holders of this document with respect to changes subsequently made GE Fanuc Automation makes no representation or warranty expressed implied or statutory with respect to and assumes no responsibility
16. I O Modules It is possible to hot insert I O modules into the I O Station When replacing a module that already exists in the configuration no other action is necessary to make the module operable Clearing the Configuration To clear an existing configuration from the NIU power down the NIU disconnect the NIU from the first I O module and power up the NIU The configuration in the NIU is then cleared VersaMax System DeviceNet Communications Modules User s Manual June 1999 GFK 1533 EDS File Every DeviceNet device certified by the Open DeviceNet Vendors Association is required to define an EDS file electronic data sheet The EDS file may be needed by DeviceNet network configuration tools to correctly configure and or operate a DeviceNet device The EDS file is a simple text file filled with keywords and values that together define the specific characteristics features and limitations of the slave device In Appendix C is a printout of the initial version of the EDS file for the VersaMax DeviceNet Network Interface Unit In Appendix D is a printout of the initial version of the EDS file for the VersaMax Network Control Module They are included only for reference an electronic version of the EDS file is included on a diskette with each VersaMax DeviceNet device GFK 1533 Chapter 3 The DeviceNet Network Interface Unit 3 5 Network Interface Unit Operation 3 6 The NIU exposes exactly one input data object to read from
17. No A 3 DeviceNet Connection Object 0x05 Required Object Object Class Attributes None Supported Implementation Object Class Services None Supported Total Active Connections 2 Possible Object Instance Instance type Object Instance 1 Attributes nun FW N O on 10 11 12 13 14 15 16 DeviceNet Services Object Instance Services Get_Attribute_Single Yes Vendor Specific No Additions Information Max Explicit Message 1 Polled O 1 Change of State 1 Description Access State Get Instance type Get Transport class trigger Get Produced connection ID Get Consumed connection ID Get Initial comm Get Characteristics Produced connection size Get Consumed connection size Get Expected packet rate Get Unused Unused Watchdog time out action Get Produced connection path Get length Produced connection path Get Consumed connection path Get length Consumed connection path Get A 4 VersaMax System DeviceNet Communications Modules User s Manual June 1999 GFK 1533 DeviceNet Required Object Implementation Assembly Object 0x04 Object Class Attributes Object Class Services Object Instance 1 Attributes Object Instance Services Vendor Specific Additions Object Instance 2 Attributes Object Instance Services Vendor Specific Additions None Supported None Supported DeviceNet Services Get_Attribute_Single No DeviceNet Services Set_Attribute_Single No GFK 1533 Appen
18. at the center point of two network segments thus supplying 8A to each segment With the use of Thin cable a maximum of 3A is permitted As with most Fieldbus networks grounding of the network and its devices is very important In DeviceNet it is required that all cable shields be tied to ground at each device connection This is done by tying the bare wire of the cable to pin 3 Shield of the connector The DeviceNet network power supply must also be grounded but only at one point The V signal must be connected to Protective Earth Ground at the power supply only If multiple power supplies are used only one power supply must have V connected to Earth Ground GFK 1533 Chapter 2 Installation 2 11 Chapter The DeviceNet Network Interface Unit 3 The DeviceNet Network Interface Unit IC200DBI001 can be used to interface VersaMax I O modules to a DeviceNet network Together the NIU and its modules form an I O station capable of handling up to 128 bytes of discrete and analog input data and up to 128 bytes of discrete and analog output data The system host can be any device capable of operating as a bus master The NIU operates as a Group 2 Only Slave automatically exchanging I O status control and diagnostic data with a master device The NIU conforms to the DeviceNet Specification Volumes I and II version 2 0 Open DeviceNet Vendors Association E DBI001 z OOO0O0O0 FORCE IC200DB1
19. ate 05 10 1999 CreateTime 11 55 00 ModDate 00 00 00 ModTime 00 00 00 Revision 1 0 Device Description Section Device VendCode 326 VendName GE Fanuc Automation ProdType 12 ProdTypeStr Communications Adapter ProdCode 1 MajRev l MinRev 100 ProdName DeviceNet NCM Catalog IC200BEM103 D 1 A Add modules to autoconfiguration Autoconfi guration 3 3 B Bit strobed I O mode 4 7 Bus cable specifications 2 8 connectors grounding 2 11 length power supply 2 11 termination 2 10 Cable specifications Catalog number 4 1 Change of State modes 4 7 Communications Carrier COMREQ error codes 4 8 Configuration clearing 3 4 Conformance to standards 2 1 Connectors Control data Data rate sane Be 3 1 Description DeviceNet messages DIN rail 2 2 Documentation 1 1 E EDS file NCM NIU C 1 Error codes loss of device 4 11 Error codes COMREQ 4 8 GFK 1533 Index Fault codes Fault table Faults clear 3 11 Firmware upgrade 2 3 G Grounding pal 1i H Hot inserting modules 3 4 TO data sizes Input data Inserting modules 3 4 Installation instructions 2 1 LEDs blinking in boot mode 2 3 M Manuals 1 1 Module installation Modules per station N NcM 4 1 communication modes 4 7 communications status data configuration description DeviceNet Statement of Compliance B
20. ations Carrier The latch on the Network Control Module must be in the unlocked position Align the connectors and the latch post and press the Network Control Module down firmly until the two tabs on the bottom of the NCM click into place Be sure the tabs are fully inserted in the holes in bottom edge of the Communications Carrier Turn the latch to the locked position to secure the Network Control Module to the top of the carrier Removing the Network Control Module from the Carrier Exercise care when working around operating equipment Devices may become very hot and could cause injury 2 6 VersaMax System DeviceNet Communications Modules User s Manual June 1999 Remove power Turn the latch to the unlocked position as illustrated Press the flexible panel on the lower edge of the NCM to disengage the tabs on the NCM from the holes in the carrier Pull the NCM straight off GFK 1533 Network Control Module Installation Observing the LEDs GFK 1533 OK oK MoD NET MOD NET Chapter 2 Installation OFF when the NCM has not yet started its powerup sequence Blinking green indicates the NCM is performing its powerup sequence and has not yet finished successfully Green indicates the NCM has successfully completed powerup diagnostics Amber when the NCM has either failed powerup diagnostics or has not yet recei
21. ctively Enter the Module ID FFFF9808 Wiring can be used to enter tags for the different data points E Power Consumption can be used to enter the power consumption figures for the DeviceNet NCM 4 4 VersaMax System DeviceNet Communications Modules User s Manual June 1999 GFK 1533 Sending the Configuration COMREQ from the Application Program The second part of configuring an NCM is to send a single COMREQ from the application program to the NCM No communications can occur until a valid COMREQ is received by the NCM The format of this COMREQ is shown on the next page The configuration COMREQ defines whether the NCM is used as a DeviceNet Master a DeviceNet Slave or as both simultaneously It specifies the network address and data rate of the NCM It also specifies the network address of each device the I O mode and the lengths of each slave s data The sum of the I O data for each slave device including the NCM itself if the NCM is a Slave and the 64 bits of Communications Status Data must exactly equal the length for each reference type entered using the configuration software Configuring the NCM as a DeviceNet Master Only When configuring the NCM as a DeviceNet Master the COMREQ must specify e the network address of the Master the network data rate of the Master e For each subordinate slave its network address its I O mode e the amount of I O data of each reference type I AI Q AQ Configuring th
22. d FRG bit in the NIU Control bytes to obtain the rack slot and point location of the fault GFK 1533 Chapter 3 The DeviceNet Network Interface Unit 3 9 3 10 Status Data Format 2 Byte 1 7 6 5 4 3 2 1 0 Point 0 63 Format 0 3 Bit s Value Meaning Format identifier 0 Format 1 of NIU Status Data 1 Format 2 of NIU Status Data 2 3 Reserved The physical point location of the fault 0 63 correspond to points 1 64 Byte 2 z e s 4 Js 2 o Bis Value Meaning a The slot location of the faulted module The value 0 indicates the NIU itself r z gt The physical rack location of the faulted I O module The value 0 refers to the NIU main rack Oor1 0 no fault data present The remaining fields in byte 1 and 2 may be ignored 1 a fault is present The remaining fields in byte 1 and 2 provide the format identifier and rack slot and point location of the fault VersaMax System DeviceNet Communications Modules User s Manual June 1999 GFK 1533 NIU Control Data Format The first two bytes of the output data from the master are reserved for the NIU control data The NIU control data defines several bits that can be used by the master application to send commands to the NIU The following table defines the bits and their meanings Byte 1 z7 e 5s 4 s Je 1 fo Bit s Value Meaning Fault fragment acknowledge command When this bit changes to 1 the NIU updates the NIU sta
23. dName DeviceNet NIU Catalog IC200DBI001 IO_Info Default 0x0001 Bit mapped 0 None Bit 0 Poll Default Bit 2 Change of State PollInfo 0x0001 Not OK to Combine w COS 1 Default Input Input 1 Default Output Output GFK 1533 c 1 C 2 COSInfo 0x0004 Not OK to Combine w Poll 1 Default Input Input 1 Default Output Output1 Input Connections Inputl 130 130 bytes maximum 0 all bits are significant 0x0005 Poll or COS Connection Status Data Name String 6 Path Size 20 04 24 01 30 03 Assy Obj Inst 01 Attr 3 NIU Status and Data Help String Output Connections Outputl 130 130 bytes maximum 0 all bits are significant 0x0005 Poll or COS Connection Control Data Name String 6 Path Size 20 04 24 01 30 03 Assy Obj Inst 01 Attr 3 NIU Control and Data Help String VersaMax System DeviceNet Communications Modules User s Manual June 1999 GFK 1533 Appendix Electronic Datasheet EDS for the NCM D GFK 1533 Module This appendix shows the initial version of the EDS file for the VersaMax DeviceNet Network Control Module It is included only for reference an electronic version of the EDS file is included on a diskette with each NCM IC200BEM103 DeviceNet Network Communications Module Electronic Data Sheet File Description Section File DescText IC200BEM103 EDS File CreateD
24. dix A NIU DeviceNet Statement of Compliance ID Yes Yes Description Access Value Data Data Get Set Limit 2 130 2 130 A 5 Appendix B General Device Data DeviceNet Physical Conformance Data DeviceNet Communication Data GFK 1533 NCM DeviceNet Statement of Compliance This section details the level of compliance required for the DeviceNet Network Control Module For details regarding this form and the items listed refer to the DeviceNet Protocol Specification Conforms to DeviceNet Specification Vendor Name Device Profile Name Product Catalog Number Product Revision Network Power Consumption Max Connector Style Isolated Physical Layer LEDs Supported MAC ID Setting Default MAC ID Communication Rate Setting Communication Rates Supported Predefined Master Slave Connection Set Group 2 Only Client Fragmented Explicit Messaging Implemented Dynamic Connections Supported UCMM Volume I Release 2 0 Volume II Release 2 0 GE Fanuc Automation DeviceNet NCM Communications Adapter 1 10 10mA 11V dc worst case unknown at this time Open Hardwired Yes transceiver powered by network Module and Network Software selectable 63 Software selectable 125K 250K 500K Yes Yes Yes Yes Group 3 B 1 DeviceNet Required Object Implementation B 2 Identity Object 0x01 Object Class Attributes Object Class Services ID Object 1 Instance At
25. e NCM as a DeviceNet Slave Only When configuring the NCM as a DeviceNet Slave the COMREQ must specify e its network address e jts network data rate e its network mode e the amount of I O data of each reference type I AI Q AQ Configuring the NCM as a DeviceNet Master and Slave Combined When configuring the NCM as both a DeviceNet Master and Slave the COMREQ must provide all of the configuration information for both a Master and Slave Note that in this combined scenario the network mode of the slave is ignored as the Master configuration requires the slave to be UCMM capable e the network address of the Master Slave e the network data rate of the Master Slave For the NCM as a Slave the amount of I O data of each reference type I AI Q AQ e For each subordinate slave its network address its I O mode e the amount of I O data of each reference type I AI Q AQ GFK 1533 Chapter 4 The DeviceNet Network Control Module 4 5 4 6 Configuration COMREQ Format The command block and the data block of the COMREQ are shown below COMREQ Command Block Word Contents 1 Length of the data block in words Shown below number of slaves length 0 8 5 23 10 38 15 53 20 68 25 83 30 98 35 113 40 128 1 11 6 26 11 41 16 56 21 71 26 86 31 101 36 116 2 14 7 29 12 44 17 59 22 74 27 89 32 104 37 119 3 17 8 32 13 47 18 62 23 77 28 92
26. e to static damage Use proper static prevention techniques when handling this module Conformance to Standards GFK 1533 Before installing VersaMax products in situations where compliance to standards or directives from the Federal Communications Commission the Canadian Department of Communications or the European Union is necessary please refer to GE Fanuc s Installation Requirements for Conformance to Standards GFK 1179 2 1 DeviceNet Network Interface Unit Installation The NIU snaps directly onto the DIN rail No tools are required AS AN P Removing the NIU from the DIN Rail 1 Turn off power to the power supply 2 If the NIU is attached to the panel with a screw remove the power supply module Remove the panel mount screw 3 Slide the NIU along the DIN rail away from the other modules until the connector disengages 4 With a small flathead screwdriver pull the DIN rail latch tab outward while tilting the other end of the module down to disengage it from the DIN rail Installing the Power Supply on the NIU Ex 1 limimil bs The power supply module installs directly on top of the NIU The latch on the power supply must be in the unlocked position Align the connectors and the latch post and press the power supply down firmly until the two tabs on the bottom of the power supply click into place Be sure the tabs
27. ecccsecccsscceuecceueceeueseees 2 10 Bus Power Supply and Grounding ee eeeseeeeeesseeeeeesneeeeeessseeeeeesaes 2 11 The DeviceNet Network Interface Unit ccccccccsssssssssssssseeees 3 1 NIU Specifications nc ccicec ce tiecce tee e e ccs cece cock cute AN ATE 3 2 Autoconfiguration 0 eee eee ee seeeccessnceeceeseeeceessaeeceesnaeeesesssaeecsssaeeesesaeees 3 3 EDS ENE ians et att com neta CONN RU UES UIS LEMUR NUON IUIU DER RUUYESY USO SU TERE UE REL TSU EOAETEREUEUUNTSN CS 3 5 Network Interface Unit Operation eeeseeeeessneeeeessseeeeessseeeeeenaeees 3 6 Network Interface Unit Status Control Data Formats cccccceecceeec eee es 3 8 The DeviceNet Network Control MOdulle ccccccccssssssssssssseees 4 1 NECM Specifications akinti i iiieitsisevebtbewsks beset RAE EEEE ET EEEE EERE EEEE ESES ENET 4 2 The Communications Carrier aene a E E E E E E E 4 3 Configuring the Network Control Module 0 cc eeeeeeesseeeeeesneeeeesnneees 4 4 Operation ofthe NGM vtsccce iecedeetieseeheteen ek ihe Sab ev Nhe Shades coke ede een eie 4 9 Fault Hani er oc 3h xe Face cavews auenccecaneceeevaucuceesancew teens EA 4 12 NIU DeviceNet Statement of Compliance cssssssssssesseseees A 1 NCM DeviceNet Statement of Compliance sssscccccccssseees B 1 Electronic Datasheet EDS for the NIU Module 00 C 1 Electronic Datasheet EDS for the NCM Module ccccccees D 1 Chapter Introd
28. es not match the data consumed by the slave device The output data length configured for the slave device in Change of State mode does not match the data produced by the slave device The input data length configured for the slave device in Change of State mode does not match the data consumed by the slave device If any other error code is persistent contact Technical Support for assistance 4 12 VersaMax System DeviceNet Communications Modules User s Manual June 1999 GFK 1533 Appendix A General Device Data DeviceNet Physical Conformance Data DeviceNet Communication Data GFK 1533 Conforms to DeviceNet Specification Vendor Name Device Profile Name Product Catalog Number Product Revision Network Power Consumption Max Connector Style Isolated Physical Layer LEDs Supported MAC ID Setting Default MAC ID Communication Rate Setting Communication Rates Supported Predefined Master Slave Connection Set Group 2 Only Server when selected UCMM Capable default Fragmented Explicit Messaging Implemented NIU DeviceNet Statement of Compliance This section details the level of compliance required for the DeviceNet Network Interface Unit For details regarding this form and the items listed refer to the DeviceNet Protocol Specification Volume I Release 2 0 Volume II Release 2 0 GE Fanuc Automation Communications Adapter IC200DBI001 1 10 TBDA 11V dc worst case Open Hardwired
29. f VersaMax 8 I O Modules per station modules I O data Up to 128 bytes of inputs 2 byte status word Up to 128 bytes of outputs 2 byte control word DeviceNet network address 0 to 63 Default is 63 DeviceNet network data rate 125K 250K 500K baud Indicators 6 Power LED to indicate presence or absence of power OK LED to indicate the status of the NIU powerup Fault LED to indicate presence of faults Mod LED to indicate the status of the NIU module Net LED to indicate health of the DeviceNet network Force LED not used 160mA at 5V 10mA at 3 3V Communication Master Slave Structure Media Access Arbitration CSMA with non destructive bit wise arbitration 3 2 VersaMax System DeviceNet Communications Modules User s Manual June 1999 GFK 1533 Autoconfiguration The NIU stores data internally as discrete input bits discrete output bits analog input words and analog output words The NIU Data Memories discrete input bits Al analog input words Q_ discrete output bits AQ analog output words At powerup the NIU automatically looks at the modules installed in the I O Station and assigns them to addresses in this internal I O map For modules with multiple data types each data type is assigned individually The process of assigning addresses is referred to as autoconfiguration Autoconfiguration Sequence Autoconfiguration assigns memory addresses by data type in the sa
30. f the NIU 2 Set the upper switch x10 to the U Upload position 3 Cycle power to the NIU When the NIU is in boot mode its OK and FAULT LEDs blink simultaneously at 1 2 second intervals Once the NIU is in boot mode the upper switch can be returned to its original position GFK 1533 Chapter 2 Installation 2 3 2 4 Network Interface Unit Installation Observing the LEDs The LEDs indicate the presence of power and show the operating mode and status of the NIU PWR pwr O OK ox FAULTS FAULTS O MOD MOD O NET FORCE NET FORCE green when power is applied to the NIU green when the NIU is operational amber if the NIU has detected one or more faults OFF when the NIU is not powered blinks red and green during NIU self test blinks green if the NIU configuration is missing incomplete or incorrect The NIU may be in Standby state green when the NIU is operating normally blinks red if there is a recoverable fault red if there is an unrecoverable fault The NIU may need replacing OFF when the NIU is not online or not powered blinks red and green if the NIU detects a Network Access error and is in the Communications Faulted state It has subsequently received and accepted an Identify Communications Fault Request Long Protocol message blinks green if the NIU is online but has no connections in the established state It is online but has no established connections to other nodes I
31. he NIU Control Word When the NIU receives this acknowledgement the NIU updates the Diagnostic Status Word to indicate the Format 1 Word of the next oldest fault in the fault table This process continues until all of the faults have been reported If no other faults exist the NIU clears the Diagnostic Status Word which indicates that no more faults are present Clearing All Faults A DeviceNet master can also use the NIU Control Word to request to clear all the faults in the NIU fault table When the NIU receives a request to clear all faults it clears the fault table clears the NIU Diagnostic Status Word and sends a Clear Fault message to each I O module present If any of the original fault conditions in an I O module still exist after the Clear Faults request the NIU logs a new fault in its fault table Resetting the NIU or cycling power also clears the fault table 3 8 VersaMax System DeviceNet Communications Modules User s Manual June 1999 GFK 1533 NIU Status Data Formats The first two bytes of the input data to the master are reserved for the NIU status data The NIU status data indicates the local status of the NIU and its associated I O modules The status is reported in the form of a fault message Each fault message requires 4 bytes to fully describe the fault Since there are only 2 bytes of NIU status in the input data to the master the NIU status defines two data formats Format 1 indicates the presence of a faul
32. ibration Bus Connectors The NIU and NCM both have the same 5 pin standard Phoenix open style pluggable connector although in different orientations The illustration below shows the connector orientation on both modules Network Interface Unit NIU Network Communications Module NCM gt 5 V4 eH 1 V 4 CAN_H e H 2 CANLL 3 Shield H 3 Shield H e 2 CAN_L e H 4 CAN_H i 1 V e H 5 V The connectors are keyed so that a mating connector may attach to either module without modification Connector Pin Assignments The pin to signal to wire color assignments are shown in the following table Pin Signal Wire Color 1 V Black 2 CAN_L Blue 3 Shield Bare 4 CAN_H White 5 V Red Termination Termination of a DeviceNet network is passive and includes one resistor at each end of the network i e exactly two resistors per DeviceNet network A terminating resistor is placed across the data communication signals at pin 2 CAN_L and pin 4 CAN_H The correct terminating resistor is a 121 ohm 1 1 4 watt resistor 2 10 VersaMax System DeviceNet Communications Modules User s Manual June 1999 GFK 1533 Bus Power Supply and Grounding DeviceNet requires a power supply of 24VDC 44 at a 16A maximum However with the use of Thick cable a maximum of 8A is permitted on a single network segment This is possible if the power supply is placed
33. ics described in the VersaMax Modules Power Supplies and Carriers Manual GFK 1504 Many types of modules can be combined to suit the needs of the application Power for module operation is provided by a power supply that installs directly on the NIU Additional booster power supplies can be included in the system if needed for modules with high current requirements DeviceNet NIU Optional booster Power supply power supply a la co ol E 2 N i Ilil a a i etl i IF a lja z D D j j Te J poos l Bood os Ao DeviceNet Network Control Module The DeviceNet Network Control Module IC200BEM103 is a communications module that can be configured to operate as a master as a slave or as both simultaneously It can exchange up to 512 bytes of input data and 512 bytes of output data with other devices on the DeviceNet network The VersaMax PLC CPU can read and write this data as though it were conventional bi
34. me order the modules occupy in the I O Station Each module is considered to occupy a slot The position adjacent to the NIU is slot 1 Booster power supplies do not count as occupying slots 0 0 o Autoconfiguration stops at the first empty slot or faulted module For example if there are modules in slots 1 2 3 and 5 but slot 4 is empty the module in slot 5 is not autoconfigured The NIU generates an Extra I O Module fault for it GFK 1533 Chapter 3 The DeviceNet Network Interface Unit 3 3 Autoconfiguring the DeviceNet NIU 3 4 When the NIU is powered up for the very first time it autoconfigures all the I O modules that are connected to it All I O modules physically installed in the I O Station are included in the new configuration provided no intervening empty carriers exist For the autoconfiguration process to work as expected any additional power supplies in the I O Station must be powered up at exactly the same time or before the main power supply The NIU retains this configuration until it is either cleared or powered up with I O modules added to the existing configuration Adding I O modules to an Already Configured NIU If additional I O modules are added to an existing NIU they do not become part of the DeviceNet network configuration until the NIU is power cycled Hot Inserting
35. ngth must be 0 P When configured as a Strobe device input data length must 1 8 bytes a nN Duplicate configuration for a slave device There are two or more entries with the same Slave network address 16 Master or Slave Discrete Input Length must be divisible by 8 8 16 24 etc 17 Master or Slave Discrete Output Length must be divisible by 8 8 16 24 etc 18 Unknown Configuration error 19 Headend stopped aborted configuration If no errors are detected the COMREQ is successfully acknowledged and the NCM begins the cycle of operations described on the next page 4 8 VersaMax System DeviceNet Communications Modules User s Manual June 1999 GFK 1533 Operation of the NCM The Network Communications Module first performs the powerup sequence described below After a successful powerup and after receiving its configuration the NCM operates as an interface between the DeviceNet network and the VersaMax CPU It receives data from the network then sends the data plus information about communications status as inputs to the CPU over the VersaMax backplane The CPU sends the NCM output data over the backplane The CPU scan time impact is 2 5usec per word Input and output data is described on the following pages NCM Input Data Format Input data is the data retrieved from the DeviceNet NCM by the VersaMax PLC CPU once each logic scan It consists of 8 bytes of information abo
36. nication structures including peer to peer multi master and master slave with broadcasting capabilities This allows DeviceNet to fill a broad range of control system needs Up to 64 nodes can be connected to a DeviceNet network without bridging or routing Nodes can range from single bit devices such as a limit switch or solenoid valve to intelligent I O stations with several I O modules The maximum amount of I O data that can be transferred from or to an individual node is theoretically not limited Practical limitations should be based on the response time requirements of the application DeviceNet Messages The DeviceNet message field can range between 0 and 8 bytes Messages longer than 8 bytes are fragmented into packets Packetizing does increase overhead and reduce data transmission throughput DeviceNet supports two types of messaging I O messaging and Explicit messaging I O messaging is time critical and is of high priority Explicit messages are typically used between two devices for configuration and diagnostic data transfer They are usually of low priority and not time critical DeviceNet I O messages are of three basic types Strobe messages are associated with a polling request from a master Strobe messages can be used for communication between two devices or where there are several consumers of a single message Cyclical messaging transfers data between devices at regular time intervals Devices may use cyclical messages t
37. nly once GFK 1533 Chapter 4 The DeviceNet Network Control Module 4 7 COMRE Q Error Codes If an error is detected the COMREQ is returned with an error code at the Status Pointer location Error codes for the module are listed below Error Code Hex Description 1 Successful Status Network operation can proceed NCM has already received a COMREQ NCM has not been configured NCM is using the default configuration 2 3 4 5 COMREQ does not include sufficient data length must be 8 when configured as a Slave Only a Slave information is incomplete length must be 11 14 17 etc when configured as a Master COMREQ Command number is invalid must be 0x1000 Reserved fields Words 7 8 are not 0 as required Total Discrete Input length does not match the module configuration Total Discrete Output length does not match the module configuration Total Analog Input length does not match the module configuration Total Analog Output length does not match the module configuration NCM network address is invalid must be 0 63 NCM network data rate is invalid must be 0 1 2 TIM OlQ W PS ejo Slave network address is invalid must be 0 63 Reserved en Slave VO type is invalid must be 1 2 4 or 0xC e N Multiple I O types are specified for a slave must be 1 2 4 or 0xC em Ww When configured as a Strobe device the output data le
38. o report their status to a master at regular time intervals The third type of I O messaging is unsolicited messaging from slave devices commonly referred to as change of state messaging This type of I O message allows I O to report information without token passing or polling Repetitive information is transmitted less frequently which frees up the available bandwidth This type of messaging offers more responsive control when network traffic is light However it can be more difficult to make sure that data collisions do not reduce network throughput Additional Information about DeviceNet For detailed information about DeviceNet please contact the Open DeviceNet Vendor Association at the address below Open DeviceNet Vendor Association Inc 20423 State Road 7 Suite 499 Boca Raton FL 33498 phone 954 340 5412 FAX 954 340 5413 Internet HTTP WWW ODVA ORG Email lt ODVA POWERINTERNET COM gt 1 2 VersaMax System DeviceNet Communications Modules User s Manual June 1999 GFK 1533 VersaMax Modules for DeviceNet Networks There are two different VersaMax modules for DeviceNet networks the DeviceNet Network Interface Unit NIU and the DeviceNet Network Control Module NCM DeviceNet Network Interface Unit The DeviceNet Network Interface Unit IC200DBI001 is a DeviceNet slave module that acts as controller for an I O Station of VersaMax modules I O modules in the station operate with their default characterist
39. ork From CPU 2d Discrete Output Area Q gt 4 Analog Output Area AQ tH W _ Maximum Total Outputs Length 512 bytes GFK 1533 Chapter 4 The DeviceNet Network Control Module 4 11 Fault Handling When a fault occurs the NCM sends a fault message to the PLC CPU The NCM does not relog the fault if the same condition continues to occur However if the fault is cleared while the fault condition still exists the NCM sends another fault message to the PLC CPU A power cycle or reset of the NCM resets all fault conditions to a cleared state aut scription O Loss of The NCM logs this fault when no communication of any kind is possible on the Communication DeviceNet network The NCM resets the entire 8 bytes of communications status data to 0 and stops logging Loss of Device faults The NCM clears this fault when it has successfully communicated at least once with a slave device on the DeviceNet network The logging of Loss of Device faults is re enabled Loss of Device The NCM logs a Loss of Device fault when it is unable to make a connection to a specific slave device The NCM resets the communications status bit corresponding to the slave device to 0 The network address of the lost device is indicated in the Fault Location field The particular error is indicated in the first byte of Additional Fault Data See the following table for a list of error codes The NCM clears
40. ork Control Module 4 3 Configuring the Network Control Module The DeviceNet Network Control Module must be configured in two steps The first step uses the configuration software to include the module in the PLC configuration The second step uses the programming software to send a COMREQ containing the network addressing and data lengths to the NCM VersaMax PLC Configuration for the DeviceNet NCM The NCM is configured as part of the overall VersaMax PLC system configuration The configuration software is used to specify the following module characteristics E A location The NCM can be placed in any module location in the system In the selected location insert a Communication Carrier On that Carrier insert a Generic Communications Module E Settings Select the Reference Address and Length for an I O area in each of the 4 reference types I AI Q and AQ The length for each must exactly match the total amount of data of that type for all the slave devices controlled by the NCM including the 64 bits of Communications Status Data provided by the NCM itself For example the I length must equal the total amount of all discrete input data contained in the NCM s input data area described later in this chapter And the AI length must equal the total amount of all analog input data contained in the NCM s input data area Conversely the Q and AQ lengths must equal the total amount of all discrete and analog output data respe
41. put Data Sent by the Master to the NIU The master sends the NIU one output message containing all of the output data for the configured discrete output Q and analog output AQ areas configured in the NIU s network I O map The data must be placed in the same sequence the modules physically occupy in the I O Station For example if the first I O module provides discrete output data that data will appear first in the Discrete Output Data area If the second module also provides discrete output data that data will appear next and so on The same rule applies for the Analog Output Data area If a single module receives both discrete and analog output data its discrete data is placed in the discrete area and the analog data in the analog area The maximum overall length of this output data is 128 bytes An additional 2 bytes at the start of the message are used by the master for control operations So the total maximum length of the output message from the master is 130 bytes First byte Output Data Message Last byte Control Discrete Output Data Analog Output Data ue 2 bytes P gt Vad ain Output Data Length 128 bytes gt Maximum Total Length 130 bytes gt Output Defaults On powerup when the bus is broken or when communications errors occur all outputs go to their auto configured default state Outputs remain at the Output Default State until the module receives output data from the master
42. source Some devices draw all of their power from the network supply A network can include both high capacity trunk cable and lower capacity cable for individual branch circuits DeviceNet specifies two types of network cable Thick and Thin cable Thick cable provides for longer distances and more power Generally Thick cable is used for the Trunk cable Thin cable is used for shorted distances and is generally used for drop cables or where cable flexibility is necessary DeviceNet Cable Specifications Thick Cable General Two shielded pairs Common axis with drain wire in center Specifications Overall braid shield 65 coverage 36 AWG or 0 12mm tinned Cu braid minimum individually tinned Drain wire 18 Copper min 19 strands minimum individually tinned Outside diameter 0 410 inches min to 0 490 inches max roundness radius delta to be within 15 of 0 5 O D Thin Cable General Two shielded pairs Common axis with drain wire in center Specifications Overall braid shield 65 coverage 36 AWG or 0 12mm tinned Cu braid minimum individually tinned Drain wire 22 Copper 19 strands minimum individually tinned Outside diameter 0 240 inches min to 0 280 inches max roundness radius delta to be within 20 of 0 5 O D Network Topology Bus with limited branching trunkline dropline Redundancy Not Supported Network Power for Node Nominal 24 volt DC 4 devices Allowed Nodes Bridging 64 nodes excluded
43. t and word type I O data The Network Control Module installs on a VersaMax Communications Carrier Power for the NCM comes from the power supply on the CPU or from a booster supply as shown below VersaMax PLC CPU j DeviceNet Network power supply crower supp Control Module G Ge N a ax al G el UR ponds Sasss GFK 1533 Chapter 1 Introduction 1 3 Chapter Z Installation This section gives instructions for installing the DeviceNet modules and the DeviceNet cable System installation instructions are located in the VersaMax Modules Power Supplies and Carriers Manual GFK 1504 e DeviceNet Network Interface Unit Installation e DeviceNet Network Control Module Installation e DeviceNet Cable Installation Preinstallation Check Carefully inspect all shipping containers for damage If any equipment is damaged notify the delivery service immediately Save the damaged shipping container for inspection by the delivery service After unpacking the equipment record all serial numbers Save the shipping containers and packing material in case it is necessary to transport or ship any part of the system Static Protection The Network Interface Unit has CMOS components that are susceptibl
44. t and a fault code that identifies the type of fault When the Format 1 fault is acknowledged by the master the NIU transmits Format 2 which indicates the specific location of that fault When the Format 2 fault is acknowledged by the master the NIU transmits Format 1 of the next fault in the NIU internal fault table By continuing to acknowledge each fault the master can read the entire fault table from the NIU Status Data Format 1 Byte 1 7 6 5 4 3 2 1 0 Fault code 0 63 Format 0 3 Bit s Value Meaning 0 1 Format identifier 0 Format 1 of NIU Diagnostic Status Data 1 Format 2 of NIU Diagnostic Status Data 2 3 Reserved z 0 to 63 The fault code that identities the fault Tol nknown Fault High Alarm Input Point Fault 1 Corrupted Configuration em 22 wena Faut __ __ 2 onsuppored feae 13 loverange __ 23 Thermistor Faut ut usr 24 i To D Convertor Fault p i n G ta T froe Fuse Blown 16 T Store e onae s a 7 Jaddton ofl 0 Mowe 18 Acton of Non Vo Modue 8 Extra I O Module 19 Insufficient Config Memory fae e e Mono a PT ft fopenwie T Byte 2 z e s J4 ls l2 i lo Reserved always 0 Bit s Value 0 6 always 0 Reserved alw 0 no fault data present The remaining fields in byte 1 and 2 may be ignored 1 a fault is present The remaining fields in byte 1 provide the fault code and 2 9 n o format identifier Use the Fault fragment acknowledge comman
45. t is not allocated to a master green when the NIU us inline and has connections in the established state The NIU is allocated to a master blinks red if one or more I O Connections are in the Timed Out state red if an error renders the NIU incapable of communicating on the network future indicates the presence of any forced I O value Always OFF VersaMax System DeviceNet Communications Modules User s Manual June 1999 GFK 1533 DeviceNet Network Control Module Installation The DeviceNet Network Control Module mounts on a Communications Carrier IC200CHS006 which is installed on the DIN rail as described in the VersaMax Modules Power Supplies and Carriers Manual GFK 1504 The Communications Carrier snaps easily onto the DIN rail No tools are required for mounting or grounding to the rail ALS ALA Removing the Communications Carrier from the DIN Rail 1 Turn off power to the power supply 2 If the Communications Carrier is attached to the panel with a screw remove the Network Control Module Remove the panel mount screw 3 Slide the carrier along the DIN rail away from the other modules until the connector disengages 4 With a small flathead screwdriver pull the DIN rail latch tab outward while tilting the other end of the module down to disengage it from the DIN rail GFK 1533 Chapter 2 Installation 2 5 Network Control Module Installation Installing the NCM on the Communic
46. the NIU and one output data object to write to the NIU These data objects and what they contain are described here Input Data Sent by the NIU to the Master The NIU sends one input message containing the data from all of the discrete input I and analog input ATI areas configured in the NIU s network I O map Within the discrete and analog data areas the data is sent in the same sequence the modules physically occupy in the I O Station For example if the first I O module provides discrete input data that data will appear first in the Discrete Input Data area If the second module also provides discrete input data that data will appear next and so on The same rule applies for the Analog Input Data area If a single module provides both discrete and analog input data its discrete data is placed in the discrete area and the analog data in the analog area The maximum overall length of input data is 128 bytes An additional 2 bytes at the start of the message are used by the NIU for status data to the master application So the total maximum length of the input message from the NIU is 130 bytes First byte Input Data Message Last byte a Status Discrete Input Data Analog Input Data To Master 2 bytes gt lt t Maximum Input Data Length 128 bytes Maximum Total Length 130 bytes ___ gt VersaMax System DeviceNet Communications Modules User s Manual June 1999 GFK 1533 Out
47. tput E eee Maximum time to recover a lost slave device Varies with size of network lt 10 seconds on a 10 device network Isolation Network to Frame Ground DeviceNet Network to Backplane 50 VAC continuous 500 VAC for 1 minute Indicators Module Status Network Status OK Current Drawn from Backplane 140 mA max 5 Volts Network Bit Rates 125 Kbps 250 Kbps 500 Kbps Maximum Number of Nodes on a DeviceNet 64 network Signaling CAN Standard 2 0B Modulation Baseband Encoding NRZ with bit stuffing Power supply 5 Volts 3 Media Coupling DC coupled differential Tx Rx Absolute maximum voltage range 25 to 18 Volts CAN_H CAN_L Transmission technology Shielded Twisted pair Linear trunkline dropline power and signal on the same network cable VersaMax System DeviceNet Communications Modules User s Manual June 1999 GFK 1533 The Communications Carrier The Network Master Slave Module installs on a mounting base called a Communications Carrier catalog number IC200CHS006 lt 66 8mm gt 2 63in 133 4mm 5 25in IC200CHS006 COMMUNICATIONS CARRIER Mus CE LISTED 8M8 E157515 Z gt v For applications requiring maximum resistance to mechanical vibration and shock the carrier must also be panel mounted GFK 1533 Chapter 4 The DeviceNet Netw
48. tributes 2 3 4 5 6 7 8 Object Instance Services Vendor No Specific Additions None Supported None Supported Description Vendor Product Type Product code Revision Status bits supported Serial Number Product Name State DeviceNet Services Reset Get_Attribute_Single Access Get Get Get Get Get N A Get Get Yes Yes VersaMax System DeviceNet Communications Modules User s Manual June 1999 Value Limit 326 12 OChex 1 1 001 0 2 8 9 10 11 DeviceNet NCM GFK 1533 GFK 1533 DeviceNet Required Object Implementation DeviceNet Required Object Implementation Message Router Object 0x02 Object Class Attributes Object Class Services Object Instance Attributes Object Instance Services Vendor Specific Additions DeviceNet Object 0x03 Object Class Attributes Object Class Services Object Instance Attributes Object Instance Services Vendor Specific Additions Appendix B NCM DeviceNet Statement of Compliance None Supported None Supported None Supported None Supported No None Supported None Supported None Supported None Supported No B 3 DeviceNet Connection Object 0x05 Required Object Object Class None Supported Attributes Implementation Object Class None Supported Services Total Active Connections Possible Object Instance Object Instance Attributes Object Instance Services Vendor Specific Additions 4
49. tus data to contain either the Format 2 bytes of a fault or the Format 1 bytes of the next fault When the Format 2 bytes of the last fault in the NIU has been acknowledged the NIU clears the NIU status data This bit is used when retrieving faults with the NIU Status service Fault acknowledge command When this bit changes to 1 the NIU updates the NIU status data to contain the Format 1 bytes of the next fault The Format 2 bytes of the fault are skipped This bit is used when retrieving faults with the Read_DP_Slave_Diagnostics_Information service see appendix A for more information If there is no next fault the NIU clears the NIU status data 2 6 Reserved always 0 0 Oor1 Clear all faults command Setting this bit to 1 clears the NIU s internal fault table The NIU s FAULT LED goes OFF unless a new fault is immediately logged or an existing fault condition continues to exist This command can be sent at any time Byte 2 z ls s 4 ls 2 j o Reserved always 0 GFK 1533 Chapter 3 The DeviceNet Network Interface Unit 3 11 Chapter The DeviceNet Network Control Module 4 The DeviceNet Network Control Module IC200BEM103 interfaces a VersaMax PLC CPU to a DeviceNet network The NCM operates as a Group 2 Only Client master and can communicate only with Group 2 Slave devices It can also operate as a Group 2 Only or a UCMM capable Server Slave or as a master and slave simultaneously When configured as a
50. uction l This manual describes the installation and operation of the VersaMax DeviceNet Communications modules Chapter 1 is a basic introduction Module and cable Installation procedures are described in Chapter 2 The DeviceNet Network Interface Unit is described in chapter 3 This chapter explains how the NIU is configured and how it operates The DeviceNet Network Control Module is described in chapter 4 This chapter explains how the NCM is configured and how it operates The NIU Statement of Compliance is shown in appendix A The NCM Statement of Compliance is shown in appendix B The NIU Electronic Datasheet EDS File is detailed in appendix C The NCM EDS File is detailed in appendix D Other VersaMax Manuals VersaMax Modules Power Supplies and Describes the many VersaMax I O and Carriers User s Manual catalog number option modules power supplies and GFK 1504 carriers This manual also provides detailed system installation instructions VersaMax Profibus Communications Describes the installation and operation of Modules User s Manual catalog number the Profibus communications modules GFK 1534 VersaMax Genius NIU User s Manual Describes the installation and operation of catalog number GFK 1535 the Genius NIU VersaMax PLC User s Manual catalog Describes the installation and operation of number GFK 1503 the VersaMax CPU GFK 1533 1 1 DeviceNet DeviceNet supports a variety of commu
51. ut the communications status of the devices on the network followed by bit type discrete and word type analog data from the devices on the network The bit type and word type data appears in the order specified by the list of slave devices in the Configuration COMREQ If the NCM is a slave itself its bit type and word type data appears first in the respective areas All of the bit type input data specified for the slaves is combined together in the I table and all of the word type input data is combined together in the AI table The maximum total amount of input data for the NCM is 512 bytes First byte Last byte 4 Status Data Bit type Input Data from Network Word type Input Data from Network To CPU lt bytes gt lt q Discrete Input Area l table lt q Analog Input Area AI table t _ Maximum Total Inputs Length 512 bytes GFK 1533 Chapter 4 The DeviceNet Network Control Module 4 9 4 10 Communications Status Data Format The first 8 bytes 64 bits of the NCM input data contain the communications status of each of the 64 node addresses By looking at this data first the application program in the PLC can determine the validity of each device s input data Byte 0 Node addresses 0 7 MSB LSB Byte 1 Node addresses 8 15 MSB Byte 2 Node addresses 16 23 Fei Es ld Geld Byte 3 Node addresses 24 31 Byte 4 Node addresses 32 39 Byte 5 Node addresses 40 47 Byte
52. ved a valid configuration from the CPU Blinking amber means the NCM has failed powerup diagnostics The number of blinks indicates the fault type OFF when the NCM is not powered blinks green if the NCM configuration is missing incomplete or incorrect The NCM may be in Standby state green when the NCM is operating normally blinks red if there is a recoverable fault red if there is an unrecoverable fault The NCM may need replacing blinks red and green during NCM self test OFF when the NOM is not online or not powered blinks red and green if the NCM detects a Network Access error and is in the Communications Faulted state blinks green if the NCM is online but has no connections in the established state It has no established connections to other nodes green when the NCM us inline and has connections in the established state blinks red if one or more I O Connections are in the Timed Out state red if an error renders the NCM incapable of communicating on the network 2 7 Installing the DeviceNet Cable 2 8 A DeviceNet network uses 5 wire multi conductor copper cable Two wires form a twisted pair transmission line for network communications A second pair transmits network power The fifth conductor forms an electromagnetic shield Cabling is available in a variety of current carrying capacities On a DeviceNet fieldbus every device must at least power its network transceivers from the network power
Download Pdf Manuals
Related Search