LabView to build a robot

Hi,
I'm new to programming in LabView and I have to built a robot using LabView.
But I don't know where exactly to start
I have to let the robot perform a few functions like grabbing an object, sort the objects,...
Can anyone help by showing examples of LabView programming for robots?

Hi gv100,
Glad to hear you're trying out LabVIEW for your robotics project. I think you've made a good choice.
Sounds like your project entails a fixed-base robotic arm that incorporates varying elements of vision and force feedback. Like the other guys said, you should probably think about what hardware you'll be working with first. What sensors do you intend to use? What kind of camera? Strain gauges? etc. There should be several technical resources available on ni.com for interfacing to a variety of sensors. Here's a good place to start: http://www.ni.com/devzone/idnet/
And what kind of processing target to you plan to use? Will you be running from a Windows computer or do you plan to use an embedded processing target? One of the nice things about LabVIEW is that you have a variety of processing targets to choose from, without having to worry about major changes in your LabVIEW code.
And I agree with Jim's suggestion: The LEGO Mindstorms NXT is a great, low-cost robot prototyping tool (despite the fact that it's typically seen as a toy). If you can get your hands on one of those, you'll have access to a variety of sensors and actuators, an ARM 7 prcoessing target, and the ability to build your program using LabVIEW and the NXT toolkit.
For general Getting Started material for building robots, we have the Robotics Fundamentals Series. These tutorials may not be specific to your project, but it might help you wrap your head around what design elements are typically involved when building a robot from scratch.
Hope this helps.
Emilie

Similar Messages

LabVIEW application builder - Deep start menus

Hi, is it possible using the labVIEW application builder to create start
menu program groups that are more than one level deep, i.e.
Start\Programs\My App\Tools

Just for you to compare I have attached some screenshots of my setup. Maybe you find a difference.
Attachments:
App_Builder_Setup.gif ‏152 KB
App_Builder_Menu_example.gif ‏83 KB

Is LabVIEW application builder needed for TS deployment?

Does the LabVIEW application builder need to be installed for TS deployment of a project containing LabVIEW VI's?

LabVIEW Application Builder is only necessary if you are deploying LabVIEW files, even then you can use the flag "Include without Processing Item or Dependencies" in all your LabVIEW files to create an image and optionally an installer without requiring LabVIEW (or app builder) at all; however, using this flag is not recommended becuase if you use it you would have to include all the files and their dependencies in your deployment manually (either by including the root directory of your test system or by adding all the files to your workspace) and you would have to make sure that they are not broken and can be called from the run-time engines you are including in your installer.

How to use labview to control a robotic arm by EMG signal

Hello,
I am working on simulation of an active Exoskeleton (wearable robot) for the upper limb using LabVIEW for my senior project. I need to use the EMG signal as an input to move the elbow joint (flexing and extending). I downloaded labview biomedical toolkit to take a ready simulated EMG signal but have a weak experience in LabVIEW.
The design criterial I am planning to use is to establish a threshold for the EMG signal using a comparator (above 0 for example) and set a counter for everytime the signal passes the threshold as(+1) in every count. Then, specify a degree value for the counter (for example when the counter reaches 10000) and feed this value of the counter to a simple simulated structure for the joint (simple angle of 2 lines) or a meter to represent the movement.. e.g. every 10000 count = 1 degree of movement. Zero crossing can also be used instead of the comparator and the signal will be filtered and that is easy to do. However, my problem is in converting this logic into LabVIEW. I don’t know how to set a counter for the signal and make every number of counts refer to a specific degree of movement and I also don’t know how to form the simulated joint structure in LabVIEW or even how to transfer this into a simple meter device in LabVIEW.
I have only one month to do this project so any help or ideas you provide are highly appreciated
Thank you ,

