LabVIEW project

Hi
I have a task to complete on LabVIEW and i was wondering if anyone is willing to create it for me as it's the only piece missing for my personal project. I am not familiar with LabVIEW and therefore, if anyone is interested, i can pay you through paypal for the completed project. Thank you

You can post such requests in the LabVIEW Job Openings forum.

Similar Messages

"unable to load labview project" in Deployment Machine

Hi all,
well the Deployment Target works fine on Development machine
But has problem Loading on the Deployment System "unable to load labview project"
has anyone had similar issues and ound a soln.
NI Support has not responded yet to the solution.
Attachments:
unabletoload.PNG ‏17 KB

Hi aparab,
I think I will need more information to solve this issue.
You told "NI Support has not responded yet to the solution." Do you already have a service request number of the NI support?
Can you post your project? Which RT-target do you use? Which hardware?
You can also post a MAX report of you windows computer and one of your target:
1. Start -> Programs -> NI MAX
2. File -> create protocol -> choose technical support and my system (development computer) -> next -> next -> choose path -> next -> finish.
3. File -> create protocol -> choose technical support and your RT-target (real-time system) -> next -> next -> choose path -> next -> finish.
Best regards
Suse
Certified LabVIEW Developer (CLD)

Is there a way to determine the equivalent ANSI C code from a Labview project?

I'm a complete beginner to Labview. I have this fairly complex Labview project that was used to create a DLL which matlab could call to control my PCI-6534 card without having to know the NIDAQmx calls.
I'm in the process of figuring out how to make those NIDAQmx calls directly from Matlab but I'm not getting the same results as when I call this DLL mentioned above so I thought I'd try to make sense of the Labview project VIs. I'm starting to make sense of the overall scheme of the VIs, but I'd like to be able to run the project, step through it, and perhaps see the NIDAQmx commands (or something equivalent so I can determine how to call the NIDAQmx commands within Matlab).
Is this possible to do?
Thanks,
Jason
Solved!
Go to Solution.

Yes. The toolbar allows you to turn on highlighting so you can run the VI and see the contents of wires. You can put probes on wires. You can single-step through code. All of this is explained in the LabVIEW Help under Fundamantals -> Running and DEbugging VIs -> Concepts -> Debugging Techniques.
In regards to the implied question in the title of your post, no you cannot directly convert LabVIEW code to C in the development environment. Yes, there are tools to convert LabVIEW to C, but that's intended for microprocessors.

LabVIEW Project and saving only the relevant vis

I have a large development folder (and sub-folders) that I have used as a repository for all of my development plus test pieces of code. There are about 800 vis in the folder, but if I save my main VI off to another folder using "Duplicate Hierarchy to new location" I end up with 150 or so relevant files. Unfortunately I have not discovered an easy way of copying the project over to the new location.
What I'm looking for is the ability within the project file to go through all of the files that in the project, determine if they are used in the VI hierarchy, transfer those files to my new location along with the project files. And then also reference all files in the new location, not the old. This way I could build a number of slightly different programs, but which uses the whole power of my development vis that I may have already.
Dan

Peter_B wrote:
Ben wrote:
I'd start by creating a source distribution in the project (use perserve hiearchy) based on the top level VI or if that is not enough create a Tree.........
A similar problem has stumped me for years and relates closely to the solution you pose Ben.
I am frustrated that LabVIEW doesn't allow me to include the lvproj file into the source distribution. I used to be able to do it in LV2009 via a workaround (I'd put the lvproj file into a subdir of the highest commmon DIR where all the project files reside on disk), but now LV 2010 intentionally seeks out and excludes my lvproj wherever I try to hide it !!
This article from NI Source Distribution Does Not Include LabVIEW Project File tells me to use the zip file distribution method instead. Well, that ain't a solution for me as zip file distributions don't have:
the 'Always Excluded' pane in the Source Files menu (there are project files that I don't need to distribute),
the 'Additional Exclusions' menu item as for some reason there are a heap of vi.lib files also included into this zip (which I don't want or need).
Yes I still that was a bad idea by NI.
I did try to log a bug about that but was fed some line about including the .proj file was not part of thier use case so... I think their use case is flawed, still.
Ben
Ben Rayner
I am currently active on.. MainStream Preppers
Rayner's Ridge is under construction

How can I copy tasks from Automation Measurement & Explorer to a LabView Project

I have a labview project which currently relies on tasks that are predefined in the Measurement and Automation Explorer. I haven't been able to figure out how to export them out of the Measurement and Automation Explorer to be imported into Labview. Can this be done?

Well, let me try to explain something, which can be really questionable
Hence both methods use the same API, the DAQmx API, they have different "implementations". The LV API consist of LV VIs, of course, in the first instance. Of course, digging deep into them, you will encouder CLFNs to the DAQmx DLLs. But some of them are "hidden" because property nodes are in fact something similar to the DLL-calls......
In MAX, you never "see" the API, you are using the wizard. Nevertheless, MAX uses the internal functions contained within the wizard to use the device just as desired (hopefully ) But it never will use the VIs to accomplish that...
Now there are imho two possibilities for you:
a) You start using the LV DAQ Assistent to create your tasks on the PC. It has the same appearence as the wizard in MAX, so you will not trade any used interface for a new one (which would be the API). When you finished the definition, the wizard can be transferred to LV code which can be altered. But if doing this, you will lose the possibility to alter the task using the "used API", the wizard.
b) You can live with the current situation but create a product suggestion for LV and DAQ at the Product Suggestion Center.
hope this helps,
Norbert
CEO: What exactly is stopping us from doing this?
Expert: Geometry
Marketing Manager: Just ignore it.

