Home

User Manual, Anybus Communicator for PROFINET IO

1. Anybus Communicator for PROFINET Doc Rev 3 01 Doc ld SCM 1200 088 Appendix E E Copyright Notices This product includes software developed by Carnegie Mellon the Massachusetts Institute of Technology the Uni versity of California and RSA Data Security kkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkk Copyright 1986 by Carnegie Mellon kkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkk Copyright 1983 1984 1985 by the Massachusetts Institute of Technology kkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkk Copyright c 1988 Stephen Deering Copyright c 1982 1985 1986 1992 1993 The Regents of the University of California All rights reserved This code is derived from software contributed to Berkeley by Stephen Deering of Stanford University Redistribution and use in source and binary forms with or without modification are permitted provided that the following conditions are met e Redistributions of source code must retain the above copyright notice this list of conditions and the fol lowing disclaimer e Redistributions in binary form must reproduce the above copyright notice this list of conditions and the following disclaimer in the documentation and or other materials provided with the distribution e Neither the name of the University nor the names of its contributors may be used to endorse or promote prod
2. 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 82 Bs 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 PROFINET Doc Rev 3 01 Doc Id SCM 1200 088 Node Monitor 88 17 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 Slave Address Function Byte count Checksum In Area 4 bytes 512 Out Area 16 bytes 512 General Area 0 bytes 1004 0 00 00 00 00 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 89 and Toolbar Icons on page 90 B Command Section This section holds the currently selected command The individual frame objects in the com mand can be
3. 4 5 Signal Ground 6 9 A 4 Subnetwork Interface 1 The RJ11 4P4C modular is sometimes referred to as an RJ9 Anybus Communicator for PROFINET Doc Rev 3 01 Doc ld SCM 1200 088 Connector Pin Assignments 103 A 4 1 General Information The subnetwork interface provides for RS232 RS422 and RS485 communication Depending on the configuration specified in the Anybus Configuration Manager different signals are activated in the sub network connector A 4 2 Bias Resistors RS485 Only 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 A 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 serial recetvers near the end nodes The resistor value should ideally match the characteristic impedance
4. 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 O eee settings See also Data Logger on page 91 Firmware Download Download firmware to the embedded field bus 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 PROFINET Doc Rev 3 01 Doc ld SCM 1200 088 Navigating the Anybus Configuration Manager 53 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 EA 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 h
5. User Manual Anybus Communicator for PROFINET Doc Id SCM 1200 088 Rev 3 01 44 AmS MA 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 this p
6. consumes data that is produced by a node on the sub network 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 subnetwork to be consumed by a node 2 3 5 DF1 Master Mode Please refer to DF1 Protocol Mode on page 79 Anybus Communicator for PROFINET Doc Rev 3 01 Doc Id SCM 1200 088 Basic Operation 22 2 4 PROFINET lO 2 4 1 General The PROFINET IO interface provides PROFINET IO Soft Real Time Communication PROFINET is the open Industrial Ethernet standard for Automation from PROFIBUS International Supported Features e Soft Real Time RT communication e Cyclic data exchange 10 ms cycle time e Acyclic Data exchange Record Data Requests e Upto 64 slots 1 subslot e Up to 512 bytes of I O in each direction e TCP IP Configuration via DCP Discovery and Configuration Protocol 2 4 2 I O Configuration PROFINET makes a distinction between fast cyclical data a k a IO data and acyclical data called Record Data By default all data in the input and output data areas are exchanged as IO data It is how ever possible to specify how much data to exchange as IO data and how much data to exchange using acyclic Record Data read write requests On PROFINET the IO data is built up by I O modules In the case of the ABC the actual I O module c
7. LJ My Documents My Computer 2 My Network Places Anybus Communicator for PROFINET Doc Rev 3 01 Doc Id SCM 1200 088 6 Web Server 6 1 General Chapter 6 The Anybus Communicator features a flexible web server with SSI capabilities The built in web pages can be customized to fit a particular application and allow access to I O data and configuration settings The web server communicates through port 80 See also e Server Side Include SSI on page 36 e IP Access Control on page 29 Protected Files For security reasons the following files are protected from web access e Files located in user pswdcfg pswd e Files located in pswd e Files located in a directory which contains a file named web_accs cfe Default Web Pages The Anybus Communicator contains a set of virtual files which can be used when building a web page for configuration of network parameters These virtual files can be overwritten not erased by placing files with the same name in the root of disc 0 This makes it possible to for example replace the HMS logo by uploading a new logo named logo jpg It is also possible to make links from a web page to the virtual configuration page In such case the link shall point to config htm These virtual files are index htm config htm configform htm configform2 htm store htm logo jpg Points to the Configuration Configuration Configura
8. 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 essarily be followed by a No Error condition later on Anybus Communicator for PROFINET Doc Rev 3 01 Doc Id SCM 1200 088 Control and Status Registers 98 20 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 increased See also Consume Transactions on page 65 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 Err
9. Output when ON Output when OFF pinas DisplayDhcpSupport This function returns Argl if DHCP is supported and Arg2 if it is not Syntax lt exec cmd_argument DisplayDhcpSupport Argl Arg2 gt DisplayEmailServer This function returns the currently used SMTP server address Syntax lt exec cmd_argument DisplayEmailServer gt Anybus Communicator for PROFINET Doc Rev 3 01 Doc Id SCM 1200 088 Server Side Include SSI 39 DisplaySMTPUser This function returns the username used for SMTP authentication Syntax lt exec cmd_argument DisplaySMTPUser gt DisplaySMTPPswd This function returns the password used for SMTP authentication Syntax lt exec cmd_argument DisplaySMTPPswd gt DisplayStationName This function returns the PROFINET Station Name Syntax lt exec cmd_argument DisplayStationName gt DisplayStationType This function returns the PROFINET Station Type Syntax lt exec cmd_argument DisplayStationType gt DisplayVendorlD This function returns the PROFINET Vendor ID Syntax lt exec cmd_argument DisplayVendorId gt DisplayDevicelD This function returns the PROFINET DevicelD Syntax lt exec cmd_argument DisplayDeviceld gt Anybus Communicator for PROFINET Doc Rev 3 01 Doc Id SCM 1200 088 Server Side Include SSI 40 StoreEtnConfig Note This
10. 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 PROFINET Doc Rev 3 01 Doc Id SCM 1200 088 Frame Objects 70 13 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 e No Swapping No swapping is performed on the data e 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 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 13 6 Variable Data Object
11. 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 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 PROFINET Doc Rev 3 01 Doc Id SCM 1200 088 Chapter
12. Rabat AAA A A 85 RA RN 85 Subnetwork Monitor Node Monitor CSU rites circa ecscala tead sac conde tascnda ead cat ececadaesaaalcaige eas sue ons Gaus aa tea aura say aoe da eae eee aveaiacea 87 Navicatinosthe Node Monto unes iaa 88 EE E EE ee ae 89 TOO IAN A uate teee suet aratavsl bute sects sau eaeaasts meee toe woe meus ne aaa unagn adem atone 90 Data Logger Goncral libras 91 oles O EUR 91 Confort lalala dl E 92 Configuration Wizards A E ere O 93 Selecuine a Wizard PEO Ginie EN A T E 93 Wa Zac Modbas RTI MASTO ai dado 94 Control and Status Registers A 95 Tarna ar i ne TAPONES IAEA SS AA A EA 95 DARE il EE 96 Status Resister Contents Gateway O COntrol Oyster ide 9y Cnr L VUE SEAE TAE A EA AEE AS A 97 Status Codes in Master Mode and DET Master Modest tada aid 97 SA Code M Gn Dara MoA AS A A od ie ON UR ae 98 Control Register Contents Control System to Gateway e cocoocconnonornnnnnnnonennonanranccnnnononcanancanacnnenaonoso 99 E E O E E E E E O alae 99 Control Codes in Master Mode and DF1 Master Mode icccccccccccccccscscsscecsesscesssccssssssessssesssasssessnees 99 UAB AA Genere Dord Mode reien E sealtagawtadestuiata cect aiecd sansa ae uteseniwioees 99 Anybus Communicator for PROFINET Doc Rev 3 01 VI Doc ld SCM 1200 088 VII Chapter 21 Appendix A Appendix B Appendix C Appendix D Appendix E Advanced Fieldbus Configuration Ge aee to et id ng ns e adas cana end e rel a ae 100 BATA Ee BDU
13. Updated sales and support page Updated System Requirements for Anybus Configuration Manager 15 Revision List Revision Date Author Chapter Description 1 00 2005 06 07 PeP All 1st release 2 00 2006 03 27 PeP All 2nd major release 2 01 2006 12 22 PeP Misc minor corrections amp updates 2 02 2008 10 14 HeS Misc minor corrections amp updates 2 03 2009 04 24 KeL All Misc minor corrections and updates 3 00 2011 01 19 KaD All Misc minor corrections new template and DF 1 functionality 3 01 2011 09 30 KaD All Misc corrections and updates new Anybus Configuration Manager name Anybus Communicator for PROFINET Doc Rev 3 01 Doc Id SCM 1200 088 About This Document P 9 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 OxNNNN 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 thi
14. 1 1 About the Anybus Communicator for PROFI NET 1 1 General The Anybus Communicator module for PROFINET acts as a gateway between virtually any serial ap plication protocol and a PROFINET IO based network Integration of industrial devices is enabled without loss of functionality control and reliability both when retro fitting to existing equipment as well as when setting up new installations PROFINET 10 Controller e g a PLC PROFINET IO Controller e g a PLC A g E PC web SCADA 2 PC web SCADA Ll El INVERTER INVERTER PC configuration PC configuration and monitoring and monitoring Multi drop up to 31 nodes A St Serial communication 5 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 physical standards e RS 232 e RS 422 e RS 485 Ethernet Interface Ethernet connectivity is provided through the patented Anybus technology a proven industrial commu nication solution used all over the world by leading manufacturers of industrial automation products e PROFINET IO e Modbus TCP server read only e Security framework with per user access rights and IP access control e Server Side Include SSI functionality e Web server and Email client capability e Easy file management via FTP e 10 100 Mbit s twisted pair Anybus Communicator
15. 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 SLC500 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 registers are enabled default first available data location will be Input area 0x002 Output area 0x202 15 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 is read from the internal memory buffer in the Anybus Communicator and written to the subnetwork bus instead of being written to the internal memory buff
16. A Starthnit l aan hs Fieldbus specific Sub entries _ Ea Endinit A 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 10rms Parameter Section Message delimiter 10ms The time between transaction Information Section Doc Id SCM 1200 088 9 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 51 Mew Open Save Save ds Print Properties Exit Ctrl N Ctrleo Ctrl s Ctrl 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 password in a safe place A lost password cannot be re trieved e Exit Close the Anybus Configuration Ma
17. Automatic Profinet IO 10 Sizes Sets whether the sizes of the 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 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 PROFINET Doc Rev 3 01 Config Line QA This menu entry is expanded Eg Fieldbus lt
18. Communicator for PROFINET Doc Rev 3 01 Doc Id SCM 1200 088 56 10 2 ABC Parameters im i Select ABC in the Navigation Section to gain access to the parameters se TE described in this section A 4 Sub Network Interface Currently only serial communication is supported Status Control Word See Control and Status Registers on page 95 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 event of a fatal error VENTE 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 VENTE 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 base
19. 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 for PROFINET Doc Rev 3 01 Doc ld SCM 1200 088 Frame Objects 71 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 e No Swapping No swapping will be performed on the data e 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 Enabl
20. PLC It can also monitor certain 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 module with a description of the subnetwork protocol No programming skills are required instead a visual protocol description system is used to specify the different parts of the serial communication sms ABC Config Tool Untitled OX File Transactions 1 Tools View Help D gH amp x Devices Configuration g Fieldbus Alphabetic Categorized ABC Sub Network Y Node1 Read Coil Status n E Query OX E Response m 4 Diagnostics E Query CQ Response Node2 Sensor a Barcodereader SelectAll DeselectAll Y Sensor Transactions 1 Hms Frame Editor TOX File Slave Address Function Starting Address Hi Lo Number of points HiLo Checksum Value Value Value Value Error check type Error check start byte 0x0000 Ox0000 CRC 0x0000 Transactions 1 2005 10 27 09 39 Config Line YA Response W Collision Reserved Trigger or Statusbytes Anybus Communicator for PROFINET Doc Rev 3 01 Doc ld SCM 1200 088 Basic Operation 17 2 2 Data Exchange Model Internally the data exchanged on the subnetwork and the data exchanged on the higher level network reside in the same memoty
21. 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 PROFINET Doc Rev 3 01 Doc Id SCM 1200 088 15 DF1 Protocol Mode Chapter 15 This mode makes it possible to let the Anybus Communicator act as a DF1 protocol master on the sub network 15 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 1s 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 1 e without first recetving a query Control System Gateway Subnetwork Devices Query y Node 1 mm a Response Query q y mm a Response Node 2 Query A 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
22. be used in e mail messages This function saves the data of a passed form to a file The Object name parameter is optional if spec ified only the data from that object will be stored If not the data from all objects in the form will be stored The Append Overwrite parameter determines if the specified file shall be overwritten or if the data in the file shall be appended Syntax lt exec cmd_argument SaveDataToFile File name Object name Ap pend Overwrite gt Default output Success Form saved to file Failure Failed to save form Anybus Communicator for PROFINET Doc Rev 3 01 Doc Id SCM 1200 088 Server Side Include SSI 46 7 3 Changing SSI output There are two methods of changing the output strings from SSI functions 1 Changing SSI output defaults by creating a file called Assi_str cfg containing the output strings for all SSI functions in the system 2 Temporarily changing the SSI output by calling the SSI function SsiOutput 7 3 1 SSI Output String File If the file Assi_str cfg is found in the file system and the file is consistent with the specification below the SSI functions will use the output strings specified in this file instead of the default strings The files shall have the following format StoreEtnConfig Success String to use on success Invalid IP String to use when the IP address is invalid Invalid Subnet Invalid Gateway Invalid Em
23. in the Anybus Configuration Manager and selecting Add Command Anybus Communicator for PROFINET Doc Rev 3 01 Doc Id SCM 1200 088 DF1 Protocol Mode 80 15 2 ABC Parameters im i Select ABC in the Navigation Section to gain access to the parameters se TE described in this section A 4 Sub Network Interface Currently only serial communication is supported Status Control Word See Control and Status Registers on page 95 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 event of a fatal error VENTE 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 VENTE 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 m
24. page The formatting of the string is similar to the C language function printf Syntax lt Fexec cmd argument printt steing to write Argl Arga vesp ACTON gt Like the C language function print the String to write for this SSI function contains two types of objects Ordinary characters which are copied to the output stream and conversion specifications each of which causes conversion and printing of the next successive argument to printf Each conversion specification begins with the character and ends with a conversion character Between the and the conversion character there may be in order e Flags in any order which modify the specification which specifies left adjustment of the converted argument in its field which specifies that the number will always be printed with a sign space if the first character is not a sign a space will be prefixed 0 for numeric conversions specifies padding to the field with leading zeroes H which specifies an alternate output form For o the first digit will be zero For x or X Ox or 0X will be prefixed to a non zero result For e E f g and G the output will always have a decimal point for g and G trailing zeros will not be removed e A number specifying a minimum field width The converted argument will be printed in a field at least this wide and wider if necessary If the converted argument has fewer characters than the field width it will be padd
25. spontaneously i e without first receiving a query 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 Anybus Communicator which features a dedicated broadcaster node Control System Gateway Subnetwork Devices Node 1 Node 2 In Master Mode Anybus Configuration Manager comes preloaded with most commonly used Modbus RTU commands which can conveniently 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 PROFINET Doc Rev 3 01 Doc Id SCM 1200 088 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 Any bus Communicator Any node including the module may spontaneously produce or consume a mes sage Nodes do not have to respond to messages nor do they have to wait for a query in order to send one Control System Gateway Subnetwork Devices Consume Ra is Produce Node 1 Progiices eo Consume Produce pensas Consume Node 2 Consume d Produce In the figure above the Anybus Communicator
26. 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 59 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 75 For DF1 Master Mode see Services on page 82 In Generic Data Mode no predefined commands exist but custom ones may be implemented as desired 14 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 amp Select Command X File Command D we 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 soa Holding Registers to the node eset Sing i i ae n na Just like other transactions the frame objects of added command xOB Fetch Comm Event Ctr Seed ie
27. to the SSI function scanf are Argument Description OutWriteByte offset Write a byte to position offset in the Output Data area OutWriteWord offset Write a word to position offset in the Output Data area OutWriteLong offset Write a long to position offset in the Output Data area OutWriteString offset Write a string to position offset in the Output Data area OutWriteFloat offset Write a floating point value to position offset in the Output Data area Default output Write succeeded Write failed Anybus Communicator for PROFINET Doc Rev 3 01 Doc Id SCM 1200 088 Server Side Include SSI 45 IncludeFile This function includes the contents of a file on a web page Syntax lt exec cmd argument Includerile File name gt Default output Success lt File content gt Failure Failed to open lt filename gt SaveToFile Note This function cannot be used in e mail messages This function saves the contents of a passed form to a file The passed name value pair will be written to the file File name separated by the Separator string The Append Overwrite parameter deter mines if the specified file shall be overwritten or if the data in the file shall be appended Syntax lt exec cmd_argument SaveToFile File name Separator Append Over write gt Default output Success Form saved to file Failure Failed to save form SaveDataToFile Note This function cannot
28. 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 PROFINET Doc Rev 3 01 Doc Id SCM 1200 088 DF1 Protocol Mode 84 15 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 15 7 Read Diagnostics This service reads diagnostic information from the module ABC DF 1 Master Untitled Devices Configuration Alphabetic Categorized E Command Params Size 0x02 EY Integrity Check El Data Options Co A ead Diagnostics Byte swap No byte swap T Node 2 Data Length 0x02 Offset 0x0000 E General Offline options for fieldbus Clear Offline options for sub network Clear Update mode Cyclically E Timing Retries Timeout time 10ms Update time 10ms BE 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 i
29. with IO Controller established o A 0 10 Controller in STOP state 2 Module Status Off No power or not initialized Green Initialized no error Green 1 flash Diagnostic data available Green 2 flashes Blink Used by engineering tools for identification Red 1 flash Configuration Error Too many modules submodules l O size or Configuration mismatch Red 3 flashes No Station Name or no IP address assigned Red 4 flashes Internal error 3 Link Activity Off Green No link or power off Link established Green flashing Receiving transmitting data 4 not used 5 Subnet Status 6 Device Status Off Power off Green flashing Running correctly but one or more transaction error s have occurred Green Running Red Transaction error timeout or subnet stopped Off Power off Alternating Red Green Invalid or missing configuration Green Initializing Green flashing Running Red Bootloader mode Red flashing If the Device Status LED is flashing in a sequence Starting with one or more red flashes please note the sequence pattern and contact the HMS support department 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 gatewa
30. yen COP mms Wizard Modbus RTU Master Physical standard RS232 y Step 20f6 Bitrate bits s asno El Select ri properties Parity None E Data bits g X Stop bits y y gt lo ryBus B i Sub I Lo network This is where the properties for the sub network are selected Please see the sub network device s manual to determine the appropriate settings for a particular serial device lt Back gt o Cancel Please see the manual for the sub network device to determine Y Doc Id SCM 1200 088 Chapter 20 20 Control and Status Registers 20 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 56 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 these 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 I
31. 19 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 52 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 adapter e Wizard Modbus RTU Master This option is suitable for Modbus RTU based net works See also Wizard Modbus RTU Master on page 94 e Blank Configuration This option creates an empty configuration Highlight the desired wizard and click OK to continue Anybus Communicator for PROFINET Doc Rev 3 01 Select Configuration _ K SA zg m se ee yl Cancel ABCC ExtLink Wizard Wizard Modbus Blank Configuration RTU Mast aster Select the desired topic to do and press the OK button 4 vizard option will guide you through 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 f
32. 2 16 bytes Input Output 3 128 bytes Input 4 64 bytes Input Output 5 32 bytes Input 6 64 bytes Output 7 128 bytes Output Resulting memory layout Input Data Output Data 0x000 OxOOF y 0x200 Ox20F 0x010 OxO1F 0x210 0x24F 128 Input saa lO Size In Supl 256 bytes 0x28F 0x09F 0x290 0x0A0 64 Input Output IO Size Out OXODF 3 128 Output 400 bytes OxOEO OxOFF 0x100 Record Data Index 1000h Jy 0x30F 0x310 unused 0x38F 0x390 Record Data Index 2000h Ox1FF Record Data Index 10FFh 0x3FF Record Data Index 206Fh Note the unused part of the output data area The reason for this is that although IO Size Out is set to 400 only 272 bytes 128 64 64 16 are actually used in the I O module configuration hence it will not be exchanged on PROFINET Anybus Communicator for PROFINET Doc Rev 3 01 Doc Id SCM 1200 088 2 5 Modbus TCP Read Only 2 5 1 General Basic Operation 24 The Modbus TCP protocol is an implementation of the standard Modbus protocol running on top of TCP IP The same function codes and addressing model are used The built in Modbus TCP server provides read only access to the input and output data areas via a subset of the functions defined in the Modbus TCP specification All Modbus TCP messages are received transmitted on TCP port no 502 For detailed information re garding the Modbus TCP protocol consult the Open Modbus Spe
33. 5255 0 AP Settings Enabled IO E Fieldbus i Profinet lO BE 10 Sizes IO Sizes TCP IP Settings Profinet lO To be able to participate on the network the following settings must be configured e Communicator IP address Fieldbus Type see Basic Network Configuration on page 27 Configuration Alphabetic Categorized E Ethernet TCP IP configuration e Default Gateway ee Subnet Mask 255 255 255 0 see Basic Network Configuration on page 27 ada Fieldbus Type Profinet lO E 10 Sizes IO Sizes Automatic x Subnet Mask Automatic User defined see Basic Network Configuration on page 27 e TCP IP Settings Enabled Use the settings above Disabled Use the settings stored in ethcfg cfe lO Sizes IO Sizes These parameters specify how data from the internal memory buffer shall be exchanged on PROFI NET This can either be handled automatically by the module or specified manually e Automatic All data will be represented as I O Data see also Data Representation IO Data amp Record Data on page 23 e User defined Additional parameter properties appear IO Size In and IO Size Out The specified amount starting at address 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 Data Representation IO Data amp Record Data on page 23 Anybus
34. ABC Internal Memory This means that in order to exchange data with the sub d 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 The internal memory buffer is divided into three areas a a based on their function e Input Data 512 bytes Subnetwork This area can be read by the higher level net work the web server and the e mail client Higher Level Network How this data is represented on the higher level network will be described later in this chapter E General Data e Output Data 512 bytes This area can be read from written to by the higher level network the web server and the e mail client How this data is represented on the higher level network will be described later in this chapter e General Data Up to 1024 bytes This area cannot be accessed from the higher level network but can be used for transfers be tween 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 Anybus Communicator can handle up to 1024 bytes of general data 2 2 1 Memory Map When building the subnetwork configuration using the Anybus Configuration Manager the different ar eas described above ate mapped to the memory lo
35. HICP on page 30 SSI See Server Side Include SSI on page 36 DHCP BootP See DHCP BootP on page 27 Mailbox Commands See Mailbox Editor on page 100 See also FTP Server on page 31 Fieldbus Settings on page 55 Anybus Communicator for PROFINET Doc Rev 3 01 Doc Id SCM 1200 088 Basic Network Configuration 29 4 3 PROFINET Settings The file pnio cfg holds various PROFINET related settings The file is read once during startup ie the Anybus Communicator must be restarted in order for any changes to have effect unless its contents has been changed by an IO Controller Supervisor via the DCP protocol In such case the settings will have effect immediately Example 1 Station Name Station Name Station name as ASCII string maximum 64 characters Nice Device Station Type Station Type ABS PRT Station type as ASCII string maximum 64 characters Vendor ID 0x010C e Vendor ID 16 bit hexadecimal value with the prefix Ox Assigned Device ID by the PNO 0x0001 a ee Device ID 16 bit hexadecimal value with the prefix Ox Assigned by vendor 4 4 IP Access Control It is possible to specify which IP addresses that are permitted to connect to the Anybus Communicator This information is stored in the system file ip_accs cfg File Format Web l XXX xxx xxx xxx___ Nodes listed here may access the web server FTP XXX xxx xxx
36. I output for the next called SSI function can be changed with the SSI function SsiOutput The next called SSI function will use the output according to this call Thereafter the SSI functions will use the default outputs or the outputs defined in the file ssi_str cfg The maximum size of a string is 128 bytes Syntax lt exec cmd argument Ss10utput Success string Failure string gt Example This example shows how to change the output strings for a scanf SSI call lt exec cmd_argument SsiOutput Parameterl updated Error gt lt exec cmd argument scanf Parameteri sd OutWriteByte 0 gt Anybus Communicator for PROFINET Doc Rev 3 01 Doc Id SCM 1200 088 Chapter 8 8 E mail Client 8 1 General The built in e mail client can send predefined e mail messages based on trigger events in Input and Output Data areas The client supports SSI however note that some SSI functions cannot be used in e mail messages specified separately for each SSI function See also e Server Side Include SSI on page 36 Server Settings The Anybus Communicator needs a valid SMTP server configuration in order to be able to send e mail messages These settings are stored in the system file A ethcfg cfg See also e Ethernet Configuration File ethcfg cfe on page 28 Event Triggered Messages As mentioned previously the e mail client can send predefined messages bas
37. 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 95 Control Register Contents Control System to Gateway on page 99 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 97 Status Code in Generic Data Mode on page 98 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 20 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 the 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
38. O 59 Kode Paramete a do miecadeusnucees 59 Maser Modeand Genen Data ei 59 Chapter 12 Transactions A E A E E EA E E E E A E E E A O Ren ore 60 Adamo Mando mo Transicion orilla 61 Transaction Parameters Master Mode nulos ta li 62 COFRES DUCADOS atra scada 62 DOTAR APO A AA AAA E T 64 Transaction Parameters Generic Data Mode nosaci ii d a 64 AOL TAN A eueas E E cea tod enastmia eset tatoo 64 EA AA A TEAT A r maura costae AE AEE naa sasoueenemtae 65 Trinsacuon dto tilo 66 Chapter 13 Frame Objects Central ca dada aida 67 Addis and Editing Trane Objects iii 67 Constant Objects Byto Word DWO sine 68 Ent ODjects Byres Word WO ayi A IA 69 DirObedt dd a dida 70 Variable DADAS AA da 70 Checksum ODECE A AA AE 12 Chapter 14 Commands A o E T 73 Addie Sev anaconda oc ii Machen 13 PAUD OU NE eis fi ct cite ios 74 O 74 TreCommand totor ple recia puso 75 O A 13 DEAN AE io 75 VS IN AAA EEEE crea cues N ecco tetne sie T T 76 FE GUE OTRA eta AA isaac ET Example Specifying a Modbus RTU Command in Master Mode icecscccscccscscscssssssscsssessseseees 78 Anybus Communicator for PROFINET Doc Rev 3 01 Doc ld SCM 1200 088 Chapter 15 Chapter 16 Chapter 17 Chapter 18 Chapter 19 Chapter 20 DF1 Protocol Mode Ss cases E E EN 79 Eo O TE E E me EE E E OT E a da E 80 SUMS EW or Paran et ES A satan daeinedensaneses 81 Node Paramet aaa a nide 82 de 82 IVA DESEE A A A eda A A A as 83 INCA O AL ISS TS Us 84 Read Danos ita ooo 84
39. a is detected Single shot The Query is issued once at start up e 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 PROFINET Doc Rev 3 01 Doc Id SCM 1200 088 Transactions 63 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 PROFINET Doc Rev 3 01 Doc Id SCM 1200 088 Transactions 64 12 3 2 Parameters Response To gain 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 byt
40. ail server Invalid IP or Subnet not match String to use when the Subnet mask is invalid String to use when the Gateway address is invalid String to use when the SMTP address is invalid String to use when the IP address and Subnet mask does Invalid DNS1 String to use when the primary DNS cannot be found Invalid DNS2 String to use when the secondary DNS cannot be found Save Error String to use when storage fails Invalid DHCP state scanf Success String Failure String IncludeFile Failure String SaveToFile Success String Failure String SaveDataToFile Success String Failure String GetText Success String Failure String on the second Example File path LO to toO to to to to toO to String to use when the DHCP state is invalid use use use use use use use use use user ssi_strings cfg on success on failure when failure on success on failure on success on failure on success on failure The contents of this file can be redirected by placing the line File path on the first row and a file path In this example the settings described above will be loaded from the file user ssi_strings cfg Anybus Communicator for PROFINET Doc Rev 3 01 s includes the filename in the string Doc Id SCM 1200 088 Server Side Include SSI 47 7 3 2 Temporary SSI Output Change The SS
41. al 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 is 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 18 2 Operation Start 8 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 e Stop logging 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 Select Log Mode Log until full e Log continuously Data will be logged continuously until logging 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 C
42. an 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 D setting see Basic Navigation on page 75 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 59 other settings Other settings are no longer supported Anybus Communicator for PROFINET Doc Rev 3 01 Doc Id SCM 1200 088 Commands 78 14 3 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 Obje
43. ary No subnetwork functionality e Use the Data logger functionality to record the serial data communication on the subnetwork e If no 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 PROFINET Doc Rev 3 01 Doc Id SCM 1200 088 Appendix D D ASCII Table NUL SOH STX ETX EOT ENQ ACK BEL BS HT LF VT FF CRIS Si 0 1 2 3 4 5 6 T 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 A B C D E F G H J K L M N O 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 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
44. ase the ABC Module or I O module Hardware or logical component of a PROFINET network device Higher Level Network In this case PROFINET Network Fieldbus IO Supervisor Anybus Communicator for PROFINET Doc Rev 3 01 Doc Id SCM 1200 088 Sales and Support About This Document P 10 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 Free 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
45. c 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 Anybus Communicator for PROFINET Rev 3 01 Copyright HMS Industrial Networks AB Sept 2011 Doc Id SCM 1200 088 Table of Contents Table of Contents Preface About This Document Related DOCM id 8 DIO CAM EE AO a AAA A A 8 Convention S Term MOOO dodo cdas 9 CCS SA da ao a a a 9 Salesiana SUP POE Eaei a var erie ited dial 10 Chapter1 About the Anybus Communicator for PROFINET Cenerale a tema wove sees etree ee aint 11 Ds A G atcle nade GO ET 12 O 13 Hardware asta iia 14 SO Mare Dist Alia IO MA 15 PAU OUS CONT OUTE OU MUAT RN onions aie cumetiear A E A 15 Chapter2 Basic Operation A E O N in 16 Ditrbrchanse Modelirne ene AA a snauiveainudt 17 MERO AD EON T O E A A E E iaeaeuet ees Ly Dari E A A 18 Subne ote FLO COCO Lt Aa 19 E T T E E E A E E 19 E AE LA AAA AAA E E AAA E A R 19 DEAT A A E AE 20 E D E AA A al DELI E T A A E E E io E E al PROFINET TO 22 a dd 22 TAO COTE AA ASA AS iia E T T 22 E O 22 Dala testar QO Dara Rercord Dila ti ida 23 Modbus TCP Read OA A A daba 24 E EE NE A E PA E A O dna aaasiaus 24 Data Represen
46. canned for SSI Area Source area Possible values IN Input Data area or OUT Output Data area No Offset Source offset written in decimal or hexadecimal Type Source data type Possible values are byte word and long Value Used as a reference value for comparison Mask Mask value applied on the trigger source prior to comparison logical AND Operand Possible values are lt or gt To E mail recipient Yes From Sender email address Subject E mail subject One line only Headers Optional may be used to provide additional headers Message The actual message Note Hexadecimal values must be written with the prefix Ox in order to be recognized by the module Anybus Communicator for PROFINET Doc Rev 3 01 Doc Id SCM 1200 088 Chapter 9 9 Navigating the Anybus Configuration Manager 9 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 SHS 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 E Response Preset Multiple Regs El Query El Response Subnet Mask TCP IP Settings 3 Fieldbus Fieldbus Type A 10 Sizes IO Sizes
47. cations addresses specified below Input Data Output Data General Data 0x000 0x200 0x400 Subnetwork Read Write Fieldbus Read Only E mail Client Read Only Subnetwork Read Write Fieldbus E mail Client Subnetwork Read Only Fieldbus Read Write E mail Client Read Only SSI Read Only SSI Read Write SSI Ox1FF 0x3FF 0x22 Anybus Communicator for PROFINET Doc Rev 3 01 Doc ld SCM 1200 088 Basic Operation 18 2 2 2 Data Exchange Example In the following example a temperature regulator on the subnetwork exchanges information with a PLC on the higher level network via the internal memory buffers in the module PLC PROFINET IO Controller 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 PROFINET network PROFINET Input Data Output Data General Data Oo 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 Reg
48. cel to abort Optionally the configuration may be protected from unauthorized access by a password To enter a password click on the Change password checkbox and enter the password under New password When protected any changes in the configuration requires that the user supplies a valid password When done click Set The new IP configuration will now be stored in the configuration file eth cfe cfo Note that if TCP IP Settings has been enabled in the Anybus Configuration Manager any settings re ceived via HICP will be lost in the event of a power loss or reset Anybus Communicator for PROFINET Doc Rev 3 01 Doc Id SCM 1200 088 Chapter 5 5 FTP Server 5 1 General The built in FTP server provides a way to access the file system using a standard FTP client The following port numbers are used for FTP communication e TCP port 20 FTP data port e TCP port 21 FTP command port Security Levels The FTP server features two security levels admin and normal e Normal level users The root directory will be user e Admin level users The root directory will be 1 i e the user has unrestricted access to the file system User Accounts The user accounts are stored in two files which are protected from web access e user pswd sys_pswd cfg This file holds the user accounts for normal level users e pswd ad_pswd cfg This file holds the user accounts for ad
49. cification 2 5 2 Data Representation Modbus TCP Register Map The following function codes are implemented Modbus Function Read Input Registers Function Code 4 Associated with Area Input Data area 0x000 0x1FF Read Multiple Registers 3 Output Data area 0x200 0x3FF The Input amp Output Data areas are mapped to Modbus registers as follows Register Type Register Memory Location Area Comments Input Registers 0x0000 0x000 0x001 Input Data area Status Register 3XXxx 0x0001 0x002 0x003 0x0002 0x004 0x005 0x0003 0x006 0x007 Ox00FF 0x1FE Ox1FF Output Registers 0x0000 0x200 0x201 Output Data area Control Register 4xxxx 0x0001 0x202 0x203 0x0002 0x204 0x205 0x0003 0x206 0x207 Ox00FF Ox3FE OXx3FF Note If enabled the control and status registers occupies input register Ux0000 and output register 0x0000 2 5 3 Supported Exception codes Code Name Description 0x01 Illegal function The function code in the query is not supported 0x02 illegal data address The data address received in the query is outside the initialized memory area 0x03 illegal data value The data in the request is illegal Anybus Communicator for PROFINET Doc Rev 3 01 Doc Id SCM 1200 088 Chapter 3 3 File System 3 1 General General The Anybus Communicator features a built in file system which is used to stor
50. 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 21 2 Mailbox Editor 88 Fieldbus To add a mailbox message to the configuration right click on Y atartinit c we c gt a Field ifi EndInit and select Insert New Mailbox e Fieldbus specific Pal Insert New Malbox 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 sage information field that is fixed to 0x4002 which means that only fieldbus specific mail box messages can be entered here a nan The mailbox message is presented as two col umns one con
51. ct 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 59 e 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 This object will retrieve its settings from the correspond ing object in the Query By default the Modbus RTU 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
52. ction call scanf Syntax lt Fexec cmd argument scani Obj Name format Arg ssp ArFON Errvall ErrvalN gt ObjName The name of the object with the passed data string format Specifies how the passed string shall be formatted Argl ArgN Specifies where to write the data ErrVall ErrVaIN Optional specifies the value string to write in case of an error Character Input Argument Type d Decimal number byte short Number byte short The number may be in octal leading 0 zero or hexadecimal leading 0x or 0X 0 Octal number with or without leading zero byte short u Unsigned decimal number unsigned byte unsigned short X Hexadecimal number with or without leading 0x or 0X byte short C Characters char The next input characters default 1 are placed at the indicated spot The normal skip over white space is suppressed to read the next non white space character use 1s S Character string not quoted char pointing to an array of characters large enough for the string and a terminating 0 that will be added e f g Floating point number with optional sign optional decimal point and optional exponent float Literal no assignment is made The conversion characters d 1 o u and x may be preceded by letter ell to indicate that a pointer to long appears in the argument list rather than a byte or a short The arguments that can be passed
53. ctions 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 is 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 PROFINET Doc Rev 3 01 Doc Id SCM 1200 088 Chapter 17 17 Node Monitor 17 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 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 1 e it should be used only when necessaty 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
54. d 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 088 Parameter Trigger byte address Transactions 65 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 system 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 stat
55. d a checksum object Transaction 13 2 Adding and Editing Frame Gass a W Sub Network Objects T New Node Transactions 1 ER Edt Transaction Add Data To add a frame object to a Transaction right click on the Transac Add Variable Data tion in the Navigation Section and select one of the entries in the a Add Byte Constan menu that appeats Add Word Constant Add DWord Constant The entry called Transaction Editor will launch the Transaction Add Byte Limits y Add Word Limits Editor which is used to edit transactions and frame objects in a aa mote visual manner For more information see Transaction Edi Rename tor on page 66 Configuration Alphabetic Categorized 3 General Data length 0x0001 Data location 0x0200 oO Operations o 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 It is also possible to edit the frame objects in a transaction in a more visual manner using the Transaction Editor see Transac tion Editor on page 66 Data Object Parameters Anybus Communicator for PROFINET Doc Rev 3 01 Doc Id SCM 1200 088 Frame Objects 68 13 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 Con
56. d 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 DF See also Protocol Modes on page 19 Anybus Communicator for PROFINET Doc Rev 3 01 Doc ld SCM 1200 088 57 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 PROFINET Doc Rev 3 01 Doc Id SCM 1200 088 58 10 3 Subnetwork Parameters Fieldbus A ABC Seg al Sub Metwaork 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 Select
57. dULong offset Read an unsigned longword from position offset in the Input Data area InReadString offset Read a string char from position offset in the Input Data area InReadFloat offset Read a floating point float value from position offset in the Input Data area OutReadSByte offset Read a signed byte from position offset in the Output Data area OutReadUByte offset Read an unsigned byte from position offset in the Output Data area OutReadSWord offset Read a signed word short from position offset in the Output Data area OutReadUWord offset Read an unsigned word short from position offset in the Output Data area OutReadSLong offset Read a signed longword long from position offset in the Output Data area OutReadULong offset Read an unsigned longword long from position offset in the Output Data area OutReadString offset Read a null terminated string from position offset in the Output Data area OutReadFloat offset Read a floating point float value from position offset in the Output Data area Anybus Communicator for PROFINET Doc Rev 3 01 Doc Id SCM 1200 088 scanf Server Side Include SSI 44 Note This function cannot be used in e mail messages This function reads a string passed from an object in a HTML form interprets the string according to the specification in format and stores the result in the Output Data area according to the passed argu ments The formatting of the string is equal to the standard C fun
58. e 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 PROFINET Doc Rev 3 01 Doc Id SCM 1200 088 Appendix C C 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 serial 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 Is the 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 necess
59. e Rename Doc Id SCM 1200 088 Transactions 62 12 3 Transaction Parameters Master Mode 12 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 e Clear The data destined for the slave devices is cleared set to zero e Freeze The data destined for the slave device is frozen e 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
60. e Command Doc Id SCM 1200 088 Commands 75 14 3 The Command Editor 14 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 14 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 com 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 Checksum ObjectType Byte Byte Checksum Value SlaveAddress ID Depend A Pull down Menu See Pull down Menu on page 76 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 comma
61. e information such as web files network communication settings e mail messages etc Storage Areas The file system consists of the different storage areas e Non volatile area approx 2 Mb This section is intended for static files such as web files configuration files etc e Volatile area approx 1 Mb This area is intended for temporary storage data placed here will be lost in case of power loss or reset Important Note The non volatile storage is located in FLASH memory Each FLASH segment can only be erased ap proximately 100000 times due to the nature of this type of memory The following operations will erase one or more FLASH segments e Deleting moving or renaming a file or directory e Writing or appending data to an existing file Formatting the file system Conventions e V backslash is used as a path separator e A path originates from the system root and as such must begin with a VY e A path must not end with a e Names may contain spaces but must not begin or end with one e Names must not contain one of the following characters A lt gt e Names cannot be longer than 48 characters plus null termination e A path cannot be longer than 256 characters filename included e The maximum number of simultaneously open files is 40 e The maximum number of simultaneously open directories is 40 Anybus Communicator for PROFINET Doc Rev 3 01 Doc Id SCM 1200 088 File Sy
62. e 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 12 4 Transaction Parameters Generic Data Mode 12 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 e Clear Data is cleared 0 on the subnetwork if the higher level network goes offline e 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 PROFINET Doc Rev 3 01 The update mode for the transaction e 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 e Change of state on trigger The transaction is sent when the trigger byte has change
63. e on trigger Valid settings range from 0x200 Ox3FF and 0x400 OXNNN 12 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 e Clear Data is cleared 0 on the higher level network if the subnetwork goes offline e 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 e Enable Enables the trigger byte The location of 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 t
64. e options for fieldbus Clear Offline options for sub network Clear Parameter Description Valid settings a A A A A AAA A A A A E E Timing Offline options for The action to take for this service Clear E Timeout time 1Oms 100 fieldbus if the fieldbus goes offline This Freeze Update time 10ms 100 i 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 Ox05FF 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 steps 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 e 99 represents a poll time of 990 ms and 101 represents a poll time of 1010 ms Trigger Parameter Description Default Request Trigger byte The memory location of the
65. ecify the sizes of the input and output data areas For more information see IO Sizes on page 55 Click Next to continue Step 2 Physical Settings Select the physical properties of the sub network Click Next to continue Steps 3 6 Consult the online help system for fur ther information Anybus Communicator for PROFINET Doc Rev 3 01 Fieldbus Type The type of the Fieldbus connected to the Communicator Profinet 10 AK Wizard Modbus RTU Master Version 1 14 Revision 1 Next gt Cancel type The purpose of this wizard is to help you through the process of creating a project with a Modbus RTU sub network When the Wizard is finished it is possible to continue editing the project in the Configuration Tool The fieldbus is the higher layer network that communicates with the serial device s on the sub network via the Communicator ieldbus Master fie PLC HMI Etc Wizard Modbus RTU Master Version 2 Enabled X Extension cycle Occupied station 4 gt Step 1a of 6 Select settings for the chosen fieldbus Fieldbus Master The fieldbus used might offer special features that can be configured Click the list below to see available settings and their meaning Only fieldbuses with specific settings are listed here lt Back J ee 4 cano
66. ed Fill unused data with the value specified in Filler byte e 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 e 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 e 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 be 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 PROFINET Doc Rev 3 01 Doc Id SCM 1200 088 Frame Objects 72 13 7 Checksum Object Most serial protocols features some wa
67. ed on events in the Input and Output Data areas In operation this works as follows The trigger source is fetched from a specified location A logical AND is performed between the trigger source and a mask value The result 1s compated to a reference value ae ae ee If the result is true the e mail is sent to the specified recipient s Which events that shall cause a particular message to be sent 1s specified separately for each message For more information see E mail Definitions on page 49 Note that the Input and Output Data areas are scanned twice per second i e to ensure that an event is detected by the module it must be present longer than 0 5 seconds Anybus Communicator for PROFINET Doc Rev 3 01 Doc Id SCM 1200 088 E mail Client 49 8 2 E mail Definitions The e mail definitions are stored in the following two directories user email This directory holds up to 10 messages which can be altered by normal level FTP users email This directory holds up to 10 messages which can be altered by admin level FTP users E mail definition files must be named email_1 cfo email_2 cfg email_10 cfe in order to be prop etly recognized by the module File Format Register Area Offset Type Register Match Value Mask Operand To recipient From sender Subject subject line Headers Optional extra headers Message message body Key Value S
68. ed on the left or right if left adjustment has been requested to make up the field width The padding character is normally space but can be 0 if the zero padding flag is present e lt A period which separates the field width from the precision e A number the precision that specifies the maximum number of characters to be printed from a string or the number of digits to be printed after the decimal point for e E or F conversions or the number of significant digits for g or G conversion or the minimum number of digits to be printed for an integer leading Os will be added to make up the necessary width e A length modifier h 1 letter ell or L h Indicates that the corresponding argument is to be printed as a short or unsigned short 1 indicates that the argument is along or unsigned long Anybus Communicator for PROFINET Doc Rev 3 01 Doc Id SCM 1200 088 Server Side Include SSI 42 The conversion characters and their meanings are shown below If the character after the is not a con version character the behavior is undefined Character Argument type converted to d byte short decimal notation For signed representation Use signed argument O byte short octal notation without a leading zero X X byte short hexadecimal notation without a leading 0x or 0X using abcdef for 0x or ABCDEF for 0X u byte short decimal notation C byte short single character after conver
69. 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 90 Anybus Communicator for PROFINET Doc Rev 3 01 Doc ld SCM 1200 088 Node Monitor 89 17 2 1 Pull Down Menu File There is only one entry in this menu Exi Fe This will close the Node Monitor Note however that if the node has Exit 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 node 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 subnetwork Command Send Command Select Command Send the specified comma
70. elp 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 PROFINET Doc Rev 3 01 Doc ld SCM 1200 088 Navigating the Anybus Configuration Manager 54 9 1 2 Toolbar Icons The toolbar features icons for the most commonly used functions e New Open amp Save a See File on page 51 L ew pen e Upload from ABC amp Download to ABC See Tools on page 52 Wee Le Upload Download e Up one Level ly Clicking on this icon will move the selection in the navigation section Up one Level e Cut Copy Paste Delete Insert M These icons are used for common editing func E Cut Copy Paste Delete Insert tions in the navigation section e 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 pe Disconnect from the gateway e Start Logging amp Stop Logging o E e By ge See Tools on page 52 amp Data Logger on page 91 ES Start Log Stop Log e Subnetwork Monitor Clicking on this icon will launch the subnetwork Monitor see Subnetwork Monitor o
71. er Anybus Communicator for PROFINET Doc Rev 3 01 Doc Id SCM 1200 088 Chapter 16 16 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 if 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 1t 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 DeselectAll SelectAll Deselect All SelectAll Deselect All Read Coil Status Read Coil Status Transactions 1 M trans actions 1 atus a 32 Mr atus ead Coil Status Out Area 0 bytes 512 General Area 0 bytes 989 ooo0oo0oo0ooooooooooooooooo e Response Collision Trigger or Statusbytes Reserved A Start Network amp Stop Network Icons These icons controls the subnetwork activity To stop all subnetwork gi activity click on the red light To start the subnetwork again click on the green light Start B Nodes Transa
72. f the higher level net work uses a different byte order the upper and lower bytes will appear swapped 20 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 PROFINET Doc Rev 3 01 Doc Id SCM 1200 088 Control and Status Registers 96 20 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 is 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 A Offline No data exchange 1 Clear the Data Valid bit in the Con trol Register 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 5 Online not
73. for PROFINET Doc Rev 3 01 Doc Id SCM 1200 088 About the Anybus Communicator for PROFINET 12 1 2 External View For wiring and pin assienments see Connector Pin Assienments on page 101 8 p 8 gt B pag A PROFINET Connector Ethernet This connector is used to connect the module to the net work See also PROFINET Connector Ethernet on page 101 B Status LEDs See also Status LEDs on page 13 C PC connector This connector is used to connect the module to a PC for configuration and monitoring purposes See also PC Connector on page 102 D Subnetwork Connector This connector is used to connect the module to the serial subnetwork See also Subnetwork Interface on page 102 E Power Connector This connector is used to apply power to the module See also Power Connector on page 101 Technical Specification on page 105 F DIN rail Connector The DIN rail mechanism connects the module to PE Protective Earth See also Hardware Installation on page 14 Anybus Communicator for PROFINET Doc Rev 3 01 Doc ld SCM 1200 088 1 3 Status LEDs 1 Comm Status About the Anybus Communicator for PROFINET 13 State Status Off Off line No connection with IO Controller Green On line Run Connection with IO Controller established O O 10 Controller is in RUN state Ca Green flashing On line STOP O 2 0 Connection
74. function cannot be used in e mail messages This function stores a passed IP configuration in the configuration file ethcfg cfe Syntax lt exec cmd_argument StoreEtnConfig gt Include this line in a HTML page and pass a form with new IP settings to it Accepted fields in form Set Ip SetSubnet SetGateway SetEmailServer SetDhcpState value on or off SetDNS1 SetDNS2 SetHostName SetDomainName SetSMTPUser Set SMTPPswd Default output Invalid IP address Invalid Subnet mask Invalid Gateway address Invalid IP address or Subnet mask Invalid Email Server IP address Invalid DHCP state Invalid DNS1 Invalid DNS2 Configuration stored correctly Failed to store configuration GetText Note This function cannot be used in e mail messages This function retrieves a text string from an object and stores it in the Output Data area Syntax lt exec cmd_argument GetText ObjName OutWriteString offset n gt ObjName Name of object offset Specifies the destination offset from the beginning of the Output Data area n Specifies maximum number of characters to read Optional Default output Success Write succeeded Failure Write failed Anybus Communicator for PROFINET Doc Rev 3 01 Doc Id SCM 1200 088 Server Side Include SSI 41 printf This function includes a formatted string which may contain data from the input and output data areas on a web
75. g or contains invalid settings the module will halt and indicate an error on the onboard status LEDs The network configuration may however still be accessed via HICP see Anybus IPconfig HICP on page 30 Anybus Communicator for PROFINET Doc Rev 3 01 Doc Id SCM 1200 088 Basic Network Configuration 28 4 2 Ethernet Configuration File ethcfg cfg 4 2 1 General To be able to participate on the network the Anybus Communicator needs a valid TCP IP configura tion These settings are stored in the system file ethcfg cfg File Format IP address XXX XXK XXK XKK Subnet mask XXX XXK XKXK XKK IP address Gateway address XXX XXX XXX XXX Subnet mask Gateway address DHCP BOOTP oN or Or DHCP BootP SMTP address ON Enabled XXX XXX XXX XXX OFF Disabled SMTP username SMTP server login settings username Username and Password is only necessaty 1f required by the SMTP password server password DNS1 address XXX XXX KKK XXX DNS2 address Primary and Secondary DNS XXX XXX XXX XXX Needed to be able to resolve host names Domain name ______ Default domain name for not fully qualified host names domain Host name Host name anybus HICP password _____ HICP password password The settings in this file may also be affected by DCP See DCP Discovery and Basic Configuration on page 27 HICP See Anybus IPconfig
76. hat when using this feature make sure to put the user password files in a directory that is pro tected from web access see Protected Files on page 33 Anybus Communicator for PROFINET Doc Rev 3 01 Doc Id SCM 1200 088 6 3 Content Types Web Server 35 By default the following content types are recognized by their file extension Content Type File Extension text html htm html shtm image gif gif image jpeg jpeg jpg jpe image x png png application x javascript js text plain bat txt c h cpp hpp application x zip compressed zip application octet stream exe com text vnd wap wml wml application vnd wap wmlc wmlc image vnd wap wbmp wbmp text vnd wap wmlscript wmls application vnd wap wmlscriptc wmlsc text xml xml application pdf pdf It is possible to configure reconfigure the reported content types and which files that shall be scanned for SSI This is done in the system file http cfg File Format FileTypes FileTypel ContentTypel FileType2 ContentType2 FileTypeN ContentTypeN SSIFileTypes FileTypel FileType2 FileTypeN Note Up to 50 content types and 50 SSI file types may be specified in this file Anybus Communicator for PROFINET Doc Rev 3 01 Doc Id SCM 1200 088 Chapter 7 7 Server Side Include SSI 7 1 General Server Side Include from now on referred to as SSI functionalit
77. he subnetwork Disable Disables the trigger byte functionality Trigger byte address Anybus Communicator for PROFINET 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 088 Transactions 66 12 5 Transaction Editor 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 Transaction Y Byte constant T f Ea constant Frame y Checksum Objects _ 9 Byte constant Transz on Editor TOX File Byte constant Ward constant Data Checksum Byte constant Value Value Data location Data length Byte swap Error check type Error check start byte Walue 0x00 0x0000 0x0200 0x0010 No swapping 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 Hen Apply Changes Apply Changes i This will save any changes and exit to the main Exit Ctr
78. hecksum 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 15 5 Services Services are 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 service it automatically chooses the appropriate DF1 command s that are used to perform the service on the selected DF1 node type Anybus Communicator for PROFINET Doc Rev 3 01 Doc Id SCM 1200 088 DF1 Protocol Mode 83 15 5 1 Available Services Right click on the node and choose Add Command A pop up window will show the four different servic Y Select Command es that are available File Command e Integrity check 7 gt e Read diagnostics el ee ere e Read data e Write data Integrity Check 002 Read Diagnostics O03 Read Data Ox04 Write Data EE amp amp A maximum of 50 services in total for all nodes can be selected The predefined services 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 Is are individual to each instance of a service Configuration Alphabetic Categorized General E General Offlin
79. her the merchantability of this software or the suitability of this software for any particular purpose It is provided as is without express or implied warranty of any kind These notices must be retained in any copies of any part of this documentation and or software kkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkk Copyright C 1991 2 RSA Data Security Inc Created 1991 All rights reserved License to copy and use this software is granted provided that it is identified as the RSA Data Security Inc MD5 Message Digest Algorithm in all material mentioning or referencing this software or this function License is also granted to make and use derivative works provided that such works are identified as derived from the RSA Data Security Inc MD5 Message Digest Algorithm in all material mentioning or referencing the derived work RSA Data Security Inc makes no representations concerning either the merchantability of this software or the suitability of this software for any particular purpose It is provided as is without express or implied warranty of any kind These notices must be retained in any copies of any part of this documentation and or software Anybus Communicator for PROFINET Doc Rev 3 01 Doc ld SCM 1200 088
80. hield Anybus Communicator Device Anybus Communicator for PROFINET Doc Rev 3 01 Doc ld SCM 1200 088 Appendix B B Technical Specification B 1 Mechanical Properties Housing Plastic housing with snap on connection to DIN rail protection class P20 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 B 2 Electrical Characteristics Power Supply Power 24V 10 Power Consumption Maximum power consumption is 280mA on 24V Typically around 100mA B 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 PROFINET Doc Rev 3 01 Doc ld SCM 1200 088 Technical Specification 106 B 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 1996 10V m EN 61000 4 6 1996 10V m all ports EN 61000 4 2 1995 8kV Air Discharge 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 interfac
81. i eb eal aras 00 PS RE A A E II II O OREN aT Re E 100 Connector Pin Assignments PROPUNE I Connector tier net ias a eaanteys sided eatin austen wears eal 101 POW CORAL A AA State 101 PE COMME COL tala A AA A 102 SUD Meh VOLK terracota 102 CONTA DORA E NIE S AIET I O E A A E 103 aE UA O A E A A E A AAE AE E A E 103 Fozi na MA RI TO IIS RS A A OU AEE E E E 103 C onnen or T no TIDI TAE A ENEE tae ar esac te cake 103 Tona CO A A 104 LUPA Conero n RIA CO AW 0 RILI td ib 104 TS AAA NN 104 Technical Specification Mechanical Properties sueshadaniunde 105 Elecmical Chien SCs ti a RA AEN 105 Enyironmental CN ALACl eS CS the orden ir 105 Keosulatory COn pun A AA 106 Troubleshooting ASCII Table Copyright Notices Anybus Communicator for PROFINET Doc Rev 3 01 Doc Id SCM 1200 088 About This Document Preface For mote information documentation etc please visit the HMS website www anybus com Related Documents Document name Author ABC PRT 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 60 Updated information about the trigger byte 65 Updated information about the CRC algorithm 72 Updated frontpage information
82. ication in accordance with the module configuration Anybus Communicator for PROFINET Doc Rev 3 01 Doc Id SCM 1200 088 About the Anybus Communicator for PROFINET 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 color or higher Microsoft Windows 2000 XP Vista 7 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 start 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 Anybus Communicator for PROFINET Doc Rev 3 01 Doc Id SCM 1200 088 Chapter 2 2 Basic Operation 2 1 General The Anybus Communicator module is designed to exchange data between a serial subnetwork and a higher level network Unlike most other gateway devices of similar kind it does not have a fixed protocol for the subnetwork and can be configured to handle almost any form of serial communication The Anybus Communicator 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
83. l Q window e Exit Exit without saving Example Transaction Editor File Byte constant Word constant Data Checksum Byte constant Value Value Data location Data length Byte swap Error check type Error check start byte Value 0x02 0x0008 Ox0202 0x0008 No swapping 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 query 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 PROFINET Doc Rev 3 01 Doc ld SCM 1200 088 Chapter 13 13 Frame Objects 13 1 General Each transaction consists of Frame Objects which makes up the serial telegram frame Each Frame Ob ject specifies how 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 e 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 an
84. l Codes in Master Mode and DF1 Master Mode on page 99 Control Codes in Generic Data Mode on page 99 Note Internally this is treated as a Motorola format word 1 e MSB first If the higher level network uses a different byte order the upper and lower bytes will appear to be swapped 20 3 2 Control Codes in Master Mode and DF1 Master Mode This 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 20 3 3 Control Codes in Generic Data Mode No Control Codes are currently supported in this mode Anybus Communicator for PROFINET Doc Rev 3 01 Doc Id SCM 1200 088 Chapter 21 21 Advanced Fieldbus Configuration 21 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 configure 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
85. mand Editor on page 75 Anybus Communicator for PROFINET Doc Rev 3 01 SY Fieldbus ABC e Sub Network Sub Network Monitor Add Node Add Broadcaster Load Node Sub Network Status SN Fieldbus df ABC wi Sub Network Y Broadcaster Y ew Mode Doc Id SCM 1200 088 Chapter 12 12 Transactions 12 1 General As mentioned previously transactions are 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 Manager 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 query is issued by the gateway while responses are issued by the slaves on the subnetwork The Broadcaster can only send transactions e Generic Data Mode Transactions 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 79 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 Anybu
86. may be edited in the Navigation Parameter Section or using the Force Multiple Coils Transaction Editor Note however that certain frame objects may be locked for editing My Custom Command 1 AD My Custom Command 2 Anybus Communicator for PROFINET Doc Rev 3 01 Doc Id SCM 1200 088 14 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 75 Edit Command Edit the currently selected command using the Command Editor See also The Command Editor on page 75 Delete Command Commands 74 Ee Select Exit Cti Q Add Command Edit Command Delete Command Delete the currently selected command from the list Note that some commands are fixed and cannot be deleted 14 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 PROFINET Doc Rev 3 01 Add Command Edit Command Delet
87. min level users File Format The format of these files are as follows Usernamel Passwordl Username2 Password2 Username3 Password3 Note If no valid user accounts have been defined the Anybus Communicator will grant admin level access to all users In such case the FTP accepts any username password combination and the root directory will be Anybus Communicator for PROFINET Doc Rev 3 01 Doc Id SCM 1200 088 FTP Server 32 5 2 FTP Connection Example Windows Explorer The built in FTP client in Windows Explorer can easily be used to access the file system as follows 1 Open the Windows Explorer by right clicking on the Start button and selecting Explore 2 Inthe address field type FTP lt user gt lt password gt lt address gt Substitute lt address gt with the IP address of the Anybus Communicator Substitute lt user gt with the username Substitute lt password gt with the password 3 Press enter The Explorer will now attempt to connect to the module using the specified settings If successful the built in file system is displayed in the Explorer window File Edit View Favorites Tools Help Qy Back Y GQ 7 gt y Search Folders ja Address ftp user password lt address gt g Go Name Size T Date Modified File and Folder Tasks a JD Make a new folder Publish this folder to the Web tad Share this folder gt gt Other Places
88. n 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 PROFINET Doc Rev 3 01 Doc Id SCM 1200 088 15 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 Clear ine options for sub network Clear Update mode Cyclically 3 100 Update time 10ms 100 E Trigger Request Trigger byte address OUx05FF Renante 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 85 10 55 Config Line HQ Valid settings PLC
89. n page 86 ae e Add Command 7 This icon is used to add commands to the currently selected node ES y omman e Add Mailbox 7 Advanced functionality see Mailbox Editor on page 100 Add Mailbox e Add Node amp Add Broadcaster These icons are 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 87 Node Monitor e Add Transaction s p m an JE S 7 These icons are used to add transactions to the currently selected node rr Pre Transactions Transaction Anybus Communicator for PROFINET Doc Rev 3 01 Doc Id SCM 1200 088 Chapter 10 10 Basic Settings 10 1 Fieldbus Settings Select Fieldbus in the Navigation Section to gain access to the param Ae ABC eters described in this section KH Sub Network 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 module Fieldbus Type Configuration Alphabetic Categorized 7 E Ethernet TCP IP configuration The Anybus Configuration Manager supports a wide range of net Communicator IP address 19276801 p Default Gateway 0 0 0 0 working systems Make sure that this parameter is set to Profinet Subnet Mask 255 25
90. nager Anybus Communicator for PROFINET Doc Rev 3 01 Download Password 6 ms Name the Configuration Select a Name for the Confiquration My confiquration Upload Password 6 pel Doc ld SCM 1200 088 Navigating the Anybus Configuration Manager 52 Tools This menu features the following entries This entry selects the COM port used Port d for the configuration of the gateway Upload configuration from ABC a id Download configuration to ABC Upload the configuration from the Start Logging gateway to the Anybus Configuration Manager Options e Download configuration to ABC Download the current configuration into the gateway e Start Logging Start the Data Logger see Data Logger on page 91 Note that when the Data Logger is active this menu entry is changed to Stop Logging e Options This will bring out the following window Item Description Warning on Delete A confirmation dialog is displayed each ee time something is deleted eee Warning on unsaved A confirmation dialog is displayed when EET She eee egw atin Nears elec data closing the Anybus Configuration Man oO eee 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
91. nd 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 PROFINET Doc Rev 3 01 Doc Id SCM 1200 088 Commands 76 14 3 3 Pull down Menu File This menu features the following entries e Apply Changes Fie M Save changes and exit to the main window Apply Changes Exit Exit Ctr Q Exit without saving Column The functions in this menu alters the structure of the command e 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 PROFINET Doc Rev 3 01 Doc ld SCM 1200 088 Commands 77 14 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 c
92. nd to the subnetwork send Command Columns This menu specifies the number of columns in the Monitor Section Columns E Free e Free 8 Multiple The number of columns depends on the width of the window e 8 Multiple The number of columns will be fixed to 8 View This menu specifies the data representation in the Monitor Section Hex CA Display the data in hexadecimal format we Hex Decimal e Decimal Display the data in decimal format Anybus Communicator for PROFINET Doc Rev 3 01 Doc ld SCM 1200 088 Node Monitor 90 17 2 2 Toolbar Icons The toolbar features icons for the most commonly used functions e Start Node Stop Node OF These icons corresponds to the functions in the Node menu O See also Node on page 89 Start Stop e Select Command amp Send Command These icons corresponds to the functions in the Command menu eer E See also Command on page 89 Select Send Resume Refresh amp Stop Refresh 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 E pe 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 PROFINET Doc Rev 3 01 Doc Id SCM 1200 088 Chapter 18 18 Data Logger 18 1 Gener
93. ode available if you intend to configure an ABC module for DF 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 PROFINET Doc Rev 3 01 Doc ld SCM 1200 088 15 3 Subnetwork Parameters To gain access to the parameters described in this section select Subnet work in the Navigation Section Communication DF1 Protocol Mode 81 8 Fieldbus di ABC O al Sub Network These parameters specify the actual communication settings used for the subnetwork Parameter Description 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 maste
94. of the cable typically 100 120R A 4 4 Connector Pinout DB9F Pin Description RS232 RS422 RS485 1 5V Output 100mA max Y Y Y 2 RS232 Rx Y 3 RS232 Tx Y 4 reserved 5 female 1 9 Signal Ground Y Y Y 6 RS422 Rx Y 7 RS422 Rx Y 8 RS485 RS422 Tx Y Y 9 RS485 RS422 Tx Y Y housing Cable Shield Y Y Y 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 transceivers lt is therefore generally recommended to connect it only to Signal Ground if available of other nodes Anybus Communicator for PROFINET Doc Rev 3 01 Doc Id SCM 1200 088 Connector Pin Assignments 104 A 4 5 Typical Connection RS485 5V RS485 RS485 RS485 RS485 Signal Signal Ground Ground Cable Shield Anybus Communicator Node Node Node Node End Node A 4 6 Typical Connection RS422 4 Wire RS485 5V RS422 Rx gt RS422 Tx 11 I 1 I RS422 Rx La RS422 Tx I I 470R 1 1 RS422 Tx s RS422 Rx 120R RS422 Tx l RS422 Rx I l 470R 1 1 I Signal a Signal Ground Ground Cable o Shield Anybus Communicator Device Note Bias resistors are normally not needed on RS422 but may be required when using 4 wire R5485 A 4 7 Typical Connection RS232 RS232 Tx RS232 Rx I no I 1 I a RS232 Rx RS232 Tx I a i I Signal J Signal Ground Ground Cable S
95. onfiguration is adopted from the I O controller supervisor provided that the total I O sizes specified by the IO controller does not exceed the sizes specified in the Anybus Configuration Manager For information about how the IO and Record Data relates to the input and output data areas see Da ta Representation IO Data amp Record Data on page 23 2 4 3 GSDML File On PROFINET all devices are associated with a GSDML file The GSDML file is the equivalent of the PROFIBUS GSD file and is based on the EXtensible Markup Language XML This file holds information about the device in this case the Anybus Communicator its features and possible I O configurations The latest version of the GSDML file for the Anybus Communicator can be downloaded from the HMS website www anybus com Anybus Communicator for PROFINET Doc Rev 3 01 Doc Id SCM 1200 088 Basic Operation 23 2 4 4 Data Representation IO Data 8 Record Data As mentioned previously the actual I O configuration is determined by the IO Controller The modules are mapped to the input and output data areas in the order of their slot number Example In this example the I O Sizes for the ABC has been set to the following values IO Size In 256 bytes 0x0100 IO Size Out 400 bytes 0x0200 The following modules are specified in the IO Controller Slot Module Size Direction Notes 0 0 Device Access Point DAP 1 16 bytes Input
96. or 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 PROFINET Doc Rev 3 01 Doc Id SCM 1200 088 Control and Status Registers 99 20 3 Control Register Contents Control System to Gate way 20 3 1 General Information The Control Register is if 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 95 Status Register Contents Gateway to Control System on page 97 This bit controls data consistency see Data Consistency on page 96 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 Registers 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 Contro
97. out this mode see DF1 Protocol Mode on page 79 2 3 2 Protocol Building Blocks The following building blocks ate used in Anybus Configuration Manager to describe the subnetwork communication How these blocks apply to the three protocol modes will be described later in this doc ument e Node A node represents a single device on the subnetwork Each node can be associated with a number of transactions see below e Transaction A transaction represents a complete serial telegram and consists of a number of frame objects below Each transaction is associated with a set of parameters controlling how and when to use it on the subnetwork e 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 e 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 PROFINET Doc Rev 3 01 Doc Id SCM 1200 088 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 to issue responses
98. r 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 PROFINET Doc Rev 3 01 Doc Id SCM 1200 088 15 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 59 amp ABC Config Tool Untitled File Node 1 Tools View Help ABC DF 1 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 DF1 Protocol Mode 82 Fieldbus ABC pe S ubnetwork Ti Ej Node 2 Parameter Description Valid Settings Checksum Selects the type of c
99. ration regarding the network settings see below Which mode to use is determined by the TCP IP Settings parameter in Anybus Configuration Manag er see Fieldbus Settings on page 55 e TCP IP Settings Enabled When operating in this mode the contents of the system file ethcfg cfg will be ignored com pletely causing the following behavior DNS services will not be available Domain and Host name cannot be set E mail services will not be available Settings received from the network i e via HICP or DCP will be lost in the event of a power loss or reset e TCP IP Settings Disabled When operating in this mode the Anybus Communicator module will use the settings stored in the system file ethcfg cfe If this file is missing the module will attempt to retrieve its settings via DHCP or HICP for 30 seconds If no configuration has been received within this period the module will halt and indicate an error on its status LEDs DCP Discovery and Basic Configuration The Anybus Communicator fully supports the DCP protocol which allows an IO Controller Supervi sor to change the TCP IP settings during runtime DHCP BootP The Anybus Communicator can retrieve the TCP IP settings from a DHCP or BootP server If no DHCP server is found the module will fall back on its current settings 1 e the settings currently stored in ethcfg cfe If no current settings are available i e ethcfg cfe is missin
100. reate Text file Anybus Communicator for PROFINET Doc Rev 3 01 Doc Id SCM 1200 088 Data Logger 92 18 3 Configuration By default the log buffer can hold 512 bytes of data in each r a i Hms Options direction To specify a different size for the buffer select Options in the Tools menu Size ofloghuter it Oo aw Firmware Download A window with various settings will appear Select the ABC Peele 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 Gaerne Block Configuration Click Apply to validate the new settings Creates an error log file Create Error Log Click OK to exit Anybus Communicator for PROFINET Doc Rev 3 01 Doc ld SCM 1200 088 19 Configuration Wizards 19 1 General Chapter 19 When creating a new subnetwork configuration the Anybus Configuration Manager provides 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
101. rmware revision of the network interface Syntax lt exec cmd_argument DisplayFWVersion gt DisplayBLVersion This function returns the bootloader firmware revision of the network interface Syntax lt exec cmd_argument DisplayBLVersion gt DisplaylP This function returns the currently used IP address Syntax lt exec cmd_argument DisplayIP gt DisplaySubnet This function returns the currently used Subnet mask Syntax lt exec cmd_argument DisplaySubnet gt DisplayGateway This function returns the currently used Gateway address Syntax lt exec cmd_argument DisplayGateway gt Anybus Communicator for PROFINET Doc Rev 3 01 Doc Id SCM 1200 088 Server Side Include SSI 38 DisplayDNS1 This function returns the address of the primary DNS server Syntax lt exec cmd_argument DisplayDNS1 gt DisplayDNS2 This function returns the address of the secondary DNS server Syntax lt exec cmd_argument DisplayDNS2 gt DisplayHostName This function returns the hostname Syntax lt exec cmd_argument DisplayHostName gt DisplayDomainName This function returns the default domain name Syntax lt exec cmd_argument DisplayDomainName gt DisplayDhcpState This function returns whether DHCP BootP is enabled or disabled Syntax lt exec cmd_argument DisplayDhcpState
102. roduct 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 domesti
103. rom file or via upload from a Communicator module Dont show this Window again Doc Id SCM 1200 088 Configuration Wizards 94 19 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 subnetwork 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 wizard doesn t handle a particular Modbus command required by a device it is possible to specify this command manually as a transaction in the Anybus Configuration Manager Using this wizard involves the following steps Step 1 Communicator Type Wizard Modbus RTU Master Select Profinet IO gt Step 1 of 6 Select the fieldbus Click Next to continue Tip It is possible to return to a previous menu at any time without losing any set tings by clicking Previous Step 1a I O Sizes Sp
104. s Communicator for PROFINET Doc Rev 3 01 Doc Id SCM 1200 088 12 2 Adding amp Managing Transactions Transactions 61 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 87 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 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 node 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 PROFINET Doc Rev 3 01 38 Fieldbus A ABC 8 Sub Network TP YN Cut Copy Insert Delete Node Monitor Add Transaction Consume Add Transaction Produce Add Command Insert New Node Save Node Insert from Fil
105. s 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 PRT PROFINET IO Broadcaster A protocol specific node in the subnetwork scan that hold transactions destined to all nodes Command A protocol specific transaction Configuration List of configured nodes with transactions on the subnetwork Fieldbus The network to which the communicator is connected Fieldbus Control System Fieldbus master Frame Higher level series of bytes forming a complete telegram on the subnetwork Monitor A tool for debugging the ABC and the network connections Node A device in the configuration that defines the communication with a node on the subnetwork Scan list List of configured slaves with transactions on the subnetwork The network that logically is located on a subsidiary level with respect to the fieldbus and to did which the ABC acts as a gateway A generic building block that is used in the subnetwork scan list and defines the data that is Transaction sent and received on the subnetwork PROFINET device which acts as a client for several lO devices usually a PLC Comparable to IO Controller a PROFIBUS DP class 1 master PROFINET programming device with commissioning and diagnostic functions Comparable to a PROFIBUS DP class 2 master IO Device Field device assigned to an lO Controller In this c
106. s 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 0xOA 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 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
107. sion to unsigned char S char characters from the string are printed until a 0 is reached or until the number of characters indicated by the precision have been printed f float decimal notation of the form mmm ddd where the number of d s is specified by the preci sion The default precision is 6 a precision of 0 suppresses the decimal point e E float decimal notation of the form m dddddd e xx or m ddddddE xx where the number of d s specified by the precision The default precision is 6 a precision of O suppresses the decimal point g G float e or E is used if the exponent is less than 4 or greater than or equal to the precision oth erwise f is used Trailing Zeros and trailing decimal point are not printed no argument is converted print a Anybus Communicator for PROFINET Doc Rev 3 01 Doc Id SCM 1200 088 Server Side Include SSI 43 The arguments that can be passed to the SSI function printf are Argument Description InReadSByte offset Read a signed byte from position offset in the Input Data area InReadUByte offset Read an unsigned byte from position offset in the Input Datalnput Data area InReadSWord offset Read a signed word from position offset in the Input Data area InReadUWord offset Read an unsigned word from position offset in the Input Data area InReadSLong offset Read a signed longword from position offset in the Input Data area InRea
108. stants are handled differently depending on the direction of the transaction e Produce Quetry 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 PROFINET Doc Rev 3 01 Doc Id SCM 1200 088 Frame Objects 69 13 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 the specified boundaries 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
109. stem 26 3 2 File System Overview admin root user root ip_accs cfg ssi_str cfg http cfg protected ethcfg cfg pniocfg cfg sys_pswd cfg ORAM volatile optional pma cfg email_1 0 cfg NTE protected ad_pswd cfg EA email_1 cfg email_1 0 cfg 3 3 System Files The file system contains a set of files used for system configuration These files known as system files are regular ASCII files which can be altered using a standard text editor such as the Notepad in Micro soft Windows Note that some of these files may also be altered by the Anybus Communicator itself e g when using SSI see Server Side Include SSI on page 36 The format of the system files are based on the concept of keys where each key can be assigned a value see example below Example Key1 value of keyl Key2 value of key2 The exact format of each system file is described later in this document The contents of the above files can be redirected Example In this example the contents will be loaded from the file here cfe File path i put it over here cfg Note Any directory in the file system can be protected from web access by placing the file web_accs cfg in the directory see Authorization on page 34 Anybus Communicator for PROFINET Doc Rev 3 01 Doc Id SCM 1200 088 Chapter 4 4 Basic Network Configuration 4 1 General Information The Anybus Communicator offers two modes of ope
110. tains header information A Allow user to 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 PROFINET Doc Rev 3 01 Doc Id SCM 1200 088 A Connector Pin Assignments A 1 PROFINET Connector Ethernet Housing Cable Shield TD TD RD Termination Termination RD Termination CO NI DD oy Bl N Termination A 2 Power Connector Pin Description 1 24V DC 2 GND Notes e Use 60 75 or 75XC copper CU wire only e The terminal tightening torque must be between 5 7 lbs in 0 5 Anybus Communicator for PROFINET Doc Rev 3 01 Appendix A 0 8 Nm Doc Id SCM 1200 088 Connector Pin Assignments 102 A 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
111. tation Modbus TEP REST MAD iseten tiasa t e E EEEE R 24 oanpart e T A O TOTS A AA E A R uals 24 Chapter 3 File System Cenere O eer 25 ls o AA E A A EO EE 26 EE O E E EOS 26 Anybus Communicator for PROFINET Doc Rev 3 01 Doc ld SCM 1200 088 Chapter 4 Chapter 5 Chapter 6 Chapter 7 Chapter 8 Chapter 9 Chapter 10 Basic Network Configuration General tor RN E A A ou ecluniemuuineies Di Ptaemet CONmoutanOn Ple eC O Go sita 28 GO hectare Abate a eases a o a 28 PTO ETN TE Sets aia 29 BCAA a E A 29 Am bas Peonio FOP aion O 30 FTP Server GENEA ea iaa NN 31 FIP Connection Example Windows Explotacion 32 Web Server A e EES O RR 33 ANONA A E 34 Content Pes lt 35 Server Side Include SSI C E E A E E E A E O O E T 36 TAE ATE BELA Seance netstat E E A T Si Chains ss Lou lid laico ice 46 SILES INCA SAA AA AA 46 COROS LAUDO tr a asa 47 E mail Client E EEE SELE EIA ANEA aaa tetas Palette eae alc eB ote TOAN ace tants sre arte ett eek 48 a II ec 49 Navigating the Anybus Configuration Manager Dt a evens e a 50 ONC I ANC SIEA EIE RN aed ones Tia dhe ee E TESS 51 DI a el len ace oa o ts eet el 54 Basic Settings Pel bus o CTOS a in mt OTT Unt re BNE rer 55 Gia Bin es eke T i ek Ear e eA CO cee Pn Arenal Ce PR aa eA eae eee eae 56 SUDOR Pareto cee eee ee een Oe TO aldo 58 Anybus Communicator for PROFINET Doc Rev 3 01 Doc Id SCM 1200 088 Chapter 11 Nodes Ss E RN 59 Addis Mana GING NO des eiaa aa T
112. 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 A 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 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 e Cyclically The transaction is issued cyclically at the interval specified in the Update time parameter e 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 dat
113. the time that separates two messages in steps of 10us Anybus Communicator for PROFINET Doc Rev 3 01 Doc Id SCM 1200 088 11 Nodes 11 1 General Chapter 11 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 11 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 86 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 View diagnostic information about the subnetwork a This function is only available in Master Mode 11 3 Node Parameters 11 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 Com
114. tion Configuration HMS logo contents of config htm frame page form page form page store page configuration gif Configuration picture boarder bg gif picture Xboarder m bg gif picture index htm 1 Points to the contents of config htm eth_stat html cip_stat html ip_config shtm smtp_config shtm style css arrow_red gif Anybus Communicator for PROFINET Doc Rev 3 01 Configuration Configuration Configuration Configuration HMS logo Configuration frame page form page form page store page picture Doc Id SCM 1200 088 Web Server 34 6 2 Authorization Directories can be protected from web access by placing a file called web_accs cfe in the directory to protect This file shall contain a list of users that are allowed to access the directory and its subdirectories File Format Usernamel Passwordl Username2 Password2 List of approved users UsernameN PasswordN Optionally a login message can be specified by including the AuthName key AuthName This message will be displayed by the web message goes her browser upon accessing the protected directory The list of approved users can optionally be redirected to one or several other files Example In this example the list of approved users will be loaded from the files here cfg and too cfg File path i put it over here cfg i actually put some of it over here too cfg AuthName Yeah Whatsda passwoid Note t
115. ucts derived from this software without specific prior written permission THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS AS IS ANDANY EXPRESS OR IMPLIED WARRANTIES INCLUDING BUT NOT LIMITED TO THE IMPLIED WARRANTIES OF MERCHANT ABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED IN NO EVENT SHALL THE RE GENTS OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT INDIRECT INCIDENTAL SPECIAL EXEMPLARY OR CONSEQUENTIAL DAMAGES INCLUDING BUT NOT LIMITED TO PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES LOSS OF USE DATA OR PROFITS OR BUSINESS INTERRUPTION HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY WHETHER IN CONTRACT STRICT LIABILITY OR TORT INCLUDING NEGLIGENCE OR OTHERWISE ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE kkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkkk Copyright C 1990 2 RSA Data Security Inc All rights reserved License to copy and use this software is granted provided that it is identified as the RSA Data Security Inc MD4 Message Digest Algorithm in all material mentioning or referencing this software or this function License is also granted to make and use derivative works provided that such works are identified as derived from the RSA Data Security Inc MD4 Message Digest Algorithm in all material mentioning or referencing the derived work RSA Data Security Inc makes no representations concerning eit
116. ulator 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 PROFINET Doc Rev 3 01 Doc ld SCM 1200 088 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 Generic Data Mode and DF1 Master Mode Note that the protocol mode only specifies the basic communication model not the actual subnetwork protocol e Master Mode In this mode the module acts as a master on the subnetwork and the serial communication takes place in a query response fashion The nodes on the network are not permitted to issue messages unless they have been addressed by the module first For more information about this mode see Master Mode on page 20 e Generic Data Mode In this mode there is no master slave relationship between the subnetwork nodes and the mod ule any node on the subnetwork including the Anybus Communicator may spontaneously pro duce or consume messages For more information about this mode see Generic Data Mode on page 21 e DFI Master Mode In this mode the module acts as a master on the subnetwork using the DF1 protocol The serial communication takes place in a query response fashion For information ab
117. xxx___ Nodes listed here may access the FTP server Modbus TCP XXX XXX xxx xxx Nodes listed here may access the module via Modbus TCP A11 xxx xxx xxx xxx Fallback setting used by the module when one or several of the keys above are omitted Note may be used as a wildcard to select IP series Anybus Communicator for PROFINET Doc Rev 3 01 Doc Id SCM 1200 088 Basic Network Configuration 30 4 5 Anybus IPconfig HICP The Anybus Communicator supports the HICP protocol used by the Anybus IPconfig utility from HMS which can be downloaded free of charge from the HMS website This utility may be used to con figure the network settings of any Anybus product connected to the network Note that 1f successful this will replace the settings currently stored in the configuration file ethcfe cfg Upon starting the program the network y rrrrrr a is scanned for Anybus products The net Ethernet configuration IP address 10 10 12 246 DHCP work can be rescanned at any time by EE ce a Off Subnet mask 255 255 255 OQ clicking Scan In the list of detected de acen eS vices the Anybus Communicator will ap pimeyons NA pear as ABC PRT To alter its network settings double click on its entry in the list A window will appear containing the IP configuration and password settings Validate the new settings by clicking Set or click Can
118. y enables dynamic content to be used on web pages and in e mail messages SSI are special commands embedded in the source document When the Anybus Communicator en counters such a command it will execute it and replace it with the result when applicable Syntax The X s below represents a command opcode and parameters associated with the command lt exec cmd_argument XXXXXXXXXXXXXXXXXXXXXX gt Example The following example causes a web page to display the Ethernet Mac ID of the module lt HTML gt lt HEAD gt lt TITLE gt SSI Test lt TITLE gt lt HEAD gt lt BODY gt The Ethernet Mac ID of the ABC is lt exec cmd_argument DisplayMacID gt lt BODY gt lt HTML gt Resulting web page 01 File Edit View Favorites Tools Help J Back y GQ 7 Search Ki Favorites a Media lt lt Lig Address http 192 168 1 125 v E2 Go The Ethernet Mac ID of the ABC is 00 30 11 78 9A BC zl 4 43 My Computer Anybus Communicator for PROFINET Doc Rev 3 01 Doc Id SCM 1200 088 Server Side Include SSI 37 7 2 Functions DisplayMaciD This function returns the MAC ID in format Xx XX XX XX XX XX Syntax lt exec cmd_argument DisplayMacId gt DisplaySerial This function returns the serial number of the network interface Syntax lt exec cmd_argument DisplaySerial gt DisplayFWVersion This function returns the main fi
119. y is in bootloader mode and firmware must be restored in order for it to work properly Start up the Anybus Configuration Manager and connect to the Anybus Commu nicator Choose Tools Options ABC Click Factory Restore to restore firmware See Tools on page 52 Anybus Communicator for PROFINET Doc Rev 3 01 Doc Id SCM 1200 088 About the Anybus Communicator for PROFINET 14 1 4 Hardware Installation Perform the following steps when physically installing the Anybus Communicator module 1 Snap the module on to the DIN rail The DIN rail mechanism works as follows To snap the module on first press it downwards 1 to compress the spring in the DIN rail mechanism then push it against the DIN rail as to make it snap on 2 To snap the module 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 module to the PROFINET Ethernet network Connect the module to the serial subnetwork Connect the module to the PC via the configuration cable Connect the power cable and apply power ot A Start the Anybus Configuration Manager program on the PC The Anybus Configuration Manager software attempts to detect the serial port automatically If not successful select the correct port manually in the Port menu 7 Configure the Anybus Communicator using the Anybus Configuration Manager and download the configuration 8 Set up the PROFINET commun
120. y 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 PROFINET Doc Rev 3 01 e CRC 2 bytes CRC 16 with 0xA001 polynome Modbus RTU standard e 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 e 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 bytes Doc Id SCM 1200 088 Chapter 14 14 Commands This information is only valid for master mode and generic mode For DF1 master mode please refer to Services on page 82 14 1 General As mentioned previously commands ate actually predefined transactions that can be stored and reused Just like regular transactions commands consist of frame objects and are representations of the actual serial
121. 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 for PROFINET Doc Rev 3 01 Doc Id SCM 1200 088 Control and Status Registers 97 20 2 Status Register Contents Gateway to Control Sys tem 20 2 1 General Information The Status Register is if enabled located at 0x000 0x001 and constitutes a bit field as follows bit s

User Manual, Anybus Communicator for PROFINET IO

Contents

Download Pdf Manuals

Related Search

Related Contents