Technical Forum

SIMATIC WinCC (TIA Portal)

WinCC TIA IO field modified event?

Thread Starter: Wulfgar   Started: 8/2/2012 5:34 PM   Replies: 9

« Previous thread Next thread »
Page 1 of 1 (10 items)
  8/2/2012, 5:34 PM
Joined 12/23/2009
Last visit: 4/2/2013
Posts: 40
Rating:
Rated: Outstanding [4 out of 5 / rated 1 time(s)]. (1) 
Rated: no ratings [0 out of 5 / rated 0 time(s)]. (0) 
Hello,

  I have some I/O fields on the HMI that the operator can modify (DINT). I need to copy the value into a recipe database in the PLC when a value is changed. I see no built in property and the only events are "activate" or "deactivate". I could not find in the manual an explanation of what these do and the help file does not have any info.
How do you tell the PLC when the operator has modified the value? Rnf:lblSmileyTooltip_  think
Top
  8/2/2012, 8:32 PM
Joined 7/7/2010
Last visit: 5/22/2013
Posts: 1980
Rating:
Rated: Excellent [4.01 out of 5 / rated 200 time(s)]. (200) 
Rated: no ratings [0 out of 5 / rated 0 time(s)]. (0) 
Wulfgar wrote:
Hello,

  I have some I/O fields on the HMI that the operator can modify (DINT). I need to copy the value into a recipe database in the PLC when a value is changed. I see no built in property and the only events are "activate" or "deactivate". I could not find in the manual an explanation of what these do and the help file does not have any info.
How do you tell the PLC when the operator has modified the value? Rnf:lblSmileyTooltip_  think

Several approaches come to mind for the basic panels.
1. For small / simple programs, just write the value every scan.
2. You can save the current value on 'first scan' to a 'LastIOfieldValue'.  Each scan compare 'LastIOfieldValue' to 'IOfieldValue'.  If they differ, update the recipe, and then update the 'LastIOfieldValue' from the 'IOfieldValue'.
3. You can try using the activate/deactivate to reset and set a bit you use to update the recipe.  If the value is the same, the recipe just gets the same value written.

You can create a simple multi-instance FB to detect the change and update recipe data and write the code just once.

Hopefully something in the above is useful.  For simple stuff, just updating it every plc scan works just fine, is easy to troubleshoot, but does mean you have to be sure it is ok to change the recipe value at that moment.

Helpful? Rate it.
Solved? Post it.
Top
  8/3/2012, 4:46 AM
Joined 12/23/2009
Last visit: 4/2/2013
Posts: 40
Rating:
Rated: Outstanding [4 out of 5 / rated 1 time(s)]. (1) 
Rated: no ratings [0 out of 5 / rated 0 time(s)]. (0) 
So it's basically a bug or oversite on Siemens part that there is no good way to do it and your just stuck trying to do a work around. I'll add this to my growing list of things that suck about Siemens right next to not being able to have a lighted push button on the HMI. Rnf:lblSmileyTooltip_
Top
  8/3/2012, 3:35 PM
Joined 7/7/2010
Last visit: 5/22/2013
Posts: 1980
Rating:
Rated: Excellent [4.01 out of 5 / rated 200 time(s)]. (200) 
Rated: no ratings [0 out of 5 / rated 0 time(s)]. (0) 
Wulfgar wrote:
So it's basically a bug or oversite on Siemens part that there is no good way to do it and your just stuck trying to do a work around. I'll add this to my growing list of things that suck about Siemens right next to not being able to have a lighted push button on the HMI. Rnf:lblSmileyTooltip_

If you use the comfort and more advanced panels, the options you are missing suddenly become possible.  I have a WinCC Flex 2008 setup running on an MP277 that has both of those features in use.

The more advanced the need, the more advanced the hardware and software.

Sure, it would be nice to have those options in basic panels, but most people just want basic stuff on the low-end panels so they can be installed at the lowest possible cost and be competitive with physical buttons, lights, and so on.

Helpful? Rate it.
Solved? Post it.
Top
  8/6/2012, 3:46 PM
