NI Switch Executive 3.0 Validation Error

[pgstein]

Hi,

I am trying to import a ivi configuration file and a Switch Executive configuration file into the Switch Executive.

The problem I am having is that everytime I go to Validate (in simulation mode) the configuration, I recieve:

"An error has occurred while attempting to access device PXI1Slot2_ivi_2"

I am by no means an expert on this.  Would somebody be able to take a quick look and see what I am doing wrong?

Another developer wrote both files. I have attached both files.

Thanks in advance,

Paul

IVI Compliance Package 4.0

Switch Executive 3.0

[enderWiggin10]

Hi pgstein,

Here is a great KnowledgeBase article dsicussing importing IVI Configurations, as well as a KnowledgeBase article for an error similar to this.

It appears that the configuration is looking for a device by the name of "PXI1Slot2_ivi_2"  Do you have a Logical name for this in MAX under your IVI Drivers section? If you do have a logical name for this, is the appropriate driver session selected? Perhaps a screen shot of your IVI drivres section in MAX, fully expanded, would provide more insight.  How are you importing the files from your old machine into the new MAX?

Best,

[Vishal_Chopra]

Adam,

I am working with Paul G. on this.

The links you sent are useful but I am already complying with those requirements.

I am comfortable with NISE and IVI but can't wrap my head around the fact that I am importing the IVI driver and NISE xml files correctly and replace the file IVIConfigurationStore.xml

in the IVI sub-folder correctly, but my Validation still fails.

The only error I am getting is exactly the same as in article:

http://forums.ni.com/t5/Switch-Hardware-and-Software/NI-Switch-Executive-generating-errors-during-va...

But the problem still persists even after re-installing NISE per the above article's advice.

What basic thing could we be missing?

Vishal

[enderWiggin10]

Hi Vishal,

Are you currently using NI Switches or 3rd party Switches? 

-For NI Switches, what is the switch and can you open the test panels for the device by right clicking on the device in MAX under Devices and Interfaces and then seelcting Test Panels?  Try opening and closing the switch.  Do you get any errors?

--->If No Errors, then see if you can open a shipping examples for NI-Switch.  Open LabVIEW and Select Help»Find Examples»Hardware IO»Modular Instruments»NI-Switch»...  and see if you can configure and run and make connecitons on the switch.

-For non-NI switches, can you validate the hardware driver is installed and is functioning?

Further, can you run NI Spy while trying to validate the switch?  Also, if it is an NI Switch, can you walk through making a completely new and seperate NISE Virtual Device while NI Spy is running?

Thank you,

[Vishal_Chopra]

Hi Adam,

We are using NI PXI-2567 for our switching.

Please find attached every screen shot of the way a new virtual device is created with one simple Route (Ch0 to COM0).

Also included is the NI Spy file with some errors I came across while trying to make this simple connection above through the test panel.

However, I can make this connection successfully through the NI DAQMx Soft Panel for PXI-2567 but when I go through NISE, it gives me the error shown in the screenshot in the zip file.

We have the NI PXI-2567 hardwired and we are using MXI-4 for controlling the PXI chassis.

I wonder if I am failing to set something prior to making a virtual device for this to fail to access the device (PXI-2567 in Slot 2 of the chassis)?

Please review the information attached and let us know if you have any insights,

Thanking you again.

Vishal

[enderWiggin10]

This post is to clarify the solution to the issue.

We were able to track the issue to be a problem with the NI SwitchExecutive of NI-Switch driver software.  The problem was persistent even with simulated hardware.  Vishal could run the NI Switch Soft Front Panel without any issues, but when attempting to run the test panles in NISE or validate the device, the error would occur.

The software was as follows:

NI DAQmx 8.9.5

MAX 4.7

NI SwEx 3.5.0

NI-Switch 3.8.5

TDAQ 7.4.4

VISA 5.0.2

Vishal already reinstalled the NI SwEx environment proactively based on a similar discussion post to his initial issue.  This did not resolve the issue.  Therefore he installed the latest version of NI-Switch driver, 4.1.  After doing so, this resolved the issue.