Switch executive 1.01 and MAX 4.1

Hi all,
I'm trying to install LabView 8.2, MAX 4.1 and Switch Executive 10.1 on one PC.
At one PC, where I constantly updated the versions, everything works fine.
On the new PC, I can not create new SE Devices in MAX.
The LabView VIs are functioning, SE is listed in MAX in "Software", but there just is no option to create a new SE Device.
What to do?
Thomas

Hi Thomas,
I know you might have tried this already, but just to verify, in MAX have you right-clicked on Device and Interfaces and selected Create New...? A window should appear and one of the options should be to create a NI Switch Executive Virtual Device, as shown in the attached picture.
If you're not getting this option, please attempt to uninstall and reinstall NI Switch Executive to see if that fixes the problem.
Hope this helps!
Chad Erickson
Switch Product Support Engineer
NI - USA
Attachments:
Create New.JPG ‏42 KB

Similar Messages

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

Why do I get "Evaluation Expired" message in MAX with Switch Executive

Why do I get �Evaluation Expired� message in MAX with Switch Executive on a PXI rack, which has a �Ghosted� image from and identical PXI rack(no problem with this PXI rack), when logged in as USER in Windows2000, but not when logged in as a Local Administrator. When logged in as Administrator in Windows2000 running a TestStand sequence, using a �C� code action step calling the nise.dll is ok, but not when logged in as local user. The alias switch name is unknown.

1.0.4.109 is a dll version number where as 1.0.2 is a NISE version number. The dll version number does not always line up with the product version number.
NISE 1.0 has a dll version of 1.0.1.109
NISE 1.0.1 has a dll version of 1.1.4.1
NISE 1.0.2 has a dll version of 1.2.4.7
NISE 2.0 has a dll version of 2.0.0.45154
The best way to find the product number is to launch the application and click on Help and About. You NISE version is probably 1.0 and NISE 1.0.2 will fix your licensing problem.

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

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

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 1.0.2 not appearing in NIMAX

Hi,
Switch Executive 1.0.2 is not appearing in NIMAX Deveices and Interfaces. Labview 7.1 and TestStand3.1 are the other software's installed. In the License manager also, NI switch executive is not listed.
Can somebody point me, what wrong could be going on?
Regards,
Papaiah Kummari

Hi Papaiah,
That is very interesting behavior. Does Switch Executive show up
under your "Software" tree in MAX? Also, does NI Switch Executive
show up under the list of NI Software when you go to Control Panel>>Add/Remove Programs and select National Instruments Software and click on Change?
Do you notice any difference if instead of opening MAX directly, you go to Start>>Programs>>National Instruments>>Switch Executive>>MAX with NI Switch Executive?
One thing to try would be to uninstall and reinstall NI Switch
Executive to see if this has any effect on the appearance of this
installer on your system. Let me know how this goes, as we
definitely want to make sure you get up and running with this software.
Have a great day!
Travis W

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

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

Hyp FR Error: 5200 : Error executing query. Exceed max row number 100000

Hi,
I am getting the error
5200 : Error executing query. Exceed max row number 100000
when I run the report on Financial Reporting. It gives the same error when run on Workspace.
Have you guys encountered this error before? What are the best ways to tackle it? Help is much appreciated guys.
-- Adi
Edit 1 - I tried to simplify the parameters but I still get the same error making me suspect that the issue is not the 100000 row issue.
Edited by: Aditya26 on Apr 11, 2012 9:02 AM

Hi Adi,
This is from My Oracle Support:
How to Increase Row Limit to Avoid Error "Exceed Max Row Number 100000" [ID 866832.1]
Modified 23-FEB-2012 Type HOWTO Status PUBLISHED
In this Document
Goal
Solution
Applies to:
Hyperion BI+ - Version: 9.3.1.0.00 to 11.1.1.3.00 - Release: 9.3 to 11.1
Information in this document applies to any platform.
Goal
How do you increase the maximum row limit to avoid the error "5200: Error executing query: Exceed max row number 100000"?
Solution
1.Edit \Hyperion\common\ADM\<version>\lib\ADM.properties as follows:
From MAX_ROW_NUMBERS=100000 to MAX_ROW_NUMBERS=500000
If you are running extremely large reports, you can increase the limit.
2.Restart Reporting and Analysis services.
For version 11.1.2.x
The path of ADM.properties file in these versions should be located under:
%Oracle_Home%\Middleware\EPMSystem11R1\commo\ADM\11.1.2.0\lib
Cheers,
Mehmet

/3 Gb switch, Windows Server 2003 and no imagecfg.exe!

