Switch Hardware and Software

cancel
Showing results for 
Search instead for 
Did you mean: 

VI "niSE Connect" connects route although returning exclusion conflict (error -29032)

Hi,

 

I am playing around with the NISE examples and VIs on a system running

- LabVIEW 2010 SP 1

- SwitchExecutive 3.50.49154

with a PXI-2535 matrix.

 

I've created a new SE virtual device, provided some channels and routes and also (mutual) exclusions between some of the channels. I wanted to try out what happens when trying do make some connections which must not be made due to the programmed exclusions.

 

  1. In a first test, I used "niSE Find Route.vi" followed by "niSE Connect.vi". Connect is only executed when Find Route returns Path Available using the returned route specification. Everything works as expected, I get exclusion conflicts and don't do connections in that case. Fine.
  2. In a second step, I called "niSE Connect.vi" twice using two conflicting routes. The 2nd call to Connect does correctly return error -29032 "Connecting this route would cause excluded channels to be shorted together. Route Channels:a,b and Exclusion Channels:b". However, this 2nd connection is made! (verified by reading back the switch status in the Switch Soft Front Panel showing the connections of both routes closed). The work around is easy: I use approach 1 and forget about the routes. Anyhow, I guess this behaviour is not expected?

 

Best regards

Uli

 

0 Kudos
Message 1 of 6
(5,112 Views)

Hi Uli

 

This error 29032 usually comes up if an exclusion was set for a particular connection set in Switch Executive. There are a number of reasons why you would want to do this, but I would suggest making sure these particular exclusions are not set.

 

Error Codes

 

Switch Executive and Exclusions with Single Pole Double Throw Relays

 

 

Error -29032 Connecting this route would cause excluded channels to be shorted together.


It is typically expected behavior to get an error when trying to connect a channel to itself. Usually that error shows up as error -29035: CANNOT_CONNECT_TO_ITSELF. Basically connecting a device to itself is not something that is possible with Switch Executive.

 

Perhaps you had some other scan channels connected at the time of the failure ?

 

Regards

Pixar

 

 

 

0 Kudos
Message 2 of 6
(5,102 Views)

Hi Pixar,

 

thanks for your reply. I've understood the reason for using exclusions in Switch Executive as this is exactly what I'll need in my application. Getting error 29032 is not the issue. The problem is that the VI is doing the connection despite the fact that it returns the error.

 

Suppose there are 3 channels c0, c1, c2 and 2 defined routes

  • A = c0->r0->c1
  • B = c0->r0->c2

In addition, c1 and c2 are defined to be mutual exclusive.

Now, I call "ni SE Connect" for route A which closes relays for columns c0 and c1.

Then, calling the same VI for route B will return error -29032 but nevertheless close the c2 relay! At the end, all 3 relays c0..2 are closed at the same time! This is what I suspect to be not okay.

 

Best regards

Uli

 

 

0 Kudos
Message 3 of 6
(5,093 Views)

Hi Uli,

 

We tried reproducing this internally and were not able to.  We correctly got the error and the connection was not made.

 

In order for us to try to reproduce this here more exactly:

1. What version of the NI-Switch driver is installed?

2. What version of NI-DAQmx is installed?

3. Please post an export of your NISE configuration

4. Please post a copy of your MAX Data Folder (zipped) (found at C:\ProgramData\National Instruments\MAX\Data on Win7).  This will allow us to run the test again with your full system configuration. 

5. Where are you checking that the connection to c2 is being made? Is it appearing closed in the Switch Soft Front Panel, or are you testing the physical connecton itself?

 

Regards,

 

Eric S.
AE Specialist | Global Support
National Instruments
0 Kudos
Message 4 of 6
(5,088 Views)

Hi Eric,

 

when I was initially adding this post I could only use the Switch Soft Front Panel to check connections. Meanwhile I have a break-out solution so I wanted to get back to this since I supposed your question 5.

> 5. Where are you checking that the connection to c2 is being made? Is it appearing closed in the Switch Soft Front Panel, or are you testing the physical connecton itself?

could be a good candidate to identify the problem on my side. So I reran the VI I used before (the NISE configuration has also not been changed since that), got the error -29032 and started checking the Front Panel...
But: this time the connection was really not made. Everything is working as expected!

 

Although I know I've seen it on the Soft Front Panel several times, I am not capable to reproduce it now. No program or driver updates, no NISE configuration change...

 

I therefore consider this topic closed (as long as I am not able to reproduce the phenomenon again). Sorry for any inconvenience and trouble this might have caused!

 

Regards

Uli

 

0 Kudos
Message 5 of 6
(5,074 Views)

Hey Uli,

 

Thanks for posting back, and I'm glad to hear everything is working as expected now.  If you ever see this phenomenon again, where a route exclusion is not honored and the connection is made, please let NI know.  If that were to ever happen it would be a large safety concern and we need to be aware of it.

 

Thanks,

Eric S.
AE Specialist | Global Support
National Instruments
0 Kudos
Message 6 of 6
(5,068 Views)