In this lab we will configure logging for some of the data being collected by the demo project.
You should already have the Demo Project up and running. If not, please go ahead and do that now. Then, bring up the CIMPLICITY Workbench for the Cimpdemo project.
Now, select Project then Properties from the menu, or click the Project Properties icon on the toolbar.
Now let’s turn on the Database Logger by clicking the box.
You may have some of the protocols selected on yours, or you may have more to choose from (depending on what was loaded from the CD when you installed), but the key is the “X” in the Database Logger option.
Click on OK to acknowledge that the changes will come into effect the next time you start the project. Don’t bother stopping it right now - we have more work to do first!
Say, did you notice that new icon in the Workbench? We didn’t have that before. Only the options you actually have or have turned on show up. There’s less confusion that way!
Let's use that new icon. In the Workbench, double-click the Database Logging icon.
Some tables are already defined. Let's leave those alone for now. We will make a new table just for our data. Click on the New Table icon.
The New Table dialog box will appear.
Let’s name the table. In a large project you might have lots of tables, so we really want to name it something meaningful. How about “DEMO.” Now, choose Group Log Table, as the Table type. Then click on the “OK” button.
CIMPLICITY HMI lets you control how and when your data is logged without writing any custom software!
From this screen you can cause data to be logged on an event, like the end of a production run or end of a shift. You can cause data to be logged only while a batch is in production using the gated logging feature or to log data only while there is an alarm out there.
We’ll go ahead and use the logging conditions of “Periodic” and “5 Seconds.” This means that at every 5 seconds, the system will automatically log the data.
Click on the Logging Attributes tab.
From here you can choose what attributes about a Point get logged. Saving the previous value and the time last logged makes it MUCH easier to create reports later that indicate how much or how fast the data has changed. Saving the engineering units takes up some extra space but again makes reporting that much easier later. It helps to determine whether that piece of data was recorded in Fahrenheit or Centigrade. Let the data tell you instead of guessing!
And, this is VERY important for larger systems since you can record the name of the CIMPLICITY project that the data came from. This is very important if you are running TWO OR MORE projects on the same computer. That's another handy CIMPLICITY feature in itself - the ability to run multiple projects on one computer. This is very handy during system debug and checkout because you can just copy one of the projects and its logged data to its own PC later as the system grows and expands!
We will use the default of “Point Value.”
Now click on the Maintenance Events tab.
Look at the defaults for the Maintenance Events and Maintenance Actions tabs. We don’t need to change them - just review them. These are powerful configuration options that mean you don’t have to write programs to support the database. Just about everything you need can be configured in here.
With many databases and database tools you have to write a program to monitor disk space so that your log files don't fill it! Well, CIMPLICITY HMI does this for you already! On this tab you can configure the parameters. No software to write! Another way to look at this is: When there is only XX space left on my disk OR I have logged a certain number of records OR every X number of days OR every day at midnight OR whenever a point goes true, its TIME TO TAKE ACTION!
On the Maintenance Actions screen, you can automatically let your data be exported from your database or deleted completely from it. You can also move the data out to a separate archive file and save it for later analysis.
Databases grow large over time. From here, you can automatically compact the database or run an external program or an SQL command to take specific actions on your data.
http://www.cadfamily.com/html/Article/Configuring%20Logging%20for%20the%20Demo%20Project%20in%20Cimplicity_535_1.htm
No comments:
Post a Comment