MorphuisOGrady
Member
Right guys can we at least agree on one thing? Regardless of whether we use VBS or C for scripting in WinCC, WinCC is one of the worst SCADA packages on the market.
Combo said:no doesn't work.
...... And no, I will not use reset in the PLC, that's not clean.
......
I worked with intouch , cimplicity , WizCon and WinCC ... and I cannot agree with you ,they all have good and bad points.They all start to look similar in lay-out.If they can use WinCC as 'engine' for PCS7 to do Process control then WinCC can't be that bad.Right guys can we at least agree on one thing? Regardless of whether we use VBS or C for scripting in WinCC, WinCC is one of the worst SCADA packages on the market.
Now why not set the bit with the Press Left action (using direct connection) and resetting the bit with the Release Left action?
This should work and needs no scripting and should work faster than running a script each time.(at least thats what the siemens-trainer told me.....)
Me too!!!I have gone away from that because I have been burned.
Jeebs said:why not set the bit with the Press Left action (using direct connection)
stplanken said:You could use that for boolean tags and fixed values. I always use 8-bit unsigned integers and some bit filtering to reduce the number of (expensive) tags required.
Jeebs said:Correct me if I'm wrong, but:
When I create a button using WinCC and go to Object properties > Events, I have the choice of:
-Action
-Press Left
-Release left
-Press right
-Release right
Now why not set the bit with the Press Left action (using direct connection) and resetting the bit with the Release Left action?
This should work and needs no scripting and should work faster than running a script each time.(at least thats what the siemens-trainer told me.....)
So I6.3 is the address you are trying to set via WinCC. I can see a problem with using an input and not any other kind of address (Mx.y, DBx.DBXy.z, Qx.y). Now what do you think the problem is ?I6.3
Have you programmed a --(R) of the same address, i.e. a reset ?OB1 cycle execution NW 58/A R ladder
JesperMP said:1st, I am with Jeebs, why use scripts to solve something that you can do without scripts ?
2nd, even if you can do it with or without scripts, like Roy says, no matter if you do it like this, it has its clear disadvantages.
And it is much worse than the 40ms cycle time Roy mentions, he probably means the cycle time in the PLC, but what about the tag update time in WinCC ? A mouseclick only lasts a few milliseconds, and a typical tag update time is 1 second (400 ms if you have set it up to be fast). So for it to work the operator has to force himself to hold the button pressed for a little while in an unnatural way.
Add to that there are many things that can go wrong, so you risk that the bit never gets reset.
I have gone away from that because I have been burned.