C3 I20 T11 / T30 / T40 ObjektManager

Size: px

Start display at page:

Download "C3 I20 T11 / T30 / T40 ObjektManager"

Lenard Derrick Moody
6 years ago
Views:

1 Last update: Application example: C3 I20 T11 / T30 / T40 ObjektManager July 11 Seite 1 von 11

2 Copyright 2011 EME All Rights reserved. Windows NT, Windows 2000, Windows XP are trademarks of Microsoft Corporation. Germany: England: Italy: Electromechanical Automation Postfach: Robert-Bosch-Str. 22 D Offenburg Tel.: +49 (0) Fax: +49 (0) Internet: Parker Hannifin plc Electromechanical Automation Arena Business Centre Holy Rood Close Poole, Dorset BH17 7BA UK Tel.: +44 (0) Fax: +44 (0) Internet: Parker Hannifin S. p. A Electromechanical Automation Via Gounod 1 I Cinisello Balsamo (MI), Italy Tel.: +39 (0) Fax: +39 (0) sales.sbc@parker.com mailto:sales.sbc@parker.com Internet: EMN - Electromechanical Automation North America USA: Parker Hannifin Corporation Electromechanical Automation 5500 Business Park Drive Rohnert Park, CA Phone #: (800) FAX #: (707) emn_support@parker.com mailto: emn_support@parker.com Internet: Seite 2 von 11

3 1 introduction Product liability Nonwarranty clause Product monitoring liability Right to make changes Warranty Disclaimer Product monitoring liability Limitation of Liability Copyright Device assignment This manual applies to the following devices: With the supplement: and the Master plc: 6 2 purpose of the Block overview restrictions and application 6 3 adjustment Compax3 Configuration Compax3 Hardware SIMATIC - HW Config Application interface of "C3ObjektManager" Schematic drawing for in- and output Declaration of In- and Output sequence of process data settings for external Master 9 4 Application example Overview of the connection: cyclic channel (PZD) Acyclic channel (PKW) sequence 10 Seite 3 von 11

4 1 introduction 1.1 Product liability Nonwarranty clause Parker Hannifin - Automation Group - does not give any guarantee that the modules for SIMATIC S7 at hand will function properly under all conditions. From today's point of view there is generally no Software that will work properly under all conditions and requirements. The manufacturer therefore shall not be liable for direct and indirect damages of all kinds caused by the use of the software modules, even if the modules are used in accordance with the description in the manual at hand Product monitoring liability Parker Hannifin - Automation Group - try, within the scope of the product monitoring liability, to identify and describe dangers arising from the use of our software modules. Due to the complexity and our limited insight into the plants of the end customers, where also products of other manufacturers are integrated, we can, however, not identify all possible dangers. Furthermore, not all properties of the software modules are described in this manual Right to make changes Parker Hannifin - Automation Group - claims the right to update the manual and the software modules at any time without advance notice. Software modules may also be blocked without advance notice if dangers are detected, that endanger the proper functioning of the modules. We are not liable to eliminate errors immediately or provide new functions on customer's request Warranty Disclaimer While efforts were made to verify the accuracy of the information contained in this documentation, Parker expressly disclaims all warranties with regard to this application note, including, but not limited to, the implied warranties of merchantability and fitness of a particular purpose. Parker does not warrant, guarantee, or make any representation regarding the use or the results of the use of this application note in terms of correctness, accuracy, or reliability. The contents of this application note are subject to change without notice. Parker will publish updates and revisions of this document as needed. The documents supersede all previous versions Product monitoring liability Parker Hannifin - Automation Group - try, within the scope of the product monitoring liability, to identify and describe dangers arising from the use of our software modules. Due to the complexity and our limited insight into the plants of the end customers, where also products of other manufacturers are integrated, we can, however, not identify all possible dangers. Furthermore, not all properties of the software modules are described in this manual. Seite 4 von 11