Can't access variables in specific S7-1200 DB's in LabVIEW project

Hi all,
I'm trying to establish a connection between LabVIEW and a Siemens S7-1200 though Ethernet and SIemens OPC Server.
The physical connection is OK (I can ping S7-1200 with no problem).
When I needed to access variables from specifics DB's inside S7-1200 ( I want to access variable DB190,X0.4), I called Siemens support and they said I had to modify the variable's definition when using OPC Scout, from "MX0.4" to "DB190,X0.4", and then it was possible to access this variable.
Same solution (renaming the path) applies to NI OPC Client, I can read and write variables properly.
My problem is that when I try to add variables in LabVIEW Project, I can't find those variables whose address were modified, so I can't access the correct variable in my program.
I tried to change the variable path in Multiple Variable Editor, but it doesn't work either.
Any suggestions on what I can try??

First: Avoid the ODBC/JDBC Bridge if at all possible.
It's the worst JDBC driver I've ever seen. It's buggy
and a great hindrance both to learning and to
producing usefull code.I agree that there might be problems with M$ Access, but there are problems with all databases, including MySQL (e.g., no referential integrity in free download version). It's capable enough for the query the OP is trying to execute.
The problem is with his code, not Access or the bridge driver. He'll go through a lot of effort to switch databases and still have this problem. Better to understand what HE'S done wrong and fix it so he'll do it correctly for all databases, including Access.
You just need to be more careful with your query, I'm sure.
%

Where Used for VIs and LabVIEW Project

Is there a way in LabVIEW Project Manager to check the Where Used status on all the VIs at the same time? I am going through a project trying to weed out VIs that are not used in the project. I know I can check the "Find Callers" for each VI, but this feels slow and cumbersome. Is there a way I can generate a report to find the Where Used status on all VIs in a project?
Thanks,
Matt

You also have the Find Items with No Callers Dialog Box as of LV 8.5
Eric V
National Instruments
Applications Engineer
Certified LabVIEW Associate Developer
"I'm a Ramblin' Wreck from Georgia Tech and a helluva (NI Applications) Engineer!"

Labview project functions differently when compiled

I have a medium sized labview project that is causing me trouble. It will work properly when I run in development mode, and it will compile with no problems, but when I run the executable it no longer functions the same. It seems that large portions of the code just don't run. I have made sure that all VIs are included in the build. I have no way to debug it in application mode, so how am I supposed to fix this problem? Any suggestions would be appreciated. I'm running Labveiw 8.5. Thanks,
-d

Hi dhowland,
what does refuse to talk mean? Is there no error message when the communication fails?
Do you work with automatic error handling? This does not work in an executable. Program the error handling yourself.
Greetings,
shb
Source, Error handling in Executable:
"- Incorporate error handling into the VIs of the application because LabVIEW does not display automatic error handling dialog boxes in the LabVIEW Run-Time Engine."
http://zone.ni.com/reference/en-XX/help/371361D-01/lvhowto/caveats_apps_dlls/
Message Edited by shb on 04-03-2008 01:34 PM

What are the advantages of using LabVIEW projects in TestStand, as apposed to just a path to a vi

What are the advantages of using LabVIEW projects in TestStand, as apposed to just a path to a vi ?
I am modifying an existing workspace for a new product, and it seems like more work to add the vi's into a LabVIEW project
does it gain anything in the long run

