Installation Manual. PLCSQL link

Transcription

1 Installation Manual PLCSQL link SQL Client in a Siemens S7 PLC Revision date: Revised by: Anders Jorsal, Automatic Syd A/S Version: 1.01

2 Contents INTRODUCTION 3 SOFTWARE REQUIREMENTS 4 SETTING UP PLCSQL LINK 5 COLLECT PARAMETERS 13 LOG VALUES 15 SQL CONTROLLER 17 CHANGE LOG DATA ARRAY LENGTH 20 Page 2 of 21

3 Introduction You can operate the PLCSQL link, with different databases. But in order to get it to work, it is important to setup the Database, to fit with the design for PLCSQL link. Have you chosen to operate the PLCSQL link, together with Microsoft SQL server? You also need to follow tutorial MS SQL Installation Manual. Have you chosen to operate the PLCSQL link, together with My SQL server? You also need to follow tutorial MY SQL Installation Manual. Page 3 of 21

4 Software requirements This example project is based on following software tools: PLC Program: HMI: Simatic Step 7 V5.5 +SP2 Simatic WinCC Flexible 2008 SP3 Page 4 of 21

5 Setting up PLCSQL Link This chapter takes you through, the process of creating your own PLC station. And interface for setting up PLC link to connect with the SQL database. Start by retrieving the delivered Step 7 Example project S7-PLCSQL_v2.zip. Here you ll find 2 PLC projects, The program of these two stations are identical, and can be used with f.eks. ET200S, S7-300, S7-400 or RTX soft PLC. Create your own station, with the respecting PLC you are going to work with, you might want to create it in a separate project. Set up the hardware configuration, Set IP address for the Ethernet port. Compile it, and download the configuration to the PLC. Page 5 of 21

6 Copy the whole program folder, from one of the example programs. And replace the program folder in your new station. Download the blocks to PLC without System data. Page 6 of 21

7 Setup of the PLC is done through the HMI interface, for this we have created 2 example panels. That can help you getting started. HMI Large: Is suitable for using in big screen panels or Runtime applications. KTP600: Is designed for small screen panels, with smaller layout. The pages from these examples can freely. be copied into your own user panel. This way, the setup interface for PLCSQL Link, has been created for you. In this case I choose to run the application HMI Large, in order to setup the PLCSQL Link. Open Netpro to setup the IP address for the HMI, to connect the same net as the PLC. Page 7 of 21

8 Open the application HMI Large with WinCC Flexible. In here you ll need to correct, the active connection for the tags, by selecting Your PLC under Partner. After this click Start Runtime System. You can now run the application in demo mode. Page 8 of 21

9 In Runtime You can access the SQL Setup page by pressing F11. Here you need to setup the PLCSQL Link to match the Configured SQL database. CPU Serial number: Memory Card serial number: SQL client license key: By clicking Read, the CPUs serial number will be read out. By clicking read, the MMCs serial number will be read out. By informing Automatic Syd, one of the above mentioned serial numbers. By Mailing Finn C. Nissen: or tlf A unique License key is being generated, for you to type in. This License key is pared to the given serial number, and cannot be used on another device. Page 9 of 21

10 Integrated PN Controller: DeviceID PN Controller: Are you using a on-board PN port, click Yes. Are you using external CP cards for S7-300 and S7-400, that supports AG_SEND / AG_RECIEVE, click No Decide which group of Communication processor your PLC uses: B#16#00: CP 443-1EX4x (with S7-400, however, only with connection_type = B#16#12), won't work with SQL B#16#01: IE interface in interface slot 1 (IF1) with WinAC RTX (TCP only) or IM151 PN B#16#02: Integrated IE interface with CPUs PN/DP and PN/DP B#16#03: Integrated IE interface on the CPU PN/DP B#16#05: Integrated IE interface with CPUs PN/DP, PN/DP and 416-3F PN/DP B#16#06: IE interface in interface slot 2 (IF2) with WinAC RTX (TCP only) B#16#0B. IE interface in interface slot 3 (IF3) with WinAC RTX (TCP only) B#16#0F: IE interface in interface slot 4 (IF4) with WinAC RTX (TCP only) Hostname: SQL Username: SQL Password: SQL Database: Server type: SQL Server IP: Write the name of your machine. Write the username created in the SQL database. Write the Password for the Username. Write name of the generated SQL Database (PLCSQL). You can work with 2 different Databases: MS SQL (this tutorial), og MySQL. Write IP Address of the SQL server. SQL Server port: Write Time before timeout: Maximum retries: ParamID1 5: Write maximum time before timeout. Number of retries allowed for the system. Is the Parameter ID numbers you want to include, to filter the SQL database. in order to find the right request data. You can choose to enter them as fixed Values on the setup screen, or dynamic by the user program. ParamValue 1 5: Is the values you want to search for. Page 10 of 21

