OPERATOR INTERFACE PRODUCTS APPLICATION NOTE

Transcription

1 Page: 1 of 26 Table of Contents OVERVIEW...2 REQUIREMENTS...3 THEORY OF OPERATION...4 GP-PRO/PBIII C-PACKAGE-03 SETUP...7 DATABASE SETUP...8 Creating a Simple Target Database...8 Configuring Windows DSN(ODBC)...10 Creating a Pointer File...13 PRO-SERVER SETUP...17 Adding DSN Capability to Pro-Server Versions earlier than Adding Nodes to the Network Project...18 Register symbol for trigger bit...20 Configuring the Upload to the Database Action...22 Configuring a Provider Sheet...24 Transferring the Network Project to the GP/GLC/FG...26

2 Page: 2 of 26 Overview Pro-Server is capable of taking data from GPs, GLCs, Factory Gateways or other sources and writing this data to a database. By default Pro-Server is only able to write to SQL or Oracle database through their respective servers. Pro-Server is also able to write to access databases however without the same flexibility as with the action associated with SQL or Oracle. This application note describes how to use the Windows DSN (ODBC) system to allow Pro-server to write to any database for which Windows NT, 2000 or XP has a driver installed. Attached with this application note are examples of an access database, a pointer file, GP-Pro project and a Pro-Server Network Project file. This application note will describe step-by-step how to create these files. We will learn how to move a word value to a specified database, table and field creating a new record each time we trigger an Upload to the Database action. Upload from the Database action uses the exact same setup except that we are retrieving data from the database and writing to the GP/GLC/FG. NOTE: This application note will discuss how to configure Pro-Server to use DSN connectivity which only supports the Microsoft Access driver. Xycom Automation and Pro-Face may not provide support and is not responsible should any problems arise with hardware or software related to using DSN(ODBC) connectivity with any other driver.

3 Page: 3 of 26 Requirements For this application note you will require the following: GP-Pro/PBIII C-Package-03 (7.02) or later Pro-Server 4.1 or later MS Access 97 or later Windows NT, Windows 2000, or Windows XP Attached with this application note are the following files for demonstration/reference purposes: Dbtest.prw -- GP-Pro/PBIII C-Package-03 project example DBtest.npj -- Pro-Server Network Project example Db1.mdb -- Access Database example Pointer.mdb Pointer file example (Access) NOTE: This demonstration files were created for a GLC2300 however the project can be changed work with any GP or GLC with an Ethernet port by changing the model # in GP-Pro.

4 Page: 4 of 26 Theory of Operation Shown in Figure 1 is the basic setup of a various GPs and/or GLCs connected to a PC running Pro-Server over Ethernet. In this case the database we would want to write to would be stored on the same PC that is running Pro-Server. This setup, while ideal, is not necessarily required. The database could be located on another PC as shown in Figure 2. GP/GLC GP/GLC GP/GLC GP/GLC Ethernet PC running Pro-Server Database stored locally Figure 1 - Basic setup

5 Page: 5 of 26 GP/GLC GP/GLC GP/GLC GP/GLC Ethernet PC running Pro-Server PC with Database Figure 2 - Remote PC contains database that Pro-Server will write to. Before setting up the software to write to a database it may be worth while to understand the chain of events which will occur when we trigger a logging action. A sample of the basic logical operation process is shown in Figure 3. For the purpose of this application note we will set a trigger bit, LS009900, high. Pro- Server will see that bit go high and run a Provider sheet. The Provider sheet will fire the Pre-defined action for logging to the database. According to the action/pointer file, the value in LS0100 will be written to the database in a location specified in the pointer file.

6 Page: 6 of 26 Check again based on Interval in Provider Sheet Pro-Server Provider Sheet Has the Trigger bit, LS009900, been set in the GP/GLC/FG? No Yes Pro-Server Provider Sheet Download to Database Action is called Pro-Server Download to Database Action Pointer file is Opened to determine data to read from or write to the database, database DSN name, data type, LS0100 value in GP/GLC/FG, etc. Windows DSN(ODBC) Based on Database name stated in the Pointer file the database is located and opened for reading/writing Windows DSN(ODBC) Pointer file data references, LS0100, are read from or written to the database Figure 3

