Switch Executive Setup error

When I Install NI Switch Executive 2.1,it report the following error,I do not know why.
Structured Exception number 0xC0000005
Exception code: C0000005 (ACCESS_VIOLATION)
Fault address: C4830003 117E60C:0000000E
Registers:
EAX:02F0277C
EBX:0117F9C0
ECX:0046007B
EDX:7C923804
ESI:00000001
EDI:00539208
CS:EIP:001BC4830003
SS:ESP:00230117E9F8 EBP:0117F9CC
DS:0023 ES:0023 FS:003B GS:0000
Flags:00010202
Stack Trace
Address Frame LogicalAddr Module SymbolName + Offset
C4830003 0117E9F4 0000:00000000
0042B20C 0117F9CC 0001:0002A20C F:\distribution\setup.exe
004232DD 0117FBD0 0001:000222DD F:\distribution\setup.exe
004226BF 0117FCC8 0001:000216BF F:\distribution\setup.exe
0046AE02 0117FD74 0001:00069E02 F:\distribution\setup.exe
0046AEF8 0117FD9C 0001:00069EF8 F:\distribution\setup.exe
004732D1 0117FDE4 0001:000722D1 F:\distribution\setup.exe
0047338E 0117FF18 0001:0007238E F:\distribution\setup.exe
004F8939 0117FF80 0001:000F7939 F:\distribution\setup.exe
004D81DE 0117FFB4 0001:000D71DE F:\distribution\setup.exe
7C80B683 0117FFEC 0001:0000A683 C:\WINDOWS\system32\kernel32.dll GetModuleFileNameA + 436
Attachments:
Switch Executive Error.jpg ‏31 KB

Hi yiweihua,
I apologize for the delay in providing a reply to your last post. Can you attempt updating your installer to the newest setup.exe? I've attached the two needed files in mif24.zip. The procedure is to replace setup.exe and NISysInf.dll in your distribution with these newer parts, and then try again. Please acquire the specific error message if another one appears during this updated installation.
Thanks!
Chad Erickson
Switch Product Support Engineer
NI - USA
Attachments:
mif_24.zip ‏1000 KB

Similar Messages

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

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?
Attachments:
max_report.zip ‏93 KB

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.
Attachments:
IVI export.zip ‏34 KB
SCXI-1129 adding to NISE.JPG ‏36 KB

NI Switch Executive error when attempting to add NI PXI-2566 switch to new virtual device.

I just loaded Switch Executive and am wanted to explore its capabilities. I have a PXI system that I am setting up. Currently I have PXI-2566 cards in slots 8 and 9.
I was following the NI Switch Executive help documentation "Creating a Virtual Device" and attempted to create a virtual device with the 2566 modules and I got this error;
Error xBFFA000A occurred.
Failure loading driver module.
The driver for the DAQmx switch is not loaded.[DeviceXI1Slot9_ivi]
Attachments:
SwitchExecutiveError_01.bmp ‏229 KB
SwitchExecutiveError_MAX.bmp ‏364 KB

I had not loaded the "NI-DAQ 7" software that came with the 2566 switch card. I assumed that since MAX showed that I had version 7.2 of DAQmx that I was already up to date.
I received a new PXI-2532 switch, and when I got a "driver not found" error in Switch Executive when I tried to add the 2532 to a new virtual device, I had second thoughts on running the setup/install from the new discs.
After running the software install, I was able to add the 2566 switches to a virtual device in Switch Executive. However, the 2532 failed.
Error xBFFA4B4A occurred.
DAQmx Error -200181 occurred:
Channel name specified is not valid for the switch device.
Device: PXI1Slot10
Channel Name: r4
Attachments:
SwitchExecutiveError_02.bmp ‏35 KB

Switch Executive Error -1074130544

An operation is getting the following error when attempting to make a NISE connection. He is running a sequence in TestStand 4.0 and using the switching properties of the step. This is the first switching operation in the test sequence.
An error occurred while performing the switch operation 'Connect' for the following device '265869_T45_LED_Driver'. Could not perform the switching operation: Details: (IVI Error Code: BFFA1190) [Device: NI_PXI-2532_ivi](Error = -1074130544) [Error Code: -17500, Operation Failed.]
I cannot find any information on any of the above error codes. What exactly does this error relate to?
I am using TestStand 4.0, and NISE 2.11
Thanks,
Paul Holzrichter

