how to add dependent vi to my project

[Cherry_QA_department]

Thanks, Kyle;   (Ref# 1984785)

Yes, the cursor situation is working out well.

May I ask 2 quick questions on another topic?

(1)  Please see attached screen shot of my project.  I created a new vi, “FindPeaks.vi”, for use inside a sub-vi, “CaptureGraph.vi”  (which is inside of the MainPanel.vi)

I created the vi using New… Then I added it to the CaptureGraph.vi.

But it doesn’t show up as a dependency, like the other two do. What did I do wrong? And can I fix it?

(2) I am having trouble calibrating the load cell that I have attached to the 9237 module.   Can you recommend a tutorial or an article in the knowledge base?  Many thanks in advance.

John Moodey Quality Engineer Cherry Aerospace 714-850-6175 jmoodey@cherryaero.com

[Alexander_Sobolev]

[1]

Everything is ok. Dependencies show subVIs of all project files, there is no main file for the project.

Project files that you write and use are not and should not be in dependencies, they should be organized in main project section. Full unorganized list of subVIs in dependencies is not a very good idea.

My rule is that dependencies should not include anything except labview folders (vi.lib, user lib, instr.lib).

[RavensFan]

---

@Alexander_Sobolev wrote:

[1]

Project files that you write and use are not and should not be in dependencies, they should be organized in main project section. Full unorganized list of subVIs in dependencies is not a very good idea.

My rule is that dependencies should not include anything except labview folders (vi.lib, user lib, instr.lib).

---

And why do you say that?  There is nothing wrong with having your own subVI's listed in the dependencies section.

The dependencies section list all subVI's that are linked to in your other VI's that haven't already been defined in the upper section of the project.  While it is a good idea to organize all of your subVI's in the upper section of the project into different folders, it is not a bad idea to not do that.

Actually, I find that you have put a subVI into the upper section, you can lose track that you don't need that subVI anymore in your project if you happen to know longer use it and remove from all your other VI's.  If you haven't defined it in the upper section, and you no longer use it, then the subVI will no longer show up in the dependencies section.

There is absolutely nothing wrong with the image of your project directory.

[Alexander_Sobolev]

My list of reasons that make this rule:

When the list of subVIs is 100+ items, you need tools to organize and control all of them from development environment - a simple list is useless.

Folders view is less convenient: organizing files on disk and organizing files for development are two different tasks. Project tree looks different from explorer tree.

Interaction of two projects is more convenient: their file folders overlap, their projects are two different structures.

Many project tools work only for the files included in this project:

1) Arranging into subfolders (virtual or autopopulating)

2) Dependencies files are not included into zip file build

3) Setting properties in all other builds (passwords, destinations, etc)

4) A lot of files are included dynamically, they are not subVIs.

5) Project folders with project tools give quick access to files that are not currently subVIs. It is like a usefull subpalette.

There is a feature to find all items with no callers within project folder. It will not work for project library (on disk) not in project. You will keep the useless VI on disk and do not have way to find it.

Any reasons not to use these? When you need something from above you will spend more time adding files to project one by one rather than having them by default.

[aeastet]

What are you trying to do for the calibration of your load cells? What output are you using and what is the input fromt he loadcells? Are you using a table calibration, mV/V calibation or slope calibration? When you say that it is not working what do you mean? Is your calibration not linear? You do not see the full scale of the sensor? We need more info for the calibration part of the question.

[Cherry_QA_department]

Tim;

 Thanks for your interest in my calibration problem.

My answer to your questions is that I believe that I have tried "all of the a bove", so to speak.

What I need is a tutorial that walks a person through performing a calibration of a load cell that is hooked up to an  NI9237 module and is reading V/V from a strain gauge full bridge and is supposed to be converting it to pounds force.  I would like to use an external table-scale for calibration, but will settle for what I can get to work.

Rather than waste your valuable time, I'd like to do my 'home work' first by viewing a tutorial or reading a paper on the topic..

I've scanned the "Examples" and must have missed any that apply.

Perhaps you know of one.

Thank you for all your advice.

John Moodey

[aeastet]

Try some of these websites for information:

http://www.dataq.com/applicat/articles/an23.htm

http://www.rinstrum.com/downloads/8/26/1203-701-100-M01.pdf

http://www.loadcelltheory.com/LoadCellSupportTheoryPDF/ShuntCalRef.pdf