Skip to Content

Register Login

Industry Online Support

Technical Forum

Navigation

Timer Tag

Created by: osama at: 3/10/2008 1:21 PM (6 Replies)

Rating (2)

Thanks 0

7 Entries

3/10/2008 1:21 PM	Rate (0)
osama Posts: 6 Rating: (0)	Hi, How can I configure and reada timer tag that start timing when a machine isstarted and stop timing when a machine is stopped in Wincc 6.0? Regards
osama Posts: 6 Rating: (0)
Suggestion To thank Quote Answer

3/10/2008 5:25 PM	Rate (1)
Phantom75 Posts: 2661 Rating: (279)	When you say machine, do you mean a motor (or some other field equipment)? You can time the “event” in WinCC (C script) but this is not a good way, since the measurement is not accurate and causes an unnecessary load. A better way is it time the event in the PLC and bring this time value to the HMI as a tag.
Phantom75 Posts: 2661 Rating: (279)
Suggestion To thank Quote Answer

3/11/2008 5:49 AM	Rate (0)
osama Posts: 6 Rating: (0)	HI Phantom, Do you mean that ,Is the only we to time an action in the Wincc will be through C- Scripts or VB? Thanks for your replay
osama Posts: 6 Rating: (0)
Suggestion To thank Quote Answer

3/11/2008 5:36 PM	Rate (1)
Danielle Posts: 1275 Rating: (123)	Hi, What are you trying to configure? Usually when we need to time machines working time we need a downtime management feature, to calculate how long certain equipments worked for, how long they were stopped by failures, etc... is this what you need? If so, take a look at the new WinCC option (available in v6.2) Downtime Monitor. If you need to know when a certain isolated event occured (machine started, for instance), you can use event messages. If you need to know how long one machine process took long, I suggest you time this on the PLC side, since, as it's been stated, it's more accurate. Also, if your WinCC station stops somehow, you won't lose the timer. Another way to implement this without the counter would be to log the time the machine started somehow, then log when the machine stopped, and find out how much time there is in between through scripts... but I still think doing it on the PLC is a lot less complicated... And once again... if you want to create a time model, being able to calculate cycle time, failure loss, performance, MTBF, MTBA, quality rate, etc. you should consider the Downtime Monitor option! Best regards, Danielle
Danielle Posts: 1275 Rating: (123)
Suggestion To thank Quote Answer

3/11/2008 6:26 PM	Rate (0)
Phantom75 Posts: 2661 Rating: (279)	Yes, either you can use the WinCC downtime manager (if it suits your needs) or you can build the downtime (or runtime) functionality in your PLC blocks, like we do in CEMAT. The bottom-line is, the solution depends on the nature of the problem you are trying to solve.
Phantom75 Posts: 2661 Rating: (279)
Suggestion To thank Quote Answer

3/12/2008 6:18 AM	Rate (0)
osama Posts: 6 Rating: (0)	HI,Exactly, Downtime Monitor has all the functions I need and I will be ordering it soon. Currently, I’ve used the tag logging and it will be superior if I can send the logged data to an Excel sheet? Thanks for your help Best Regards
osama Posts: 6 Rating: (0)	Last edited by: osama at: 12.03.2008 06:22
Suggestion To thank Quote Answer

3/13/2008 12:57 PM	Rate (0)
Danielle Posts: 1275 Rating: (123)	Hi, Downtime monitor will provide you ActiveX controls which will not only log data, but make it into useful treated information! I'm not sure to what extent these controls will allow you to filter the data to be exported. But you can still export data through scripts to Excel, or use the new tool (from v6.2 on) which allows you to export trend data to .csv files (which can be read into excel sheets through a macro)... Best regards, Danielle
Danielle Posts: 1275 Rating: (123)
Suggestion To thank Quote Answer

|

Share this page:

Share this page on...

Follow us on