8/27/2020 7:25 AM | |
Joined: 10/7/2005 Last visit: 10/9/2024 Posts: 3024 Rating: (1054)
|
Hi esantos I'm not surprised with what you observe and the reason is probably twofold:
|
Cheers |
|
8/27/2020 6:05 PM | |
Joined: 11/17/2010 Last visit: 10/8/2024 Posts: 105 Rating: (2) |
Hi Frink, I'm using one 414-2DP - 6ES7414-2XK05-0AB0 with Firmware 5.1. Thanks! |
Best regards, |
|
8/28/2020 12:53 AM | |
Joined: 10/7/2005 Last visit: 10/9/2024 Posts: 3024 Rating: (1054)
|
You could call the timer right away a second time so that it sees an RLO of 0 and is ready to started again in the next scan (or OB34 call). This won't help you with the S5 Timer inaccuracy itself though and the million $ question is: What is it that are you actually trying to achieve? Using the CPU 's clock bits or reading out the system time via SFC1 READ_CLK or using SFC64 TIME_TCK etc. are all based on the internal real time clock and will be far more accurate (although the CPU's real time clock drifts too as per CPU spec). IF a 100ms OB34 is already there, you could of course also simply add up an INT by 1 on every call and check when it reaches 10 to get a 1 second indicator. Back to the million $ question is: What is it that are you actually trying to achieve? (or why do you think you need an S5 Timer to achieve it) |
Cheers |
|
This contribution was helpful to1 thankful Users |
Follow us on