Skip to Content

Register Login

Industry Online Support

Technical Forum

Navigation

Total Response time of an Automation System

Created by: BAIJU at: 3/2/2010 9:05 AM (2 Replies)

Rating (2)

Thanks 0

3 Entries

3/2/2010 9:05 AM	Rate (0)
BAIJU Posts: 9 Rating: (0)	Hi All, I am using the WinCC HMI, S7417 controller and S7300 family IO Modules in my project. My customer is interested in knowing the response time of my system. ie., the response time from the instance of issuing a command (DO or AO) on the HMI until actual closing contact in the IO card. And the maximum duration from the contact closure on IO card until reflection of the corresponding signal in the HMI. How this can be calculated? What factors are responsible for determining this parameter? Thanks in advance. Regards, Baiju
BAIJU Posts: 9 Rating: (0)	Last edited by: BAIJU at: 3/2/2010 9:06 AM
Suggestion To thank Quote Answer

5/28/2010 8:45 AM	Rate (1)
Ayman Elotaify Platinum Member Joined: 5/28/2008 Last visit: 9/9/2024 Posts: 4515 Rating: (839)	BAIJU Hi All, I am using the WinCC HMI, S7417 controller and S7300 family IO Modules in my project. My customer is interested in knowing the response time of my system. ie., the response time from the instance of issuing a command (DO or AO) on the HMI until actual closing contact in the IO card. And the maximum duration from the contact closure on IO card until reflection of the corresponding signal in the HMI. How this can be calculated? What factors are responsible for determining this parameter? Thanks in advance. Regards, Baiju Hello BAIJU, Let's talk here about scan cycle time Scan cycle time : is the time the CPU takes to run the user program once through. And for sure this scan time changes from one cycle to the other based on the user program. Also you can easily monitor it by connecting your PG with the CPU and open the Module Information. You can see the shortest scan time, longest scan time and current/last scan time. But if you want to talk about WinCC (I mean to measure the time from the instance of issuing a command DO or AO until actual response in the IO card). That's depends on the triggering time you are using in WinCC. you may use 2 sec. update time for the whole project. so if a DI for instance changed from 0 to 1, you expect to see that change immediatlly while you will see it after about 2 sec. Thus because the triggering time / update time of that tag in the WinCC. You can change that time from the properties of the I/O field in the WinCC. Also to sense this value you can make different I/O fields in the same screen with different values of that time and now, change the input value in PLC and see the effects on the RT of WinCC. To Conclude, What I would like to say, you can tell your customer exactlly how long the longest scan cycle is. and how long the shortest scan cycle is. and you can show him the response on the WinCC which is depened also on the update time. If he feel that there is a delay in this time, you can minimize this time. Hope this helps, Attachment mod info.JPG (395 Downloads)
	Last edited by: Ayman Elotaify at: 5/28/2010 8:46 AM Ayman Elotaify
Suggestion To thank Quote Answer

5/28/2010 11:24 AM	Rate (1)
fritz Diamond Expert Joined: 10/7/2005 Last visit: 9/19/2024 Posts: 3021 Rating: (1054)	HelloBAIJU I have a feeling you will like the link below: Establishing the DP response time, HMI update time and the HMI operating time for typical configurations on the non-clocked PROFIBUS DP A fair few more other useful performance calculators can be found HERE I hope this helps
	Cheers fritz The advice and opinion given in this thread is that of the author and does not necessarily reflect the views of I S Systems Pty Limited. To find out how I S Systems can help you with your automation needs please visit www.issystems.com.au.
Suggestion To thank Quote Answer

|

Share this page:

Share this page on...

Follow us on