LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

using LVOOP with multiple instrument drivers

Solved!
Go to solution

I have created 3 classes SigGen.lvclass, HP8657B.lvclass, and HP8648B.lvclass. The second 2 classes inherit from SigGen which is simply the instrument address and virtual functions. I created a VI that intializes one of classes depending on configuration in a file. This VI outputs a SigGen.lvclass. This seems to be working quite well with dynamic dispatching. So, I created another set of classes for power meters. However in the VI that initializes one of the objects and outputs it as the base class, I get a coercion dot whereas on the SigGen I get none. I am new to LVOOP so I am not sure I am doing this correctly. Can someone take a look?

 

 

Labview 8.5 Professional

0 Kudos
Message 1 of 2
(2,759 Views)
Solution
Accepted by topic author RickieMcDonald

Nothing to worry about. It's becuase you only have one type of power meter to output so the casting doesn't happen until it hits the indicator. With the SigGens the casting happens at the exit terminal of the case structure (which doesn't show a coercion dot).

 

LabVIEW should probably be more constistent in whether it shows a coercion dot when upcasting LVOOP objects.

0 Kudos
Message 2 of 2
(2,741 Views)