.NET references with OOP

[bmann2000]

I have a large OOP app that uses various external instruments from multiple vendors, the instruments are controlled over .NET.

My colleague creates DLLs in VB that communicate with the same instruments, the DLLs are structured in such a way that we can create a GUI in LabVIEW or VB and call the same DLLs to perform the same functions. 

I'm trying to use a DLL that connects to multiple instruments, and I'm having trouble dealing with the constraint that LabVIEW does not like the .NET reference to be passed out of the Class.

In the diagram below, I am attempting to pass the .NET reference for the motion system to the DLL.  Elsewhere in the app, the motion system would obtain the reference and command a move from A to B, i.e. the motion VIs you see in the diagram below are normally sub-VIs of a motion VI that would command the motion.  This new DLL is design to command moves and therefore needs only the reference to the motion system.

How do I create a design pattern to accommodate what I'm trying to achieve?

 

[Quiztus2]

this looks like a type mismatch between 'get .net ref' and motion device. Of which type is 'motionDevice' and which type does 'get .net ref' output?

[Yamaeda]

Try 'To More Specific', i've solved similar problems with that before. .NET seems bad at handling inheritance.