Hey kwseitz3 and Paul,
After doing some more testing on
our end, we believe that this might be a separate bug and would thus
warrant a separate CAR to be filed. Do you still have the NI Spy
captures from: 1. using Reset and 2. using Single Pass? You also
mentioned that it worked just fine when you ran your test without
hardware so it would also be helpful if you could get us NI Spy
captures for Reset and Single Pass for this scenario as well.
One last piece of the puzzle that would help us would be your Switch
Executive and IVI configuration information. For Switch Executive you
could just export your configuration from MAX and for IVI you can copy
the IVI configuration store file. Both of these should be .XML files.
NISE Configuration: In MAX, right-click Switch Executive Virtual Device, select Export. Send this file.
IVI Configuration: Click on IVI Drivers to find the Master IVI
Configuration Store Location. Send the IviConfigurationStore.xml file.
I went ahead and attached screenshots of where you can grab these files.
Do you think either of you could get us these files so we can further isolate the
cause of this issue?
Attachments:
NISE Configuration.JPG ‏65 KB
IVI Configuration.JPG ‏49 KB

Switch Executive error: -1074126826

The following error occasionally occurs when executing a Disconnect All TestStand step, Switch Executive:"Filename",Connect/Disconnect.
I Need a solution
Error, Error executing substep 'Post'. An error occurred calling 'RunStep' in 'ISubstep' of 'TestStand Ivi Step Types' An error occurred while executing the step. Unexpected Error: Switch Executive failed to initialize for virtual device 'NLAWQAT_Rev01'. Details: NLAWQAT_Rev01_init returned an error: -1074126826 (0x%3). Source: TSIviStepTypes [Error Code: -1074126826, User-defined error code.]

Hi Ken,
does this occur if this switch is simulated too?
That error can sometimes point to a timeout error in trying to connect to the device itself.
Is there anything else going on at that point?
Does it occur even if you step your way through the sequence?
Does it ever occur on a cut down sequence?
You say a "Disconnect All" step. Do you mean you have a step type that does this (i.e. the IVI-C switch step type) or you have this set on the switching tab of another step type (i.e. using switch executive)?
What version of TestStand are you using?
What is the model and manufacturer of the switch? Can you provide the driver install for that switch?
Does it happen in the sequence editor, the operator interface or both? If both, which one does it happen in more?
Which IVI compliance package do you have installed, and what's your version of VISA.
Any other information you think is pertinent would also help.
Thanks
Sacha Emery
National Instruments (UK)
// it takes almost no time to rate an answer

Driver Setup for PXI 2569 and PXI 2529 in Switch executive

Hi,
What sould be tha "Driver Setup" for PXI 2569 and PXI 2529 in Switch executive under 'Driver Session"
Regards!!!
Vineet Shukla

Hi Vineet,
You do not need to insert anything under Driver Setup. Anytime you are using NI switches, you can simply click Configure NI Switches when creating a NI Switch Executive Virtual Device to configure the topology settings of those switches.
Just so you know, you can insert information under Driver Setup, and then you wouldn't have to use the Configure NI Switches wizard. More detail on what to insert under Driver Setup can be found in the following KnowledgeBase:
How Do I Create a Virtual Switch and Use it in my Application?
http://digital.ni.com/public.nsf/websearch/A1F0D6A3357E14B386256E4B0071FDA2?OpenDocument
In short, you would type "Topology:" followed by the topology name such as "2569/100-SPST" or "2529/2-Wire 4x32 Matrix".
Let me know if you have further questions or if this does not resolve your issue!
Chad Erickson
Switch Product Support Engineer
NI - USA

Cannot connect to com1 in PXI2530 using Switch Executive

