Labview Opening

Hi, I am Raghul,
Currently working as Hardware test engineer . I have 4 + years of exeperience on Electronics field and 4 years of experience in labview automation tool. I am attaching my resume here. Kindly review the resume and please let us know possible vaccancies in your organization
Attachments:
Raghul Chandran Resume.pdf ‏265 KB

Hello Sumithra_Nagappan,
1. I've certified in NI-LabVIEW CLAD Exam with 75%, and also I know about PLC, SCADA, & HMI Applications.
2. I've 4 months Experience in PLC (DELTA) Programming Language.
Thanks & Regards,
SABARI SARAVANAN M
Certified LabVIEW Associate Developer
Attachments:
SABARI SARAVANAN M (Certified LabVIEW Associate Developer).docx ‏55 KB

Similar Messages

How do I load a vi of global variables whenever LabView opens?

I want to be able to load a VI with Global Variables whenever I open Labview, and not have it open dynamically. So in short, how do I bind or attach a VI to open every time LabView opens and starts up.

Look at this KnowledgeBase article:
http://digital.ni.com/public.nsf/3efedde4322fef19862567740067f3cc/44e99cc41aa39f538625694b005679c0?OpenDocument

Labview opens all VIS in Run mode

LV2013 PDS is opening all VIs in Run Mode. This is a global problem, not specific to one or a specific number of VIs.
If I create a new VI, save it, close it and re-open it, it's in Run Mode, not Edit mode. Nothing is set to Run When Opened, nothing is set to be locked without a password.
It's only on this installation; if I take my code to another machine, there's no issue.
I have deleted the labview.INI file, but the behavior repeats itself.
Any ideas?

Jed_Davidow wrote:
SCC is not configured; I use perforce, but it's not configued to use it or to treat read-only as locked. I have also checked out all the filed ahead of time with P4, so LV never sees them locked. The folders themselves are not read-only.
Also, I have created VIs outside of my P4 folder, and I have the same trouble.
Example:
Launch LV: Create a blank VI (comes up in Edit mode).
Save to Desktop (not within P4 control) as test.VI
Close
Open test.VI ---> It's in Run Mode
I have never seen this happen before.
Neither have I
I'll assume a reboot was attempted and did not change anything. I would attempt a repair of LabVIEW from the control panel and another restart.
Jeff

Vi will not open, instead Labview opens a search window for the vi

I have a vi in 7.1 that, while running, locked the PC. After rebooting, Labview could no longer open the code. Instead it acts as if searching for a sub-vi it cannot find.....itself. I've seen similar questions posted from years ago with the rare and only solution from an NI engineer using LabView development utilities.

Hi Freestream
What information were you able to find? Do you receive an error when you try to open this file? You can access the labview error log from C:\Documents and Settings\(User Name)\Local Settings\Temp for Windows 2000 or XP and C:\users\(User Name)\Documents\LabVIEW Data\lvfailure log for Windows Vista. There is a second log file for the previous time LabVIEW was run LabVIEW_versionsusername_log.txt. Also try opening the VI in a later version of LabVIEW. Let us know if you get a specific error message or .cpp error. Since the VI crashed in the middle of operation its also entirely possible that it has become corrupted and this error will not be reproducible.
Thank You
Eric Reid
National Instruments
Motion R&D

LabVIEW opening @ Bangalore, INDIA

Hi,
I have two labVIEW developer opening
* Experience: Minimum of 4+ years
* Should be able to handle the projects individually with minimal assistance.
* Engineering Degree is must
Position open for : Freelancers / Consultants / Full time employees.
Mail me your profile to [email protected]
Best regards,
Raja

Hello Friends,
Moog Aircraft Group, Bangalore is looking for LabVIEW and TestStand Engineers with 1 to 8 years of experience in test automation field. Please find the job description as mentioned below. If interested, please send the resumes to [email protected] or [email protected]
For more information regarding company and its product profile, please visit us at www.moog.com\aircraft
Job Location: Bangalore, India
Job Profile:
Design, Development and Configuration of Automated Test Equipment (ATE) for complex systems\sub-systems, simulation and control system environments.
LabVIEW and LabVIEW RT\FPGA proficiency (Desirable certifications include CLAD, CLD, CLA).
Familiarity with National Instruments Hardware Platforms. General Communication Protocols (GPIB, RS-232/485, EtherCat).
Exposure to Avionic Communication Protocols is an added advantage (ARINC, MIL1553) dSPACE®, Python, Matlab® \ Simulink® knowledge is an added advantage.
Aircraft systems/sub-system testing verification and validation environments.
Knowledge of Aircraft Actuation systems is an added advantage Process Standards (D0-178\CMMI) is an added advantage.
Note: 1) Please do not send the resumes, if you have attended the interview at Moog in last 6 months.
Regards,
Karthik SP