Joined 12/23/2009
Last visit: 4/2/2013
Posts: 40
Rating:
Rated: Outstanding [4 out of 5 / rated 1 time(s)]. (1) 
Rated: no ratings [0 out of 5 / rated 0 time(s)]. (0) 
Thanks huggy, I was not aware their were basic software differences between the panel series. I can understand the low end panels having cheaper components, lower end touch screen and such to keep cost down. But handicapping the software on the low end seems a little silly to me.
Top
  8/6/2012, 3:57 PM
Joined 7/7/2010
Last visit: 5/22/2013
Posts: 1980
Rating:
Rated: Excellent [4.01 out of 5 / rated 200 time(s)]. (200) 
Rated: no ratings [0 out of 5 / rated 0 time(s)]. (0) 
Wulfgar wrote:
Thanks huggy, I was not aware their were basic software differences between the panel series. I can understand the low end panels having cheaper components, lower end touch screen and such to keep cost down. But handicapping the software on the low end seems a little silly to me.

There is only so much memory for the firmware and applications to run within with the basic panels.  It seems like a good business choice to make it affordable to support the stuff most people are replacing - customized button and light control stations.  I think once you want more event driven actions, you are not so much replacing an operator panel.  Instead, you are from the ground up thinking you will use the features available in a higher end human machine interface.

Sure, we would like both options even in lower end panels, but most are not willing to pay for it.  There are probably work-arounds for the things you want to do, but will take more programming on your part to make it happen.  Pay for your time, or pay for the more advanced panel.  Not always an easy choice.

Helpful? Rate it.
Solved? Post it.
Top
  8/6/2012, 4:16 PM
Joined 12/23/2009
Last visit: 4/2/2013
Posts: 40
Rating:
Rated: Outstanding [4 out of 5 / rated 1 time(s)]. (1) 
Rated: no ratings [0 out of 5 / rated 0 time(s)]. (0) 
Yes I understand there will be limitations due to hardware. But we are talking about very basic features that you would expect to have in any HMI not something exotic. For example the basic panel has some more advanced features like recipes but on the other hand you can't do something as basic as a lighted push button. Seems a bit odd doesn't it?
Top
  8/6/2012, 5:50 PM
Joined 7/7/2010
Last visit: 5/22/2013
Posts: 1980
Rating:
Rated: Excellent [4.01 out of 5 / rated 200 time(s)]. (200) 
Rated: no ratings [0 out of 5 / rated 0 time(s)]. (0) 
Wulfgar wrote:
Yes I understand there will be limitations due to hardware. But we are talking about very basic features that you would expect to have in any HMI not something exotic. For example the basic panel has some more advanced features like recipes but on the other hand you can't do something as basic as a lighted push button. Seems a bit odd doesn't it?

You can make a lighted pushbutton.  I did it with simple toggle logic, and visibility of drawn objects tied to the toggle bit.  Red for off state and Green for on state.  Over top of the 2 colored circles was an invisible button that toggles a bit.  Group that up and save to your library.  Now you have a simple lighted PB anywhere you need one.

Helpful? Rate it.
Solved? Post it.
Top
  8/6/2012, 5:52 PM
Joined 7/7/2010
Last visit: 5/22/2013
Posts: 1980
Rating:
Rated: Excellent [4.01 out of 5 / rated 200 time(s)]. (200) 
Rated: no ratings [0 out of 5 / rated 0 time(s)]. (0) 
I clicked on the library, global library, buttons and switches, and came up with a better option rather than drawing and grouping. Rnf:lblSmileyTooltip_   Try it, you might like it.

Helpful? Rate it.
Solved? Post it.
Top
  8/6/2012, 5:55 PM
Joined 12/23/2009
Last visit: 4/2/2013
Posts: 40
Rating:
Rated: Outstanding [4 out of 5 / rated 1 time(s)]. (1) 
Rated: no ratings [0 out of 5 / rated 0 time(s)]. (0) 
I've not tried creating a custom library object. I'll give your suggestion a try.
Thanks again for your response huggy.
Top
Page 1 of 1 (10 items)
Actions