Switch Executive with SCXI "an error occurred while attempting to access device"

[LoquitoPollo]

I get "an error occurred while attempting to access device" when trying to validate or use the test panel for my current configuration:

PXI-1010 (PXI/SCXI combo chassis)

PXI-4060 in the PXI rightmost slot

SCXI-1129 in slot 1 of the SCXI portion

Clean install of all NI software (2012 DS1 developer suite) and a reset of MAX configuration data after not getting this resolved previously.

Because the SCXI-1129 is being controlled by the 4060 (legacy), I can't use DAQmx in NISE 3.5. So I'm stuck with IVI. I've configured everything in IVI so that I can at least add my device (SCXI_1129) into a new NISE virtual device. But when I go to validate or make a connection in the test panel within NISE, I get the above error.

Am I configuring something incorrectly?

[J-Barticus]

Hi LoquitoPollo,

On page 5 of the Getting Started Guide NI Switches it does not list the PXI-4060 as a usable switch controller. It does however list the following DMMs: 4021, 4065, or 407x. Below is a link to the document I mentioned.

http://www.ni.com/pdf/manuals/375471a.pdf

-Jake B.

[J-Barticus]

LoquitoPollo,

Under further investigation, although the PXI-4060 is not listed as a switch controller in the Getting Started Guide it should be able to communicate with the SCXI chassis in the PXI-1010. You should try going through procedure 3 in the guide to verify your hardware configuration. Additionally, I have provided below a link to a document regarding the configuration of an SCXI switch using Traditional DAQ.

http://zone.ni.com/reference/en-XX/help/375472F-01/switch/config_scxi/

-Jake B.

[LoquitoPollo]

Jake,

I'm glad you said it for me because I was trying to gather all the resources that indicated that it was possible. NI's documentation could definitely use some help. I feel like I have to piece together all the info I need. (I'm not trying to insult NI. I know from personal experience as I was in your shoes a few years ago.) Although I don't need handshaking, you could assume that the scenario with the PXI-4060 in the rightmost slot gives an indication it's possible--Can I do hardware Handshaking with a PXI-4060 and SCXI Switch in a Combo Chassis?

I can't find any right now, but I know I've seen other documents that actually said a 4060 was OK as a controller.

I still need help. I went through the steps and have things configured correctly in HW. I've also experimented with different SW settings to see what works and what doesn't because the documentation is misleading. For example, even though NI Switches Help >> Using NI Switches in IVI says the driver setup string is of the format topology:<topology name>;resourcetype:legacy, it's not. It's just <topology name>. Anything else will throw an error when adding the IVI device in NISE.

I know you'd rather not, but I also know you can, so would you be willing to set this up with a PXI-1010, PXI-4060 and whatever SCXI switch to see if you can successfully get a non-simulated validation in NISE? I've really come to the end of troubleshooting on my own. I've been at this all week and had other people jumping in too. I'll feel like a moron if it's something simple, but at this point that's better than continuing on with no results. My MAX report was attached in my first post so hopefully that can help with your configuration or to validate mine.

Thanks!

[Frank-L]

Loquito,

Have you tried verifying that your IVI configuration is working as expected? I would run/attempt to run the following code to verify that the device functions in IVI [outside of NISE]:

Do you have the error code that was thrown when you make an NISE device without the "legacy" setting? Do you have the error code that was thrown when you tried to used the "legacy" setting?

[LoquitoPollo]

Yes, my IVI configuration works as verified in Ivi Swtch - Path Operation Test.vi. My hardware seems to check out fine when I use niSwitch Controlling a Individual Relay.vi. I just can't seem to get it to validate in NISE.

By the way, I finally got a fresh machine and installed the 2012 DS1 developer suite from scratch and we get the same issue. I know it's gotta be something small I'm missing, but I've tried to verify everything involved piece by piece and getting it to work in NISE seems to be the last piece.

Resource Descriptor in the Driver Session -- "SCXI1::1" -- I used a VI to retrieve the property and that's what I get.

Driver Setup string -- "1129/2-Wire Quad 4x16 Matrix" -- even though Using NI Switches in IVI indicates it's "topology:1127/2-Wire 32x1 Mux;resourcetype:legacy" (which causes errors).

The attached MAX report can be used to see everything else on the system.

If I were new to NI and found these different documents, how would I know what's supposed to work in my scenario?

NI Switches Getting Started Guide (page 5) - (4021, 4065, 407x, USB, E/M Series)

Configuring an SCXI Switch - (407x, M, USB)

Can the PXI-40xx be Used to Control SCXI in a Combo Chassis? - (Non-PXIe 407x, NO 4065, YES 4060 - but why not recommended in the 1010 chassis?)

Can I Do Hardware Handhaking with a PXI-4060 and SCXI Switch in a Combo Chassis? ("...PXI 4060 and it is installed in the right-most slot of an SCXI combo chassis...")

My production line is down. Can you please re-create this on your end to verify you can get it to work? I see no further value occupying the time of either one of us unless you can first get this to work because we need to know it's possible. Then we can try to pinpoint the issue. I've done so much troubleshooting it would take a long time to regurgitate it all here, and I don't want documentation to be used to brush me off (because it's obviously not conclusive).