Any LabVIEW Opening at Jacksonville,FL???

Hi,
I have 2 + years experience in Functional Test development. I have 2 years of LabVIEW and TestStand Experience and aIso certified in CLAD.I am searching for a job in Jacksonville , Florida. Is there any opening here?

Looks like you made a mistake, by that name I can tell you, its not 'he' but 'she'.

Can LabView open a browser?

I would like to be able to open a Microsoft Internet Explorer window from a LabView program generated address. A user entered address though a Front-Panel Control would be fine to start me off.
This would seem to be a simple task compared to all the other web related possibilities. I've tried DataSocket (which I now understand to be geared to sending data across the internet, not for generating or reading web sites) and System Exec (giving the �IEXPLORE www�� as the �command line� input. Can anyone point me in the right direction? I hope eventually to create a server application offering real time images from a device controlled by LabView (the controlling part already works) but this seems to be in the far far distance at the moment. Any
help or example would be greatly appreciated.
Richard.

Take a look at the VI in the in Browser.vi.
Rolf
"R" wrote in message
news:[email protected]..
I would like to be able to open a Microsoft Internet Explorer window
from a LabView program generated address. A user entered address
though a Front-Panel Control would be fine to start me off.
This would seem to be a simple task compared to all the other web
related possibilities. I've tried DataSocket (which I now understand
to be geared to sending data across the internet, not for generating
or reading web sites) and System Exec (giving the "IEXPLORE www." as
the "command line" input. Can anyone point me in the right direction?
I hope eventually to create a server applicatio
n offering real time
images from a device controlled by LabView (the controlling part
already works) but this seems to be in the far far distance at the
moment. Any help or example would be greatly appreciated.
Richard.

Full time LabVIEW opening in Silicon Valley

My name is Jon Christensen and I have been recruiting in Silicon Valley for 15 years. I have a firm called SearchTech Solutions and one of our clients is looking for a senior LabVIEW developer. The info about our client and the position are below. Please contact me at 408 540 1800 or [email protected]
Company:
Our client is an aggressive startup that has developed and deployed technologies that are dedicated to making the streets safer by using leading edge technologies to solve a real world problem. They have funding and a consistent revenue stream, with systems installed in many cities across the United States.
Technologies:
They use GPS, Acoustics, Signal Processing, distributed wireless technologies and web technologies coupled with a very reliable backend based on .NET and SQL Server running LabVIEW.
Position:
This person will work in the software group (currently 4 people) developing LabVIEW applications that will reside on the server. There are number of new modules that need to be added to their current product (tweaking the GPS, where to listen, UI, etc). Whenever there is an event (some gunshot or sound is recorded), the server collects the information and stores it in the database (SQL Server). The application will make sense of all this information and look for patterns in the information. Scalability is also an issue that needs to be addressed.
Big plusses are going to be acoustics, noise cancellation, SQL Server, mathematics background and signal processing.
US Citizen is a very strong plus!

Hi Jim,
CTG has been asked to assist our client in staffing a LabVIEW Developer opportunity. This is a 200 hour, short term project onsite in San Jose, CA. This quick job will entail very little new development and will consist primarily of enhancements and modifications to existing code. If you are interested, please forward a copy of your resume (.doc or .txt) to the e-mail address listed below. I will contact you directly upon receipt of that information.
Thanks for your consideration!
Regards,
Jessica Owens, Sr. Recruiter
ctg Computer Task Group, Inc
phone: 800-992-5350
[email protected]
www.ctg.com
Backed by 39 years' experience, CTG provides IT staffing, application management, and consulting solutions to help Global 2000 clients focus on their core businesses and use IT as a competitive advantage to excel in their markets. CTG combines in-depth understanding of our clients' businesses with a full range of integrated services, proprietary service methodologies, and a proven track record of delivering solutions that work. More information about CTG is available on the Web at http://www.ctg.com.

LabVIEW opening in Kyle, TX (south Austin)

Primary Function:
The LabVIEW Development Engineer will be a key member of small team of LabVIEW developers that is responsible for developing and maintaining the company's energy storage SCADA systems. There is Core software that is common to all customers and customer specific software requirements as well. He designs control systems for XP products. We are not looking for long term contractors for this position, but someone devoted to our Team.
Primary Duties:
Writes LabVIEW Code.
Unit Tests and debugs code.
Designs, validates and maintains control systems (optional)
Mentors others.
Ability to travel up to 20% in support of remote sites and/or customer installations
Qualifications / Experience:
Bachelor of Science in Electrical Engineering or Computer Science.
National Instruments Certified LabVIEW Architect (CLA) or equivalent experience.
5+ years of designing, developing, implementing, and debugging LabVIEW and LabVIEW RT software.
Technical requirements - Hardware.
Broad knowledge of instrumentation and data acquisition technologies including PXI, NI Data Acquisition, LabVIEW Real Time, NI FPGA, and signal conditioning.
Strong hands-on hardware troubleshooting and debugging skills.
Technical requirements − Software.
Experience using Source Code Control Systems like Subversion (SVN) and TortoiseSVN.
Familiar with software communication protocols such at TCP/IP, UDP, and modbus.
Familiar with all current LabVIEW application architectures.
Experience connecting LabVIEW to third-party database systems such as MySQL.
Strong background in architecture design and development.
Good communication skills, both written and verbal.
Experience creating documentation for large scale LabVIEW projects spanning VI descriptions to system diagrams.
Experience writing software requirement specifications.
Excellent people skills, must be a leader.
Previous start-up experience is a plus.
Email your resumes to [email protected]

Dear Sir,
I would like to introduce myself over here. This is Vimal R. I had experience of 4 years in the instrumentation field .
Now I am looking for a change from my current assignment in india as well as foreign countries in the same field (instrumentation).Here with i have attached my CV. Please find it . I have enclosed my expectation and other details below in short.
Expectation and details :
Field: Instrumentation.
Experience: 4 Years, in lab view development, NI related hardware's, and other hardware.
Skills: Labview 7 to 2009, DIAdem, Test Stand,Machine Vision, Embedded Labview, Embedded C,C.
Certification: CLAD (Lab View Certification), CLD appeared.
Award Won: Rajapuraskar award, Rastrapathi Award in scouts,and Star fish Award @ 2008 and 2009 in apna technologies.
Expected CTC: 6-7 Lakhs/ Annum (in india), Negotiatable for abroad.
Current CTC: 4.2 Lakhs/ Annum,
For more details please look at the resume, and do the needful.
Contact me on: 09590580872
Email ID: [email protected]
Thanks and regards,
Vimal.R.
Attachments:
4 year Experience CV_v02.doc ‏73 KB

VSS and two versions of LabVIEW open is BAD

Wow,
So I had LabVIEW 2009 up for scratchpad code (so it would not try to add into my project in 2010) A trick I play to keep my scratch code out of my development.
I just got a second monitor and am still getting used to having "stuff over there">>>> and forgot to Close LabVIEW 2009 per my normal operation when I finish in my scratchpad.
Hit the old "Add to SCC" on some new vi's in the main project. They did add.... and LabVIEW 2010f4PDS went totally unresponsive in ways I've never seen. Yes I have SCC configured on both LabVIEW versions and auto-connect to VSS during launch.
Luckilly I save often- lost ZERO work but......Should I be able to connect to VSS for multiple LabVIEW versions simultaineously? or would that be a totally brain-dead way to cause hair loss?
Jeff

And no matter what you find out keep in mind that VSS is no longer under development by Microsoft and support will soon end.
See this link. Then switch over to SVN!
=====================
LabVIEW 2012

Labview crashes upon opening a specific VI

In LabVIEW 6.1 in Mac, LabVIEW crashes everytime I open a specific VI. I went to this article (http://digital.ni.com/public.nsf/allkb/8C333947DE8EC423862567AC00510975) also known as KnowledgeBase entry 1NB8NIU0. I downloaded Macsbug and followed instructions. When LabVIEW crashed, Macsbug openned. I typed stdlog, clicked enter, but no log was generated on the desktop as the knowledge base article indicated. Can anyone help me troubleshoot this? (I'm running Mac OS 10.4.9. Labview opens Mac OS 9 classic when it runs. I don't know if this has anything to do with it.)
Thanks,
Nathan Fast

Hi Nate,
This is odd. Do you have any previous versions of this file? If so, could you please let me know what may have changed in the code between when it worked and when it caused LabVIEW to crash? At this point, a workaround would probably be the best bet in order to get the code back up and running.
Best regards,
Steven

Open vi file with specific Labview version using batch file (Windows)

I want to open certain vi with using Windows batch file and to use specific version of Labview development system. I tried
"C:\Program Files (x86)\National Instruments\LabVIEW 2012\LabVIEW.exe" "path_to_vi"
"C:\Program Files\National Instruments\LabVIEW 2012\LabVIEW.exe" "path_to_vi"
to use 32-bit and 64-bit development systems respectively. However Labview opens file with version which was last used before. Are there any ways to force it use specified version?

No, it's a VI I wrote so that when I open any VI from Windows Explorer it will open it in correct version of LabVIEW according to it's source version (rather than the latest/last version of LabVIEW I opened). All it does to launch the right version of LabVIEW is to call System Exec with the path to the correct version of the LabVIEW.exe and the path to the VI - which is essentially the same as what your batch file is doing.
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

Quirk, Open VI Reference and LLB

I found a strange quirk opening a VI Reference (on a PXI). The "normal" method of doing this is to Open Application Reference (to find the remote site) then to Open VI Reference with the path to the desired VI. Darren Nattinger pointed out (in 2006) that you can use just the name of the VI, provided the VI is on the same folder or LLB as the current VI.
Caveat -- this behavior is present in LabVIEW 7.0 (I'm maintaining some "legacy code"). I suspect it will be present in later versions, but haven't (yet) tested it.
Quirk 1 -- if the VI in question has been downloaded (or deployed) to the remote site, and hence is in memory, then the "path" information isn't used, only the VI name. Thus if you have a path "C:\ni-rt\startup\MyVI.vi" specified in the Open VI Reference, but have absolutely nothing in the startup folder on your PXI, but have "deployed" your Project, this call will work, even though the "path" part of the argument is not valid. Useful when testing.
Quirk 2 (and the "real" reason for this post) -- if the VI is embedded in an LLB, it depends on whether or not it is a "Top-level" VI or not. Suppose the path is C:\ni-rt\startup\MyLib.llb\MyVI.vi. Consider two VIs in this LLB -- TopLevel.vi and SubVI.vi (where TopLevel is at the top level of the LLB, whereas SubVI is not).
Case A -- the LLB has actually been downloaded to the remote site. Doing an Open VI Reference, with either the full path or just the VI name, works, whether or not you are calling TopLevel or SubVI. Nothing surprising here.
Case B -- you are taking advantage of Quirk 1, and have not actually put the file on the Remote site (i.e. there is nothing at the path specified). You have, however, downloaded the LLB to the Remote. Doing an Open VI Reference with SubVI, whether with full path or just VI name, works fine. However, trying to open TopLevel fails, with Error 7 (File Not Found), whether using full path or VI name.
Summary -- Quirk 2 is that Quirk 1 has a quirk if the VI being referenced is a top level VI in an LLB.
[My apologies if this is common knowledge -- I failed to find this behavior documented, but may have overlooked something].

Bob Schor wrote:
I found a strange quirk opening a VI Reference (on a PXI). The "normal" method of doing this is to Open Application Reference (to find the remote site) then to Open VI Reference with the path to the desired VI. Darren Nattinger pointed out (in 2006) that you can use just the name of the VI, provided the VI is on the same folder or LLB as the current VI.
Caveat -- this behavior is present in LabVIEW 7.0 (I'm maintaining some "legacy code"). I suspect it will be present in later versions, but haven't (yet) tested it.
Quirk 1 -- if the VI in question has been downloaded (or deployed) to the remote site, and hence is in memory, then the "path" information isn't used, only the VI name. Thus if you have a path "C:\ni-rt\startup\MyVI.vi" specified in the Open VI Reference, but have absolutely nothing in the startup folder on your PXI, but have "deployed" your Project, this call will work, even though the "path" part of the argument is not valid. Useful when testing.
Quirk 2 (and the "real" reason for this post) -- if the VI is embedded in an LLB, it depends on whether or not it is a "Top-level" VI or not. Suppose the path is C:\ni-rt\startup\MyLib.llb\MyVI.vi. Consider two VIs in this LLB -- TopLevel.vi and SubVI.vi (where TopLevel is at the top level of the LLB, whereas SubVI is not).
Case A -- the LLB has actually been downloaded to the remote site. Doing an Open VI Reference, with either the full path or just the VI name, works, whether or not you are calling TopLevel or SubVI. Nothing surprising here.
Case B -- you are taking advantage of Quirk 1, and have not actually put the file on the Remote site (i.e. there is nothing at the path specified). You have, however, downloaded the LLB to the Remote. Doing an Open VI Reference with SubVI, whether with full path or just VI name, works fine. However, trying to open TopLevel fails, with Error 7 (File Not Found), whether using full path or VI name.
Summary -- Quirk 2 is that Quirk 1 has a quirk if the VI being referenced is a top level VI in an LLB.
[My apologies if this is common knowledge -- I failed to find this behavior documented, but may have overlooked something].
This will likely not apply at all to >= 8.0. LabVIEWs Open VI Reference will now distinguish cleanly between absolute path and just the VI name itself. If you use just the VI name the VI needs to be in memory or for a built application included in the app. The quirk about VIs in the same LLB as the currently active VI sounds very strange to me but it may still work.
However if you specify an absolute path, Open VI Reference will bark with an error if the VI can not be found at that location or if the VI already loaded in memory with that name has not the same absolute path. This is supposedly to make it very hard to create cross linking even when using VI server.
Rolf Kalbermatter
Rolf Kalbermatter
CIT Engineering Netherlands
a division of Test & Measurement Solutions

Open vi reference by string in executable

Hi all,
Scenario: A top-most vi (main.vi) calls two subvis (subvi1.vi and subvi2.vi) separately such that they run in parallel. subvi1.vi has a front panel that appears when called, subvi2.vi does not.
subvi2.vi uses Open vi Reference to get a reference to subvi1.vi. It then uses this reference in a loop and continually polls the property FrontPanel.IsFrontmost to determine if the front panel of subvi1.vi is frontmost. When it is frontmost, it performs certain actions. When it isn't frontmost - it doesn't.
This all works great in the development environment, but as soon as I build this 'scenario' into an application I get the following error:
subvi2.vi is generating the reference to subvi1.vi using the string "subvi1.vi" as an input to the path terminal of the Open vi Reference function. Why does this cause problems in a built executable?
P.S. Clearly this scenario is actually a part of my much bigger project, hence I don't have any simple vi's to attach
Message Edited by Thoric on 04-27-2009 01:06 PM
Thoric (CLA, CLED, CTD and LabVIEW Champion)
Solved!
Go to Solution.
Attachments:
crash.jpg ‏28 KB

Thoric wrote:
Norbert B wrote:
Thoric,
it's disturbing that LV is crashing on your system due to this error. What version of LV do you use?
LV 8.6.1 at least (i don't know which version was the first one) creates the following error:
LabVIEW: Open VI Reference no longer matches VIs in memory by filename. A filename is no longer sufficient because the full name of a VI now includes any owning libraries.
This error occurs even in the developement system.
I asume that the crash itself is created by handling of invalid references.
hope this helps,
Norbert
Norbert,
I am using LV 8.6 (not 8.6.1). I am using strings to identify vis, not paths. I believe the error you are encountering only relates to using paths for referencing vis.
If your assumption is correct and my crash is due the handling of invalid references, then I need to generate a path to the vi, rather then using it's name. But generating a full (non-relative) path might be tricky? If within subvi2.vi I use the 'current vi's path' function and strip it to determine the executable path, then add subvi1.vi, should that get me the path to subvi1?
THis really depends on how you did your build. If VI1 ends up as dynamic file vs part of the app, the paths will be different. Easy enough to check. Look at where your exe is and figure out if VI1 is there in the support/dynamics. If not it is probably inside the exe to the path would then be "My.exe.VI1.vi".
But I am speculating thats the issue so try to get more info.
Ben
Ben Rayner
I am currently active on.. MainStream Preppers
Rayner's Ridge is under construction

Open and run the VI using FP.Open from another VI

I would like to have LabVIEW open and run the VI when I open the second VI (number 2) from VI (number 1). I set the appropriate Execution options in File»VI Properties
to make both VI run when opened but it works only for the first vi and
when I open 2.vi from another 1.vi the second vi will open but not
run.Would u plz let me know how can I make the second vi run when I open it using FP.Open.
Attachments:
111112w.jpg ‏33 KB

There are several ways to start VI 2.
- use a invoke node of VI 2 which says : "run when opened"
- edit the VI properties of VI2 en set "run when opened" to TRUE
See attachment
Kind regards,
- Bjorn -
Have fun using LabVIEW... and if you like my answer, please pay me back in Kudo's
LabVIEW 5.1 - LabVIEW 2012
Attachments:
RunWhenOpened.PNG ‏33 KB

Labview Opening

Similar Messages

Maybe you are looking for