Brute force vs. "programming"

CoDeSys Tasks (if the hardware supports it) allow you to define a watchdog time and sensitivity. The sensitivity is an integer that goes along with the time to determine when to throw a watchdog error.

If the sensitivity is 0 or 1, the error is thrown as soon as the task exceeds the watchdog setting.

If the sensitivity, n, it > 1 then the error is thrown after n consecutive task executions > the watchdog time OR a single execution that exceeds n times the watchdog time setting.

I think this is to allow for occasional running of code expected to take a little longer than the normal watchdog time. I don't think I'd do this with a task doing the I/O work but perhaps for a task that runs during setup or analysis it would be ok.
 
Last edited:

Similar Topics

I know, why bother...If I had my druthers I wouldn't. I have a proven batching application developed and written in CLX, but the newest customer...
Replies
7
Views
2,731
Hi everyone i have a customer, who wants to show an alarm on the machine, if the I/O forces are enabled and set, on at ControlLogix L81E with...
Replies
3
Views
223
Hi there, I'm doing some extensive testing and commissioning with a slew of new Emerson PACSystems RX3i PLCs. It would be convenient to...
Replies
5
Views
93
Hello all, I have a question in regards to RSlogix 5000. I am having issues with the program force closing when I try to make online edits. We...
Replies
0
Views
114
Hello all, I have some parameter files that I'm using. Most of the tags are direct reference to the PLC, but a couple are HMI tags. If I change...
Replies
1
Views
481
Back
Top Bottom