6/7/2013 8:36 AM | |
Joined: 12/27/2007 Last visit: 8/16/2024 Posts: 80 Rating: (1) |
Hello Damayanti, You can achive this by writing few VBS in your WinCC Project. Please refer attached document by which you will be able to store the data in to MS Access Database. You can retrive this data by writing basic connectivity scripts. Regards, Pramod Mahadik AttachmentExample__Configuring_a_Database_Connection_with_VBS.pdf (297 Downloads) |
Last edited by: Whiteford at: 6/7/2013 8:36 AM |
|
6/8/2013 1:39 PM | |
Joined: 1/29/2006 Last visit: 9/11/2024 Posts: 446 Rating: (64) |
Hey, Damayanti! It can be done, basically in 2 ways: 1. with use of original WinCC tools: on-line trend control or on-line table control. On line trend control has an option of exporting data to csv, But, as I remember, you can define only variable and time period (with usual controlls, on trend) But you do not have any influence on amount of data and time resolution of data, that will be exported. I have tested that, it exports all data, saved in archive, for selected period. If you f.e. define archiving period of 10s, you will receive one value for every 10 seconds. The samo goes for export from table control. 2. With use of options, f.e. WinCC Connectivity pack and VBS programming, or option WinCC DataMonitor and only configuring. Logical question is, why do you need Options (that cost additional money) for access to WinCC archive data: in WinCC, data is archived in SQL server; so, if you have WinCC installed, you also have complete SQL server. But acces to databases is restricted (with Licence policy, Siemens & MS) only to things, that can be "reached" through normal use of WinCC, as described in my Point 1. Also, if you look on forum about sollutions, how to export data from WinCC to other applications (f.e. Excell, or even in other DataBases), it is valid allways only for "current" values, and not for archived values). So, to gain "free" access to archived data (legally), you need to buy one of options. I have allready worked with both options, WinCC DataMonitor and WinCC connectivity pack. Both are OK; with DataMonitor you get more, you do not have to programm anything, only configure, but it is appr. 3 times more expensive than option Connectivity pack.With option Connectivity pack, which is cheaper, you get free access to all archived data, but you have to do programming by yourself (VBS scripting,...). So, to your concrete problem: I have had very similar project, few years ago. Customer wanted to have 30 minuteaverage values from Midnight to midnight (for 1 day, any day in archived values!) and also a 24 hour average value for each day in month. I did it with Option Connectivity pack and VBS scripting. This project was originally made with WinCC V6.2, SP3, butyesterday, I converted it inV7.0, SP3, Upd1. It works normally. I wanted to send youthis project, but unfortunatelly, it is 128 MB big and I can not attach it here (there is a restriction of 4MBfor attachments in forum). So, If you are interested in this project, send me a private message with your e-mail, and I will split this project to smaller, 10MB pieces and send it to you directly. At this time, I will only attach 2 pdl-s, where the whole system is running, and also VBS and C scripts, needed for that. If you want, you can find in those files and scripts, which tags and archives are needed in this example (only internal tags). Scripts were originally written in my native (Slovene) language. Therefore, all function names and local variable names might sound very strange to you, but I tried to make all comments in english, so that you would understand, how script works. As you will see, the most VBS scripting is about writing proper date and time strings in order to get right data from SQL. Let me remind you, that data in SQL allways has a UTC time stamp, which normally differs from your local time. UTC also does not recognise the difference between summer and winter time, and so on. .... Another thing: in VBS, there is also a part, where you save gathered data to a file. Before you do that, you have to create a new folder on your disk, C:\TEST_VBS_FORUM. This folder is "hard" defined in VBS scripts; if you want to change it, find it in scrpits and change it. Have fun! uel123. AttachmentFORUM_DAMAYANTI.zip (172 Downloads) |
6/10/2013 8:09 AM | |
Joined: 10/3/2010 Last visit: 9/20/2024 Posts: 1562 Rating: (191) |
Depending on how many tags you need to log and the logging frequency, you can write a VBScript to log data yourself to another SQL database instead of the one from WinCC itself (to avoid licensing issues, although access to WinCC's SQL and its licensing has been discussed many times before without a clear result). There's a Siemens Support manual about logging data to an SQL (it's actually about WinCC Flexible but it could set you on the right way): http://support.automation.siemens.com/US/llisapi.dll/csfetch/24677043/24677043_WinCC_flexible_SQL_Datenbank_en.pdf?func=cslib.csFetch&nodeid=44253917 At the end of the topic below, you can get some clues (check attachment there). https://www.automation.siemens.com/tf/WW/en/Posts/65120 Brgds. |
B r g d s , |
|
Follow us on