Home

DeviceNet Module - GE Intelligent Platforms: Support Home

1. DeviceNet PLC network Explicit RX3i Series 90 30 Message DeviceNet Master or eae Series 90 30 DeviceNet Slave Module Figure 72 Client Explicit Messages Transaction Objects that Do Not Require PLC Application Programming Some client explicit messages are serviced directly by the DeviceNet module and do not require PLC application program interaction The objects defined in the module firmware and reserved that do respond automatically are Identity Object 0x01 Message Router Object 0x02 DeviceNet Object 0x03 Assembly Object 0x04 Connection Object 0x05 PLC Data Object 0x64 You do not need COMMREQ commands to reply to services associated with these objects the reply is generated by the DeviceNet module For many applications client messages to the automatic message objects will achieve the application goal For example the PLC Data Object allows a device like a personal computer or another PLC to read or write an array of PLC data memory where the DeviceNet module is installed This could be used to send a recipe to PLC R memory or to retrieve an array of status data on demand With a minimum of PLC programming to unpack or pack data within a single PLC data type it is manageable to generate almost any data structure needed and access it as needed from the client Making use of the automatic responses typically simplifies the PLC application program It should be considered as a first opti
2. 0x00 Idle Group 2 master slave connection is not allocated the o0 siae sener E not acive romusterescomeg n 0x01 Active Group 2 master slave connection allocated the slave PrP _ fenersocive ands beng scanned py o master devel Bits indicating the various connection states in this example the module s output land 2 connections are both configured for receive idle and it has an UCMM connection 4 11100000 _ EO Reserved these bits should be ignored 1 Output connection 1 receive idle condition 1 Output connection 2 receive idle condition 1 Group 3 UCMM connection s allocated o foo a these bits should be ignored Bits ne explicit message status since the last Get Detailed Server Status These bits are a byte automatically cleared by this COMMREQ in preparation for the next call For this example the module has sent the explicit message response on the network 00001 0001 bitO 1 Explicit response sent Set when the scanner has submitted the explicit response from a Send Server Explicit message for transmission on the network bits 1 7 Reserved Bits showing the configured features of the module For this example the DeviceNet module aah byte slave server is set up for explicit messaging and polled I O operation 00000011 03 bit O 1 Explicit connection allocated This bit is always on regardless of whether the explicit messaging is turned on or off ott bit 1 Polled 1 Polled 1 0 connection all
3. Chapter 6 Programmed Communications 6 11 Command Codes 3 amp 8 Replying to a DeviceNet Explicit Message After retrieving a DeviceNet explicit message from a DeviceNet Slave Module or Master Module in slave mode the application program can respond to the network master using COMMREQ 3 Send Server Explicit If the content of the response is more than 238 explicit data bytes use COMMREQ 8 Send Server Explicit Extended instead RX3i Series 90 30 DeviceNet Master or Series 90 30 DeviceNet and Extended PLC CPU PLC Slave Module Backplane A 2 ee No Ti DeviceNet EO pinen IN network i l Receive Server Ai Explicit gt Queue of Application i SSS ff ree Client Program P a 2a i from Explicit Messages 1 lt Reply i Clients on AN a Network Bend Server Explicit 1 1 Figure 74 Send Server Explicit Transaction The difference between Send Server Explicit and Send Server Explicit Extended is how they store the data that will be sent in PLC memory For Send Server Explicit the data to be sent is located in the same memory area as the COMMREQ command block Series 90 30 PLC or PACSystems RX3i Controller COMMREQ Command Block Data to be Sent Figure 75 Send Server Explicit Transaction Showing Memory Usage DeviceNet network Send Server Explicit Client DeviceNet Explicit Module Message For Send Serv
4. For details on the effects of different types of faults on Series 90 30 PLC behavior refer to the Series 90 30 CPU Reference Manual GFK 0467 For PACSystems RX3i fault information refer to the PACSystems CPU Reference Manual GFK 2222 5 3 1 Faults Reported to the I O Fault Table The I O Fault Table will list the following DeviceNet module faults Loss of Device This indicates a DeviceNet fault on a configured slave For example if the master detects a slave timeout and there is not a Loss of Network the master logs a Loss of Device fault when the device bit in the Slave Status Table transitions from 1 to 0 Addition of Device This indicates that a device bit in the Slave Status Table has gone from 0 to 1 indicating that a slave device is active in the DeviceNet scan list Headend Fault A headend fault affects the operation of the DeviceNet module or the network Configuration errors initialization errors and bus faults are some possible headend faults Because of the nature of these faults some are not reported to the fault table However the PLC application program can detect many types of errors by monitoring the module s three status words If a fault is detected the program may be able to get more information about the fault by sending a Read Module Header COMMREQ to the module See chapter 5 Programmed Communications for more information GFK 2196B October 2014 57 Chapter 5 Module Operation 5 4 PLC Status
5. 28 DeviceNet Modules for PACSystems RX3i and Series 90 30 User s Manual GFK 2196B Chapter 3 PLC Configuration for the DeviceNet Master 3 5 2 Configuring I O Messaging Connections for Slaves added to the Master I O Messaging is the term used for the routine and automatic exchange of data between the master and slaves in a DeviceNet system Each configured I O Message defines a dedicated communication path between a producing device and one or more consuming devices Once these connections have been established I O Messaging communications occur automatically during system operation Each Series 90 30 device in a DeviceNet system can be set up for up to two different I O Messaging connections Each connection can be disabled the default or set up for Polled Strobed Change of State or Cyclic operation Connections should be configured to meet the needs of the application For example the master might Strobe all the input only slave devices and Poll the remaining slave devices The selection made for one I O Messaging connection to a slave determines which connection types remain available for the same slave s other I O Messaging connection as shown by the table below For example you can only select one polling connection for a device Selected for One Available for the Other Connection Connection Disabled Disabled polled strobe cos cyclic Polled Disabled strobed cos cyclic Strobed Disabled pol
6. Connection ID required for request response matching From the command 2 COMMREQ used to service this client reply Size Number of service data bytes Service DeviceNet service code Service Data Offset The number of bytes between this word and the beginning of the service data to be sent If the offset is O the service data is located immediately after this data word at word 12 see below For example if the offset were 2 then two bytes would be skipped and the data would begin at word 13 Skipped optional Service Data Byte 0 Attribute GFK 2196B October 2014 95 Chapter 6 Programmed Communications Command Code 8 Send Server Explicit Extended COMMREQ Command Length Always 4 words for command 8 Always 0 no wait mode request Status segment select Memory type of COMMREQ status word R for this example 8 R 10 Al 12 AQ 16 1 18 Q 20 T 22 Status memory offset COMMREQ status word address minus 1 R10 for this example fo idteeves OS Command Code Send Server Explicit Extended 8 Data segment select Memory type for the data to be sent 8 R 10 AI 12 AQ 16 I 18 Q 20 T 22 M Data memory offset Offset within the memory type for the data to be sent Word offset for memory types 8 10 12 byte offset for memory types 16 18 20 22 Data memory size Size data block to send in words for memory types 8 10 12 in bytes for memory types 16 18 20 22
7. Finally RX3i users should not let the CPU s sweep time approach a length of 1000ms Detecting Bus Off Errors If a DeviceNet bus off failure occurs the module is not able to communicate on the network The CAN Status portion of the module s status data shown in this chapter indicates that a bus off condition has occurred For a DeviceNet Master Module after the internal connection timeouts expire the status of each node indicates that the device is no longer active The application can monitor both the CAN Status word and the Slave Status bits to check for bus off conditions and loss of slaves Fatal Errors If a DeviceNet Module has a fatal error it takes the following actions if possible It sets its Module Status LED to solid RED and its Network Status LED to OFF It informs the PLC CPU It stops any current network activity The module tries to maintain communications with the PLC CPU and to respond if it receives COMMREQ 9 Read Module Header In addition the module starts continuously sending the Module Header information to its RS 232 serial port using the following communications parameters 19200 baud 8N1 8 data bits no parity 1 stop bit The entire Module Header in ASCII hex codes The message field of the Module Header in readable form GFK 2196B October 2014 55 Chapter 5 Module Operation 5 2 Operation of a Slave Server DeviceNet Module A DeviceNet Slave Module operates as a server slave
8. Module Type Contains DN Ox4E44 or ER 0x4552 if a fatal error is detected Window size Indicates host interface window size 0 16K 1 32K 2 64K 3 128K 1 4 5 7 9 Kernel revision 5 Kernel identification 0x0001 CAN 2 0A kernel 7 Module ID 0x0017 DeviceNet module Module revision in binary coded decimal BCD 4 hex digits Xx Xx ie rev 1 0 0x0100 rev 1 10 0x0110 10 DeviceNet serial number 11 18 Card type IC693DNM200 or IC693DNS201 19 22 Module serial number i e 9409001 5 6 23 24 25 Main Application Error Code See the error code listings on the following pages 2 CAN Network Status word Mmt Ro fo O fa fa feo few fo OEO sa fos foz fjor re Be J Application Specific Flags SA Scanner Active at least one connection established 05 Online at 500 Kbaud 02 Online at 250 Kbaud 01 Online at 125 Kbaud RE Firmware is performing DeviceNet reset I O data is not valid Common Flags Bus power present zero if power sense not supported CAN communication error Message lost CAN controller receive ISR Receive buffer overrun host app too slow emptying receive queue Transmit failed due to timeout flooded network Transmit failed due to ack error no other nodes connected Network activity detected messages received or transmitted Bus off this node has been disconnected due to excessive errors Bus warning this node is experiencing a large number of errors Onli
9. Must be large enough to specify the entire explicit data block defined below In bytes the size needed is Number of Service Data bytes 8 Service Data Byte offset Unit conversions are required for non byte units Send Server Explicit Extended Data Format The following data format must be written to the PLC memory location specified in the command Description Connection ID The server connection ID is required for request response matching From the command 2 used to initiate service to this request Service Data Size Number of service data bytes Service Code DeviceNet service code 4 Service data byte Offset The number of bytes between this word and the beginning of the service data to be sent If the offset is 0 the service data is located immediately after this data word at word 7 see below For example if the offset were 2 then two bytes would be skipped and the data would begin at word 8 Skipped optional Service Data byte 0 Attribute Service Data 96 DeviceNet Modules for PACSystems RX3i and Series 90 30 User s Manual GFK 2196B Chapter7 DeviceNet Objects This chapter describes the DeviceNet Objects that are defined for the DeviceNet Master Module and the DeviceNet Slave Module These modules use the following types of Objects in DeviceNet information exchanges Identity Object Message Router Object DeviceNet Object Assembly Objects Connection Object PLC
10. Slave ID 1 Properties General Connection 1 Connection 2 Explicit Messages I Explicit Message Size 20 bytes coc Hee Figure 33 Explicit Messaging Screen for a Slave on the Network 34 DeviceNet Modules for PACSystems RX3i and Series 90 30 User s Manual GFK 2196B Chapter 3 PLC Configuration for the DeviceNet Master 3 6 Configuring Network Settings for a DeviceNet Master Acting as a Slave The Network Settings include MAC IDs baud rates and the messaging connections between devices on the network This was described previously in the section Configuring Network Settings for Slaves Added to the Master 3 6 1 Configuring I O Messaging Connections for a DeviceNet Master Acting as a Slave I O Messaging is the term used for the routine and automatic exchange of data between the master and slaves in a DeviceNet system Each configured I O Message defines a dedicated communication path between a producing device and one or more consuming devices Once these connections have been established 1 0 Messaging communications occur automatically during system operation Each Series 90 30 device in a DeviceNet system can be set up for up to two different I O Messaging connections Each connection can be disabled the default or set up for Polled Strobed Change of State or Cyclic operation Connections should be configured to meet the needs of the application For example the master might Strobe all the input onl
11. 0x0000 0x0000 Zero in Main Code indicates no error Config File 0x0001 Unknown Version 0x0001 Incorrect unsupported version Error Init File 0x0002 0x0001 _ Incorrect unsupported version Error Unknown Header Id 0x0002 Init file s header ID not recognized or invalid Unknown Block Type 0x0004 Block type not recognized nvalid Block Definition 0x0003 Block s definition count is invalid Count nvalid Shared Memory 0x0006 Shared memory offset not in the 0x1000 to Offset Ox3FFF range nvalid Mac Id 0x0008 Mac Id in the Data Pointer list not in the range of nee PO cea neuete oresse Type nvalid Block Checksum 0x0005 Block s checksum is invalid nvalid Block Size Ox000A Size of block in INIT file did not match what was expected or larger than the maximum size supported by the firmware maximum INIT file size INIT file Missing Block OxO00E One or more of required blocks 1 3 and 4 are missing from the INIT file Add 0x0003 Duplicate Device 0x0005 Device already in scan list Data Pointer Out Of Range 0x000D Data pointer refers to a location outside of shared memory Error nvalid Connection Flags OxOOOF The combination of bits in the Flags field is invalid nvalid Explicit Buffer Size 0x0010 Explicit buffer size is invalid Device nvalid Shared Memory 0x000D Shared memory offset not in the 0x1000 to Offset Ox3FFF range nvalid Strobe Buffer Size 0x0011 Strobe buffer size is invalid Note that the output size
12. 10893CHS392 fil Rack 5 C693CHS392 ffi Rack 6 IC693CHS392 Figure 20 Network Settings Dialog Box The General tab allows setting a name and description for the module On this tab you can also select the MACID Baud Rate Scan Interval and Reconnect Time These parameters are also found on the Configuration Parameter screen they can be set in either place The rest of the tabs are only used if the DeviceNet Master Module will operate as a server slave to another master on the network If the DeviceNet Master is not a slave to another DeviceNet master these three tabs should be left blank 26 DeviceNet Modules for PACSystems RX3i and Series 90 30 User s Manual GFK 2196B Chapter 3 PLC Configuration for the DeviceNet Master 3 4 Adding Slaves to the Network After adding the DeviceNet Master Module to the PLC rack you need to tell the Master about the required communication to the slave devices on the DeviceNet network by adding slaves to the Master There are two ways to add a slave to the network configuration xl Inthe Navigator window right click the IC693DNM200 rus Master Module and choose Add Slave EEA DeviceNet System Ei Targett a Data Watch Lists fin Hardware Configuration 5 Main Rack IC693CHS391 Gl PWR IC693PWR321 l Slot 1 IC693CPU364 Slot 2 IC693DNS201 Configure Enter Slot 4 ES Slot 50 Cut Ctx a g g D Ssg fEng ie ase
13. Allocate reply size at least 10 bytes for reply words 1 5 larger than the service data DeviceNet service code internal result code Values less than OxFF The service code low byte in explicit message replies contains the same service that is returned on the DeviceNet network Since the message is in reply to the explicit service issued by the COMMREQ the high bit of the low byte is set to a 1 For example GET_ATTRIBUTE_SINGLE is service code 0x0E The DeviceNet response will have the high bit set Ox8E SET_ATTRIBUTE_SINGLE is service code 0x10 With the high bit set on response 0x90 DeviceNet errors use service code 0x14 and since errors are responses the high bit will be set 0x94 For example GET_ATTRIBUTE_SINGLE Ox0E DeviceNet error response 0x94 With following bytes of main code and additional code Error Value Reserved 0x12 0x02 Resource needed for the object to 0x13 The service did not supply enough perform the requested service not data to perform the requested service available supported 0x08 Requested service not implemented 0x15 The service supplied more data than or not defined for the object was expected class instance invalid attribute data detected 0x16 the device Reserved 0x17 Object is already in requested mode 0x18 or state requested by the service stored prior to the requested service Object cannot perform the 0x19 Attribute data of this object not saved requested service in its current by the object
14. Fur Rau ot TnfoViewer 0 2 ICB990N Field is read only Figure 16 Setting Parameters for DeviceNet Module 3 3 1 Parameters of a DeviceNet Master Module Settings tab Mac ID The Mac ID medium access control identification of the master on the DeviceNet network Valid range 0 63 Default 0 Slave Status Bit Array Address The starting address for an array of bits indicating the health of each node on the DeviceNet network It must be a non overlapping range in Al l Q G AQ R WT or M It defaults to I memory and uses the next available l address A slave s status address equals Start Address Station Address of the slave For example if the status bits are mapped to 100001 the status for the slave at Station Address 5 would be found at 100001 5 100006 The master s status is located in the same way as the slaves Start Address Station Address The master is configured as station 0 by default but can be set to any valid address 0 64 Length of slave status bits Read only Length has a value of 64 corresponding to 64 network devices Network Status Firmware ID Address The starting address for three words of module network status information The default is Al memory and uses the next available Al address The Network Status Firmware ID Address must be a non overlapping range in Al l Q G HAO R T or M During system operati
15. Memory type of COMMREQ status word R for this example 8 R 10 Al 12 AQ 16 1 18 Q 20 T 22 M 4 00009 0009 Status memory offset COMMREQ status words address minus 1 R10 for this example 16 oo000 looo0 Reseved o e 00005 0005 Command code Get Detailed Server Status command 5 00008 0008 Reply segment select Memory type for the reply data R for this example 8 R 10 Al 12 AQ 16 1 18 Q 20 T 22 M Pi OOFA Reply memory offset Offset within the memory type for the reply minus 1 For this example it is R251 i 0009 Reply memory size Maximum size for the reply in words for memory types 8 10 12 in bytes for memory types 16 18 20 22 Maximum 2048 bytes Note For command 5 must be 18 bytes 9 words or more or an error is returned in the COMMREQ status and the command is ignored 78 DeviceNet Modules for PACSystems RX3i and Series 90 30 User s Manual GFK 2196B Chapter 6 Programmed Communications Get Detailed Server Status Reply Data Format The response to a Get Detailed Server Status COMMREQ supplies details of the module s configured Network Settings It also shows whether the module has sent on the DeviceNet network a previously commanded Send Server Explicit M ae Command number that this data block is replying to 5 t oa 01 Indicates whether the module is set up for slave ee Network a byte Settings ee For this example the module is being scanned
16. Module Operation CAN Network Status m fro o a j fo Application Specific Flags Scanner Active at least one connection established Online at 500 Kbaud Online at 250 Kbaud Online at 125 Kbaud Firmware is resetting so DeviceNet I O data is not valid Common Flags Bus power present zero if power sense not supported CAN communication error Message lost CAN controller receive ISR Receive buffer overrun host app too slow emptying receive queue Transmit failed due to timeout flooded network Transmit failed due to ack error no other nodes connected Network activity detected messages received or transmitted Bus off this node has been disconnected due to excessive errors Bus warning this node is experiencing a large number of errors OL Online CAN interface has been initialized Firmware ID Minor revision In BCD four hex digits For example revision 1 10 01 10 hex Firmware ID Major revision See above GFK 2196B October 2014 59 Chapter 5 Module Operation 5 5 Device Status Bits for the DeviceNet Master Module In addition to maintaining the three status words described previously a DeviceNet Master Module maintains 64 device status bits in PLC memory There is one bit for each potential device on the network The memory type and starting offset of this status area in memory are configurable An individual device s status bit location equals the configured Start Address plus the Station A
17. Response Query Slave 2 Response DeviceNet network Query Slave n Response Figure 34 DeviceNet Polled 1 0 Sequence To configure polling for slave connection 1 or connection 2 select Polled on the Slave Properties menu General Connection 1 Connection 2 Explicit Messages C Disabled m Input Resources Polled Size fo bytes C Strobed C cos C Cyclic m Output Resources Update Interval fo ms Size fo bytes ok caret Hep Figure 35 Polled I O Messaging Screen for a DeviceNet Master Module For input resources specify the number of data bytes the slave will send to the master For output resources enter the number of bytes the slave will consume from the master For Update specify the interval in milliseconds at which the DeviceNet master will update data for this device To select the fastest update rate possible enter zero Note The number of bytes for input and output must match between this setup and the setup of the Slave Device or the Master will be unable to communicate with the slave 36 DeviceNet Modules for PACSystems RX3i and Series 90 30 User s Manual GFK 2196B Chapter 3 PLC Configuration for the DeviceNet Master Configuring a Strobed I O Messaging Connection In Strobed I O mode the master produces a single Strobe request message that is consumed by all devices with a connection configured for strobing reques
18. Slave 1 lt Response Slave 2 DeviceNet network lt Response Slave n Figure 26 DeviceNet Strobed 1 0 Sequence Strobed I O Messaging can be more efficient than Polled I O messaging because the master does not send an individual Poll request to each device Strobed I O Messaging is particularly useful for slave devices that have input data only such as sensors To configure Strobed I O Messaging for a slave connection select Strobed on the Slave Properties menu Mac ID 1 DeviceNet NCM Slave ID 1 Properties General Connection 1 Connection 2 Explicit Messages e Disabled E Input SA Ee FE a naa eee A ea C Bolled Size fo bytes Btobed C cos Connection Custom fiche i lena SES aan i Output Size fi bytes Connection Custom z coc e Figure 27 Strobed I O Messaging Screen for a Slave on the Network For input resources specify the number of data bytes the device will send to the master The length for output resources is automatically set to 1 byte The message from the Master to the Slave telling them to send back their inputs is a 1 byte message It reflects the state of the I O bit in the strobe request message for the device set 1 or clear 0 GFK 2196B October 2014 31 Chapter 3 PLC Configuration for the DeviceNet Master Configuring a Change of State COS I O Messaging Connection A connection configured for Chang
19. device Unlike Polled messaging Cyclic messaging can use a different interval as configured for each slave DeviceNet Query gt Master Response Slave 1 Slave 2 DeviceNet network Query Response Query gt Slave n K Response Figure 59 DeviceNet Cyclic I O Sequence A Cyclic I O connection can be used as a heartbeat to provide assurance of a device s continued operation with a Change of State I O connection to the same device used to update its I O state To configure Cyclic I O Messaging for a connection select Cyclic on the Slave Properties menu General Connection 1 Connection 2 Explicit Messages Deed m Input Resources Polled Size 0 bytes C Strobed cos Epig a M Output Resources Size fo bytes I Ack Suppress cae eee Figure 60 Cyclic 1 0 Messaging Screen for a DeviceNet Slave Module For input resources specify the number of data bytes the module will send to the master For output resources enter the number of bytes the module will consume from the master If Acknowledge Suppress flag is selected the DeviceNet master does not wait for an acknowledge message from the module GFK 2196B October 2014 51 Chapter 4 PLC Configuration for the DeviceNet Slave 4 4 2 Configuring DeviceNet Explicit Messaging Explicit Messaging is the highest priorit
20. 62 Send Zeroed Data 54 SERA bit 91 Serial cable 17 Server operation 56 Server status 58 Slave Status Bit address 22 Slave Status Fault Table entries 45 Specifications environment 4 6 power consumption 6 slave module 6 Start Scan errors 72 Status Address 45 Status bits for network devices 60 Status Word codes 67 Status words 58 Strobed I O mode 31 37 49 T Table of Contents v Table of Figures ix Taps 13 Technical Support See page iii Terminating the bus 12 Tick Interval 71 Transmit Idle 54 U UCMM 3 5 V VersaPro 4 6 110 DeviceNet Modules for PACSystems RX3i and Series 90 30 User s Manual GFK 2196B Index W Window size 70 GFK 2196B October 2014 111 GE Intelligent Platforms Additional Resources Information Centers For more information please visit Headquarters the GE Intelligent Platforms web site 1 800 433 2682 or 1 434 978 5100 www ge ip com Global regional phone numbers are available on our web site www ge ip com Copyright 2002 2014 General Electric Company All Rights Reserved Trademark of General Electric Company All other brands or names are property of their respective holders GFK 2196B
21. DeviceNet Modules for PACSystems RX3i and Series 90 30 User s Manual GFK 2196B Chapter 6 Programmed Communications 10 00006 0006 Reply Memory Size Maximum size required to hold the reply to the command in words for memory types 8 10 12 in bytes for memory types 16 18 20 22 For command 1 the size must be 10 bytes 5 words or more or an error will be reported in the COMMREQ status word and the request will be ignored Note The size needed for the reply depends on the service used and the instance accessed Consult the server device documentation Add 10 bytes 5 words to the server reply data for the reply header The reply memory size can be larger than the reply data of a particular message it must not be smaller VersaPoint Network Interface Unit uses MAC ID 4 12 00002 0002 Service Data Size Number of Service Data bytes being sent This needs to be determined from the documentation of the DeviceNet server to which the message is being sent For the example 2 bytes 1 attribute byte 1 bytes data Note For service codes 0x10 or OxOE the attribute byte is contained in the service data at byte zero 13 00016 0010 DeviceNet service code See the vendor documentation for the server device In this example the Service Code for the VersaPoint DeviceNet NIU is 0x10 Set Attribute Single Service to write data Another service code often used is Ox0E Get Attribute Single Service to read data 00010 000A C
22. Figure 13 Configuring Network Settings at the DeviceNet Master 20 DeviceNet Modules for PACSystems RX3i and Series 90 30 User s Manual GFK 2196B Chapter 3 PLC Configuration for the DeviceNet Master 3 2 Adding a DeviceNet Master Module to the PLC Configuration First add the DeviceNet Master Module to the PLC rack configuration The Master and Slave Modules are compatible with any Series 90 30 CPU except IC693CPU321 or IC693CPU340 They require release 8 0 CPU firmware as a minimum Release 10 6 or later is recommended if available for your particular CPU The Master Module is compatible with PACSystems RX3i CPU firmware version 3 50 or later 1 In that configuration in the Project tab of the Navigator expand the Hardware Configuration folder 2 Inthe Hardware Configuration folder right click the intended PLC Slot for the DeviceNet Master Module In an RX3i system it can be slot 2 or higher in the main rack only In a Series 90 30 system the module can be in slot 2 or higher in the main rack only Note DeviceNet Master modules cannot be installed in remote or expansion racks 3 Select Add Module from the shortcut menu EDs E F DeviceNet System Targeti 6 C Blocks amp Data Watch Lists fip Hardware Configuration f Main Rack 1C693CHS391 a PWR IC693PWR321 Hardware Slot 1 IC693CPU364 Configuration Folder Slot 7 eonngure a Slot ey Navigator Window Slot Copy Slot
23. Location for DeviceNet SIAVE sssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssessssssssessssssnsasssssses aaa Figure 45 Configure Network Settings for DeviceNet SIOVE sssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssnssssssssssanssssss Figure 46 Add Module to Slot LOCOUON cxzzczess2 c 2cses22sse22220s22224000224002224202222022220222082022228040666666646444646446482eeceeedcceccccccscscsssssssssssssssssssscauaaatiattistitele Figure 47 Select DeviceNet Slave Module from LISt sssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssasssssssssssnsssssatiaauuasnnsnssssnssssss Figure 48 Configuring Parameters for DeviceNet Slave sssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssst saunas Figure 49 Data Area Tab for DeviceNet Slave MO QU sec eeccccCeccccccsccccssccscccccsscsscscccccccccccccccccscccccccecccccccccccccccccccccceeccccccecceesee oessseassdboeosee Figure 50 Power Consumption Tab for DeviceNet Slave Module ssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssnssssnssses Figure 51 Configure Network Settings for DeviceNet SlOVE ssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssnsssssnsssssssssssnssaanssisss Figure 52 DeviceNet Polled 1 0 Mode Sequence omisi Figure 53 Polled I O Messaging Screen for a DeviceNet Slave Module Figu
24. Programmed Communications 6 4 1 Read Module Header COMMREQ Example This example COMMREQ does the following Gets the Module Header Data Returns the COMMREQ Status Words to R10 R13 Returns the Device Status to R251 R283 fe 00004 0004 Length of command Block Always 8 bytes 4 words for command 9 i 00000 0000 Always 0 no wait mode request 00008 0008 Status segment select Memory type for COMMREQ status words R for this example 8 R 10 Al 12 AQ 16 1 18 Q 20 T 22 M 4 00009 0009 Status memory offset status words starting address minus 1 R10 for this example 00009 0009 Command Code Read Module Header command 9 00008 0008 Reply segment select Memory type for the reply data R for this example 8 R 10 Al 12 AQ 16 1 18 Q 20 T 22 M 00250 OOFA Reply memory offset Offset within the memory type for the response minus 1 R251 for this example 10 00065 0041 Reply memory size Maximum size for the reply in words for memory types 8 10 12 in bytes for memory types 16 18 20 22 Maximum 2048 bytes Note For command 9 must be 130 bytes 65 words or more or an error will be returned in the COMMREQ status and the command will be ignored GFK 2196B October 2014 69 Chapter 6 Programmed Communications 6 4 2 Read Module Header Reply Data Format 11 Command Code Echo of Command Code that this data block is replying to 0x0009 2
25. Slot meas Add Module Replace todale Delete Modale Figure 14 Adding Module to a Slot Location in PME The Module Catalog dialog box appears 4 To add a DeviceNet Master Module click on the Bus Controller tab The Bus Controller module list appears Select IC693DNM200 DeviceNet Master from the list and click OK Intelligent Option Discrete Input Discrete Output Discrete Mixed Analog Input 3rd Party Analog Output Analog Mixed Communications Bus Controller Motion IC693PBM200 Profibus Master xl HE693PBM100 Homer Electric Profibus Master HE693PBM101 Homer Electric Profibus Master PTO Certified HE693PBM101F Horner Electric Profibus Master w 125 Xtra Param Data ICB93BEM321 90 30 1 0 Link Master IC693BEM331 90 30 Genius Bus Controller IC693DNM200 DeviceNet Master Figure 15 Selecting the DeviceNet Module as Item to be Added GFK 2196B October 2014 21 Chapter 3 PLC Configuration for the DeviceNet Master 3 3 Configuring the Parameters of a DeviceNet Master Module The DeviceNet Master Module is added to the PLC configuration in the Navigator window and the module s Parameter Editor window appears in the InfoViewer window space DeviceNet System CIMPLICITY Machine Edition 0 2 IC693DNM200 P Ele Edt Search Project Target Vajables Parameter Tools Window Help lgj x a geovede p me ocxe mameeers ier onda AE YEO FAT Se o
26. Status memory offset COMMREQ status words start address minus 1 R10 for this example je 00000 loo00 Reseved o 7 00006 0006 Command code Get Status Info command number 6 roe eae Reply segment select Memory type for the reply data R for this example 8 ee lee 10 Al 12 AQ 16 1 18 Q 20 T 22 M ae OOFA Reply memory offset Offset within the memory type for the reply 0 based For this example it is R251 Word offset for memory types 8 10 12 byte offset for memory types 16 18 20 22 ain 0008 Reply memory size Maximum size for the reply in words for memory types 8 10 12 in bytes for memory types 16 18 20 22 Maximum 2048 bytes Note For command 6 must be16 bytes 8 words or more or an error will be returned in the COMMREQ status and the command will be ignored 80 DeviceNet Modules for PACSystems RX3i and Series 90 30 User s Manual GFK 2196B Chapter 6 Programmed Communications Get Status Information Reply Data Format GFK 2196B Command code that this data block is replying to 6 Device Status Each bit corresponds to an individual device MAC ID The state of that bit indicates the device s status 0 Device is not active not configured faulted etc 1 Device is active being scanned For the master s own MAC ID the status bit is always 0 bit bite bits bit bits bit2 we r dJe eo a ee 10 18 26 34 50 loyte7 es ee fo 6o s Serve
27. a change of status The master then sends an output message to the module and the module responds with its input data DeviceNet DeviceNet Master Slave 1 Master Slave 1 Change of State Message x x fe o 2 l Slave 2 2 Inputs Slave 2 oO oO Cc 3 3 e e Slave n Slave n Figure 56 Device Produces Change of State Message Figure 57 Master Sends Outputs Device Replies To configure Change of State I O Messaging for a connection select COS on the Connection tab menu Figure 58 COS I O Messaging Screen for a DeviceNet Slave Module For input resources specify the number of data bytes the module will send to the master For output resources enter the number of bytes the module will consume from the master If Acknowledge Suppress is selected the master will not wait for an acknowledge message from the module 50 DeviceNet Modules for PACSystems RX3i and Series 90 30 User s Manual GFK 2196B Chapter 4 PLC Configuration for the DeviceNet Slave Configuring a Cyclic I O Messaging Connection In Cyclic I O Messaging as in Polled I O Messaging the DeviceNet master automatically sends a message containing outputs to a device connection configured for Cyclic update The module sends back a response containing input data Like Polling Cyclic I O Messaging requires 2 messages to update the O data for a
28. about slaves by adding the network slaves to the Master and configuring their network settings Figure 12 Configuring DeviceNet Slaves Associated with the Master The number and type of slave devices and the amount of data they can exchange with the master may be limited by the CPU memory available The amount of CPU memory available for the DeviceNet configuration depends on the CPU model being used the version of the CPU firmware the number and type of other modules in the configuration the number and type of slave devices configured and the amount and type of communication in progress with an external programmer or HMI devices With Logic Developer PLC the size of the current configuration can be read by selecting Data View for the hardware configuration and adding the sizes of the components listed LD PLC will not allow configurations to be created that exceed 65 535 bytes The size of the DeviceNet configuration is also limited by the size of the user configuration space for the models listed below CPU 311 313 4 736 bytes available CPU 331 4 673 bytes available Optional Configuring the network settings of the DeviceNet Master Module itself This is ONLY done if the DeviceNet Master Module will also operate as a server to another network master For example it might exchange data relating to the operation of its slaves with a higher level host controller hodda
29. amp Descriptions Series 90 30 only This setting determines whether or not names and descriptions that have been use in the configuration will be downloaded to the PLC when the configuration is downloaded By default this parameter is False and names and descriptions are not downloaded to the PLC This is the recommended choice because downloaded names and descriptions can take up too much memory in the PLC Names and descriptions are a convenience only Omitting them from the download does not affect system operation However if this parameter is set to False later uploads of the configuration from the PLC to the programmer will contain only default names and descriptions If this parameter is set to True names and descriptions that have been entered for the slaves and the master are downloaded to the PLC and will be present in the configuration if it is uploaded to the programmer later Names and descriptions are always downloaded to PACSystems RX3i GFK 2196B October 2014 23 Chapter 3 PLC Configuration for the DeviceNet Master Settings tab Download EDS Files Series 90 30 only This setting determines whether or not the EDS files that have been used for the configuration will be downloaded from the programmer to the PLC when the configuration is downloaded By default this parameter is False and EDS files are not downloaded to the PLC This is the recommended choice because downloaded EDS files can
30. consume too much memory in the PLC However when this is set to False if the configuration is later uploaded from the PLC back to the programmer it will not contain the EDS files You would need another source for the EDS files for example on disk to configure more modules of a given type If the EDS files are no longer available it is only possible to add more modules of that type as generic modules If this parameter is set to True the EDS files are included when the configuration is downloaded to the PLC If the configuration is later uploaded back to the programmer the EDS files will be restored to the Toolchest for use by the configuration EDS files are always downloaded and uploaded to a PACSystems RX3i 1 0 Scan Set PACSystems RX3i only The scan set as defined in the CPU s Scan Sets tab to be assigned to this module The default scan set is 1 The valid range is 1 through 32 Data Areas Tab This tab shows the PLC program references assigned to the DeviceNet Master Module s Network Settings when it is used as a slave This TAB is optional and should only be used when the DeviceNet Master Module is also a slave to another DeviceNet master device Note Do not enter values on this tab if the DeviceNet Master Module is not also used as a slave Entering values on this tab when the DeviceNet Master is not used as a slave causes the DeviceNet Master to fail to communicate with slaves E p M E fijip Ha
31. en a a OON 27 Figure 23 Configuring the MAC ID OF the SIV zeccccccccccccccccccccsssssssssssssssssssssssssssssssssesscssscssesecessccsccccsccccssccccccsccccssseees asssssaasssezsassnsssassaeesseeese 28 Figure 24 DeviceNet Polling SCQUENCE s sssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssasssssssssssssnseseseet anise 30 Figure 25 Polled I O Messaging Screen for a DeviceNet Slave in the DeviceNet Master Configuration 30 Figure 26 DeviceNet Strobed 1 0 Sequence n Figure 27 Strobed I O Messaging Screen for a Slave on the Network Figure 28 Device Produces Change of State MSSOGE suiii Figure 29 Master Sends Outputs Device REPIICS sssssssssssssssssssssssssssssssssssssssssssssssssssssssasssssassssssssssssssssssssassnsssssassssssssstsanausnissnnssssssnsssses Figure 30 COS I O Messaging Screen for a Slave On the NetWork csssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssse Figure 31 DeviceNet Cyclic I O Messaging SCQUENCE sssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssansssassssssasssasaaaananaasuasnssss Figure 32 Cyclic I O Messaging Screen for a Slave on the N tWork ccsssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssesssssse Figure 33 Explicit Messaging Screen for a Slave on the NEtWwOFK ccssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssessssesssssssss
32. failed An error occurred testing the CAN controller data bus Return the module for repair 8 CAN address test failed An error occurred testing the CAN controller address bus Return the module for repair 9 Invalid NVRAM data The module s non volatile memory contains invalid information Return the module for repair 10 Execution permission This module has not been configured to execute the application denied module Contact the vendor of the application module for assistance 11 Application initialization An error occurred initializing the application module Report this error condition to the vendor of the application module 12 Unknown application An error occurred initializing the application module Report this initialization code condition to the vendor of the application module 13 Application terminated The application module terminated abnormal condition Report this condition to the vendor of the application module 14 Application fatal error A fatal headend fault occurred Report this condition to the vendor of the application module 15 21 XXX interrupt An unexpected interrupt was detected This error should be reported to the vendor of the application module Make note of the circumstances that caused this error 22 Event queue overflow This error should be reported to the vendor of the application module 23 Nested user timer Make note of the circumstances that caused this error interrupt 74 DeviceNet Modules for PAC
33. for Service Data Byte Offset Service data to is limited to 238 bytes maximum for command 1 For the example Range 3 is the vendor code for the VersaPoint Analog Input 4 20ma setting and the data type is USINT 2 bytes Note It is important to know the type of the data to properly calculate the length setting of word 1 and word 12 of the COMMREQ 19 to end Service Data Additional service data as required by the message In the example this is unused space GFK 2196B October 2014 85 Chapter 6 Programmed Communications Send Device Explicit Extended COMMREQ Example The Send Device Explicit Extended COMMREQ command block contains a pointer to the data to be sent in the explicit message The programmer can use this functionality to point to different stored messages without recalculating command length each time Command 7 additionally avoids the 238 byte service data limit of command 1 by increasing the maximum size for the service data This command is only valid to a Master Module This example COMMREQ does the following Sends an explicit message to Mac ID 4 a GE Intelligent Platforms S2K DeviceNet Motion Controller Returns the COMMREQ Status Words to R10 R13 Sets writes an array of data 32 DINT variables to the S2K integer memory VI registers Word Value Description S O Heade Header Extended command Always 7 words 2 foo000 Awayso no walt mode request ee 00008 Status Memory Select Memory
34. ms 5 oe Connection Custom z i coo __ Figure 25 Polled 1 0 Messaging Screen for a DeviceNet Slave in the DeviceNet Master Configuration For input resources specify the number of data bytes the slave will send to the master For output resources enter the number of bytes the slave will consume from the master For Update specify the interval in milliseconds at which the DeviceNet master will update data for this device To select the fastest update rate possible enter zero Note The number of bytes for input and output must match between this setup and the setup of the slave device or the DeviceNet Master Module will be unable to communicate with the slave 30 DeviceNet Modules for PACSystems RX3i and Series 90 30 User s Manual GFK 2196B Chapter 3 PLC Configuration for the DeviceNet Master Configuring a Strobed I O Messaging Connection In Strobed I O mode the master produces a single Strobe request message that is consumed by all devices with a connection configured for strobing requesting their current status This occurs at the rate selected using the Scan Interval parameter of the DeviceNet Master Module Each strobed device then responds with its input data Devices respond in the order of their MAC IDs beginning with the lowest MAC ID first MAC IDs can be specifically assigned to prioritize I O reporting by the slaves DeviceNet Master Strobe Message Response
35. must be 1 nvalid Baud Rate 0x0003 Baud rate not set to 0 1 or 2 i e 125K 250K or 500k Duplicate Mac Id Failure 0x0004 DUP Macld check failed while attempting to go online Bus Not Offline 0x0009 Bus is already online Internal firmware error report to manufacturer Bus Off OxO00E Bus fault detected nvalid Path Buffer 0x0012 Path buffer is not initialized Online 0x0004 Invalid Mac Id 0x0002 Macld in the Server Config block is not in the Error range of 0 to 63 inclusive 72 DeviceNet Modules for PACSystems RX3i and Series 90 30 User s Manual GFK 2196B Chapter 6 Programmed Communications Category Main Additional BEF Invalid Connection Flags OXOOOF Combination of bits in the Flags field of the Server Config block is invalid size must be 1 Ack Fault 0x0013 No CAN acknowledge received during Duplicate Start Scan 0x0005 Bus is not online yet GFK 2196B October 2014 73 Chapter 6 Programmed Communications Fatal Error Codes in the Module Header If the module is capable of executing and reporting an error after a fatal error the Module Type field of the Module Header data contains the value ER 0x4552 All DeviceNet network activity if active stops Proper DeviceNet shutdown messages are not guaranteed The Module Status LED turns RED and the Network status LED goes off The entire Module Header in ACSI hex code and the message field of the Module Header in string form are cont
36. supplies The chassis of each power supply is connected to earth ground Power Supply 1 Power Supply 2 Return 24V Return 24V V CAN_H SHIELD o CAN_L l l V l e y XN NS l DN amma Figure 8 Grounding Example Ground Wire Size The minimum size ground conductor for the DeviceNet screw clamp terminals on a DeviceNet module is a 2 5mm 14 AWG wire For other network devices larger wire diameters may be necessary 14 DeviceNet Modules for PACSystems RX3i and Series 90 30 User s Manual GFK 2196B Chapter 2 Installation 2 4 Installing the DeviceNet Module in the PLC Rack In a PACSystems RX3i system a DeviceNet Master module can be installed in slot 1 or higher of the main rack only It cannot be installed in any expansion rack or remote rack In a Series 90 30 system a DeviceNet Master or Slave module can be installed in the main CPU rack in slot 2 or higher The Series 90 30 system does not support DeviceNet modules in expansion or remote racks a 2 5 4 Turn off power to the rack Place the module into its slot by hooking the top of the module on the notch above the slot and slowly lowering the module until it snaps into place Attach the DeviceNet cable to the module Terminate the network as required Note For details about installing PACSystems RX3i rack systems and modules refer to the PACSystems RX3i System Manual GFK 2314 For details about installing S
37. the DeviceNet master will update data for a network device To select the fastest update rate possible enter zero GFK 2196B October 2014 35 Chapter 3 PLC Configuration for the DeviceNet Master 3 5 3 Configuring DeviceNet Explicit Messaging Explicit Messaging is the highest priority messaging Explicit messaging provides access to objects other than the default I O connection set and optionally creates a buffer for explicit connection Not all slaves support explicit services and many including most discrete I O devices do not use explicit services Some devices rely on Explicit Messaging for configuration of selected parameters For example some VersaPoint modules can be configured using Explicit Messaging To be configured by Explicit Messaging an Explicit Messaging connection to the device must first be set up as shown below If Explicit Messaging should be enabled click on Enable Explicit Connection on the Explicit Messages tab In addition for a DeviceNet Slave Module or DeviceNet Master module operating as a slave specify the message request and message response size Make sure the size specified is large enough The DeviceNet modules implement Explicit Messaging through the use of COMMREQ instructions in the application program These COMMREQ messages are described in chapter 6 Programmed Communications The message sizes of each explicit message type are described in that chapter Mac ID 1 90 30 DeviceNet Slave
38. the FT output is High for only one PLC scan To capture the fact that a fault occurred you can program the fault output as a Set coil which would not be automatically reset at the end of ascan Additional logic would then be needed to reset the fault output coil after the fault is acknowledged and before the next execution of the COMMREQ Programming a device such as a Set Coil on the FT output of the COMMREQ is optional The FT output can be left open COMMREQs must be sent sequentially A new COMMREQ may be sent only after the previous COMMREQ indicates completion either success or error via the Status Block When using more than one COMMREQ in a ladder program verify that a previous COMMREQ executed successfully before executing another one This can be done by checking the Status Word and the FT Fault output 6 3 1 Checking the Execution of the COMMREQ The FT output of the COMMREQ function goes high for certain faults and can be used for fault detection In addition to using the FT output the program should monitor the first COMMREQ Status Word and use error message logic to generate text on an Operator Interface device In this case specific Status Word error codes might correspond to appropriate operator messages on a display screen The CPU places a value of 1 in the State COMMREQ Status word status word 1 if the COMMREQ is processed normally If any error condition is detected a value greater than 1 is returned Fo
39. to a master device on a DeviceNet network The DeviceNet Master Module can be also be configured for server operation and can perform the same functions as the DeviceNet Slave Module For the DeviceNet Master module use of the server features is optional Server features are configured using the module s Network Settings The module can be configured for two types of I O Messaging connections It can also be configured to enable or not enable DeviceNet Explicit Messaging I O Messaging for a DeviceNet Module PLC references are assigned to each I O Messaging connection configured for the server A master on the DeviceNet network can use these I O Messaging connections to read or write data in up to two memory areas in the PLC CPU One Memory Area for Polled and one memory area for cyclic strobed or COS 1 0 Explicit Messaging for a DeviceNet Module If Explicit Messaging is enabled in its Network Settings a module can receive DeviceNet Explicit Messages from a network master The module automatically responds to Explicit messages except for Explicit Messages for User defined objects which are queued for transfer to the PLC CPU where the user application program is responsible for handling them The application program in the PLC CPU reads the queued Explicit Messages individually and can respond appropriately The process of doing this is explained in chapter 5 Programmed Communications Error Handling If an error occurs the DeviceN
40. type of COMMREQ status word R for this example 8 R 10 Al 12 AQ 16 1 18 Q 20 T 22 M 00009 Status Memory Offset COMMREQ status words start address minus 1 R10 for this example S Reserved o 6 Reserved S f 7 00007 Command Code Send Device Explicit Extended command number 7 Reply Segment Select Memory type for the reply data R for this example 8 R 10 Al 12 AQ 16 I 18 Q 20 T 22 M Reply Memory Offset Offset within the memory type for the reply minus 1 For this example it is R251 Word offset for memory types 8 10 12 byte offset for memory types 16 18 20 22 Reply Memory Size Maximum size required to hold the reply for the command in words for memory types 8 10 12 in bytes for memory types 16 18 20 22 Add 10 bytes to expected reply size Note must be 10 bytes 5 words or more or an error will be reported in the COMMREQ status word and the request will be ignored Actual length needed will vary depending on which message is sent consult vendor information for the target device Maximum 2048 bytes Peed Segment Select Memory type for the service data R for this ARE 8 R 10 Al 12 AQ 16 1 18 Q 20 T 22 M Data Memory Offset Offset within the specified memory type for the service data start address minus 1 Word offset for memory types 8 10 12 byte offset for memory types 16 18 20 22 For this example it is R301 Data Memory Size Size of
41. types 8 10 12 byte offset for memory types 16 18 20 22 For this example it is R251 00010 000A Reply size Maximum size required to hold the reply for the command in words for memory types 8 10 12 in bytes for memory types 16 18 20 22 Note It must be 15 bytes or more or an error will be reported in the status word and the request will be ignored 92 DeviceNet Modules for PACSystems RX3i and Series 90 30 User s Manual GFK 2196B Chapter 6 Programmed Communications Receive Server Explicit Reply Data Format When it receives a Receive Server Explicit COMMREQ the DeviceNet module returns a reply containing either the next explicit request in its internal memory or an indication that there is no explicit request in the queue to process The reply contains information about the device that sent the explicit request and a description of the service requested The application program must be set up to respond appropriately to the request Command number that this data block is replying to 2 Status of Receive Server Explicit command If any of the following bits are set the corresponding condition is true A value of zero indicates that a message was retrieved 1 No explicit request available All remaining reply data is set to zero by the module bits 1 15 Reserved Service Data Optional data as required by the service The size of this data is indicated by GFK 2196B October 2014 95
42. wired with one cable connection only Figure 6 Wiring with a Single Connection October 2014 If the module is installed directly on the trunk cable or as part of a daisy chained drop cable it has both an incoming and outgoing cable connected 00000 Figure 7 Wiring with Two Connections 13 Chapter 2 Installation 2 3 Grounding 2 3 1 DeviceNet Cable Grounding All DeviceNet cable shields must 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 2 3 2 DeviceNet Power Supply Grounding 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 2 3 3 DeviceNet System Grounding DeviceNet communications should only be grounded to earth at a single point Typically this is done in the control cabinet where the DeviceNet power supply is located Return for the DeviceNet power V the drain bare wire and the cable shields must be directly tied to earth ground Ideally this grounding is done at a central location Connection should be made using a 25mm 1in copper braid or a 8 AWG wire not longer than 3meters 10ft The illustration below represents grounding for a network that has two power
43. 0x10 and Ox0E messages See documentation of targeted server device for meaning of specific attributes Since word 6 skipped a byte this is the actual beginning of the service data Locate data for messages without an attribute to start data here May be at a different location depending on the m a word boundary 10 to end Service Data For this example the end of the service data is located at word 71 6 header words 1 skipped byte 1 attribute byte 64 data words GFK 2196B October 2014 87 Chapter 6 Programmed Communications 6 8 2 Send Device Explicit amp Extended Reply Data Format The DeviceNet Master Module replies to a Send Device Explicit or Send Device Explicit Extended COMMREQ The reply data has the following format 1 Command code that this data block is replying to 1 for Send Device Explicit or 7 for Send Device 5 eo Explicit Extended 2 Status of the explicit message Bits O and 1 should both be 0 1 Explicit message response truncated to fit in shared memory buffer The configured size of the explicit buffer of the device is too small j 1 Explicit message response truncated to fit in Reply Memory The reply buffer 3 4 allocated by the COMMREQ is too small bits 2 15 Reserved should be ignored 3 MAC ID ofthe device producing this reply S O Number of reply data bytes consumed Note if allocated buffers are not large enough this value should indicate the actual size of the reply data
44. 2 Get Detailed Server Status 62 Get Status Info 62 Grounding 14 October 2014 109 Index H Hand Held Programmer 4 6 Headend Fault codes 72 O Messaging 8 configuration 29 35 O Messaging configuration 47 dentity Object 90 98 dle packets 22 nitialization file errors 72 nput data amounts 3 5 nputs on loss of slave 23 nstallation procedures 9 installing the module in the rack 15 K Kernel identification 70 L LEDs 16 Logicmaster 4 6 M MAC ID 22 45 Machine Edition Logic Developer 4 6 Message Router Object 90 99 Module Header file 74 Module ID 70 Module operation 53 54 Module revision 70 Module serial number 70 Module Status LED red 74 Module Type 70 N Network Status Data address 22 Network termination 13 O Online errors 72 Open DeviceNet Vendors Association ODVA 1 Operation in Program mode 54 Output data amounts 3 5 Outputs on loss of master 45 P PLC Data Object 90 104 PLC power supply load 10 PLC status references 58 Polled I O mode 29 30 35 36 47 48 Power Consumption 4 6 Power Consumption tab 25 46 Program mode transmission 23 45 R Read Module Header 62 Receive Server Explicit 62 Reconnect time 23 Removing the module from the rack 15 RS 232 serial port 17 S Scan interval 23 Send Device Explicit 62 Send Device Explicit Extended 62 Send Server Explicit 62 Send Server Explicit Extended
45. A second pair transmits network power The fifth conductor forms an electromagnetic shield Most cables have color coded leads which correspond to the color coding on the terminals on the DeviceNet modules 2 2 1 Cable and Network Specifications Thick Cable General Specifications Two shielded pairs Common axis with drain wire in center 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 Specifications Two shielded pairs Common axis with drain wire in center 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 devices Nominal 24 Vdc 4 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 GFK 2196B October 2014 11 Chapter 2 Installation 222 Bus Conne
46. ACK sssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssnssnssssssnssssssssstsee 15 2 5 Mod le LED Siciceciscesasstecevecsvacusedesusseasisetsvalscatesessiavesenssecssnchsodeiesssscasecbiadbsosdsesssoossndeinstndssease cssesvedcusasecedsienes 16 2 6 RS 232 SErAll POM AA A A E OAA 17 2 6 1 Upgrading Firmware in the DeviceNet Module cssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssse 17 Chapter 3 PLC Configuration for the DeviceNet Master ccccscecscscecesesececeseseseseseseseseseseseseseeeeeeeeeees 19 3 1 COMPIGUFOTION Ste PS oarenien aaa EE ENNAN AENA AENEA E AN ANEN ANANE 20 3 2 Adding a DeviceNet Master Module to the PLC Configuration scscscssscscecssesesecesessseceeeeeeeeeees 21 3 3 Configuring the Parameters of a DeviceNet Master Module scssssssssessesesesesesesesesesesereseseres 22 33 1 Parameters of a DeviceNet Master Module eecsssssssessssssssssssssssssusnsssssssseseessssesuunssssssesseeeeeeeeett 22 3 3 2 Configuring Network Settings of a DeviceNet Master MOdule ccsssuunsccssssssssssssssssssssssccssceseceeeees 26 3 4 Adding Slaves to the Network sssssssssssssesesesessseseseseseseseseseseseseseseseseseseseseseseseseseseseseseseseseseseeeeeeeeeses 27 3 5 Configuring Network Settings for Slaves Added to the Master sssssecessssceeecesseeeeees 1 28 3 5 1 Assigning the MAC IDs and Baud Rate messeseiisisirsiiscseti etn 28 3 5 2
47. COMMREQ messages are described in chapter 6 Programmed Communications The messages sizes of each explicit message type are described in that chapter Figure 43 Explicit Messaging Screen for a DeviceNet Master Module 40 DeviceNet Modules for PACSystems RX3i and Series 90 30 User s Manual GFK 2196B Chapter 4 PLC Configuration for the DeviceNet Slave This chapter explains how to add a DeviceNet Slave Module to the configuration of the Series 90 30 PLC It also explains how to configure communications connections between a DeviceNet Slave Module and the DeviceNet network Configuration Steps Adding a DeviceNet Slave Module to the PLC Configuration Configuring the Parameters of a DeviceNet Slave Module Configuring the Network Settings of a DeviceNet Slave Module Configuring the MAC ID Configuring I O Messaging Connections Configuring DeviceNet Explicit Messaging These configuration procedures are written for users who have a basic knowledge of the Machine Edition Logic Developer software and the Series 90 30 PLC For help with using the software please see the software s built in help system Note The DeviceNet Slave Module is only supported in Machine Edition Logic Developer The Logicmaster VersaPro and Control software do not support this module GFK 2196B October 2014 41 Chapter 4 PLC Configuration for the DeviceNet Slave 4 1 Configuration Steps There are three basic steps to configuring
48. Configuring I O Messaging Connections for Slaves added to the MASP 29 3 5 3 Configuring DeviceNet Explicit MESSAGING sssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssessseceeceeeeees 34 3 6 Configuring Network Settings for a DeviceNet Master Acting as a Slave ssessesseseseeeseeeees 35 3 6 1 Configuring I O Messaging Connections for a DeviceNet Master Acting as a Slave 35 3 6 2 Configuring DeviceNet Explicit MESSAGING sssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssccsscseceseeeeeees 40 Chapter 4 PLC Configuration for the DeviceNet Slave sscscscscscssssssssssesesessssceseseseseseseseseseseeseeseees 41 4 1 CONFIGURATION SEO PS cisean r nan aaa EEEE EEEE EEEE EERE 42 4 2 Adding a DeviceNet Slave Module to the PLC Configuration ssscssscscesecsseseseseseceeeseseseeeeeeeeeees 43 4 3 Configuring the Parameters of a DeviceNet Slave Module s sssssesssssessessesssssesssssesssesessseseesseseesee 44 4 3 1 Parameters of a DeviceNet Slave MOCUIC essssssssssssesnsssssssssssessssssutsnsssssseseseessesesuunssssssesseeeeseeseeee 45 4 4 Configuring the Network Settings of a DeviceNet Slave Module ccsssssssesessessesssseseeeseseeeees 47 4 4 1 Configuring 1 0 Messaging COMME CtiONS cesssssssssssssussssssssssessusssssssssssssusssssssssssssassssseuussesssaseseseee 47 4 4 2 Configuring DeviceNet Explicit MESSAGING ssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssss
49. D Oo GFK 2196B October 2014 Tt Chapter 6 Programmed Communications 6 6 Command Code 5 Getting Status Information of a DeviceNet Slave Module or the Server Function of a Master Module To retrieve status information about a DeviceNet Slave Module or a DeviceNet Master module operating in server mode use COMMREQ 5 Get Detailed Server Status This command supplies the following information about the module whether the module is set up for slave operation its network settings are configured the module s output connection states whether the module has sent a DeviceNet explicit message previously commanded by a Send Server Response COMMREQ how the module s I O messaging settings are configured This function is internal to the PLC it does not generate a DeviceNet network message PLC PLC Get Detailed Slave or Application Server Master Program Status Module Figure 67 Get Detailed Server Status Transaction Get Detailed Server Status COMMREQ Example In this example the application program sends a Get Detailed Served Status COMMREQ to a DeviceNet Master Module that is configured for slave operation This COMMREQ specifies the command number and command length and sets up memory locations for both the COMMREQ status and the reply message 00004 0004 Length of command Data Block Always 4 words for this command 00000 _ 0000 Always 0 no wait mode request 00008 0008 Status segment select
50. Data Object GFK 2196B October 2014 Chapter 7 DeviceNet Objects 7 1 Identity Object Object Class 0x01 The Identity Object contains the module s identifying information There is only one instance of this object 7 1 1 Class Attributes id Description sd 6 Max ID of class attributes Max ID of instance attributes Supported O Not supported 7 1 2 Class Services pO Reset pO FT 7 1 3 Instance Attributes Supported O Not supported 1 DeviceNet specifies that Major and Minor Revision may not be 0 the lowest valid minor revision is 1 7 1 4 Instance Services Service Param Options A ee Get_Attribute_Single a aaa Supported O Not supported 98 DeviceNet Modules for PACSystems RX3i and Series 90 30 User s Manual GFK 2196B Chapter 7 DeviceNet Objects 7 2 Message Router Object Object Class 0x02 The Message Router Object routes the explicit messages it receives to other Objects There is only 1 instance of this object 7 2 1 Class Attributes Max ID of instance attributes Supported O Not supported 7 2 2 Class Services Co Co 6 7 2 3 Instance Attributes Active connections list Supported O Not supported 7 2 4 Instance Services Get_Attributes_All Supported O Not supported GFK 2196B October 2014 99 Chapter 7 DeviceNet Objects 7 3 DeviceNet Object Object Class 0x03 The DeviceNet Object contains the parameter
51. EF DeviceNet System Q Target LQ C Blocks Ga Data Watch Lists fiji Hardware Configuration if Main Rack IC693CHS 391 i a PWR IC693PWR321 Hardware BP Slot 1 IC693CPU364 Configuration Folder E A i Configure Navigator Window Short Cut Menu Figure 46 Add Module to Slot Location 4 The Module Catalog dialog box appears To add a DeviceNet Slave Module click on the Communications tab Select the IC693DNS201 DeviceNet Slave from the list and click OK Profibus Slave Homer Electric Profibus Slave Genius Communications Module Enhanced Genius Communications Module Communications Coprocessor IC693CMM321 Ethen CE93DNS201 Figure 47 Select DeviceNet Slave Module from List GFK 2196B October 2014 43 Chapter 4 PLC Configuration for the DeviceNet Slave 4 3 Configuring the Parameters of a DeviceNet Slave Module After selecting the module its Parameter Editor window appears in the InfoViewer window space Data Watch Lists Hardware Configuration 5 Main Rack IC693C0HS391 500 Bll PWR IC693PWR321 2 amp 0004 A Slot 1 IC693CPU364 3 Hold Last State lt Double click to configure gt Send Idle Send Idle True 2000 Figure 48 Configuring Parameters for DeviceNet Slave 44 DeviceNet Modules for PACSystems RX3i and Series 90 30 User s Manual GFK 2196B Chapter 4 PLC Configuration for the DeviceNet Slave 4 3 1 Parameters o
52. EQs are used for reading information from the DeviceNet module itself and for sending or replying to DeviceNet explicit messages over the network See the following sections COMMREQs for DeviceNet Modules Using COMMREQs to Program Communications an overview COMMREQ Programming Requirements and Recommendations Reading Identification Status and Error Information from DeviceNet Master or Slave Module Module Type Module ID Module revision CAN Kernel identification and revision DeviceNet serial number Error codes CAN Network status Getting the Status of a Network Slave for DeviceNet Master Module only whether it is included in the master s list of configured devices whether it is being scanned its configuration error status its connection 1 and connection 2 input states Getting Slave Status Information of a DeviceNet Master or Slave Module whether the module is set up for slave operation the module s output connection states whether the module has sent a DeviceNet explicit message how the module s I O messaging settings are configured Getting Input Status from a Device from DeviceNet Master Module the network activity status of each MAC ID on the network the DeviceNet Master Module s own configured Network Settings the DeviceNet Master Module s current network status the DeviceNet Master Module s firmware ID Sending a DeviceNet Explicit Message on the Network DeviceNet
53. EQs support 8 DeviceNet Modules for PACSystems RX3i and Series 90 30 User s Manual GFK 2196B Chapter 2 Installation This chapter provides basic installation information for the DeviceNet Modules Power requirements PLC system power and DeviceNet network power The DeviceNet cable specifications length termination taps Grounding DeviceNet cable DeviceNet power supply DeviceNet system Installing the DeviceNet module in the PLC The Module LEDs Module Status Network Status Network Power The RS 232 Serial Port For Additional Information Correct installation of cables power supplies and other network hardware requires a more detailed knowledge of DeviceNet specifications than can be provided here Readers are referred to www ODVA org for additional information Conformance to Standards Before installing GE Intelligent Platforms 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 the following publications available on the GE Intelligent Platforms support site http support ge ip com Series 90 30 Installation Requirements for Conformance to Standards GFK 1179 PACSystems RX3i PACSystems RX3i System Manual GFK 2314 GFK 2196B October 2014 9 Chapter 2 Installation 2 1 Power Supplies When using a DeviceNet module there are two separate powe
54. Extended the data to be sent is located in a separate memory area which is indicated by a pointer in the COMMREQ command block This makes it possible to store and send more data or to have the data separate from the command memory GFK 2196B October 2014 83 Chapter 6 Programmed Communications Series 90 30 PLC or PACSystems RX3i Controller COMMREQ Command Block Data to be Sent SESSIE Explicit Extended Figure 71 Send Device Explicit Extended Transaction Showing Memory Usage Send Device Explicit COMMREQ Example The Send Device Explicit COMMREQ command block contains the data to be sent in the explicit message the data may optionally be offset from the end of the command block as explained below For this example there are multiple channels in the VersaPoint analog module to configure The application program can repeat the message with a different instance another channel Having the PLC application check the COMMREQ status is important even if there is only one COMMREQ to be sure it has worked The VersaPoint DeviceNet NIU network interface unit may be off line for example When sequencing multiple commands to the same device MAC ID it is critical to test for successful command completion prior to executing a subsequent command This example COMMREQ does the following Sends an explicit message to device 4 a VersaPoint DeviceNet NIU Returns the COMMREQ Status Words to R10 R13 Sets Analog Inpu
55. Intelligent Platforms Programmable Control Products DeviceNet Modules for PACSystems RX3i and Series 90 30 User s Manual GFK 2196B October 2014 Warnings Cautions and Notes as Used in this Publication Warning 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 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 These instructions do not purport to cover all details or variations in equipment nor to provide for every possible contingency to be met during installation operation and maintenance The information is supplied for informational purposes only and GE makes no warranty as to the accuracy of the information included herein Changes modifications and or improvements to equipment and specifications are made periodically and these changes may or may not be reflected herein It is understood that GE may make changes modifications or improvements to the equipment referenced herein or to the document itself at any time This document is intended for trained personnel familia
56. LE operation Configurable fault behavior on loss of communication UCMM capable Group 2 Server GFK 2196B October 2014 5 Chapter 1 Introduction 1 4 2 DeviceNet Slave Module Specifications Catalog Number IC693DNS201 Description Slave Module for DeviceNet networks Mounting Location Series 90 30 main rack Any slot except slots 0 and 1 Environment Storage temperature 40 C to 85 C Operating temperature 0 C to 60 C Backplane Current Consumption 450mA at 5Vdc typical Current Consumption from DeviceNet 50mA at 24Vdc typical Network 80mA at 24Vdc peak 1 4 3 Compatibility Compatible with any Series 90 30 CPU except IC693CPU321 and IC693CPU340 Requires Series 90 30 release 8 0 or later CPU firmware Release 10 6 or later is recommended if available for the particular CPU Requires Proficy Machine Edition Logic Developer PLC version 3 0 SP1 Special 2 or later Not compatible with the VersaPro Control or Logicmaster programming software The Series 90 30 Hand Held Programmer IC693PRG300 cannot be used to configure this module DeviceNet Modules for PACSystems RX3i and Series 90 30 User s Manual GFK 2196B Chapter 1 Introduction 1 5 The DeviceNet Network DeviceNet is a communications network that transmits data between control systems for example PLCs PCs VMEbus computers and robot controllers and distributed industrial devices such as switches sensors valve manifo
57. Master Reading and Responding to DeviceNet Explicit Messages from the Network DeviceNet Slave Module or Master Module configured for slave operation For more general information about programming COMMREQs please use the online help provided with the programming software GFK 2196B October 2014 61 Chapter 6 Programmed Communications 6 1 COMMREQs for the DeviceNet Modules The DeviceNet Master Module and Slave Module can use the COMMREQs listed below COMMREQs are described in detail on the following pages Command Feature Command Description Code Support Name 1 Master Send Device Explicit Used to send and receive explicit messages to a server device over the DeviceNet network Maximum 238 service data bytes 2 Slave Receive Server Used to retrieve an explicit request sent to the server Explicit within the module 3 Slave Send Server Explicit Used to service an explicit request sent to the server within the module e g reply to the client explicit request Maximum 238 service data bytes 4 Master Get Detailed Device Used to retrieve detailed status information for a Status specified node on the network 5 Slave Get Detailed Server Used to retrieve detailed status about the server Status function of the module 6 Master amp Get Status Info Used to retrieve the module status bytes that may also Slave be configured to PLC I O An alternate method to access this data Includes Devic
58. OMMREQ 7 minus the number of bytes skipped in the data byte offset command 7 data word 6 of the service data header For the command 7 example that follows the device at network address 4 the S2K controller must have a minimum of 141 bytes 142 bytes data block minus 1 skipped byte explicit message size configured Series 90 30 PLC or PACSystems RX3i Controller DeviceNet network PLC Send Device Application Master Explicit and Extended Moguig Network Explicit p Node Message Program Figure 69 Send Device Explicit Extended Transaction If the device was not configured for explicit messaging or if the number of bytes configured is not enough for the command the COMMREQ fails with a code of 8 in the COMMREQ Status Word Difference between Send Device Explicit and Send Device Explicit Extended The difference between Send Device Explicit and Send Device Explicit Extended is how they store the data that will be sent in PLC memory For Send Device Explicit the data to be sent is located in the same memory area as the COMMREO command block Series 90 30 PLC or PACSystems RX3i Controller COMMREQ Command Block DeviceNet network DeviceNet Master Module Data to be Sent SEES EDIO Explicit Network Node Explicit Message Figure 70 Send Device Explicit Transaction Showing Memory Usage For Send Device Explicit
59. OS I O Messaging Screen for a Series 90 30 DeviceNet Master Module For input resources specify the number of data bytes the device will send to the master For output resources enter the number of bytes the device will consume from the master If Acknowledge Suppress is selected the DeviceNet master will not wait for an acknowledge message from the device For Inhibit specify the minimum delay in milliseconds between two data productions For example a slave is running a COS connection that has a change in data every 5ms but the control application needs new data every 25ms Setting the inhibit value to 25 causes the slave to transmit data at minimum intervals of 25ms and avoids needless use of network bandwidth For Update specify the interval in milliseconds at which the DeviceNet master will update data for this device To select the fastest update rate possible enter zero 38 DeviceNet Modules for PACSystems RX3i and Series 90 30 User s Manual GFK 2196B Chapter 3 PLC Configuration for the DeviceNet Master Configuring a Cyclic I O Messaging Connection In Cyclic I O Messaging as in Polled I O Messaging the DeviceNet master automatically sends a message containing outputs to a device with a connection configured for Cyclic update The device sends back a response containing input data Like Polling Cyclic I O Messaging requires 2 messages to update the 1 0 data for a device Unlike Polled messaging Cyclic messaging can use a
60. PU reads input data from the DeviceNet Master Module during its normal input scan The PLC CPU updates the data in each device s configured memory location After solving the application program the PLC CPU sends the appropriate output data to the DeviceNet Master Module The module then provides output data to network devices according to their configured I O Messaging communications type Operation if the CPU Stops Reading Inputs from the Module in PLC Run Mode If the PLC CPU stops reading inputs from the DeviceNet Master Module for an interval of 1 second the module assumes the CPU is no longer communicating and declares a PLC fault The module continues to monitor inputs from the network but does not send the input data to the PLC CPU It also stops sending output data on the network Instead it either transmits idle messages or zeroed data as described for Stop Mode Network devices then enter their own configured safe states 54 DeviceNet Modules for PACSystems RX3i and Series 90 30 User s Manual GFK 2196B Chapter 5 Module Operation The module does not recover until the rack containing the module is power cycled Because of this if you have a DNM200 or DNS201 module in your PLC do not execute a SUS_IO Suspend 1 0 function block or SVC_REQ 45 Skip Next I O Scan RX3i users should use caution when configuring the DNM200 for a scan set that is not scanned every sweep the of sweeps times the sweep time cannot exceed 1000ms
61. References for a DeviceNet Module A DeviceNet module automatically reports the three words of status information shown below to its configured PLC references Network Status Firmware ID The application logic can monitor these references and take appropriate actions in response to specific changes This can be done in conjunction with or instead of monitoring faults in the fault tables The format of the three status words is the same for both modules For the DeviceNet Master Module word 1 Server Status is meaningful only if the module is set up to operate as a slave server on a network with another master device The same information mapped to the status words can also be read directly from the module using COMMREQ 6 Get Status Information as described in chapter 6 Programmed Communications reserved Group 2 only I O connections Acknowledge suppress enabled Cyclic I O connection allocated Change of state I O connection allocated Bit Strobed I O connection allocated Polled I O connection allocated Server Status Group 2 Explicit Connections Explicit connection allocated Group 3 Connection At least one Group 3 UCMM connection allocated Status Bits Output area 1 receive idle status bit Output area 2 receive idle status bit Server Explicit Request Available Use Receive server explicit command to retrieve the request 58 DeviceNet Modules for PACSystems RX3i and Series 90 30 User s Manual GFK 2196B Chapter 5
62. Suppress is selected the DeviceNet master will not wait for an acknowledge message from the device For Inhibit specify the minimum delay in milliseconds between two data productions For example a slave is running a COS connection that has a change in data every 5ms but the control application needs new data every 25ms Setting the inhibit value to 25 causes the slave to transmit data at minimum intervals of 25ms and avoids needless use of network bandwidth For Update specify the interval in milliseconds at which the DeviceNet master will update data for this device To select the fastest update rate possible enter zero 32 DeviceNet Modules for PACSystems RX3i and Series 90 30 User s Manual GFK 2196B Chapter 3 PLC Configuration for the DeviceNet Master Configuring a Cyclic I O Messaging Connection In Cyclic I O Messaging as in Polled I O Messaging the DeviceNet master automatically sends a message containing outputs to a device with a connection configured for Cyclic update The device sends back a response containing input data Like Polling Cyclic I O Messaging requires 2 messages to update the 1 0 data for a device Unlike Polled messaging Cyclic messaging can use a different interval as configured for each slave DeviceNet Query gt Master lt Response Slave 1 X fe o c 3 Slave 2 Q 2 gt o a Query gt Response Query gt Slave n Response Figure 31 Devic
63. Systems RX3i and Series 90 30 User s Manual GFK 2196B Chapter 6 Programmed Communications eae aigi Error Description 24 Invalid CAN interrupt 25 Nested system timer interrupt 26 Imperfect interrupt This error should be reported to the vendor of the application module Make note of the circumstances that caused this error This error is caused by an incorrectly generated interrupt from the host bus adapter to the module 27 Stack Overflow This error should be reported to the vendor of the application module Make note of the circumstances that caused this error 99 Unexpected condition A fatal headend fault occurred Report this condition to the vendor of encountered the application module GFK 2196B October 2014 75 Chapter 6 Programmed Communications 6 5 Command Code 4 Getting the Status of a Network Device To retrieve from the DeviceNet Master Module a set of detailed status information about a selected network device use COMMREQ 4 Get Detailed Device Status Series 90 30 PLC or PACSystems RX3i Controller PLC Application Get Detailed Device Status Master Module Program Figure 66 Get Detailed Device Status Transaction This command obtains the following information for the specified node whether it is included in the master s list of configured devices whether it is being scanned configuration error status invalid vendor id device type pro
64. U memory e Data e Status Block GFK 2196B PLC Backplane RX3i Series 90 30 DeviceNet Master or Series 90 30 DeviceNet Slave Module Status data res Figure 63 COMMREQ Sequence October 2014 DeviceNet network NS ieee a ee 63 Chapter 6 Programmed Communications 6 2 1 Format of the Communication Request Function The Communication Request COMMREQ function has the following parameters Enable Input Command Block Pointer Fault Output Rack Slot Location Task Figure 64 COMMREQ Function Representation 6 2 2 Parameters of the COMMREQ Function Enable When the function is energized the communications request is performed Must be Logic 1 to enable the COMMREQ instruction The enabling logic should be a contact from a transition one shot coil Pointer to the first word of the Command Block For example R00100 at IN would mean that the starting address of the Command Block is R00100 The length of the Command Block depends on which command is being executed Command Blocks for all the DeviceNet module commands are shown in this chapter l Q M T G R Hex value that specifies the rack number most significant byte and slot Al AQ number least significant byte of the target device For example constant rack O slot 4 0004 rack 2 slot9 0209 Must be set to 1 for the DeviceNet Master or DeviceNet Slave module flow none The FT fault output can provide an output to
65. _PLC_DATA Service 0x33 Service Specific Request Data Offset UINT2 Offset into memory area Units are dependent on Seg_Selector Offset is 1 based not 0 based Length UINT2 Length of data to write Units are dependent on Seg_Selector A maximum of 255 bytes per service request can be written If more than 255 bytes are sent SET_PLC_DATA will return error 0x15 OxFF too much data Data UNIT Length Data to be written Size of data is Length size of Unit Note The Service Request Data for this service does not include an attribute byte Service Specific Success Response Data On success the Explicit Service field will be set to OxB3 and will contain no data Service Specific Error Response Data Error responses contain 0x94 in the Service Code field of the explicit message and an Error Code and Additional Code in Bytes 1 and 2 respectively The following error codes may be returned Description Service not supported invalid Service Code Object state conflict i e internal mail system unavailable Reply data too large the data to be transmitted is larger than the internal transmit buffer 255 bytes Not enough data Too much data Object does not exist invalid Instance ID or Class ID Register base address is not in the proper form Register quantity is not in the proper form Register base address out of range for this CPU model Register quantity out of range for this CPU model or DN module Sum of register bas
66. a DeviceNet Master Module A DeviceNet Master Module automatically exchanges data with devices on the network once connections are established However the content of the data it sends to network devices depends on the operating mode of the PLC 5 1 1 DeviceNet Master Module Operation while the PLC is in Stop Mode While the PLC is in STOP Mode the DeviceNet Master Module updates its internal memory with input data from devices on the network and with any output data it may receive from the PLC CPU However the DeviceNet Master Module does not transmit PLC output data on the network until the PLC returns to Run mode Depending on its configuration it transmits either of the following during Stop mode Idle Messages zero length Transmit Idle is the default state In the Transmit Idle state the DeviceNet Master Module sends zero length I O messages to all its configured DeviceNet devices Each device detects this as a Receive Idle condition as defined in the DeviceNet Specification The device then implements its configured safe state behavior Zeroed Data In the Send Zeroed Data state the DeviceNet Master Module sets the output data for all devices to zero If the DeviceNet Master Module receives a new configuration while the PLC is in Stop Mode it closes down connections with all DeviceNet devices and processes the new configuration Operation when the PLC Transitions from Stop Mode to Run Mode When the PLC transitions
67. a DeviceNet Slave Module Configuring its module parameters as part of the PLC CPU system in which it is installed This is described on the next page Figure 44 Select Slot Location for DeviceNet Slave Configuring its network settings For information see the section Configuring Network Settings later in this chapter hn Oe Figure 45 Configure Network Settings for DeviceNet Slave Configuring the module as a slave on the network of a master module Instructions for configuring the network of a DeviceNet Master Module are given in chapter 3 Instructions for configuring other master types are not described in this manual 42 DeviceNet Modules for PACSystems RX3i and Series 90 30 User s Manual GFK 2196B Chapter 4 PLC Configuration for the DeviceNet Slave 4 2 Adding a DeviceNet Slave Module to the PLC Configuration First add the DeviceNet Slave Module to the PLC rack configuration The DeviceNet Slave Module is compatible with any Series 90 30 CPU except IC693CPU321 and IC693CPU340 It requires release 8 0 CPU firmware as a minimum Release 10 6 or later is recommended if available for your particular CPU 1 In that configuration in the Project tab of the Navigator expand the Hardware Configuration folder 2 Inthe Hardware Configuration folder right click the PLC Slot for the DeviceNet Slave Module It can be in slot 2 or higher in the main rack 3 Select Add Module from the shortcut menu
68. an communicate with the module for Explicit Messaging and for reading status information Chapter 7 DeviceNet Objects describes the information objects that are defined for the DeviceNet modules Appendix A DeviceNet EDS Files contains the Electronic Datasheet EDS Files that are defined for the DeviceNet Master Module and the DeviceNet Slave Module 1 1 1 For Detailed Information about DeviceNet For detailed information about DeviceNet contact the Open DeviceNet Vendor Association 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 odva odva org GFK 2196B October 2014 1 Chapter 1 Introduction 1 2 DeviceNet Modules Two different DeviceNet modules bring the flexibility of DeviceNet communications to a PACSystems RX3i or a Series 90 30 PLC The DeviceNet Master Module IC693DNM200 IC694DNM200 operates as the network master It exchanges I O messages and custom explicit messages with up to 63 other devices on the network On DeviceNet networks that include a higher level host computer this module s built in server function can be used for both automatic data transfer and custom explicit messaging with the master The DeviceNet Slave Module IC693DNS201 operates as a network server slave only It can automatically exchange PLC data with a network master and respond to custom explicit messages from
69. arameters of a DeviceNet Master Module Parameters of a DeviceNet Master Module Network Settings of a DeviceNet Master Module Telling the DeviceNet Master about Slaves by Adding Slaves to the Network Adding a Device s EDS File Configuring Network Settings for Slaves Added to the Master Assigning the MAC IDs and Baud Rate Configuring I O Messaging Connections Configuring DeviceNet Explicit Messaging Configuring Network Settings for a DeviceNet Master Acting as a Slave Assigning the MAC IDs and Baud Rate Configuring I O Messaging Connections for a DeviceNet Master Acting as a Slave Configuring DeviceNet Explicit Messaging These configuration procedures are written for users who have a basic knowledge of the Machine Edition Logic Developer software and the Series 90 30 PLC or PACSystems RX3i control system For help with using the software please see the software s built in help system Note The DeviceNet Master is only supported in Machine Edition Logic Developer The Logicmaster VersaPro and Control software do not support these DeviceNet modules GFK 2196B October 2014 19 Chapter 3 PLC Configuration for the DeviceNet Master 3 1 Configuration Steps There are three basic steps to configuring a DeviceNet Master Module Adding the module to the PLC rack and configuring its operating parameters CH iD Figure 11 Selecting Slot Location for the DeviceNet Module Telling the DeviceNet Master
70. b shows master inputs which are module outputs The output data area tab shows master outputs which are module inputs For both inputs and outputs data can be configured for both connection 1 and connection 2 Settings Input Data Area Output Data Area Power Consumption Type Ref Address Length Connection 1 0 100081 Connection 2 100 5 3 Empty Empty Empty Empty E rontu co 1 Jon eco ro Connection 2 Output Data To Master j E Empty Connection 1 Output Data To Master Connection 2 Output Data To Master N wo a Cancel Help Figure 49 Data Area Tab for DeviceNet Slave Module For both inputs and outputs the offset is the starting address in the master PLC memory area It must be less than the size of the data area specified in the Network Settings dialog box To specify data area Size in the Navigator right click the DeviceNet slave and choose Network Settings The DeviceNet Slave Properties dialog box appears On the Connection 1 or Connection 2 tab set the Size under Resources The Reference Address is the location in master PLC memory where the data is mapped This field is read only if Size is set to 0 This must be a range in Al l Q MG WAQ WR KT or M If the number of bytes Size is odd only the discrete addresses I Q G M T can be used Power Consumption Tab Power consumption This read only tab shows the backplane power t
71. bject for that I O message There can be a maximum of 255 instances of the Connection Object in any combination of connection types 7 5 1 Class Attributes Description Revision lesa ee 1 State ae oo 3 Transport class co aE a a a T oa a Lo or trigger or jor for 0x10 0x13 i ee E A connection ID ea e of HHH connection ID a Waa characteristics e a PO connection size ee connection size e AA rate 12 Watchdog aia timeout action 1 102 DeviceNet Modules for PACSystems RX3i and Series 90 30 User s Manual GFK 2196B Chapter 7 DeviceNet Objects lid Description Get Set Attribute Limits Fixed Values 13 Produced connection path length A feon connection path 15 Consumed connection path length 16 Consumed connection path Supported O Not supported 1 set attribute service supported only by the server explicit messaging connection 2 set attribute service supported on client trigger connections only Connection types Explicit Client Connection Attribute Limits 2 Explicit Server Connection Attribute Limits 3 Poll Client Connection Attribute Limits 4 Poll Server Connection Attribute Limits 5 Strobe Client Connection Attribute Limits 6 Strobe Server Connection Attribute Limits 7 COS Cyclic Client Connection Attribute Limits acknowledged 8 COS Cyclic Server Connection Attribute Limits acknowledged 9 COS Cyclic Client Connection Attribute Limits unacknowledged 10 COS C
72. ceNet bus that is controlled by another master device neis Status The module s three DeviceNet compliant LEDs show its rE LEDs operating and communications status The RS 232 serial port a 9 pin male D connector is used for a computer connection during firmware upgrades The DeviceNet connector is a pepe removable spring clamp terminal It provides bus continuity and can be removed from the module without disrupting bus SERVICE Rena RS 232 operation Connector DeviceNet Connector DEVICENET Series 90 30 DeviceNet Slave Module 1 4 1 Features Bus communications at all standard DeviceNet data rates 125K 250K 500K baud Up to 255 bytes input data transfer and 255 bytes output data transfer Configurable for Poll Strobe Cyclic and COS I O Connections and Explicit Messaging Supports Unconnected Message Manager UCMM allowing up to 250 simultaneous explicit messaging connections One or two O connections plus explicit messaging can be configured Each I O connection can be set up for one of the following Poll Strobe Cyclic or Change of State COS operation Typically one connection is used for Polled and the other is used for Strobe Cyclic or COS Supports the Assembly Object and access to the input and output data for each of the configured slave I O areas I O Area 1 and I O Area 2 with the SET_ATTRIBUTE_SINGLE and GET_ATTRIBUTE_SINGLE services Up to 255 bytes of attribute data may be supplied in the SET_ATTRIBUTE_SING
73. ceseseseseeeseceseseceeeeeseeeeeees 61 COMMREQs for the DeviceNet Modules ccccssssssessecssseccssescsssssesessecessecessecesseseesesseceseecesseceseeseenees 62 Using COMMREQsS to Program COMMUNICATIONS ceseeeeecececseeecececsctscececseescececcessesceceeeeesceceeters 63 6 2 1 Format of the COMMUNICATION REQUEST FUNGON sssini 64 6 2 2 Parameters of the COMMREO FUNCTION cesccsseescssssescsssseescssssesssssssescsssssecesssuescssssesssssssesesssssesssneeesssssesessanes 64 COMMREQ Programming Requirements and RECOMMENCATIONS scssesssesesssssseseseseseceeeees 65 6 3 1 Checking the Execution Of the COMMREQ sereen 65 6 3 2 Using COMMREQs for DeviceNet Explicit MESSAGING sssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssse 65 6 3 3 The COMMREQ Status Block for DeviceNet MOCUICS ooo eeccceesscssssescssssessssssescssssessssssscssssetsessasesesssnes 67 Command Code 9 Reading Identification Status and Error Information cccsceccesseeeeeees 68 6 4 1 Read Module Header COMMREO EXGimi ples csssccscccecccceeeecccceeccececeescceccccecccectcccccccccceetcccctccccccccetececececcecettet 69 6 4 2 Read Module Header Reply Data FOrMdt ssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssste 70 Command Code 4 Getting the Status of a Network Device sssssseseseseseseseseseseseseseresererereres 76 Command Code 5 Getting Status Information of a DeviceNe
74. cit A Application i Explicit z a Program i Messages lt Client Client s on a 4 i SERRA bit Network i i i I i 1 3 Command Reply Figure 73 Reading Custom Explicit Message Transaction s A DeviceNet module can receive multiple explicit request messages from a network master before the first response message is generated Command code 2 Receive Server Explicit Example COMMREQ Format This example Receive Server Explicit COMMREQ specifies the command number 2 and sets up in the PLC CPU a memory type starting address and length for the reply data that will be returned by the module Test the SERA bit to initiate this command Description o o 1 00004 aa Command Length of command Data Block For the Receive Server Explicit command the length is 4 2__ 00000__ 0000 _fAlways 0 Ino wait mode request __________ 00008 008 Status eagment select Memory type of COMMREQ status words R for this example 8 R 10 Al 12 AQ 16 1 18 Q 20 T 22 M 4 00009 0009 Status memory offset COMMREQ status words start address minus 1 R10 for example 00000 __ 0000 gt o H 0000 7 00002 0002 Command code Receive Server Explicit 2 oO p 4 Reply segment select Memory type for the reply data R for this ee deco 8 R 10 Al 12 AQ 16 1 18 Q 20 T 22 M pf OOFA Reply memory offset Offset within the memory type for the reply minus 1 Word offset for memory
75. csccessuasccssccastuaceccdosssue I i 3 1 3 2 DeviceNet Master Module Specifications sessessesessesseresrererresrerserserserrerrerrerserrerrerrerrererererrerrerrerrerrerrerrerrerreni 4 1 3 3 Compatibility 1 4 DeviceNet Slave Module cssssssssssssssscssssssssssssssssssssssssesesssssesssssesesesssesssesssescssscssssssecesesssesesesaseseseseseses 5 14 1 AEC LA A ELS E E E 5 1 4 2 DeviceNet Slave Module Specifications 6 1 4 3 Grol a alo le to 18 geveereeeveevereeeeeeeeresevrereerereverresrebrevervrrrrr rrr rrr PP rrr PPP PPP PPP PP reeees Fe 0 bse lrrrrrneenersrrreeeeeee rere ee Pere e epee eeeeeeeeeeeEeEE EE 6 1 5 The DeviceNet Network ccscssssssscscscscssscscssscssscssscssscssscsessscesscccscseecscscceeeceeseecceeesecseeceeeeeeneteeeeeeeaes 7 1 6 DeviceNet Communications for DeviceNet Modules sssccscsscscscsssssesssessssssseseseseseseseseserererererenes 8 1 6 1 I O M SSCGIING eesssscsssssssssssessssssesessssseseusssessssnsseseasaseessansseseussssesuassseseunsssessasnssseseuasseesnussssesuassseseunsseessansseseuasse 8 1 6 2 Fapt MessSgg iN isss 8 Chapter 2 IMSTANATION 0 0 esesecececesecececececeseseseseseceseseseseseseseseseseseseseseseseseseseseseseseseseseseseseseseseseseseseseseesseeeneees 9 2 1 Power SUP POS cies cceecasocaCcckencstcsitssitatioussdessdasslasscasstanstaestasscassuanabasalatsucnsuassbasalatsusnauceavanedassuanaucsacesscetecanste 10 2 1 1 PUC ROWE Mis secesserseevsctececesvesseececsscvese
76. cssscseseeceeeees 52 Chapter 5 Module O Pe ratio i escsccscscscacacscscacacacacacacacacacacacacacacacacacacacacacacachcacacacacocpcachcachchcachcpcbcbcachcnchcacbcbcbete 53 5 1 Operation of a DeviceNet Master MOodule sssssssesssssessesesesesesesesssesesesessseseseseseseseseseserereserenes 54 5 1 1 DeviceNet Master Module Operation while the PLC is in Stop MOde esssssssssssssssssssssssssssssssssssse 54 5 1 2 DeviceNet Master Module Operation while the PLC is IN Run Mode esssssssssssssssssssssssssssssssssssssse 54 5 2 Operation of a Slave Server DeviceNet Module s ecsscecsssecsesecsesecsssecsssecsesecsesecseseceesecseseceeeecees 56 5 3 Fault Table Entries for a DeviceNet Module esesessscssececsssssesececsseesececusoesesecucosecsecscnsessesesseoees 57 5 3 1 Faults Reported to the 1 0 Fault Table cccsssssssssssssssssessssssesssssessussssessusssessusssssssussseseuassseseuee 57 vi DeviceNet Modules for PACSystems RX3i and Series 90 30 User s Manual GFK 2196B Contents 5 4 5 5 Chapter 6 1 6 2 6 3 6 4 6 5 6 6 6 7 6 8 6 9 6 10 6 11 Chapter 7 1 7 2 PLC Status References for a DeviceNet Module esssssssecessssssesececsssssesecsssesesecscsssesececseaeseeeeseeeees 58 Device Status Bits for the DeviceNet Master Module 0 esessssesecessssesececssesesecscsssesececsseeeeeeeneeeere 60 6 Programmed COMMUNICATIONS cececececececececececececssecececesesecesececese
77. cting Slot Location for the DeviceNet MOUIE ssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssnssssssssnsisss 20 Figure 12 Configuring DeviceNet Slaves Associated With the MOStOD ccsssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssee 20 Figure 13 Configuring Network Settings at the DeviceNet MOSTtEL ssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssse 20 Figure 14 Adding Module to a Slot Location in PME csssssssssssssssssssssssssee Figure 15 Selecting the DeviceNet Module as Item to be Added Figure 16 Setting Parameters for DeviceNet MOdUIE ssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssnsssat saunas PIQUE IT DOTA TOO DISDIOY sccsscccsscesssesessscsceectsceecdesecececeeeceeeeeeeeececeececeeeececeeececececececeececeeeeetettteetcssss5s3335533343434sssssssssssNNN EINE Figure 18 Power Consumption Display Read Only smuss Figure 19 Selecting Module for Network Configuration ASSIQNMENES cssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssee 26 Figure 20 Network Settings Dialog BOX eccesssssssssssssssssssssssassssssssssssssssssssssssssssssssssssssssesssssssssssssssssssssesssesssssssessssssssssssssssssssssssssssssssssssssssssssssssis 26 Figure 21 Associate Slave with DeviceNet Master Module sunnia 27 Figure 22 Select TVD OF SOVE riarann
78. ctor Pin Assignments The DeviceNet connector on a DeviceNet module has five color coded screw clamp terminals The connector provides bus continuity it can be removed from the module without disrupting bus operation Signal Pin Wire Color Ve V 5 Red CAN_H er CAN_H 4 White SAN Shield Bare CAN_L 2 Blue Figure 2 DeviceNet Connector V 1 Black 2 2 3 Bus Length The maximum length of the trunk cable and drops both depend on the cable type and data rate Individual drops may not exceed 6 meters and are limited to one network node per drop However the node may have multiple ports Data Rates 125kbps 250kbps 500kbps thick cable trunk length 500m 1640ft 250m 820ft 100m 328ft thin cable trunk length 100m 328ft 100m 328ft 100m 328ft maximum drop length 6m 20ft 6m 20ft 6m 20ft total length of all drops 156m 512ft 78m 256ft 39m 128ft For each baud rate the total drop length is the sum of all the drop lines of both cable types in the network In addition if the distance from a tap to the most distant device on its drop is longer than the distance from the tap to the nearest terminating resistor as illustrated below the drop line length also counts as part of the trunk cable length as well as the overall drop length Distance to Terminating Resistor n T ap Resistor Terminating Node Longest Distance to a N
79. ddress MAC ID of the device For example if the status bits begin at 100001 the status for the device at Station Address 5 is at 100001 5 which is I00006 The status bit for the DeviceNet Master Module also corresponds to its MAC ID The value of DeviceNet Master Module s own status bit is always 0 For other devices if a status bit is 0 the device at the corresponding MAC ID is inactive not configured or faulted If a status bit is 1 the corresponding device is active Transitions in these bits from 0 to 1 and from 1 to O are reported as Addition of Module and Loss of Module faults in the I O Fault Table The example status bits shown below represent a network with 25 devices assigned MAC IDs 0 to 24 The DeviceNet Master Module is assigned MAC ID 0 and the device with MAC ID 8 is faulted so there are Os in status bits 100001 100009 and 100026 through 100064 Example Device Status Bits 100001 100017 100033 100049 The same information about device status can be read directly from the module using COMMREQ 6 Get Status Information as described in chapter 6 Programmed Communications 60 DeviceNet Modules for PACSystems RX3i and Series 90 30 User s Manual GFK 2196B Chapter6 Programmed Communications This chapter explains how the application program can use Communications Request Instructions COMMREQs to exchange information with a DeviceNet Master Module or DeviceNet Slave Module COMMR
80. different interval as configured for each slave DeviceNet Query gt Master lt Response Slave 1 Slave 2 DeviceNet network Query gt Response Query gt Slave n Response Figure 41 DeviceNet Cyclic I O Sequence Cyclic messaging can be appropriate for devices such as analog input sensors For example a temperature sensor might use Cyclic messages to report its measurements every 500ms Cyclic messaging can cut down on network traffic while accurately capturing certain types of input measurements This can also be more efficient for the application program in the PLC CPU A Cyclic I O connection can also be used as a heartbeat to provide assurance of a device s continued operation with a Change of State I O connection to the same device used to update its I O state To configure Cyclic I O Messaging for a connection select Cyclic on the Slave Properties menu General Connection 1 Connection 2 Explicit Messages C Disabled m Input Resources C Polled Size 0 bytes C Strobed C cos amp Eig Update Interval Wns fo ms Size 0 bytes I Ack Suppress Cancel Hep Figure 42 Cyclic I O Messaging Screen for a DeviceNet Master Module For input resources specify the number of data bytes the device will send to the master For output resources enter the number of bytes the device will consume from the
81. duct code I O connections etc its connection 1 and connection 2 input states This function is internal to the PLC it does not generate a DeviceNet network message Get Detailed Device Status Example COMMREQ This example COMMREQ does the following Gets the Device Status of the slave with MAC ID 4 from the DeviceNet Master Module Returns the COMMREQ Status to R10 R13 Returns the Device Status to R251 R260 Description 00005 0005 Length of command Data Block For the Get Detailed Device Status COMMREQ always 5 0008 Status segment select Memory type of COMMREQ status word R for this example 8 R 10 Al 12 AQ 16 18 Q 20 T 22 M 6 00000 0000 Reserved o O 00008 0008 Reply segment select Memory type for the reply data R for this example 8 R 10 Al 12 AQ 16 1 18 Q 20 T 22 M 00250 OOFA Reply memory offset Offset within the memory type for the response minus 1 For this example R251 Word offset for memory types 8 10 12 byte offset for memory types 16 18 20 22 10 00009 0009 Reply memory size Maximum size for the reply in words for memory types 8 10 12 in bytes for memory types 16 18 20 22 Maximum 2048 bytes Note For command 9 must be 18 bytes 9 words or more or an error will be returned in the COMMREQ status and the command will be ignored 00004 0004 MAC ID of the network device For this example 4 76 De
82. e Technical Support Email support emea ip ge com Primary languages of support English French German Italian Czech Spanish Asia Pacific Online Technical Support http support ge ip com Phone 86 400 820 8208 86 21 3877 7006 India Indonesia and Pakistan Technical Support Email support cn ip ge com China support jp ip ge com Japan support in ip ge com remaining Asia customers Customer Care Email customercare apo ip ge com customercare cn ip ge com China Table of Contents Contact IMFOFMATION sssscessccsessosscsnons to eu Cuno NELER GRE CEREUS CENONE CERE NE CENONE CENONE CRR ONER ii Tabledi Con onis secere NPM ye Py gy ey yy v MUON OT FAG D E E A AE AE A E A A A A EE E E O A A A E E ix Chapter 1 EPO DU CHION isc ccccccccsesestecscesstecscveseesevsstuesevesevesevsstesevesevesevestesevestvesevestvesevesuvesevestecsevestveuevesteeueventes 1 1 1 Finding Information in this BOOK ccsssscscscscscssssssssssssesesesesssssesesssssssssesesescsescsesesessacsesescacaeacacasacacaces 1 LLI For Detailed Information about DeVICENEL csssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssenssasssssessst 1 1 2 DeviceNet Modules rrecesireri aar ia nan aa AAEE AELE E 2 1 3 DeviceNet Master Module cssssscscscscecssssssssssssssssssesesssesesesesssesssesssesesesssescscsescseacacasasscaseseseseseseneseses 3 13 1 FEON ES a sssecccesccssssnssescesccenssue e
83. e Figure 34 DeviceNet Polled O SGU CN CC scccecceccccscecceeesecceeceeeeeceeceeeeeceseececececeeeececceesbeeseeeeeeeeeeseeceeeeeeeeeeeeesccsscccts asdsssssssssssssisieeeeeeeeeeeees Figure 35 Polled I O Messaging Screen for a DeviceNet Master MOCUIC csssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssee 36 Figure 36 DeviceNet Stroged VO Seguente czscsscscssscsscccccssestsccseseccecesdceceeccccecescececeeecceeeeeeeeeeeeeeeeeeeeceeeeeeeeeeeesesesseesdsssssssssssssssssssssssssssssssssssssante 37 Figure 37 Strobed I O Messaging Screen for a DeviceNet Master Module ssssssssssssssssssssssssssesssssssssssseessssssstunnnsssssssesseeseeeesiees 37 Figure 38 Device Produces Change of State Message Figure 39 Master Sends Outputs Device REPIIOS ssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssessssssasssssnanssssssssseseed ananassae Figure 40 COS I O Messaging Screen for a Series 90 30 DeviceNet Master Module ccsssssssssssssssssssssssssssssssssssssssssssssssssssssssss 38 Figure 41 DeviceNet Cyclic 1 0 SEQUENCE senori 39 Figure 42 Cyclic I O Messaging Screen for a DeviceNet Master MOCUIC ccsssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssse 39 Figure 43 Explicit Messaging Screen for a DeviceNet Master MOCUIE ccsssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssse 40 GFK 2196B October 2014 Ix Contents Figure 44 Select Slot
84. e and quantity are out of range for this CPU Error communicating with PLC on GET_PLC_RGS service Error communicating with PLC on SET_PLC_RGS service GFK 2196B October 2014 105 Chapter 7 DeviceNet Objects 106 DeviceNet Modules for PACSystems RX3i and Series 90 30 User s Manual GFK 2196B Appendix A DeviceNet EDS Files This section contains the Electronic Datasheet EDS Files that are defined for the DeviceNet Master Module and the DeviceNet Slave Module The content of these files is included for reference only an electronic version of the most up to date EDS file is provided as part of the Proficy Machine Edition programming software The EDS files and any updates are also found on the GE Intelligent Platforms support site http support ge ip com A 1 Electronic Datasheet File for the DeviceNet Master Module DeviceNet Electronic Data Sheet Copyright C 2002 GE Fanuc Automation North America File DescText 90 30 DeviceNet Master CreateDate 06 05 2002 CreateTime 12 59 12 ModDate 10 23 2002 ModTime 12 34 56 Revision 1 04 Device VendCode 326 VendName_ GE Fanuc Automation NA Inc ProdType 12 ProdTypeStr Communication Adapter ProdCode 32 MajRev 1 MinRev 16 ProdName 90 30 DeviceNet Master Catalog IC693DNM200 GFK 2196B October 2014 107 Chapter 7 DeviceNet Objects A 2 Electronic Datasheet File for the DeviceNet Slave Module DeviceN
85. e of State COS I O Messaging is activated only when the device sends a message to the master reporting a change of status The master then sends an output message to the device and the device responds with its input data DeviceNet DeviceNet Master Slave 1 Master Outputs Slave 1 Change of State Message EA Ea 5 5 Slave 2 H Inputs Slave 2 2 2 z z S a i a J e e Slave n Slave n Figure 28 Device Produces Change of State Message Figure 29 Master Sends Outputs Device Replies Change of State I O Messaging is the most efficient type of messaging on the network but it can be less precise than the other methods To configure Change of State I O Messaging for a connection select COS on the slave properties menu Mac ID 1 DeviceNet NCM Slave ID 1 Properties General Connection 1 Connection 2 Explicit Messages C Disabled ep j C Polled Size p bytes C Strobed g ggz Connection Custom z er r Sae Dutput Ack Suppress Size fo bytes Update 0 ms Ci tion Cust X Inhibit Do onnecti ustom Figure 30 COS I O Messaging Screen for a Slave on the Network For input resources specify the number of data bytes the device will send to the master For output resources enter the number of bytes the device will consume from the master If Acknowledge
86. e status Server Status CAN status and firmware ID 7 Master Send Device Explicit Extended version of Send Device Explicit command Extended code 1 Does not have the 238 byte limit and allows separate data area in PLC memory 8 Slave Send Server Explicit Extended version of Send Server Explicit command code Extended 3 Does not have the 238 byte limit and allows separate data area in PLC memory 9 Master Read Module Used to retrieve the detailed status of the client within Header the module 62 DeviceNet Modules for PACSystems RX3i and Series 90 30 User s Manual GFK 2196B Chapter 6 Programmed Communications 6 2 Using COMMREQs to Program Communications A Communications Request begins when a COMMREQ ladder instruction is activated in the PLC application program The CPU sends the COMMREQ to an intelligent module in the PLC system in this case a DeviceNet Master or Slave module The module receives the command and performs the requested function Some COMMREQs for the DeviceNet Master or Slave are used to read or write module data Other COMMREQs cause the DeviceNet module to execute DeviceNet messages on the network In that case the data in the COMMREQ itself includes the DeviceNet message in a format that will be recognized by the DeviceNet recipient s At the conclusion of every COMMREQ the PLC CPU reports the status of the operation into designated a location in CPU memory PLC CPU Ladder program e COMM_REQ CP
87. e to 0 63 Dat som 2 0081 Number of Service Data bytes This needs to be determined from the vendor documentation of the DeviceNet server to which the message is being executed For the example Service Data 0x81 129 bytes 1 byte attribute 128 bytes 32 DINT of data 3 DeviceNet service code See the vendor documentation for the server device In this example the Service is 0x10 Set Attribute Single Service to write data 4 Object Class to which this is requested See the documentation for the server device For this example the object class is 0x04 S2K Assembly Object Instance of the object class to which this request is directed See documentation for the server In this example Instance 768 decimal 0300h points to VIOO1 in the S2K as the first of 32 DINT variables to write Data Byte Offset The number of bytes between this word and the beginning of the service data to be sent If the offset is 0 the service data is located immediately after this data word at word 7 see below For example if the offset were 2 then two bytes would be skipped and the data would begin at word 8 7 LSB Skipped Least significant byte skipped because of setting in word 6 value of word 6 Service Data May be located at a different offset based on word 6 Using the offset in word 6 allowed in this example the DINT data to be aligned on Service Data Byte 0 Attribute An attribute is used in service
88. eNet Cyclic I O Messaging Sequence Cyclic messaging can be appropriate for devices such as analog input sensors For example a temperature sensor might use Cyclic messages to report its measurements every 500ms Cyclic messaging can cut down on network traffic while accurately capturing certain types of input measurements This can also be more efficient for the application program in the PLC CPU A Cyclic I O connection can also be used as a heartbeat to provide assurance of a device s continued operation with a Change of State I O connection to the same device used to update its I O state To configure Cyclic I O Messaging for a connection select Cyclic on the Slave Properties menu Mac ID 1 DeviceNet NCH Slave ID 1 Properties General Connection 1 Connection 2 Explicit Messages C Disabled Input C Polled Size fo bytes C Strobed C cos Connection Custom z Cyl 2 aa Ack Suppress Size fo bytes Update J0 ms Connection Custom z coa He Figure 32 Cyclic 1 0 Messaging Screen for a Slave on the Network For input resources specify the number of data bytes the device will send to the master For output resources enter the number of bytes the device will consume from the master If Acknowledge Suppress flag is selected the DeviceNet master does not wait for an acknowledge message from the device For Update specify the interval in milliseconds at which
89. er Explicit Extended the data to be sent is located in a separate memory area specified by a pointer in the COMMREQ command block This makes it possible to store and send more data Series 90 30 PLC or PACSystems RX3i Controller COMMREQ Command Block DeviceNet network Data to be Sent Send Server Explicit Extended DeviceNet Module Explicit Message Figure 76 Send Server Explicit Extended Transaction Showing Memory Usage 94 DeviceNet Modules for PACSystems RX3i and Series 90 30 User s Manual Client GFK 2196B Chapter 6 Programmed Communications Command Code 3 Send Server Explicit COMMREQ Description For the Send Server Explicit COMMREQ there is no reply to the command Care should be taken to verify the success of the command via the COMMREQ status word You must have the appropriate connection ID from command 2 prior to executing this command Command Length Length of command For this command the length is 5 words plus the number of words of Service Data Note Service Data is in bytes divide by 2 and round up For this example Service Data is 5 bytes 3 Words Always 0 no wait mode request Status segment select Memory type of COMMREQ status word R for this example 8 R 10 Al 12 AQ 16 18 Q 20 T 22 M Status memory offset COMMREQ status word address minus 1 R10 for this example C OOSCSC CSCSCSCSCSCSCSCS Command Code Send Server Explicit 3
90. er module DNM200 does not present valid network status firmware ID inputs unless at least one slave is configured The DNM200 s configuration should always include at least one slave module and the slave module should be present on the network Adding a Device s EDS File If the device you want to configure is not listed and is not in the Toolchest you can provide the EDS file which is supplied by the device manufacturer by clicking Have Disk In the Open dialog box browse to the EDS file and click Open When you select an EDS file using this method it is added to the Slave Catalog and the DeviceNet Devices drawer of the Toolchest GFK 2196B October 2014 er Chapter 3 PLC Configuration for the DeviceNet Master 3 5 Configuring Network Settings for Slaves Added to the Master The Network Settings include MAC IDs baud rates and the messaging connections between devices on the network 3 5 1 Assigning the MAC IDs and Baud Rate Be sure the MAC IDs entered for slaves in the Machine Edition configuration match the MAC IDs set up for the devices themselves Many devices have their MAC IDs set by DIP switches Some have their MAC IDs set by configuration commands from the master All software configured devices originally have the same default MAC ID 63 To configure a software configured device add a generic device with MACID 63 and enable Explicit Messaging to allow the configuration message to be sent to the device Therefore assi
91. eries 90 30 rack systems and modules refer to the Series 90 30 Installation Manual and Hardware Manual GFK 0356 2 4 1 Removing the Module from the Rack To remove the module from the rack 1 Turn off power to rack 2 Remove all cables from the module 3 Press the release located on the bottom of the module and slowly raise the module from the bottom until it comes out of the slot GFK 2196B October 2014 15 Chapter 2 Installation 2 5 Module LEDs The module s three LEDs show its operating and communications status NET POWER O MOD STATUS O NET STATUS O Figure 9 Module LEDs Network Power LED Rd There is no power detected on the network Power detected on the network Module Status LED There is no backplane power to the module The module is operating normally Flashing Green The module is in standby mode Its configuration is missing incomplete or incorrect The module may be in Standby state Flashing Red Recoverable Fault Rd o The module has an unrecoverable fault it may need resetting or replacing Flashing Red The module is in Self Test mode Green Network Status LED The module is not online or The module has not completed the Duplicate MACID test or The module may not be powered See Module Status LED Flashing Green The module is online but has no connections in the established state or The module has passed the Duplicate MACID check is online but has no established co
92. et Electronic Data Sheet Copyright C 2002 GE Fanuc Automation North America File DescText 90 30 DeviceNet Slave CreateDate 06 05 2002 CreateTime 12 59 12 ModDate 10 23 2002 ModTime 12 34 56 Revision 1 04 Device VendCode 326 VendName_ GE Fanuc Automation NA Inc ProdType 12 ProdTypeStr Communication Adapter ProdCode 31 MajRev 1 MinRev 16 ProdName 90 30 DeviceNet Slave Catalog IC693DNS201 108 DeviceNet Modules for PACSystems RX3i and Series 90 30 User s Manual GFK 2196B Index A ACK timeout 23 45 Add Device errors 72 Adding slaves to the network 27 Additional error codes 74 Assembly Object 90 101 B Baud Rate 23 45 Bit strobed I O mode 31 37 49 Bus cable specifications 11 connectors 12 length 12 termination 12 Bus off error detection 55 C Cable connection to module 13 Cable specifications 11 CAN acknowledgment error counter 70 CAN communication error counter 70 CAN lost messages counter 70 CAN Network Status word 70 CAN receive counter 70 CAN receive queue overrun counter 71 CAN status 58 CAN transmit counter 70 Change of State I O mode 32 38 50 COMMREQs 61 1 Send Device Explicit 83 2 Receive Server Explicit 91 3 Send Server Explicit 91 4 Get Detailed Device Status 76 5 Get Detailed Server Status 78 91 6 Get Status Information 80 7 Send Device Explicit Extended 83 8 Send Server Explic
93. et Master modules cannot be installed in remote or expansion racks Environment Storage temperature 40 C to 85 C Operating temperature 0 C to 60 C Backplane Current Consumption 450mA at 5Vdc typical Current Consumption from DeviceNet Network 50mA at 24Vdc typical 80mA at 24Vdc peak Data rates Supports all standard DeviceNet data rates 125K 250K and 500K Baud 1 3 3 Compatibility Compatible with PACSystems RX3i CPUs and NIUs Requires PACSystems firmware release 3 5 or later Compatible with any Series 90 30 CPU except IC693CPU321 and IC693CPU340 Configuration size is limited for CPU311 313 331 as described in chapter 3 Requires Series 90 30 release 8 0 or later CPU firmware Release 10 6 or later is recommended if available for the particular CPU For Series 90 30 CPUs Proficy Machine Edition Logic Developer PLC version 3 0 SP1 Special 2 or later is required For PACSystems RX3i Proficy Machine Edition Logic Developer PLC version 5 5 or later is required Not compatible with the VersaPro Control or Logicmaster programming software The Series 90 30 Hand Held Programmer IC693PRG300 cannot be used to configure this module DeviceNet Modules for PACSystems RX3i and Series 90 30 User s Manual GFK 2196B Chapter 1 Introduction 1 4 DeviceNet Slave Module The DeviceNet Slave Module interfaces a Series 90 30 PLC to a NET POWER Module Devi
94. et Slave Module ccccscssstsstsctsctsstscssctsctsstscsees 108 Index 109 vill DeviceNet Modules for PACSystems RX3i and Series 90 30 User s Manual GFK 2196B Table of Figures FIGURE 13 DOVICENCHINCLW OFK ITAA 7 Figure 2 DeviceNet CONNECTION sce s sis i5 ss sssssscsassssssssssssseassncscnsnsnsnnssssounennsnsgcansnnnnssssauycccddlllcas stoassesnateeecsssnmasaaanesssnnanesennnmenneeesseenmeenunned 12 Figure 3 Determining Drop LONG sszcsccscctccccccccccccccccccsceeececeesececceesescecececcecessccecscessccccscsssseeeseeeeeeeeeeeeeneeeeecta lGsssssssssssssssssssssssssssssssssseeeeeeeeeeeeeeese 12 Figure 4 Network showing Taps Daisy Chains amp BrONCHeS ssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssessssssssnsssssnssessaanaasass 13 Figure 5 Wiring with Terminating Resistor at End Of BUS Truk isisisi 13 Figure 6 Wiring with a Single Connecti Nsessememmmmmm AA 13 Foure T Wining wiin TWO 1COMMECU ONS Secctcccccccccccccccccccccccecscecscssccssscssssssesssssssssssessssceseseeeeeeeeeeeeseeeeeeeececeeeeeccrls fessosssasssssusuuscsssssssctoceccccccccasace 13 Figure 8 Grounding EXAMPIe ssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssessnssessssssssesssssesssesset annie 14 FIGUEES MOGUIO LEDS EEA AAE 16 Figure 10 R5 232 Serial Port D COMMCCEOR cccccs ssssiiesscsssestesccccacscsheschescsecccesessecccccecceeccaccenccsceeceeeecececeateeeeeeetenatttttaath i 17 Figure 11 Sele
95. et Slave Module handles it as described on the previous page for a DeviceNet Master Module 56 DeviceNet Modules for PACSystems RX3i and Series 90 30 User s Manual GFK 2196B Chapter 5 Module Operation 5 3 Fault Table Entries for a DeviceNet Module A DeviceNet module automatically reports fault information to the PLC Fault Table screens MEE ES 129 Statu PLC Date Time 02 11 2000 19 29 42 Fault Table Viewer s Last Cleared 02 11 2000 19 29 32 Online 1 0 Fault Table Displaying 2 of 2 faults 0 Overflowed pues CIRC Ref Fault Category Fault Type Date Time Point Address 1 nja 0 7 2 Disgnostic 131 0 Fault Extra 1 0 Bus Bus Address F Group Action EEE Category IN ata 00 00 00 00 02 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 Fault Description undefined I 00209 Loss of Device 02 11 2000 19 29 47 Point Address 1 n a I o 3 2 Diagnostic 130 o Fault Extra Data Fault Description I O Bus Bus Address Group Action Category Fault Type 00 03 03 00 02 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 undefined Figure 62 PLC Fault Table Display This automatic fault reporting can be disabled by setting the Fault Table Entries parameter in the module s software configuration to False Regardless of whether the information appears in the fault tables status information is available in the module s status references as explained on the next page
96. f a DeviceNet Slave Module Settings tab Mac ID Baud Rate kbps The Mac ID medium access control identification of the slave on the DeviceNet network Valid range 0 63 Default 0 To set this parameter in the DeviceNet Slave Properties dialog box go to the Navigator right click the DeviceNet slave and choose Network Settings The DeviceNet Slave Properties dialog box appears The data transmission rate for the DeviceNet Slave Module The maximum baud rate that can be used depends on the bus length and cable type See chapter 2 for more information Choose 125K 250K or 500K Default is 500 Status Firmware ID Address The starting address for three words of module status information The default is AI memory The Network Status Firmware ID Address must be a non overlapping range in AI l Q G AQ R T or M The default offset is the next available reference in the memory type selected The Firmware ID word contains the current firmware version running on the DeviceNet Master Module The Major Revision number resides in the upper byte and the Minor Revision number resides in the lower byte of this word Length of module status firmware ID Outputs on Loss of Master This is the length of the Network Status Firmware ID Address memory location described above The length is 3 words or 48 bits read only This parameter determines how a slave will handle inputs outputs if the slave loses communicat
97. for their plastic housing DeviceNet Connector PACSystems RX3i DeviceNet Master Module 1 3 1 Features Bus communications at all standard DeviceNet data rates 125k 250k 500k baud Up to 255 bytes input data transfer and 255 bytes output data transfer per slave and up to 3972 bytes of input data transfer and 3972 bytes of output data transfer per master Unconnected Message Manager UCMM with 1 proxy connection per slave One or two O connections plus explicit messaging can be configured for each slave Each slave I O connection can be set up for one of the following Poll Strobe Cyclic or Change of State COS operation Typically one connection is used for Polled and the other is used for Strobe Cyclic or COS Independent configuration of update rates for Poll and COS Cyclic I O devices Configurable global scan rate PLC application initiated Explicit messaging using COMMREQs Status of communication with slaves available in the PLC fault table configurable Provides 64 network device status bits Configurable fault behavior on loss of communication GFK 2196B October 2014 3 Chapter 1 Introduction 1 3 2 DeviceNet Master Module Specifications Catalog Numbers IC693DNM200 IC694DNM200 Description Master Module for DeviceNet networks Mounting Location Series 90 30 PACSystems RX3i Series 90 30 main rack Any slot except slots 0 and 1 RX3i main rack Any slot except slot 0 Note DeviceN
98. from Stop mode to Run mode the DeviceNet Master Module transmits the most recent output data it received from the PLC CPU to nodes on the DeviceNet network If no previous output updates were received the network output data is all zeros 5 1 2 DeviceNet Master Module Operation while the PLC is in Run Mode While the PLC is in Run mode the DeviceNet Master Module communicates with the devices on the network according to their configured connections for polled strobe change of state or cyclic communications The DeviceNet Master Module sends the strobed multi cast message first Devices that have been configured for Strobed I O messaging begin responding in order of their MAC IDs The module then interrogates each device connection that is configured for Polling Polling can begin while strobe responses are being received The module performs this polling sequence as quickly as possible The module interrogates devices that have been configured for Cyclic communications according to their configured update rates The devices then respond with their present inputs Network devices configured for Change of State communications send the master a message only when their status changes After receiving a Change of State message from a device the master sends a request to the device The device responds with its new data The DeviceNet Master Module stores data it receives from the network in its own memory During normal operation the C
99. gning the MAC ID 63 to be used by a device on the network should be done carefully to prevent duplicate MAC ID conflicts when adding a new slave Because all software configurable slaves originally have the same default MAC ID such slaves should be connected to the network one at a time As each new slave is connected its MAC ID should be changed using a Send Device Explicit COMMREQ and its operation should be checked before connecting the next slave Remember that the device will take on the new MAC ID after the configuration message is sent to it Configuring the MAC ID of a Slave Device On the Network Settings General tab configure the device s MAC ID The MAC ID will default to the next available address but will not fill in skipped addresses The dropdown list displays MAC IDs that have not been used in the Machine Edition configuration In this example IDs 2 and 3 have already been assigned so those numbers do not appear in the list Mac ID 1 DeviceNet Network Interface Slave ID 1 Properties x General Connection 1 Connection 2 Explicit Messages Name Mac ID 1 DeviceNet Network Interface Mac ID 1 z z Description DeviceNet Network Interface Product Code j 60 Vendor ID Device Type pe Figure 23 Configuring the MAC ID of the Slave Name A field is provided to give the slave an identifying name Description A field is provide to add a description of the slave
100. hat will be consumed by the DeviceNet Slave Module This power will be used for module operation Input Data Area Output Data Area Power Consumption lt gt 24VDC Isolated We Figure 50 Power Consumption Tab for DeviceNet Slave Module The DeviceNet Slave Module also draws power for its DeviceNet transceiver from the 24Vdc power supply on the DeviceNet network 46 DeviceNet Modules for PACSystems RX3i and Series 90 30 User s Manual GFK 2196B Chapter 4 PLC Configuration for the DeviceNet Slave 4 4 Configuring the Network Settings of a DeviceNet Slave Module To configure the Network Settings for a DeviceNet Slave Module right click the DeviceNet Slave in the PLC configuration and choose Network Settings The Network Settings dialog box appears General Connection 1 Connection 2 Explicit Messages Name Series 90 30 DeviceNet Slave Mac ID fo z Description Card Type JDN 3030 SLAVE Baud Rate 500 z kbps OK Cancel Help Figure 51 Configure Network Settings for DeviceNet Slave The General tab allows setting a name and description for the module On this tab you can also select the MACID and Baud Rate These parameters are also found on the Configuration Parameter screen they can be set in either place The rest of the tabs set up the messaging connections that will be used by the module Configuring the MAC ID All software configured device
101. ing them to send back their inputs is a 1 byte message It reflects the state of the I O bit in the strobe request message for the device set 1 or clear 0 GFK 2196B October 2014 Sa Chapter 3 PLC Configuration for the DeviceNet Master Configuring a Change of State COS I O Messaging Connection A connection configured for Change of State COS I O Messaging is activated only when the device sends a message to the master reporting a change of status The master then sends an output message to the device and the device responds with its input data DeviceNet DeviceNet Master Slave 1 Master Outputs Slave 1 Change of State Message EA Ea 5 5 Slave 2 H Inputs Slave 2 2 2 z z gt gt a e e e e e Slave n Slave n Figure 38 Device Produces Change of State Message Figure 39 Master Sends Outputs Device Replies Change of State I O Messaging is the most efficient type of messaging on the network but it can be less precise than the other methods To configure Change of State I O Messaging for a connection select COS on the slave properties menu General Connection 1 Connection 2 Explicit Messages C Disabled m Input Resources Polled Size fo bytes C Strobed Cos C Cyclic Update Interval pinea fo ms Size fo bytes I Ack Suppress a e Figure 40 C
102. inuously sent over the RS232 port at 19200 baud N81 Status flags and information update to cause a PLC fault table entry Backplane communication continues possibly limited in order to service the PLC COMMREQ command 9 to read header data For specific errors listed below that do not have any source code information available the value OxFFFF is placed in the Main Code and one of the listed error numbers is placed in the Additional Code field Fatal errors that can report source code location store the source file number in Main Code and the source line number in Additional Code sae pror Error Description 1 RAM data test failed An error occurred during testing of the RAM data bus Return the module for repair 2 RAM address test failed An error occurred during testing of the RAM address bus Return the module for repair 3 RAM A16 address test An error occurred during testing of the RAM A16 signal Return the failed module for repair 4 RAM A17 address test An error occurred during testing of the RAM A17 signal Return the failed module for repair 5 Module checksum is The most likely cause of this error is an undetected memory failure If invalid this error occurs with more than one application module the module should be returned for repair 6 CAN reset flag failed to An error occurred testing the CAN controller Return the module for clear repair 7 CAN data test
103. ions status events loss and re establish occur the DeviceNet Master Module can either report them in the fault table or not If this setting is True the default the Master makes fault table entries If this setting is False slave status events are not reported to the fault table Ack Timeout ms Number of milliseconds to wait for a Controller Area Network CAN acknowledge of the Duplicate MacID check performed during startup before reporting an Ack acknowledge failure Valid range 0 to 65 535 The default is 2 000ms 2 seconds Baud Rate kbps The data transmission rate for the DeviceNet Master Module The maximum baud rate that can be used depends on the bus length and cable type See chapter 2 for more information Choose 125K 250K or 500K Scan Interval ms for Strobed connections The time interval between successive scans of Strobed slave connections This defaults to zero A time must be specified if any slave connections are set up for strobing The valid range is 0 to 65 535ms All strobed connections will be scanned at this same interval Reconnect Time ms If a slave fails to respond to three consecutive scan cycles the slave is flagged as not present and the master tries to reconnect to it This parameter specifies how long the master should wait before attempting to reconnect The default time is 100 for RX3i 0 for Series 90 30 The valid range is 0 or 100 to 65535ms Download Names
104. ions with the master The default is Hold Last State It can be changed to clear Network Settings Double click to edit the network communications settings of the slave See Configuring Network Settings in this chapter for more information Program Mode Transmission When the PLC is in Program mode Stop mode the module can either send idle packets or data to zero The default is to send idle packets Fault State Transmission When the module detects a PLC fault the module can either send idle packets or set data to zero The default is to send idle packets Entries Slave Status Fault Table When slave communications status events loss and re establish occur the DeviceNet Master Module can either report them in the fault table or not If this setting is True the default the Master makes fault table entries If this setting False slave status events are not reported to the fault table Ack Timeout ms GFK 2196B Number of milliseconds to wait for a CAN Acknowledge of the Duplicate MacID check performed during startup before reporting an Ack acknowledge failure Valid range 0 to 65 535 The default is 2 000ms 2 seconds October 2014 45 Chapter 4 PLC Configuration for the DeviceNet Slave Data Areas Tabs These tabs show the PLC program references assigned to the selected module These reference assignments can be edited or left at their defaults Note that the input data area ta
105. issue alarm to operator increment a fault counter stop the PLC or skip to next message On a success state optionally manipulate the reply data depending on command executed You control where the reply data is located in PLC via the COMMREQ command However it may be prudent to buffer the reply and copy it elsewhere in the PLC only after status is validated as success A buffer is simply a location in PLC memory used to contain the reply data until it is validated to be a result of a successful command When the COMMREQ status 1 the data can be copied to its final location In the event of a failure status the reply data will not be the data you expect and will contain various values describing the failure mode Any time the reply data will be tested as part of the application logic or used as a control value within an application the buffer method is recommended Start over at the beginning a of the command sequence for the next explicit message Caution It is very important that the PLC logic does not set its own reply timeouts on explicit messaging commands If this is done it is possible that the command reply sequence will get out of synch and prevent further proper generation of explicit messages DeviceNet Modules for PACSystems RX3i and Series 90 30 User s Manual GFK 2196B Chapter 6 Programmed Communications 6 3 3 The COMMREQ Status Block for DeviceNet Modules The COMMREQ Status Block is four words long Each sta
106. it Extended 91 9 Read Module Header 68 error detection and handling 65 general information programming recommendations 65 ladder instruction 63 tatus word 67 Configuration Master module 19 Slave module 41 Configuration file errors 72 Configuration size 20 Configuring a DeviceNet Slave Module 42 Configuring DeviceNet Master Module 20 wn GFK 2196B Configuring network devices 27 Configuring network nettings 20 Configuring network settings 28 35 Connection Object 90 102 Connectors 12 COS See change of state CPU fails to read inputs 55 Current limits for cable 10 Custom Explicit Messaging 90 Cyclic I O mode 33 39 51 D Data Areas tab 25 45 Device status bits 60 DeviceNet communications 8 DeviceNet data rates 3 DeviceNet Master Module 3 DeviceNet message field 8 DeviceNet network 7 DeviceNet network power 10 DeviceNet Object 90 100 DeviceNet object class identifier 90 DeviceNet Objects 97 DeviceNet serial number 70 DeviceNet Slave Module 5 Download EDS files 24 Download names and descriptions 24 Drops 13 E EDS File 27 EDS files 107 EDS files downloading 24 Error Code 70 Explicit Messaging 8 Explicit Messaging configuration 34 40 F Fatal Error codes 74 Fatal module error 55 Fault state transmission 23 45 Fault Table entries 23 Fault Table screens 57 Firmware ID 58 Firmware upgrade 17 G Get Detailed Device Status 6
107. lass Object The object class to which this is requested See the vendor documentation for the server device For this example the object class is OxOA Analog Input Point Object aia E Instance The specific instance of the object class to which this request is directed See vendor documentation for the server device For the example the instance ee see which VersaPoint analog channel to set i al 0001 Service Data Byte Offset If the offset is 0 then the service data is located immediately after this data word in memory at word 17 see below The value entered here is the number of bytes between this word and the beginning of the service data For example if the offset were 2 then two bytes would be skipped and the service data would begin at word 18 1792 ler byte s This byte is skipped because the data byte offset in word 16 is a 1 for this example Multiple bytes may be skipped Data in skipped bytes is eater 07 Service Data byte 0 Attribute Attribute is used in service code 0x10 and Ox0E messages The attribute is a one byte field always at byte zero of the service data when used The Attribute field is not used by other message services This byte is the actual beginning of the service data since the data byte offset caused a one byte skip For the example attribute 7 is the VersaPoint Analog Input Point Object Range setting 18 00003 0003 Service Data Offset of the start of this data depends on entry
108. lds motor starters bar code readers drives displays and operator interfaces The network can also link intelligent interface modules such as the VersaPoint DeviceNet Network Interface Unit NIU and the VersaMax DeviceNet NIU An NIU is the network interface for an I O Station of many additional modules The DeviceNet network has a linear structure There is a main trunk line with drop lines routed to the networked devices Power and signals are carried on the same network cable A Series 90 30 DeviceNet module can be connected directly to the trunk cable or installed as an individual drop or as part of a daisy chain drop Master Series 90 30 PLC or Slaves PACSystems RX3i with DeviceNet Master Module Series 90 30 PLC with DeviceNet Slave Module Figure 1 DeviceNet Network GFK 2196B October 2014 4 Chapter 1 Introduction 1 6 DeviceNet Communications for DeviceNet Modules DeviceNet uses the Producer Consumer technique of messaging A device with data produces the data on the network All devices that need data listen for messages When a device recognizes the appropriate identifier it consumes the data A message is not specific to a particular source or destination and one message can be consumed by multiple devices For example one message could control several motor starter modules A DeviceNet message field can range between 0 and 8 bytes Messages longer than 8 bytes are fragmented into packets The DeviceNet modules ass
109. led cos cyclic Cos Disabled polled strobed Cyclic Disabled polled strobed Configuration of each of these connection types is described on the following pages GFK 2196B October 2014 29 Chapter 3 PLC Configuration for the DeviceNet Master Configuring a Polled I O Messaging Connection In Polled I O mode the most common method of doing 1 0 the DeviceNet master automatically sends a message containing outputs to each slave with a connection configured for polling The slave sends back a response containing input data Polling therefore requires 2 messages to update the I O data for each polled device The master completes the polling sequence as quickly as possible Polling is the most accurate but least efficient method of updating I O data It is most suitable for high availability control data that is used to drive application logic DeviceNet Query Master Slave 1 Response Query Slave 2 Response DeviceNet network Query Slave n Response Figure 24 DeviceNet Polling Sequence To configure polling for slave connection 1 or connection 2 select Polled on the Slave Properties menu Mac ID 1 DeviceNet NCM Slave ID 1 Properties General Connection 1 Connection 2 Explicit Messages gt Input Size fo bytes Connection Custom z p Output a j Si fo b Update 0
110. master If Acknowledge Suppress flag is selected the DeviceNet master does not wait for an acknowledge message from the device For Update specify the interval in milliseconds at which the DeviceNet master will update data for a network device To select the fastest update rate possible enter zero GFK 2196B October 2014 39 Chapter 3 PLC Configuration for the DeviceNet Master 3 6 2 Configuring DeviceNet Explicit Messaging Explicit Messaging is the highest priority messaging Explicit messaging provides access to objects other than the default I O connection set and optionally creates a buffer for explicit connection Not all slaves support explicit services and many including most discrete I O devices do not use explicit services Some devices rely on Explicit Messaging for configuration of selected parameters For example some VersaPoint modules can be configured using Explicit Messaging To be configured by Explicit Messaging an Explicit Messaging connection to the device must first be set up as shown below If Explicit Messaging should be enabled click on Enable Explicit Connection on the Explicit Messages tab In addition for a DeviceNet Slave Module or DeviceNet Master module operating as a slave specify the message request and message response size Make sure the size specified is large enough The DeviceNet modules implement Explicit Messaging through the use of COMMREQ instructions in the application program These
111. mode state Reserved 0x1A 1E Reserved by DeviceNet OxOE Request to modify a non modifiable Ox1F Vendor specific error attribute was received Permission privilege check failed 0x20 Invalid parameter 88 DeviceNet Modules for PACSystems RX3i and Series 90 30 User s Manual GFK 2196B Chapter 6 Programmed Communications Word Description 0x10 Device s current mode or state 0x21 CF Reserved prohibits the requested service 0x11 Data to be transmitted is larger OxD FF Vendor specific object and class errors than the allocated response buffer Values above OxFF are internal DeviceNet Master Module codes see below 0x0100 Explicit connection is not established 0x0101 Explicit body format cannot represent requested class i e class gt 255 and m connection body format is 8 8 or 8 16 Explicit body format cannot represent requested instance i e instance gt 255 and connection body format is 8 8 or 8 16 Resources not available to send explicit message 0x0104 FFFF Reserved 6 end Optional data as required by the service The size of this data is indicated by word 4 GFK 2196B October 2014 89 Chapter 6 Programmed Communications 6 9 Command Codes 2 3 amp 8 Reading and Responding to Client Explicit Messages A client on the network may send DeviceNet explicit messages to a DeviceNet Slave Module or to a DeviceNet Master Module when explicit messaging is enabled for the server
112. ne CAN interface has been initialized 28 N acknowledgment error counter Increments if a transmit message is terminated due to lack of acknowledgment from other stations When this counter is incremented the CAN transmit counter word 27 is decremented to compensate for a message not actually transmitted CAN receive counter Increments when messages are received Messages that fail the receive filter still increment this counter 31 N lost messages counter Increments if a CAN message is received before the previous message is i placed into the receive queue 70 DeviceNet Modules for PACSystems RX3i and Series 90 30 User s Manual GFK 2196B Chapter 6 Programmed Communications 34 63 When Module Type in word 2 is DN contains the module identification string For example DeviceNet Module 1 00 00 n C 2002 GE Fanuc Automation The format is major rev minor rev build When Module Type is ER contains the kernel error string Major Tick Interval equivalent of system time base Number of minor ticks per major tick interval GFK 2196B October 2014 71 Chapter 6 Programmed Communications Headend Fault Codes in the Module Header After a headend fault word 2 of the Read module header reply data DN 0x444E the Main Error Code word 25 and Additional Code word 33 fields of the reply data describe the fault A zero value in the main error code word indicates no error Category Main Additional a
113. nnections with other nodes The module is online and has one or more connections in the established state Flashing Red One or more I O Connections are in the Timed Out state Rd o The module is not capable of communicating on the network Flashing Red The module has detected a Network Access error and is in the Communication Faulted Green State 16 DeviceNet Modules for PACSystems RX3i and Series 90 30 User s Manual GFK 2196B Chapter 2 Installation 2 6 RS 232 Serial Port The RS 232 serial port is a 9 pin male D connector This port is used for a computer connection during firmware upgrades SERVICE RS232 5 IGNDIT Po Oo 3 TxD 120 2 RxDI fo Figure 10 RS 232 Serial Port D Connector 2 6 1 Upgrading Firmware in the DeviceNet Module When upgrades to the firmware are made available the module can be upgraded as described below 1 Download the firmware upgrade to the computer that will be used to perform the upgrade Firmware upgrades are usually available from the GE Intelligent Platforms support site http support ge ip com 2 Connect a straight through serial cable from the computer to the serial port on the front of the DeviceNet module Only the RX and Tx lines are used The cable that is part of the RS232 to RS485 kit IC693ACC903 is suitable 3 The computer can use any standard communication software to communicate with the module The module supports 19200 baud no parity 8 data bits 1 sto
114. ocated gt lt gt gt o allocated Not ie ses a these bits should be ignored GFK 2196B October 2014 79 Chapter 6 Programmed Communications 6 7 Command Code 6 Getting Input Status from a Device To read the information normally mapped to a DeviceNet Module s 3 status words plus all the information normally mapped to the DeviceNet Master Module s 64 device status bits use COMMREQ 6 Get Status Information COMMREQ 6 is alternate way to access this information The module responds to the command with the following information the network activity status of each MAC ID on the network the module s own configured Network Settings the module s current network status the module s firmware ID The information read by this command comes directly from the module this command does not generate a DeviceNet message PLC PLC Get Status Master or Application Information Slave Program Module Figure 68 Get Status Information Transaction Get Status Information COMMREQ Example This example COMMREQ does the following Gets status information from the DeviceNet master Returns the COMMREQ Status Words to R10 R13 Returns the Device Status to R251 R260 1 00004 0004 Length of command Data Block PP PON FRerSetstotcinrmoton thelengthistworsiebytes Status segment select Memory type of COMMREQ status words R for this example 8 R 10 Al 12 AQ 16 1 18 Q 20 T 22 M
115. ode Node Node fli Le Figure 3 Determining Drop Length 12 DeviceNet Modules for PACSystems RX3i and Series 90 30 User s Manual GFK 2196B Chapter 2 Installation 2 2 4 Network Termination 121 Ohm 1 watt terminating resistors MUST be installed at both ends of the DeviceNet network Each terminating resistor is placed across the data communication signals at pin 2 CAN_L and pin 4 CAN_H 2 2 5 Taps Daisy Chaining and Branches Devices can be connected directly to the trunk cable or to drop lines that are joined to the trunk cable with taps Taps can be mounted in junction boxes or panels Drop lines and daisy chains are often used inside control panels where multiple devices are grouped together When using drops with daisy chains and branches the maximum length from a tap to its farthest drop is 20 feet Trunk Line Node Node Drop Lines Node Node Node Figure 4 Network showing Taps Daisy Chains amp Branches Wiring to the DeviceNet Master module depends on its location on the network If the DeviceNet module is located at either end of the bus trunk it is wired with one cable connection and a terminating resistor Figure 5 Wiring with Terminating Resistor at End of Bus Trunk GFK 2196B If the module is installed at the end of a drop or drop segment it is
116. on the module and network status data and module firmware ID will be stored in this memory location Length of network status firmware ID read only Length of the Network Status Firmware ID Address memory location three words 22 DeviceNet Modules for PACSystems RX3i and Series 90 30 User s Manual GFK 2196B Chapter 3 PLC Configuration for the DeviceNet Master Settings tab Program Mode Transmission When the PLC is in Program mode Stop mode the DeviceNet Master Module can either send idle packets or set data to zero The default is to send idle packets Fault State Transmission When the DeviceNet Master Module detects a PLC fault because the PLC has not requested its regular I O update from the module the module can either send idle packets or set data to zero The default is to send idle packets Inputs Default RX3i Inputs on Loss of Slave Series 90 30 If the DeviceNet Master loses communications with a slave it can hold the module s input reported to the CPU in its last state default or clear the input data Outputs Default RX3i Outputs on Loss of Master Series 90 30 If a slave loses communications with the DeviceNet master it can retain the last output value it has successfully received from the master default or clear the output values from the master Fault Table Entries RX3i Slave Status Fault Table Entries Series 90 30 When slave communicat
117. on when designing the overall system Custom Explicit Messaging Using COMMREQs The COMMREQ commands described in this section allow the PLC hosting the DeviceNet module to reply to custom explicit messages One use of custom explicit messaging is to allow the DeviceNet module to respond to existing client messages or to emulate the response of a particular DeviceNet device template For example the DeviceNet module could emulate the response expected from a DeviceNet motor control center or position controller device The only restriction is that the reserved automatic objects mentioned above may not be used for custom explicit class object identifiers A DeviceNet object class identifier is specified by a numeric value in the range of 1 65535 With just six reserved identifiers there is a lot of room to work with custom explicit identifiers In general use object values higher than 0x64 for custom explicit messages to minimize conflicts with DeviceNet objects in common use Through the use of custom explicit messaging the PLC program can implement application objects and allow other client devices on the DeviceNet network to read and write parameters within these objects The application program in the PLC CPU can read and respond to DeviceNet custom explicit messages as explained below 90 DeviceNet Modules for PACSystems RX3i and Series 90 30 User s Manual GFK 2196B Chapter 6 Programmed Communications How the Module Handles a Cu
118. onssvossossoneds 100 7 4 Assembly ODjOCUs si scsscsss deccccscscecececceczcececececaucccncuccucpcnaucuanencacucacuancnaucnccuaceancuabesabebedenebevepesdbenepenezenedenezers 7 4 1 COSS AtIOUE yareeewemeeeteree eereseeersenererrerierereeet reereTirfeTeert EAE 7 4 2 GOSS SOR VIC AEA Vt sacs cas cacauuccecccerc naa 7 4 3 Instance Attributes 7 4 4 FISEOIM CO SERVICES a EEEE A A 7 5 Connection Object 7 5 1 Class Attributes 7 5 2 Class Services viceeccecescssssesscssssesesssssescssssescssssscessssesesssssscessssusessssssessssessssssscesssuscssssecsssssusessssssessssussssnsessssnseeassnseees 7 5 3 Instance ALtriDULES oc eccceccccceesccssssescsssssescssssescsssssecsssssescssssuecsssssesessssusesssssesessssuscessusessuussssssuesesssstsesssnutsssssssessanee 102 7 5 4 TASEOMC SS CNY COS E E E E EE E 103 7 6 PEC DOTO ODEO Aenean ay eae ae ey AEAEE EE EAE E ERE SEEE 104 7 6 1 E SOY COS AE A 104 7 6 2 Specific INSTANCES ers SS 104 7 6 3 GET_PLC_DATA Service 0X32 s in 104 7 6 4 SE TEPEC DATA SEICE OMS ON tear caececcscccccnsescerceccanecccceccuneesccoceccatseceecercenseseecceccatseceececcunsessceccccatnsas aston 105 Appendix A DeviceNet EDS Files ics ics cssccssfaccscestavsuceasaseucessetacctalatecetatetecataletecatatetecthaletacchaletecthaletecctaletactieletecttlancnaiiens 107 A 1 Electronic Datasheet File for the DeviceNet Master Module uu cect csscsccsssssssscsscsssssssssscssseeees 107 A 2 Electronic Datasheet File for the DeviceN
119. optional logic that can verify successful completion of the Communications Request The FT output is set High if The specified target address is not present for example specifying Rack 1 when the system only uses Rack 0 The specified task number is not valid for the device Data length is set to 0 The FT output can either be connected to another device such as a set coil or can be left open Note If the COMMREQ instruction is executed via a one shot permissive as recommended then the FT output state will only be valid for one PLC sweep The FT output can have these states 64 DeviceNet Modules for PACSystems RX3i and Series 90 30 User s Manual GFK 2196B Chapter 6 Programmed Communications 6 3 COMMREQ Programming Requirements and Recommendations Data must be placed in the Command Block before executing the COMMREQ instruction For some commands additional data areas must also be set up Since the normal PLC sweep order is from top to bottom this should be done ahead of the rung that contains the COMMREQ f you use MOVE instructions to load values into Command Block registers use a Word type MOVE to load a hexadecimal number and an Integer type MOVE to load a decimal number COMMREQ instructions should be enabled by a contact from a transition coil The FT output is held False if the Enable Input is not active If the COMMREQ is enabled by a transitional one shot contact and a fault occurs
120. p bit and no flow control 4 Cycle power to the rack that contains the DeviceNet module 5 Atthe computer press ENTER until you see the initial greeting The greeting indicates that the boot code is waiting for new firmware Initiate an Xmodem send of the module firmware file using your communication software Note You must press the ENTER key immediately after the power is cycled It is recommended you hold down the ENTER key when turning the power back on 6 When it finishes successfully storing the new firmware the module automatically resets and attempts to start the new firmware 7 If the firmware transfer was not successful the greeting screen reappears Retry the transfer On success disconnect the serial cable and cycle power to the rack Note The RX3i CPU will log an Unsupported Hardware fault against the DNM200 when upgrading the DNM200 s firmware This fault can be safely ignored GFK 2196B October 2014 17 Chapter 2 Installation 18 DeviceNet Modules for PACSystems RX3i and Series 90 30 User s Manual GFK 2196B Chapter 3 PLC Configuration for the DeviceNet Master This chapter explains how to add a DeviceNet Master Module to the configuration of the PACSystems RX3i or the Series 90 30 PLC It also explains how to configure communications connections between a DeviceNet Master Module and the DeviceNet network Configuration Steps Adding a DeviceNet Master Module to the PLC Configuration Configuring the P
121. r Status bit bites bits bit bit3 bitz bit3 bito eyte0 res aks cyc cos fres st P J byte 1 Group 2 only I O connections Acknowledge suppress enabled Cyclic I O connection allocated Change of state I O connection allocated Bit Strobed I O connection allocated Polled I O connection allocated Group 2 Explicit Connections Explicit connection allocated Group 3 Connection At least one Group 3 UCMM connection allocated Status Bits Output area 1 receive idle status bit Output area 2 receive idle status bit Server Explicit Request Available Use Receive server explicit command to retrieve the request October 2014 81 Chapter 6 Programmed Communications 82 C onz one Jons fona Jons ot ori ono eom fo po a A eo Jw o byer sa Jos Joo jor e reseve e JR Application Specific Flags Scanner Active at least one connection established Online at 500 Kbaud Online at 250 Kbaud Online at 125 Kbaud Firmware is resetting so DeviceNet I O data is not valid Common Flags BP Bus power present zero if power sense not supported ER CAN communication error Message lost CAN controller receive ISR Receive buffer overrun host app too slow emptying receive queue Transmit failed due to timeout flooded network Transmit failed due to ack error no other nodes connected Network activity detected messages received or transmitted Bus off this node has been disconnected due to excessive errors B
122. r error detection in a ladder program you can use a Greater Than GT compare instruction to determine if the value in the Status Word is negative less than zero If an error occurs the GT instruction s output Q will go high A coil driven by the output can be used to enable fault handling or error reporting logic To dynamically check the Status Word write a non significant positive number outside the range of 0x01 0x0D or OXOE OxFF 0 is typically used into all four of the Status Words each time before its associated COMMREQ is executed If the instruction executes successfully the CPU will write the number 1 in the State status word If the number 1 is present it means that the last COMMREQ executed successfully the 1 is not from a previous execution When multiple COMMREQs are used in the application program scan it is important to verify the successful completion of each one before enabling the next Monitoring the Status Word is one way to accomplish that Corrective Actions for COMMREQ Errors The type of corrective action to take in response to a COMMREQ error depends upon the application If an error occurs during the startup or debugging stage of ladder development you should check the COMMREQ parameters The COMMREQ parameters should also be checked if an error occurs right after a program is modified When an error occurs in a proven application that has been running successfully the problem is more likely to be ha
123. r supplies to consider the PLC power supply and the DeviceNet network power supply 2 1 1 PLC Power A DeviceNet module consumes 450mA at 5Vdc typical from the PLC backplane In a Series 90 30 system a high capacity power supply such as IC693PWR330 or IC693PWR331 is recommended when using these modules especially for CPU models CPU350 or higher or if the PLC includes Ethernet adapters and or multiple DeviceNet modules The PLC power supply load is automatically calculated by the Machine Edition configuration software Additional information about estimating power supply load can be found in the Series 90 30 Installation and Hardware Manual GFK 0356 and the PACSystems RX3i System Manual GFK 2314 2 1 2 DeviceNet Power The DeviceNet modules power their network transceivers from the 24Vdc DeviceNet network power source Linear power supplies are recommended for the DeviceNet power source The DeviceNet power source should not also be used for device power Transients caused by I O devices can cause communications errors and even create bus off conditions The DeviceNet specification recommends using a power tap to connect a power supply to the network The power tap should be appropriately fused for the current capacity of the bus cables The maximum current on the network depends on the cable type The DeviceNet modules consume 50mA typical BOMA peak at 24Vdc from the DeviceNet Network Note The DeviceNet Master module fails during a
124. r with the GE products referenced herein GE may have patents or pending patent applications covering subject matter in this document The furnishing of this document does not provide any license whatsoever to any of these patents GE PROVIDES THE FOLLOWING DOCUMENT AND THE INFORMATION INCLUDED THEREIN AS IS AND WITHOUT WARRANTY OF ANY KIND EXPRESSED OR IMPLIED INCLUDING BUT NOT LIMITED TO ANY IMPLIED STATUTORY WARRANTY OF MERCHANTABILITY OR FITNESS FOR PARTICULAR PURPOSE Indicates a trademark of General Electric Company and or its subsidiaries All other trademarks are the property of their respective owners Copyright 2002 2014 General Electric Company All Rights Reserved Contact Information If you purchased this product through an Authorized Channel Partner please contact the seller directly General Contact Information Online technical support and GlobalCare http support ge ip com Additional information http www ge ip com Solution Provider solutionprovider ip ge com Technical Support If you have technical problems that cannot be resolved with the information in this manual please contact us by telephone or email or on the web at http support ge ip com Americas Europe the Middle East and Africa Online Technical Support http support ge ip com Phone 800 1 433 2682 1 433 2682 EMEA Direct E n aa 420 239015850 See E toll free 800 option is unavailable or if dialing from a mobile telephon
125. rdware Configuration fff Main Rack IC693CHS391 Bl PWR IC693PWR321 Al Slot 1 IC693CPU364 Bl Slot 2 IC6930NS201 S 8 Slot 3 1C693DNM200 WERE Cee amp 2 90 30 DeviceNet Slave Slat 4 Slot 5 Cla Ci Settings Data Areas Power Consumption Figure 17 Data Tab Display Power Consumption Tab 24 DeviceNet Modules for PACSystems RX3i and Series 90 30 User s Manual GFK 2196B Chapter 3 PLC Configuration for the DeviceNet Master Power consumption This read only tab shows the backplane power that will be consumed by the DeviceNet Slave Module This power will be used for module operation Input Data Area Output Data Area Power Consumption 4 gt Figure 18 Power Consumption Display Read Only The DeviceNet Slave Module also draws power for its DeviceNet transceiver from the 24Vdc power supply on the DeviceNet network GFK 2196B October 2014 25 Chapter 3 PLC Configuration for the DeviceNet Master 3 3 2 Configuring Network Settings of a DeviceNet Master Module To configure the Network Settings for a DeviceNet Master Module right click the DeviceNet Master in the PLC configuration and choose Network Settings viceNet System Ei Targetl i Data Watch Lists Eb fii Hardware Configuration Eff Main Rack IC693CHS391 cof PWR IC693PWR321 lt E Slot 1 CE93CPU364 i Slot 2 IC69 Affi Rack 1 IC693CHS392 i fii Rack 4
126. rdware related Check the PLC fault tables for possible additional information when troubleshooting COMMREQ errors 6 3 2 Using COMMREQs for DeviceNet Explicit Messaging When using the COMMREQ commands to send or receive explicit messages it is important to follow the proper sequence of events The DeviceNet explicit message interface is a half duplex interface which means that only GFK 2196B October 2014 65 Chapter 6 Programmed Communications a single command can be in progress per configured device The module always provides a response in the COMMREQ status to an explicit command If the device does not respond the module generates an error response on behalf of the unresponsive device so that the command reply sequence at the PLC level does not get hung up The appropriate sequence is always 66 a b c d e f load a complete COMMREQ command into the configured explicit message transmit buffer memory in the PLC specified by the COMMREQ command Clear the COMMREQ status memory 4 words location indicated by the command to a known cleared state Execute the COMMREQ command in ladder with a transitional permissive one shot The PLC application logic must examine the COMMREQ status for success State 1 or failure State gt 1 If the command does not succeed it always returns a failure status after an appropriate time delay On failure state determine the appropriate action retry the command
127. re 54 DeviceNet Strobed I O Mode SCQUCIM CC i ssssssi sssss 1s 1244400440404444440444sss000s4444444444444444444444444444444444444444444444sss4s0spsuessssssssssssssssssuadies Figure 55 Strobed I O Messaging Screen for a DeviceNet Slave MOQUIE ccsssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssse 49 Figure 56 Device Produces Change of State Message ssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssesssssssssssssnssead saan 50 Figure 57 Master Sends Outputs DEVICE REDIES ssscccccccccccccsccsssscssscssss cccsccsssssssccscscccceccccccececccccccccccccccceccccceccccecceccecescesesadassssosesseeseene 50 Figure 58 COS I O Messaging Screen for a DeviceNet Slave MOUIE sssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssessssssssssssssssse 50 Figure SOS DCVICEN CE CYCHET O SEQUENGE EA sssssssssssssssssssssssssasaasabstaanaast 51 Figure 60 Cyclic I O Messaging Screen for a DeviceNet Slave Module essssssssssessssssssssssessssssssesssnsssssseseesessessuunnnssssseeeeeeeeseeeieee 51 Figure 61 Explicit Messaging Screen for a DeviceNet Slave Module Figure 62 PLC Fault FGDC Di SPIO ceececcceeccceescccccccetsceccccecdecceeececcecccceccescecccccccceccecececceccessessesesesceceseseeee cota ssszascescsssssscssssssssssssssssssssscsssssstesssssssttss4 Figure 65 COMMREQ SOCOM CC e scczzzszzcaittt272zzcczzcesszazzssazazzzeaseeeecesssaazsiaaaazzezasececenszaazsaaaasazssieeeeeescssetasse
128. responds with its input data Devices respond in the order of their MAC IDs beginning with the lowest MAC ID first MAC IDs can be specifically assigned to prioritize O reporting by the slaves DeviceNet Strobe Master Message Response Slave 1 Response Slave 2 Response Slave n DeviceNet network Figure 54 DeviceNet Strobed I O Mode Sequence To configure Strobed I O Messaging for a connection select Strobed on the Slave Properties menu General Connection 1 Connection 2 Explicit Messages e omabed m Input Resources C Polled Size fo bytes Stiobed C cos C Cyclic m Output Resources Size fi bytes Cancel Help Figure 55 Strobed I O Messaging Screen for a DeviceNet Slave Module For input resources specify the number of data bytes the module will send to the master The length for output resources is automatically set to 1 byte The message from the Master to the Slaves telling them to send back their inputs is a 1 byte message It reflects the state of the I O bit in the strobe request message for the device set 1 or clear 0 GFK 2196B October 2014 49 Chapter 4 PLC Configuration for the DeviceNet Slave Configuring a Change of State COS I O Messaging Connection A connection configured for Change of State COS I O Messaging is activated only when the module sends a message to the master reporting
129. ro Faste Cia D Ssg g Siot30 Add Module Ins g Slot 100 Replace Module ff Rack 1 IC6S3CHE Delete Module Del fff Rack 2 ICB93CHE fill Rack 3 IC633CHE fill Rack 4 IC693CHS fff Rack 5 IC693CHS a f Rack 6 ICB93CH Lil Rack 7 f1CR93CHS 3921 Figure 21 Associate Slave with DeviceNet Master Module Select the slave type from the list that appears Click OK to 90 30 DeviceNet Slave Major 1 Minor 2 select the slave For example to add a DeviceNet Slave Module as a slave on the network you would select Figure 22 Select Type of Slave You can also drag and drop a device from the Toolchest to the DeviceNet master Open the Toolchest by clicking the Toolchest button on the Tools toolbar Select the DeviceNet Devices drawer Choose a slave device If you are editing a configuration that was uploaded from the PLC the presence of device EDS files and also device names and descriptions depends on the DeviceNet Master Module configuration as described earlier in this chapter If the EDS files and names and descriptions were not downloaded they will not be part of the uploaded configuration and the EDS files may no longer be present in the Toolchest Whether you are adding devices in the Navigator or using the drag and drop method if you don t see the type of device you want to add and also don t have an EDS file for the device you can only configure the slave as a generic device Note The DeviceNet Mast
130. s for DeviceNet operations There is only 1 instance of this object 7 3 1 Class Attributes Supported O Not supported 7 3 2 Class Services Supported O Not supported 7 3 3 Instance Attributes eo MAC ID switch value Baud rate switch value Supported O Not supported 7 3 4 Instance Services Get_Attribute_Single Allocate M S connection set Lee Release M S connection set Le Supported O Not supported 100 DeviceNet Modules for PACSystems RX3i and Series 90 30 User s Manual GFK 2196B Chapter 7 DeviceNet Objects 7 4 Assembly Object Object Class 0x04 Assembly Objects group the data from multiple applications objects into a single message There are up to 4 instances of this object 7 4 1 Class Attributes Description Revision Max Instance Supported O Not supported 7 4 2 Class Services Co Co 6 7 4 3 Instance Attributes Supported O Not supported Only for non Established output connections 7 4 4 Instance Services C Set_Attribute_Single Supported O Not supported Only for non Established output connections GFK 2196B October 2014 101 Chapter 7 DeviceNet Objects 7 5 Connection Object Object Class 0x05 The Connection Object handles the module connection Each Connection Object represents the end points of a connection In an I O message all the information about what to do with the data in the message is contained in the Connection O
131. s originally have the same default MAC ID 63 Therefore assigning the MAC ID 63 to be used by a device on the network should be avoided if possible to prevent duplicate MAC ID conflicts when adding a new slave 4 4 1 Configuring I O Messaging Connections I O Messaging is the term used for the routine and automatic exchange of data between the master and slaves in a DeviceNet system Each configured I O Message defines a dedicated communication path between a producing device and one or more consuming devices Once these connections have been established 1 0 Messaging communications occur automatically during system operation The DeviceNet Slave Module can be set up for up to two different I O Messaging connections Each connection can be disabled the default or set up for Polled Strobed Change of State or Cyclic operation Connections should be configured to meet the needs of the application The selection made for one I O Messaging connection determines which connection types remain available for the other I O Messaging connection as shown by the table below For example you can only select one polling connection for the module Selected for One Connection Available for the Other Connection Disabled Disabled polled strobe cos cyclic Polled Disabled strobed cos cyclic Strobed Disabled polled cos cyclic Cos Disabled polled strobed Cyclic Disabled polled strobed Configuration of each of the
132. s out waiting for a response Therefore the first step in responding to custom explicit messages is for the PLC application program to read the next available custom explicit request it has received from a client device on the network using COMMREQ 2 Receive Server Explicit After reading an explicit message from the DeviceNet module the PLC application program replies to the custom explicit client request using COMMREQ 3 Send Server Explicit for messages up to 238 bytes or COMMREQ 8 Send Server Explicit Extended for longer messages To determine whether the DeviceNet module has completed sending the reply to the custom explicit message the program logic can subsequently use COMMREQ 5 Get Detailed Server Status The reply data to command five indicates whether the module has sent a DeviceNet explicit reply message that was previously commanded by a Send Server Explicit COMMREQ GFK 2196B October 2014 91 Chapter 6 Programmed Communications 6 10 Reading a DeviceNet Custom Explicit Message from the DeviceNet Module The Receive Server Explicit COMMREQ commands a DeviceNet Slave Module or a DeviceNet Master Module in slave mode to return a DeviceNet the most recent explicit client message it has received from the network RX3i Series 90 30 DeviceNet Master or Series 90 30 DeviceNet Slave PLC Module DeviceNet Backplane network PLC CPU Receive Queue of Explicit r i i i i 1 Server ia Message icati ci Expli
133. scoscsoveeseceereceveeteccevedsecteceucustccccetcccsseesccccoia aaa O O 10 2 1 2 DeviceNet POWE annen EEEE E NNN 10 2 2 DeviceNet Cable for the MOodules cssssssssssssssssessssscsssssesssssesesesesssesssesesssesessscsesescacacseseseacacacesasacaces 11 2 2 1 Cable and Network Specifications ccssscsscsssssssssssssssssssssssssssssssssssssssssssssssssessesseeseessessecsssseeseeseseeecsssssssssse 11 2 2 2 BUS Connector PIN ASSIGNMENTS eesssscssssscscsssssssssnnessssesccccescesssssnnuunsssssseceeessssssnnuuuueseseeeeeesssssnuuuuneesesesssanaee 12 2 2 3 BUS WING ccteeceecccececccececccedScceccccecceccceccceccccecceeccceccccccccceeceecceceeccecceceeececececececcessen tassios 12 2 2 4 Network Tennit O eE 13 225 Taps Daisy Chaining and Branches ssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssnsssssnsssnssnnsasssannees 13 2 3 OVON esris aisina ai AEREE AE E E 14 2 3 1 DeviceNet Cable Grounding ssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssnssnsssssnssssssstiuiniinnnnensse 14 2 3 2 DeviceNet Power Supply Grounding o oo cccccccccccccecceececccecccccecececececceeeceeccecceececeeeeeececccccececcceccceeeeceeccsssssssnses aotetos 14 2 3 3 DeviceNet System Grounding GFK 2196B October 2014 v Contents 2 4 Installing the DeviceNet Module in the PLC RACK sssssssssssscssscscscssssssssssessessessssssssssesseecesaceceeeseces 15 2 4 1 Removing the Module from the R
134. se connection types is described on the following pages GFK 2196B October 2014 47 Chapter 4 PLC Configuration for the DeviceNet Slave Configuring a Polled I O Messaging Connection In Polled I O mode the DeviceNet master automatically sends a message containing outputs to each slave with a connection configured for polling The slave sends back a response containing input data Polling therefore requires 2 messages to update the 1 0 data for each polled device ie Master ae gt Slave 1 Slave 2 Response DeviceNet network Slave n Response Figure 52 DeviceNet Polled I O Mode Sequence i To configure polling for slave connection 1 or connection 2 select Polled on the Slave Properties menu Figure 53 Polled I O Messaging Screen for a DeviceNet Slave Module For input resources specify the number of data bytes the DeviceNet Slave Module will send to the master For output resources enter the number of bytes the DeviceNet Slave Module will consume from the master 48 DeviceNet Modules for PACSystems RX3i and Series 90 30 User s Manual GFK 2196B Chapter 4 PLC Configuration for the DeviceNet Slave Configuring a Strobed I O Messaging Connection In Strobed I O mode the master produces a single Strobe request message that is consumed by all devices with a connection configured for strobing requesting their current status Each strobed device then
135. second store of HWC when there is no network power Users should make every effort to ensure that DeviceNet network power is available to the DNM200 when storing Hardware Configuration power cycling the PLC with configuration available in retentive memory reading Hardware Configuration from Flash EEPROM If the module fails because of this issue restore network power and power cycle the rack that contains the DNM200 Current Limit for Thick Cable For thick cable the maximum current on the network is 16 Amps However only 8 Amps is permitted on a single network segment 16 Amps can be drawn from a single power supply by locating the power supply at the center point of two network segments supplying 8 Amps to each segment Current Limit for Thin Cable For thin cable the maximum current permitted is 3 Amps 10 DeviceNet Modules for PACSystems RX3i and Series 90 30 User s Manual GFK 2196B Chapter 2 Installation 2 2 DeviceNet Cable for the Modules DeviceNet modules can be used with the either DeviceNet thick cable or thin cable Thick cable permits greater cable lengths and higher current levels Generally thick cable is used for the trunk cable Thin cable is normally used for shorter distances and is suitable for drop cables and for installations where more cable flexibility is needed Both thick cable and thin cable are 5 wire multi conductor copper cable Two wires form a transmission line for network communications
136. sengasgesssssssaaaasssssnnssssssssssssssaasasensessssssstiooase Figure 64 COMMREQ F nction REDTESCMEQU OM saissisisssscccscccevvsssssszsssszzssesesesenssssassaneeesereeeseoneenariinneaaranen aan SESSE o Figure 65 Read Module Header Trans ction ssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssessaninisniianinnsnsannnnnssnsnnsnsss Figure 66 Get Detailed DEVICE Status TKGNSOCHON istessccssscssscccccssccccceeeeeeeeceeeeeeeeeecesccccecceececceccceecesceesececeesceseesaegeg2eessss2 4 thesassesssnsnsnsssssesasse0 Figure 67 Get Detailed Server Status TrONSACTION sssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssnssssensssssssest aussie Figure 68 GEE STGTUSAMTONMOUON T ONS OCU acses o a o a a o O a SE S S S S E R ERRE ai Figure 69 Send Device Explicit Extended Transaction ecssssssssssssssssssssssssssssee Figure 70 Send Device Explicit Transaction Showing Memory USAGE rrssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssse 83 Figure 71 Send Device Explicit Extended Transaction Showing Memory USAGE rrsssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssse 84 Figure 72 Client Explicit MESSAGES TFGNSOCHON asss EREE 90 Figure 73 Reading CUStOM EXPIIGIt Message TEAM SCCLION S sisuna 92 Figuire 74 Send Server EXDIICI TROMSGCHON A 94 Figure 75 Send Server Explicit Transaction SHOWING Memory USAGE rrssssssssssssssss
137. ssssssseeeesseseesuuusnsssssseseeeeesetemtuustunnssssssseeeeeeeceeeeiuuunnasesseeeeees 98 7 14 Instance Services Message Router Object csssssssssesssesesssesesesssesesssesesesesesesesesssesesesesesesesesesesssesessacsessacaeaeacecseacacacesasecaces 99 7 2 1 COSS ANADULE Sa ce ee 99 7 2 2 CIASS SOPVICES weeeeessssssssssssseesssssssssssseeessesesuunsnsssssseeeeessssesuuunsssessesseeeeesseentuusnssssunsssseeeeeeeeeseesuuuunnssssseeeeeeeseeeeniennnaeet 99 7 2 3 UAVS PAIS cece A A ee A E E E E 99 7 24 Instance SEPVICES sessssssssssssssssssesssssssessssssssssnsssssnsnssnassnsansssaseensanesssnsssansassenessseseseeeaseseesestunnttnnnnnenenenneeneeeeeeeeee 99 GFK 2196B October 2014 vii Contents 7 3 DeviceNet Object ni snnnknscdnadknandnanknandnanknandnaslnandnanlnandnandaandadnkaan 100 7 3 1 Class Attributes wee cecccccssescsssseescssssescsssssescssssescssssssscssssssssssssesessssessssssssccssssuseessesessssueesssuesessssesessssusesssnetessssseees 100 7 3 2 Class Services voc eeccesescssssesscssssesssssssscssssescsssssecessssescsssssssessssuessssssssessssssesssssssesssussssssesesssseseessusessssssessessnssssssnneeessnseees 100 7 3 3 Instance AttriDULOS occ escccceesssssssescsssseescssssscsssssecssssseccsssssessssssesessssusssssssssssssutsessssessuusessssutsesssssessanuessssssesessanee 100 7 3 4 MSANE SONPVICES vscssicsssscsssccssscsosscsonssosossscssssosossscosssosossoseussosossscsessesosssosessosesssosessesosseoesusoassonsavoossssosssvoossus
138. sssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssees 94 Figure 76 Send Server Explicit Extended Transaction SHOWING Memory USAGE csssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssse 94 x DeviceNet Modules for PACSystems RX3i and Series 90 30 User s Manual GFK 2196B Chapter 1 Introduction This manual describes the features and operation of the DeviceNet Master and Slave modules when they are used in a PACSystems RX3i and in a Series 90 30 system 1 1 Finding Information in this Book Chapter 1 Introduction provides basic information about the DeviceNet Master Module IC693DNM200 IC694DNM200 and the DeviceNet Slave Module IC693DNS2011 Chapter 2 Installation discusses power requirements cable specifications grounding module installation and LED indications Chapter 3 PLC Configuration for the DeviceNet Master explains how to add a DeviceNet Master Module to the configuration of the control system It also explains how to configure communications connections the module and the DeviceNet network Chapter 4 PLC Configuration for the DeviceNet Slave explains how to add a DeviceNet Slave Module to the configuration of the control system Chapter 5 Module Operation describes how the DeviceNet Master Module and the DeviceNet Slave Module function in a PACSystems RX3i or a Series 90 30 PLC system Chapter 6 Programmed Communications COMMREQs explains how the application program c
139. stom Explicit Message When the DeviceNet server receives a custom explicit message from the network it stores the messages in an internal queue At any given time up to 255 connections are available in the message queue However this message queue is used by all the client or server message functions within the module For example the DeviceNet Master module s polled connection to a slave is a client connection Any explicit message to the DeviceNet module server from a client device will open an active server connection until that client message is replied to or times out After the connection is idle for a short time 2 3 seconds is typical it is released back to the queue for a subsequent message to use Should the same client device produce a second explicit message to the DeviceNet module before the idle timeout the same connection is reused for the new message Additionally the Server Status word SERA bit is set logically ON for at least one PLC sweep The Server Status word is mapped to PLC I O via configuration and is optionally available via COMMREQ 6 The application should monitor the Server Status word instead of constantly generating command 6 COMMREQs to search for the arrival of a custom explicit message Application logic in the PLC can monitor the SERA bit to determine when a client custom explicit message is present in the queue The PLC application program must process the client message and produce a reply before the client time
140. t Set to 0 if no command was lost Command Error code Meaning Depends on the Command number Command Error Code 0 tReserved a Reserved o e 1 3 7 8 Explicit data too large for shared memory buffer Additional Code word holds the real size of the shared memory buffer 1 4 7 2 invalid MaclD specified 1 2 3 7 8 Explicit connection not configured Explicit request not available 4 Additional code for error reporting GFK 2196B October 2014 67 Chapter 6 Programmed Communications 6 4 Command Code 9 Reading Identification Status and Error Information To read the following information from a DeviceNet Master or Slave module use COMMREQ 9 Read Module Header Module Type Module ID Module revision CAN Kernel identification and revision DeviceNet serial number Error codes for any existing faults CAN Network status This command reads data from the module internal memory no DeviceNet message is sent on the network PLC PLC Read Master or Application Module Slave Program Header Module Figure 65 Read Module Header Transaction Upon detecting an error the PLC application program can send a ReadModuleHeader COMMREQ to the module Unless the error prevents normal backplane operation the module returns information about the fault in the reply data Error codes are listed in this section 68 DeviceNet Modules for PACSystems RX3i and Series 90 30 User s Manual GFK 2196B Chapter 6
141. t 1 to the 4 20mA range 00012 ae Length of command Length of the command block for this COMMREQ For the Send Device Explicit command 1 the command length is 10 words plus the number of words of Service Data The COMMREQ header words 1 6 is not counted in the command length Note Service Data is in bytes divide by 2 and round up for words Service data length will vary depending on message executed consult vendor documentation of the addressed server device For this example 12 words Service Data is 3 bytes rounded up to 2 Words 10 words command length 12 00000 0000 Always 0 no wait mode request Pn pe Gaal Status Segment Select Memory type of COMMREQ status word R for this DeviceNet network Explicit Network Node DeviceNet Master Module Message Gia eee 8 R 10 Al 12 AQ 16 1 18 Q 20 T 22 M ia 0009 Status Memory Offset COMMREQ status words start address minus 1 R10 for this example 00000 0000 6 00000 0000 00001 0001 Command Code Send Device Explicit command number 1 00008 0008 Reply Segment Select Memory type for the reply data R for this example 8 R 10 Al 12 AQ 16 1 18 Q 20 T 22 M 00250 OOFA Reply Memory Offset Offset within the memory type for the reply minus 1 Word offset for memory types 8 10 12 byte offset for memory types 16 18 20 22 For this example it is R251 84
142. t Slave Module or the Server FUNCTION OF a Master MOdUle ccsssscscicstssacsiscesasscacacesssecece cesasacesesouasecusasasndacasssocesesnsacasusedavesosesveseuchsasasaseieses 78 Command Code 6 Getting Input Status from DeViCe ssssesessesesesssssssssssssssssessssssssseseseseseeeces 80 Command Codes 1 amp 7 Sending a DeviceNet Explicit Message on the Network cccsccseeees 83 6 8 1 Send Device Explicit Extended Data Block Fo Mats 87 6 8 2 Send Device Explicit amp Extended Reply Data FOrmat csssesssssssssssssssseeesnsssssseseeessesssseunnssesssseeeee 88 Command Codes 2 3 amp 8 Reading and Responding to Client Explicit MeSSageS ccccceeees 90 Reading a DeviceNet Custom Explicit Message from the DeviceNet Module ccccsssseseees 92 Command Codes 3 amp 8 Replying to a DeviceNet Explicit MESSAGeC ccssssssesessssssesecseceeeeeees 94 7 DeviceNet Objects oie isis ccscicss cc acscug cc scbeucscudlescscnsdetcuend Gave vavd seb dendseud asnan dau dabdcendedadeadsanicenteuidevave 97 id ntity ODjSCt a csscescicisaccseccccctcsctcsctctcsccetcactcsctstenctepenetcnetctenctancacbcnetcdnchapcnepcnanceuncoancpencncncdacpuncocncncncactencnene 98 7 1 1 Class Attributes unaia aE AR EEE EE EEk 98 7 1 2 ESES IN E S 2c ceccceecsezcasesccssscsccecesevsvzssastssssssececeecseevsvsisssassesseceeeeeecevsviiasisissesa oaruenneeeeaneceaneenneemnnaennnes 98 7 1 3 INSTANCE AttriDUTeS eeeessssssessssssmeeessssssssssseeessesssuuss
143. the data to be sent in units of the selected type in words for memory types 8 10 12 in bytes for memory types 16 18 20 22 Must be large enough to contain the entire explicit data block The entire data block calculation is the service data header 12 bytes 6 words skipped bytes specified in word 6 of the service data header the service data Note It is important to know the type of the data used in the service to calculate the minimum length accurately The attribute byte when used is always byte 0 of the service data and must be added to the data length Round size up as needed For this example we have 71 words 6 service data header words 1 skipped byte 1 attribute byte 32 DINT data 64 words service data 86 DeviceNet Modules for PACSystems RX3i and Series 90 30 User s Manual GFK 2196B Chapter 6 Programmed Communications 6 8 1 Send Device Explicit Extended Data Block Format The following data must be placed in the PLC memory location specified in the command by the data memory offset One use of the data byte offset see below would be to point to a start location within a large array of data in the PLC memory In the following example the data byte offset is used to maintain word boundary location of the data within the PLC memory even though we require the service data to contain the attribute value wordt pa pem SSCS Service 0004 MAC ID Address of the device to send the messag
144. the master In an RX3i system a DeviceNet Master Module can be installed in the RX3i main rack only It cannot be installed in any expansion rack In a Series 90 30 PLC the Master Module can only be installed in the main rack A DeviceNet Slave Module can be installed in the main rack in a Series 90 30 PLC Each module counts as a single node on the DeviceNet network However the server function of each module is easily configured for up to two DeviceNet I O Messaging connections and for Explicit Messaging 2 DeviceNet Modules for PACSystems RX3i and Series 90 30 User s Manual GFK 2196B Chapter 1 Introduction 1 3 DeviceNet Master Module The DeviceNet Master Module allows the control system CPU to send A e and receive data over a DeviceNet network It can act as master for EAR Module up to 63 slaves on the DeviceNet network It can also be configured to simultaneously function as a slave to another master on the bus MODSTATUS Status LEDs NETSTATUS The module s three DeviceNet compliant LEDs show its operating A and communications status The RS 232 serial port a 9 pin male DEVICENET D connector is used for a computer connection during firmware Aa upgrades The DeviceNet connector is a removable spring clamp SERVICE RS232 terminal It provides bus continuity and can be removed from the RS 232 module without disrupting bus operation Connector The RX3i and Series 90 30 DeviceNet Master Modules are identical except
145. ting their current status This occurs at the rate selected using the Scan Interval parameter of the DeviceNet Master Module Each strobed device then responds with its input data Devices respond in the order of their MAC IDs beginning with the lowest MAC ID first MAC IDs can be specifically assigned to prioritize I O reporting by the slaves DeviceNet Master Strobe Message Response Slave 1 lt Response Slave 2 DeviceNet network lt Response Slave n Figure 36 DeviceNet Strobed 1 0 Sequence Strobed I O Messaging can be more efficient than Polled I O messaging because the master does not send an individual Poll request to each device Strobed I O Messaging is particularly useful for slave devices that have input data only such as sensors To configure Strobed I O Messaging for a slave connection select Strobed on the Slave Properties menu DN 9030 MASTER Properties x General Connection 1 Connection 2 Explicit Messages C Disabled Input Resources Cc Polled Size fo bytes Strobed C cos C Cyclic M Output Resources Size fi bytes cot nes Figure 37 Strobed I O Messaging Screen for a DeviceNet Master Module For input resources specify the number of data bytes the device will send to the master The length for output resources is automatically set to 1 byte The message from the Master to the Slave tell
146. tus word is data type UINT The status block can be located in any of the supported PLC memory areas The PLC application must set the Status Block contents to 0 before each COMMREQ Word Name Description 1 State The state of the current COMMREQ request 0x00 Module has not yet processed the COMMREQ 0x01 Command Complete Note This status does not necessarily mean success Some commands have reply data that must also be checked 0x02 Busy Command is being processed and has not completed Note It is not guaranteed that the status will transition to busy before complete or terminated 0x03 Command Terminated invalid command 0x04 Command Terminated invalid command data 0x05 Command Terminated not enough data 0x06 Reserved 0x07 Command Terminated not enough memory in reply area The command did not specify sufficient PLC memory for the reply Command will be ignored 0x08 Command Terminated command specific error See Error Code and Additional Code in the Status Block for more information 0x09 Command Terminated invalid COMMREQ Ox0A Command Terminated specific segment selector for COMMREQ reply is not supported Ox0B Command Terminated reply failed to write PLC memory Ox0C Command Terminated specific segment selector for COMMREQ data is not supported 0x0D Command Terminated failed to read PLC memory OxOE to OxFF Reserved 2 Lost Command code of the last command los
147. ure data integrity for each network node 1 6 1 I O Messaging I O messaging is used for the routine and automatic exchange of data between devices Individual I O messages can be up to 255 bytes in length I O messages provide a dedicated communication path between a producing device and one or more consuming devices System configuration sets up the parameters for the connections between the producing and consuming devices With the connections established communications occur automatically There are four basic types of I O messages Polled Strobed Cyclic and Change of State COS The DeviceNet Master Module can be configured for up to two different types of I O messaging connections to each slave for example one Cyclic I O messaging connection and one Change of State I O messaging connection See chapter 3 PLC Configuration for the DeviceNet Master for details 1 6 2 Explicit Messaging Explicit messaging provides a point to point communication link between two devices on the network Explicit messaging is often used for slave configuration and for diagnostics Specific Explicit messages are defined for the DeviceNet protocol For the DeviceNet Master module Communications Requests COMMREQs are used to send Explicit messages See chapter 6 Programmed Communications for more information Received Explicit messages are automatically processed by the DeviceNet module except for user defined Objects which require user programmed COMMR
148. us warning this node is experiencing a large number of errors O Online CAN interface has been initialized L Firmware ID Minor revision In BCD four hex digits For example revision 1 10 01 10 hex Firmware ID Major revision See above DeviceNet Modules for PACSystems RX3i and Series 90 30 User s Manual GFK 2196B Chapter 6 Programmed Communications 6 8 Command Codes 1 amp 7 Sending a DeviceNet Explicit Message on the Network To send a DeviceNet explicit message up to 238 bytes long to a specified device on the network use COMMREQ 1 Send Device Explicit The reply data is limited to 2048 bytes maximum To send more than 238 bytes of data or to use a separate data memory area in the PLC use COMMREQ 7 Send Device Explicit Extended The reply is limited to 2048 bytes maximum Both of these COMMREQs command the DeviceNet Master Module to send a DeviceNet explicit message on the network The addressed device must be configured for an explicit message connection in the configuration of the DeviceNet Master Module and sufficient buffer memory must be configured to contain the largest message produced by the COMMREQ or the largest reply produced by the device It is important to configure the Series 90 30 DeviceNet slave device Network Settings explicit messages tab of the device addressed with enough explicit message size bytes to contain at a minimum all the data specified in the data memory size word 12 of C
149. viceNet Modules for PACSystems RX3i and Series 90 30 User s Manual GFK 2196B Chapter 6 Programmed Communications Get Detailed Device Status Reply Data Format Upon receiving COMMREQ 4 from the PLC CPU the DeviceNet Master Module generates a reply containing the status data it currently has stored for the specified MAC ID aye Status Meaning Status Device not in device list Ox OD Device idle not being scanned Ox OE Error reading I O connection 1 input size Device being scanned Ox OF Invalid I O connection 1 output size Device timed out Ox 10 Error reading I O connection 1 output size UCMM connection error Ox 11 Invalid I O connection 2 input size Master Slave connection set is Ox 12 Error reading I O connection 2 input busy size Ox 06 Error allocating Master Slave Ox 13 Invalid I O connection 2 output size connection set Ox 07 Invalid vendor id Ox 14 Error reading I O connection 2 output size Ox 08 Error reading vendor id Ox 15 Error setting I O connection 1 packet rate Ox 09 Invalid device type Ox 16 Error setting I O connection 2 packet rate Ox OA Error reading device type Ox 17 M S connection set sync fault Ox OB Invalid product code Ox 18 Error setting Production Inhibit Time Ox OC Error reading product code Ox 19 FF 2 Status flags Bits indicating the connection states of the slave s connection 1 and connection 2 high byte inputs Status Oxoa 0x08 xoc TIT gT le a NL
150. y messaging Explicit messaging provides access to objects other than the default I O connection set and optionally creates a buffer for explicit connection If Explicit Messaging should be enabled for the DeviceNet Slave Module click on Enable Explicit Connection on the Explicit Messages tab Also specify the message request and message response size Make sure the size specified is large enough The DeviceNet module implements Explicit Messaging through the use of COMMREQ instructions in the application program These COMMREQ messages are described in chapter 6 Programmed Communications The messages sizes of each explicit message type are described in that chapter Figure 61 Explicit Messaging Screen for a DeviceNet Slave Module 52 DeviceNet Modules for PACSystems RX3i and Series 90 30 User s Manual GFK 2196B Chapter5 Module Operation This chapter describes how the DeviceNet Master Module and the DeviceNet Slave Module function in a control system GFK 2196B Operation of the DeviceNet Master Module Operation while the PLC is in Stop Mode Operation while the PLC is in Run Mode Operation of a Slave Server DeviceNet Module Fault Table Entries for a DeviceNet Module Faults Reported to the I O Fault Table Faults Reported to the PLC Fault Table PLC Status References for a DeviceNet Module Device Status Bits for the DeviceNet Master Module October 2014 53 Chapter 5 Module Operation 5 1 Operation of
151. y slave devices and Poll the remaining slave devices The selection made for one I O Messaging connection to a slave determines which connection types remain available for the same slave s other I O Messaging connection as shown by the table below For example you can only select one polling connection for a device Selected for One Connection Available for the Other Connection Disabled Disabled polled strobe cos cyclic Polled Disabled strobed cos cyclic Strobed Disabled polled cos cyclic Cos Disabled polled strobed Cyclic Disabled polled strobed Configuration of each of these connection types is described on the following pages GFK 2196B October 2014 35 Chapter 3 PLC Configuration for the DeviceNet Master Configuring a Polled I O Messaging Connection In Polled I O mode the most common method of doing 1 0 the DeviceNet master automatically sends a message containing outputs to each slave with a connection configured for polling The slave sends back a response containing input data Polling therefore requires 2 messages to update the I O data for each polled device The master completes the polling sequence as quickly as possible Polling is the most accurate but least efficient method of updating I O data It is most suitable for high availability control data that is used to drive application logic DeviceNet Query Master Slave 1
152. yclic Server Connection Attribute Limits unacknowledged 7 5 4 Instance Services Reset Delete Apply_Attributes Get_Attribute_Single Set_Attribute_Single Supported O Not supported GFK 2196B October 2014 103 Chapter 7 DeviceNet Objects 7 6 PLC Data Object Object Class 0x64 Number of Instances 7 7 6 1 Specific Services Implemented for Service Code Instance Service Name 7 6 2 Specific Instances The DeviceNet modules support access to PLC memory using the following segment selectors The segment selectors are set in the Instance ID of the Explicit request E E oseere Mi osere oree fi E E 7 6 3 GET_PLC_DATA Service 0x32 Service Specific Request Data Offset UINT2 Offset into memory area Units are dependent on Seg_Selector Offset is 1 based not 0 based Length UINT2 Length of data to read Units are dependent on Seg_Selector A maximum of 255 bytes per service request can be read If more than 255 bytes are requested GET_PLC_DATA will return error 0x11 OxFF reply data too large Note The Service Request Data for this service does not include an attribute byte Service Specific Success Response Data On success the Explicit Service field will be set to OxB2 and will contain the following data Name Data Type Description Data Data requested 104 DeviceNet Modules for PACSystems RX3i and Series 90 30 User s Manual GFK 2196B Chapter 7 DeviceNet Objects 7 6 4 SET

DeviceNet Module - GE Intelligent Platforms: Support Home

Contents

Download Pdf Manuals

Related Search

Related Contents