LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Why does Lab View add control elements to some driver VI's!

Solved!
Go to solution

Hi,

 

I have downloaded a driver project that was developed with Lab View 2009sp1. Now I will this project use with LV2010.

To do this I have the library installed in instr.lib. But when I opened some VI's I discovered that Lab View have added control elements.

Why is it so and how can I stop this behaviour?

 

0 Kudos
Message 1 of 23
(3,249 Views)

What do you mean by control elements?  Controls in the front panel palette?


GCentral
There are only two ways to tell somebody thanks: Kudos and Marked Solutions
Unofficial Forum Rules and Guidelines
"Not that we are sufficient in ourselves to claim anything as coming from us, but our sufficiency is from God" - 2 Corinthians 3:5
0 Kudos
Message 2 of 23
(3,244 Views)

Yes, Lab View adds a numeric control to this VI.

I have attached a screen shot of this VI. One time opened with LV2009 and on time opened with LV2010.

0 Kudos
Message 3 of 23
(3,235 Views)

Rightclick on the control>> Visible Items>>Uncheck Digital Display.

Its the digital display from the same control, its not an extra control.


CLA CTAChampionI'm attending the GLA Summit!
Subscribe to the Test Automation user group: UK Test Automation Group
0 Kudos
Message 4 of 23
(3,224 Views)

I doesn't mean the Operation Mode enumeration. I mean the control below with the label "Value (0)". This control is generated by LabView.

And also in some other VI in the same library are different changes who are made by Lab View.

0 Kudos
Message 5 of 23
(3,207 Views)

Wait. What?

 

Your advice that "Its the digital display from the same control, its not an extra control." is not true.

 

Look at the PDF the OP provided.  Clearly someone modified the VI in question to add an extra floating-point parameter to be passed to the instrument after the mode-setting command.  This is an NI-supplied instrument driver for a family of Höcherl & Hackl electronic loads.

 

I'm not sure where the OP got the earlier version of the driver.  I just checked the IDN, and there is only one release listed, and the VI in question has the "Value (0)" parameter on the conpane and wired in to the Format Into String node.  So, there's no telling where the OP got the prior version.

 

Dave

David Boyd
Sr. Test Engineer
Abbott Labs
(lapsed) Certified LabVIEW Developer
Message 6 of 23
(3,207 Views)

Surely that didnt just happen because you saved it in 2010. You downloaded a new set of drivers for 2010 from here: http://sine.ni.com/apps/utf8/niid_web_display.download_page?p_id_guid=AFAA2CBD85041C96E04400144F1EF8...

The second driver has more features.

Also, note that the two modes are different, in the second case you are specifying the current where as the first one is a constant current configuration for the load.


CLA CTAChampionI'm attending the GLA Summit!
Subscribe to the Test Automation user group: UK Test Automation Group
0 Kudos
Message 7 of 23
(3,197 Views)

You weren't explicit, but based on what I am seeing, you downloaded the LV2009 and then downloaded the LV2010 ersions of the driver here right?

 

http://sine.ni.com/apps/utf8/niid_web_display.download_page?p_id_guid=AFAA2CBD85041C96E04400144F1EF8...

 

It looks like they made some revisions between the driver and didn't update the LV2009 version.  Just use your 2009 version and move it into the LV2010 instr.lib directory.  LV will upgrade it and you will have the same code you used in 2009.

0 Kudos
Message 8 of 23
(3,193 Views)

This driver was made with Lab View 2009sp1. And if I open it with the same Lab View version then all VI works well.

But when I will use the same project in Lab View 2010 then I get this additional floating point element. And as result the load who should work with is getting an syntax error.

0 Kudos
Message 9 of 23
(3,190 Views)

.aCe.,

 

Now I'm curious - I followed the download links for both the 2009 and 2010 versions of that driver - carefully, into separate folders - and in both zip archives the file in question has a modified date of 2011-12-15, and a file history version of 74.  Where do you see the OP's older version without the extra parameter?

 

Further down on that page, there are links for the individual instruments supported - and some of those lead you to an older-style driver "0604" enclosed in an LLB.  But those look completely different.

 

Dave

David Boyd
Sr. Test Engineer
Abbott Labs
(lapsed) Certified LabVIEW Developer
0 Kudos
Message 10 of 23
(3,184 Views)