7 Page: 7 of 26 GP-Pro/PBIII C-Package-03 Setup We are going to set up a project so that when a bit, LS goes high Either open the attached GP-Pro Project, DBtest.prw, and download it to your unit (select correct model you are using) or create your own as shown below. For the purpose of this application note create a Project for a GP or GLC using the Modbus Slave driver (this way no driver error appears on the display if a PLC is not connected). Add the following to a Base Screen: Bit Switch with trigger and monitor address set to LS009900, bit set Keypad input display using address LS0100 (to change the value) Save and download this project to the GP or GLC. A factory gateway can be used also but seeing that it does not have a display it is more difficult to interact with compared to touching the touch screen of a GP or GLC

8 Page: 8 of 26 Database Setup Creating a Simple Target Database In this section we will create a simple Access database that we will use in later sections to read and write GP/GLC/FG data from and to. Microsoft Access 2003 is shown in the pictures here. You can use any database that Windows DSN(ODBC) has a driver for. 1. Open Microsoft Access and create a new Blank Database. For simplicity save the database as C:\db1.mdb 2. Double-click on Create Table in Design View 3. Enter a field name as GPData as shown in Figure Set the data type to Number as shown in Figure Close and save the Table as Table1. If prompted for a Primary Key, select Yes to create one

9 Page: 9 of 26 Figure 4 We now have a database that will allow us to write integers to the GPData field within a table called Table1. It should be saved as C:\db1.mdb.

10 Page: 10 of 26 Configuring Windows DSN(ODBC) In this section we will set up the Windows DSN to point at the database we created in the previous section. The purpose of the windows DSN is to allow databases to be reference purely on a given name. Associated with the given name is the driver, location of the database as well as other database attributes. Administrative rights are required to setup DSN (ODBC) entries. 1. Open Control Panel Administrative Tools Data Sources (ODBC) 2. Click on the System DSN tab 3. Click the Add button 4. Choose the Microsoft Access Driver (*.mdb) from the list and click Finish 5. Enter the Data Source Name TargetDB 6. Click the Select button and select the database C:\db1.mdb which we created previously. The Dialog should now look similar to Figure 5

11 Page: 11 of 26 Figure 5 7. Click OK 8. We now see the new DSN entry TargetDB as shown in Figure 6 9. Click OK to complete DSN(ODBC) setup

12 Page: 12 of 26 Figure 6

13 Page: 13 of 26 Creating a Pointer File In order for data to be passed to a database we need to create a pointer file which will be read by Pro-Server. The purpose of the pointer file is to: identify what data is to be read from the GP/GLC/FG specify the data format of the data to be written to the Database Specify the database name, table and field to write the data There are two types of pointer files that you can use: Excel (.xls) or Access Database. Each has advantages and disadvantages as shown in Table 1 Can be used by Pro-Server while being edited/changed High speed execution Ease of setup If target database not available can hold data till next time pointer file is run by action in Pro-Server Table 1 Excel Access In this app note we will show how to setup logging using an Access Database Pointer file. Microsoft Access 2003 is shown in the pictures here. 1. Open Microsoft Access and create a new Blank Database. For simplicity save the database as C:\pointer.mdb

14 Page: 14 of Double-click on Create Table in Design View 3. Enter a field names and associated data type as shown in Figure 7 4. Close and save the Table as Table1. If prompted for a Primary Key, select Yes to create one 5. Open Table1 by double-clicking on it s name 6. Enter a new record as shown in Figure Close the Database

15 Page: 15 of 26 Figure 7

16 Page: 16 of 26 Figure 8 When this pointer entry is executed by Pro-Server using the Upload from the Database Action the integer signed valued of LS0100 is read from the Provider Node and written to the Database, TargetDB, into Table Table1, into the field GPData. When Download from the Database action is used the data is read from the database and written to LS0100. Instead of using LS0100 a Pro-Server Symbol name can also be used. The Data Type field represents the format that Pro-Sever should use to read from and write to the database. A list of supported data types is shown in Table 2 In this case we are using 2 which represents a 16-bit Signed Decimal number. Depending on the format or data, choose the correct number. Table 2