I have a PXI2530 configured using Switch Executive 2.10. The first 60 Channels are setup with my signal names on ch0 - ch59. Com0, 1, 2 and 3 are my Instrument connections. The IVI Driver Sessions has Driver Setup set to Topology:2530/1-Wire Octal 16x1 Mux.
When I try to configure either a Channel, Route or a Group, there is only a com0 pin and no com1, 2, 3, 4, 5, 6 or 7. There is no way to connect to any pin beyond ch15.
The configuration looks like it is setup for a 128:1 mux, but when I try to connect ch16 to com0, it cannot complete the route. Ch16 cannot be connected to com0 or any channel in the list. Any idea what I am doing wrong?
Michael Munroe, ABCDEF
Certified LabVIEW Developer, MCP
Find and fix bad VI Properties with Property Inspector

http://forums.ni.com/ni/board/message?board.id=320&message.id=633
Duplicate threadMessage Edited by Berto on 02-28-2006 12:15 PM

Switch executive stops working after labview 2009 installation

Hi, After I've installed labview 2009 my old switch executive virtual device routes stop working in such a way even if I try to set a route from switch executive test panel the attached error message pops up.
I am using:
Labview 9.0.1
TestStand 4.2.1
Switch Executive 4.6.2
Many Thanks in advance
Mehran Fard
Mehran Fard
Attachments:
niSE.png ‏11 KB

Hi Fardm,
I might try doing a repair on LabVIEW, TestStand and Switch as it sounds like a dll might have become corrupt.
Kind Regards,
Owen.S
Applications Engineer
National Instruments

Can't execute setup.exe on PDA

hi, i'm testing simple example with Oracle817 and 9i lite database..
my problem is that i can't execute setup.exe on my PDA...
i packaged new application by only importing scott.emp tabale with wtgpack.exe
then i set user priviledge and parameter in the mobile server control center web page..
i downloaded mobile client for wince on strong arm cpu...
while i packaged mobile application there was no exception or error messages..
but i can't execute downloaded setup.exe file for installing mobile client.. though..
only it's not proper wince application sign can be seen on PDA..
PDA that i use is with strong arm sa-1100 cpu and windows CE 3.0(build 126)..
but it's not compaq or any other well known product though..
anyway.. anyone had this kinda situation..?
please help me out..
thank your in advance..

When I turned my computer on I had the setup.exe shortcut on my desktop (0 bytes), and can't delete it.
good lord. this is precisely the second time i've ever seen this reported. (the other chap i saw with this ended up with two such icons on his desktop, if i remember correctly.)
Katrina: am i remembering this correctly?
what eventually worked for him was downloading and installing a copy of Pocket Killbox, which he eventually managed to use to get rid of the beasts.
keep us posted.
love, b

Setup Error message in Query Designer

Hi all,
I have built a BW IP query with an aggregate as infoprovidor. In order to make the query plannable I have to use all KF and Characteristic and set the correct filtervalues. I have executed this specific query many times in order to check if all rows/columns are filled ok and are plannable but the last time I executed the query the following error message popped up :
"Setup Error Failed to load resources from resource file. Please check your setup"
When I click OK the Query Designer shuts down. When I then start the Query Designer again and want to select my query the same error message appears so I cannot access my query anymore.
I am going to built a new one but like to know the probable cause of this error message as my query was consistent for sure.
Thanks!
Raymond Flaton

Did you find a solution to this? we are having the same issue

How can Teststand have Switch Executive dynamically change a route.

I have created routes in Switch Executive and when I try to connect these routes thru Teststand via Action Properties under the Switching Tab. I get an error saying:
Details:A reserved for routing channel required for connecting this route is already in use by another route.(Error = -29031) [Error Code: -17500, Operation Failed.]
I am trying to connect two different routes by the following syntax in the "Routes to Connect" section:
"Route1 & Route2"
It seems that in Switch Executive Route1 and Route2 are both using the same reserved for routing paths. For example:
Route1:      [C0->MatrixA/r1->C2]
Route2:      [C1->MatrixA/r1->C5]
So my question is then...How can Teststand make Switch Executive change the route path? I have r0, r1, r2, and r3 set as reserved for routing. Thanks for your help.

