Hi Priya,
If you are able to load the data interactively with the NAVIGATOR, then you should have the required LOGOS drivers installed on that computer, and we should be able to load that data programmatically with DIAdem.
The simplest thing to do is to turn on the Script Recorder and have DIAdem trap the specific load command to input your selected traces. This works, but the resulting code is very hard to re-use, unless you want to load the same traces each time.
As you suggested, the alternative approach is to use the Ods...() functions in DIAdem, which is a very general API for loading hierarchical data and data properties from any data storage. This is, in essence, how the NAVIGATOR does its magic.
Below you will find attached a ZIP file which contains examples of using this API. If you choose to use the "SimpleDataSets" Citadel database in the ZIP file, you will need to register it first with your DIAdem as a new Citadel 4 Data Storage. When you decide to try to use your own Citadel Data Storage, you must change the Data Storage name in line 5 or 7 of "Load Selected Traces.VBS". Note that this VBScript launches a SUDialog which contains the same ActiveX control that you see in the NAVIGATOR. The ODS...() functions in the SUDialog control this instance of the ActiveX object which the user manipulates in the SUDialog.
The other VBScript, "Load Citadel Traces.VBS", uses the items selected in the "ASAM Data Service" dialog. I seriously doubt you will want to use this built-in dialog, but the ODS...() functions in this VBScript are easier to find and understand than in the callbacks of the SUDialog.
Ask as you have questions,
Brad Turpin
DIAdem Product Support Engineer
National Instruments