Hi Rusty,
I wanted to quickly clarify on the integration between TestStand and LabVIEW Projects.
As Jeff mentioned, some of the big benefits of using LabVIEW Projects is to organize code and to namespace them.
For instance if you had a project called "Power Supply" that housed all your power supply code and had a VI in that called "Initialize", and another project called "Temperature Chamber" that also had a VI called "Initialize", both these VIs are namespaced by the project, so there is no longer confusion about which "Initialize" VI is being used.
Now from a TestStand point of view, in prior version of TestStand, we lost some of this benefit because TestStand did not know about TestStand projects and called VIs simply as un-namespaced VIs. However, in TestStand 2010 (released last year, free eval available at ni.com/teststand), we added the ability to (optionally) call VIs within the context of their projects. This means that:
VIs are now namespaced by their project, even when called from TestStand
VIs can use project specific constructs like NI-DAQmx tasks and conditional compilation settings
Note: When creating deployments, the VIs maintain their projects and namespacing, so this benefit holds true for deployments as well.
Additionally, someone had mentioned looking into using lvlibs to namespace your VIs for deployment. Two comments:
With TestStand 2010, this is no longer neccessary since the project itself namespaces the VIs
You might also want to look into LabVIEW Packed Project Libraries, which combined several VIs into a single file. Think of it as a DLL specific to LabVIEW that is as easy to call as normal LabVIEW VIs. TestStand 2010 can call VIs that are exposed by PPLs. In addition, the deployment utility can automatically pack your VIs into PPLs for deployment.
Hope this is helpful!
Jervin Justin
NI TestStand Product Manager

Required in labview project

hello sir/madam,
I am working on labview project.i am learning myself and implementing the logic.
I had a doubt.does using merge function will effect ohter signal.suppose i am merging two signals using merge function.so will one signal effect other signal after merging.waiting for your positive reply

hello,
First of all thank you for your response.i have cleared my doubt about merging any number of signals and displaying it on waveform chart.
I have other doubt.So there are two signals.As one have 8 value and other has 10 value.i have merged this two signals using merge functions.now at output of merge signal is a single wire.From that single wire i have extracted one signal by specifying channel number.say that signal value is 8.i have done subtraction operation on that single.now this subtracted signal i have merged with already merged signals.so my question is now value 8 should be overriden bt this subtracted value and on chart it should show subtracted value and value 10 which is not operated.bt i am getting three graphs.one is value with 8 ,other with value 10 and other with subtracted value.bt i dont value value 8 on graph instead i need subtracted value and value 10 on graph.i even have attached the code .pls suggest me the solutions.
waiting for your response.
Attachments:
labview code.doc ‏51 KB

I can't connect to my PXI from within my LabView Project

Please advise,
I have been programming my PXI-8195 fine for weeks, but this morning I am receiving an error in connecting to the remote system from within my LabView Project. MAX says it is 'connected-running' and I even successfully tested a DAQmx task. I tried rebooting the PXI a couple of times as well as my host computer.
Thanks in advance for any assistance.

Hi Nik11,
What error are you receiving in LabVIEW? Also, what operating system are you using on the 8195, and are you using LabVIEW or LabVIEW RT?
Regards,
Adam W
Applications Engineering

Custom LabVIEW projects

I am trying to create a new template to be used with LabVIEW 2013 Create Project wizard. I have followed the tutorial 'Using Custom Templates and Sample Projects to Develop LabVIEW Projects' but still seem to be having issues.
I am pretty sure it is something really simple that I am doing wrong but can't seem to find the issue.
I have placed the template project in LabVIEW Data/ProjectTemplates/Source and the xml in LabVIEW Data/ProjectsTemplates/MetaData.
When I create a new project using the wizard, the project gets created and runs perfectly the first time.
Then when I open it a second time, there are a load of conflicts that all of a sudden exist where some of the vi's are linked to the template project.
I can go and resolve all the conflicts and then the project works but there must be something that I am doing wrong.
I will be grateful for any help getting this sorted. I have attached the conflicts and my xml file (I have changed the extension of the xml file to attach it).
Thanks,
Greg
Certified LabVIEW Developer
Solved!
Go to Solution.
Attachments:
Conflicts.png ‏95 KB
TemplateMetaData.txt ‏1 KB

I am trying to do the same thing, and am curious -- is there any way to have auto-populating folders in the template that will point to the correct folder after the wizard runs?
I use auto-populate in all of my projects, I had assumed that auto-populating folders used relative paths instead of absolute paths. Since an autopopulate folder in a template points to the template folder after the wizard creates the new folder structure it would appear that auto-populating folders use absolute paths and there is then no way to do what I'd like... Any thougths?
For now it appears that I need to manually duplicate my basic folder structure in the template project, then after the wizard runs I'll manually convert the folders to auto-populating.