11 You can choose to enter them as fixed Values on the setup screen, or dynamic by the user program. Query 1 (Init): Query 2 (Request data): Query 3 (Log data): Query for initialization of connection to SQL. Query for receiving data from SQL. Query for logging data to SQL. NOTE: NOTE: If you are using My SQL, the expression EXEC must be replaced with CALL. After entering the communication setup, you need to click Restart SQL Client, for the changes to take effect. Page 11 of 21

12 Access the page SQL Status by pressing F10. On this page status of the connection is displayed, if Controller Step Nr. Indicates 150, the connection was established successfully. The process can be reset, in order to re-initialize the connection. For detailed information, a number of information s are listed. TCP Network communication: SQL Query: Query Length: Status of the last query executed. Displays the actual Query string being Send to SQL. Displays length of the generated Query. Updated test parameters from SQL: Displays the last updated parameters, Send from SQL. Values to log from PLC: Displays te values being logged from the PLC. Page 12 of 21

13 Collect Parameters For collecting values / parameters from SQL, You can link or move the specific parameter numbers out in the user program, sorted to fit your needs. This is done in FC 157 MoveTestValues, where the values are pinned out from DB147 SQL_TestParm. It is also possible to see if the specific parameter has been updated in this particular recipe, by using the bit SQL_TestParm.UpdatedParameters[ ], according to the parameter number. NOTE: Following parameters are reserved for system information: 10001: SetCount 15001: SetID 30001: DateTimeStamp. Page 13 of 21

14 Page 14 of 21

15 Log values For logging values to SQL, You can link or move the specific parameter numbers from the user program, and into the structured DB148 SQL_LogParm. This is done in FC 158 MoveLogValues For this particular value to be logged, you need to set the according bit SQL_LogParm.UpdatedParameters[ ] to true, while the log trigger is activated. In this way you can in an flexible way, define what to log, and when. NOTE: Following parameters are reserved for system information: 10001: SetCount 15001: SetID 30001: DateTimeStamp. Page 15 of 21

16 Page 16 of 21

17 SQL Controller To set up the triggers for executing the querys from the PLC. You need to edit FB140 SQL_Call. If you choose to move the program blocks, in order to fit into your user program. You also need to change the DB pointers on the SQL_Controller, to the new range. Page 17 of 21

18 To trig a log query, you can replace the OP_db. LogTrigger with your user defined trigger bit. To get new parameters from SQL. You need to define the recipe name, for the dataset, GetData query should refer to. In SQL. Replace OP_db.NewReceiptName, with your user defined string. Page 18 of 21

19 To trig a GetData query, you can replace the OP_db. GetData with your user defined trigger bit. Besides the 3 previously mentioned Function blocks: FC 157 MoveTestValues FC 158 MoveLogValues FB140 SQL_Call. You do not have to edit the other blocks, they are predefined from Automatic Syd. Page 19 of 21

20 Change log data array length The amount of data can be optimized, to fit the needs for your application. This example project is preconfigured to a limited range, in order to reduce unnecessary space obtained in the PLC. But can be expanded according to your needs. For setting up desired length of address arrays, you need to adjust two things. First open UDT146 SQL_DataTypes, where you can adjust the number of parameters assigned, in each datatype. Note: It is important that you only adjust the last number in the array, and that it doesn t exceed the start number of the next array. This means that you Maximum can assign up to: Real: Integer: Double integer: Bool: String: Updated values: parameters parameters parameters parameters 999 parameters Must be able to contain the maximum number of data, you need to handle in one query. Updated parameters: Contains a bit for each parameter, therefore range must cover the maximum number for paramstring. Page 20 of 21

21 After editing these array lengths, the whole project needs to be compiled and downloaded. In DB142 SQL_Setup, Max and Min ranges for each data type must match the ranges edited in UDT146 SQL_DataTypes. Page 21 of 21