5 1.1.6 Limitation of Liability You agree that Parker shall not be liable to you under this agreement for any damages, including without limitation any lost profits, or any consequential, incidental, or punitive damages arising out of the use or inability to use this application note and related documents, or for any claim by another party. You agree and hold Parker harmless for all claims and damages from any third party as a result of their use or inability to use any product that you develop based on this application note and the products and/or services documented herein Copyright This manual and the accompanying software modules contain information which is a spiritual property of the author. The authorised user commits to use this information exclusively for the operation with C3 positioning controller and their integration. The duplication and disclosure of the documentation or from extracts needs to be permitted separately. Duplication of the software modules is permitted for the purposes of a data protection. 1.2 Device assignment This manual applies to the following devices: Compax3H050V4 + Supplement Compax3H090V4 + Supplement Compax3H090V4 + Supplement Compax3H125V4 + Supplement Compax3H155V4 + Supplement Compax3M050D6 + Supplement Compax3M100D6 + Supplement Compax3M150D6 + Supplement Compax3M300D6 + Supplement Compax3S025V2 + Supplement Compax3S063V2 + Supplement Compax3S100V2 + Supplement Compax3S150V2 + Supplement Compax3S015V4 + Supplement Compax3S038V4 + Supplement Compax3S075V4 + Supplement Compax3S150V4 + Supplement Compax3S300V4 + Supplement With the supplement: F10 (Resolver) F11 (SinCos ) F12 (linear and rotary direct drives) I20 T11 T30 Seite 5 von 11

6 T and the Master plc: SIMATIC S7-300 with integrated PROFIBUS DP Master (e. g. CPU315-2DP) 2 purpose of the Block 2.1 overview Absolute Symbol Comment Vers Date Device Application FB41 C3ObjectManager C3 I20 T11 / T30 / T40 Manager for reading and writing objects V :44:16 PM C3 I20 T11 / T30 / T40 Objects read / write 2.2 restrictions and application The block is for backup and restore of the object list of the C3 in the S7. In the object list are all parameters and actual data included. If the areas PLC - programme and CAM - data (only T40) are also saved: a complete backup and restore is possible! This makes sense by exchange (defect) devices or serial set-ups. However, this is called also: The same variation of the C3 as well as the same Firmware state must be used with the "backup" and "Restore". The FB41 uses PKW-interface, is suitable therefore for all PPO types with PKW. Because other FBs use as well PKW interface: this has the consequence: It may communicate in each case only one FB via this interface! The FB41 may be only activated with disabled drive. 3 adjustment 3.1 Compax3 Configuration With C3ServoManager few following adjustments: At folder: \\ Communication \ PROFIBUS DP - node settings [PLC -> Compax3] The input tags are up to the user. [Compax3 -> PLC] The output tags are up to the user. [Operation Mode Settings] Seite 6 von 11

$At folder: \\ Communication \ scaling factors Y2/Y4 Scaling factors (only T30 / T40) are up to the user. 3.$

7 Acyclic process data channel / Parameter channel Select with "PKW" Error response on fieldbus failure is up to user. At folder: \\ Communication \ scaling factors Y2/Y4 Scaling factors (only T30 / T40) are up to the user. 3.2 Compax3 Hardware DIP-Switch: Bus address Bus plug: ``ON / OFF`` Bus termination resistance SIMATIC - HW Config Correlated to PPO-Type (see pic 1 communication - PROFIBUS DP node settings - shown in C3-Manager wizard) use the type at SIMATIC - HW Config pic 1 SIMATIC - HW Config Edit the Start address of PKW (here 256) in Instance Variable <nladdr> (DB41.DBW10). 3.4 Application interface of "C3ObjektManager" Schematic drawing for in- and output DB41 Seite 7 von 11

