Opening VI written in labview 5.0 with version 8.5

Hi,
I am new to Labview. I have VIs to capture the Tektronics real time scope waveforms written in Labview 5.0. I am currently using is evaluation version 8.5. I am getting an error that the new version does not support these old files. I just want to open these files and look at the code for reference. Can anyone suggest a way to open these files.
Thanks,
Chakradhar

As Dennis explained, there is not much you can do...  See images below:
All the sub-vi's (within the .llb file) do not have block diagrams, so the calling VI is rather useless.
R
Message Edited by JoeLabView on 07-29-2008 07:54 PM
Attachments:
notConvert1.PNG ‏5 KB
notConvert2.PNG ‏20 KB

Similar Messages

  • Open a VI in LabVIEW 5.1 that was saved in version 6.1

    Does anyone know if it is possible to open a VI saved in LabVIEW 6.1 with version 5.1? I have come across some VI's that were either saved in version 6.1 or they were created in that version. Our computers are running Version 5.1 currently. If they can be opened in ver. 5.1 would they run ok in that version? Thanks

    Each LabVIEW version can go back one step uing "save for previous". You need LabVIEW 6.1 to save them in 6.0 format. Then you need LabVIEW 6.0 to save them for LabVIEW 5.1.
    Unless they use new 6.0 or 6.1 specific features, they should run just fine in LabVIEW 5.1 once converted.
    If you want, you can post your VIs here and somebody will probably convert them for you.
    LabVIEW Champion . Do more with less code and in less time .

  • Ability to open PDF Doc on Motorola Android Razr using version 10.4.2 Reader

    I received an Email from my Bank with a PDF form and tried to open it on my Motorola Android Razr with version 10.4.2 Reader and it instructed me to upgrade. So I went on Google Playstore on the phone and I was told it was already on the phone. I then went to my pc which has version XI and it opened with no problem. How can I configure the Android phone to be able to open these important docs?

    I had the same issue. I found an answer on a link on this matter today. The suggestion was to uninstall Reader 9.1, or any other recent version, and install a prior version, 8.12, which apparently is the same as 8.1.2, you may see it referred to both ways. Just type in your web browser "download adobe reader 8.12" and you'll get a page of links. I chose one that referred to a free 8.12 download, or it may have said 8.1.2. It worked!
    Uninstall any current versions of Reader then install the 8.1.2. I didn't bother to reboot the computer before or after I installed it. I was receiving different error messages in Internet Explorer and Firefox before the new install. Now Reader works with both, as it did before. Hope this helps.

  • How to compile and link the LabView program(G) with some function written in C?

    Before, some employee in our company developed some program which was written in LabView (G). Now we want to add some new function with has already been done in C++. Can we combine them together? how to do it?

    Hi;
    To use external code in LabVIEW, you can create a dynamic link library (.dll) that you can call from LabVIEW or a Code Interface Node (CIN). The instructions on how to make any of those are in National Instruments manual Using External Code in LabVIEW, which is included with LabVIEW, or you can download it from NI website.
    Also, in the knowledge base there is a "External Code for LabVIEW - CIN / DLL - Starting Point" page.
    If, on the contrary, you want to use LabVIEW code on your C application, you can build dll's in LabVIEW. Depending on your version of LabVIEW, you may need Application Builder to do so.
    Of course, you can also use other techniques like, for example, making that your LabVIEW application save the data in a file and then your C++ application read the file and continues from there, or vice versa. You can also use the "System Exec.vi" in LabVIEw to do that, assuming your C code is an executable.
    Regards;
    Enrique
    www.vartortech.com

  • Can't open Pdf written with adobe V7 in Adobe V9 properly

    Hi,
      I'm novice working with Pdf's. I have a task where we need to upgrade to Adobe Reader9 from Adobe Reader7. I'm able to open old pdf which works fine in Adobe Reader 7 but in Adobe Reader 9, I see the pdf broken into several fragment. Is there a way to open the pdf properly in Adobe V9 with no broken fragments.
    Regards,
    VJ

    Reader 11 is not available for general release. If you participated in the beta program, there is a place for this discussion which you have been provided. If you did not participate in the beta program, then you should not yet have access to Reader 11. I have just checked the Adobe website and it is not available to download from there.

  • Problem on WinXP / Labview 6.1 with VISA (serial port)

    There is a problem on WinXP / Labview 6.1 with VISA which i use to poll the state lines of the serial port. The only functions that i use are "VISA Open", "Find Resource", line state properties and "VISA close".
    On my own machine (WinME) it works fine as a standalone application (with runtime engine in the same direction), even if i rename the Labview directory so that Labview is not found.
    From my VXIpnp directory i deleted all but these files:
    directory "Win95",
    subdirectory "Bin" containing "NiViAsrl.dll",
    subdirectory "NIvisa" containing "visaconf.dll".
    When shipping this to WinXP (and copying "VXIpnp" to the root directory), the serial port was not found, so i renamed the direction "Win95" to "
    WinNT", but this did not work also.
    I installed the VISA server, although it seems not to be required -- no result.
    Final question:
    What must i do for distributing the program as a standalone application for all windows platforms?

    Hey Joachim,
    In order to create an installer that includes the VISA Run-time engine for serial IO you will have to purchase LabVIEW 7.x. See screen shot. This packages a small compact version of the run-time that can only be used for serial, but it takes up much less space. The installer that I created has my application, the LV Run-time, and the VISA run-time and it is about 26 MB.
    That is much smaller than if I had to include the 32 MB LV 7.1 run-time and the 14 MB VISA run-time separately. It would have been even smaller if I would have uncheck some of the items that I wasn't using.
    -Josh
    Attachments:
    advanced.JPG ‏31 KB

  • What is the easiest way to open an application from Labview?

    I need to open an application from labview and depending on a user's selection, load one out of a group of files for the application that is opened. I need to know what is the best or easiest way to open an application and load a file that is used by the application based on a selection.

    Here is the response that I got from Cognex when I asked them about how to do this. Do you understand what they are talking about?
    In order to do something like this you will probably want to look into the Display Control/SDK for In-Sight. The Display Control gets installed along with In-Sight Explorer and includes a control that can be used in an environment like Labview to communicate with In-Sight sensors while the SDK is an enhanced version of the Display Control that gives you more control and functionality. I am not very familiar with the Labview environment so I will give some code snippets in VB.Net and hopefully you can adjust them as necessary. Specifically I see 3 possible avenues to do this:
     1) Using the Display Control you have access to many of the dialog boxes that are used in In-Sight Explorer including the Load Job dialog box. You can spawn this dialog box through a line of code similar to cvsInSightDisplay1.Edit.OpenJob.Execute(). I am not certain if the Labview environment will be able to spawn and display this dialog though. 2) With the addition of the SDK (additional purchase) you can directly access sensor properties including the job. There is a method called LoadJobFile to load jobs from on the sensor and LoadJobFileLocally to load jobs from the host machine. A typical line of code might be cvsInSightDisplay1.InSight.File.LoadJobFile("myjob1.job").3) If Labview cannot handle the dialogs and the SDK is not an option for you then you may still be able to do this using Native Mode commands. Native Mode commands are sent through a socket on the telnet port (typically port 23). Keep in mind that you will need to handle the username/password prompt and response when you first open the socket before issuing any Native Mode commands. The command to load a job file from the sensor would be the Load File command which would be a string similar to "LF myjob1.job". The Native Mode commands are documented in the In-Sight Explorer help file. 

  • Not executed Commands from Testprogra​ms written in Labview communicat​ing over GPIB

    Hello
    Sometimes I have the problem that the commands sent from testprograms written in Labview aren't executed from the devices
    (for example a counter or a power supply).
    An extension of the the wait time between Write and Read couldn't solve the problem (We use VISA-VIs or the Manufacturers-VIs).
    First workaround is to send the command again.
    Somebody else ever had the same problems to deal with? What did you do?
    Many thanks
    Best Regards
    Silvio

    Usually stuff like this is caused by incomplete understanding of communications using the GPIB bus (either by the programmer OR by the supplier of the drivers - the latter reason being why I almost always write my own drivers).
    Many times, an instrument fails to respond in what we considre a "timely" manner - a prime example is an instrument that takes several seconds to complete a measurement.  Many times, instruments don't queue commands, so if you send a command to an instrument while it is still processing a previous command, it won't be aware of the command you just sent, and you will get a timeout.  In this case, it's best to make the VISA timeout something like 5000 ms and - if your instrument accepts the command - use *OPC? to turn your command into a query.  This way, your application always waits for a response - usually a "1" - from the instrument being commanded before sending the next command. 
    Bill
    Bill
    (Mid-Level minion.)
    My support system ensures that I don't look totally incompetent.
    Proud to say that I've progressed beyond knowing just enough to be dangerous. I now know enough to know that I have no clue about anything at all.

  • Case study: "Large?" labview programs flooded with different VIT's

    Case study: "Large?" labview programs flooded
    with different VIT's
    Type of application:
    Computer with loads of individual hardware connected or other software (either
    onsite (different buses) or offsite (Satelite/GSM/GPRS/radio etc.).
    Hardware
    description: little data "RPM" but communications to all devices are intact.
    More "RPM" when many VITs are involved.
    Size: 1000+
    VITS in memory (goal). Total software has been tested and simulated with 400.
    I'm posting
    this post after reading this thread (and actually I cant sleep and am bored as
    hell).
    Note: I do
    not use LVOOP (but sure post OOP examples, am starting to learn more and more
    by the day.)
    Things I
    will discuss are:
    Case 1: Memory usage using a plugin
    architecture
    CASE 2: memory usage using VITs (!)
    CASE 3: updating datastructures:
    CASE 4: shutdown of the whole system
    CASE 5: stability & heath monitoring
    CASE 6: Inifiles
    CASE 7: When the hardware is getting crappy
    Total
    application overview:
    We have a
    main application. This main application is mainly empty as hell, and only holds
    a plugin functionality (to register and administer plugins) and holds an
    architecture that holds the following items:
    Queue state
    machine for main application error handling
    Queue state
    machine for status messages
    Queue state
    machine for updating virtual variables
    Event state
    machine for GUI
    Some other
    stuff
    Other
    global functionality is:
    User
    logins, user configurations and unique access levels
    Different
    nice tools like the good old BootP and other juicy stuff
    Supervision
    of variables (like the NI tag engine, but here we have our own datastructures)
    Generation
    of virtual variables (so that the user can configure easy mathematical
    functions and combining existing tags)
    Licensing
    of plugins (hell we free-lance programmers need some money to don't we?)
    Handles
    all communication between plugins themselves, or directly to a plugin or vice
    versus.
    And now we don't
    talk about that (or marketing) the main application .
    Message Edited by Corny on 01-20-2010 08:52 AM

    CASE 3: updating datastructures:
     As we do NOT use clusters here (that would
    just be consuming) we only use an 1D array of data that needs to be updated in
    different functional globals. If the the number of VITS exceeds so that the
    updating of this datastructures becomes the bottleneck, this would cause
    delays. And since in this example we use 250 serial interfaces (lol) we do not
    want to disrupt that by any delays. When this happends, does anyone know a good
    solution to transfer data?
    A thought:
    perhaps sending it down to the plugin and let the plugin handle it, this should
    save some time, but then again if more VITs are added again this would become a
    bottleneck and the queue would fill up after a while unable to process it fast
    enough. Any opinions?
    CASE 4: shutdown of the whole system
    Lets say we
    want to close it all down, but the VITs need perhaps to do some shutdown
    procedure towards the hardware, that can be heavy.
    If we ask
    them to shutdown all together we can use an natofier or userevent to do this
    job. Well, what happends next is that the CPU will jump to the roof, and well
    that can only cause dataloss and trouble. The solution here was to let the
    plugin shut them all down one by one, when one has been shutdown, begin at the
    next. Pro; CPU will not jump to the moon. Con's: shutdown is going to take a
    while. Be ready with a cup of coffee.
    Also we
    want the main application not to exit before we exit. The solution above solved
    this as the plugin knows when all have been shut down, and can then shut itself
    down. When all plugins are shutdown - the application ends.
    Another
    solution is to use rendovous (arg cant spell it) and only shut the system down
    when all rendezvous have met.
    CASE 5: stability & heath monitoring
    This IS
    using a lot of memory. How to get it down. And has anyone experienced any
    difficulties with labview using A LOT of memory? I want to know if something
    gets corrupt. The VITs send out error information in case, but what if
    something weird happens, how can I surveillance all the VIT's in memory to know
    one is malfunctioning in an effective way/code (as backup
    solution  so the application knows
    something is wrong?
    CASE 6: Inifiles
    Well, we
    all like them. Even if XML is perhaps more fahionally. Now Ive runned some
    tests on large inifiles. And the labview Inifile functions use ages to parsing
    all this information. Perhaps an own file structure in binary format or
    something would be better? (and rather create an configuration program)?
    CASE 7: When the hardware is getting crappy:
    Now what if
    the system is hitting the limit and gradually exceeds the hardware req. of the
    software. What to do then (thinking mostly of memory usage)? Needing to install
    it on more servers or something and splitting configurations? Is that the best
    way to solve this? Any opinions?
    Wow.  Time for a coffee cup. Impressive if someone
    actually read all of this. My goal is to reach the 1000 VIT mark.. someday.. so
    any opinions, and just ask if something unclear or other stuff, Im open for all
    stuff, since I see the software will hit a memory barrier someday if I want to
    reach that 1000 mark hehe

  • LabVIEW 2009 launches with errors

    Hi Folks,
    LabVIEW 2009 launches with errors now everytime I open it.  A window appears showing an error list with nothing in it, with a close and show dialog box (hangs with hour glass).  Neither option is possible since the window self closes in about two minutes.  It's a little frustrating since it adds to my loading time everytime I launch it.
    Any suggestions other than unistall/install process?
    Windows XP Professional 2002, SP3
    Labview 2009, Mem Alloc 39125K, TCP Server inactive, Version 9.0 (32bit)
    Regards,
    -SS

    Hi!
    The exact sme thing happend to me. But for me it was on the LV2010 version. Just suddenly it started to launch everytime I opened LV. After a re-installation of LV it was gone. 
    Regards,
    Even
    Certified LabVIEW Associate Developer
    Automated Test Developer
    Topro AS
    Norway

  • LabVIEW and Excel with ActiveX

    Hi,
    I am using LabVIEW6.1 and I am trying to format data for printout that I have stored in Excel using activeX.
    I have three questions that I included the recorded Excel macro for:
    1) How do I set the horizontal and vertical page breaks using ActiveX?
    Excel macro:
    Set ActiveSheet.VPageBreaks(1).Location = Range("F1")
    Set ActiveSheet.HPageBreaks(1).Location = Range("A41")
    2) How do I set the print area using activeX?
    Excel macro:
    ActiveSheet.PageSetup.PrintArea = "$A$1:$J$57"
    3) How do I left, right center justify the content of cell using ActiveX.
    Excel macro:
    Range("B3:B8").Select
    With Selection
    .HorizontalAlignment = xlCenter
    End With
    Thanks in advance for your time.
    KMA

    You cannot index the VPageBreaks if you are creating a new worksheet. You would use the index to change an existing VPageBreak. To create a new VPageBreak, replace the Item method with the Add method. Wire the range ref directly into the Before input. I fixed your VI and attached it.
    To get the value of the xlCenter constant, open the Visual Basic editor that comes with Excel and use the Object Browser (F2). Type xlcenter into the search window and click the binoculars. The value is displayed at the bottom of the window. You will use that trick a lot when looking for the Excel constants for LabVIEW.
    Michael
    Michael Munroe, ABCDEF
    Certified LabVIEW Developer, MCP
    Find and fix bad VI Properties with Property Inspector
    Attachments:
    Excel_Page_Break_mod.vi ‏67 KB

  • Using "panelresize.vi" in Labview 2013, in code originally written for Labview 2006.

    Hello,
    I'm updating code written in Labview 2006 to make it compatible with Labview 2013.  My code calls a custom TDMS file viewer vi.  This viewer calls a function called "panelresize.vi".  This is a NI vi that has been updated since the 2006 version.  The new version includes a "help - boolean refnum" in the input cluster, so that the vi now expects a cluster of 9 elements instead of the 8 that I am sending it.  I am not sure what this "help refnum" is, how to use it, or how to add this to my input cluster in the calling function so that the error goes away.
    Any suggestions?
    Thanks!
    Attachments:
    Untitled.png ‏392 KB

    Hi,
    it is a help button. You can add a help button to your customized File Viewer. If you don't want this button, you can make it invisible. 
    What requirements drive you to make your own customized File Viewer?
    FYI. In LabVIEW 2013, we made changes to improve the performance of the file viewer. For the compatibility, we kept the panelresize.vi and added a specific panelresize_tdms.vi for this improvement. panelresize_tdms.vi requires more than 9 elements.

  • Every time I open my project file (LabView 8.5) it needs to be re-saved

    Since LabView version 8.5, each and every time I open my project file (*.lvproj), it needs to be re-saved as indicated by the asterisk next to the project file name in the title bar of the Project Explorer. That is confirmed when I close it and a dialogue box pops up asking if I want to save the project.
    I've clicked both "Save All" file menu items. The asterisk goes away and I can close the project without the dialogue box opening. But if I immediately re-open the project, the asterisk is there again.
    Note that I have not made any changes - it occurs immediately after opening the project, as if it were a project file from a previoius version (which it was initially, but after saving it once in the new version, it should not happen again when no changes are made.
     I did not observe this behavior with versions prior to 8.5. Anyone else see this? Thanks.
    Ed S.

    Thanks for your input. I don't know what you mean by a "mass compile". I've build my application - both a stand-alone exe and the installer (and it works), and I've saved the project. Then when I re-open it I get the asterisk. I can save it again, but the same thing occurs when I open it again.
    No, I'm not using XControls or LVLOOP (whatever they are). Also, the application was developed originally in version 8.2.1 and then saved in version 8.5 when it became available. Everything else works fine, the same as it did in the previous version. This is the only difference I've seen.

  • How can I configure labview for communication with Modbus I/O?

    i read a article about configureing Labview for communication with modbus I/O in NI developer zone, but it was written for Labview 6, how can I configure it with labview 7. it seems there are some difference. Thanks!

    In both LabVIEW 6 and 7, you connect to modbus using Lookout Protocol Drivers (LPD) and then communicate to LPD using the tag engine of LabVIEW DSC or through DataSocket.

  • How can a LabView process communicate with a Visual c++ process

    How can a single Labview process communicate with another Visual c++ Process?
    Both Application are running separately. The LabView  Application must have the Possibility to send command to the C++ Application and receive Data from this process.
    Thanks.

    Thank y for your answer.
    The c++ application has already been written but don´t have an external interface.
    The LabView application can have an activeX  interface other dlls.
    Do you have some LabView example code using activeX interface other another Method to communicate with a c++ application?
    I have no practical experience with the interprocess communication.
    Any example in LabView will help me.
    Thanks

Maybe you are looking for