CarlFHellwig
Thank you for providing this example I just implement it in the software to check the counter results.
In fact, the design criteria I desided to use latly is to use is to establish a threshold for the EMG signal using a comparator and correlate the EMG signal with the angles of movement of a simple simulated structure "motor" for a single joint (simple angle of 2 lines) eg. 30,60,90,120,150 degrees for flexing and extending. Zero crossing can also be used instead of the comparator and the signal will be filtered and that is easy to do.
In other words, the idea is to drive a motor for different angles based on the input EMG signals. I am now stuck with developing the algorithm of how the angles are related to the RMS value of the signal while flexing and extending and how to convert this RMS into angular velocity and angular position to form the simulation.
I will be grateful if someone guided me to a person did a similar project to discuss some issues.

DLL build by Labview App Builder doesn't work if Built-IN functions used!?

Hi All,
I hope somebody shed some light on this;
(All VIs are in the attached case1-2.zip)
Case 1:
A VI reads a 1D array data and Uses RMS.vi to calc the rms of the data and returns the rms value and the error value. (make1_dll.vi).
This VI is used to build a DLL. (test1.dll using the test1.bld)
Call this DLL in a new VI (just to test that the DLL works) (test1.vi)
RUN the new VI >>> Result Nothing happens No Error or Crash and No result!!!
Case2 :
Build the above without using the “RMS.vi” and works OK. (see case2 VIs)
Any idea why the build-in function doesn’t work?
Best regards
Attachments:
case1-2.zip ‏44 KB

Joel A wrote:
You might want to look at the path building you are doing to find the RMS VI. If you are using relative paths, then LabVIEW calls like "VI Path" will have an extra path if the VI is an exe or inside an LLB.
Drop some probes (indicators, outputs, etc.), rebuild and double check the paths. I've been burned by this before...
If this is the case, you can use the VI properties, or path parsing to solve it.
joel
I don't think that is the problem. The RMS.vi is referenced as statically linked VI in the make1_dll.vi.
As such it should be linked into the LabVIEW DLL as well. What I suspect is the problem is the fact that
the RMS.vi uses the lvanlys.dll and that for some reason there is something going wrong with the LabVIEW
test1.dll, which runs in the LabVIEW runtime context, calling lvanlys.dll while executed in the context
of LabVIEW itself. Probably something to do with the changes to how lvanlys.dll is treated between LV 7.0
and 7.1.
I see this same behaviour on my system too, so an installation problem is quite unlikely. Other than that calling a LabVIEW dll from within LabVIEW makes not that much sense (but did work fine in the past save from some hassles in 6.0 and 6.0.1), I have no explanation why this doesn't work.
Rolf Kalbermatter
Rolf Kalbermatter
CIT Engineering Netherlands
a division of Test & Measurement Solutions

Labview communicate with ABB robot through dll Dot Net

Hi all,
Currently  I need to use labview to do the communicate with dot net, for example to read and write RAPID data, Get execute status from robot. I'm able to read from RAPID but can't manage to write. Does anyone have an idea how to do? Please advice. Thanks

Hi,
     The NI OPC Server supporting device and drivers are here. Labview and third party device communication through OPC Server web cast avalable on here.
     Datasocket/OPC Server Example avalable on following link. \Program Files\National Instruments\LabVIEW 2009\examples\comm\datasktx.llb
Siva
Sivaraj M.S
CLD

I seek exemple of codes in labview for programming a robot

Hello,
I have a project and i seek codes programming in labview for move an lego mindstorm. It's for have an idea on how use labviex for move or turn the robot
Thanks

Have you tried the vi's contained in the NXT Toolkit? It has most of the NXT-G blocks, including Move and Motor.

LabVIEW 2009 build memory usage exceeds Windows limit

We have a large application that builds without problems using 8.6.1, but failed to build using LabVIEW 2009 with the error "Not enough memory to build this application".
We solved the problem by adding the parameter /3GB to the Windows XP boot.ini file. This increases the available memory for a Windows XP application from 2Gb to 3Gb.
It appears that LabVIEW 2009 uses more memory during the build process and, in our case, this took it over the 2Gb limit.

