Skip to Content

Register Login

Industry Online Support

Technical Forum

Navigation

WinCC V7 .Net controls

Created by: RPvM at: 9/19/2008 2:14 PM (3 Replies)

Rating (0)

Thanks 0

4 Entries

9/19/2008 2:14 PM	Rate (0)
RPvM Posts: 22 Rating: (0)	Hello, I'm struggling with the .net container in WinCC V7. This could be (potentially) a very nice and powerfull feature. For myself I see lot's of opportunities with this. Sofar I managed to get a selfmade control in it, make a property visible and attach a tag to it. The control can receive the tagvalue and make it visible/do actions with it. However I can't manage to get information from the control to WinCC. Does anyone have (general) information on the .Net container? Samples? How-to's? Behaviour? And especially how to get info from the control to WinCC? For example, Direct Connection and Access from VB-script did not work for me. (Or I was doing something wrong) (Siemens NL couldn't help me and the WinCC-help is very limited on this subject) Of course I do understand that the content of the .Net container cannot be the responsibility of Siemens. However, it would begreat if there was somekind of description how to use this feature and a description of possibilities and/or limitations. It should be in WinCC with a purpose, I hope.... Thanks in advance Ronald
RPvM Posts: 22 Rating: (0)	Last edited by: RPvM at: 9/26/2008 2:58 PM It looks like it should(?) or could(?) be done with IndustrialX V7 Description downloadable here (CHM) http://cache.automation.siemens.com/dnl/TM/TM4ODkxAAAA_29489481_HB/Infoseite.html It looks like it now works with VB.Net (VS 2005) Description is not too clear (still lots of ActiveX in here) but there should be some samples with VB.Net as well in this package. Question is still: Is it also possible without IndustrialX? (maybe with some limitations) Or do I have to use IndustrialX? Last edited by: RPvM at: 9/19/2008 4:37 PM
Suggestion To thank Quote Answer

6/25/2009 12:23 PM	Rate (0)
miro79 Posts: 15 Rating: (0)	Hi I have the same problem. My .net control made in Visual C# 2008 is a login dialog with two TextBoxes (username and password). I added two properties "User" and "Pass" with code: [code] [Category("Access")] [Description("Gets or sets the user name in the text box")] public string User { get { return username.Text; } set { username.Text = value;} } [Category("Access")] [Description("Gets or sets the password in the text box")] public string Pass { get { return password.Text; } set { password.Text = value; } } [/code] and I connect Tags in WinCC 7 to these two properties. When I change tag value in WinCC immediately I see new value in control, but when I change username or password field in the control nothing happen in WinCC. WinCC doesnt see that properties changed value and not assign new value to Tags. I can read properties value by script and its works fine, but why WinCC doesnt change value of tags ? What I should do in C# to wincc read corectly properties ?
miro79 Posts: 15 Rating: (0)
Suggestion To thank Quote Answer

6/25/2009 1:37 PM	Rate (0)
RPvM Posts: 22 Rating: (0)	Hi Miro79, Yes, I found this as well... More info is in the IndustrialX manual You can find it here: http://support.automation.siemens.com/WW/llisapi.dll?func=cslib.csinfo&lang=en&objid=29489481&caller=view Click the "Info" on the right (NOT "display" or "download") A popup will show you the available downloads, also for IndustrialX This manual won't help you that much, but in the IndustrialX package itself there area fewVB.NET samples as well. Writing to tagslooked not that straightforward to me. IndustrialX takes some of the handling for this (as setting the property of the control with the tag attached obviously does not work). In the samples you can see some additional stuff that handles tagwriting (and other things) Still it's quite a hussle and I decided to make all in VB.NET and unfortunately not use WinCC, because the advantage was almost gone in my case. Maybewas also my lack of understanding of the IndustrialX package and the .NET platform as well...However support on this seems to be more or non-existent and for sure not in the Netherlands. Maybe it can help you...maybe not, but this is my experience sofar. Goodluck!
RPvM Posts: 22 Rating: (0)
Suggestion To thank Quote Answer

7/9/2010 6:12 PM	Rate (0)
knockNrod Posts: 1 Rating: (0)	I'm struggling with many of these same issues. Our company (myself in particular) design HMIs for other other companies (usually to operate a furnace they've purchased through the company). Typically, these are Level 2 HMI screens using .Net with OPC. More recently, however we have more demand to incorporate our Level 2 screens into Level 1 screens, and the power and potential of WinCC is intriguing. Like you, I wish they'd document this better. Heck, some enterprising schmuck from Siemens should publish a book on this stuff, which would isolate Siemens from liability, if that's their concern, and they' make a bundle of money! That said, here's my theory of what's happening in your case. The objects that are created by Siemens for use in graphics designer are using some internal mechanism to link events back to the tags. There are exceptions, even within their code -- the I/O Fields are revealing (a graphic's geometry is another example, but not very revealing). In the case of I/O Fields, the tag has to be tied back to change event manually, or the tag isn't updated. You can do the same thing in the case of your .Net controls. They have visible change events associated with them, and the tag can be written to from within that event, either dynamically or via a short script function. It's not exactly what you're looking for, but I suspect it's as close as you'll get.
knockNrod Posts: 1 Rating: (0)
Suggestion To thank Quote Answer

|

Share this page:

Share this page on...

Related topics by keywords:

WinCC Scripting

Follow us on