LabVIEW/La​bwindows CVI Freelancer - Programmer​/Tutor - Chennai based - CLAD

LabVIEW/Labwindows CVI  Freelancer - Programmer/Tutor - Chennai based - CLAD
Hi,
Open for short/long term LabVIEW/Labwindows CVI project.
Familiar with NI PXI (Digital/Analog/Serial IO/PMU etc). PXI modules analysis and comparison based on project requirement .
Familiar with NI LabVIEW Labwindows CVI & MS Visual Studio.NET programming.
Available as a freelancer.
Chennai based.
For any query please feel free to contact me at [email protected]
With project requirement in mind/paper will be great. 
Thanks for reading this post.
Regards,
Sithick H

Similar Messages

  • LabVIEW Freelancer - Programmer/Tutor - Singapore based - CLA

    Hello * ,
    Open for short/long term LabVIEW project.
    Familiar with NI PXI (Digital/Analog/Serial IO/PMU etc). PXI modules analysis and comparison based on project requirement .
    Familiar with NI LabVIEW & MS Visual Studio.NET programming.
    Available as a freelancer.
    Singapore based.
    For any query please feel free to contact me at drawsomecode (at) gmail.com 
    With project requirement in mind/paper will be great. 
    Thanks for reading this post.
    Regards,
    Drawsome

    Hi,
    Students are welcome to email me at [email protected] for help or enquiry on LabVIEW tutor / FYP oriented tutoring / FYP project.
    Drawsome

  • Other "NIDialog" Font when running CVI 2010 programm after 2012 runtime is installed

    I noticed a font changes when running a pre CVI 2012 programm with 2012 runtime.
    It appears to be the "NIDialog" Font unless it is "NIDialogMeta".
    The UI looks as it should when editing it in CVI 2010.
    Is this intended?
    It's making UI editing kind of a gamble...
    /* Nothing past this point should fail if the code is working as intended */
    Solved!
    Go to Solution.

    Yes, you're correct. It looks like the typeface that corresponds to NI Dialog has changed in CVI 2012. This is something that should have been explicitly called out in the readme, and I apologize for that oversight.
    NI Dialog is, by design, a "variable font". That mean that it's a font that can correspond to different typefaces in differect computers, since it's tied to an alias (DEFAULT_GUI_FONT) that can resolve to different actual fonts in different computers, different OSes, and potentialy (as in this case) different versions of the CVI runtime. What happened in this case is that a bug was fixed in CVI 2012 in that CVI was previously not taking into account the Microsoft font substitution table:
                HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\FontSubstitutes
    Going back many years now, the DEFAULT_GUI_FONT has corresponded to MS Shell Dlg. It seems to me that MS Shell Dlg is somewhat obsolete and so it turns up in the FontSubstitutes table above, so that applications to replace it with something else. In my PC, that becomes "Microsoft Sans Serif". Before CVI 2012, it was incorrectly not being replaced with Microsoft Sans Serif, whereas now it is.
    Sorry about this.
    Luis
    NI

  • Using DLL functions created with LabVIEW 6i in CVI 4.0.1

    I want use SQL functions from LabVIEW 6i in LabWindows/CVI 4.0.1. Building DLL with this LabVIEW-functions was succesfull, but after using DLL in CVI project and run, error message was generated: FATAL ERROR : LABVIEW.LIB was not called from a LabVIEW process. Can you help me? In attachment are VIs and build script for this DLL.
    Attachments:
    DLL.ZIP ‏24 KB

    The SQL toolkit appears to be an ActiveX program. Why not call the objects with activeX in CVI directly?
    There are several hits for labview.lib on ni's site. Goto http://search.ni.com/?col=alldocs&layout=TechResources&ql=a
    and search for labview.lib.

  • Interopérabilité entre labview et labwindows/CVI

    Bonjour,
    j'utilise labview 7.0 dans lequel je souhaite utiliser une DLL compilée avec LabWindows/CVI. Cette DLL contient une fonction de communication avec un équipement distant de type get_value.
    Donc, grâce à cette DLL, l'outils labview demande une valeur à l'équipement distant. La fonction CVI envoie la requête à l'équipement distant et attend la réponse de celui-ci avant de retourner la réponse sous labview.
    Donc l'exécution de la fonction CVI est assez longue mais entre l'envoie de la requête et la réception de la réponse, le processeur n'est pas utilisé. Néanmoins, durant l'exécution de la fonction, le rafraichissement de la fenetre labivew n'est plus opérationnel et de manière général, l'application labview sem
    ble gelée.
    Est-il possible de libérer le process pour labview au sein de la DLL sans en sortir ?
    J'ai essayé les fonction delay, process draw event et process system event mais rien ne semble libérer le process.
    Y a-t-il une solution?
    Merci

    Hello,
    La bonne vieille recherche d'exemples (Help-> Find Examples) reste toujours efficace. Je vous suggère d'aller faire un tour dans la partie MultiThreading. On y trouve toutes les principales fonctions pour créer des threads et y exécuter du code (en parallèle, donc !).
    Cet article est aussi un bon départ.
    Cdt,
    Eric M. - Application Engineering Specialist
    Certified LabVIEW Architect
    Certified LabWindows™/CVI Developer

  • LabVIEW position for an experienced programmer (immediate start)

    There is LabVIEW position available (immediate) in Houston, TX on a contract basis for an experienced programmer. Please send your resume at [email protected] or call 281-851-9062.

    Please include some details like Job Desc. , Salary Range, Where in Houston, Contract duration, etc...

  • What is the difference between LABVIEW and LABWIN/CVI?

    I want to take a course about one of these two softwares.
    I know a little bit about LABVIEW but I know nothing about LABWIN/CVI.
    What is the difference between them?
    Do they have different aplications?
    thanks
    Tzviel

    LabVIEW is a graphical programming language. It is made up of a user interface which is called the front panel and a block diagram where all the coding is done. CVI is National Instrument's C interface for virtual instrumentation. CVI includes a user interface complete with graphs, buttons, and other interface objects. However, the code is done in ANSI C. Some great features of CVI include the function panels, which provide a wizard interface for CVI functions, and code generation. CVI also easily integrates with National Instruments DAQ & GPIB devices as well as other intrument drivers.

  • LabVIEW toolkit for digital still camera - PTP protocol based

    Dear List,
    Just to let you know that a LabVIeW toolkit for PTP
    (picture transfer protocol)camera is available. PTP is
    the new standard for still imaging devices such as
    still camera and scanner, it does not require camera
    vendor extra special drivers (unlike Twain)and it's OS
    independant, thus being supported widely in modern
    high resolution digital still cameras. Interested
    people can check out this link:
    http://www.hytekautomation.com/Products/PTPCam.html
    Irene
    =====
    Irene He
    [email protected]
    www.hytekautomation.com
    www.geocities.com/irene_he

    Hello rbergs, 
    I apologize for just now responding to your post below but I would like to redirect you to a different resource that will be able to provide the necessary support for using the LabVIEW Interface for Arduino toolkit. Currently, this toolkit is only supported by posts on ni.com/arduino forum. If you have any additional questions regarding the LabVIEW environment specifically, please feel free to post any additional questions in this discussion forum. 
    Wes W
    Application Engineering
    National Instruments
    www.ni.com/support

  • Freelance LabVIEW Programmer

    Hi everyone!
    I'm here to offer my services to anyone who is in search of a freelance programmer.  I'm 24 and currently a 3rd year student in Electrical engineering .  I've been programming pretty intensively for almost 4 years now in my current job (part-time for now!).  I have a few projects under my belt, many of which are fairly extensive.  I have very good knowledge of radiofrequencies, specifically microwave range, ActiveX (COM in general), GPIB instrument control, OOP programming in LabVIEW, etc. etc.
    I'm simply offering my help because I enjoy programming in LabVIEW and would like to make a few extra bucks in my spare time working from home (being a full-time student with a job leaves me with only a few hours a week).
    My main fields of interest are RF and biomed but I will review any type of project that is offered to me.  Hourly rate is very negociable, I'm a student after all!
    I'm located in Montréal, Québec, Canada (Oui, ma langue maternelle est le français (québécois )!
    Anyone looking for more information can contact me at: [email protected]
    Thanks for the interest!
    Yohan Belval

    Thanks for the info!
    Sorry for the inconvenience.
    Moderator: Please delete thread!
    Message Edited by NahoY on 09-24-2007 11:15 AM

  • Import CVI Instrument Driver in LabView 8.6

    Hi,
    I am working on Instrument Driver and have code developed in LabWindow/CVI. I have got the information of importing those code in LabVIew through Import CVI Instrument Drive option in Tools»Instrumentation but can't able to see such option on the stated menu. We are using LabView 8.6 Evaluation Version and about to get the License of the same. Does such option unavailable in 8.6 version or am i missing somewhere??
    Please help me !!
    Thanks in Advance,
    Vivek
    Solved!
    Go to Solution.

    Hey Thanks Alot Dennis. I didn't know we need to perform such things. But Why we reaaly need to install those Wizard. If possbile would definitely like to know the reason.
    Thanks,
    Vivek

  • LabVIEW programmer needed for full time position, Orange County CA

    Anaheim CA 92801
    [email protected]
    Job Title: Project Manager
    Job Type: Permanent
    Job Location: Anaheim CA
    Main hardware expertise required: Compact DAQ/RIO (cDAQ,cRIO), Enclosures, Cabling, Other (please comment)  
    Main software expertise required: LabVIEW, LabVIEW Real-time (RT)
    Job Description: LabVIEW programmer needed to program and update a series of technologies while using NI CompactRIO and Single Board RIO applications. Some basic networking and basic electronics experience required.
    40 hrs/wk at our Orange County facility.
    What qualifications and T&M certifications do you require? Technical, LabVIEW Certified Developer Prefered
    Salary Offered: $60K-80K based on experience and qualifications  
    The attachment is a picture of the prototype ETU unit. The DBA of the company is "GreenLink Systems," our website is www.greenlinksystem.com
    Attachments:
    ETU and Staff.jpg ‏186 KB

        Bill,
    We are able to offer you the help you need on
    this.  I work for a LabVIEW/test-system consulting group based here out
    of Salt Lake City...not too far if a quick trip is needed.  Among the
    six of us, four of us are former NI employees and we count with a lot of LabVIEW experience and regularly do
    contract work, local and remote.  This sounds interesting and right up
    our alley as far as experience goes.  I'd refer you to our website for
    further info about different projects that we've done for many
    clients.  www.mooregoodideas.com.
    If this seems workable for
    you, feel free to shoot me a note at [email protected]  I'd be
    curious to know more about what you're after and how we can help you
    out. 
    Thanks,
    Jim

  • Can't step into CVI step that calls LabVIEW DLL?

    Windows 2000 SP1
    TestStand 2.01f
    LabWindows CVI 6.0
    LabVIEW 6.1 Runtime
    We have a framework based on TestStand and CVI. A customer has supplied us
    with a DLL written in LabVIEW 6.1 and packaged with the Application Builder
    that we need to call from a CVI test library DLL. They say they can't
    supply us with a non-LabVIEW implementation. We installed the LabVIEW 6.1
    run-time. We added code to the CVI test library to dynamically load and
    unload the LabVIEW DLL using LoadLibrary and FreeLibrary. LoadLibrary is
    called in a function in the MainSequence Startup step group, FreeLibrary is
    called in a function in the MainSequence Cleanup step group.
    Things run as expected when the CVI DLL is built as Release or Debug and the
    CVI
    adapter is configured to run in-process.
    However, if we try to debug CVI DLL by building it as Debug and configuring
    the CVI adapter to run in an external instance of CVI, things hang the first
    time we try to step into, or run, a CVI test library step that calls one of
    the functions in the LabVIEW DLL. On the Applications tab in Task Manager,
    the item named LabVIEW is marked as 'Not Responding'. The only way to
    recover is to kill the LabVIEW process, which takes down CVI and TestStand
    with it. If none of the LabVIEW DLL functions are called, no problems are
    seen (no hang).
    I assume the problem has something to do with the library getting mapped to
    the wrong process space (TestStand v. the external CVI instance). Is there
    any way to solve this problem? Any ideas or suggestions would be
    appreciated.
    Joe

    > Out of curiousity, what happens if you attempt to debug your DLL from
    > CVI? For example, configure TestStand to run its steps 'inProcess'...
    > but then close the TestStand application and in CVI, configure it so
    > that the Specified External Process dialog points to TestStand's
    > SeqEdit.exe (CVI launches TestStand when debugging the project). Once
    > TestStand is running, run your test and set your break points as
    > usual, you should be able to step into the CVI code if nothing else.
    > If not, I would be interested in hearing what problems you encounter.
    When 'debugging' SeqEdit from CVI, we experienced no lock up.
    Thanks for this suggestion. Debugging from CVI is a workaround for now,
    though not highly desirable as it is reverse from normal debug proc
    edure
    (user can't step into CVI from TestStand). Still would like to know if
    'normal' debugging of this problem is possible.
    > The nice thing about debugging directly from Labwindows/CVI while
    > TestStand runs 'inprocess' is that you can avoid some library linking
    > errors, which may be the source of the troubles you are seeing.
    The problem appears to be general to LabVIEW DLLs called from an external
    instance of CVI under TestStand. We were able to reproduce the problem with
    a simple LabVIEW VI compiled to a DLL, then called from a simple CVI DLL
    under TestStand. We will package up some sample code and submit it to NI
    tonight or tomorrow.
    Thanks for you help.
    Joe

  • Should i choose Labview or CVI

    I am a student of automatic control in VN .
    I want to learn a language that can help me to progam app.s to control automatic system .
    I 've ever read  alot and i see that Labview and  LabWindows/CVI seems to be the best suitable softwares . But i also see that may be they have equivalent ability .
    So what should i choose ?     

    All good answers above.
    It really boils down to personal preference.  There's the good, the bad & the ugly in any language.  All languages require time to learn and to learn to code well.
    The advantage that LabVIEW has over any programming language is the cult following and superb assistance you can get within this forum. 
    Far superior to any vxWorks forum....   

  • Can I convert Labview panel to Labwindows/CVI uir file

    I a project that I want to convert from labview to Labwindows\CVI.
    I don't want to call my VI's from LabWindows.
    It is possible to convert some Labview fronts panels to *.uir files (Labwindows/CVI)
    Thanks

    Hi Artus!
    Unfortunately there is no automatic way to convert a LabView Front Panel into a Labwindows UIR.
    The only way you can do this is by creating a new interface and adding all the elements that you need, but this way would actually mean rebuilding everything based on something you already have. Sorry about the bad news
    I wish you the best day!
    Oswald Branford

  • Is LABVIEW better then LABWIN/CVI ?

    I am going to take a NI course just need to decide if it is going to be LABVIEW or LABWIN/CVI.
    I have been working a bit with LABVIEW and it seems like you can do more things with it then with LABWIN/CVI?
    Am I right or not?
    Please let me know what do you think? which one is better for test engineering.
    thanks

    That's not the kind of question to be posted here
    You may have noticed that this is a LabVIEW forum. Do you really expect that people here could tell you that LabVIEW can't compete with other programming languages (even developped by NI...) ?
    OK I'll do it :
    Nooo ! Never use LabVIEW ! It's the worst tool I'have ever used! Look : I'm bald, my teeth are falling, my wife just left me (hum... may be I should avoid that one, she is complaining...), my dog bite me, and I'm chased by a giant female rabbit that want to fight on the beaches...
    May be you should try elsewhere ?
    Chilly Charly    (aka CC)
             E-List Master - Kudos glutton - Press the yellow button on the left...        

Maybe you are looking for