FAQSOFWINCC5

1、faqs of wincc5.0 on simens onlinehardcopy of partial areas of images in wincc v5.0 sp2question:how can i make a hardcopy of partial areas of an image (e.g. a graph). answer:for example, you have a graph placed in your window and you want to make a hardcopy of this image. to achieve this, you need to

2、 know the coordinates and the size of your window, then you can initiate the generation of a hardcopy with a button as follows: #include "apdefap.h"void onclick(char* lpszpicturename, char* lpszobjectname, char* lpszpropertyname)winexec("prtscr.exe /c="20;10;800;400"",s

3、w_shownormal); the numerical values in the sequence "positionx;positiony;width;height" correspond to the coordinates in the top left corner and the size of the window (figure 1).figure 1: print area please also consider entry-id 9414679 about printing hardcopies in landscape format wi

4、th wincc v5 (sp2)/ wincc v5.1 functions & samples: display driver block technique with the property "tag prefix" of picture windows (v5.0 and higher)question:how does the display driver block technique work with the property "tag prefix" of screen windows? answer:in your conf

5、iguration you are using the display driver technique. since version v5 of wincc you can use the property "tag prefix" of screen windows. in this example there is dynamization with tag linking, dynamic dialog and c script. dynamic dialog and c script work with a tag trigger. important:it is

6、 important that the tag prefix of a picture window corresponds to a global definition. this means that the tag prefix of the picture window is valid for all tags that are edited in this picture window or changed in any other way (script).consequently, these tags have to be members of the structure w

7、hose name you have specified as tag prefix for the image window.let us assume that you declare a tag with the name "hallo" outside the above-mentioned structure and try to change it in the picture window, then an attempt is made to change the tag with the name "tag_prefix.hallo".

8、 this leads to an error, because this tag does not exist.furthermore, make sure that the tag prefix of the picture window is also valid when you create another tag prefix in the picture window.the following interpretation is valid for tags that are edited in this picture window or changed in any oth

9、er way (script) in the sense of the second definition:"tag_prefix1.tag_prefix2.tag_name". note on dynamic dialog:in order to be able to work with the dynamic dialog you must observe the following two items: · the item must be specified with the property "tag prefix".example:

10、"ampel13." · the dynamic dialog checks whether the tab exists. therefore you have to create another normal tag again for each member tag of a structure.example:the structure has the three members ".red", ".yellow" and ".green". then you have to create the

11、 three tags "red", "yellow" and "green". advantage of this block technique:you don't have to use any unnecessary c scripts. a good performance is also achieved through the tag trigger. note on changing the tag prefix:please note that a change to a tag prefix only be

12、comes effective in a picture window when a picture change takes place in the picture window. this has been implemented in a sample project. see here also the online help of the graphics designer, in the "tag prefix" property of the picture window. charged software (payment by simatic card

13、/ automation value card):the download contains a wincc v5 project which demonstrates the functionality described using an example. ampel.exe (323 kb, 50 units) copy the "ampel.exe" file into a separate directory and start the file with a double-click. the wincc v5 project is now unpacked w

14、ith all its associated subdirectories. then you can open and process the project with wincc. steps required for setting up an opc connection (wincc v5.0 sp2)question:what steps are required to start up a wincc station as opc server or as opc client (ole for process control)? answer:steps required on

15、 the wincc station as opc server if you want to access this from another computer: 1. the opc server/client component must be installed (automatically installed at setup with wincc v5.0 sp2 and higher). 2. the dcom interface must be parameterized. necessary steps on the wincc station as opc client:

16、1. the opc server must be in the same network as the opc client. 2. in the wincc explorer you insert the opc channel via "right-click on tag management > add new drivers". please select "opc.chn" here. 3. now open the opc unit by clicking the + icon on the left of it or by dou

17、ble-clicking the opc channel. 4. in "opc groups" right-click "system parameters" and the "opc item manager" opens. 5. click the "computer" button, enter the name of the computer of the opc server and then click ok. this is only necessary if the opc server is n

18、ot operated locally. if used locally on the same computer, then double-click "local". 6. if the opc server supports a browser, then this can be selected accordingly through "browse server" to offer the possible opc tags in the "opc item manager".if this is not the case,

19、 then the opc tags have to be created manually. 7. acknowledge the subsequent "filter criteria" window with "next->". 8. now you see all the tags that the opc server has to offer. select the relevant tag with "add items". using the ctrl key you can select several tag

20、s at once. 9. if there is no connection, you can set one up by acknowledging with "yes" in the window that now opens. 10. select an appropriate name and acknowledge with "ok". 11. you should give a prefix for the sake of easy recognition. the opc connection should now be possible