We are also facing the same problem...
can National Instruments help us ??????
Following error is occuring while creating exe.
"Build was unsuccessful
An error occurred while saving the following file:
D:\BIS_Main_2009_V3.XY\branches\BIS_Main_2009_V3.61_Trans\User Interface Panels\Inspection.vi
Invoke Node in AB_Source_VI.lvclass:Close_Reference.vi->AB_Build.lvclass:Copy_Files.vi->AB_Application.lvclass:Copy_Files.vi->AB_EXE.lvclass:Copy_Files.vi->AB_Build.lvclass:Build.vi->AB_Application.lvclass:Build.vi->AB_EXE.lvclass:Build.vi->AB_Build.lvclass:Build_from_Wizard.vi->AB_UI_Frmwk_Build.lvclass:Build.vi->AB_UI_FRAMEWORK.vi->AB_Item_OnDoProperties.vi->AB_Item_OnDoProperties.vi.ProxyCaller
<APPEND>
Method Name: <b>Save:Target Instrument</b>"
Please suggest!!!

LabVIEW Application Builder Crash : ntdll.dll faulting module

Hello guys,
I'm currently experiencing problems while building my project (LV2012 (32 bits) , Windows 7). At the very end of application build, LabVIEW crashes with no explanation (Screenshot in french, sorry)
Windows error logging follows :
Event 1000 Application Error
Faulting application name LabVIEW.exe, version : 12.0.0.4024, time stamp : 0x4fea600e
Faulting module name : ntdll.dll, version : 6.1.7601.17725, time stamp : 0x4ec49b8f
Exception code : 0xc0000374
Fault offset : 0x000ce6c3
Faulting process id : 0x16fc
Faulting application start time : 0x01cda5350f41f87c
Faulting application path : C:\Program Files (x86)\National Instruments\LabVIEW 2012\LabVIEW.exe
Faulting module path: C:\Windows\SysWOW64\ntdll.dll
Report Id : 8e5b1344-1128-11e2-97d8-c0f8dae81bad
I had the same problem on LabVIEW 2011. I tried to build my application with another computer (also LV2012 32 bits and Windows 7 64 bits) and I do not have any error.
What is wrong with my computer?
For french people, topic in french
Thank you for your help,
Regards,
Quentin
Solved!
Go to Solution.

Solution found :
-Uninstall all NI products
-Clear registry keys related to LabVIEW
-Delete National Instruments directory into Application Data
-Reinstall LabVIEW

Using the LabView application builder

Hi.. I'm trying to build an application from my labview project and I want it to run it in a computer with no Labview installed. When I'm trying to run this Error shows up: Unable to locate the Labview Run-time engine. Is It possible to run my application in this computer? or definetily I have to install Labview on it in order to run it.
Thank you

You need to install the LV runtime engine corresponding to the LV version of the development environment.
This can be easily accomplished by creating an installer for the executable. Also an option in the project build menu.
Otherwise search the Ni website and download it.
Regards,
André
Regards,
André
Using whatever version of LV the customer requires. (LV5.1-LV2012) (www.carya.nl)

LabVIEW 2009 Build Path Problem

[Cross Posted to LAVA]
I had some code that worked fine on my home PC, when I moved it to work, the exe would not build due to errors.
The errors coming back weren't that good at explaining the problem
Until I got this one:
Look at the path in the error:
C:\Users\Developer2\Desktop\User Group Meeting\LabVIEW 2009 new features\code\02 intermediate\01 build specifications\build executable file paths\dist\application 9.0\my application.exe\LabVIEW 2009\vi.lib\addons\_ICON Library\String\_icon_lib_string.llb
That path is referring to a VI inside my executable!
This may be a bigger issue that I first thought
So my question is:
If a have a path inside my build that would be relative to the executable and LabVIEW needs to resolve it, could that process fail depending on where the exe sits in a folder hierarchy?
I guess this could have happened before? but it would be more likely now due longer paths!
Message Edited by jg-code on 08-26-2009 05:20 AM
Certified LabVIEW Architect * LabVIEW Champion
Solved!
Go to Solution.