The Imagecfg tool is not provided in the support toolkit for Windows Server 2003. How do I then implement the /3 Gb switch for oracle.exe and tnslsnr.exe as has been recommended in Metalink notes 116076.1 and 46001.1?
Also does this not appear a bit confusing:
Note 1036312.6 states:
On Windows NT Server, Enterprise Edition 4.0, Microsoft provides the 4GT (4GB
RAM Tuning) support so an application can utilize up to 3GB virtual memory
instead of the 2GB limit as it used to be.
The Windows NT service pack 3 provides the same feature but is not officially
claimed in the SP3 readme.txt.
The Oracle 8.0.3 release and higher have already been enabled to take
advantage of the new feature.
However a more recently updated note (46001.1) states:
d) Configuring the Oracle process to make allocations greater than 2GB
The Oracle database supports the 4GT tuning feature of Windows NT Server,
Enterprise Edition from release 7.3 onwards, allowing it to access up to 3GB
of virtual address space per instance. It may be the case that certain
releases / patch sets do not have the 4GT flag set even though the release
does support the feature. To check the executable has been correctly enabled
run :
imagecfg oracle.exe
oracle.exe contains the following configuration information:
Subsystem Version of 4.0
Image can handle large (>2GB) addresses
Stack Reserve Size: 0x100000
Stack Commit Size: 0x1000
For executables that do not have the flag set, run :
imagecfg -l oracle.exe
The above settings will only take affect if the boot.ini has been set up as
described in Note 46053.1.
So, do we really require to run the imagecfg utility (which is no longer provided in 2003 server support tool package) for versions higher than 8.1.7? Which tool should I then use instead of imagecfg for Windows Server 2003?

I think one of the reasons behind those Notes is that in older releases support for the feature existed and despite 7.3.4 or 8.0.3 and onwards had the capabilities, some patch sets or patches "forgot" this. The first Note you references says
"There may be a case where you are running 8.0.4.3.7 on NT and the 3gig address issue required the use of imagecfg to access the larger address space. One major reason might be the fact that patch sets may have brought in an executeable without the flag being set."
Sometimes it can be really hard to get notes on metalink to add upp, maybe mostly because there is so much info to maintain and cope with...
I dont think you should worry much about it. In any case, the developer/vendor who controls the code need to make sure the program is in reality large address aware and set flags accordingly.
If you want to check, to report something back to Oracle Support, there is dumpbin.exe to verify image header available in Visual Studio. Dont know of a public alternative.
http://msdn2.microsoft.com/en-us/library/c1h23y6c.aspx

How do I associate switches in a four layer relay tree using Switch Executive

I have a three layer relay tree, controlled with a PXI-2567, to route an instrument input to 16 DUT channels. How do I create aliases in Switch Executive to turn the appropriate set of three relays on and off to route the input signal to one of the channels?

Bob,
Here is what you need to do to be able to call 2 end channels and create a route though 3 layers.
1) You have to tell NISE how the independent relays are connected to each other. You will do that by creating Hardwires.
2) You need to tell NISE that you want the channels connected to the hardwires to be used for routing. You will do that by marking the connected channels as "Reserved for Routing".
3) You can name the end channels according to your topology. COM for the single input channel and CH0 to CH15 for the output channels by creating aliases.
In the route editor, you will only need to create a route between COM and CHx and NISE will find the appropriate relays to close. In the route editor, if you only want to see the channels with an alias (COM, CH0, CH1 etc...) select in Options "Hide channels without aliases"

Connecting two 1-wire channels to a 2-Wire channel in Switch Executive

I have a custom IVI 24x16 matrix and will be using the channels in groups of 2 and 4. I would like to connect these 2 and 4-wire signals to the AB0 and AB1 inputs of a PXI-2503 multiplexer. In Switch Executive all the signals of my matrix are characterized as 1-wire, but the PXI-2503 multiplexer inputs are characterized as 2 and 4-wire when in those respective modes. I can't figure out how to configure these as hardwires or buses so that Switch Executive will allow me to select one endpoint as the matrix and one as the multiplexer output.
-Andy

Andy,
At this time, Switch Executive does not have support for creating
routes that span channels with different wire modes. As a work around,
you could create routes for individual legs of a route that have
uniform wire mode, and then group them into route groups. This way you
will lose some of the auto-routing otherwise available to you when you
have uniform wire mode, but you will still have the flexibility of
having named routes in your application.
I hope this helps,
-Serge
Srdan Zirojevic

Switch executive 1.01 and MAX 4.1

Similar Messages

Maybe you are looking for