21、 if the opc supports a browser like wincc. in the case of other opc servers you must ask the provider whether this is the case. please note that this is only a rough overview of the necessary steps. more information is available in the wincc information system. keywords:setup, connection, software i

22、nterface    saving process pictures locally on the multi-client with wincc multi-user systems with wincc v5.0 + sp2 and higher.question:how can i save the process pictures locally on the multiclient with wincc multi-user systems? answer:you have a project that runs on a wincc multi-user sy

23、stem. now process pictures are to be stored locally on the multiclient, so that these pictures and not the pictures from the server are used. this reduces the number of accesses made to the server via the network.go into the directory "<drive>siemenswinccbinpdlcache". (you may have t

24、o create this directory). in this directory create a subdirectory called <symbolicservername>. the "symbolic server name" corresponds to the service prefix; both terms mean exactly the same thing. you have to create a separate subdirectory with its own symbolic name for each server.

25、then you copy into it the process images for the respective server.the pictures must also continue to be available on the server. the date of the picture files of the multiclient must be more recent or the same as the date of the picture files of the server. as soon as the picture files on the serve

26、r have a more recent date, the runtime on the multiclient acquires the pictures from the server via the network. important:if through configuration new files are added or files are modified, then you must do a manual comparison of the copies on the client computer. referenced files (e.g. emf, wmf, b

27、mp) are always loaded from the project path via the network. note:how to store pictures on the uniclient is described in faq entry id 982658. keywords:performance improvement wincc v5.0: starting the project automatically depending on the user logged inquestion:how can i start a wincc project automa

28、tically depending on the user logged in when the computer is booted? answer:when starting the computer you want to have a specific project started in the wincc control center or in wincc runtime depending on the user logged in. if you are using the "autostartrt.exe" program, it is only pos

29、sible to start wincc directly when the computer is booted independent of the user logged in. there is however one possibility of starting a project depending on the user logged in either in rt or only in the control center. for this you must create a link to the "<project_name>.mcp"

30、file of the required project in the following directory: <drive:>winnt.400/profiles/<username>/startmenu/programs/autostart if this project is terminated in the rt, then the next time the computer is booted with the corresponding login, then it starts again in runtime mode. if another us

31、er has another project open on this computer, then a link is to be made to this project under the other user profile in the same way as described above.note:this is only possible if you have an rc license installed on your computer, because otherwise wincc runs in demo mode.keywords:automatic startu

32、psimatic wincc option package: open development kit odk version 5.0 sp1summary:effective immediately, the simatic wincc option package open development kit v5.0 sp1 is released for delivery. compared to the previous version, it contains the following function expansion: · process control option

33、s support for wincc v5.0 sp2 for additional information, see the product description. product description: general informationthe simatic wincc option package open development kit (odk) v5.0 sp1 replaces the previous odk v5.0. odk v5.0 sp1 is released for wincc v5.0, v5.0 sp1 and v5.0 sp2. odk v5.0

34、sp1 can be ordered from the internet as a free update to odk v5.0. to do so, access the simatic customer support web site at www.ad.siemens.de/simatic-cs and select the "product support" tab. in the "entry id" field of the "simple search" function, enter the id number &

35、quot;6944475" and then click on the "display" button. as proof of purchase and authorization for this free update, you will need the identification number of your original odk v5.0 software delivery.for users of odk v4.01, a low-priced upgrade package from odk v4.01 to odk v5.0 sp1 is

36、 available. function expansionsthe open development kit (odk) makes data and functions of wincc available via programming interfaces, which allows individual wincc extensions to be created in scripts or programs. odk v5.0 includes expansions that support the increased configuration possibilities of

37、the wincc v5.0 basic package. in odk v5.0 sp1, process control options are supported as well (basic process control, storage and chipcard). open development kit odkthe odk option package enables you to use internal wincc functions. for example, the following applications are possible: · access

38、to values from tag management or archives · generic configuration, e.g. generation of tags or screens · integration of already existing processing programs · generation of messages and application routines · control of the measured value recording from application routines ·

39、 control of reports from application programs · use of wincc configuration dialogs for in-house-developed software options the following data can be accessed: · tag management data · archive data · configuration data configuration and runtime functions can be utilized. the api fu

40、nctions can be used at the following places: · in c development environments for your own windows applications; as the development environment, microsoft visual c+ version 6 is required · within wincc, e.g. for c-actions in global scripts or the graphics designer the odk option package con

41、sists of: · cd-rom containing header files, libraries, online help and examples · documentation of the api functions in electronic form (no printed manuals) · voucher for a one day "odk introduction" class for a maximum of 3 participants for questions regarding the introduct

