Watchdog timer on simulated device expires

[SteveP]

A Watchdog Timer for a simulated device is supposed to never expire according to http://zone.ni.com/devzone/cda/tut/p/id/3698 under theTiming and Trigering Considerations for Using Simulated Devices where it states "Watchdog timers never expire."

However, a simulated X series USB-6343 which does have a hardware watchdog timer, indicates it is expired upon a check of the DAQmx Expired property immediately after starting a watchdog timer task.  The attached Write Dig Chan-Watchdog Timer.vi example, modified to include the DAQmx Expired property shows this behavior when the device is a simulated device.

DAQmx 9.3, LV2010 SP1

[KyleTTU]

Hi SteveP, 

Could you also attach a screenshot of your front panel to indicate the channels/values you are setting?  I ran this on my end and was unable to reproduce the issue with the VI you provided.  I am using the newer DAQmx but would like to be able to get the same result you are seeing. 

Regards, 

Kyle S

[SteveP]

Kyle,

Channel Parameters - Lines is Dev1/port0/line0:7

Watchdog parameters - Device is Dev1, Expiration States index 0 has Physical Channel set to Dev1/port0/line0:7 and expiration state is low.

Screenshot jpg attached.

I also simplified this vi (attached) by removing the digital write and only leaving the watchdog timer.  It still gives the expiration error and gives the error with timeout set to 1 sec and physical channel set to Dev1/port0/line0.

It also gives the timeout error with timeout set to -1 which is supposed to mean the internal timer never expires.

I will try with DAQmx 9.4 after downloading.  I have tried with MAX 5.0

Steve

[KyleTTU]

Hi Steve,

Thanks for the info, I gave it another shot and was not able to get the expiration/error.  If there is a physical error message popping up could you give me the error number associated with it to try to dig in further?  It may as well be something that is tied to the driver and hopefully is fixed in the newer one, that I'm not sure of yet.  I have been trying to locate a PC that hasn't been upgraded to the newest version of LabVIEW which in turn most of the time has the newer DAQ.  Try the update and see if it persists, also if there is an error code I'd like to know more details on it.

Regards,

Kyle S 

[SteveP · Accepted solution]

Running now with DAQmx 9.4 with no expiration error.  Of course, a reboot was involved and I don't recall for sure if I rebooted since the time I first noticed this issue.  Maybe I should have done a reboot before testing with DAQmx 9.4 just to make sure.

[KyleTTU]

Hi Steve,

It is good to hear you got things up and running.  It may have been an issue with not rebooting and the driver not fully installing but it sounds like everything is working now!

Happy Programming!

Regards, 

Kyle S