Labwindows requirements

Hi all...
I am having 4yrs exp in LabWindows... now am working on contract basis at Keltron. I am searching for an opening in labWindows.. particularly in Chennai and bangalore... but i hardly found any...
i dont knw whethr i am searchin in the right way... In which all companies they hav labwindows... to name a few...
plz reply me....

mels is having an opening for labwindows in chennai. But you can post this in the job section right?

Similar Messages

  • Labwindows recompiles files when I switch from the development environment to another application

    I am writing a labwindows driver, but having issues with the environment itself.  I am able to compile the .c file for the driver, and my panels are working.  I am having problems with labwindows recompiling the .c file even though nothing has changed.  It is a random problem that I have seen before, but never managed to get around.  The problem shows up in a variety of instances.
    I.E.  While in interactive execution, I can click on another application on the taskbar (internet explorer, email, etc.)  and labwindows displays a message that the c file is being recompiled.  Nothing in the file changed!  Why does it try and recompile when it is simply losing focus?  This is 'random'.  Just when I think I have found a way to reliably reproduce the issue, it quits recompiling when I switch applications.  I have tried playing with the build options, but haven't had any repeatable success.  I even tried to enable the -o option, but is still recompiles the file.  (maybe -o won't work on a driver since it won't build without a main?)  I have even had issues with calling printf in a function during interactive execution.  It recompiles the c file for no apparent reason right after the stdio window prints the message.  At this point, the stdio window closes, and labwindows pops up the compiling message again.  It kills my interactive session, and I have to redeclare all of my variables to continue checking out my driver.
    I see the same issue randomly when I go back to the project from another application. (Click on labwindows in the taskbar, and it immediately compiles the c file.)
    I have seen this in other projects, and it appears that the issue is limited to instrument drivers.  When labwindows pops up the message that it is compiling files it is almost always a driver that is loaded as an instrument.  I played with unloading the instrument but leaving the .fp in the project, but I don't think that worked. (It has been awhile since I tried to figure this out.)  When working on a driver, it would be difficult to unload the .fp or not load the instrument anyway.
    (I just clicked on labwindows in the taskbar to see if I left anything out.  Labwindows popped up the message that it was compiling the c file.  It appears that I can go back and forth between the labwindows icon in the taskbar and the cvi icon ~15-20 times and then labwindows will recompile the file.  I even walked away from my computer for a couple of minutes, and it compiled when I came back and clicked on the labwindows icon.) 
    I am running labwindows 9.1 (but have seen this on 8 also)
    The files are on a network drive.
    (Could it be mcaffee or some network security stuff confusing labwindows?)

    My pc is currently running Windows XP sp3.
    I first saw this issue when I went from LabWindows 7.1? to 8.1?   I am sure that I had the issue in 8.1 
    I was able to reproduce the issue in production on a pc running windows 2000.  (Which is what I had at my desk previously, and had seen the issue.)
    I asked another member of the test engineering group, and I am not the only one seeing the issue.
    One of the earlier replies mentioned the auto save feature.  When I went to production to see if I could reproduce the problem there, I opened CVI and explorer.  I wanted to check the time-date stamp on the .c file that keeps recompiling.  The time-date stamp was a day old, and did not change when the period of time for auto save was passed.  (It probably would if I made changes but didn't save the file?)  I was able to switch back and forth between the explorer window and cvi, and the file would recompile.  I played with turning off the auto save, enabling the build status window, making the -o option compatible with cvi 5.0, displaying the build status column, etc.  It appeared at one point that it had quit recompiling when switching between applications.  I went back to my desk, and tried to match the settings, but never reached the same conclusion.
    There is not anything special about the project I am working on.  It is a labwindows driver for a pxi module.  There are only three files in the project, the .c .h and .fp.  The .c file keeps getting recompiled at seemingly random times.  It is especially frustrating during interactive execution while testing my code/function panels.  If I switch to another application and back, I almost always have to start over because compiling the file closes the interactive execution.  I have to redeclare all of the variables, and re-run any of the setup panels that are required.  (I have to open the DRM, load the module fpga/dac, and then I can run the panel I am actually trying to test.)  I have similar problems when trying to troubleshoot with printf statements, as it seems to recompile when focus switches to the stdio window.  I have resorted to a test project, where I can add the function calls and skip having to do any work via interactive execution.
    I haven't been able to find anyone outside of where I work reporting the same issue.  Maybe it has something to do with IT/viruscan/etc.  It is definately a strange issue.
    (I have switched back to CVI several times while writing this, and the .c filed recompiled about 20% of the time.  At one point,  I had left the build options dialog open when switching back and forth.  I did not change any options, but the .c file recompiled when I closed the options window?)
    Occasionally, when I see what appears to be the recompile message flash up, my interactive execution does not halt.  I.E. I don't have to redeclare my variables.  It is sometimes hard to see what the message says, you just see a dialog box pop up and disapear really quickly. 

  • How to use CAN256 and CAN257 in Labwindows CVI?

    I am trying to learn about CAN programming in LabWindows CVI. None of the samples do anything other than generate cryptic error messages. I do not have a card or interface device yet, but reading in the help files I found this:
    "NI-CAN provides a virtual CAN card with two interfaces, CAN256 and CAN257. The two virtual interfaces are connected by a virtual bus. When you write CAN frames to one virtual interface, those frames are received by the other virtual interface, and can be read as channels. This feature allows you to read and write CAN data in the same manner as two real CAN interfaces connected by a real CAN cable. The conversion does not require real NI CAN hardware, and your application is not required to check for specific CAN IDs."
    I modified the Waveform ouput project and add CAN256 to the dropdown in the uir file. However when I run it, I get the same error message as always, error -1074388725.
    Is there an example CVI code someplace to demonstrate the use of these virtual channels?

    Thanks Drew.
    Ultimately, my customer provided me with a WriteCAN256.vi and ReadCAN257.vi that were perfect for my needs. The WriteCAN256.vi along with my NI USB 8473s allowed me to provide data collection on multiple CAN devices and to verify that my Software can handle all data types from CAN devices.
    Note: My customer allowed me to share his .vi's. They are enclosed ...
    Best Regards,
    Don W
    Attachments:
    CanBus Read (Frames)_85.vi ‏55 KB
    CanBus Write (Frames)_85.vi ‏48 KB

  • How to use COM DLL in LabWindows

    Hello
    I have a COM .dll which looks like that when opened with dll export viewer:
    I would like to use the Get4AxisPos function in LabWindows.
    I understood that, as I only have the .dll, the only way of calling these functions are with the LoadLibrary() and GetProcAddress() functions.
    My problem is that the Get4AxisPos function is not of type Exported Function but COM Method so I don't know how to use it in my LabWindows project!
    My questions are: Is it possibleto use this dll in Labwindows? If yes how?
    Thanks
    Solved!
    Go to Solution.

    Hi ,
    I am new to C++ and COM  .
    i need to implement a client application in C(lab windows CVI) , server is a c++ COM object.
    steps followed by me
    ---> accessed the registered COM object with Labwindows CVI active x controller template,output was a c file which is implementation of the class names in COM (interfaces).
    I can use majority of the functions directly from the generated, but i need to implement some event functions like message box events and then use it.
    I have seen one method of accessing in C++ client sample ,
    which implements Queryinterface function...takes the IID_Unknown as input and returns interface pointer(inhereted static_castof the required class, uses static_cast for that) as output.
    when i try to follow up the same in c , i am lost  with the inheritance concept.
    In short i need to send IID Unknown to the Queryinterface function and should get the interface pointer of message box type or other class type ...
    Sorry for the long mail,Please guide me
    Thanks in advance ,
    Satish

  • Labwindows CVI 2010 and GetProcessAddress()

    I am using Labwindows CVI 2010 v10.0.1 after upgrading from version CVI 2010 v10.0.0. After the upgrade, I have a compile error from a statement that compiles just fine in the previous version. The error is:
    "Operands of = have illegal types 'pointer to __stdcall int function(int,pointer to char,pointer to char,pointer to char,int,pointer to char,pointer to char)' and 'FARPROC'."
    What causes this error is the following statement in the code:
    my_FP = GetProcAddress(dll_handle, "DLL_FUNCT");
    and the definition of my_FP is:
    int __stdcall (*my_FP)(int x, char y[], char z[], char *m, int g, char A[], char B[]);
    (function names and parameters have been changed for simplicity)
    As I said, this line compiles just fine in 10.0.0, but not in 10.0.1. Is there a specific update to the compiler that will cause this error? What can be done to fix this?
    Thank you very much for your time and help.
    Solved!
    Go to Solution.

    You're correct. This was caused by a change in CVI Windows SDK headers that took place in version 2010 SP1. The change was associated with bug fix #275934. Unfortunately, this bug fix introduced this undesirable side effect of requiring a cast for any function that returns a FARPROC function poinrter (such as GetProcAddress). Upon further reflection, this side effect is unacceptable, and needs to be corrected in the next release. This is being tracked internally with bug ID #336341.
    I'm really sorry for this inconvenience. Until the problem is resolved, using the typedef & cast solution that you already implemented is a valid workaround.
    An alternative workaround, in case you're worried about other projects, or other functions, where this error might also pop up, is to edit CVI2010\sdk\include\windef.h and replace the following FARPROC definitions (in lines 226 and 230, respectively):
    typedef INT_PTR (FAR WINAPI *FARPROC)(void);
    typedef int (FAR WINAPI *FARPROC)(void);
    with:
    typedef INT_PTR (FAR WINAPI *FARPROC)();
    typedef int (FAR WINAPI *FARPROC)();
    Doing this will avoid the problem throughout a given installation of CVI.
    Luis
    NI

  • Conversion of an Instrument Driver from LabWindows/CVI to LabVIEW

    Hello All,
    Conversion of an Instrument Driver from LabWindows/CVI to LabVIEW
    http://zone.ni.com/devzone/conceptd.nsf/webmain/9A93316BEBEDB17786256FA300675A0A 
    But I can not find any hyperlinkt to download
    "LabVIEW Interface Generator for LabWindows/CVI Instrument Drivers"
    Is there any evaluation version for downloading?
    Thanks,
    nonomiya

    So strange,
    I go through three pages but does not find any entry for download,
    hmm...,
    1. After press the hyperlink,
    See Also:
    LabVIEW Interface Generator for LabWindows/CVI Instrument Drivers
    2. and for a resuest info. form.
    3. press download..
    ====
    LabVIEW Interface Generator for LabWindows/CVI Instrument Drivers
    System Requirements
    NI LabVIEW 7.1 or later
    Windows 2000/NT/XP
    Use the LabVIEW Interface Generator for LabWindows/CVI Instrument Drivers to create LabVIEW VIs for VXIplug&play and IVI-C instrument drivers from function panel (.fp) files.
    Instrument Driver Network
    Before using the conversion utility to create a new instrument driver wrapper, please visit ni.com/idnet to see if a LabVIEW Plug and Play instrument driver is available for your device. The Instrument Driver Network (IDNET) provides support for more than 3,000 different instrument models from over 170 different instrument vendors.
    Recommendations
    This utility was created for developers of C-based instrument drivers who wish to provide a LabVIEW interface, but do not develop a LabVIEW Plug and Play driver. By developing the C and LabVIEW interfaces together, it keeps the components synchronized, and eliminates the need for customers to create their own LabVIEW interfaces. Vendors should distribute the LabVIEW wrapper files with the associated VXIplug&play or IVI instrument driver, so that end users do not have to visit multiple web sites to download the complete driver.
    If you are not an instrument vendor, we recommend that you use this utility only if you have instrument driver expertise. Access to the instrument driver source code is preferred, in case you need to edit the C instrument driver in LabWindows/CVI.
    After generation, the wrapper VIs should be tested with the instrument.
    Instructions
    Once you install the software, simply access the utility from the Tools>>Instrumentation>>Import CVI Instrument Driver...menu in LabVIEW. This software replaces the built-in tool and provides feature enhancements.
    For additional information on this utility, view the resources below.
    Readme for the LabVIEW Interface Generator for LabWindows/CVI Instrument Drivers
    Submit your Driver
    Visit the Instrument Driver Network
    nonomiya

  • Does the USRP SDR require LabVIEW Communications?

    I've recently installed LabVIEW 2013 on my machine, along with a whole bunch of toolkits:
    LabVIEW 2013 English
    VI Package Manager
    LabVIEW 2013 Control Design and Simulation Module
    LabVIEW 2013 Datalogging and Supervisory Control Module
    LabVIEW 2013 MathScript RT Module
    NI LabVIEW 2013 LEGO(R) MINDSTORMS(R) NXT Module (English)
    NI Vision Development Module 2013
    LabVIEW 2013 FPGA Module (English)
    Xilinx Compilation Tools 14.4
    LabVIEW 2013 Real-Time Module (English)
    LabVIEW 2013 Touch Panel Module
    LabVIEW 2013 Robotics Module
    NI SignalExpress 2013
    LabVIEW 2013 Sound and Vibration Measurement Suite
    LabVIEW 2013 Statechart Module
    LabVIEW 2013 for myRIO Module
    NI Real-Time Execution Trace Toolkit 2013
    LabVIEW 2013 System Identification Toolkit
    LabVIEW 2013 Digital Filter Design Toolkit
    LabVIEW Modulation Toolkit 4.3.4
    LabVIEW 2013 VI Analyzer Toolkit
    LabVIEW 2013 Database Connectivity Toolkit
    LabVIEW 2013 Report Generation Toolkit for Microsoft Office
    LabVIEW Spectral Measurements Toolkit 2.6.4
    LabVIEW 2013 Advanced Signal Processing Toolkit
    LabVIEW 2013 PID and Fuzzy Logic Toolkit
    LabVIEW 2013 Adaptive Filter Toolkit
    LabVIEW 2013 DataFinder Toolkit
    LabVIEW 2013 Desktop Execution Trace Toolkit
    LabVIEW 2013 Multicore Analysis and Sparse Matrix Toolkit
    LabVIEW 2013 Electrical Power Suite
    LabVIEW 2013 GPU Analysis Toolkit
    LabVIEW 2013 Biomedical Toolkit
    LabVIEW 2013 NI SoftMotion Module
    NI Motion Assistant 2013
    NI Vision Builder for Automated Inspection 2012 SP1
    NI DIAdem Professional 2012 SP1 (English)
    LabWindows/CVI 2013 Development System
    LabWindows/CVI 2013 Real-Time Module
    LabWindows/CVI Spectral Measurements Toolkit 2.6.4
    LabWindows/CVI Spectral Measurements Runtime 2.6.4
    LabWindows/CVI SQL Toolkit 2.2
    LabWindows/CVI Signal Processing Toolkit 7.0.2
    LabWindows/CVI PID Control Toolkit 2.1
    LabWindows/CVI Execution Profiler 1.0
    Measurement Studio 2013 Enterprise Edition for Visual Studio 2012
    NI General Security Patch Q2 2013
    NI TestStand 2013
    NI ELVISmx 4.5
    NI DAQmx 9.7.5
    Xilinx Compilation Tools 10.1 (Requires Additional Xilinx Compilation Tools DVD)
    NI Device Drivers - February 2013
    I wanted to follow this tutorial with the USRP 2932, which will arrive soon, but I later found out that I don't seem to have any of the LabVIEW Communications. Will not having those prevent me from using the USRP radio? If not, then are there any restrictions on what I can do with the radio without Communications?

    Hi BreadLB,
    The link to the tutorial that you posted is based on LabVIEW Communications System Design Suite, a new software environment designed to accelerate algorithm prototyping and over the air testing.  It is a completely separate and independent environment from LabVIEW.  See my post here for more details.  You can also download a free 30 day evaluation copy here.  Your hardware is supported with both LabVIEW and LabVIEW Communications.
    The NI 2932 is a network based USRP, and it has a small onboard FPGA.  Because of that, the FPGA on that specific product is not a LabVIEW FPGA target.  The NI 294x/5x family has a large Kintex 7 FPGA and can be programmed using LabVIEW FPGA or LabVIEW Communications, like in the tutorial that you posted.  The NI 2932 can be used with your host PC and LabVIEW for a wide variety of applications.  Unfortunately the tutorial that you linked in your post requires the NI 294x/5x hardware and LabVIEW Communications.  If you have questions about a specific application for your 2932, please post more details and we would be happy to help.

  • Can C# dll's be integrated with a LabWindows project?

    Hi,
    I've integrated C++ dlls into LabWindows projects before, but recently I've been given a C# project that I would like to use instead of deconstructing the source and reconstructing it in C++.
    Is there any way of doing this and if so what are the differences between C++ and C# integration? Or am I looking at a minimum of a C++ wrapper?
    Solved!
    Go to Solution.

    Okay, have made progress but I have a question regarding object destruction.
    When I create a link to the C# dll I get a .fp, .c, and .h file which I naturally build into my project
    At the top of the .h file are listed the following:
    // Global Functions
    int CVIFUNC Initialize_TB_USB_Comms(void);
    int CVIFUNC Close_TB_USB_Comms(void);
    // Type: DipoleRxUSB.USBInterfaceExternal
    int CVIFUNC DipoleRxUSB_USBInterfaceExternal__Create(
     DipoleRxUSB_USBInterfaceExternal * __instance,
     CDotNetHandle * __exception);
    I note that there is no Destructor type call to compliment the Create
    In the required functionality I call the Initialise_TB_USB routine, then the Create routine - followed by all the other stuff I need to do, and finally the Close routine.
    However I know from experiment that this doesnt destroy the object created by the Create routine, as if I come in again I can still access the previously created objects functions.
    So how do I go about destroying the instance of the dll I assume I've created. I have put a default constructor and destructor in the C#, but this doesnt seem to have had any effect.
    What am I missing?

  • How to create constellation diagram using Labwindows?

    I am using the labwindows CVI 2009 version. Is it possible to create Constellation diagram using this software?

    I believe you may require a Modulation Toolkit (Modulated Signal Processing for LabVIEW and LabWindows/CVI).
    -Ciao

  • Running a LabWindows/CVI application created and built in Windows XP Serv.Pack 2 on a Windows 2000 computer

    I have created an application using LabWindows/CVI on my computer. I would like to install this application on a Windows 2000 machine but  I receive a message saying something like  "This program requires Windows XP service pack 2". 
    What can I do to make this work. 
    I am using LabWindows/CVI version 2010.
    Any Ideas?

    OK, Thanks, I will try that.
    Regards
    // Mikael

  • Measurment studio will not recognize LabWindows/CVI installation?

    It order for me to use the Driver factory program to make a DLL, the program requires that LabWindows/CVI version 5.0 or greater be installed. Version 5.5 was installed first and Measurment studio does not recognize it. After installing the DAQ software, MAX does recognize both LabWindows/CVI and Measurment studio. Help!
    Steve

    Hi Steve,
    What the IDF does, is
    (1) Look for the installation of CVI in the registry under HKLM/Software/NationalInstruments/CVI/xxx. "xxx" being the version number.
    (2) If there are multiple CVIs on the machine, IDF uses the highest version number of CVI located i.e.if you have
    HKLM/Software/NationalInstruments/CVI/5.0
    and HKLM/Software/NationalInstruments/CVI/5.5 it will pick 5.5.
    (3) IDF will then look up the installDir key under this folder.
    If either of (2) or (3) fails, you get the message you've been seeing.
    So what do you see under that registry location ? Is the registry version folder, or the installDir key missing?
    It is possible that the machine had installed a higher version of CVI , then uninstalled, but the folder a
    nd key is still there, so you have a key with a higher version of CVI, with the installdir key pointing to a "" value, instead of a valid path....
    If things do appear fine in the registry, then please reconfirm the software you have installed, as i under stand it, you have CVI 5.5, then installed MesurementStudio 6.0 ? I can try to then reproduce this.
    I sincerely apologize for all the trouble that you have been having...I hope this makes things little clearer and hopefully we can get you started soon..
    With regards to the other thread that you pointed to , it's possible that the evaluation CD did not install all the registry keys or installed them to a different location, or the user, did not install CVI at all...
    Best Regards,
    Nandan
    Nandan Dharwadker
    Staff Software Engineer
    Measurement Studio Hardware Team

  • LabWindows/CVI Idea Exchange

    National Instruments introduced the LabWindows/CVI Idea Exchange for submitting and voting on feature requests to be included in future versions of LabWindows/CVI.
    The LabWindows/CVI R&D team is committed to reviewing every idea submitted via the LabWindows/CVI Idea Exchange, so start posting your ideas today!
    Adri Kruger
    National Instruments
    LabVIEW Product Marketing

    One of the more valuable tools within LabWindows is the ability of the editor to fill in struct elements given the struct name. I also work with Eclipse-based tools for embedded systems work, and it has a similar ability. Unfortunately, whereas Eclipse dynamically analyzes the code as it is written, and can provide stuct elements (and other variable information) as soon as the programmer types it in, LabWindows cannot provide this information until after the code has been successfully compiled. As this may or may not happen for some time after the file has been started, or major changes begun, it is almost useless.
    Another useful tool that Eclipse offers that LabWindows does not is the ability to refactor variables and other symbols. Again, Eclipse dynamically tracks the code as it is written, not requiring compilation; refactoring is similar to global replace, except that it tracks the 'C' usage of the symbol and only changes the proper usage. So, for instance, if I use a local variable named "X1" in three different subroutines, and refactor "X1" to "X2" in one of them, only the variable in the particular routine gets changed.It works with any C symbol, including routine names, global and static variables, and structures.
    As a matter of fact, I would encourage NI to look into the possiblity of basing LabWindows on the Eclipse platform, as Atmel did in replacing its proprietary Studio software with an Eclipsed-based version. This would enable users to take advantage of a large number of available Eclipse tools, such as source-code management.

  • UK based LabWindows developer available for contract.

    Experienced software engineer available for contract LabWindows/CVI development
    in the south of England.
    Recently completed projects at Motorola and Panasonic.
    Details on my web site http://www.hhsw.cwc.net

    Dear Sir,
    I would like to get an opportunity to participate in your upcoming or ongoing projects and work for you as a team member. I am a final year MSc Electrical and Communications Engineering student at University of Greenwich UK. Please give me some task to deliver as my MSc final year project or it could provide results for my project. From this experience I intend to move to enhanced certification level and have an experience of working with professionals in the industry.
    My experience of LabVIEW programming and hardware integration is two years plus and I have successfully done my CLAD LabVIEW certification at NI Week last year in London. On my job I was responsible to interact with clients, gather their requirements, suggest suitable hardware modules and then program and integrate to provide deliverable solution.
    Please find my CV attached and contact me at your most convenient. I can work in your South East office at Northolt if required.
    Best Regards,
    Harris Junaid
    Cell: 07813 764372
    email: [email protected]
    Attachments:
    Harris_Junaid(CV).docx ‏24 KB

  • NI USB-6501 - 24-line Digital I/O (NI-DAQ) with LabWindows/CVI 7.0 ?

    Hi
    Can I use a recent NI USB-6501 - 24-line Digital I/O (NI-DAQ) with LabWindows/CVI 7.0, even if Labwindows/CVI 8.x is required ?
    Thank you
    Dayn
    Solved!
    Go to Solution.

    Hello.
    In DAQmx Readme, you can see which version of CVI are supported by the actuel DAQmx version. For a 6501 card, 8.7.2 or 8.9.5 DAQmx versions will work.
    Regards

  • Does LabWindows/CVI support C++?

    Hi there,
      I have been using labview for long time and we are looking for another way to improve the performance and labwindows/CVI seems to be a good choice. But here I got few questions
    1) Does it support C++ also?
    2) Could I compile the LabWindows/CVI applicaiton as a standalone program using in other computer without labview installed?

    Hi dragondriver,
    are you using CVI or LabVIEW??!? 'Cause here we are on the CVI board 
    Anyway, whichever is the system you are developing on the Run-time Engine must match the requirements for the executable. As per CVI, the runtime must be of the same level or higher that this. That is why you cannot run a CVI2012 executable with a CVI7 IDE or runtime installed, while it is safe to so the opposite. I do not know the state of the art with LV: in the past the release of the development system and that of the runtime needed to match exactly (infact you could have several LV runtime installed on the same system).
    You cannot expect of course that a CVI executable can run on a system with the LV runtime installed (and vice versa)!
    With reference to your last question, Traditional DAQ and DAQmx are completely different products, so installing one of them does not affect the other. Additionalle, you cannot mix commands from both environments in the same application: either you develop using old Traditional DAQ functions or you move entirely to the new DAQmx. You can have both of them installed on the target system.
    Proud to use LW/CVI from 3.1 on.
    My contributions to the Developer Zone Community
    If I have helped you, why not giving me a kudos?

Maybe you are looking for