Home

User Manual, Anybus Communicator for DeviceNet

1. Select Command x Ele Command Dg Command Name Select the desired command in the list and select Add Command Command Name in the Command menu The specified command will be added Read Input Status Read Holing Registers to the node eset Sing i i es al Just like other transactions the frame objects of added command xOB Fetch Comm Event Ctr Fetch Comm Event Log may be edited in the Navigation Parameter Section or using the Force Multiple Coils SieveD Transaction Editor Note however that certain frame objects may rite 4X Register be locked for editing ead Write 4X Registers ad FIFO Queue 0x99 My Custom Command 1 0 My Custom Command 2 Anybus Communicator for DeviceNet Doc Rev 3 01 Doc ld SCM 1200 098 8 2 1 Pull Down Menu File This menu features the following entries Select Add the currently selected Command to the node Exit Exit without adding a command to the node Command This menu is used to manage the commands in the list Add Command Add a custom command to the list and open the new command in the Command Editor See also The Command Editor on page 49 Edit Command Edit the currently selected command using the Command Editor See also The Command Editor on page 49 Delete Command Commands 48 Ee Select Exit Ctrl Q Add Command Edit Command Delete Command Delete the currently selected command
2. This object will retrieve its settings from the correspond ing object in the Query By default the Modbus R TU specific frame objects are already in place and a data object is inserted between the function code and the CRC These objects cannot be moved or deleted however it is pos sible to add additional objects between the function code and the CRC as desired Name the new command by entering its name in the Command Name field and enter a suitable func tion code in the Command ID field If the command is allowed to be broadcasted check the Allow Broadcasting checkbox Anybus Communicator for DeviceNet Doc Rev 3 01 Doc Id SCM 1200 098 9 DF1 Protocol Mode Chapter 9 This mode makes it possible to let the Anybus Communicator act as a DF1 protocol master on the sub network 9 1 General In DF1 master mode communication is based on services A service represents a set of commands and operations on the subnetwork that is predefined in the Anybus Communicator Each service is as sociated with a set of parameters controlling how and when to use it on the subnetwork The communication is based on a query response scheme where the gateway issues a query on the sub network The addressed node on the subnetwork is expected to issue a response to that query Nodes are not permitted to issue responses spontaneously i e without first receiving a query Control System Gateway
3. To snap the gateway on first press it downwards 1 to comptess the spring in the DIN rail mechanism then push it against the DIN rail as to make it snap on 2 To snap the gateway off push it downwards 1 and pull it out from the DIN rail 2 as to make it snap off from the DIN rail Connect the gateway to the DeviceNet network Connect the gateway to the serial subnetwork Connect the gateway to a free COM port on the PC via the PC cable Set the DeviceNet baudrate and Mac ID using the on board switches Connect the power cable and apply power QU Qv Ue qe T Start the Anybus Configuration Manager program on the PC Ihe Anybus Configuration Manager attempts to detect the serial port automatically If not suc cessful select the correct port manually in the Port menu 8 Configure the ABC using the Anybus Configuration Manager and download the configuration Anybus Communicator for DeviceNet Doc Rev 3 01 Doc Id SCM 1200 098 About the Anybus Communicator for DeviceNet 15 1 5 Software Installation 1 5 1 Anybus Configuration Manager System requirements Pentium 133 MHz or higher 650 MB of free space on the hard drive 32 MB RAM Screen resolution of 800x600 16 bit colour or higher Microsoft WindowsTM 2000 XP Vista 77 32 bit Internet Explorer 4 01 SP1 or newer Installation Anybus Communicator resource CD Insert the CD and follow the on screen instructions If the installation does not star
4. View diagnostic information about the subnetwork a This function is only available in Master Mode 5 3 Node Parameters 5 3 1 Master Mode and Generic Data Mode To gain access to the parameters described in this section select a node in the Navigation Section Parameter Slave Address Description The value entered here may be used to set the node address in certain commands For more information see The Command Editor on page 49 Anybus Communicator for DeviceNet Doc Rev 3 01 SY Fieldbus A ABC METERS Sub Network Monitor Add Node Add Broadcaster Load Node Sub Network Status gp Fieldbus Aa ABC KH Sub Netwark Y Broadcaster Y ew Mode Doc Id SCM 1200 098 Chapter 6 6 Transactions 6 1 General As mentioned previously transactions ate representations of the actual serial telegrams exchanged on the serial subnetwork While the gateway doesn t feature a scanlist in the traditional sense all nodes and their transactions will be processed in the order they have been defined in the Anybus Configuration Managet Transactions are handled slightly differently in the three protocol modes e Master Mode For regular nodes transactions always come in pairs a query and a response The quety is issued by the gateway while responses are issued by the slaves on the subnetwork The Broadcaster can only send transactions e Genetic Data Mode Transactions
5. A Offline No data exchange 1 Clear the Data Valid bit in the Con trol Registet A Offline no data exchange 2 Write initial data to the Output Area according to the subnetwork configu ration 3 Wait until the fieldbus control system 7 Online not yet exchanging data and the gateway are online on the field bus network and shift to state B B Online Not yet exchanging data 4 Wait until the Data Valid bit in the Status Register is cleared by the gate C way Online F Le exchanging data 5 Set the Data Valid bit in the Control Register 6 When the Data Valid bit in the Status Register is set by the gateway shift to state C 7 If the gateway goes offline on the fieldbus shift to state A C Online Exchanging data Exchanging valid data in both directions If the gateway goes offline on the fieldbus shift to state A Note The gateway cannot spontaneously clear the Data Valid bit in the Status Register Latency The Data Valid bit in the Status Register may in some cases be delayed This latency can be caused by a missing node or a bad connection to a node with a long timeout value assigned to it Therefore the fieldbus control system should not wait for this bit to be set before communicating with the subnetwork devices it should be considered as an aid for the fieldbus control system to know when all data has been updated Anybus Communicator fo
6. Doc Id SCM 1200 098 3 1 1 Pull down Menu File This menu features the following entries e New Create a new configuration See also Configuration Wizards on page 67 e Open Open a previously created configuration e Save Save the current configuration e Save As Save the current configuration under a new name e Print Navigating the Anybus Configuration Manager 25 Mew Open Save Save ds Print Properties Exit Ctrl N Ctri O Ctri 5 Ctri P Send details about the current configuration to a printer e Properties This brings out the following window Item Description Select a Name for the A name for the configuration Configuration may be entered here Download Password 6 These fields can be used to Upload Password 6 password protect the configu ration in the gateway CAUTION Always keep a copy of the passwotd in a safe place A lost password cannot be re trieved e Exit Close the Anybus Configuration Manager Anybus Communicator for DeviceNet Doc Rev 3 01 Download Password 6 ms Name the Configuration selecta Name forthe Configuration My configuration Upload Password 6 p am Doc Id SCM 1200 098 Navigating the Anybus Configuration Manager 26 Tools This menu features the following entries This entry selects the COM port used Port d for the configuration of the gateway Upload configuratio
7. User Manual Anybus Communicator for DeviceNet Doc Id SCM 1200 098 Rev 3 01 44 HITIS Vi Connecting Devices HALMSTAD CHICAGO KARLSRUHE TOKYO BEIJING MILANO MULHOUSE COVENTRY PUNE COPENHAGEN HMS Industrial Networks Mailing address Box 4126 300 04 Halmstad Sweden E mail info hms networks com Visiting address Stationsgatan 37 Halmstad Sweden Web www anybus com Important User Information This document contains a general introduction as well as a description of the technical features provided by the Anybus Communicator including the PC based configuration software The reader of this document is expected to be familiar with PLC and software design as well as communication systems in general The reader is also expected to be familiar with the Microsoft Windows operating system Liability Every care has been taken in the preparation of this manual Please inform HMS Industrial Networks AB of any inaccuracies or omissions The data and illustrations found in this document are not binding We HMS Industrial Networks AB reserve the right to modify our products in line with our policy of continuous product development The information in this document is subject to change without notice and should not be considered as a commit ment by HMS Industrial Networks AB HMS Industrial Networks AB assumes no responsibility for any errors that may appear in this document There are many applications of thi
8. Fieldbus Control System Fieldbus master Frame Object Low level entities which are used to describe the different parts of a transaction Monitor A tool for debugging the Anybus Communicator and the network connections Node A device in the configuration which defines the communication with a node on the subnetwork The network that is logically located on a subsidiary level with respect to the fieldbus and to Sub network which the Anybus Communicator acts as a gateway Transaction A generic building block that is used in the subnetwork configuration and defines the data that is sent and received on the subnetwork User Person or persons responsible for installing the Anybus Communicator Higher Level Network X In this case DeviceNet Network Fieldbus Anybus Communicator for DeviceNet Doc Rev 3 01 Doc Id SCM 1200 098 Sales and Support About This Document P 9 Sales Support HMS Sweden Head Office E mail sales hms se E mail support hms networks com Phone 46 0 35 17 29 56 Phone 46 0 35 17 29 20 Fax 46 0 35 17 29 09 Fax 46 0 35 17 29 09 Online www anybus com Online www anybus com HMS North America E mail us Sales hms networks com E mail us support hms networks com Phone 1 312 829 0601 Phone 1 312 829 0601 Toll Free 1 888 8 Anybus Toll Fr
9. Object Description Implemented Services Class setvices Instance services 15 6 2 Class Attributes Get Attribute Single Get Attribute Single Set Attribute Single Access Name Type Value Description 1 Get Revision UINT 0001h Revision 1 2 Get Max Instance UINT 0001h Max instance number 15 6 3 Instance Attributes Access Name Type Value Description 1 Get Set Acknowledge Timer UINT 16 Time in ms to wait for acknowl edge before re sending 2 Get Set Retry Limit USINT 1 Number of ACK timeouts before retry limit reached event 3 Get Set Producing connection Instance UINT 4 Connection instance which con tains the path of the producing I O application object which will be notified of Ack Handler events 4 Get Ack List Size Byte Max no of members in Ack list 0 Dynamic 5 Get Ack List Array of USINT N A List of active connection instance which are receiving Acks 6 Get Data with Ack Path List Size Byte Max no of members in Data with Ack Path List 0 Dynamic 7 Get Data with Ack Path List Array of USINT N A List of connection instance con suming application object pairs Note Instance 1 is created when using an ACK ed COS Cyclic connection Anybus Communicator for DeviceNet Doc Rev 3 01 Doc Id SCM 1200 098 CIP Object Implementation 82 15 7 Diagnostic Object Class AAh 15 7 1 General Information Object Description This vend
10. When idle RS485 enters an indeterminate state which may cause the serial receivers to pick up noise from the serial lines and interpret this as data To prevent this the serial lines should be forced into a known state using pull up and pull down resistors commonly known as bias resistors The bias resistors form a voltage divider forcing the voltage between the differential pair to be higher than the threshold for the serial receivers typically gt 200mV Note that bias resistors shall only be installed on one node installing bias resistors on several nodes may compromise the signal quality on the network and cause transmission problems B 4 3 Termination RS485 amp RS422 Only To avoid reflections on the serial lines it is important to properly terminate the subnetwork by placing termination resistors between the setial receivers near the end nodes The resistor value should ideally match the characteristic impedance of the cable typically 100 120R B 4 4 Connector Pinout DB9F Pin Description RS232 RS422 RS485 1 5V Output 100mA max Y v v 2 RS232 Rx v 3 RS232 Tx v 4 reserved 5 female 1 5 Signal Ground Y Y Y 6 RS422 Rx v 7 RS422 Rx Y 8 RS485 RS422 Tx v v 9 RS485 RS422 Tx v v housing Cable Shield v v v a Connecting this signal directly to Protective Earth PE of other nodes may in case of grounding loops etc cause damage to the on board serial
11. No programming skills are required instead a visual protocol description system is used to specify the dif ferent parts of the serial communication ME ABC Config Tool Untitled DEAK i File Transactions 1 Tools View Help D gH amp X Devices Configuration qM Fieldbus Alphabetic Categorized ABC Sub Network Ty Nedel Read Coil Status E Query OX E Response m Diagnostics E Query LE Response Node2 Sensor HE Barcodereader SelectAll DeselectAll Y Sensor Transactions 1 Hms Frame Editor TOX Ele Slave Address Function Starting Address Hi Lo Number of points Hi Lo Checksum Value Value Value Value Error check type Error check start byte 0x0000 0x0000 CRC 0x0000 Transactions 1 2005 10 27 09 39 Config Line YA E Collision Trigger or Statusbytes Response Reserved Anybus Communicator for DeviceNet Doc Rev 3 01 Doc Id SCM 1200 098 Basic Operation 17 2 2 Data Exchange Model Internally the data exchanged on the subnetwork and the data exchanged on the higher level network resides ABC Internal Memory in the same memoty i This means that in order to exchange data with the sub p Input Data network the higher level network simply reads and i 512 bytes writes data to memory locations specified using the An ybus Configuration Manager The very same memory locations can then be exchanged on the subnetwork Th
12. Ox04 Write Data E E E E A maximum of 50 services in total for all nodes can be selected The predefined setvices can be configured to suit the application Select a service to show the parameters General Configuration Parameters These parameters are common to all services but the settings are individual to each instance of a service Configuration Alphabetic Categorized General E General Offline options for fieldbus Clear Offline options for sub network Clear Parameter Description Valid settings a RM CR SE LU AAA A A d A E E Timing Offline options for The action to take for this service Clear D Timeout time 10ms 100 fieldbus if the fieldbus goes offline This Freeze Update time 10ms 100 i i E Trigger option affects the data that is sent Noscanning Request Trigger byte address Ox0SFF Response Trigger byte Disabled out to the subnetwork Response Trigger byte address OxD5FF Offline options for The action to take for this service Clear subnetwork if the subnetwork goes offline Freeze This option affects the data that is reported to the fieldbus master Update mode The update mode for this service Cyclically On data change Single shot Change of state on trigger Timing Parameter Description Default Retries The number of times to resend this service before the node is disconnected 3 Timeout time 10 ms The time to wait before resending this service in ste
13. When enabled the data displayed in the Monitor Section will be re freshed cyclically When disabled 1 e stopped the data will have to be refreshed manually using the Refresh icon see below D o Stop Resume e Refresh When clicking on this icon the data displayed in the Monitor Section will be re MH freshed Refresh Anybus Communicator for DeviceNet Doc Rev 3 01 Doc Id SCM 1200 098 Chapter 12 12 Data Logger 12 1 General This feature allows the subnetwork traffic to be logged into a buffer for examination This may provide valuable information when debugging the lowest levels of the subnetwork communication Note that the logger function is part of the gateway itself and 1s separate from the Anybus Configuration Manager This means that logging can be performed even if the gateway is physically disconnected from the PC running the Anybus Configuration Manager 12 2 Operation Start amp Stop Logging e Start logging Select Start Logging in the Tools menu Anybus Configuration Manager will then prompt for the desired mode of operation see below Stoplogging Select Stop Logging in the Tools menu This will open the log window see below Modes of Operation Select the desired mode of operation and click OK to start logging data e Log until full Data will be logged until the log buffer is full e Log continuously togata Data will be logged continuously until lo
14. 1 atus a 32 Mr atus ead Coil Status Out Area 0 bytes 512 General Area 0 bytes 989 C OoOoOoooooooooooooooooooco e Response LE Collision Trigger or Statusbytes Reserved A Start Network amp Stop Network Icons These icons controls the subnetwork activity To stop all subnetwork ier activity click on the red light To start the subnetwork again click on the green light Start B Nodes Transactions To view data blocks associated with a transaction select the transaction in the list The corre sponding data will then appear in the Monitor Section C C Monitor Section This section visualizes how data 1s allocated in the Input Output and General Data areas Color Meaning White Not allocated Yellow Data allocated by a Response or Consume transaction Blue Data allocated by a Query or Produce transaction Red Collision area has been allocated more than once Grey Reserved illustrates memory consumption area can be allocated if necessary Green Data allocated by Trigger byte Transmit Receive Counter or Control Status Registers Anybus Communicator for DeviceNet Doc Rev 3 01 Doc ld SCM 1200 098 Chapter 11 11 Node Monitor 11 1 General The Node Monitor can provide valuable information when setting up the communication with the sub network by allowing individual commands to be issued manually and monitoring the response if ap plicable
15. 4 1 General DeviceNet is based on the Control and Information protocol CIP which is also the application layer for ControlNet and EtherNet IP The input and output data is accessed using I O connections or explicit messages towards the Assembly Object and the Parameter Input Output Mapping Objects See also e CIP Object Implementation on page 74 2 4 2 Data Types The input and output data holds two types of data I O Data and parameter data I O Data is exchanged on change of value and can be accessed using I O connections towards the Assembly Object Parameter data can be accessed acyclically via the Parameter Input and Output Mapping Objects Note however that each instance attribute within these objects must be created manually using the Anybus Configuration Manager For more information see Parameter Data Initialization Explicit Data on page 86 See also e Assembly Object Class 04h on page 78 e Parameter Data Input Mapping Object Class BOh on page 83 e Parameter Data Output Mapping Object Class B1h on page 84 e Fieldbus Settings on page 29 Anybus Communicator for DeviceNet Doc Rev 3 01 Doc Id SCM 1200 098 Basic Operation 23 2 4 3 Memory Layout The I O sizes are specified using the Anybus Configuration Manager and correlates to gateway memory as follows Example In this example the I O Sizes for the gateway have been set to the following values IO Size In 256 bytes 0x0
16. 5 Example Specifying a Modbus RTU Command in Master Mode In the following example a Modbus RTU command is created in Master Mode In Modbus RTU a transaction always feature the following parts e Slave Address 1 byte e Function Code 1 bytes e A data field e CRC CRC 16 Furthermore each command always consists of a query and a response e Example Query DisplayName Slave Address Function Data Checksum Object Type Byte Object Byte Object Data Object Checksum Object Value SlaveAddress ID User User The value of this byte The value of this byte The size and location The checksum type constant will be set using the SlaveAd dress parameter see Node Parameters on page 33 Example Response Response DisplayName Slave Address constant will be set using the Command ID field Function of the data associated with this object is determined by the User Data etc can be selected by the user By default this is set to match the Modbus RTU stan dard Checksum Object Type Byte Object Byte Object Data Object Checksum Object Value SlaveAddress ID User Depend This value is linked to the SlaveAddress parameter in the parameter window The value of this byte constant will be set using the Command ID field The size and location of the data associated with this object is determined by the User
17. C 3 Environmental Characteristics Relative Humidity The product is designed for a relative humidity of 0 to 95 non condensing Temperature Operating 0 C to 55 C Non Operating 25 C to 85 C Anybus Communicator for DeviceNet Doc Rev 3 01 Doc ld SCM 1200 098 Technical Specification 96 C 4 Regulatory Compliance EMC Compliance CE This product is in accordance with the EMC directive 89 336 EEC with amendments 92 31 EEC and 93 68 EEC through conformance with the following standards EN 50082 2 1993 EN 55011 1990 Class A EN 61000 6 2 1999 EN 61000 4 3 199610V m EN 61000 4 6 1996 10V m all ports EN 61000 4 2 1995 8kV Air Discharge T 4kV Contact discharge EN 61000 4 4 1995 2kVPower port 1kVOther ports EN 61000 4 5 1995 0 5kVPower ports DM CM 1kVSignal ports UL c UL compliance The certification has been documented by UL in file E214107 Galvanic isolation on subnetwork interface e EN 60950 1 2001 Pollution Degree 2 Material Group IIIb 250 Vrms or 250 VDCWorking voltage 500 VSecondaty circuit transient rating Anybus Communicator for DeviceNet Doc Rev 3 01 Doc Id SCM 1200 098 Appendix D D Troubleshooting Problem Solution Problem during configuration Upload Download Serial communication failed Try again The Config Line LED turns red in the Anybus Configura tion Manager The serial port seems to be available but it is not possible The ser
18. Checksum ObjectType Byte Byte Checksum Value SlaveAddress ID Depend A Pull down Menu See Pull down Menu on page 50 B Name of Command Actual name of the command in text form C Command Transactions This section holds the actual transactions associated with the command This can either be a que ry response pair or a single transaction depending on the protocol mode etc D Command ID This can be used as desired when building the command e g to specify the function code E Other Settings Setting Description Allow Broadcasting Specifies if it is allowed to broadcast the command only relevant in Master Mode Produce The command is producing data Generic Data Mode only Consume The command is consuming data Generic Data Mode only Anybus Communicator for DeviceNet Doc Rev 3 01 Doc Id SCM 1200 098 Commands 50 8 3 3 Pull down Menu File This menu features the following entries e Apply Changes L3 Save changes and exit to the main window Apply Changes Exit Exit Ctri Q Exit without saving Column The functions in this menu alters the structure of the command Append Column Column h Add another column to the command Append Column Insert Column Shift Ins Delete Column Shift Del e Insert Column Insert a column at the selected position e Delete Command Delete the column at the selected posi tion Anybus Communicator for DeviceNet Doc
19. DF1 functionality 3 01 2011 09 30 KaD All Misc corrections and updates new Anybus Configuration Manager name Anybus Communicator for DeviceNet Doc Rev 3 01 Doc Id SCM 1200 098 About This Document P 8 Conventions amp Terminology The following conventions are used throughout this document e Numbered lists provide sequential steps e Bulleted lists provide information not procedural steps e The term user refers to the person or persons responsible for installing the Anybus Communi cator in a network e The term ABC refers to the Anybus Communicator e Hexadecimal values are written in the format Ox NINNN where NNNN is the hexadecimal value e Decimal values are represented as NNNN where NNNN is the decimal value e As in all communication systems the terms input and output can be ambiguous because their meaning depend on which end of the link is being referenced The convention in this doc ument is that input and output are always being referenced to the master scanner end of the link Glossary Term Meaning ABC Anybus Communicator Broadcaster A protocol specific node in the configuration that handles transactions destined to all nodes DEV DeviceNet Command A predefined transaction Configuration List of configured nodes with transactions on the subnetwork Fieldbus The higher level network to which the communicator is connected
20. Delimiter The parameters in this category differs slightly between the different protocol modes e Master Mode The Message Delimiter specifies the time that separates two messages in steps of 10ms If set to 0 zero the gateway will use the standard Modbus delimiter of 3 5 characters the actual number of ms will be calculated automatically based on the currently used communication settings e Generic Data Mode The Message Delimiter specifies the time that separates two messages in steps of 10us Anybus Communicator for DeviceNet Doc Rev 3 01 Doc Id SCM 1200 098 5 Nodes 5 1 General Chapter 5 In Anybus Configuration Manager a node represents a single device on the network While the gateway doesn t feature a scanlist in the traditional sense all nodes and their transactions will be processed in the order they have been defined in the Anybus Configuration Manager The maximum number of nodes that can be created in the Anybus Configuration Manager is 31 5 2 Adding amp Managing Nodes Right click on Sub Network in the Navigation Section to gain access to these functions Function Paste Description Paste a node from the clipboard z Subnetwork Monitor Launch the subnet monitor Subnetwork Monitor on page 60 Subnetwork Status Add Node Add a node to the configuration Add Broadcaster Add a broadcaster node to the configuration Load Node Add a previously saved node
21. HT LF VT FF CRIS SI 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 DLE DC1 DC2 DC3 DC4 NAK SYN ETB CAN EM SUB ESC FS GS RS US 16 17 18 19 20 21 22 23 24 235 26 27 28 29 30 31 sp i amp a i 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 0 1 2 3 4 5 6 7 8 9 lt gt 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 Q A B C D E F G H J K L M N O 64 65 66 67 68 69 70 71 72 73 T4 75 76 77 TO T9 P Q R S T U V W X Y Z _ 80 81 82 8 84 85 86 87 88 89 90 91 92 93 94 95 a b C d e f g h j k m n 0 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 p q r S t u V Ww X y Z DEL 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 Anybus Communicator for DeviceNet Doc Rev 3 01 Doc ld SCM 1200 098 Anybus Communicator for DeviceNet Doc Rev 3 01 99 Doc Id SCM 1200 098
22. It also provides an overview of the memoty used by a particular node Note The node monitor has a negative influence on the overall performance of the gateway i e it should be used only when necessary The Node Monitor behaves somewhat differently in the three protocol modes e Master Mode and DF1 Master Mode The selected Command Query Transaction or Service is sent to the subnetwork The response to the Query can be monitored in the Response Section Monitor New Node File Node Command Columns View 8sg2 mo Command Section Query Subnetwork Response Section In Area 1 bytes 512 Out Area 1 bytes 512 General Area 0 bytes 1022 e Generic Data Mode The selected command Transaction Produce is sent to the subnetwork It is not possible to monitor any responses etc generated by other nodes Monitor New Node File Node Command Columns View LE 2 738 Wr Command Section Produce Subnetwork Not used In Area 1 bytes 512 Out Area 1 bytes 512 General Area 0 bytes 1022 000 oo Anybus Communicator for DeviceNet Doc Rev 3 01 Doc Id SCM 1200 098 Node Monitor 62 11 2 Navigating the Node Monitor Monitor New Node File Node mmand Columns View EES WS Read Coil Status Query Slave Address Function Starting Address Hi Lo Number of points Hi Lo Checksum Value Value Value Error check type Error check start byte 0x0000 0x0000 CRC 0x0000 Read Coil Status Response Sl
23. Online www anybus co uk Online www anybus com HMS Denmark E mail info anybus dk E mail support hms networks com Phone 45 0 22 30 08 01 Phone 46 0 35 17 29 20 Fax 46 0 35 17 29 09 Fax 46 0 35 17 29 09 Online www anybus com Online www anybus com HMS India E mail in sales anybus com E mail in support hms networks com Phone 91 0 20 40111201 Phone 46 0 35 17 29 20 Fax 91 0 20 40111105 Fax 46 0 35 17 29 09 Online www anybus com Online www anybus com Anybus Communicator for DeviceNet Doc Rev 3 01 Doc Id SCM 1200 098 Chapter 1 1 About the Anybus Communicator for DeviceNet The Anybus Communicator for DeviceNet acts as a gateway between virtually any serial application pro tocol and a DeviceNet based network Integration of industrial devices is enabled without loss of func tionality control and reliability both when retro fitting to existing equipment as well as when setting up new installations 408 ControlNet Master e g a PLC ControlNet Master e g a PLC INVERTER INVERTER ControlNet Network ControlNet Network PC configuration and monitoring PC configuration and monitoring Multi drop up to 31 nodes ye Serial communication E device Serial communication devices Single Node Serial Sub Network Multi Node Serial Sub Network Subnetwork The Anybus Communicator can address up to 31 nodes and supports the following phys
24. Only fieldbuses with specific settings are listed here Step 2 Physical Settings lt a FJ e one cop Select the physical properties of the sub network Click Next to continue LAA Physical standard 2232 y Step 20f6 Bitrate bits s asno Select sub network properties Parity None E Steps 3 6 Data bits g x Stop bits 1 y mt lo Arypus Consult the online help system for fur La DO P 7 This is where the properties for ther information pos device s manual to determine the appropriate settings for a particular serial device lt Back Please see the manual for the sub network device to determine Y Anybus Communicator for DeviceNet Doc Rev 3 01 Doc Id SCM 1200 098 Chapter 14 14 Control and Status Registers 14 1 General The Control and Status Registers are disabled by default but can be enabled using the Anybus Config uration Manager see Status Control Word on page 30 These registers form an interface for ex changing status information between the subnetwork and the fieldbus control system The main purpose of these registers is to e Report subnetwork related problems to the fieldbus control system e Ensure that only valid data is exchanged in both directions e Enable the fieldbus control system to start stop data exchange with selected nodes on the sub network If enabled t
25. Subnetwork Devices Query y Node 1 mm 4 Response Query y mm 4 Response d Node 2 Query y 4 In DF1 Master Mode Anybus Configuration Manager comes preloaded with a number of services that can be selected by the user The actual DF1 commands that perform the services during runtime are predefined in the Anybus Communicator The configuration of the services is performed by right click ing on a node in the Anybus Configuration Manager and selecting Add Command Anybus Communicator for CANopen Doc Rev 3 01 Doc Id SCM 1200 099 DF1 Protocol Mode 54 9 2 ABC Parameters Select ABC in the Navigation Section to gain access to the parameters e TE described in this section 2j 4 Sub Network Interface Currently only serial communication is supported Status Control Word See Control and Status Registers on page 69 VENTE Description Enabled Enable the Control and Status Registers The Data Valid bit in the Control Register must be set to start the subnetwork communication Enabled but no startup lock This setting is similar to Enabled except that the control system is not required to set the Data Valid bit to start the subnetwork communication Disabled This setting completely disables the Control and Status Registers Module Reset This parameter specifies how the gateway will behave in the ev
26. and firmware must be restored in order for it to work properly Start up the Anybus Configuration Manager and connect to the Any bus Communicator Choose Tools Options ABC Click Factory Restore to restore firmware See Tools on page 26 Anybus Communicator for DeviceNet Doc Rev 3 01 sequence starting with one or more red flashes please note the sequence pattern and contact the HMS support department Eo Ec Ec hu d ain Le Doc Id SCM 1200 098 1 3 Configuration Switches The configuration switches are used to set the DeviceNet MacID and baudrate settings a reset for any changes to have effect About the Anybus Communicator for DeviceNet 13 Note that the these settings cannot be changed during runtime i e the Anybus Communicator requires The switches are interpreted as follows Baudrate sw 1 sw 2 125k OFF OFF 250K OFF ON 500K ON OFF reserved ON ON Anybus Communicator for DeviceNet Doc Rev 3 01 Mac ID sw 3 sw 4 sw 5 sw 6 sw 7 sw 8 0 OFF OFF OFF OFF OFF OFF 1 OFF OFF OFF OFF OFF ON 62 ON ON ON ON ON OFF 63 ON ON ON ON ON ON Doc Id SCM 1200 098 About the Anybus Communicator for DeviceNet 14 1 4 Hardware Installation Perform the following steps when physically installing the Anybus Communicator 1 Snap the gateway on to the DIN rail See External View on page 11 The DIN rail mechanism works as follows
27. can be added as desired for both directions Transactions sent to the subnetwork are called Transaction Produce and transactions issued by other nodes are called Transaction Consume e DF1 Master Mode Please refer to DF 1 Protocol Mode on page 53 Theoretically the gateway supports up to 150 transactions The actual number may however be less de pending on the memory requirements of the defined transactions Anybus Communicator for DeviceNet Doc Rev 3 01 Doc Id SCM 1200 098 6 2 Adding amp Managing Transactions Transactions 35 Right click on a node in the Navigation Section to gain access to these functions Function Description Cut Cut a node to the clipboard Copy Copy a node to the clipboard Insert Insert a node from the clipboard Delete Delete a node Node Monitor Launch the node monitor Node Monitor on page 61 Add Transaction s On regular nodes this adds a Query and a Response The two transactions will be grouped in order to increase readability On the Broadcaster a single transaction will be added Add Transaction Consume Add transaction Produce b Add a Consume transaction Add a Produce transaction Add Command Insert New Node Save Node Insert from File Add predefined transactions to the node Insert a new node above the currently selected one Save the selected node Insert a previously saved node above the currently selected nod
28. e hau utet 94 Appendix C Technical Specification Mechanical Properties UP EE 95 Ilecttical Characters CS lala 95 as si e dta T eu Nm dedu rope e MP UN 95 Resulatory Compliance T denn dedi 96 Appendix D Troubleshooting Appendix E ASCII Table Anybus Communicator for DeviceNet Doc Rev 3 01 Doc ld SCM 1200 098 About This Document Preface For more information documentation etc please visit the HMS website www anybus com Related Documents Document name Author ABC DEV Installation Leaflet HMS DF1 Protocol and Command Set Reference Manual 1770 6 5 16 October 1996 Allen Bradley Document History Summary of Recent Changes 3 00 3 01 Change Page s Updated software name Anybus Config Tool to Anybus Configuration Manager Changed the number of possible transactions 34 Updated information about the trigger byte 39 Updated information about the CRC algorithm 46 Updated frontpage information Updated sales and support page Updated System Requirements for Anybus Configuration Manager 15 Revision List Revision Date Author Chapter Description 2 00 2003 12 03 PeP All Second major release 2 01 2004 03 08 PeP 16 Corrected Control Codes 2 50 2006 04 05 PeP All Major update 2 51 2006 12 22 PeP Misc minor corrections amp updates 2 52 2009 04 23 KeL All Misc minor corrections and updates 3 00 2011 02 09 KaD All Misc corrections new template and
29. edit the frame objects in a transaction in a more visual manner using the Transaction Editor see Transac tion Editor on page 40 Data Object Parameters Anybus Communicator for DeviceNet Doc Rev 3 01 Doc Id SCM 1200 098 Frame Objects 42 7 3 Constant Objects Byte Word Dword Constant Objects have a fixed value and come in three sizes e Byte 8 bits e Word 16 bits e Dword 32 bits Constants are handled differently depending on the direction of the transaction e Produce Query Transactions The gateway will send the value as it is without processing it e Consume Response Transactions The gateway will check if the received byte word dword matches the specified value If not the message will be discarded To set the value of the object select it in the Navigation Section and enter the desired value in the Pa rameter section Parameter Description Value Constant value Anybus Communicator for DeviceNet Doc Rev 3 01 Doc Id SCM 1200 098 Frame Objects 43 7 4 Limit Objects Byte Word Dword Limit Objects have a fixed range and come in three sizes Byte 8 bits Word 16 bits Dword 32 bits Limit Objects are handled differently depending on the direction of the transaction Produce Query Transactions This object shall not be used for such transactions value will be undefined Consume Response Transactions The gateway will check if the received byte word dword fits inside
30. of state on trigger Valid settings range from 0x200 OX3FF and 0x400 OxNNN Update mode This parameter is used to specify when the transaction shall be sent to the slave Cyclically The transaction is issued cyclically at the interval specified in the Update time parameter On data change The data area is polled for changes at the time interval defined by Update time A transac tion is issued when a change in data is detected Single shot The Query is issued once at start up Change of state on trigger The Query is issued when the trigger byte value has changed This feature enables the control system to notify the gateway when to issue a particular Query To use this feature correctly the control system must first update the data area associated with the Query transaction then increase the trigger byte by one The location of the trigger byte is spec ified by the Trigger byte address parameter Anybus Communicator for DeviceNet Doc Rev 3 01 Doc Id SCM 1200 098 Transactions 37 Parameter Description Update time 10 ms This parameter specifies how often the transaction will be issued in steps of 10 ms only rele vant when Update mode is set to Cyclically The entered value is multiplied by 10 For instance an entered value of 5 results in 50 ms Anybus Communicator for DeviceNet Doc Rev 3 01 Doc Id SCM 1200 098 Transactions 38 6 3 2 Parameters Response To ga
31. on page 85 A 2 Add a Mailbox Message bg Fieldbus l l l l 3B Startinit To add a mailbox message to the configuration right click on b Fieldbus specific EndInit and select Insert New Mailbox 4 M _ Insert New Mailbox El WH Sub Network This causes the following window to appeat o xj File 1 Header Message Message ID 0x0001 Message information Ox4002 Command 0x0001 Data size 0x0000 This window a k a the Mail Frame count 0x0001 E Frame number 0x0001 box Editor will be used 1n the Offset high Ox0000 7 Offetiow 0 0000 examples later in this chapter Extended Word 1 Ox0000 Extended Word 2 Ox0000 Extended Word 3 Ox0000 ec H 99 AS Rp See also Mailbox Editor on Extended Word 5 Ox0000 Extended Word 6 0x0000 page 85 Extended Word Ox0000 Extended Word 8 Ox0000 Allow user to enable disable Anybus Communicator for DeviceNet Doc Rev 3 01 Doc Id SCM 1200 098 Parameter Data Initialization Explicit Data 87 A 3 Mapping Input Parameter Data to DeviceNet Example In the following example a total of 160 bytes of data will be mapped to the Parameter Data Input Map ping Object The data is made up of 5 separate data blocks each associated with a particular instance attribute To achieve this perform the following steps 1 Add a new mailbox message to the configuration see Add a Mailbox Message on page 86 2 Change the Command value in
32. sage information field that is fixed to 0x4002 which means that only fieldbus specific mail box messages can be entered here a The mailbox message is presented as two col umns one contains header information A Allowuserto enable disable the other one contains the message data B To add message data simply change the Data size parameter in the header column A and the corresponding number of bytes will ap pear in the message data column B For more information about fieldbus specific mailbox messages consult the separate Anybus S Fieldbus Appendix for the fieldbus you are using For general information about the Anybus S platform consult the Anybus S Design Guide Anybus Communicator for DeviceNet Doc Rev 3 01 Doc Id SCM 1200 098 Appendix A A Parameter Data Initialization Explicit Data A 1 General The portion of the input and output data that is declared as parameter data cannot be accessed from the network unless it has been properly initialized The purpose of this procedure is to specify which data blocks in the input and output data areas to as sociate with the instance attributes in the Parameter Data Input Mapping Object and the Parameter Data Output Mapping Object To achieve this it is required to set up two mailbox messages in the Mailbox Editor of the Anybus Con figuration Manager For more information about the Mailbox Editor see Advanced Fieldbus Config uration
33. the mailbox header to 0004h 3 Adjust the Data Size value in the mailbox header left column In this example the size shall be set to 20 0014h since each mapped attribute occupies 4 bytes of mailbox data 4 Specify the mapping locations for the attributes in the mailbox data section As mentioned above each mapping entry needs 4 bytes two bytes specifying the offset of the data block followed by two bytes which specify the length of the data block Note that these values must be entered in big endian Motorola format In this example this gives us the following mailbox data neue ae Attribute no Comments Location Data 0x00 0x00 1 Offset 0000h 0x01 0x00 0x02 0x00 Size 32 bytes 0x03 0x20 0x04 0x00 2 Offset 0040h 0x05 0x40 0x06 0x00 Size 64 bytes 0x07 0x40 0x08 0x00 3 Offset 0080h 0x09 0x80 Ox0A 0x00 Size 16 bytes 0x0B 0x10 0x0C 0x00 4 Offset 0090h OxOD 0x90 OxOE 0x00 Size 32 bytes OxOF 0x20 0x10 0x00 5 Offset OOFOh 0x11 OxFO 0x12 0x00 Size 16 bytes 0x13 0x10 As shown in the table above the attributes are numbered in the order they are mapped i e it is possible to rearrange the attribute numbering by physically changing the mapping order in the mailbox data S To save the new mailbox select Apply changes in the File menu 1 The offset is specified from the start of the parameter data not from the physical mem
34. the specified boundaties If not the message will be discarded There are 3 types of interval objects Byte 8 bit interval Word 16 bit interval Dword 32 bit interval To set the range of the object select it in the Navigation Section and enter the desired range in the Pa rameter section as follows Parameter Description Maximum Value This is the largest allowed value for the range Range 0x00 OxFFh byte 0x0000 OXFFFFh word 0x00000000 OxFFFFFFFFh dword Note Value must be larger than the Minimum Value below Minimum Value This is the smallest allowed value for the range Range 0x00 OxFEh byte 0x0000 OXFFFEh word 0x00000000 OxFFFFFFFEh dword Note Value must be less than the Maximum Value above Anybus Communicator for DeviceNet Doc Rev 3 01 Doc Id SCM 1200 098 Frame Objects 44 7 5 Data Object Data Objects are used to represent raw data as follows e Produce Query Transactions The specified data block is forwarded from the higher level network to the subnetwork e Consume Response Transactions The specified data block is forwarded from the subnetwork to the higher level network To specify the properties of the object select it in the Navigation Section and enter the desired settings in the Parameter section as follows Parameter Description Byte Swapping No Swapping No swapping is performed on the data Swap 2 bytes A B C D becomes B
35. the trigger byte must be specified in the Trig ger byte address below The trigger byte value will be increased each time a valid transaction has been con sumed by the gateway The trigger byte will also be increased if the offline option is set to Clear and the offline timeout time value is reached This feature enables the control system to be notified each time new data has been consumed on the subnetwork Disable Disables the trigger byte functionality Trigger byte address Anybus Communicator for DeviceNet Doc Rev 3 01 This parameter specifies the location of the trigger byte in the internal memory buffer Valid settings range from 0x000 Ox1FF and 0x400 OXNNN Please note that the trigger byte address must be unique to each transaction It can not be shared by two or more transactions Doc Id SCM 1200 098 6 5 Transaction Editor Transactions 40 The Transaction Editor can be used to edit the individual frame objects of a transaction The same set tings are also available in the parameter section of the main window however the Transaction Editor presents the frame objects in a more visual manner Transz on Editor File Byte constant Word constant Data Value Value Data location Data length 0x00 0x0000 0x0200 0x0010 Transaction Y Byte constant Lo ile constant Eram A E Checksum Objects Byte constant LOX i Checksum Byte constant Error check type Error chec
36. 1 VALERO 2072017 TM URN m 81 Dirsnoste Object Glass AM So 82 CR 171012777717 1 e ass 82 SUP rU IA Aita 82 Instance Aroue dusane 0 BEER 82 Parameter Data Input Mapping Object Class DU dto 83 E 07118 17 713 7171 11 OSATEN PE 83 CASARON ITEE EE EAA E E A E cag be Neenah Nea spe 83 TANCE 112 7477 P1 ANNE OT ERR RE E T Radte tealeioaudsd 83 Parameter Data Outout Mapping Object Glass DI sd dia a did 84 E E E E E A T E E ipu 84 ARAS MUR 84 TSAO PATIOS INTACTA A AA A E E EE 84 Anybus Communicator for DeviceNet Doc Rev 3 01 Doc Id SCM 1200 098 Chapter 16 Advanced Fieldbus Configuration OSC 1 E EEE E EET 85 Milbo Edito ts T Rm 85 Appendix A Parameter Data Initialization Explicit Data coc C M 86 Add a IMAI DO Messi Eee uid Hae etu eo E Ea tato bn d bd t tua UE 86 IMappine Input Parameter Data to Device NE tanda 87 Mappine Output Parameter Data to Device Neb us eene oett dt 89 Appendix B Connector Pin Assignments IUe SIC ONGE ONG CLO eter hah ua ob tae ee teas eh ee eters 91 POVE GOMMEGCUO em M ao 91 FE CORN OOT o A E E A EA S 92 Sube ot TAT IOE necia E m fi Du e iadba ian EM UE 93 8771142188171 0777177 AAA AAA AAA E T 93 DIAS IIS AS TATI Fe NE 93 LOMRARIRA RIAS CO dS ZZ A e t NE Tb e esa tuted 93 171705001 9820111774 ID E er KIT DES 93 TYPE C OBEDIRE AS ASAS T IA 94 Typist Connection 834 22 GAVE IM ii A AAA Ad AA ete A Ai 94 DPI AS OREA IND A A oU E E Ut
37. 100 IO Size Out 128 bytes 0x0080 Resulting memory layout Input Data Output Data General Data 0x200 0x400 0x000 I O Data Output 0x27F I O Data Input 0x280 OxOFF 0x100 Cannot be accessed from DeviceNet Parameter Data Output Parameter Data Input Ox1FF Ox3FF 0x22 Anybus Communicator for DeviceNet Doc Rev 3 01 Doc Id SCM 1200 098 Chapter 3 3 Navigating the Anybus Configuration Manager 3 1 Main Window The main window in the Anybus Configuration Manager can be divided into 4 sections as follows ums ABC Config Tool Untitled File Fieldbus Tools View Help D c a Configuration Alphabetic Categorized E Ethernet TCP IP configuration Communicator IP address 192 168 0 1 Default Gateway 0 0 0 0 255 255 255 0 Enabled we Sub Network Y New Node C Read Holding Registers E3 Query EJ Response Preset Multiple Regs L3 Query El Response Subnet Mask TCP IP Settings Fieldbus Fieldbus Type A 10 Sizes IO Sizes Automatic Profinet IO o IO Sizes Sets whether the sizes ofthe IO areas are user defined or automaticly configured 2005 10 24 A Pull down Menus amp Tool Bar The second drop down menu from the left will change de pending on the current context The Tool Bar provides quick access to the most frequently used functions B Navigation Section This section is the main tool for selecting
38. 4 bytes of data will be mapped to the Parameter Data Output Mapping Object The data is made up of 4 separate blocks each associated with a a particular instance attribute To achieve this perform the following steps 1 Add a new mailbox message to the configuration see Add a Mailbox Message on page 86 2 Change the Command value in the mailbox header to 0005h 3 Adjust the Data Size value in the mailbox header left column In this example the size shall be set to 16 0010h since each mapped attribute occupies 4 bytes of mailbox data 4 Specify the mapping locations for the attributes in the mailbox data section As mentioned above each mapping entry needs 4 bytes two bytes specifying the offset of the data block followed by two bytes which specify the length of the data block Note that these values must be entered in big endian Motorola format In this example this gives us the following mailbox data Mailbox Data Attribute no Comments Location Data 0x00 0x00 1 Offset 0020h 0x01 0x20 0x02 0x00 Size 16 bytes 0x03 0x10 0x04 0x00 2 Offset 0050h 0x05 0x50 0x06 0x00 Size 32 bytes 0x07 0x20 0x08 0x00 3 Offset 0070h 0x09 0x70 Ox0A 0x00 Size 32 bytes 0x0B 0x20 0x0C 0x00 4 Offset 00DOh 0x0D OxDO OxOE 0x00 Size 64 bytes Ox0F 0x40 As shown in the table above the attributes are numbered in the order they are mapped i e it is possible to rear
39. A D C Swap 4 bytes A B C D becomes D C B A Data Length The length of the data block in bytes In case of a Response or Consume transaction incom ing messages where the data size differs from the value specified here will be discarded Max imum data length allowed for one frame is 300 bytes Data Location The location of the data block in the internal memory buffer 7 6 Variable Data Object Note Only one Variable Data Object is permitted for each transaction This object is similar to the Data Object except that it has no predefined length Instead an End or Length character specifies the size of the data block as follows Variable Data Object Variable Data Object Data of arbitrary length End Character Length Character bytes of data e Produce Quety Transactions The specified data block will be forwarded from the higher level network to the subnetwork The control system must supply an End or Length character in order for the gateway to know the size of the data block The End or Length character itself may either be forwarded to the subnetwork or discarded e Consume Response Transactions The specified data block is forwarded from the subnetwork to the higher level network The End or Length character will be generated by the gateway automatically if applicable The End or Length character itself may either be forwarded to the higher level network or dis carded Anybus Communicator
40. Add Transaction s p m an JE S These icons are used to add transactions to the currently selected node rr Fm Transactions Transaction Anybus Communicator for DeviceNet Doc Rev 3 01 Doc Id SCM 1200 098 Chapter 4 4 Basic Settings 4 1 Fieldbus Settings a Select Fieldbus in the Navigation Section to gain access to the parame Ae ABC ters described in this section T x cCub Haetwark General During start up the fieldbus interface of the Anybus Communicator is initialized to fit the configuration created in the Anybus Configuration Manager Optionally some initialization parameters can be set manually to provide better control over how the data shall be treated by the gateway Configuration Alphabetic Categorized E Fieldbus Fieldbus Type The Anybus Configuration Manager supports a wide range of net Canto working systems Make sure that this parameter 1s set to Device Net IO Sizes Fieldbus Type These parameters specify how data from the internal memoty Configuration x Alphabetic Categorized buffer shall be exchanged on DeviceNet This can either be han B Fieldbus A Fieldbus Type DeviceNet dled automatically based on the subnetwork configuration or iC T specified manually TA E y Automatic User defined e Automatic All data will be represented as I O Data on DeviceNet e User defined Additional parameter properties appear IO Size In and TO
41. Class services Get Attribute All Instance services Get Attribute Single 15 8 2 Class Attributes Access Name iwpe Value Description 1 Get Revision UINT 0001h Revision 1 15 8 3 Instance Attributes Instance 01h Each attribute corresponds to a block of Input Data Note that the size and location of each block must be specified using the Anybus Configuration Manager For more information see Mapping Input Parameter Data to DeviceNet on page 87 Access Name Type Description 01h Get Data Array of USINT Mapped block if Input Data 02h Get Data Array of USINT Mapped block if Input Data 02h Get Data Array of USINT Mapped block if Input Data 02h Get Data Array of USINT Mapped block if Input Data 02h Get Data Array of USINT Mapped block if Input Data 02h Get Data Array of USINT Mapped block if Input Data 32h Get Data Array of USINT Mapped block if Input Data Anybus Communicator for DeviceNet Doc Rev 3 01 Doc Id SCM 1200 098 CIP Object Implementation 84 15 9 Parameter Data Output Mapping Object Class B1h 15 9 1 General Information Object Description This object can be used to access output data acyclically and is set up dynamically based on the Param eter Data Mailbox initialization see Parameter Data Initialization Explicit Data on page 86 See also e Data Representation on DeviceNet on page 22 e Parameter Data Input Mapping Object Class BOh on pa
42. O sto slit AA pa e be eae te Cu us uer este uuu 48 TA ass 49 GUI asso see cM E M uL LN DIM M uM tue eue e iE 49 5717991571710 TNT 49 PIO ENS 50 1217 7 OR 807775777 COTTE STEREO ORC E T TERN TONS 5 Example Specifying a Modbus RTU Command in Master Mode eee 52 Anybus Communicator for DeviceNet Doc Rev 3 01 Doc Id SCM 1200 098 Chapter 9 DF1 Protocol Mode Ss A TEN EN 53 Eo O TE E E EE E E OT E a da meee 54 Subnetwotrk Paran et ES A os 55 Node Paramete oe 56 SORVICOS E eae hrc eae eee ta ae T T E A E mts 56 A AULAE S IDE ETE E AA A AA A 57 ane udin aa e ARO 58 Read Danos eii so 58 Radiata P 59 NO nica 59 Chapter 10 Subnetwork Monitor Chapter 11 Node Monitor Bs A E MX M MEE M E EE 61 INavisatine the Node Monto unen iio 62 UND OI A aca mc 63 ERAT T EI Soca siete hare cae THERE 64 Chapter 12 Data Logger S eur EA M A S 65 OD EUA 65 Confort tilda dl iia 66 Chapter 13 Configuration Wizards Genre lada 67 oelecuno a Wizard Protein 67 Mazar Modbus RITUM ASt aate tenet pit en on o pn desiit di iore a 68 Chapter 14 Control and Status Registers SI TREO ETUC DER aT TEE 69 VARAS DATO TAO ASADA A AS AA o aono vi D oe E 69 DARE its 70 Status Resister Contents Gateway to COntrolLo VSLOD uo a 71 1714 17 BN OVULATION RR NR MM RT ral Status Codes in Master Mode and DET Master Modest tilde 71 S Code M Gn Dara Mode A RET 72 Control Register Contents Co
43. Offline options for fieldbus Clear Offline options for sub network Clear Update mode Cyclically E Timing Retries Timeout time 10ms Update time 10ms E Trigger Request Trigger byte address OxD5FF Response Trigger byte Disabled Response Trigger byte address OxD5FF Read Diagnostics 2010 05 07 10 53 Config Line Command parameters The command parameter Size decides the amount of data that can be read The size is given in bytes which means that it always has to be an even number as only whole elements can be read from the slave One bit integer element is 2 bytes and one float element is 4 bytes The range of the size differs de pending on node type PLC 5 SLC500 Size range in bytes 1 28 Data options Parameter Description Valid settings Byte swap Determines if the data shall be swapped No byte swap Swap words Swap double words Data length The number of bytes read from the DF1 network to write to the area determined lt Size by the Offset parameter Offset The offset in the internal memory buffer in the module where the data shall be read See Memory Map on page 17 Anybus Communicator for CANopen Doc Rev 3 01 Doc Id SCM 1200 099 9 8 Read Data This service is used to read data from the nodes in the subnetwork ABC DF 1 Master Untitled Configuration Alphabetic Categorized E Comman d Params File Type Siz e E Data Options ine options for fieldbus Cle
44. Rev 3 01 Doc Id SCM 1200 098 B Connector Pin Assignments B 1 DeviceNet Connector Pin Signal Description 1 V DeviceNet bus power negative supply voltage 2 CAN L Can L bus line 3 Shield Cable shield 4 CAN H CAN H bus line 5 V DeviceNet bus power positive supply voltage B 2 Power Connector Pin Description 1 24V DC 2 GND Notes e Use 60 75 or 75XC copper CU wire only The terminal tightening torque must be between 5 7 lbs in 0 5 0 8 Nm Anybus Communicator for DeviceNet Doc Rev 3 01 Appendix B Doc Id SCM 1200 098 Connector Pin Assignments 92 B 3 PC Connector Configuration Cable Wiring DP9F PC RJ11 ABC RJ11 4P4C modular ABC Pin Description 1 Signal ground 2 3 RS232 Rx Input 4 RS232 Tx Output DB9F PC Pin Description q 2 RS232 Rx Input 5 female 1 3 RS232 Tx Output 4 5 Signal Ground 6 9 1 The RJ11 4P4C modular is sometimes referred to as an RJ9 Anybus Communicator for DeviceNet Doc Rev 3 01 Doc ld SCM 1200 098 Connector Pin Assignments 93 B 4 Subnetwork Interface B 4 1 General Information The subnetwork interface provides for RS232 RS422 and RS485 communications Depending on the configuration specified in the Anybus Configuration Manager different signals are activated in the sub network connector B 4 2 Bias Resistors RS485 Only
45. Rev 3 01 Doc Id SCM 1200 098 Commands 51 8 3 4 Editing a Command As mentioned previously the transaction section in the Command Editor represents the actual transac tions associated with the command Each column represents a frame object within the transaction Each column features four rows with the following parameters e Query Response Produce Consume The upper right cell indicates the direction of the transaction e DisplayName Each column can be named so that the different parts of the command appears in a more user friendly manner when editing its settings in the Transaction Editor or in the Parameter Section of the Main Window e ObjectType This row specifies the type of frame object that shall be used for the column e Value This row specifies where the frame object shall retrieve its value settings Value Description Depend This setting is only relevant for Responses in Master Mode The value will be retrieved from the corresponding part of the Query transaction Id The value will be retrieved from the Command ID setting see Basic Navigation on page 49 User The settings associated with the object can be edited by the user SlaveAddress The value will be retrieved from the SlaveAddress parameter see Node Parameters on page 33 other settings Other settings are no longer supported Anybus Communicator for DeviceNet Doc Rev 3 01 Doc Id SCM 1200 098 Commands 52 8 3
46. Size Out The specified amount starting at address lO Sizes 0x0000 of the respective memory buffers will be reserved for and represented as I O Data The remainder will be reserved for parameter data See also e Data Representation on DeviceNet on page 22 e Assembly Object Class 04h on page 78 e Parameter Data Input Mapping Object Class BOh on page 83 e Parameter Data Output Mapping Object Class B1h on page 84 Anybus Communicator for DeviceNet Doc Rev 3 01 Doc ld SCM 1200 098 30 4 2 ABC Parameters Select ABC in the Navigation Section to gain access to the parameters e TE described in this section 2j 4 Sub Network Interface Currently only serial communication is supported Status Control Word See Control and Status Registers on page 69 Value Description Enabled Enable the Control and Status Registers The Data Valid bit in the Control Register must be set to start the subnetwork communication Enabled but no startup lock This setting is similar to Enabled except that the control system is not required to set the Data Valid bit to start the subnetwork communication Disabled This setting completely disables the Control and Status Registers Module Reset This parameter specifies how the gateway will behave in the event of a fatal error Value Description Enabled The gateway will be restarted and no error will
47. age 91 G DIN rail Connector The DIN rail mechanism connects the gateway to PE Protective Earth See also Connector Pin Assignments on page 91 Anybus Communicator for DeviceNet Doc Rev 3 01 Doc Id SCM 1200 098 1 2 Status LEDs About the Anybus Communicator for DeviceNet 12 State Status 1 Network Status Off Not powered not online Green Link OK On line Connected Green flashing On line Not connected Red Critical Link Failure O O Red flashing Connection timeout o ee 6 2 Module Status Off No power to device ICONS Green Device Operational O o Green flashing Data size bigger than configured Red Unrecoverable fault Red flashing Minor Fault 3 Not used 4 Not used 5 SubnetStatus Of Power off Green flashing Running correctly but one or more trans action error s have occurred Green Running Red Transaction error timeout or subnet stopped 6 Device Status Off Power off Alternating Red Green Invalid or missing configuration Green Initializing Green flashing Running Red Bootloader mode Red flashing Ilf the Device Status LED is flashing in a a This led turns green when all transactions have been active at least once This includes any transactions using change of state or change of state on trigger If a timeout occurs on a transaction this led will turn red b The gateway is in bootloader mode
48. and altering dif ferent levels of the subnetwork configuration Entries preceded by a holds further configuration pa rameters or sub menus To gain access to these parame ters the entry must be expanded by clicking There are three main levels in the navigation window namely Fieldbus ABC and subnetwork Right clicking on entries in this section brings out addi tional selections related to that particular entry C Parameter Section This section holds a list of parameters or options related to the currently selected entry in the Navigation Section The parameter value may be specified either using a selec tion box or manually depending on the parameter itself Values can be specified in decimal form e g 42 or in hexadecimal format e g Ox2A D Information Section This section holds information related to the currently se lected parameter Anybus Communicator for DeviceNet Doc Rev 3 01 Config Line QA This menu entry is expanded Egi Fieldbus li Starilnit nia Fieldbus specific Sub entries ind nda Endlnit Aa ABC This menu entry holds additional sub entries parameters Configuration Alphabetic Categorized E Communication Bitrate bits s Data bits Parity Physical standard Start bits Stop bits E Timing Message delimiter 10ms Parameter Section Message delimiter 10ms The time between transaction Information Section
49. ar ine options for sub network Clear Update mode Cyclically 3 100 Update time 10ms 100 E Trigger Request Trigger byte address O O05FF Resnonse Trinner hute Misahled Type The file type of the data file to be accessed 2010 05 07 Command Parameters Parameter Element Number Description The element number of the data file to be accessed within the slave DF1 Protocol Mode 59 10 55 Config Line Valid settings PLC 5 0 999 SLC500 0 255 MicroLogix 0 255 File number The file number of the data file to be accessed PLC 5 3 7 8 10 999 SLC500 3 7 8 10 255 MicroLogix 3 7 8 10 255 File type The file type of the data to be accessed Integer Bit Float Size The number of bytes to read from the slave One bit integer element is 2 bytes and one float element is 4 bytes The parameter must have an even value as only whole elements can be read from the slave Data Options Parameter Byte swap Description Determines if the data shall be swapped PLC 5 2 240 SL C500 2 236 MicroLogix 2 242 Valid settings No byte swap Swap words Swap double words Data length The number of bytes read from the DF1 network to write to the area determined lt Size by the Offset parameter Offset The offset in the internal memory buffer in the module where the data shall be read See Memory Map on page 17 Note If the control and status regi
50. ave Address Function Byte count Checksum In Area 4 bytes 512 Out Area 16 bytes 512 General Area 0 bytes 1004 00 00 DO DO DD DD DO DO DO DD 0D DO DO DO DD DD DO DO DO DO n A Pull down Menu amp Toolbar Icons See Pull Down Menu on page 63 and Toolbar Icons on page 64 B Command Section This section holds the currently selected command The individual frame objects in the com mand can be edited in a similar way as in the Transaction and Command Editors C Response Section Master Mode and DF1 Master Mode only This section holds the response to the selected Command z Monitor Section This section displays the data associated with the node Areas in dark grey are reserved for the Status amp Control Registers and areas displayed in light grey represent the data that is used by the node The data displayed in this section will be refreshed based on the refresh icons in the toolbar For more information see Toolbar Icons on page 64 Anybus Communicator for DeviceNet Doc Rev 3 01 Doc Id SCM 1200 098 Node Monitor 63 11 2 1 Pull Down Menu File There is only one entry in this menu s Es Lh This will close the Node Monitor Note however that if the node has Exit j been disabled using Stop Node see below it will not resume data exchange until enabled again using Start node Node This menu controls the data exchange for the n
51. be indicated to the user Disabled The gateway will halt and indicate an error Protocol Mode This parameter specifies which protocol mode to use for the subnetwork Value Description Generic Data Mode This mode is primarily intended for Produce amp Consume based protocols where there are no Master Slave relationship between the gateway and the nodes on the subnetwork Master Mode This mode is intended for Query amp Response based protocols where a single Master exchanges data with a number of Slaves DF1 This mode is intended for the DF1 protocol The Anybus Communicator can only be con figured as a Master with half duplex communication Note This is the only mode available if you intend to configure an ABC module for DF1 See also Protocol Modes on page 19 Anybus Communicator for DeviceNet Doc Rev 3 01 Doc Id SCM 1200 098 31 Statistics The Transmit and Receive Counters indicate how many transactions that have successfully been ex changed on the subnetwork This feature is primarily intended for debugging purposes e Receive Counter Location Specifies the location of the Receive Counter in the internal memory buffer e Transmit Counter Location Specifies the location of the Transmit Counter in the internal memory buffer Both counters are enabled by setting Statistics to Enabled Anybus Communicator for DeviceNet Doc Rev 3 01 Doc Id SCM 1200 098 32 4 1 S
52. e Rename To increase readability each node can be given a unique name using this function a Only available in Master Mode b Only available in Generic Data Mode Anybus Communicator for DeviceNet Doc Rev 3 01 83 Fieldbus A ABC WA Sub Network TP E N Cut Copy Insert Delete Node Monitor Add Transaction Consume Add Transaction Produce Add Command Insert New Node Save Node Insert from File Rename Doc Id SCM 1200 098 Transactions 36 6 3 Transaction Parameters Master Mode 6 3 1 Parameters Query 8 Broadcast To gain access to these parameters select a Query or Broadcast transaction in the Navigation Section Parameter Minimum time between broadcasts 10 ms Description This parameter specifies how long the gateway shall wait after transmitting a broadcast trans action before processing the next entry in the scanlist The value should be set high enough to allow the slave devices time to finish the handling of the broadcast The entered value is multiplied by 10 For instance an entered value of 5 results in 50 ms Note This setting is only relevant for the Broadcaster node Offline options for field bus This parameter specifies the action to take for this transaction if the higher level network goes offline This affects the data that is sent to the subnetwork Clear The data destined for the slave devices is cleared set to zero Freeze The data dest
53. e discarded The value must not exceed 300 bytes which is the maximum data length allowed for one frame a Only relevant for Consume Response transactions b Only used if Object Delimiter is set to End Character or End Character Visible Anybus Communicator for DeviceNet Doc Rev 3 01 Doc Id SCM 1200 098 Frame Objects 46 7 7 Checksum Object Most serial protocols features some way of verifying that the data has not been corrupted during trans fer The Checksum Object calculates and includes a checksum in a transaction Parameter Description Error Check Start byte This parameter specifies the byte offset in the transaction to start checksum calculations on Error Check Type This parameter specifies which type of algorithm to use Anybus Communicator for DeviceNet Doc Rev 3 01 e CRC 2 bytes CRC 16 with 0xA001 polynome Modbus RTU standard LRC 1 byte All bytes are added together as unsigned 8 bit values The 2 s complement of the result will be used as a checksum e XOR 1 byte All bytes are logically XOR ed together The resulting byte will be used as a checksum ADD 1 byte All bytes are added together as unsigned 16 bit values The lowest 8 bits in the result will be used as a checksum e AddinvASCll 2 bytes All bytes are added together as unsigned 8 bit values The lowest 8 bits in the result are inversed and used as a checksum represented as hexadecimal ASCII 2 byte
54. e internal memory buffer is divided into three areas a a based on their function e Input Data 512 bytes This area can be read by the higher level net wotk Higher Level Network how this data is represented on the higher level network will be described later in this chapter General Data x pum o A rab lt Q 7p e Output Data 512 bytes This area can be written to by the higher level network how this data is represented on the higher level network will be described later in this chapter e General Data This area is not exchanged on the higher level network and can be used for transfers between individual nodes on the subnetwork or as a general scratch pad for data The actual size of this area depends on the amount of data that is exchanged on the subnetwork The gateway can han dle up to 1024 bytes of General Data 2 2 1 Memory Map When building the subnetwork configuration using the Anybus Configuration Manager the different at eas described above are mapped to the memory locations addresses specified below Input Data Output Data General Data 0x000 0x200 0x400 Subnetwork Read Write Fieldbus Read Only Subnetwork Read Only Fieldbus Read Write Subnetwork Read Write Fieldbus Ox1FF 0x3FF 0x22 Anybus Communicator for DeviceNet Doc Rev 3 01 Doc Id SCM 1200 098 Basic Operation 18 2 2 2 Data Exchange Example In the following example a temperature regu
55. ee 1 888 8 Anybus Fax 1 312 629 2869 Fax 1 312 629 2869 Online www anybus com Online www anybus com HMS Germany E mail ge sales hms networks com E mail ge support hms networks com Phone 49 0 721 989777 000 Phone 49 0 721 989777 000 Fax 49 0 721 989777 010 Fax 49 0 721 989777 010 Online www anybus de Online www anybus de HMS Japan E mail jp sales hms networks com E mail jp support hms networks com Phone 81 0 45 478 5340 Phone 81 0 45 478 5340 Fax 81 0 45 476 0315 Fax 81 0 45 476 0315 Online www anybus jp Online www anybus jp HMS China E mail cn sales hms networks com E mail cn support hms networks com Phone 86 0 10 8532 3183 Phone 86 0 10 8532 3023 Fax 86 0 10 8532 3209 Fax 86 0 10 8532 3209 Online www anybus cn Online www anybus cn HMS Italy E mail it sales hms networks com E mail it support hms networks com Phone 39 039 59662 27 Phone 39 039 59662 27 Fax 39 039 59662 31 Fax 39 039 59662 31 Online www anybus it Online www anybus it HMS France E mail fr sales hms networks com E mail fr support hms networks com Phone 33 0 3 68 368 034 Phone 33 0 3 68 368 033 Fax 33 0 3 68 368 031 Fax 33 0 3 68 368 031 Online www anybus fr Online www anybus fr HMS UK 8 Eire E mail uk sales anybus co uk E mail support hms networks com Phone 44 0 1926 405599 Phone 46 0 35 17 29 20 Fax 44 0 1926 405522 Fax 46 0 35 17 29 09
56. ent of a fatal error ELITS Description Enabled The gateway will be restarted and no error will be indicated to the user Disabled The gateway will halt and indicate an error Protocol Mode This parameter specifies which protocol mode to use for the subnetwork ELITS Description DF1 This mode is intended for the DF1 protocol The Anybus Communicator can only be con figured as a Master with half duplex communication Note This is the only mode available if you intend to configure an ABC module for DF1 See also Protocol Modes on page 19 Statistics The Transmit and Receive Counters indicate how many transactions that have successfully been ex changed on the subnetwork This feature is primarily intended for debugging purposes e Receive Counter Location Specifies the location of the Receive Counter in the internal memory buffer e Transmit Counter Location Specifies the location of the Transmit Counter in the internal memoty buffer Both counters are enabled by setting Statistics to Enabled Anybus Communicator for CANopen Doc Rev 3 01 Doc Id SCM 1200 099 9 3 Subnetwork Parameters To gain access to the parameters described in this section select Subnet work in the Navigation Section Communication DF1 Protocol Mode 55 Fieldbus A ABC See Sub Network These parameters specify the actual communication settings used for the subnetwork Parameter De
57. ers are set as Enabled Execute Command If set the specified command will be executed by the gateway see below Control Code Data This field holds commands which can be executed by the gateway see below See also Control Codes in Master Mode and DF1 Master Mode on page 73 Control Codes in Generic Data Mode on page 73 Note Internally this is treated as a Motorola format word i e MSB first If the higher level network uses a different byte order the upper and lower bytes will appeat to be swapped 14 3 2 Control Codes in Master Mode and DF1 Master Mode Ihis table is valid only in Master Mode and DF1 Master Mode Code 0x00 0x01 0x02 Instruction Disable Node Enable Node Enable Nodes Data Actual node address Description Disables the specified node Actual node address Enables a previously disabled node Enables the specified number of nodes start ing from the first node in the configuration Remaining nodes will be disabled Actual number of nodes to enable 14 3 3 Control Codes in Generic Data Mode No Control Codes are currently supported in this mode Anybus Communicator for DeviceNet Doc Rev 3 01 Doc Id SCM 1200 098 Chapter 15 15 CIP Object Implementation DeviceNet is based on the Control and Information protocol CIP which is also the application layer for ControlNet and EtherNet TP The following CIP objects ate implemented i
58. for DeviceNet Doc Rev 3 01 Doc Id SCM 1200 098 Frame Objects 45 To specify the properties of the object select 1t in the Navigation Section enter the desired settings in the Parameter section as follows Parameter Description Byte Swapping No Swapping No swapping will be performed on the data Swap 2 bytes A B C D becomes B A D C e Swap 4 bytes A B C D becomes D C B A Fill unused bytes Enabled Fill unused data with the value specified in Filler byte Disabled Don t fill Filler byte Filler byte value Only used if Fill unused bytes has been enabled Data Location The offset in the internal memory buffer where the data shall be read from written to Object Delimiter Length Character Length character is visible in the internal memory buffer but not on the subnetwork Length Character Visible The length character is visible both in the internal memory buffer and on the subnetwork End Character The end character is visible in the internal memory buffer but not on the subnetwork End Character Visible The end character is visible both in the internal memory buffer and on the subnetwork No Character No End or Length character is generated in the internal memory buffer End Character Value End Character value Maximum Data Length The maximum allowed length in bytes of the variable data object If the actual length of the data exceeds this value the message will b
59. from the list Note that some commands are fixed and cannot be deleted 8 2 2 Toolbar Icons The toolbar features icons for the most commonly used functions Add Command Same as Add Command in the Command menu Edit Command Same as Edit Command in the Command menu Delete Command Same as Delete Command in the Command menu Anybus Communicator for DeviceNet Doc Rev 3 01 Add Command Edit Command Delete Command Doc Id SCM 1200 098 Commands 49 8 3 The Command Editor 8 3 1 General The Command Editor is used to define new commands and edit existing ones This makes it possible to build a library of commands which can be stored and reused at a later stage Note that the Command Editor is somewhat protocol dependent in the sense that certain frame objects may not be deleted or altered The examples in this section use Master Mode The procedures involved are similar in Generic Data Mode but without the limitations imposed by the Modbus RTU protocol 8 3 2 Basic Navigation Open the Command Editor by selecting Edit Command or Add Command from the Command menu Command Editor Fil lumn Command Name New o Command ID 0x3 Allow O Query 1 2 3 4 DisplayName Slave Address Function Data Checksum ObjectType Byte Byte Data Checksum Value SlaveAddress ID User User Response 1 2 4 DisplayName Slave Address Function
60. ge 83 e Fieldbus Settings on page 29 e Parameter Data Initialization Explicit Data on page 86 Supported Services Class services Get Attribute All Instance services Get Attribute Single Set Attribute Single 15 9 2 Class Attributes Access Name iye Vae Description 1 Get Revision JUNT 0001h Revision 1 15 9 3 Instance Attributes Instance 01h Each attribute corresponds to a block of output data Note that the size and location of each block must be specified using the Anybus Configuration Manager For more information see Mapping Output Parameter Data to DeviceNet on page 89 Access Name Type Description 01h Get Set Data Array of USINT Mapped block of Output Data 02h Get Set Data Array of USINT Mapped block of Output Data 03h Get Set Data Array of USINT Mapped block of Output Data 04h Get Set Data Array of USINT Mapped block of Output Data 05h Get Set Data Array of USINT Mapped block of Output Data 06h Get Set Data Array of USINT Mapped block of Output Data 32h Get Set Data Array of USINT Mapped block of Output Data Anybus Communicator for DeviceNet Doc Rev 3 01 Doc Id SCM 1200 098 Chapter 16 16 Advanced Fieldbus Configuration 16 1 General The fieldbus interface of the gateway consists of an embedded Anybus S communication interface Nor mally the Anybus S configuration settings are set up automatically by the gateway However advanced users can conf
61. gging is stopped by clicking Stop Logging The log buffer will contain the most recent data Log Window The logged data is displayed in hexadecimal decimal and AS CII format for both directions The time between the log en tries is displayed in a separate column The data may optionally be saved in ASCII text format by clicking Create Text file Click Close to exit x zj se E Create Text file Anybus Communicator for DeviceNet Doc Rev 3 01 Doc Id SCM 1200 098 Data Logger 66 12 3 Configuration By default the log buffer can hold 512 bytes of data in each i Hms Options direction To specify a different size for the buffer select Options in the Tools menu Size oflogbufer iE Oo aw Firmware Download A window with various settings will appear Select the ABC RUE Firmware to the Anybus tab and enter the desired number of buffer entries under Size of logbuffer valid settings range from 1 512 Restores Communicator firmware Factory Restore Block the current configuration in the COTRA PIDE Block Configuration Click Apply to validate the new settings Creates an error log file Create Error Log Click OK to exit Anybus Communicator for DeviceNet Doc Rev 3 01 Doc Id SCM 1200 098 13 Configuration Wizards 13 1 General Chapter 13 When creating a new subnetwork configuration the Anybus Configuration Manager p
62. he subnet Counter Updated work has increased If this problem persists this may eventually trigger a Single or Multi ple Node s Missing condition 0x01 Single Node Missing Error Slave address A single node is missing 0x02 Multiple Nodes Missing Error Number of nodes Multiple nodes are missing 0x03 Buffer Overrun Warning Slave address A node returned more data than expected 0x04 Other Error Error Slave address Undefined error Ox1F No Error Warning No errors Note Conditions of type Error will eventually be followed by a No Error condition when the cause has been resolved Conditions of type Warning are however considered informational and may not nec essatily be followed by a No Error condition later on Anybus Communicator for DeviceNet Doc Rev 3 01 Doc Id SCM 1200 098 Control and Status Registers 72 14 2 3 Status Code in Generic Data Mode This table is valid only in Generic Data Mode Code Condition Type DELE Description 0x00 Invalid Transaction Error Counter The number of invalid transactions i e received transac Counter Updated tions which doesn t match any of the consume transactions defined in the subnetwork configuration has increased 0x01 Frame Error Warning End character is enabled but a message delimiter timeout occurs prior to receiving it 0x02 Offline Timeout Error Counter The of number of timed out consume transactions has Counter Updated
63. hese registers occupy the first two bytes in the input and output data areas 0x000 0x001 and 0x200 0x201 respectively which means they can be accessed from the fieldbus just like any other data in these areas Note Internally these registers are stored in Motorola format 1 e MSB first If the higher level net work uses a different byte order the upper and lower bytes will appear swapped 14 1 1 Handshaking Procedure A special handshaking procedure which is illustrated in the two flowcharts below must be followed when accessing these registers to ensure that both parts receive proper information Read Status Register Write to Control Register Anybus Communicator for DeviceNet Doc Rev 3 01 Doc Id SCM 1200 098 Control and Status Registers 70 14 1 2 Data Consistency The Data Valid bits in the Control and Status Registers are used to ensure data consistency during start up and fieldbus offline online transitions If the Status Control Word parameter in Anybus Configuration Manager is set to Enabled the gate way will wait for the fieldbus control system to set the Data Valid bit in the Control Register before it starts exchanging data on the subnetwork If the same parameter 1s set to Disabled or Enabled but no startup lock communication will start as soon as the fieldbus goes online State Machine The fieldbus network participation can be described using a state machine as described below
64. ial port may be in use by another application to connect to the gateway Exit the Anybus Configuration Manager and close all other applications including the ones in the system tray Try again e Select another serial port Try again Poor performance e Right click subnetwork in the Navigation window and select subnetwork Status to see status diagnostic information about the subnetwork If the gateway reports very many retransmissions check your cabling and or try a lower baud rate setting for the subnetwork if possible e Is the Subnet Monitor in the Anybus Configuration Manager active The subnetwork monitor has a negative influence on the overall performance of the gateway and should only be used when necessary e sthe Node Monitor in the Anybus Configuration Man ager active The node monitor has a negative influence on the overall performance of the gateway and should only be used when necessary No subnetwork functionality e Use the Data logger functionality to record the serial data communication on the subnetwork e fno data is being transmitted check the configuration in Anybus Configuration Manager e fno data is received check the subnetwork cables Also verify that the transmitted data is correct Anybus Communicator for DeviceNet Doc Rev 3 01 Doc ld SCM 1200 098 Appendix E E ASCII Table NUL SOH STX ETX EOT ENQ ACK BEL BS
65. ical standards e RS 232 e RS 422 e RS 485 DeviceNet Interface DeviceNet connectivity is provided through patented Anybus technology a proven industrial commu nication solution used all over the world by leading manufacturers of industrial automation products Communications Adapter profile no 12 Group two only server e MacID and baudrate configuration via on board switches e Polled Change of state and Bit strobed I O Anybus Communicator for DeviceNet Doc Rev 3 01 Doc Id SCM 1200 098 About the Anybus Communicator for DeviceNet 11 External View For wiring and pin assignments see Appendix Connector Pin Assignments on page 91 A DeviceNet Connector This connector is used to connect the Anybus Communi IBS gt cator to the fieldbus network See also DeviceNet Connector on page 91 B Configuration Switches See also Configuration Switches on page 13 C Status LEDs See also Status LEDs on page 12 D PC connector This connector is used to connect the gateway to a PC for configuration and monitoring purposes See also PC Connector on page 92 E Subnetwork Connector This connector is used to connect the gateway to the serial subnetwork See also Subnetwork Interface on page 93 F Power Connector This connector is used to apply power to the gateway See also Power Connector on page 91 Connector Pin Assignments on p
66. ig Consist UINT N A Value Device Status bit s Name 0 Module Owned 1 reserved 2 Configured 3 7 reserved 8 Set for minor recoverable faults 9 Set for minor unrecoverable faults 10 Set for major recoverable faults 11 Set for major unrecoverable faults 12 519 reserved Anybus Communicator for DeviceNet Doc Rev 3 01 Doc Id SCM 1200 098 CIP Object Implementation 76 15 2 Message Router Class 02h 15 2 1 General Information Object Description Supported Services Class services Get Attribute Single Instance services E 15 2 2 Class Attributes Access Name Type Vale Description 1 Get Revision UINT 0001h Revision 1 15 2 3 Instance Attributes Anybus Communicator for DeviceNet Doc Rev 3 01 Doc Id SCM 1200 098 15 3 DeviceNet Object Class 03h 15 3 1 General Information Object Description Implemented Services Class setvices Instance services 15 3 2 Class Attributes Recess Name ie dus Description 6M Reson UN 2 Revision 2 15 3 3 Instance Attributes Get Attribute Single Get Attribute Single CIP Object Implementation 77 Access Name Type Value Description 1 Get MAC ID USINT N A Currently used MaclD 2 Get Baud Rate USINT N A Currently used baudrate 1 125 kbps 2 250 kbps 3 500 kbps 5 Get Allocation Information Struct of BYTE N A Allocation choice byte USINT N A Master s MAC ID Anybus C
67. igure the Anybus S card for specific features This chapter assumes that the reader is fa miliar with the Anybus S and it s application interface For more information about the Anybus S plat form consult the Anybus S Parallel Design Guide The standard initialization parameters are determined by the subnetwork configuration Information about the amount of input and output data used for subnetwork communication is used by Anybus Con figuration Manager to create the configuration message that sets the sizes of the input and output data areas in the Dual Port RAM of the embedded Anybus S interface It is possible to add fieldbus specific mailbox messages to customize the initialization This is done in the Mailbox Editor see below A mailbox message is a HMS specific command structure used for low level communication with an Anybus S interface Consult the Anybus S Parallel Design Guide and the fieldbus appendix for the de sired fieldbus for further information 16 2 Mailbox Editor 88 Fieldbus To add a mailbox message to the configuration right click on atartinit c D c gt a Field ifi EndInit and select Insert New Mailbox e Fieldbus specific Pal Insert New Malbox xw Sub Network A mailbox message consists of a Header sec germ all tion and a data section where the Header con sists of 16 words 32 bytes and the data section consists of up to 128 words 256 bytes All fields are editable except the Mes
68. in access to these parameters select a Response transaction in the Navigation Section Parameter Trigger byte Description This parameter is used to enable disable the trigger functionality for the response If enabled the gateway will increase the trigger byte by one when the gateway receives new data from the subnetwork This can be used to notify the control system of the updated data The location of the trigger byte is specified by the Trigger byte address parameter below Trigger byte address This parameter specifies the location of the trigger byte in the internal memory buffer Valid settings range from 0x000 Ox1FF and 0x400 OXNNN 6 4 Transaction Parameters Generic Data Mode 6 4 1 Produce Transactions To gain access to these parameters select a Produce Transaction in the Navigation Section Parameter Offline options for fieldbus Description This parameter specifies the action to take for this transaction if the higher level network goes offline This affects the data that is sent to the subnetwork Clear Data is cleared 0 on the subnetwork if the higher level network goes offline Freeze Data is frozen on the subnetwork if the higher level network goes offline NoScanning Stop subnet scanning for this transaction if the higher level network goes offline Update mode Update time 10 ms Anybus Communicator for DeviceNet Doc Rev 3 01 The update mode for the tra
69. increased See also Consume Transactions on page 39 Offline timeout time 0x03 Buffer Overrun Warning A node returned more data than expected or the gate way was unable to finish processing a message prior to receiving a new one 0x04 Other Error Error Undefined error Ox1F No Error Warning No errors Note Conditions of type Error will eventually be followed by a No Error condition when the cause no longer is detected Conditions of type Warning are however considered informational and may not necessarily be followed by a No Error condition later on Anybus Communicator for DeviceNet Doc Rev 3 01 Doc Id SCM 1200 098 Control and Status Registers 73 14 3 Control Register Contents Control System to Gate way 14 3 1 General Information The Control Register is 1 enabled located at 0x200 0x201 and constitutes a bit field as follows bit s Name 15 Confirm CR HS CONFIRM 14 Send CR HS SEND Data Valid Description These bits control the handshaking towards the gateway See also Handshaking Procedure on page 69 Status Register Contents Gateway to Control System on page 71 This bit controls data consistency see Data Consistency on page 70 1 Output Area valid exchange data on the subnetwork 0 Output Area not valid do not exchange data on the subnetwork Note This bit is only relevant if the Control Status Regist
70. ined for the slave device is frozen NoScanning The updating of the subnetwork is stopped Offline options for sub network This parameter specifies the action to take for this transaction if the subnetwork goes offline This affects the data that is reported to the control system Clear Data is cleared 0 on the higher level network if the subnetwork goes offline Freeze Data is frozen on the higher level network if the subnetwork goes offline Reconnect time 10 ms Retries This parameter specifies how long the gateway shall wait before attempting to reconnect a dis connected node node will be disconnected in case the maximum number of retries below has been reached The entered value is multiplied by 10 For instance an entered value of 5 results in 50 ms Note This setting is not relevant for the Broadcaster node This parameter specifies how many times a timeout may occur in sequence before the node is disconnected Timeout time 10 ms This parameter specifies how long the gateway will wait for a response from a node If this time is exceeded the gateway will retransmit the Query until the maximum number of retries see above has been reached The entered value is multiplied by 10 For instance an entered value of 5 results in 50 ms Trigger byte address This parameter specifies the location of the trigger byte in internal memory only relevant when Update mode is set to Change
71. k start byte Value CRC 0x0000 0x00 To edit the value of a parameter click on 1t and enter a new value using the keyboard When editing transactions which are based on predefined commands certain parts of the transaction may not be ed itable The File menu features the following entries Apply Changes Exit Ctri Q Example Transaction Editor File Byte constant Word constant Data Value Value Data location Data length 0x02 0x0008 0x0202 0x0008 Apply Changes This will save any changes and exit to the main window Exit Exit without saving Checksum Byte constant Error check type Error check startbyte Value CRC 0x0001 0x03 The transaction created in this example are built up as follows The first byte holds the STX 0x02 followed by two bytes specifying the length of the data field in this case 8 The next 8 bytes are data and since this is a fquety transaction the data is to be fetched from the Output Area which starts at address location 0x202 No swapping will be per formed on the data This is followed by a two byte checksum The checksum calculation starts with the second byte in the transaction The transaction ends with a byte constant the ETX 0x03 Anybus Communicator for DeviceNet Doc Rev 3 01 Doc Id SCM 1200 098 Chapter 7 7 Frame Objects 7 1 General Each transaction consists of Frame Objects which makes up the serial telegram frame Each Frame Ob ject specifies ho
72. lator on the subnetwork exchanges information with a PLC on the higher level network via the internal memory buffers in the Anybus Communicator PLC DeviceNet Scanner PLC Memory Inputs Actual Temperature PLC Memory Outputs Temperature Setpoint The PLC Memory associated with the ABC is exchanged Data from the Input Data area is copied to PLC Input Memory and PLC Output Memory is copied to the Output Data area The PLC exchange data between the internal PLC memory and the slaves in this case the ABC on the DeviceNet network DeviceNet Input Data Output Data General Data MEME not used in this example The ABC copies the Output Register of the Temperature Regulator to the Input Data area The ABC copies the Temperature Setpoint from the Output Data area to the Input Register in the Temperature Regulator Subnetwork Serial Device Temperature Regulator Output Register Input Register The Temperature Regulator has two Actual Temperature Temperature Setpoint registers holding the Setpoint Temperature and the Actual Temperature respectively Anybus Communicator for DeviceNet Doc Rev 3 01 Doc Id SCM 1200 098 Basic Operation 19 2 3 Subnetwork Protocol 2 3 1 Protocol Modes The Anybus Communicator features three distinct modes of operation regarding the subnetwork com munication called Master Mode DF1 Master Mode and Gene
73. licit messaging connection Predefined in DeviceNet object Instance 2 Polled connection COS Cyclic consuming connection Instance 3 Bit strobe connection Instance 4 COS Cyclic producing connection Instance 10 14 Explicit connection UCMM allocated 15 5 3 Instance 1 amp 10 14 Explicit Messaging Connection Attributes Access Name Type Value Description 1 Get State USINT N A 0 Non existent 1 Configuring 3 Established 4 Timeout 5 Deferred delete 2 Get Instance type USINT 0 Explicit messaging connection 15 5 4 Instance 2 Polled Connection Attributes Access Name Type Value Description 1 Get State USINT N A 0 Non existent 1 Configuring 3 Established 4 Timeout 2 Get Instance type USINT 1 I O Connection Anybus Communicator for DeviceNet Doc Rev 3 01 Doc Id SCM 1200 098 CIP Object Implementation 80 15 5 5 Instance 3 Bit strobe connection Attributes Access Name Type Value Description 1 Get State USINT N A 0 Non existent 1 Configuring 3 Established 4 Timeout 2 Get Instance type USINT 1 I O Connection 15 5 6 Instance 4 COS Cyclic connection Attributes Access Name Type Value Description 1 Get State USINT N A 0 Non existent 1 Configuring 3 Established 4 Timeout 2 Get Instance type USINT 1 I O Connection 3 Get Transp
74. ls View Help ABC DF1 Master Untitled Devices Fieldbus ABC el Subnetwork TUN TT Node 2 Configuration Alphabetic Categorized E General Checksum CRC Slave address 2 Type PLC 5 Slave address The address of the slave 2010 05 07 10 38 Config Line 8 DF1 Protocol Mode 56 Fieldbus ABL uu 5 ubnetwork ZI 1 Node 2 Parameter Description Valid Settings Checksum Selects the type of checksum on the network BCC CRC default Slave Address The value entered here sets the node address 0 254 Type The PLC type of the slave PLC 5 SLC500 MicroLogix 9 5 Services Services ate commands that can be stored and reused The user configures each slave with services that can be issued from the master A total of 50 services are allowed The Anybus Communicator supports a selection of DF1 commands When the gateway is going to ex ecute a setvice it automatically chooses the appropriate DF1 command s that are used to perform the setvice on the selected DF1 node type Anybus Communicator for CANopen Doc Rev 3 01 Doc Id SCM 1200 099 DF1 Protocol Mode 57 9 5 1 Available Services Right click on the node and choose Add Command mA A pop up window will show the four different servic x Select Command es that ate available File Command e Integrity check ime e Read diagnostics pm ere e Read data e Write data Integrity Check 002 Read Diagnostics O03 Read Data
75. ly as a transaction in the Anybus Configuration Managet Using this wizard involves the following steps Step 1 Communicator Type Wizard Modbus RTU Master Step 1 of 6 Select the fieldbus type The purpose of this wizard is to help you through the process of Select DeviceNet Fieldbus Type The type ofthe Fieldbus connected to the Communicator Click Next to continue DeviceNet creating a project with a Modbus S A s Profibus DP F RTU sub network When the e Interbus S Wizard is finished it is possible to Tip It is possible to return to a previous oe piri oles h l mE E the Configuration Tool m m W a A YN Modbus Plus The fieldbus is the higher layer enu at any ti e 1t out osing any set p Ale network that communicates with ontrolne M Al the serial device s on the sub ngs by clicking Previous d network via the Communicator Wizard Modbus RTU Master Version 1 14 Revision 1 Next gt Cancel Step 1a I O Sizes This parameter is used to set the sizes of Wizard Modbus RTU Master the in out data areas For more informa veson Step 1a of 6 Select settings for tion see IO Sizes on page 29 Ea zi the chosen fieldbus Occupied station 1 y Mester Ex Click Next to continue en Ufo The ier used might offer special features that can be configured Click the list below to see available settings and their meaning
76. n One vice NOE Ua dlls 22 SONT E 22 PATO mu CR 22 DUI Um A E 23 Chapter 3 Navigating the Anybus Configuration Manager E O aaaaieutts 24 AE NE A RR 25 VEAN AR O O 28 Anybus Communicator for DeviceNet Doc Rev 3 01 Doc Id SCM 1200 098 Chapter 4 Basic Settings Pel ers diga T 29 APC Patto TCLS nece uasa cn d sce M ne E ELE M M he Dhaene A 30 Subtietwotkc AALS EH Su o to outils itai doutes o semuis AN 32 Chapter 5 Nodes A ae ee al A 33 deine Se Ma acimo Node aria iia 39 Node Patata td Mete M um P RUE 23 Maser Nodeand nr LIUEN GO s aus dot eto tub toe ovest idc i dedo too pde 33 Chapter 6 Transactions Generals 34 PG GIO Se IATA Oe Transicion ia AA AA 35 Transaction Parameters Master Mode E tU Cua 36 117107171 110 711 a E DOUNAT BREMEN RR TEM C 36 NE Nette NEU 38 Transaction Parameters Generne Dar MO te 38 Produit MR T MEI O EEE T EAT 38 COM SATO N TAREAS AAA AAA A OET A 59 JTransacton al 6 ilee aida iii its 40 Chapter 7 Frame Objects O IS 41 dcin and atinado 4 Constant Objects Byte Word DWord aseo da eon han no aO 42 Trot Objects Byte Word DVO Sec bdo a olt lm etri 43 TD AGA OCCU assunti tester eit duode OU DN N o AAA 44 Narable Dar ODECE o d ket omn det id 44 Check un Ob crap ld 46 Chapter 8 Commands A e P M A 47 Addie Wanasmo Commands ueno cla diante 47 SSB QUI RN Doo O O 48 LOTT L
77. n from ABC a id Download configuration to ABC Upload the configuration from the Start Logging gateway to the Anybus Configuration Manager Options Download configuration to ABC Download the current configuration into the gateway Start Logging Start the Data Logger see Data Logger on page 65 Note that when the Data Logger is active this menu entry is changed to Stop Logging Options This will bring out the following window Item Description Warning on Delete A confirmation dialog is displayed each ES time something is deleted HM NR Warning on unsaved A confirmation dialog is displayed when Elem Was egw atin o data closing the Anybus Configuration Man e ager with unsaved data Show Wizard when The Wizard is displayed each time a new New menu is selected configuration is created Language next time the Selects which language to use The new program is launched setting will be active the next time the pro gram is launched Selecting the ABC tab will reveal additional properties Item Description Size of logbuffer By default the Data Logger can log up to 512 entries in each direction If necessary Apply it is possible to specify a different number of entries valid settings range from 1 512 Click Apply to validate the new A E settings See also Data Logger on page 65 Firmware Download Download firmware to the embedded field bu
78. n this product Mandatory Objects Object Page Identity Object Class 01h 75 Message Router Class 02h 76 DeviceNet Object Class 03h TT Assembly Object Class 04h 78 Connection Object Class 05h 79 Acknowledge Handler Object Class 2Bh 81 Vendor Specific Objects Object Page Diagnostic Object Class AAh 82 Parameter Data Input Mapping Object Class BOh 83 Parameter Data Output Mapping Object Class B1h 84 Anybus Communicator for DeviceNet Doc Rev 3 01 Doc Id SCM 1200 098 CIP Object Implementation 75 15 1 Identity Object Class 01h 15 1 1 General Information Object Description Implemented Services Class setvices Get Attribute All Get Attribute Single nstance setvices Get Attribute All Get Attribute Single Reset 15 1 2 Class Attributes Access Name Type Vae Description 1 Get Revision UINT 0001h Revision 1 15 1 3 Instance Attributes Access Name Type Value Description 1 Get Vendor ID UINT Default 005Ah HMS Industrial Networks AB 2 Get Device Type UINT Default 000Ch Communication Adapter 3 Get Product Code UINT Default 003Ch Anybus Communicator for Device Net 4 Get Revision Struct of USINT Major fieldbus version USINT Minor fieldbus version 5 Get Status WORD Device status see table below 6 Get Serial Number UDINT Module serial number Serial number of the module 7 Get Product Name SHORT STRING AnyBus C Product name 8 Get Conf
79. nsaction Cyclically The transaction is sent cyclically at the interval specified in the Update Time param eter On data change The data area is polled for changes at the time interval defined by Update time A transaction is issued when a change in data is detected Single shot The transaction is sent once at startup Change of state on trigger The transaction is sent when the trigger byte has changed This feature enables the control system to notify the gateway when to issue a particular transaction To use this feature correctly the control system must first update the data area associated with the transaction then increase the trigger byte by one The location of the trigger byte is specified by the Trigger byte address parameter This parameter specifies how often the transaction will be issued in steps of 10ms only relevant when Update mode is set to Cyclically The entered value is multiplied by 10 For instance an entered value of 5 results in 50 ms Doc Id SCM 1200 098 Parameter Trigger byte address Transactions 39 Description This parameter specifies location of the trigger byte in the internal memory buffer If Update mode is set to Change of state on trigger the memory location specified by this parameter is monitored by the gateway Whenever the trigger byte is updated the gateway will produce the transaction on the subnetwork This way the control s
80. ntrol System to Gateway eese 73 SOARES A A AOS 73 Control Codes in Master Mode and DE Master Mode eee nennen 73 Control Codon Genere Dal Mode uie ons tiia pla tux Chee e loben tie Do aes EA sansa D a Pede us 73 Anybus Communicator for DeviceNet Doc Rev 3 01 Doc Id SCM 1200 098 Chapter 15 CIP Object Implementation Ide mit Ob s lOs 75 875714171810 1719 77177 UN EN ASA AAA ae aint 75 SAA E SN EE pta col 15 I 17717 14 A 111277 TOS AAA TE TA 75 Message Router Clase DAD dssdo n obo eoe in taa 76 77170718 171105717771 T 76 CLASS NII TOL a M 76 VOTAR AOS rM NN 76 Device Net Object as SO tna als 77 E NO Y A eterna earners a ne A OA a CHASE p LUN Iq Ta AA ac ENT TI Assemb Object Class Di A 78 077114719 AEE E E casos E E A A T TT 78 CASA RN ER 78 Instance Attributes Instance Connection Point 64 ooooocnoconaninanononnononanannonanoronnnnrnnnnnrrnnnnn conan nono 78 Instance Attributes Instance Connection Point 96h eese eee tenente conan n conan n cios 78 Conuecion Object Class 05 Dci ic A A ao 19 E Le T A EIO UE 19 E E A EONI OI ATE rm 79 Instance TEF T0 4 M Eph Messauine Connection SATITIDULES tdo 79 Varo 2 LOUCE C T T E T E EET O E E NET QUE Iano o ated 79 TEA BO SLOVO COMETON Z LV DULES SERRE RN A sd O doa 80 Ditame AAC OSTEN COET U A I OUS d sona EE EA 80 incknowledee Handil Object Class Z Bin ari on 81 SAA 1717 17777717 AMNEM TNERE ENIM ME 81 WE PII rmm o
81. ode This feature can rade help isolate problems associated with a particular node Start Node Stop Node e Start Node Enable the transactions associated with the node e Stop Node Disable the transactions associated with the node Command This menu is used to specify and issue a command manually e Select Command Select a command to be sent to the subnetwotk Command Send Command Select Command Send the specified command to the subnetwork send Command Columns This menu specifies the number of columns in the Monitor Section Columns E Free Free 4 8 Multiple The number of columns depends on the width of the window 8 Multiple The number of columns will be fixed to 8 View This menu specifies the data representation in the Monitor Section m ERN Display the data in hexadecimal format v Hex Decimal e Decimal Display the data in decimal format Anybus Communicator for DeviceNet Doc Rev 3 01 Doc Id SCM 1200 098 Node Monitor 64 11 2 2 Toolbar Icons The toolbar features icons for the most commonly used functions e Start Node Stop Node O e These icons corresponds to the functions in the Node menu e o o See also Node on page 63 Start Stop e Select Command amp Send Command These icons corresponds to the functions in the Command menu ES Ead See also Command on page 63 Select Send Resume Refresh amp Stop Refresh
82. ommunicator for DeviceNet Doc Rev 3 01 Doc Id SCM 1200 098 CIP Object Implementation 78 15 4 Assembly Object Class 04h 15 4 1 General Information Object Description This object provides access to the I O Data in the Input and Output Data areas in the Anybus Com municatot See also e Data Representation on DeviceNet on page 22 p pag e Fieldbus Settings on page 29 Services Class services Get Attribute Single Instance services Get Attribute Single Set Attribute Single 15 4 2 Class Attributes Access Name Type Vae Description 1 Get Revision UINT 0001h Revision 1 15 4 3 Instance Attributes Instance Connection Point 64h This instance is used to access I O Data Input in gateway memory F ces ame Tipe a en 3 Array of BYTE Data produced by the ABC 15 4 4 Instance Attributes Instance Connection Point 96h This instance is used to access I O Data Output in gateway memory Fes ame ipo Nate escritos 3 Array of BYTE Data consumed by the ABC Anybus Communicator for DeviceNet Doc Rev 3 01 Doc Id SCM 1200 098 CIP Object Implementation 79 15 5 Connection Object Class 05h 15 5 1 General Information Object Description Implemented Services Class services Get Attribute Single Instance setvices Get Attribute Single Set Attribute Single 15 5 2 Class Attributes Recess Name lype Vae Descriptor joer Revision UNT jh Reison2 Instance 1 Exp
83. onveniently be reached by right clicking on a node in the Anybus Config uration Manager and selecting Insert New Command Note however that this does not in any way pre vent other protocols based on the same query response message scheme to be implemented Anybus Communicator for DeviceNet Doc Rev 3 01 Doc Id SCM 1200 098 Basic Operation 21 2 3 4 Generic Data Mode In this mode there is no master slave relationship between the nodes on the subnetwork and the gate way Any node including the gateway may spontaneously produce ot consume a message Nodes do not have to respond to messages nor do they have to wait for a quety in otder to send one Control System Gateway Subnetwork Devices Consume d Produce Node 1 Produce p Consume Produce p Consume Node 2 Consume d Produce In the figure above the gateway consumes data that is produced by a node on the subnetwork This consumed data can then be accessed from the higher level network This also works the other way around the data received from the higher level network is used to produce a message on the subnet work to be consumed by a node 2 3 5 DF1 Master Mode Please refer to DF 1 Protocol Mode on page 53 Anybus Communicator for DeviceNet Doc Rev 3 01 Doc Id SCM 1200 098 Basic Operation 22 2 4 Data Representation on DeviceNet 2
84. oolbar features icons for the most commonly used functions New Open amp Save b i See File on page 25 New Open Save e Upload from ABC amp Download to ABC See Tools on page 26 Wee Upload Download e Up one Level e Clicking on this icon will move the selection in the navigation section Up one Level e Cut Copy Paste Delete Insert X X 1 These icons ate used for common editing func ma Cut Copy Paste Delete Insert tions 1n the navigation section Connect Ss Clicking on this icon will cause the Anybus Configuration Manager to attempt to connect to the gateway Connect e Disconnect fer Clicking on this icon will cause the Anybus Configuration Manager to disconnect A Disconnect from the gateway Start Logging amp Stop Logging See Tools on page 26 amp Data Logger on page 65 n Start Log Stop Log e Subnetwork Monitor Clicking on this icon will launch the subnetwork Monitor see Subnetwork Monitor on page 60 ae e Add Command v This icon is used to add commands to the currently selected node ES omman e Add Mailbox E Advanced functionality see Mailbox Editor on page 85 Y Add Mailbox e Add Node amp Add Broadcaster These icons ate used to add nodes to the configuration k Node Broadcaster e Node Monitor Clicking on this icon will launch the Node Monitor see Node Monitor on page 61 Node Monitor e
85. or specific object provides diagnostic information from the module Implemented Services Class services Instance services Get Attribute All 15 7 2 Class Attributes Access Name Type Value Description UINT 0001h Revision 1 1 Get Get Attribute Single 15 7 3 Instance Attributes Instance 01h A Access Name Type Description 01h Get Module serial number UDINT Serial number 04h Get Module Software version UINT DeviceNet Interface software version OFh Get Input I O Size UINT IO Size In 11h Get Input Total Size UINT Total size of Input Data area I O Parameter Data 12h Get Output I O Size UINT IO Size Out 14h Get Output Total Size UINT Total size of Output Data area I O Parameter Data a See IO Sizes on page 29 Anybus Communicator for DeviceNet Doc Rev 3 01 Doc Id SCM 1200 098 CIP Object Implementation 83 15 8 Parameter Data Input Mapping Object Class BOh 15 8 1 General Information Object Description This object can be used to access input data acyclically and is set up dynamically based on the Parameter Data Mailbox initialization see Parameter Data Initialization Explicit Data on page 86 See also e Data Representation on DeviceNet on page 22 e Parameter Data Output Mapping Object Class B1h on page 84 e Fieldbus Settings on page 29 e Parameter Data Initialization Explicit Data on page 86 Supported Services
86. ort Class trigger BYTE N A Defines the behaviour of the con nection 4 Get Produced Connection ID UINT N A CAN ID for transmission 5 Get Consumed Connection ID UINT N A CAN ID for reception 6 Get Initial Comm Characteristics BYTE OFh No ACK Produces over message group 1 Does not consume 01h ACK Produces over message group 1 Consumes over message group 2 7 Get Produced Connection Size UINT N A Number of bytes transmitted across this connection 8 Get Consumed Connection Size UINT 0 Number of bytes received across this connection 9 Get Set Expected Packet Rate UINT 0 Timing associated with this connec tion 12 Get Watchdog timeout action USINT N A 0 Transition to the timed out state 1 Auto Delete 2 Auto Reset 3 Deferred Delete 13 Get Produced Connection path UINT 0006h Number of bytes in the produced length connection path attribute 14 Get Produced Connection Path EPATH 20 04 24 66 30 03h Application object producing data on this connection 15 Get Consumed Connection path UINT 0004h Number of bytes in the consumed length connection path length attribute 16 Get Consumed Connection Path EPATH 20 2B 24 01h Specifies the application object s that are to receive the data con sumed by this connection object Anybus Communicator for DeviceNet Doc Rev 3 01 Doc Id SCM 1200 098 CIP Object Implementation 81 15 6 Acknowledge Handler Object Class 2Bh 15 6 1 General Information
87. ory location in the Anybus Communicatot Anybus Communicator for DeviceNet Doc Rev 3 01 Doc Id SCM 1200 098 Parameter Data Initialization Explicit Data 88 Resulting Attribute Mapping Input Data Parameter Data Input Mapping Object I O Data Input IO Size In Attributes 256 bytes Instance 1 Attributes 32 bytes UD 0x0000h not mapped 64 bytes 16 bytes 32 bytes not mapped Ox1FF 16 bytes Offset OxOOFFh Mailbox Editor Screenshot ioj xj File Header Message Message ID 0x0001 0x00 0x00 Message information 0x4002 0x01 0x00 Command 0x0004 0x02 0x00 Data size 0x0014 0x03 0x20 Frame count 0x0001 0x04 0x00 Frame number 0x0001 10 05 0x40 Offset high 0x0000 0x06 0x00 Offset low 0x0000 0x07 0x40 Extended Word 1 0x0000 0x08 0x00 Extended Word 2 Ox0000 0x09 0x80 Extended Word 3 0x0000 Ox0A 0x00 Extended Word 4 Ox0000 0x0B 0x10 Extended Word 5 0x0000 0x0C 0x00 Extended Word 6 0x0000 0x00 0x90 Extended Word 7 0x0000 Ox0E 0x00 Extended Word 8 Ox0000 Ox0F 0x20 0x10 0x00 0x11 0xF0 0x12 0x00 0x13 0x10 Allow user to enable disable EE E Anybus Communicator for DeviceNet Doc Rev 3 01 Doc Id SCM 1200 098 Parameter Data Initialization Explicit Data 89 A 4 Mapping Output Parameter Data to DeviceNet Example Mapping output data is similar to mapping input data in the following example a total of 14
88. ough and explain all steps of a configuration The output from a wizard will result in a working configuration ready to download It is also possible to edit the configuration in the dard configuration tool after Wizard completion The Blank Configuration option will open the standard configuration tool and a configuration can be created from scratch Here it is also possible to open an existing configuration from file or via upload from a Communicator module Don t show this Window again Doc Id SCM 1200 098 Configuration Wizards 68 13 3 Wizard Modbus RTU Master This wizard can be used to create a Modbus RTU based network configuration based on certain infor mation about the subnetwork The online help system explains each configuration step in detail e Important Notes Many OEM devices do not fully comply with the Modbus standard For example they may im plement a variation of this standard or be limited to the use of specific Modbus commands other than the ones used by this wizard In all cases the user should consult the documentation of the devices that shall be used on the subnetwotk for information about their serial communication requirements and if necessary contact the manufacturer of the device to obtain further informa tion about the serial communication protocol In the event that the wizatd doesn t handle a particular Modbus command required by a device it is possible to specify this command manual
89. ps of 10 ms 1000 ms Update time 10 ms The minimum time between two services of this kind in steps of 10 ms 1000 ms a The default value is given as 100 in the parameter window Each change of 10 ms either increases or decreases this value by 1 i e 99 represents a poll time of 990 ms and 101 represents a poll time of 1010 ms Trigget Parameter Description Default Request Trigger byte The memory location of the trigger byte this service uses for updates on trigger Ox05FF address byte changes Response Trigger byte Enables disables the trigger byte Disabled Response Trigger byte The memory location of the trigger byte this service uses for updates on trigger Ox05FF address byte changes Valid settings range from 0x200 Ox3FF and 0x400 OxNNN Anybus Communicator for CANopen Doc Rev 3 01 Doc Id SCM 1200 099 DF1 Protocol Mode 58 9 6 Integrity Check This service checks that a node is up and running correctly A telegram is sent to the node The node mirrors and returns the telegram No configuration is needed apart from the general parameters com mon to all services 9 7 Read Diagnostics This service reads diagnostic information from the module ABC DF1 Master Untitled Devices Configuration Alphabetic Categorized E Command Params Size 0x02 CJ Integrity Check El Data Options C3 A ead Diagnostics Byte swap No byte swap T Node 2 Data Length 0x02 Offset 0x0000 E General
90. r DeviceNet Doc Rev 3 01 Doc Id SCM 1200 098 Control and Status Registers 71 14 2 Status Register Contents Gateway to Control Sys tem 14 2 1 General Information The Status Register is 1 enabled located at 0x000 0x001 and constitutes a bit field as follows bit s Name 15 Send SR_HS_SEND 14 Confirm SR HS CONFIRM Description These bits control the handshaking towards the fieldbus control system See also Handshaking Procedure on page 69 Control Register Contents Control System to Gateway on page 73 13 Data Valid This bit is set when all transactions have been executed successfully at least once Master Mode and DF1 Once set it will not change Master Mode Only 1 Data Valid 0 Data not Valid Note This bit is not used in Generic Data Mode 12 8 Status Code This field holds the last status report from the gateway 7 0 Dat See also Status Codes in Master Mode and DF1 Master Mode on page 71 Status Code in Generic Data Mode on page 72 Note Internally this is treated as a Motorola format word i e MSB first If the higher level network uses a different byte order the upper and lower bytes will appear swapped 14 2 2 Status Codes in Master Mode and DF1 Master Mode This table is valid only in Master Mode and DF1 Master Mode Condition Description 0x00 Retransmission Warning Counter The number of retransmissions on t
91. range the attribute numbering by physically changing the mapping order in the mailbox data 5 To save the new mailbox select Apply changes in the File menu 1 The offset is specified from the start of the Parameter Data not from the physical memory location in the Anybus Communicatot Anybus Communicator for DeviceNet Doc Rev 3 01 Doc Id SCM 1200 098 Parameter Data Initialization Explicit Data 90 Resulting Attribute Mapping Output Data I O Data Output IO Size Out 128 bytes Parameter Data Output Mapping Object Attributes not mapped Minus l 16 bytes not mapped Offset 0x0000h Instance 1 Attributes 32 bytes 32 bytes not mapped 64 bytes not mapped Mailbox Editor Screenshot iol xj File Header Message Message ID 0x0001 0x00 0x00 Message information 0x4002 0x01 0x20 Command 0x0005 0x02 0x00 Data size 0x0010 0x03 0x10 Frame count 0x0001 0x04 0x00 Frame number 0x0001 0x05 0x50 Offset high Ox0000 0x06 0x00 Offset low 0x0000 0x07 0x20 Extended Word 1 0x0000 0x08 0x00 Extended Word 2 Ox0000 0x09 0x70 Extended Word 3 0x0000 0x0A 0x00 Extended Word 4 0x0000 x B 0x20 Extended Word 5 Ox0000 0x0C 0x00 Extended Word 6 0x0000 0x0D xD Extended Word 0x0000 Ox0E 0x00 Extended Word 8 Ox0000 0x0F 0x40 Allow userto enable disable DIN E Anybus Communicator for DeviceNet Doc
92. ric Data Mode Note that the protocol mode only specifies the basic communication model not the actual subnetwork protocol Master Mode In this mode the gateway acts as a master on the subnetwork and the serial communication takes place in a quety response fashion The nodes on the network are not permitted to issue messages unless they have been addressed by the gateway first For mote information about this mode see Master Mode on page 20 DF1 Master Mode In this mode the gateway acts as a master on the subnetwork using the DF1 protocol The serial communication takes place in a query response fashion For more information about this mode see DF1 Protocol Mode on page 53 Generic Data Mode In this mode there is no master slave relationship between the subnetwork nodes and the gate way any node on the subnetwotk including the gateway may spontaneously produce or con sume messages For mote information about this mode see Generic Data Mode on page 21 2 3 2 Protocol Building Blocks The following building blocks are used in Anybus Configuration Manager to describe the subnetwork communication How these blocks apply to the two protocol modes will be described latet in this doc ument Node A node represents a single device on the subnetwork Each node can be associated with a number of transactions see below Transaction A transaction represents a complete serial telegram and consist
93. rovides a choice between starting out with a blank configuration or using a predefined template a k a a wizard The wizard automatically creates a subnetwork configuration based on information supplied by the user i e the user simply has to fill in the blanks Note however that this will only work when the subnetwork fits the wizard profile in all other cases the Blank Configuration option must be used 13 2 Selecting a Wizard Profile The following window appears each time the Anybus Configuration Manager is started or upon select ing the New entry in the File menu unless it has been disabled in the Options menu see Tools on page 26 Currently the following wizards are available e ABCC ExtLink Wizard This wizard is intended for use with the Anybus Com pactCom Modbus RTU fieldbus communication module e Wizard Modbus RTU Master This option is suitable for Modbus RTU based net wotks See also Wizard Modbus RTU Master on page 68 Blank Configuration This option creates an empty configuration Highlight the desired wizard and click OK to continue Anybus Communicator for DeviceNet Doc Rev 3 01 Select Configuration _ XJ SA zT T se e 5 Cancel ABCC ExtLink Wizard Wizard Modbus Blank Configuration RTU Mast aster Select the desired topic to do and press the OK button A wizard option will guide you thr
94. s Doc Id SCM 1200 098 Chapter 8 8 Commands 8 1 This information is only valid for master mode and generic mode For DF1 master mode please refer to Services on page 56 General As mentioned previously commands are actually predefined transactions that can be stored and reused Just like regular transactions commands consist of frame objects and are representations of the actual setial telegrams exchanged on the serial subnetwork Adding a command to a node actually results in a transaction s being added according to the directions specified in the command The frame objects in such a transaction may retrieve their values not only from parameters in the parameter section but also from other sources such as the SlaveAddress pa rameter see Node Parameters on page 32 In such case the parameters in the parameter section will be greyed out and cannot be edited directly In Master Mode Anybus Configuration Manager comes preloaded with commands for most common Modbus RTU functions Additional commands can easily be added using the Command Editor see The Command Editor on page 49 For DF1 Master Mode see Services on page 56 In Generic Data Mode no predefined commands exist but custom ones may be implemented as desired 8 2 Adding amp Managing Commands To add a command to a node right click on the node in the Navigation Section and select Add Com mand A list of commands will appear
95. s interface Warning Use with caution Factory Restore Restores the gateway firmware to it s orig inal state does not affect the embedded fieldbus interface Block Configuration When selected the downloaded configu ration will not be executed by the gateway Warning Use with caution Create Error log Creates an error log file Firmware Download Block Configuration Anybus Communicator for DeviceNet Doc Rev 3 01 Doc Id SCM 1200 098 Navigating the Anybus Configuration Manager 27 View This menu features the following entries view M e Toolbar This entry enables disables the toolbar icons at the top of the Toolbar main window we Status Bar e Status Bar This entry enables disables the status bar at the bottom of the main window Help This menu features the following entries Hep i Contents Search For Help On e Contents Display the table of contents of the online help system Note At the time of writing no online help sys About tem exists e Search For Help On Search for a particular topic in the online help sys tem Note At the time of writing no online help system exists e About Display general information about the gateway and the current build of Anybus Configuration Manager Anybus Communicator for DeviceNet Doc Rev 3 01 Doc Id SCM 1200 098 Navigating the Anybus Configuration Manager 28 3 1 2 Toolbar Icons The t
96. s of a number of frame objects see below Each transaction is associated with a set of parameters controlling how and when to use it on the subnetwork Commands A command is simply a predefined transaction stored in a list in the Anybus Configuration Man ager This simplifies common operations by allowing transactions to be stored and reused Frame Object Frame objects are low level entities used to compose a transaction see above A frame object can represent a fixed value a constant a range of values limit objects a block of data or a cal culated checksum Anybus Communicator for DeviceNet Doc Rev 3 01 Doc Id SCM 1200 098 Basic Operation 20 2 3 3 Master Mode In this mode the communication is based on a query response scheme when the Anybus Communica tor issues a query on the subnetwork the addressed node is expected to issue a response to that query Nodes are not permitted issue responses spontaneously i e without first receiving a quety There is one exception to this rule the broadcaster Most protocols offer some way of broadcasting mes sages to all nodes on the network without expecting them to respond to the broadcasted message This is also reflected in the gateway which features a dedicated broadcaster node Control System Gateway Subnetwork Devices 4 Node 1 Node 2 In Master Mode Anybus Configuration Manager comes preloaded with most commonly used Modbus RTU commands which can c
97. s product Those responsible for the use of this device must ensure that all the necessary steps have been taken to verify that the applications meet all performance and safety requirements in cluding any applicable laws regulations codes and standards HMS Industrial Networks AB will under no circumstances assume liability or responsibility for any problems that may arise as a result from the use of undocumented features timing or functional side effects found outside the documented scope of this product The effects caused by any direct or indirect use of such aspects of the product are undefined and may include e g compatibility issues and stability issues The examples and illustrations in this document are included solely for illustrative purposes Because of the many variables and requirements associated with any particular implementation HMS Industrial Networks AB cannot assume responsibility for actual use based on these examples and illustrations Intellectual Property Rights HMS Industrial Networks AB has intellectual property rights relating to technology embodied in the product de scribed in this document These intellectual property rights may include patents and pending patent applications in the US and other countries Trademark Acknowledgements Anybus 0 is a registered trademark of HMS Industrial Networks AB All other trademarks are the property of their respective holders Warning This is a class A product in a dome
98. scription Valid Settings Bit rate baud rate Selects the bit rate 2400 4800 9600 19200 38400 Default Data bits Selects the number of data bits 8 Parity Selects the parity mode None Odd Even Physical standard Selects the physical interface type RS232 RS422 RS485 Start bits Number of start bits Stop bits Number of stop bits 1 DF1 Settings Parameter Description Master Node Address Node address of the master valid values 0 254 default 1 Poll time active slaves 10 ms Determines how often the slave shall be polled in steps of 10 ms default 100 ms Poll time inactive slaves 10 ms Determines how often the slave shall be polled in steps of 10 ms default 1000 ms a The default value is given as 10 in the parameter window Each change of 10 ms either increases or decreases this value by 1 i e 9 represents a poll time of 90 ms and 11 represents a poll time of 110 ms b The default value is given as 100 in the parameter window Each change of 10 ms either increases or decreases this value by 1 i e 99 represents a poll time of 990 ms and 101 represents a poll time of 1010 ms Anybus Communicator for CANopen Doc Rev 3 01 Doc Id SCM 1200 099 9 4 Node Parameters To gain access to the parameters described in this section select a node in the navigation section For more information about nodes see Nodes on page 33 amp ABC Config Tool Untitled File Node 1 Too
99. sters are enabled default first available data location will be Input area 0x002 Output area 0x202 9 9 Write Data This service is used to write data to the nodes in the subnetwork The parameters to be configured are the same as for the service Read Data The only difference is that data 1s read from the internal memory buffer in the Anybus Communicator and written to the subnetwork bus instead of being written to the internal memory buffet Anybus Communicator for CANopen Doc Rev 3 01 Doc Id SCM 1200 099 Chapter 10 10 Subnetwork Monitor General The Subnetwork Monitor is intended to simplify configuration and troubleshooting of the subnetwork Its main function is to display the data allocated for subnetwork communication and detect 1f any area has been allocated twice 1 e if a collision has occurred All configured nodes and their transactions are listed in the middle of the screen B Selecting and de selecting single transactions makes it possible to view any combination of allocated data Note The subnetwork monitor has a negative influence on the overall performance of the gateway Therefore the monitor functionality should be used with care Operation Hms Sub network Monitor File Columns Y Y Nodel Node2 Barcodereader Sensor SelectAll Deselect All SelectAll Deselect All SelectAll Deselect All Select All Deselect All Read Coil Status Read Coil Status Transactions 1 v trans actions
100. stic environment this product may cause radio interference in which case the user may be required to take adequate measures ESD Note This product contains ESD Electrostatic Discharge sensitive parts that may be damaged if ESD control procedures are not followed Static control precautions are required when handling the prod uct Failure to observe this may cause damage to the product DeviceNet protocol mode for Anybus Communicator Rev 3 01 Copyright HMS Industrial Networks AB Sept 2011 Doc Id SCM 1200 098 Table of Contents Table of Contents Preface About This Document Related DOCM A A A AAA 7 Document TES COTY A A A A A A R Y Conventions cc Lerminol08 arial ai 8 Glossdty ic ace ec o td CE 8 Sales and SU OLE ves ar aces sneha di ias 9 Chapter 1 About the Anybus Communicator for DeviceNet DN E S T M 11 A O ATTAT EIEE tanec ea TEO 12 Contieuration Witness dando aaa 13 Hardware last ia 14 Solares Stallone Aa LS P N CIAO OS 15 Y Il NS sat A ua d tta DPI UD a DI BUM ADR A E btodmD Gola 15 Chapter 2 Basic Operation Centralita M 16 Data BxchanseModel iid cun coeno Si 17 OS PLU Loo MEDIO c TR uae eat 17 VPE TOUT SUR E17 1 MU M TR TR m 18 SUbne work Protocol a acoustic A me Usu nua Re Ups eI dU ond a USA 19 D 0 WII PER 19 LIDO Budane DO NENNEN ER 19 INEST CP IVIG AC ree T 20 CONCILIO mem N E E E E 21 DELNI NO AAA AA A AAA DR da E 21 Data Repre emano
101. t automati cally right click on the CD drive icon and select Explore Execute setup exe and follow the on screen instructions From website Download and execute the self extracting exe file from the HMS website www anybus com 1 5 2 Electronic Datasheet EDS file On DeviceNet the characteristics of a device is stored in an ASCII data file with the suffix EDS This file is used by DeviceNet configuration tools when setting up the network The latest version of this file can be obtained from the HMS website www anybus com Anybus Communicator for DeviceNet Doc Rev 3 01 Doc Id SCM 1200 098 Chapter 2 2 Basic Operation 2 1 General The Anybus Communicator is designed to exchange data between a serial subnetwork and a higher level network Unlike most other gateway devices of similar kind 1t does not have a fixed protocol for the subnetwork and can be configured to handle almost any form of serial communication The gateway can issue serial telegrams cyclically on change of state or based on trigger events issued by the control system of the higher level network i e the fieldbus master or PLC It can also monitor cer tain aspects of the subnetwork communication and notify the higher level network when data has changed An essential part of the Anybus Communicator package is the Anybus Configuration Manager a Win dows M application which is used to supply the ABC with a description of the subnetwork protocol
102. transceivers It is therefore generally recommended to connect it only to Signal Ground if available of other nodes Anybus Communicator for DeviceNet Doc Rev 3 01 Doc Id SCM 1200 098 Connector Pin Assignments 94 B 4 5 Typical Connection RS485 5V RS485 RS485 RS485 RS485 Signal Signal Ground Ground Cable Shield Anybus Communicator Node Node Node Node End Node B 4 6 Typical Connection RS422 amp 4 Wire RS485 5V RS422 Rx gt RS422 Tx m I 1 I RS422 Rx L RS422 Tx I 470R 1 1 RS422 Tx s RS422 Rx 120R RS422 Tx l RS422 Rx l 470R TE 1 I Signal f Signal Ground Ground Cable J Shield Anybus Communicator Device Note Bias resistors are normally not needed on RS422 but may be required when using 4 wire RS485 B 4 7 Typical Connection RS232 RS232 Tx RS232 Rx I oa I 1 I a RS232 Rx RS232 Tx I a I Signal J Signal Ground Ground Cable Shield Anybus Communicator Device Anybus Communicator for DeviceNet Doc Rev 3 01 Doc Id SCM 1200 098 Appendix C C Technical Specification C 1 Mechanical Properties Housing Plastic housing with snap on connection to DIN rail protection class IP20 Dimensions 120 mm x 75 mm x 27 mm Lx W x H inches 4 72 x 2 95 x 1 06 Lx W x H C 2 Electrical Characteristics Power Supply Power 24V 10 Power Consumption Maximum power consumption is 280mA on 24V Typically around 100mA
103. ubnetwork Parameters Fieldbus A ABC ES al Sub Netwark To gain access to the parameters described in this section select Subnet work in the Navigation Section Communication These parameters specify the actual communication settings used for the subnetwork Parameter Description Master Mode and Generic Mode Bit rate baud rate Selects the bit rate 1200 2400 4800 9600 19200 35700 38400 57600 Data bits Selects the number of data bits 7 8 Parity Selects the parity mode None Odd Even Physical standard Selects the physical interface type RS232 RS422 RS485 Start bits Number of start bits 1 Stop bits Number of stop bits 1 2 Start and End Character Note These parameters are only available in Generic Data Mode Start and end characters are used to indicate the beginning and end of a serial message For example a message may be initiated with lt ESC gt and terminated with lt LF gt In this case the Start character would be 0x1B ASCII code for lt ESC gt and the End character OxXOA ASCII code for lt LF gt Parameter Description Valid settings End Character Value End character for the message ASCII 0x00 OxFF Use End Character Determines if the End character shall be used or not Enable Disable Start Character Value Start character for the message ASCII 0x00 OxFF Use Start Character Determines if the Start character shall be used or not Enable Disable Timing Message
104. w the gateway shall interpret or generate a particular part of the telegram There are 5 types of frame objects which are described in detail later in this chapter e Constant Objects Limit Objects e Data Objects e Variable Data Objects e Checksum Objects Example The following Transaction consists of several frame objects three constants a data object and a checksum object Transaction 7 2 Adding and Editing Frame Objects W Sub Network T New Node Transactions 1 To add a frame object to a Transaction right click on the Transac 2 E pm ER Edt Transaction tion in the Navigation Section and select one of the entries in the Add Data Add Variable Data menu that appears Add Checksum Add Byte Constant The entry called Transaction Editor will launch the Transaction Add Word Constant Editor which is used to edit transactions and frame objects in a fen sie as A yte Limits mote visual manner For more information see Transaction Edi Add Word Limits to p on p 2 9 e 40 Add DWord Limits Rename Configuration Alphabetic Categorized General Data length 0x0001 Data location 0x0200 Operations O To edit parameters associated with a particular frame object select the frame object in the Navigation Section The settings for that frame object will be displayed in the Parameter Section Byte swap No swapping It is also possible to
105. ystem can instruct the gateway to produce a specific transaction on the subnetwork by updating the corresponding trigger byte The trigger byte should be incremented by one for each activation Please note that the trigger byte address must be unique to each transaction It can not be shared by two or more transactions Note This parameter has no effect unless the Update mode parameter is set to Change of state on trigger Valid settings range from 0x200 OX3FF and 0x400 OXNNN 6 4 2 Consume Transactions To gain access to these parameters select a Consume Transaction in the Navigation Section Parameter Offline options for subnet work Description This parameter specifies the action to take for this transaction if the subnetwork goes offline This affects the data that is sent to the higher level network Clear Data is cleared 0 on the higher level network if the subnetwork goes offline Freeze Data is frozen on the higher level network if the subnetwork goes offline Offline timeout time 10 ms This parameter specifies the maximum allowed time between two incoming messages in steps of 10ms If this time is exceeded the subnetwork is considered to be offline A value of 0 disables this feature i e the subnetwork can never go offline The entered value is multiplied by 10 For instance an entered value of 5 results in 50 ms Trigger byte Enable Enables the trigger byte The location of

User Manual, Anybus Communicator for DeviceNet

Contents

Download Pdf Manuals

Related Search

Related Contents