Need help loading DLL in labVIEW project

I have a DLL that was written in C# that I want to load it to my labVIEW project. I have never done this before, so I need help. I chose Connectivity-Call Library Function Node then loaded my DLL. After, under function name, I typed in the function name from the code. I don't know what to do with other like Parameters.
They don't let me attach dll file
Can someone explain how to set the parameters and etc?

Well, it seems that you really need to learn quite a bit about .NET (ActiveX is very similar!) first.
The constructor node in your code creates an object in your .NET CLR (Common Language Runtime). This object exposes properties and/or methods. Use Property Node(s) and Invoke Node(s) to access these. Usually, you get references to other objects which you can work this.
Remember the golden rule for ActiveX and .NET:
Close all references you created in your LabVIEW code on your own (using Close Reference)!
Norbert
CEO: What exactly is stopping us from doing this?
Expert: Geometry
Marketing Manager: Just ignore it.

Upgrade labview project that has classes and subVi's

We have a LabVIEW project in LV 8.5( freated by a different developer) that has classes, and various Vi's , subVi's.
I am looking to upgrade it to LV 2014. To be safe, I wanto to copy everthing into new classes( renamed from old ones), rename all the Vis( I hav ealready done that in Windows explorere, though not yet added them to project), and use them with renamed subVI's.
The old classes and VI's should remain in the same folder.
What is best way to do that?
I found something here
https://lavag.org/topic/17741-the-nightmare-that-is-renaming-a-class-and-its-folder/
but this basically suggests many methods, and then, would delete the old structure.
Also, what happens to the "controls" that show up under "private" folder?
I have never worked with LV classes, so pardon any lack of knowledge.
sed_y

4) All the subVI's that are being used and reside in different directories, will be made copy of into their own subdirectories, with the originals zipped.
That's the one you need to be careful of. If you have any shared code or re-use libraries outside of the project folder then these will get loaded and saved in LV2014. Use the 'files' tab of the project folder to see which files aren't in your project subdirectory.
Anything that is in user.lib you can copy from the 8.5 user.lib to the LV2014 user.lib folder and your project will automatically find them.
There are some useful tips here about working with LabVIEW projects and keeping all of your code in sensible locations. Anything relating to your project should be within the project subfolder and any shared code should go in the respective user.lib/vi.lib of the appropriate LabVIEW version - this does mean that you have a copy of the VI for each version of LabVIEW so you will need to be careful about making sure if you change it in one version you change it in the other. Even better still is to make your shared code into VI packages - then you can install them for any LabVIEW version and it will automatically save/compile them for the appropriate version. We used to have all of our re-use code in user.lib but it made moving between LabVIEW versions a pain so we started using VI packages and haven't looked back.
Certified LabVIEW Architect, Certified TestStand Developer
NI Days (and A&DF): 2010, 2011, 2013, 2014
NI Week: 2012, 2014
Knowledgeable in all things Giant Tetris and WebSockets

Labview Project questions.. (methodologies...)

Hi
I will be starting a labview project that will be controlling a model
production line system via a web based front end, with data acquisition also
performed and analyse of the results obtained.
Now I was wondering what sort of methodology would be a good one to look
into before starting this project?
what do most other people use for a labview project.
Any help (and references/links) that anyone might think could be useful
would be appreciated
thanks a lot
D

cheers for your help
This is for my final year project, so i was just wondering if anyone could
point me a good direction for a specific design method. Having not done
much Information Technology methodologies is not one of my strong areas.
I'll have a look at the programming standards topic you mentioned
thanks again
D
"Labviewguru" wrote in message
news:[email protected]..
> D
>
> Take a look at the topic: Programming Standards.
>
> There is a lot of applicable information there.
>
> The most important thing for a project is design. At least half the
> time and effort spent on a project should be design.
>
> As for specific design models, well, that's why you were hired to do
> the job, right?
>
> Good
luck

Flow Diagrams for LabView Projects

Hi!
What techniques should I follow to develop a flow diagram for one of my labview projects?
Thanx

What an open ended question! I could find no documents that I thought would answer your question. You might find them useful however:
Linear Systems in LabVIEW
Event-Driven Programming in LabVIEW
NI offers classes for LabVIEW. You might find of of them useful. www.ni.com/custed

LabVIEW project

Similar Messages

Maybe you are looking for