Why do I get Error-22011 when I try to run a HW Watchdog Timer vi?

[pmac]

I am trying to use the HW watchdog timer vi's on the RT functions palette (Watchdog Configure.vi and Watchdog Clear.vi). Error-22011 is generated when Watchdog Open.vi is called (a subvi to Watchdog Configure.vi).

"Explain Error" gives this result:

"NI-Watchdog: The watchdog hardware you requested is already in use, or has been permanently locked."

I get this error every time I execute Watchdog Configure.vi even if the host computer and network controller have just been rebooted. There is no place to specify or lock/unlock the hardware (that I can find). I'm using Windows XP, LV8.5, and the FP2010 controller.

Thanks in advance for any help.

pmac

[Graziano]

Hi!
   Just a silly question.... have you checked that NI-Watchdog software is installed on your FP? Check in MAX, see attachment.

   Have a nice day!

graziano

[pmac]

Yes, I have NI-Watchdog  2.1.5 installed on my FP.

In fact, I figured out what the Error-22011 problem was all about and I'm almost too embarrassed to say. I had Watchdog Configure.vi inside a while loop... so only the first iteration would be error free and for every iteration after that, the hardware would be "already in use". Hence, Error-22011.

I've made it over that hurdle, but I'm still having problems.

Now,I have both Watchdog Configure.vi and Watchdog Clear.vi outside the while loop and I put Watchdog Whack.vi inside the while loop (mainly to monitor the watchdog status output). I also wired the occurrence output of Watchdog Configure.vi to a second while loop in which there is a wait for occurrence.vi wired to a boolean indicator.

If I disconnect the ethernet cable while this vi is running, the program pauses and I get a Labview generated message informing me of a lost connection however, there is no occurrence generated and the watchdog stays in "running" status.

Apparently, I've misunderstood how to implement the watchdog vi's and I'll need someone to set me straight.

Is there anyone who can help?

Thanks,

pmac

[Graziano]

Hi!
   When you disconnect network cable, of course your LabView sees that target is no longer present, so it stops control of target (and PC application), but on the field point the application goes on until next reboot (perhaps it is like this in Real-Time, where I can embed application on cFP). That's because application runs in FieldPoint's local RAM.

   You can verify this letting your application blinking a LED of FieldPoint module.

   What do you expect to see when you disconnect network cable? Maybe I don't understand....

   Please, let me know....

   If you want, post your code (possibly for LV 7.1...)

   Have a nice day!

graziano

[Graziano]

and.... I have to admit that no everybody admit on the forum when they post for a silly mistake: I consider that a sort of honesty

Most of the time, people just say "yes, the problem is fixed now...". (me too, probably, in the past... )

graziano

[pmac]

I'm developing a system that will be running an embedded program on the FP that will continuously operate a pump while monitoring temperature, pressure, and a few other inputs. At the same time it will be sending and receiving status with another system via ethernet.

My interest in the watchdog vi's originated when I decided it might be useful to know if the communication link is lost. Several documents I looked through stated that the network watchdog feature set does not support the FP2010 network controller. This led me to the hardware watchdog vi's.

 So, I'm looking for a way to detect a lost communication link. It doesn't matter if it's an occurrence in the software or a digital output is toggled, just some indication of a lost link. It seemed like the watchdog vi's would be the way to do that, but I could be wrong.

pmac

[Graziano]

Hi!
   I think that for first you have to master Watchdog programming.  Then decide what you wish the application to do: do you want that application stops when link is lost? You can implement it raw with a simple ping, and a loop that if doesn't fed stops application... I don't know.... but for first troubleshoot watchdog.

    Apart from this, who should detect that communication is lost? PC or FieldPoint?PC automatically looses control of FP, if ethernet is disconnected, while from FP point of view is slightly different.....

   Let me know a little bit more!

graziano

[pmac]

The FP system should detect the lost link.

In our setup, the other system will be the host. My system will just be executing software on the FP hardware and waiting for commands from the host. 

For example, occassionally the host system will need to have fluid transferred to it and will send my FP system a boolean requesting a transfer. The FP system will open a valve to start the transfer and then wait for the host system to toggle the boolean. When the host system toggles the boolean, the FP will close the valve to stop the transfer. If communication is lost during a transfer the FP system will need to stop the fluid transfer so as not to overflow the host system. 

This is one possible scenario where it will be important to take action if communication is lost. There is probably others as well.

I'm not new to LV but I am new to Fieldpoint and ethernet and your questions are helping to clarify how these two systems will work together. - Thanks

pmac

[Graziano]

Hi pmac,
   please, clearify this: your application has to be embedded in FP (id est, you have LabView + Real-Time module AND build application for the target, set it to launch app at boot....), or you are controlling it from a PC (ie you launch LV on PC, connect LV to target and run app)? I can seem annoying, but it's usefull to know right.....

   By host you mean PC, if I understood.....
 
   Sorry for all these annoying questions, again.....have a nice day!

graziano

Message Edited by Graziano on 10-12-2007 08:10 AM

[pmac]

Currently, for the purposes of development, I'm running LV on a PC and connecting to the target and running the app, but the final implementation will be embedded and launched at boot. The host I refer to will be a PC running another application that communicates with my embedded application.

Does that clarify?

pmac