[Frank-L]

Loquito,

Using this "1129/2-Wire Quad 4x16 Matrix" as the Driver Setup does not allow the device to be added to a NI Switch Executive virtual device.

Using "topology:1129/2-Wire Quad 4x16 Matrix;resourcetype:legacy" does NOT result in that same error, and validation works as expected [When using the "Simulate With" in the IVI Driver Session].

• Can you export and upload you IVI configuration file so that we can confirm everything is set up correctly?
• Can you confirm that these errors occur on a new NISE virtual device? Does validation work when you check "Use Simulation Mode"? 
• Can you upload a screenshot of the errors that you are getting? We still do not know exactly what errors you are getting.
• What specific "Items to Validate" does the device fail on?
• You mentioned that your production line is down. Did something change that caused this new failure? Why are you adding hardware / creating new virtual devices? Are you trying to restore a previous image?

If your production line is indeed down, using the discussion forums may NOT be the best course of action and I would call 1-866-ASK-MYNI to talk to a support engineer ASAP.

[LoquitoPollo]

Frank, Thanks for continuing to look at this issue. Here are my responses to your questions. 1) You get an error when your driver setup string in in the General tab of your Driver Sessions is "1129/2-Wire Quad 4x16 Matrix"? Are you using a PXI-4060 in the right-most slot of a combo chassis. If you're using a DAQmx device, it's a whole different ball game. If you're not using a PXI-1010 combo chassis, it's a different story too. 2) I can't seem to find a way to cleanly export my IVI configuration files. Even the VI you wrote (Programmatically Export All Virtual Devices & IVI Configurations for NI Switch Executive) didn't copy the IviConfigurationStore files. So I manually copied them over and attached them. When I create my driver session, I type 3 things: the topology ("1129/2-Wire Quad 4x16 Matrix") in the driver setup string, "SCXI-1129" and "SCXI1::1" in the hardware tab (It would be "SCXI0::1" if the dip switches on the PXI-1010 were set to address 0, which is the default), and niSwitch in the software tab for the software module. 3) The error I'm getting is the name of the post. "An error occurred while attempting to access device". It get this when validating my NISE virtual device when simulation is not checked. It's also peachy-keen for me when I simulate. 4) See the screenshot. 5) Production line down is par for the course for this lab due to how many people have messed with this station in an effort to bandage it over the years to keep product flowing. Long story, but there has one problem after another on this machine for a while with no owner. I'm now responsible for the automated tests on it. I'm adding new devices because I'm essentially starting from scratch so I know what's going on and can trust it. But apparently I'm either getting the same error they had before or it's a new one. I suspect it's the same one but it "used to work". I had another coworking here yesterday and he opened a phone SR, gave the information, and was told they'd get back to him. I haven't heard anything yet.

[MaggieAggie]

I am working with Frank and we have set up the system and recreated your errors. We are still working on a solution. 

[LoquitoPollo]

Thanks for working on it and thanks for the update.