8 EN ENO DBX0.0 bexecute bcommerr DBX8.0 DBX0.1 bdirection bdbcopyramerr DBX8.1 DBW2 idbnummc bdbcreatemcerr DBX8.2 DBW4 idbnumcopyram bdbreadmcerr DBX8.3 DBX6.0 bexdatatransfer btranserr DBX8.4 bdone DBX8.5 babborted DBX8.6 DBW12 nladdr bbusy DBX8.7 DBX12.0 Word 4 stc3pkwindint.npke stc3pkwoutdint.npke DBX20.0 Word Declaration of In- and Output Parameter Declaration Type Description bexecute IN BOOL Start transfer with positive flank, must True during the whole transfer (put back with bdone =1) bdirection IN BOOL =0 Upload, =1 Download idbnummc IN INT Upload: the first free DB number in the loading memory, all together are required at present 6 DBs to save the object list. Download: the first DBnumber in the loading memory with object list (from Upload). idbnumcopyram IN INT Number of the DB to copy (8,000 bytes) needs to be put in from the user like the example! bexdatatransfer IN BOOL =0 integrated PROFIBUS DP interface (communication with SFC14 / SFC15) =1 external PROFIBUS DP interface (communication with FC1 / FC2) bcommerr OUT BOOL =1 communication error(from SFC14 / SFC15) bdbcopyramerr OUT BOOL DB for copying not available or too small (<8,000 bytes), error message SFC24 bdbcreatemcerr bdbcreatemcerr OUT BOOL DB cannot be created in the loading buffer, error message SFC82, (only Upload) bdbreadmcerr OUT BOOL DB cannot be read from the loading buffer, error message SFC83 (only Download) btranserr OUT BOOL Format command error when transmitting to C3 bdone OUT BOOL the transmission is finished (only when bexecute=1) babborted OUT BOOL transmission was in progress during bexecute was reseted bbusy OUT BOOL transmission in progress nladdr STATIC WORD = 0100hex (=256dez) Start address C3-Slave at HW Config, necessary with <bexdatatransfer> = 0 StC3PKWInDint.nPKE STATIC Word 4 Local input area for external CP StC3PKWOutDint.nPKE STATIC Word 4 Local output area for external CP sequence of process data setting of inputs of the block - <nladdr> (Parameter from HW Config) - <bdirection> (Upload or Download) - <idbnummc> (pointer to first Data block: this and 5 following DBs are generated with Upload; at Download this blocks need to exist) Seite 8 von 11

9 - <idbnumcopyram> (pointer to Data block: No. of DB this needs to exits in the PLC) - <bexecute> set - <bdone> wait for TRUE settings for external Master the function block is only possible with S7 plc with integrated PROFIBUS DP Master: Without the block is not suitable. If this interface is used for another purpose and the connection to c3 should be realised with an external communication processor (cp342-5) the function block is possible to be used with following settings: For running the CP there are to functions: FC1 / FC2 (DP_SEND / DP_RECV, out of SIMATIC Standard library). Put at DP_SEND the global output t area, and at DP_RECV the global input area. attention! These global areas included the data's of all bus slaves. The local field of c3 must be transferred to the field at DB41 (e.g. via SFC20 BLKMOV). The local input and output field could be identified with SIMATIC - HW Config. Correlated to PPO-Type (see pic 1 communication - PROFIBUS DP node settings - is shown in C3-Manager wizard) use the type at SIMATIC - HW Config. 4 Application example 4.1 Overview of the connection: Connection between one plc SIMATIC S7 300 as PROFIBUS DP Master and one drive C3 I20 T30 as PROFIBUS DP Slave. S7 < = PKW = > (8 Byte) < = PZD = > (14 Byte) C3 4.2 cyclic channel (PZD) The in- and output parameters are not used in this application. It is. Up to the user to fill in the parameters he needs. This project only uses the PKW channel. Seite 9 von 11

10 4.3 Acyclic channel (PKW) Via the 8 Byte PKW interface are all object of c3 read and saved in the flash of the s7, respectively read from s7 flash and transferred to the C3. so you ve the possibility to put the complete configuration from one drive to another. S7 = > C3 In There s no validation of data before transferring from s7 flash to c3. so it is up to the user to make sure that the parameters are correct interpreted: the source and destination must be the same type of drive: (equal power stage, equal motor etc.)! sequence 1. singe settings at the function block: - DBW12 <nladdr> setting of the start address from SIMATIC hardware configuration. (first analogue address of PKW) - DBW2 <idbnummc> from the function block are automatically data blocks produced from this address: (here 202) - DBW4 <idbnumcopyram> DB No. Of user DBs to save uploaded data in CPU (RAM) - DBX6.0 <bexdatatransfer> only for CP342-5 activate 2. Activate of command Backup - DBX 0.1 <bdirection> select false for read - DBX 0.0 <bexecute> select true for start - DBX 8.5 <bdone> wait until this is true. (it depends on c3 firmware version the bus frequency and the s7 CPU how much time is needed: e.g. few minutes). 3. Activate of command Restore - DBX 0.1 <bdirection> select true for write - DBX 0.0 <bexecute> select true for start - DBX 8.5 <bdone> Seite 10 von 11

11 wait until this is true. (it depends on c3 firmware version the bus frequency and the s7 CPU how much time is needed: e.g. few minutes). Seite 11 von 11

C3 I20 I32 T11 ControlManager FB45

CONTROL TECHNOLOGY FROM PARKER C3 I20 I32 T11 ControlManager FB45 A1039 Version: 39 Warranty Disclaimer While efforts were made to verify the accuracy of the information contained in this documentation,