02-23-2006 07:47 AM
02-23-2006 11:02 AM
02-24-2006 03:02 AM
Thank you for these elements,
Il will test today the capabilities of "GenerateExcelReport.xls" from NISE2.1.
I have opened "Configuration Management.vi" in LabVIEW 8.0 to be inspired for NISE Method and Properties use but I can't access to "IVIDevice.name" ! I hope it can be possible to access this property in read/write mode. Could you explain me what is wrong please ?
Emmanuel
02-24-2006 12:13 PM
Hello Guy,
We have used the example "GenerateExcelReport.xls", modified the IviDevice names, exported to NISE the new configuration with "ImportFromExcel.xls" and then tested the new configuration (validation).
Unfortunately the new configuration is badly recomposed with [???]...[???] routes ; so it is unusable !
To summarize, the initial solution : "I change the Hardware Devices names (IVI Logical Name) "manually" in the xml file (with replace tool in notepad) before importing it" seems to be better but not really "elegant" !
Do you notice the same effects ?
Emmanuel
02-24-2006 02:58 PM - edited 02-24-2006 02:58 PM
Message Edited by Guy Ferraro on 02-24-2006 02:58 PM
02-27-2006 12:35 AM
Hello Guy,
"[...] Once the NISE config is downloaded to Excel, you need to do a find and replace on the WHOLE workbook in order to change the old logical name to the new one for every tab."
==> That's what I have done on two different examples, but when I try to check the new configuration done, I notice some [???] in place of the previous valid routes ! I think there is a problem with the XL macro.
Regards,
Emmanuel
02-27-2006 11:50 AM
First I am assuming the route names in the Excel file do not show "???" after find and replace and before teh import from Excel. If once imported they do show "???" it means that NISE dose not recognize the channel names used in the routes.
The procedure I described in previously will work if you are ONLY changing the logical name. This means that the 2 device driver need to be identical, the topology has to be the exact same one so the channels for the new logical device will not differ from the old one.
To verify the procedure I created two logical names pointing to the same device driver (so I can make sure the channels are exactly the same). I then created a NISE vd with one logical name, I created some routes, imported the NISE vd into Exel, find and replace the old logical name by the new one, change the A1 cell on all tabs (to change the NISE vd name) and reimport the new config into MAX. I can confirm that the routes do not show "???" in the new imported NISE vd.
My guess is that there is something different between the old device driver session pointed to by the old logical name and the new one pointed to by the new logical name that prevents the two configurations to have the exact same channel names