Route list in Switch Executive

How can I get (in LabVIEW) the list of the configured routes in Smy witch Executive session ?
Jean-Louis SCHRICKE
├ CTA - Certified TestStand Architect (2008 & 2010 & 2014)
├ CTD - Certified TestStand Developer (2004 & 2007)
└ CLD - Certified LabVIEW Developer (2003 & 2005)

There is a way of accessing the routes and route groups of a particular virtual device programaticaly. You will need to have session manager server installed.
1) Create an activeX session and connect to the session manager server 1.0.
2) Select "IInstrSessionMgr" for the Automation refnum
3) Enter your virtual device name in filter
4) Select "ReturnRouteGroups" or "ReturnRoutes" for Flags
5) Enter empty string in Category
6) Change the Variant to data (Array of string) to get the names of routes or route groups.
Regards
Attachments:
NISE_routes_and_route_groups.vi ‏71 KB

Similar Messages

Scan list using Switch Executive

I have a number of signal routes using multiple switch cards that I have set up using switch executive. I want to create a scan list that will switch each of my routes in turn each time I see a hardware trigger on the trigger inputs of my switches.
I have looked at some examples in TestStand and can see that if I use the IVI Switch Step using the IVI Switching setting that I can set up a scan list but that seems to be only for one switch card, I have two that I need to route signals to a Digitizer. I can not see a way of using my routes set up using Switch Executive.
I can either use LabView2013 or TestStand 2013 to do this.
Some help would be most appreciated?
Wayne

Hi Wayne,
If I have understood your problem correctly, this VI in LabVIEW sound like it does what you are after.
NI Switch Route Trigger Input
Also at the bottom of this LINK are some examples of scan lists, perhaps you will be able to adapt this to your needs
Please let me know how you get on
Kevin R
Applications Engineer
National Instruments UK&Ireland

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 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

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

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"

Is it possible to sort or filter the switch routes under the switching tab?

In Teststand 3.1, is it possible to filter the switch routes under the switching tab in Action Properties? Since I have a large amount of routes that have been created in Switch Executive, how can I filter out some of the routes from the "Routes to Connect" section?

The TestStand Switching does not provide any inherent filtering capabilities. You do have a couple of options, however.
(1) NI-Switch provides the ability to set up route connections in
different groups. The Switch Page in TestStand allows you to
select Routing groups as well as specific Routes. It may be
easier for you to organize your Connections as groups and choose
between different groups.
(2) The Property page also allows you to build route connection
string and use that string for your Switching actions. It
may be easier for you to build a Route string and easily change that
string rather than selecting your routes everytime from within the
TestStand window.
Good Luck!
Tyler T.
Applications Engineer
National Instruments

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

Route List

Hello everbody,
I have a route list which points to 3 route groups. Here's the order:
First one is a PRI in Boston (Primary), second is a T1 in Boston and the tired one is a PRI in New York. As Configured; when first PRI is not available the T1 has to kick in and when none of the links in Boston are available the PRI in New York has to take the charge. The links are working individually but when I unplug the PRI in Boston, we cannot make any calls. It looks like the switch over is not configured properly. Is there any configuration that I am missing? Where else de I need to look and configure in order to assure the failover?
Thanks,
BT

Also, one thing I noticed in the router config, you have dial-peer 101 pots configured, putting mcgpapp on the the PRI - the interop guide says you should not do this:
Restrictions for MGCP PRI Backhaul and T1 CAS Support
?Voice interfaces on the NM-HDA and the AIM-VOICE-30 are not supported.
?Integrated access, in which the channels on a T1 or E1 interface are divided between a group used for voice and another group used for WAN access, is not supported when voice is controlled by Cisco Unified CallManager through MGCP.
?T1 and E1 protocols, such as QSIG, E1 R2, T1 FGD, and PRI NFAS, are not supported with MGCP only with H.323.
?E1 CAS is not supported.
?Do not add the application mgcpapp command to dial peers that support PRI backhaul.
http://www.cisco.com/en/US/products/ps6441/products_configuration_guide_chapter09186a0080541bf5.html
That used to be generated when you downloaded the config from CM, and then it went away, and I know we put it back in a few places, but now they specify that you should not. I wonder if you removed that and did a ccm config check reset on the router to redownload config if it would behave better - that is, if you determine that it is really not unregistering.
Mary Beth

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

Switch Executive Libraries for LabVIEW 8.2

My company uses LabVIEW, TestStand, Switch Executive, and more. I'm in the process of setting up a new PC with LV8.2, TS3.5, and SE2.1. It seems, however, that this version of SE does not have libraries for LV8.2. There are directories on the CD for LV7.0, 7.1, and 8.0, but not 8.2. When I install, as expected, there is no option to get support for LV8.2-- only the other versions I listed. I need the nise.llb file but am not sure if I should just install the 8.0 version into my LabVIEW 8.2 directory. It just seems strange to me that the libraries for 8.2 are not there. Can someone please provide me some direction here?
I'm new here so please keep your responses at the "new college hire" level .
Thanks,
Greg

Hi TekGreg,
The attached file was written in the format of a KnowledgeBase document and details how you can use Switch Executive version 2.1 with LabVIEW 8.2. The workaround is simply to copy files from 8.0 to 8.2, but you want to make sure you copy them all. Let me know if you have further questions or if this does not resolve your issue!
Chad Erickson
Switch Product Support Engineer
NI - USA
Attachments:
Installing NI Switch Executive For LabVIEW 8.2.pdf ‏20 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

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

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

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

Route list in Switch Executive

Similar Messages

Maybe you are looking for