Thanks for your help.
For situation 1:
When I use this method Switch Executive dynamically chooses a route but its always the same route.   What I need to do is have a set of pins that use only one route and another set of pins that uses a different set of routes. You can think of it as c1 is one lead of a multimeter and c2 is the other lead. I need to be able to connect c1 on any other column besides c2 and also c2 to be able to connect to any other pin besides c1. Since in Teststand I need to connect c1 and c2 simultaneously as a step I get an error because both are trying to use the same route.
Also when I change the route from:
                                                         channelA->matrix/r0->channelB
                                                     to: channelA->matrix/r1->channelB,
then when I save and close Switch Executive and I reopen it the channels automatically routes itself back to channelA->matrix/r0->channelB.
Is there any way that I can save these routes to my configured route?

Cannot connect to com1 using Switch Executive

I have a PXI2530 configured using Switch Executive 2.10. The first 60 Channels are setup with my signal names on ch0 - ch59. Com0, 1, 2 and 3 are my Instrument connections. The IVI Driver Sessions has Driver Setup set to Topology:2530/1-Wire Octal 16x1 Mux.
When I try to configure either a Channel, Route or a Group, there is only a com0 pin and no com1, 2, 3, 4, 5, 6 or 7. There is no way to connect to any pin beyond ch15.
The configuration looks like it is setup for a 128:1 mux, but when I try to connect ch16 to com0, it cannot complete the route. Ch16 cannot be connected to com0 or any channel in the list. Any idea what I am doing wrong?
Michael Munroe, ABCDEF
Certified LabVIEW Developer, MCP
Find and fix bad VI Properties with Property Inspector

Michael,
What probably happened is that originally the NISE vd was created using the 128x1 topology. If the driver session is changed to another topology (like Octal 16x1 Mux) and saved the linked from the NISE vd and the old topology still exists until you close MAX and reopen it. When MAx opens it establishes a link between the NISE vd and driver session which remains in memory until MAX is closed and reopened.
Guy Ferraro
Switch Product Support Engineer
NI - USA

Switch Executive 2.0 and Deployment 3.0

I have Switch Executive 2.0 on my development computer producing the exported [switch].XML file.
Are there any problems or issues with importing this switch configuration file into
NI-Switch deployment version 3.0?
Background:A previous project using 2.0 into a 2.0 deployment worked fine.
Now my attempt to deploy into a deployment computer with a recently purchased NI-Switch deployment 3.0
does not configure the same switches properly.
The switch configuration Validation process does not work. It gives a cannot find IVI switches errors.
Scott Youngren

Hi Scott,
This error is common when the IVI configuration does not match on the development and deployment machine.
1. On the deployment machine, verify the IviConfigurationStore.xml file has been copied to the correct location.
The IVI Configuration Store XML file includes the IVI Logical Names and Driver Sessions information that can be seen in MAX.  With IVI Compliance Package 2.1.2 (which is installed with NI Switch Executive 2.0):
C:\Program Files\IVI\Data\IviConfigurationStore.xml
With IVI Compliance Package 3.2 (which is installed with NI Switch Executive 3.0):
C:\Documents and Settings\All Users\Application Data\IVI Foundation\IVI\IviConfigurationStore.xml
2. If you are using NI switches, then additionally verify the DAQmx device names in MAX (under Devices and Interfaces) match on the development and deployment machine.
Each IVI Driver Session configures a hardware asset, and the hardware asset is basically a pointer to the DAQmx Resource Descriptor (also known as a DAQmx device name). If the listed Resource Descriptors shown on the hardware tab of the IVI Driver Sessions do not match the DAQmx device names under Devices and Interfaces, you will get an error.
Let me know if this does not resolve your issue!
Chad Erickson
Switch Product Support Engineer
NI - USA

Conflict using simultaneously IVI Switch and Switch Executive ?

Hi,
I use IVI Switch and Switch Executive libraries in an Labwindows CVI project, and I meet some problems :
I call SE lib for InitSession/CloseSession/FindRoute and Connect/Disconnect (apply to any switch devices in the SE configuration).
I call IVI Switch lib for SelfTest and Reset (apply to a single device).
But when I do an IVI Switch Reset then a Switch Executive Connect or Disconnect, an error occurs : Switch Executive seems to ignore what IVI Switch operations do to the device ?
Also, can you tell me if :
niSE_OpenSession performs a self test for the devices in the config ? A reset ?
niSE_CloseSession performs a reset for the devices in the config ?
Thanks.

