Agilent 16700 Logic Analysis System Driver Problems (Intuilink Software)

[daarya]

Hello,

I am using the Intuilink 16700 Software to remotely control the 16700 Logic Analysis System with my PC. The LA system uses the 16750B Analyzer module. I am using the LabVIEW interface to the COM Automation server to control the instrument. In the examples for LabVIEW 6.0, there is a vi called Analyzer Listing that does what I want to do. It works well when I run this vi. I see a problem when I make a small modification to this vi.

Here's what I changed in the example code (Analyzer listing.vi):

1) Removed the automation open and Invoke Node (calling the "Connect" Method)

2) Created a new vi and placed the above 2 functions in the new vi.

3) Placed the modified example in the new vi as a subvi.

4) Connected the automation refnum from the Invoke node (calling the "Connect" Method to the modified example.

Strangely, I now get an error at the Property Node where I am trying to Get the Analyzer Acquisition module. Every other function before this works; it fails only at this point and gives an error stating "Server Execution failed". It gives me the correct module name and description too.

My instrument driver architecture requires that the Initialization related functions be wrapped in a subvi and I need to call the vi in this way.

Anyone who has used the Intuilink software, please help me understand what the problem is and how it can be corrected.

Thanks in Advance

[Brett_B.]

Timing may be the biggest issue when you start manipulatin the code in your driver. Did you use the error clusters in your subVIs? These often ensure execution order between VIs. If your code happens in the wrong order...you may get errors. Run your code in highlight exe mode and make sure everything is happening in the same order as the un-altered code.

-Brett

[daarya]

As far as I can see, I am not changing the logic in the code at all. It is analogous to this example:

If I have vi A that does these actions:

File Open, Read Data from file, File Close

Now I remove the File Open from vi A and call the modified vi, B.

I create a third vi C which does this:

File Open, Call vi B as a subvi.

That should make both A and C identical - thats the only change I'm making so I really cant see why this problem occurs.

Something seems to happen to the refnum when it gets through the connector pane of the subvi B.

[Brett_B.]

Have you probed the refnum to see if it is changing? I won't be able to run it...but you could post your code and I could look at it. A ZIP file is the best way to post multiple files to the forum.

-Brett