01-27-2008 08:06 PM
01-28-2008 09:32 PM
01-29-2008 01:54 PM
01-30-2008 09:29 AM
Hi Vanessa,
I am glad that you were able to find the appropriate VIs for the RFSA and Switch cases. I went ahead and installed the drivers for the 5690 and confirmed that there is in fact no Self-Test VI for the 5690. A possible work around would be to initialize the device and then close it right away and then handle the errors that correspond to a malfunction of the device. For instance, you could use a case structure with cases that correspond to various error codes that come up when the board isn't functioning properly, and then use those cases to direct your program flow accordingly.
Let me know if I need to clarify anything or this doesn't work for your application.
Regards,
01-30-2008 01:41 PM - edited 01-30-2008 01:44 PM
01-30-2008 02:02 PM
01-30-2008 02:32 PM
Hi Vanessa,
You are correct, the 5660 requires the use of the 5660 drivers rather than RFSA. I apologize if I misled you there. It also appears there is no Self-test for this device so I would definitely attempt to implement the alternative work around for the 5660 as well.
The reason why the 5660 and other older devices do not have the self-test functionality is due to the underlying driver API they are derived from. For instance, the 5660 used the 5620 Digitizer which is fundamentally based on the Traditional DAQ driver. The 5661 on the other hand uses the 5142 Digitizer which is supported on an API (RFSA) derived from the DAQmx driver. You can verify this in Measurement and Automation Explorer by where the device is listed. Newer devices will be listed as NI-DAQmx Devices, while older devices will be listed as Traditional NI-DAQ (Legacy) Devices. Furthermore, if you right click on a traditional DAQ device in MAX, the self-test option will not be present, while the NI-DAQmx device will have this feature.
Again, I apologize for the confusion between the RFSA and 5660 drivers. Hopefully this clears things up a bit.
Regards,
01-30-2008 06:50 PM