Hello,
the niSE session talks to underlying IVI drivers using the IVI Switch session underneath, so any additional opening of IVI Switch session to the same device will cause the two driver sessions (that keep the information about the state of the hardware connections) to be either one or both out of synch with the actual hardware state). Because of the architecture of the underlying IVI drivers, niSE session cannot know if and what someone did to the instrument using IVI Switch session.
Therefore, it is not adviseable to use IVI Switch session while having another session open to the same device. If you need to use the invasive operations - which is anything that changes the state of the device, such as Reset and possibly self-test (self-test may be implemented as an operation that cycles relays and it may not but you can't be sure), you must make sure that one session is open and closed before another type of session is open.
The ni Switch Executive Open Session calls IviSwtch_init (with ID Query and Reset set to true) and CloseSession closes the IVI Switch sessions with the call to Close. The niSE session does not make calls to either reset or self-test explicitly.
Always attempt to perform all the operations on the same piece of hardware using the same API. If you need to reset switches, use the niSE_DisconnectAll function. If you need to perform the self-test operation, open a session to IVI Switch and perform the self-test, and then close it before opening the session to niSE virtual device.
There is also a back-door possibility that you can obtain the IVI Switch session that has been open for the constituent devices by niSE, but you must make sure that whatever you do with that session leaves the state of the switch intact when you get back to making calls to the niSE session. If unsure, you can always call niSE_DisconnectAll() as the first thing coming back to the niSE session to ensure that the state stored in niSE session matches the state on the actual hardware.
Again, it is best not to use both sessions, but rather pick one and try to perform all operations with it before switching to another type of session.
Srdan Zirojevic

Update Switch Configuration from Switch Executive 2.1 to 3.5

Hi everybody,
I tried to update from Switch Executive 2.1 to 3.5 and had to find out, that my configurations have stoppped working. To me, it looks like 3.5 doesn't like my IVI configuration for the switching modules.
The Verify function in MAX tells me that the PXI cards are not accessible. The frontpage of the switch configuration shows no configurations / terminal blocks.
Since the configuration consists of nine matrix cards with a lot of hardwires, I'd really appreciate a way to properly import the old configurations (xml files are available)
Any ideas?
Cheers
Oli
Programming languages don't create bad code, programmers create bad code....
Solved!
Go to Solution.

Hey Oli,
Background:
By default, NISE 3.5 and later use the DAQmx API (instead of IVI) to directly control switch modules. This is different from previous versions, which required setting up an IVI session for each NI Switch module. You can still use IVI with NI Switch modules in NISE 3.5 and later, but this is not the default behavior.
The KB Sebastian referenced lists three different upgrade paths to use exported IVI Virtual devices in NISE 3.5 and later. As you've discovered, NISE 2.1 has fewer export formats, so we'll need to take the following steps:
Assumptions:
You have virtual devices created in NISE 2.1 (file format doesn't matter).
IVI Sessions and Logical names haven't been setup on your NISE 3.5 machine:
Action items:
Create IVI sessions and logical names. You could manually create the IVI sessions (as mentioned in the KB), but there's a MUCH easier method:
Right click on the NISE Virtual Devices tab and select 'Create New':
Click the 'auto create IVI devices' button. A dialogue will pop up... just click yes:
The NISE Create Virtual device window should now look like this:
Notice that we now have IVI devices. Sweet! So now just click cancel (yes, cancel)... we only used this dummy virtual device to simplify the IVI creation process.
If you look in MAX, it'll appear as if there still aren't any IVI devices:
Fear not, all we need to do is refresh. To do this, hit F5, and voila!:
So now all you need to do is change the IVI Logical name to whatever your old IVI Logical name was and then import as normal.
At this point, you should be operational using IVI devices in NISE 3.5 (if not, post up). If you'd like to go one step further and upgrade to purely DAQmx calls, just follow the steps in the 'Upgrading from IVI to NI-DAQmx' section. Note that once you've upgraded to DAQmx, you'll only be able to use exported Virtual devices with NISE 3.5 and later.
Have a great day!
-John Sullivan
Analog Engineer

Switch Executive Setup error

Similar Messages

Maybe you are looking for