FieldPoint Family

cancel
Showing results for 
Search instead for 
Did you mean: 

Can not get Hardware Watchdog to work on cFP2000

I am trying to implement the hardware watchdog on a cFP2000. The problem is, it doesn't seem to do anything. Am I missing something?
 
I have a remote PC toggling the LED D between 0 and 1 every second. The RT HW watchdog is Whacked every time the value of LED D changes. If the LED D doesn't change for 10 seconds, the HW Watchdog should timeout and set an occurance which changes the state of LED C, but I can never get LED C to change states.
 
Thanks,
Steve
0 Kudos
Message 1 of 9
(8,551 Views)
Hi Selmore!
   It seems to me that I've found why.  It seems to  be quite an odd behavior, but... you have to "whack" manually at least 2 times, or ocurrence won't be generated!

   I'm cleaning up my code, then I'll post it.... I'll be back in a minute!

   BTW, the problem is that watchdog VIs are not documented...... your code seems right, in fact, if you manually switch LED D some times, at the beginning, then it works!

   PS.: which version of LV are you using?

graziano


Message Edited by Graziano on 01-04-2008 04:34 AM
0 Kudos
Message 2 of 9
(8,538 Views)
Here's the code: I hope it is compatible with your LV/driver versions.  If not, I'll post a picture of modifications!

Have a nice day!

graziano





Message Edited by Graziano on 01-04-2008 04:49 AM
Download All
0 Kudos
Message 3 of 9
(8,535 Views)

Thanks for the help graziona!

I'm running LV 7.1.1 with Watchdog 2.1.5 and implemented you change without any errors, but it still won't work. One thing I noticed is that the Watchdog Status output from the Whack remains DISABLED no mater how many times I Whack it. Is there some secret to enabling the HW Watchdog other than the Config block?

 

Thanks,

Steve

0 Kudos
Message 4 of 9
(8,524 Views)
Hi Steve!
   On my cFP-2020, your original VI doesn't work, and with my modifications it works, I don't know what it's related to.... I'll check the "disabled" stuff.....

   I have LV 7.1, Real-Time 7.1 and WatchDog 2.1.3.

   I'll be back in a while....

graziano
0 Kudos
Message 5 of 9
(8,520 Views)
Hi!
   I've tested application, and as "watchdog status" I get "running.  Can you post back the complete updated version f your VI?

   Once I made a silly VI demonstrating watchdog: it's here.  It resets cFP-2020 when watchdog expires.  If you want to try it... obviously you should make some daptions.

graziano
0 Kudos
Message 6 of 9
(8,517 Views)
hi!
   I've also found that the two "whack" are not needed, they can be substituted by "START" and "ENABLE", that you can find in advanced watchdog functions. They're embedded in Whack function, that's why putting 2 whacks it worked!





   About your problem, I can't actually figure out what's going on... if it is a matter of driver, or a matter of device (I've tested on cFP-2120).

graziano





Message Edited by Graziano on 01-04-2008 09:06 AM
0 Kudos
Message 7 of 9
(8,515 Views)

I finally managed to not only make it work, but to do what I want it to!!  Your version initially didn't work for me because the RT and the programmer were out of sync, so to speak.

The latest VI is attached and allows for some additional functionality.

 

Thanks for all the assistance,

Steve

 

P.S.: I know I committed a mortal sin by using Local Variables, but it works!

0 Kudos
Message 8 of 9
(8,499 Views)

Hi,

Thanks for posting your solutions! This helps other visitors to the forum. Just for reference, here are a couple of KnowledgeBase articles for reference:

Watchdog Timers - The New Industrial Feature Set

FieldPoint Watchdog Timer Questions

Good luck with your application!

Amanda Howard
Americas Services and Support Recruiting Manager
National Instruments
0 Kudos
Message 9 of 9
(8,442 Views)