42、ory class, please contact your responsible siemens office. ordering wincc option package odk v5.0 sp1 product name order number wincc/odk consisting of:- odk cd-rom- electronic documentation- 1 day class (for on-site class, add travel expenses) 6av6371-1cc05-0bx0 wincc/odk upgrade 1)(from v4.01 to v

43、5.0 sp1) 6av6371-1cc05-0bx4 wincc/odk update(from v5.0 to v5.0 sp1) ordering via the internet(entry id: 6944475) 1) the installation of the odk upgrade requires odk v4.01 to be already installed! for further questions, please contact your responsible siemens office. function extension of the control

44、 variables of the user archive to wincc v5.0question:i would like to attach data records to a user archive. is there a simpler way than via c scripts? answer:with wincc v5.0 the function of the control variables for the user archive is extended. it is now possible to attach data records to a user ar

45、chive via the control variables. this does away with the need for a c script. enter the id "-1" and job "6" to read the current contents of the process variables into the table. the new values are added to the end of the table. the ids of the data records are counted up in sequen

46、ce. the jobs "write, job 7" and "delete, job 8" are not possible via id "-1". more information on the control variables is available from the online help on the user archive. keywords:archive configuration functions & samples: create message when logging onquestion:

47、how can i create a message when logging on? answer:the following example for wincc v5.0 / v5.0 spx shows how you can generate a message in alarm logging when logging on. as process value block this message contains the name of the user logged on. proceed as follows for this: 1. create an internal te

48、xt variable (8 bits, length sufficient for the longest user name) for the previous user "olduser" and for the user currently logged on "currentuser". if the variable "currentuser" already exists, you do not need to create it again. 2. in addition you need the internal b

49、it variable "loginbit" to trigger the message system. 3. in the message system link the "loginbit" as event variable with a message and in the message incorporate the variable "currentuser" as process value block. 4. the following script is to be incorporated as new act

50、ion in the "global script" editor under "actions/global actions". the trigger of this action is set on the variable "currentuser". you need the "sleep call" (see script) of windows, because the alarm logging has its own variable display that is refreshed every

51、 second. this means that the variable "currentuser" in the message system at the moment the message is generated does not yet have the actual value. with the "sleep call" the action is delayed until the variable "currentuser" is updated in the variable display. 5. in or

52、der for you to obtain an entry in your archive when you start wincc, you must assign an initial value (e.g. restart) for the variable "olduser".program code:include "apdefap.h"int gscaction( void )/ include sleep() - function#pragma code ("kernel32.dll")void sleep(int a

53、);#pragma code() / variable declarationchar *newuser, *olduser;olduser=gettagchar("olduser");newuser=gettagchar("currentuser"); / output in the diagnostic windowprintf("new-user: %srn",newuser);printf("old-user: %srn",olduser);printf("%drn",strlen(ne

54、wuser); / check out if the "currentuser" is emptyif(strlen(newuser)!=0)/ reset of the "loginbit"settagbit("loginbit",0); / waiting for 1 sec. and then releasing the messagesleep(1000); / release messages + setting again the "olduser"settagbit("loginbit&qu

55、ot;,1);settagchar("olduser",newuser);return 1; charged software (payment by simatic card):the example contains a wincc v5.0 + sp1 project that generates a message in the alarm logging when logging on. the logged-on users are stored in a long-term/short-term archive. you can test the functi

56、on immediately with the following users: userpasswordadministratoradministratortestertesteruseruserlogin1.exe(2,002 kb, 25 units) copy the "login.exe" into a separate directory and then start the file with a double-click. the wincc v5.0 + sp1 project is unpacked automatically with all the

57、associated subdirectories. then you can open the unpacked project with the wincc explorer. please change the name of the server in the project to the name of your computer. now you can test the project and adapt it to your requirements. note:information on this topic for wincc v5.1 / wincc v6.0 and

58、higher is available in entry id: 11870927. search terms:logging on, protocols functions & samples: exporting multiple wincc trends to an excel filequestion:how can i export multiple trends to an excel file? answer: function:the sample project "export.exe" calls the tlgbackupa or tlgbac

59、kupa_ug function multiple times. in this project, you can define the export period exactly down to the second. by calling this function multiple times you can export multiple trends to a csv file. you have two options for creating the csv file: 1. the individual values of the exported trends are sep

60、arated by a line with the name of the trend and dashes. this file can be edited with microsoft excel. you can define the name of the file to be exported yourself (tlgbackupa). 2. the individual values of the exported trends are written in one column per trend. this file can be edited with microsoft

61、excel. you can define the name of the file to be exported yourself (tlgbackupa_ug).charged software (payment by simatic card / automation value card avc): the following download includes a wincc project with the necessary configuration in the graphics designers and the global scripts required. the project has been created with wincc v5.0 + service pack 1. you can adapt the configuration as you wish to suit your requirements. note:before using the