Backward Compatibility with Labview 6.0 and 6.1

Hello,
I am having the same problem as discussed in the following message board of yours:
"how to open a vi (made in version 6.1 labview) in version 6.0"
One of your support staff offered to take a user's version 6.1 vi, open it and Save As a version 6.0 vi.
Could you please do the same thing for me? I have attached a vi that was created using version 6.1, however, I am trying to do some work at home. Unfortunately, I only have version 6.0 at home. Version 6.1 was only installed in my research lab.
In case simply saving the vi as a 6.0 version will not sole the problem, could you take screen shots of the front-panel and block-diagram and then just attach the jpeg's?
Thank you,
Charles
Attachments:
chuckmot_6p0.vi ‏72 KB

Hey Chuck:
I think I sent you the wrong file…
These are the ones that the program created, after converting to 6.0 (I hope)
Best wishes and Fight on!
Santiago
Attachments:
chuckmot_6p0.vi ‏67 KB
AI0.vi ‏35 KB
AI1.vi ‏37 KB

Similar Messages

  • Windows 7 Compatability with Labview 8.0 and missing files while interfacing the FPGA with LV

    I am trying to use an FPGA (PCI-7830R) with Labview 8.0. The computer has Windows 7 OS. I installed LV 8.0 in the proper order with the FPGA Module and labview is able to see the FPGA when I open a .lvproj (the FPGA is in the tree) however there is a warning symbol next to the FPGA selection and when I try to open a .vi file that is used on the other stations in my lab (it works on all the other stations), labview is unable to find a whole bunch of files. There are some pictures.
    Missing File (there are a bunch more but this is the fist one).

    According to this LabVIEW Compatibility LabVIEW 8.0 is NOT compatible with Windows 7
    Visualize the Solution
    CLA
    LabVIEW, LabVIEW FPGA

  • Labview 7.0 is compatable with Labview Imaq6.1 , vision builder 6.0 and Imaq run time engine 6.0.

    Sir,
    My system is PXI 8174 and i an using NI 1411 card for my application. I want to know the compatability of the softwares. Whether Labview 7 is compatable with Labview Imaq 6.1 , vision builder 6.0 and Imaq run time engine 6.0.

    Hi,
    Assuming you meant IMAQ Vision 6.1 instead of IMAC 6.1, this software was intended to run on LabVIEW 5.1, 6.0, and 6.1.  I have heard of it being used with LabVIEW 7 on occasion, so it may be possible to make it work, but this has not been tested and is not officially supported.  Vision Builder 6.0 should run; however, it was developed long before LabVIEW 7.x and will not generated code for LabVIEW 7.0 and later.  The Vision RTE version should correspond to the version of Vision you are using.  For instance, if the program was developed with Vision 6.1, the computer should have the Vision 6.1 RTE installed.  With this being said, if you plan to use LabVIEW 7, I recommend updating your other software.
    Regards,
    Ryan M.
    Applications Engineer

  • Known backwards compatibility issues between Robohelp 9 and Robohelp 8?

    Hi Group,
    In addition to avoiding the tasks in the Review menu, does anyone know of any other backwards compatibility issues encountered while opening and using files generated in RoboHelp 9 from within Robohelp 8? Thanks, gail

    Welcome to the forum.
    Simply the fact that RoboHelp 8 will not open a project that has been run in RoboHelp 9. Sure you might well open a project by deleting the CPD and perhaps the XPJ and using the HHP, however I would not recommend that except in an emergency.
    What I am not clear on is how you link that to "avoiding the tasks in the Review menu." What has that got to do with the question?
    See www.grainge.org for RoboHelp and Authoring tips
    @petergrainge

  • I am using report generation toolkit 1.1 with Labview 7.0 and Office 2003 profession​al. The create new report VI opens Excel but throws error (-21471672​62- from automation open VI) when I try to open MS word. please help...

    I am using report generation toolkit 1.1 with Labview 7.0 and Office 2003 professional. The create new report VI opens Excel but throws error (-2147167262- from automation open VI) when I try to open MS word. please help...

    Hi Leo22,
    Does this error occur if you use any of the example programs that come shipped with LabVIEW? I would try opening one of the examples that write data to Word and see if those give you an error. Also, have you tried just putting down a New Report.VI and change the report type to Word? If this simple vi (that's all you need to open Word) breaks, I would check to see if there are any instances of Word still open. Check the task manager to see if any word processes are still open. There should not be a problem accessing Word 2003 from LabVIEW 7.0. If neither of these solutions work, please give some more detail about your application and we can research further. Thanks!
    Jeremy L.
    National Instruments
    Jeremy L.
    National Instruments

  • Problems with LabVIEW 7.1 and lock-in amplifier Stanford SR530?

    Does has anybody had problems with LabVIEW 7.1 and the instrument driver for the lock-in amplifier Stanford SR530?
    With LabVIEW 6 there are no problems at all, but with LabVIEW 7.1 it is impossible to communicate with the instrument.

    amr_attia wrote: (Private message, no need to private message)
     My problem is to get the data out from the divice x and y readings . Can you help me
    Here is the code and snippet. I had it from before. It reads Channel 1 and Channel 2 from the SR530, that is whatever the display is for Channel 1 & 2. You set the display manually or programmatically, I let you figure that part out.
    Cheers,
    mcduff

  • Report Generation Toolkit Compatibility with Microsoft Office 2013 and LabVIEW 2012

    Hello community,
    on this page there is shown the Report Generation Toolkit Compatibility with Microsoft Office and LabVIEW.
    In our company we use actually LabView 2012 and it works perfectly with MS Office 2010.
    Has anyone ever tried the "Report Generation Toolkit" of LabVIEW 2012 with MS Office 2013? Does it really not work? Has anyone an emirical value for this topic?

    Hi digital_badger,
    as you sure have seen in the link it is not officially supported by NI, which means to you one of the following things:
    1. You could upgrade your LabVIEW and your Report Gerneration Toolkit to Version 2014 and use MS Office 2013
    2. You could just try it with MS Office 2013 which might work but if it's not working you don't get any support from NI.
    Even if someone tried it already and it worked for him does not mean that it will work on your machines. It is possible that on some of your machines it could work but not on others. Their can be a lot of problems while playing around with unsupported setups.
    3. You could leave your setup as it is and stick to your MS Office 2010.
    I hope I could give you a good answer to your question

  • Windows 7 with labview 8.5 and NI-8451

    Hello,
    I am using LabVIEW 8.5 with NI-8451 device on Windows 7. I installed 1.1 driver for NI-8451, but I am unnable to access any subVI connected with NI-8451.  Can you advise?
    Thank you.

    Hi miso2562,
    The issue is most likely compatibility between the drivers, LabVIEW, and the OS. LabVIEW 8.5 is not supported on Windows 7 (only up to Vista), and NI-845X 1.1 is not supported on Windows 7 either (only up to XP). Also, NI-845X 1.1 does not support LabVIEW 8.5 either (only up to 8.2).
    Ideally, if you use Windows 7 you should have LabVIEW 2009 SP1 or newer and NI-845X 2.1 or newer (1.1.4 could work as well). If you can move to XP, LabVIEW 8.5 and NI-845X 1.1.1 should work.
    References for compatibility:
    http://digital.ni.com/public.nsf/allkb/B972242574D4BB99862575A7007520CB 
    http://download.ni.com/support/softlib//i2c_spi/ni-845x/1.1/readme.htm
    As for your main question "unable to access any subVI connected with NI-8451", do you mean they do not show on the function pallete?
    - FCTesting

  • Backward compatibility with Captivate 7.0

    We are in the process of procuring Captivate 7.0. If we develop web based training materials using Captivate 7.0 will be able to make edits in future with Captivate 6.0 ?

    No backward compatibility!  This is crazy.  We've just tried the Save As option expecting there to be an option to save for previous versions and it's not there.  What a short sighted approach to take, and very frustrating.
    I am not on a maintenance contract for the software, but my colleagues are, so to be able to collaborate either they have to hold back on updates or I have to upgrade.
    So this is Adobe’s approach to supporting licensed users in their ability to work collaboratively?   I wish there was a competitor on the market we could use instead of Adobe.

  • Does the new version of pages for ipad have backwards compatability with previous versions of Pages?

    This one question is preventing me from downloading the new version of pages - I am worried I will lose the ability to read documents made with the previous version of pages, or that they will be automatically converted into the new format without my knowing. My laptop does not have Mavericks so I will have to keep using an older version of pages here, but I am reluctant to download the new version to my ipad because of concerns that users have previously voiced about the lack of backwards compatability. Is this still the case, or is there now backwards compatability?

    Did we get HyperCard back?
    Did we get all the features of AppleWork Back?
    Has QuickTime X got back the editability of QuickTime?
    Has FileMaker now got all the Bento features?
    Has Final Cut been reduced to match iMovie for iOS?
    Apple is out to attract iOS users, who mainly do selfies and twitter. They pay better because they are undemanding, don't even notice when Apple offers them something inferior and have been broken in with the iTunes Store harness.
    Peter

  • IMAQ PCI-1424 compatibility with Labview 8.6

    Hi, the computer I used for image analysis work had a broken motherboard problem, and I replaced it with a new one. I removed both the harddisks and the IMAQ board from the old computer to the new one and then installed Labview 8.6, but Labview 8.6 is not compatible with the image processing software programmed using labview 5.0, so I uninstalled Labview 8.6 and re-installed Labview 6.0. I still have some problems to run the image analyzer and processing software. After I uninstalled labview software, the computer cannot start successfully, poping up error information as "Check your hard drive to make sure it is properly configured and terminated. Run CHKDSK /F to check for hard drive corruption, and then restart your computer".
    Some basic information about that computer and the image acquisition system (set up in 2000) is as follows:
    Windows 2000 operating system;
    Labview Base Package 5.0;
    advanced IMAQ vision for Labview;
    IMAQ PCI-1408, IMAQ-BNC-1 cable, and Ni-IMAQ for Windows NT/95;
    IMAQ-A2504-1 (1m);
    Sony XC-55 1/3" Interline transfer progressive scan CCD, 659 (H) X 494 (V), C-mount with JB-77, CCXC-12P-02 and DKT503M;
    Computar H1212FI 1/2" C-mount 12mm w/focus and iris (10 inch FOV at 24 Working Dist.);
    Computar VM100 extension tube kit;
    Graftek High Frequency Fluorescent Light 11";
    Is the IMAQ hardware I am using compatible with Labview 6.0 or 8.6? Should I install also drivers for IMAQ hardware when I remove IMAQ board? Any solutions for my problems? Thanks very much in advance!!!
    Solved!
    Go to Solution.

    Hi simpra,
    Here are two links to articles that list compatability between Windows & LabVIEW and LabVIEW & IMAQ.   Why do you say that the image processign software was not compatable with LV 8.6?  Did a message appear?  Or did it just not work?  Also, are you talking about Vision Development Module, by chance?  
    I'm afraid I can't help with hard drive corruption if that's the case here.  Were you able to get past that?
    My suggestion is to upgrade to the most recent version possible.
    I hope this helps!
    Kristen H.

  • 11.1.2.1 HFR Studio backwards compatibility with 9.3.1?

    We're currently working through a migration upgrade from 9.3.1 to 11.1.1.3 to 11.1.2.1 and plan to run through a couple of months of parallel testing before going live.
    I've seen that the 11.1.2.1 Smartview has some backwards compatibiility with 9.3.1, but I'm trying to verify if we could install and use the 11.1.2.1 version of HFR Studio to manage both reporting environments (9.3.1 & 11.1.2.1) during the parallel phase.
    Anyone with any experience on this topic?

    According to the support matrix, FR Studio 11.1.2.1 only supports 11.1.2.1 Essbase, Planning and HFM database connections:
    http://www.oracle.com/technetwork/middleware/bi-foundation/oracle-hyperion-epm-system-certific-131801.xls
    Cheers,
    Mehmet

  • Font compatibility with Office (for Mac and Windows)

    Hi,
    Despite extensive searching, I'm struggling with a font compatibility issue between my Mac and my colleagues' PCs. The main points in order:
    The fonts work correctly on both my Mac and other PCs.
    The font in question is HelveticaNeueLT Std, rolled up into which are several different weights. The files are OTF files. The same files install without any problems on all the computers in question (and show up in Font Book). And the font can be used successfully:
    - in Keynote, I select Helvetica Neue LT Std, and underneath choose whichever weight I want
    - on PCs, the font and weight can be selected from the drop-down list in MS Office.
    - in Office for Mac 2016 (Preview), I cannot select the font from the drop-down list, but can hit Cmd+T, and then select the appropriate font and weight under 'Latin text font'. What is odd is that in the dropdown list, only a particular weight/typeface is shown:
    As this is a preview version, I wouldn't expect Office to work perfectly just yet...
    When a file is created on a PC, it works fine on my Mac.
    Every file I have attempted to open that was created on a PC, and using these fonts, works fine. The fonts display correctly (i.e. including the correct weights), and I can work with the document without any problems. The only odd bit: sometimes in the dropdown box on my Mac it then says (null):
    Whereas at other times, the font name shows correctly:
    Both of those examples were created using the 'Thin' weight of HelveticaNeueLt Std. I can't see any pattern as to what causes this inconstency.
    The problem is that what I create on my Mac shows incorrectly on a PC.
    If I create anything using Office 2016 or Keynote, selecting the preferred weight as described above, it shows just fine on my Mac. But when I send the PPTX file to a PC, all weights look identical (it looks as though the PC has just displayed everything in a standard weight). This is the problem I am trying to solve.
    To try to get around this, I tried the process of removing the Helvetica/Helvetica Neue .dfont files that come with the Mac - but this didn't work and caused several other problems. Besides, the font I'm trying to get to use as intended has a different name.
    All help would be greatly appreciated - my thanks in advance.
    John

    Thanks Kappy and apologies if it is inappropriate - but just to clarify, my main question is whether fonts used in Keynote should be compatible with other software (in this case Office running on Windows). The Office for Mac Preview is a bit of a red herring but I thought it should be mentioned.
    I tried to clarify my first post, but it didn't work. What I wanted to add was simply whether Keynote handles fonts in a way that other pieces of software struggle to read - despite the font itself working perfectly in both environments.

  • Logic Pro X compatibility with mbox 2 mini and 2009 core duo macbook

    I currently have Pro Tools LE 8.0.3 and an Mbox2 Mini, both of which amazingly still work on Mountain Lion 10.8.4.  I'm interested in learning Logic and am trying to confirm compatitility with the Mbox2 Mini on a first generation core duo Aluminum Macbook (2.4 Ghz) running 4gb of RAM.  The system requirements just say 10.8.4 or later with a 64 bit processor.  The Macbook runs fine, and I primarily just record stereo piano tracks, so it's not like I'm going to have 16 tracks running on it.  Anyone using an Mbox2 Mini, and any issues with the hardware?

    It's not an external device's compatibility with LPX that matters...
    It's your external hardware's compatibility with whatever OS X version you are using to run LPX in.... that is important.
    Im guessing you upgraded OS X about the same time you switched to LPX?
    So....
    Make sure you have installed the drivers and software from this page....
    http://www.apogeedigital.com/support/quartet#tab-id-1
    Failing that, contact Apogee support for further assistance
    http://www.apogeedigital.com/support/contact-support
    Note: Why is it showing Duet and not Quartet briefly? Are you sure you installed the correct drivers or did you, at one time have a Duet?
    Additional: You might want to try this.. though I doubt it will fix things... but this can cure all kinds of weird issues...
    Delete both the main plist and the CS file...
    Delete the user preferences
    You can resolve many issues by restoring Logic Pro X back to its original settings. This will not impact your media files. To reset your Logic Pro X user preference settings to their original state, do the following:
    Quit Logic Pro
    In the Finder, choose Go to Folder from the Go menu.
    Type ~/Library/Preferences in the "Go to the folder" field.
    Press the Go button.
    Remove the com.apple.logic10.plist file from the Preferences folder. Note that if you have programmed any custom key commands, this will reset them to the defaults. You may wish to export your custom key command as a preset before performing this step. See the Logic Pro X User Manual for details on how to do this. If you are having trouble with a control surface in Logic Pro X, then you may also wish to delete the com.apple.logic.pro.cs file from the preferences folder.
    Restart the computer.
    Note: if you cannot find either of these files you didn't follow the instructions exactly as described

  • Using RSLinx OPC with Labview 2009 SP1 and Getting Wierd Problem

    I have a small test system with 4 analog inputs and 4 analog outputs. Oddly, I can use the Labview Distributed Systems Manager and read the input (level) changes and stroke the analog outputs (valves). However, when I go into a VI, I can get the level readings (only the first time I enter, after that not), but can never stroke the valves. Looking at the shared variable setup in both the project I am using and the Distributed Systems Manager, I have them both set up the same as a PSP with the same OPC reference, although formerly the project used project-attached shared variables.

    Using the timed structure set at the same acquisition rate as the OPC interface corrected the problem.

Maybe you are looking for