Uograding from labview 8.5 to 2009

I'm thinking about upgrading from LabVIEW 8.5 to 2009.  We currently call a large number of VIs from TestStand 4.01 - What risks do you see in making this move (i.e. drivers, breaking code)

The same risks one would see in updating, from, say 7 to 8, or 6.1 to 8.5. If you're using Toolkits then you should first check to make sure there are 2009-compatible versions of toolkits. As far as drivers are concerned, it's the same thing. What drivers are you using? If it's DAQ, then just make sure you get the latest DAQ software.
Some things will be different, but nobody can predict what problems you're going to have because we don't know what your code is doing. Your best bet is to look over the Release Notes for 2009 and see if you are using anything that has been drastically changed in 2009. 

Similar Messages

  • Convert KI DAQ libraries from LabView 5.0 to 2009

    Hello everybody!
    I have in the following zip containing the 4 libraries that can control my PCI 3102 acquisition card from Keithley. 
    Unfortunately, these libraries were implemented in LabView 5.0 and I have the new 2009.
    I saw on other posts that the easiest solution is to ask if someone has intermediate version of LabView (like 8.0 or 8.2, preferably 8.2.1 according to the FAQ  http://zone.ni.com/devzone/cda/tut/p/id/8387). In these versions, the libraries will be opened without any problem, and you could just save them in the earlier release so that I can open them in 2009.
    It could be very nice if one of you could do it so that I can avoid installing LabView temporary version just to convert these 4 libraries!
    Thanks in advance for the help.
    Attachments:
    KI DAQ Examples.zip ‏1428 KB

    Well, the easiest thing to do would probably be to get up to date code from Keithley.
    Here they are but you did not include the low level functions so you would need to convert those or get them from Keithley.
    Attachments:
    KICT Examples_71.zip ‏970 KB

  • UDP Error when upgrading from Labview 8.6 to Labview 2009

    I recently updgraded from Labview 8.6 to Labview 2009. I am writing an application to stream data to disk from UDP. My VIs run just fine in Labview 8.6, but when I try to run them in Labview 2009 my UDP read times out despite being able to monitor UDP traffic and see that the data is being sent and nothing in the file is changed from 8.6 to 2009. Is there a known issue related to this?

    How are you moniting the UDP traffic? Have you verified that the port you are trying to use is actually available? When you installed 2009 there may have been an additional service installed that may have used the port you're trying to use. If you're running on Windows you can use the command "netstat -n -o -a" to see all the ports that are currently in use, as well as the process ID that has that port open.

  • Downconvert from LabView 2011 to 2009

    Hi !
    Can anyone convert these VIs (attached file) from Labview 2011 to LabView 2009 ?
    Thanks a lot.
    DMONS
    Solved!
    Go to Solution.
    Attachments:
    LCC25 driver for LabView 2011.zip ‏4308 KB

    Here you go.
    There are only two ways to tell somebody thanks: Kudos and Marked Solutions
    Unofficial Forum Rules and Guidelines
    Attachments:
    LCC25 driver for LabView 2009.zip ‏4230 KB

  • Error -17600 when switching from LabVIEW Development System to LabVIEW Run-Time Engine in Adapter Configuration

    I receive an error message (code -17600) while loading my test sequence after switching from LabVIEW Development System (2009 f3) to LabVIEW Run-TIme Engine using the Adapter Configuration.
    ErrorCode: -17600,
    Failed to load a required step's associated module.
    LabVIEW Run-Time Engine version 9.0.1f3.
    When I switch back to the LV development system, everything is OK, and the sequence loads and runs perfectly.
    My TestStand Engine Version is 2012 f1 (5.0.0.262).
    I'd appreciate any help on this issue.
    Roman

    Hi Roman,
    There are a couple of things you can try:
    1) Determine if the LabVIEW RunTime Engine is corrupted in some way. Create a new simple VI with no sub-VIs, using the same LabVIEW Development system you used for mass-compiling the VIs. Create a TestStand step that calls this VI and ensure it runs correctly. Now switch your LabVIEW adapter to use the RuntimeEngine and choose the "Auto detect using VI version" option.
    Check if the simple VI is loadable and runs without errors in TestStand.
    If the step generates the same error, you should try a re-install of the LabVIEW development system.
    If not, its most likely that there is some VI you are using that is not loadable in the LabVIEW Runtime Engine because:
    1) Some sub-VI is still not saved in the right version or bitness. Open the VI heirarchy of the top-level VI that you are calling from TestStand and examine the paths of all the sub-VIs to check if they were in the folder you masscompiled and re-save any that are outside this directory.
    Also, when you try to close the top level VI, do you get a prompt to save any unsaved files? If so, they could be the sub-VIs that are not saved in the right version. Save all of them.
    Check if you are loading any VIs programatically and if these are compiled and saved in the right version as well.
    2) There is some feature you are using in your LabVIEW code that is not supported in the LabVIEW RunTime Engine. To check this, add your top-level VI to a LabVIEW project and create a new build specification and create a new executable from this VI.
        Right-click "Build Specifications" and choose "New->Application(EXE)".
        In the Application Properties window, select Source Files and choose the top level VI as the start-up VI.
        Save the properties.
        Right-click on the newly created build specification and choose Build.
    Run this executable (it will be run using the LabVIEW RunTime) and check if the VI has a broken arrow indicating that it cannot be loaded and run in the LabVIEW Runtime Engine.
    You might need to examine your code and find the feature which is not supported in the LabVIEW RunTime and find an alternative.
    Another thing i forgot to mention the last time around is if you are using 64-bit LabVIEW with 32-bit TestStand, then executing code using LabVIEW RTE from TestStand will not work since the 64-bit LabVIEW RTE dll cannot be loaded by the 32-bit TestStand process.
    If none of the above steps resolve the issue, consider sharing your LabVIEW code so i can take a look.
    Regards,
    TRJ

  • Where can I get the example application FuzzyEx Car Backward Parking.vi from LabView?

    Where can I get the example application FuzzyEx Car Backward Parking.vi from LabView? I've got the LabView 2009 and I don't find it.

    First verify if you have the PID and Fuzzy Logic Toolkit installed. To do that, you can just look at the "Control Design and Simulation" palette and you should see PID Palette and Fuzzy Logic Palette available. If you do not see, you need to install this toolkit.
    Second, in 2009 you have two options to access the example: you can directly open the example by using this address:
    C:\Program Files\National Instruments\LabVIEW 2009\examples\control\fuzzy\Car Parking\FuzzyEx Car Backward Parking.vi
    Or you can use the example finder and browse examples by going to: "Menu Help>>Find Examples" and "Toolkits and Modules>>PID and Fuzzy Logic Control>>Fuzzy Logic". yoiu should see "FuzzyEx Car Backward Parking".
    Hope this helps.
    Message Edited by Barp on 05-29-2010 12:59 PM
    Barp - Control and Simulation Group - LabVIEW R&D - National Instruments

  • Controlling Tera Term from labview

    Hi guys
    In my new project I would like to send commands to Tera Term Pro. Tera Term then responds to the commands from Labview the same way as I would type the commands directly into Tera Term.
    I'm able to use cmd.exe with the SystemExecute Vi, but for my program I would like to do the same with Tera Term.
    I would like to send commands with a stringcontrol and get the respond in a string indicator, all in labview. Tera Term should run invisible in the background.
    So for this I thought using ActiveX would be the best. I have downloaded tera term pro.
    In Labview I create this from the ActiveX Palette and select browse on the ActiveX Class.
    In the Tera Term folder I find many .dll's:
    I have tried to open them all, but I only get this message:
    Does this mean it's impossible to use Tera Term with Labview like I described?
    I'm not so familiar with ActiveX, only with Excel (which is in the ActiveX Class list), so I might have missed something.
    My goal was to create a sub-vi which does the communication with Tera Term, the same way SystemExecute VI is built.
    Regards,
    Even
    Regards,
    Even
    Certified LabVIEW Associate Developer
    Automated Test Developer
    Topro AS
    Norway
    Solved!
    Go to Solution.

    Sorry for this late reply. I have been using Teraterm Macro (not Teraterm Pro serial terminal) to interface with my previous provisioning app written in LabVIEW.
    Teraterm Macro is such a lifesaver in that it can easily interface with your development boards that need: (1) RS-232C, (2) FTP, (3) TFTP or (4) SSH connections. The plain-vanilla 'serial' VI's are just that - serial port only and those need additional code to work reliably. If you need a good serial port VI try Prabhakant Patil's Hyper Terminal for LV 2009 and newer. You will find an ZIP or VIPM package from LAVA (lava.org). I have used his versions countless of times and is 10x more reliable than provided in LV examples.
    You will indeed use the System-Exec.VI to call Teraterm Macro since *sigh* no one has written a wrapper for the DLLs (as you mentioned they are built for .Net framework. I have talked with the current developers and they are willing to give anyone the pass to extend Teraterm for LabVIEW so C++ devs out there with good LabVIEW knowledge should re-build the DLLs as static libraries that can be called from within LabVIEW. For now, this is the only way and it is a kludge - but it works - just not in a way you expect.
    Here you can see that I am building the command line arguments before I call the system-exec node. Refer to the excellent how-to instructions at:
    http://ttssh2.sourceforge.jp/manual/en/macro/commandline.html
    Teraterm Macro will be spawned (opened) like it would when called from the command line. Its std input & output are not tied to your VI. You can merely pass arguments to the system-exec node. This is the reasons why we need someone to recompile the Teraterm Macro DLL as a static library (anyone?) so we can build a wrapper VI around the functions. Then its std inputs and outputs can be tied to LabVIEW's controls and indicators - hence, it becomes LV native.
    -Relativity

  • Converting from LabView 4.0 to 9.0

    I also need to convert this llb from LabVIEW 4.0; to 9.0. Anyone willing to do this for me? see attached and thanks...
    Attachments:
    gj18i.llb ‏247 KB

    Hey!! Could somebody help me?? I have an labview 2009 and it would be nice if somebody could convert these files (version 4.0.1)  for me! Thx
    Attachments:
    lgy1m.llb ‏73 KB

  • Convert labview file 2010 to 2009

    Hi,
    Can anyone convert the file from labview 2010 version to labview 2009.
    File attached as attachment. 
    Thanks in advance
    Owen
    Solved!
    Go to Solution.
    Attachments:
    LAPP.vi ‏37 KB

    For future reference, there is the Conversion Board for this kind of thing.
    There are only two ways to tell somebody thanks: Kudos and Marked Solutions
    Unofficial Forum Rules and Guidelines
    Attachments:
    LAPP.vi ‏96 KB

  • Can you generate PDF file from LabVIEW?

    Can you generate a PDF file from LabVIEW?

    Hi there,
    I just read this post in passing.
    Heres a fairly detailed forum post on the matter - seems to be a few work arounds, but basically no you can't with just the normal labview.
    http://forums.ni.com/ni/board/message?board.id=170&message.id=259103&query.id=65866#M259103
    Thanks
    Kind Regards
    James Hillman
    Applications Engineer 2008 to 2009 National Instruments UK & Ireland
    Loughborough University UK - 2006 to 2011
    Remember Kudos those who help!

  • Why the acquisition with DAQmx is different by using Labview 8.2 from Labview signal express?

    Hello,
    I am using a PCi-6281 to acquire a voltage. When I am using Labview signal express with only the step to acquire I read the good signal with the exact voltage. But when I am using my VI, the y axis and the values recorded are wrong. Why this difference appears?
    I insert a picture with both signal: at the top is the signal from my vi (wrong measurement) and at the bottom is the signal from labview signal express (correct).
    The vi I am using is the example Cont Acqu&Graph Voltage-To file (binary).vi.
    Thank you for your answer!
    Sophie
    Sophie

    I am using the binary file because it requires the minimum change in another VI. I have tried to change in scaled data but now my second VI has not enough memory to display all data.... What's wrong? Here is my second VI. Totest with data you need to insert a number in the "scaling factor" if not the dat are multiplied by zero...
    thanks for your help!
    Message Edité par stage84 le 07-24-2009 10:11 AM
    Attachments:
    Display 3.vi ‏1867 KB

  • Convert from Labview 5.1 to labview8.6

    Hello Everyone,
    Can any one please convert this vi from labview 5.1 to labview 8.6 or labview 2009
    Thanks in advance
    Nadim
    [email protected]
    Attachments:
    4-Channel Power Spectrum with estimate.vi ‏750 KB

    Hi,
    Here it is in LV 8 but there are some VI's missing (DAQ)
    Kees
    Attachments:
    4-Channel Power Spectrum with estimate.vi ‏402 KB

  • How to freeze and unfreeze panes in window by using Excel from LabVIEW

    Hello
    I am creating an Excel Report file programmatically using LabVIEW. I make the row headers for the sheet and store data using the program.
    The requirement that i need is that when the user opens the Excel sheet, the row heading should remain fixed at top, as the sheet is scrolled down by the user.
    This is possible in Excel, by clicking on Window in the menu bar and then select Freeze panes/Unfreeze panes. The same operation i need, to be done from LabVIEW. Please let me know how this can be done.
    I use LabVIEW 2009
    Thank you.
    Solved!
    Go to Solution.

    Please see this discussion. TCPlomp has an example of how to achieve this.
    Cory K

  • How can i update an html web page from Labview?

    I intend to publish the "status" of an experiment online through an web page. I mean, if my vi is running i would like to have a phrase or indicator set on at my web page. If my Vi is not running i would like this indicator set off. This page is hosted in a server and I would like to know if its possible to update the html file from labview through an ftp connection.
    Thanks in advance...
    MSc. Alexandre Michel Maul
    Parana Federal Univeristy - Brasil

    The system exec function is on the Communication palette. Its for executing system commands. On my Win2K system, the help for FTP is:
    "Ftp
    Transfers files to and from a computer running an FTP server service (sometimes called a daemon). Ftp can be used interactively. Click ftp commands in the Related Topics list for a description of available ftp subcommands. This command is available only if the TCP/IP protocol has been installed. Ftp is a service, that, once started, creates a sub-environment in which you can use ftp commands, and from which you can return to the Windows 2000 command prompt by typing the quit subcommand. When the ftp sub-environment is running, it is indicated by the ftp command prompt.
    ftp [-v] [-n] [-i] [-d] [-g]
    [-s:filename] [-a] [-w:windowsize] [computer]
    Parameters
    -v
    Suppresses display of remote server responses.
    -n
    Suppresses autologin upon initial connection.
    -i
    Turns off interactive prompting during multiple file transfers.
    -d
    Enables debugging, displaying all ftp commands passed between the client and server.
    -g
    Disables file name globbing, which permits the use of wildcard characters (* and ?) in local file and path names. (See the glob command in the online Command Reference.)
    -s:filename
    Specifies a text file containing ftp commands; the commands automatically run after ftp starts. No spaces are allowed in this parameter. Use this switch instead of redirection (>).
    -a
    Use any local interface when binding data connection.
    -w:windowsize
    Overrides the default transfer buffer size of 4096.
    computer
    Specifies the computer name or IP address of the remote computer to connect to. The computer, if specified, must be the last paramete
    r on the line."
    I use tftp all of the time to transfer files in a similar manner. Test the transfer from the Windows command line and copy it into a VI. Pass the command line to system exec and wait until it's done.

  • Need to convert to labview 11 from labview 12

    hello
    I need to convert the following Labview 12 VIs to Labview 11.
    thank you in advance
    Attachments:
    QAM Demodulation.vi ‏30 KB
    QAM Modulation.vi ‏30 KB
    rx QAM.vi ‏57 KB

    The conversion was done here: http://forums.ni.com/t5/Version-Conversion/need-to-convert-from-Labview-12-VI-to-Labview-11/m-p/3021...
    There are only two ways to tell somebody thanks: Kudos and Marked Solutions
    Unofficial Forum Rules and Guidelines

Maybe you are looking for