AUTOMATION TECHNICAL SERVICES

Transcription

1 AUTOMATION TECHNICAL SERVICES APPLICATION NOTES Topic: Using Structures as Input Variables Date: August 26, 1998 APPnote: 208 i

2 PREFACE Application notes are intended to explain the use and/or configuration of subtle or complex functionality related to the Siemens Energy and Automation products manufactured in Johnson City, TN. Typical functions described in application notes are either not covered, or are only superficially covered in currently available end user documentation. The information in this document has been carefully checked and is believed to be entirely reliable. However, no responsibility is assumed for inaccuracies. Furthermore, Siemens Energy and Automation, Inc. reserves the right to make changes to any products herein to improve reliability, function, or design. Siemens Energy and Automation does not assume any liability arising out of the application or use of any product or circuit described herein; neither does it convey any license under its patent rights or the rights of others. Further information is available from the SE&A System Product Support Group in Johnson City ( ). PCS and APT are registered trademarks of Siemens Energy & Automation, Inc. All other trademarks are the property of their respective owners. ii

3 CONTENTS USING STRUCTURES AS INPUT VARIABLES 1 Symbol 1 Address 1 Data Type 1 Comment 1 Block: FB110 3 iii

4 Using Structures as Input Variables One way to use several input variables in a program is to use structures. To do this, make a UDT (User Defined Table) with the data to be used in the program. The first line in the UDT will be the name of the structure with type STRUCT. The next lines are the variables to pass to different DB s to be used in the program. After saving the UDT, make an Instance DB referencing the UDT. In a FB or FC made a local declaration Structure that matches the Instance DB and what else is to be passed when The Function is called. Open up the Symbol Editor and insert a symbolic name for the Instance DB to the UDT and the other parts of the program you require. Save the table and open up Container to Call the FB or FC that uses a structure for the input. When you insert the structure, it must be done symbolically not coded to the address. A programming example is included on the following pages. Symbol Address Data Type Comment Alarms UDT 100 UDT 100 User Defined Table for Alarms Sequencer1 FB 110 FB 110 FB to handle alarms Alarms 1 DB 100 DB 100 Instance DB to UDT100 Input 1 I 0.0 BOOL Alarm Bit Output 1 Q 0.0 BOOL Alarm Output OB1 - <Offline> DT# :29: DT# :33: Length (Block / MC7 code / Data) : Address Decl. Name Type Initial Value Comment 0.0 Temp OB1_EV_CLASS BYTE Bits (coming event), Bits (event class 1) 1.0 temp OB1_SCAN_1 BYTE 1 (Cold restart scan 1 of OB 1), 3 (Scan 2-n of OB 1) 2.0 temp OB1_PRIORITY BYTE 1 (Priority of 1 is lowest) 3.0 temp OB1_OB NUMBR BYTE 1(Organization block 1, OB1) 4.0 temp OB1_RESERVED 1 BYTE Reserved for system 5.0 temp OB1_RESERVED BYTE Reserved for system 6.0 temp OB1_PREV_CYCLE INT Cycle time of previous OB1 scan (milliseconds) 8.0 temp OB1_MIN_CYCLE INT Minimum cycle time of OB1 (milliseconds) 10.0 temp OB1_MAX_CYCLE INT Maximum cycle time of OB1 (milliseconds) 12.0 temp OB1_DATE_TIME DATE AND TIME Date and time OB1 started Block: OB1 1

5 Network: 1 When using a Structure as an input, you must use symbolic addressing for that input CALL Sequencerl, DB110 FB110 --FB to handle alarms Alarm := Input 1 I0.0 --Alarm Bit PB := Alarms_1.Alarms DB100 --Instance DB to UDT100 Alarmlgt := Output 1 Q0.0 --Alarm Output UDT100 - <Offline> DT# :37: DT# :13: Length (Block / MC7 code / Data) : Address Name Type Initial Value Comment 0.0 STRUCT +0.0 Alarms STRUCT +0.0 Ack BOOL FALSE +0.1 Reset BOOL FALSE +0.2 Foutrst BOOL FALSE +0.3 LT BOOL FALSE DB100 - <Offline> Alarms DT# :14: DT# :13: Length (Block / MC7 code / Data) : Address Name Type Initial Value Comment 0.0 STRUCT +0.0 Alarms STRUCT +0.0 Ack BOOL FALSE +0.1 Reset BOOL FALSE +0.2 Foutrst BOOL FALSE +0.3 LT BOOL FALSE FB110 - <Offline> Alarm Sequencer 1 FB to handle alarms 2

6 Author: Version: DT# :58: DT# :58: Length (Block / MC7 code / Data) : Address Decl. Name Type Initial Value Comment 0.0 in Alarm BOOL FALSE 2.0 in PB STRUCT +0.0 in Ack BOOL FALSE +0.1 in Reset BOOL FALSE +0.2 in Foutrst BOOL FALSE +0.3 in LT BOOL FALSE =2.0 in END_STRUCT 4.0 out Alarmlgt BOOL FALSE in_out 6.0 stat AlarmOn BOOL FALSE 6.1 stat AlarmOff BOOL FALSE 6.2 stat AlarmFF BOOL FALSE 6.3 stat AlarmSF BOOL FALSE 6.4 stat FirstOut BOOL FALSE 6.5 stat Horn BOOL FALSE temp Block: FB110 Network: 1 #Alarm #AlarmOn #AlarmFF (P) (S) #Horn (S) Network: 2 #Alarm #AlarmOff #AlarmSF (N) (S) Network: 3 #PB.Ack #Horn (R) Network: 4 3

7 #PB.Reset #AlarmFF (R) #AlarmSF (R) Network: 5 DB200.DBX0 #AlarmFF.0 #AlarmLgt ( ) DB200.DBX0 #AlarmSF.1 #Alarm #AlarmSF #AlarmFF #PB.LT DB110 - <Offline> Alarm Sequencer 1a Instance DB to FB110 DT# :40: DT# :58: Length (Block / MC7 code / Data) : Address Decl. Name Type Initial Value Comment 0.0 in Alarm BOOL FALSE 2.0 in PB STRUCT +0.0 in Ack BOOL FALSE +0.1 in Reset BOOL FALSE +0.2 in Foutrst BOOL FALSE +0.3 in LT BOOL FALSE =2.0 in END_STRUCT 4.0 out Alarmlgt BOOL FALSE 6.0 stat AlarmOn BOOL FALSE 6.1 stat AlarmOff BOOL FALSE 6.2 stat AlarmFF BOOL FALSE 6.3 stat AlarmSF BOOL FALSE 6.4 stat FirstOut BOOL FALSE 6.5 stat Horn BOOL FALSE 4