switch executive relay information

[petrz]

I'm creating IVI driver and I want to show relay information in NISE Virtual Device Relay Information table. Is it possible do that or is this options avilable only for NI switch?

[BalazsNagy]

Dear petrz!

First of all let me wellcome You on NI Discussion Forums!

Please allow me to recommend some learning material for NISE:

Learn to Program Switch Systems Using NI Switch Executive  

Pleae let me know, if Your problem is solved.

Best Regards,

[petrz]

For NI drivers it works fine. But I want use it in my own IVI driver, which I wrote in CVI.

[BalazsNagy]

Dear petrz!

Sorry for my late reply!

Did You implement he relay count functionality in Your own dirver?

I searched some useful documents, hat may help:

Instrument Driver Development Tools and Resources

The mos useful is the LabWindows CVI Instrument Driver Developers Guide (probably You know it)

Getting Started with IVI Drivers

Of course http://www.ivifoundation.org is one of the mos timportant resources.

Related to the usage of third party switches, I found these:

Using Third-Party Switches

You may try to implement Your driver by modifying the IVI driver for an NI SWITCH.

Creating or Modifying IVI Class Simulation Drivers

I hope these resources may help You.

Best Regards,

[petrz]

How the realy count functionality can be implemented? I can't find it in both IVI switch specification and driver atributes (im using CVI IVI switch driver template).

I'm can't found any information about relay status or count in given links.

[SachaE · Accepted solution]

Hi,

  you're referring to the listing underneat the switch executive virtual device where it brings up the Relay Information table for each selected switch unit.

Most of the NI switches have an onboard EEPROM which manages the list of switches and their count of interactions . The IVI driver for the NI hardware is niswitch, and the function to get the count back is niSwitch_GetRelayCount. 

Unfortunately, that's not an IVI-C standard call (more of an extension), so unless you try making that inside your DLL (following the IVI standard of the prefic name) then it's going to be limited to the way in which the NI hardware and it's API works.

Sorry

Thanks
Sacha