Switch Hardware and Software

cancel
Showing results for 
Search instead for 
Did you mean: 

Switch Executive stores wrong Multiconnect Mode default value

In my last project I wondered why all routes suddenly had a "Multiconnect Routes" mode, while I could not remember having entered that value deliberately. I put this down to some stupid mistake on my side and then converted all routes back to "No Multiconnect" mode. Everything was fine after that.


Now I have started work on a new NISE Virtual Device and the same thing happens again:

Whenever I create a new route the default mode shown on the Switch Executive frontpanel is "No Multiconnect" Smiley Happy.
If I do NOT change that default and save the configuration, the value actually writen to disk is "Multiconnect Routes" Smiley Mad.
I can see that by reverting to the saved configuration in MAX or by reading it into an EXCEL Table.

If however (after creation) I change the mode to "Multiconnect Routes" and then back to "No Multiconnect" before saving, the correct value is stored.


Is there any other - less tedious and error prone -  way to change or circumvent this "bad behaviour" ?

Anke

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

Hi Anke,

You have identified a problem with the NI Switch Executive GUI in MAX.  On the Routes/Groups tab, Multiconnect Mode has two selectable options from the pull-down menu:

1.  No Multiconnect
2.  Multiconnect Routes

Upon creating a new route, the default option in the Multiconnect Mode pull-down menu is shown to be No Multiconnect.  However, in actuality, NI Switch Executive creates routes with the Multiconnect Routes option (not apparent to a user).  When you Save and Revert, the actual configuration (Multiconnect Routes) is displayed.  We plan to fix this in the next revision of NI Switch Executive.

For now, as a workaround, you have a few options.

1.  Upon creating each route, change the Multiconnect Mode to Multiconnect Routes and then back to No Multiconnect.  You have to change the mode to write to the configuration.  This option should only be chosen if there are a small number of routes that need their modes changed.

2.  Finish the entire NI Switch Executive Virtual Device.  Once finished, generate a Microsoft Excel report, change the Multiconnect Modes, and then import from the Excel report.  Examples showing how to generate the report and import the report are provided with NI Switch Executive: C:\Program Files\National Instruments\Switch Executive\Examples\Excel.  The examples are GenerateExcelReport.xls and ImportFromExcel.xls.  This option is likely to be the preferred option if a select number of routes need to be changed.

3.  Utilize the NI Switch Executive Configuration API to automate the change from Multiconnect Routes to No Multiconnect.  As an example, I've attached No Multiconnect.llb.  The Top Level VI (NI Switch Executive - No Multiconnect.vi) uses the NI Switch Executive Configuration API to change all the routes of any NI Switch Executive Virtual Device so that the routes are configured with the No Multiconnect option.  The attached VIs can be coded to do custom changes (in reference to Multiconnect Modes), though I would expect this option is preferred when a customer wants all their routes changed to No Multiconnect.

Hope this helps!

Chad Erickson
Switch Product Support Engineer
NI - USA

Message Edited by Chad PSE on 09-05-2007 01:07 PM

0 Kudos
Message 2 of 5
(6,774 Views)
Hi Anke,
 
Update for workaround 1. You can use this option for a large number of routes.  Just select multiple routes and change them all at once to Multiconnect Routes and then back to No Multiconnect.
 
I apologize for any confusion,
 
Chad Erickson
Switch Product Support Engineer
NI - USA
0 Kudos
Message 3 of 5
(6,768 Views)
Hi Chad,

This workaround will do nicely. Select Multiple Routes - I should have thought of that myself!

Thanks for your quick reply, and no need to apologize.
It's good to know someone is solving my problems while I enjoy sweet dreams this side of the Atlantic Ocean.

Regards
Anke
0 Kudos
Message 4 of 5
(6,757 Views)
Hi Anke,
 
Glad to help.  In the future, if you need to reference this issue again, please mention Corrective Action Request (CAR) ID#: 4D4CTTKI, as it was filed to fix the problem.
 
Best regards,
 
Chad Erickson
Switch Product Support Engineer
NI - USA
0 Kudos
Message 5 of 5
(6,747 Views)