Log In

Come Join Us!

Are you an
Engineering professional?
Join Eng-Tips Forums!
  • Talk With Other Members
  • Be Notified Of Responses
    To Your Posts
  • Keyword Search
  • One-Click Access To Your
    Favorite Forums
  • Automated Signatures
    On Your Posts
  • Best Of All, It's Free!
  • Students Click Here

*Eng-Tips's functionality depends on members receiving e-mail. By joining you are opting in to receive e-mail.

Posting Guidelines

Promoting, selling, recruiting, coursework and thesis posting is forbidden.

Students Click Here


Tripping a PLC watchdog - May be hard to trip something with 4 legs..

Tripping a PLC watchdog - May be hard to trip something with 4 legs..

Tripping a PLC watchdog - May be hard to trip something with 4 legs..

I'd like to restart a PLC by tripping its watchdog.

Most PLCs use the scan time to discover they're hung.

Do you folks have any ideas on how to forcefully extend the scan time. Got any favorite infinite-loop code? Done anything that inadvertently caused WD trips on your PLCs?

Keith Cress
kcress - http://www.flaminsystems.com

RE: Tripping a PLC watchdog - May be hard to trip something with 4 legs..

Use a Call function, and have it call its self.
Or use a Jump to label then Jump back to another label just in front of the first Jump.

RE: Tripping a PLC watchdog - May be hard to trip something with 4 legs..

Thanks dV8r.

Turns out the CLICK is too bungle-proof to allow either of those errors.
1) It has no "jump" commands to control program flow.
2) You cannot "nest" any subroutine calls so Calling a Call doesn't fly.

HOWEVER! I did just figure out another way to trip the Watch Dog. The WD looks at the scan time. If the scan time exceeds the currently set WD time the dog will go down. The CLICK also shows you what the current scan times are taking. So all I needed to do was come up with something time intensive to execute on command. CLICK offers a FOR loop. I just used a couple of lines to request a register shift of one bit to each of a thousand spare registers I had laying around, and the scan time would jump from 12ms to 155ms. Next I set the allowed WD time from the default of 200ms down to 50ms and voila! A tripped watchdog on command.

Sadly.. This causes a 'System Error' which halts everything and takes human intervention to recover from. There's no error trapping or any other mechanism to force a restart on detection of a system error. Guess I was thinking too much like an embedded systems guy where we have full control of everything.

So thanks for the suggestions. I'm just going to have to reset all 60 states in 5 state machines and deal with whatever else needs to be modified to restart the menagerie.

Keith Cress
kcress - http://www.flaminsystems.com

Red Flag This Post

Please let us know here why this post is inappropriate. Reasons such as off-topic, duplicates, flames, illegal, vulgar, or students posting their homework.

Red Flag Submitted

Thank you for helping keep Eng-Tips Forums free from inappropriate posts.
The Eng-Tips staff will check this out and take appropriate action.

Reply To This Thread

Posting in the Eng-Tips forums is a member-only feature.

Click Here to join Eng-Tips and talk with other members!


Close Box

Join Eng-Tips® Today!

Join your peers on the Internet's largest technical engineering professional community.
It's easy to join and it's free.

Here's Why Members Love Eng-Tips Forums:

Register now while it's still free!

Already a member? Close this window and log in.

Join Us             Close