LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Gradual drift on the X-axis whilst using the DAQ.mx sub VI's

Solved!
Go to solution

Hi GerdW,

 

The two case structures have similair goals however they do things slightly different. I am creating a VI for the chemists at a company i am interning at. This VI will be run on a spectroscopy setup. The two case structures are made to activate according to which tab is being used in the VI. 

 

I did not know i could hide labels in the front panel. However could you elaborate why removing the labels is a problem?

 

Which parts of the VI are you referring to with the Rube-Goldberg constructs. I cant see which parts of the VI are redundant.

 

Best regards,

Ulas

0 Kudos
Message 11 of 14
(400 Views)

Hi ulas,

 


@Ulas wrote:

I did not know i could hide labels in the front panel. However could you elaborate why removing the labels is a problem?


Would you write in text-based programming language a:=b+c or would you write "":=""+""?

How do you want to differ two string indicators when both have no label?

Best regards,
GerdW


using LV2016/2019/2021 on Win10/11+cRIO, TestStand2016/2019
0 Kudos
Message 12 of 14
(394 Views)

This is no immediate help for your problem at hand, but is meant to be helpful for the longer term.

 

I opened your vi, and my 10-second assessment was, "don't get involved."   Way too much mess and clutter and too many express vi's for me to spend the needed time trying to figure out what the heck I was looking at.  So I closed the vi and moved on.

 

My feeling is that I don't want to spend more time understanding someone else's code than they're willing to spend making it more neat and understandable.

 

I would recommend you go into Tools->Options->Block Diagram and turn off "automatic wire routing".  It tends to turn connections into a cluttery mess.

 

 

-Kevin P

ALERT! LabVIEW's subscription-only policy came to an end (finally!). Unfortunately, pricing favors the captured and committed over new adopters -- so tread carefully.
0 Kudos
Message 13 of 14
(383 Views)

Hi Ulas,

 


@Ulas wrote:

The two case structures have similair goals however they do things slightly different. I am creating a VI for the chemists at a company i am interning at. This VI will be run on a spectroscopy setup. The two case structures are made to activate according to which tab is being used in the VI.


The two case structures are both connected to the very same tab container.

The two case structures both have the very same two cases each.

Both case structures only have code in one of those case, and it is not the same case.

Conclusion:

Use just one case structure and place the code in each of the two cases…

 


@Ulas wrote:

Which parts of the VI are you referring to with the Rube-Goldberg constructs. I cant see which parts of the VI are redundant.


 

Just to name a few, some of them shown in this image:

  • Case structures outputting a TRUE or FALSE in the TRUE or FALSE case, repectively. No need to output those values as they are the very same as the selector input…
  • Sequence structures inside those cases…
  • Using ToDDT on a DDT wire…
  • Add with 1 when there is a "+1" function…
  • Again: what's the meaning of those unlabelled frontpanel elements?
Best regards,
GerdW


using LV2016/2019/2021 on Win10/11+cRIO, TestStand2016/2019
0 Kudos
Message 14 of 14
(377 Views)