Solution in cross post
Certified LabVIEW Architect * LabVIEW Champion

LabVIEW hangs building packed library

Hi,
I have migrated most of my object libraries to PPLs (suffering the common pitfalls). But yesterday I encountered a (what I think) Biuld process specific issue:
after updating / changing som dependencies I tried to re-build, but LabVIEW locks up in the build process: the dialog says "Building packed library"
and LabVIEW can only be stopped using the Task Manager.
What I see in the target directory is, that all the dependencies are generated corretly (PPLs themselves) as well as a ZIP File with the name of the target PPL.Using 2013SP1f5
Any hints anyone?
Cheers
Oli
Programming languages don't create bad code, programmers create bad code....

So... finally tried on a different computer (f2 though)
Worked from scratch five times in a row until I dared to disable debugging. Reenabling debugging after restart did not solve the problem. Tried a Clean before the next try. This worked for the next build. But a subsequent build without doing any changes failed again.
On this computer, the NI Error Report did not always occur; if it didn't LV came up with the following eror message:
Might be related to f2, but maybe it might be a hint.
Programming languages don't create bad code, programmers create bad code....

Labview project build specification

I created a LabVIEW8 project. WIthin it I have a few folders that organize my code. I'm trying to create a Build Specification (found at the bottom of the project view). I created a new Build Spec and began populating it. I can add information to all fields, except the Source Files category. When in the Source Files category I'm able to specify the Dynamic VIs and Support VIs in the bottom box by selecting Full OI - Top Level VI.vi. However, when I try to select any single file (Launcher.vi in this case) as the Startup VI, all my VI files become grayed out. I can't select any of them. I tried placing my launcher file in a new folder (apart from the majority of my code). It allows me to move the folder into the Startup VIs area, but when I say 'OK' or 'Build' at the bottom, it comes back telling me that it can't continue because I haven't selected a Startup VI. Any ideas?

Have you tried saving the project and trying again. I tried to create one on the fly and it wouldn't allow me to select it as a top level VI until I saved the project and the VIs in the project. Give that a try and let us know how it goes.
Tyler H.
National Instruments

Why does LabVIEW Application Builder 8.0.1 create an executable that will not run?

My VI runs perfectly. But when I generate the executable, it will not run. I get a "File Not Found" error. The file it can't find is "File Open+.VI" from vi.lib. I've tried copying File Open+.vi into my project. If still generates the same error.
Attachments:
OTS.zip ‏3105 KB

There error is coming out of FlowCal Server. You use the current VI path to build up the file paths. That works great in development but when you compile a VI into an exe, an extra layer is added. See this KB http://digital.ni.com/public.nsf/websearch/FD7DE8BC8FFC256C862565F4006BE363?OpenDocument
So when its an exe you need to strip the path one more time.

How can I call a DLL from Borland C++Builder that was generated by LabVIEW?

In the linking phase, the linker of Borland C++Builder echoes the message shown below:
[Linker Error] 'Test.LIB' contains invalid OMF record, type 0x21 (possibly COFF)
'Test.LIB' was generated by LabVIEW Application Builder and had been verified working well with Microsoft Visual C++

"Murray Chen" schrieb im Newsbeitrag
news:[email protected]..
> In the linking phase, the linker of Borland C++Builder echoes the
> message shown below:
>
> [Linker Error] 'Test.LIB' contains invalid OMF record, type 0x21
> (possibly COFF)
>
> 'Test.LIB' was generated by LabVIEW Application Builder and had been
> verified working well with Microsoft Visual C++
Hi Murray,
Borland C++ Builder uses a .lib format which is not equal with VC++. You
have to rebuild your .lib by using implib.
Try 'implib library.lib library.dll' to create a new .lib.
Greets
Henrik

LabView to build a robot

Similar Messages

Maybe you are looking for