17 Page: 17 of 26 Pro-Server Setup Adding DSN Capability to Pro-Server Versions earlier than 4.5 By default Pro-Server versions earlier than 4.5 are not able to use the Windows DSN(ODBC). To configure Pro-Server to be able to use Windows DSN follow these steps: 1. Shut down Pro-Server and Pro-Studio 2. Open My Computer or Windows Explorer and browse to the Pro-Server Program Directory. Normally it is C:\Program Files\Pro-face\Pro-Server with Studio 3. Using a text editor open ProDB.ini. The contents of ProDB.ini should appear as below: [ODBC] DRIVER1=SQL Server DRIVER2=Oracle ODBC Driver 4. Edit the file so that it appears as below: [ODBC] DRIVER1=SQL Server DRIVER2=Oracle ODBC Driver DRIVER3=DSN 5. Save and close the file.

18 Page: 18 of 26 In Pro-Server the Upload to the Database and Download from the Database actions now include a new driver name called DSN. Adding Nodes to the Network Project Ensure that you have the GP/GLC/FG running a GP-Pro Project and that they connected to the same Ethernet network as the Pro-Server PC. 1. Start Pro-Studio and either create a new Network Project file or open an existing one 2. Click on the Search Active Nodes icon on the toolbar 3. Click on the Pro-Server PC IP address and click Entry. 4. Click on the Search Active Nodes icon on the toolbar again 5. Click on the IP address for the GP/GLC/FG you which you are gathering data from and click Entry. 6. Click on the Search Active Nodes icon on the toolbar again 7. When both are entered you should see a screen similar to Figure 9. Click Cancel

19 Page: 19 of 26 Figure 9 8. If the driver shown for the GP/GLC/FG in the nodes list does not match the driver in the GP-Pro Project, edit the node by right-clicking on it and selecting Edit node (Figure 10). Select the correct driver and click Enter

20 Page: 20 of 26 Figure 10 In this case the GP/GLC/FG is IP address The PC is IP address If you wish you can edit the names of the nodes as well. GP1 is the GP/GLC/FG and GP2 is the PC in this example. Register symbol for trigger bit In a later section we will set up a Provider Sheet which requires a trigger. We need to define a symbol which is just a common name for this trigger bit address. 1. Right clicking on the GP/GLC/FG node and select register symbol

21 Page: 21 of Enter the LS address as shown in Figure Click on the Bit button 4. Click the Create from Address button. This generates a name for us. 5. Click Ok Figure 11

22 Page: 22 of 26 Configuring the Upload to the Database Action This section will help us create a Pro-Server Action which can call using one or more Provider Sheets. In our case we want to write data to our database. 1. Right click on Action List. Choose Register Action 2. Select Upload to the Database from the Drop-down list 3. Change the name of the action to Database_Write as shown in Figure 12 Figure 12

23 Page: 23 of Click on Parameter 5. Make sure the Pointer file is not being edited then complete the form as shown in Figure 13. Figure 13

24 Page: 24 of Click OK to complete the action registration Configuring a Provider Sheet In this section we will create a Provider Sheet which will trigger the Database_Write action we created previously. 1. Right Click on Provider Information and select Register Provider Information 2. Select the GP/GLC/FG node and click Ok 3. Click the Upper edge trigger button. 4. Fill out the rest of the sheet so that it appears just like Figure Click Ok. When LS goes high a value of 1 will be written to the Database_Write action. The action will then execute it s list of entries to write to the database. In our case there is just one entry so only one piece of data will be written. When the action is complete the LS bit will be reset. When the bit is reset this does not necessarily mean the action completed successfully. To determine successful completion use the Provider Completion Settings tab.

25 Page: 25 of 26 Figure 14

26 Page: 26 of 26 Transferring the Network Project to the GP/GLC/FG In order for Pro-Server to react to a bit changing in the GP/GLC/FG the Pro-Server Network Project must be download to the unit. 1. Save the Network Project if it is open. 2. Right-click on the GP/GLC/FG node. 3. select Transfer Network Project