PNOZmultiProfibus.docx

1、PNOZmultiProfibusAPPLICATION NOTEPNOZmultiFieldbus Connection Issue No. : V1.0 Date of Issue : 08.08.2004 Editor : Bauer, Christ, LetscheProperty of PILZ GmbH & Co. KGFelix-Wankel-Strae 2D-73760 OstfildernGermanyFile: I:DatenAPPLIKATALLG_DOCApplication NotesPNOZmultiPNOZmulti_Fieldbus V2.docAll righ

2、ts to this manual are reserved by the publishers. Copies may be made for internalpurposes.While every effort has been made to ensure that the information in this manual is accurate, no responsibility can be accepted for errors or omissions contained within it.We reserve the right to amend any specif

3、ications without prior notice. We are grateful forany feedback on the contents of this manual.The names of products, goods and technologies used in this manual are the trademarks ofthe respective companies.CONTENTS1 HISTORY 32 Scope 33 Introduction 33.1 Structure of Bus Connection 33.1.1 User I/O Bi

4、t Data 43.1.2 List of Tables 83.2 Configuration of the Fieldbus Module 123.2.1 Fieldbus Configuration in Programming Tool 123.2.2 Version Management 123.2.3 Fieldbus Configuration File 123.2.4 Data Consistency 123.2.5 Data Consistency Protocol 133.3 Fieldbus Specific Features 143.3.1 Address and Bau

5、d Rate Setting 143.3.2 Configuration Files 144 Profibus DP (PNOZ mc3p) 154.1 Importing the GSD file 154.2 Configure the network 154.3 Application program 175 DeviceNet (PNOZ mc4p) 195.1 Sample I/O Communication with ControlLogix 195.1.1 Import EDS File 195.1.2 Configure Network 215.1.3 Application P

6、rogram 275.1.4 Test Data Exchange 325.2 Sample Messages with ControlLogix 395.2.1 Application program 395.2.2 Test Data Exchange 476 Interbus-S (PNOZ mc5p) 497 CC-Link 527.1 What is CC-Link 527.2 PNOZmulti Data in the CC-Link Registers 527.3 Sample with MELSEC System Q and GX IEC Developer 537.3.1 C

7、onfigure the Network 537.3.2 Application Program 547.3.3 Test Data Exchange 548 CANopen (PNOZ mc6p) 568.1 What is CANopen ? 568.1.1 CANopen Object Dictionary 578.2 Adressing the Pilz interface ? 578.3 Example With Hilscher CANopen pc master 588.4 Summary 631 HISTORYDatumVersions-Nr.Auslser (N./A.)be

8、tr. KapitelGrund der nderung13.09.20041.0Bauer/LetscheAll2 ScopeThis document describes the fieldbus communication of PNOZ multi. It is based on the developing documents. The document is subject to change without further notice. The document is not intended as a technical documentation for general u

9、se of the fieldbus modules for the PNOZmulti. It may not be distributed to customers without a special note to its scope.3 Introduction 3.1 Structure of Bus ConnectionThe PNOZmulti uses a common profile based on 20 bytes input and 20 bytes output using the process data channel for the following fiel

10、dbuses: Profibus-DP DeviceNet Interbus-S CC-Link (24 bytes)Note: CANopen is handled differentlyThe Fieldbus module of the PNOZ multi sends an “output data block” and receives an “input data block” . with each OS-cycle.Each data block consists of 20 bytes. The first three bytes are used for user bit

11、data, the next one is for status bits and 15 bytes are used for Table transfer and one byte as Control bits. 3.1.1 User I/O Bit DataA part of the data blocks will be processed in PNOZmulti as fieldbus flags. The first three bytes of the input data block and the first three bytes of the output data b

12、lock are user bit data.3.1.1.1 Assignment of the I/O Bit DataIn the first step, (V3.0) the user can only assign 24 flags of the PNOZmulti and internal flags to the output data block. The transfer of bits to the Multi into the input data block is realized in a later version. The user can choose the f

13、ieldbus bit in the same process using “set active”The user can assign each internal flag of PNOZmulti to the fieldbus bits.In the diagram “Profibus” is the name that the user has given to the fieldbus module during the configuration in the window “Select Base and Expansion Modules”.The “O” and “I” a

14、fter mean Output and Input. There are 24 bits as output.In the same way for “Set input and outputs active”, the fieldbus bits can have comments. It will be displayed like the others symbolic namesFor example: “Profibus O.2.Main E-Stop” ”Profibus” is the name of the module. ”O” means Output. ”2” mean

15、s the bit 2 of the module. ”Main E-Stop” is the symbolic name of the bit.There are some restrictions due to the safety to use the fieldbus input bits. The using of the input bits will be not realized in the first step (V3.0)The bits 0 to 23 are organized in the bytes 0 to 2 as shown: 3.1.2 List of TablesTable NoDescriptionNumber of Segments1Configuration62Error Stack128 (