LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

How to integrate a sensor with USB connection to LabView?

Hi,

 

I see exactly what you see. Are you trying the 8.5 version or 8.6? I'm using the downcoverted version (8.5).

 

I checked my .NET framework version, its 4 and I have Windows 7. So it should be fine. I already have TRHC_1.3.11.0927_Full_Setup.zip installed but my goal is integration with Labview. Because I have to make a program in which I analyze the pressure and send a command to a motor.

 

Also when I right click on constructor node and click on "select constructor", it doesn't bring me any option to select the .dll file!   

 

Other errors are as follow:

 

2- Property node: invalid refnum class 

The refnum class that is being passed into this node is not fully defined.  This is because the refnum is defined using external files, and one or more of these files are missing.

 

3-  Constructor node: invalid constructor

The constructor selected in the constructor node is invalid or no constructor has been selected.  Double-click the constructor node and select a constructor.

 

4-  property node: invalid property

 

There are some more similar errors.

 

0 Kudos
Message 21 of 43
(2,302 Views)

Hello EBMec,

 

When I right-click on my constructor node and hit "select constructor", I see this screen (both when opening the 8.5 version and 8.6 version). 

 

constructor node picture.png

 

Can you set your assembly to Omega.USB(1.1.0.4)? Or does that not show up on the list?

 

Also, what does your project view look like? Mine is in 2011, so it will look different from 8.5, but yours should have all the same files (or if it doesn't, then you should add them - the only exception here is that obviously you don't need two copies of Omega.USB.LabView.vi). This is what mine looks like:

project view.png

 

 

 

Finally, I have all my Omega drivers in the same folder location as the VIs. This shouldn't affect anything, but maybe you should move them there just in case.

 

 

Colden
0 Kudos
Message 22 of 43
(2,289 Views)

Hi Colden R,

 

When I right-click on my constructor node and hit "select constructor", nothing pops up to continue!

 

And when I create a constructor node in a new VI and try to select the constructor, I can select the Omega.USB(1.1.0.4) but this time it doesn't show anything in Constructors window (like you have PX409() and PX409(String serial Number)!

 

0 Kudos
Message 23 of 43
(2,287 Views)

EBMec,

 

Are you including both DLL files in your LabVIEW project?

Colden
0 Kudos
Message 24 of 43
(2,267 Views)

Yes, I do add both DLL files. But it doesn't work! I'm still getting those errors.

Could it be because of downconverting?

0 Kudos
Message 25 of 43
(2,262 Views)

Hello EBMec,

 

In order to modify a constructor node, just double-click on it.

 

If you create a new constructor node, can you set its assembly and objects to what I have selected here?

 

constructor_select.png

 

If not, what does your window look like when you double click on the constructor?

 

Also, do you have mscorlib in the list of dependencies of your project?

Colden
0 Kudos
Message 26 of 43
(2,242 Views)

Hi Colden R,

 

Yes, I can set its assembly and objects to what you have shown. What else should I do?

I thought that I have to browse to DLL file!

 

And yes, I have the mscorlib in the list of dependencies of my project.

  

0 Kudos
Message 27 of 43
(2,248 Views)

Can you post a screenshot of what your "Select .NET Constructor" window looks like when you select Omega.USB(1.1.0.4)?

 

Specifically, what do you see under "Objects"?

Colden
0 Kudos
Message 28 of 43
(2,243 Views)

Here is what it looks like. Nothing appears under constructors regardless of the object I select.

 

 

Untitled.png

0 Kudos
Message 29 of 43
(2,239 Views)

Hello EBMec,

 

It looks like this might just be a problem with LabVIEW 8.5 that has been fixed in later versions of LabVIEW. With certain DLLs the constructors do not show up. The solution, unfortunately, is to upgrade.

 

You might be able to get the constructors to work if you can acquire new DLLs that are written for .NET 3.5, as a work around.

 

The other work-around is to try and load the FTD2XX_NET(1.0.6.0) assembly first (the other DLL that came with the driver). Then see if you can load the other driver. This also probably won't work, but it's worth a try.

 

You can also probably manually talk to the device, if you know what kind of commands it expects. I'll get some resources for you on this later this afternoon, if you're interested.

Colden
0 Kudos
Message 30 of 43
(2,233 Views)