From Lv9.0 to Lv7.1

Anyone can help to converse the files from Lv9.0 to 7.1? Thank a lot
Solved!
Go to Solution.
Attachments:
lv9.vi ‏14 KB
lv9_1.vi ‏15 KB

attached
Attachments:
lv9.vi ‏48 KB
lv9_1.vi ‏62 KB

Similar Messages

  • Conversion from LV9 to LV7

    Hi,
    I work in a lab where LabView 7 is always used. But this morning I had to open a VI from another computer, which has LabView 9 installed... and I made the mistake of making a minor change and saving it. Now it is impossible to open the VI from any other computer in the laboratory, and LV9 won't convert it to a lower version than 8. Does anyone know a method to restore it to version 7? Or would anyone be kind enough to convert it for me and upload it here?
    I attached the file in version 9 format, then in version 8 format if needed (but I'm not sure I converted it properly).
    Thank you,
    Attachments:
    spectra_integrator.vi ‏22 KB
    spectra_integrator_lv8.vi ‏27 KB

    Hi Dominic,
    the "Upconvert" and "Downconvert" threads were created to bundle request of these kinds into one place. They were placed in the Announcement section of the forum to be available without a lot of searching. The reason for this was to avoid a lot of individual "please convert" threads (as NI isn't able to provide a service for this...)
    So please don't foil this aim in the future...
    Edit:
    Additionally this request was already answered with a LV7.1-conversion like yours. And it was already pointed out by Ravnos that he needs the LV7.0-version of the VI instead...
    Best regards,
    GerdW
    CLAD, using 2009SP1 + LV2011SP1 + LV2014SP1 on WinXP+Win7+cRIO
    Kudos are welcome

  • Recompiled from LV6.1 to LV7.0, now I can't configure CIN

    I have a VI using a CIN that works in LV 6.1 and in LV7.0 (no CIN load errors). BUT, I can't configure the CIN in LV7.0, even after reloading the .lsb file. All the inputs are unnamed as well (the pop-up says simply 'input'). But the vi still works. I have all the source code for the .lsb files.
    Any ideas what's happening here?
    Thanks.

    vituning wrote:
    > I have a VI using a CIN that works in LV 6.1 and in LV7.0 (no CIN load
    > errors). BUT, I can't configure the CIN in LV7.0, even after reloading
    > the .lsb file. All the inputs are unnamed as well (the pop-up says
    > simply 'input'). But the vi still works. I have all the source code
    > for the .lsb files.
    What sort of configuration would you want to do on a CIN node? Are you
    sure you don't confuse this with the Call Library Node?
    Rolf Kalbermatter
    Rolf Kalbermatter
    CIT Engineering Netherlands
    a division of Test & Measurement Solutions

  • Downconvert firls from LV8.6 to LV7.1

    Hi everyone,
    can someone please convert the function FIRLS (Labview version 8.6 (found on this site)) down to LabView version 7.1?
    I know, there is a solution using the MathScript but I hope there's a way without an Matlab installation.
    Greetings
    Thank you!
    Attachments:
    lms_adaptive_filt_lab_code.zip ‏206 KB

    Thank you very much for your prompt answer.
    I knew that there must be a difference between "MathScript" and "Matlab Script".
    But since I can`t find MathScript in my LabView 7.1 it might not be installed in this version.
    I think I still need the conversion.
    Greetings from cold Germany (-19°C)
    Bon

  • Upgrading from LV6.1 to LV7.1 crashes w/r nipalk.sys

    I am using a PXI-1010 chassis with a PXI-8175 controller. This controller had WIN 2000 and LabVIEW 6.1 installed with no problems. I also had no problems installing the LabVIEW 7.1 full developement system until I tried to installed the 101 modules from the full Device Driver Reference CD. When system now continously reboots with a dialog message box stating "\SystemRoot\System32\DRIVERS\nipalk.sys device driver could not be loaded Error Status 0xc000012f". How do I fix this problem?

    Hello Jimmy,
    System crashes such as the one you are experiencing are usually caused due to driver layer software. You said that the system continuously reboots. Does this mean that you are unable to do anything with the computer, or does it reboot after you perform some action?
    What I recommend is making sure that you have all of the latest drivers installed on your machine by looking for the latest driver versions at Drivers and Updates. The problem could be something as simple as a driver layer incompatibility.
    If the problem continues to persist evern after verifying the latest version of the drivers, post back to the thread with some further information. In particular, helpful information to troubleshoot such issues include driver versions, particularlly NI-PAL, detailed computer specifications, all hardware involved, how the problem is replicated, detailed error description, and a dump from the crash if possible.
    Best of luck.
    Jared A

  • Could not build an executable in LV7.1.1

    Hello,
    I have shifted my project from LV6.1 to LV7.1.1. Since them I can not
    compile an executable. The error is
    "Error 1003 occurred at [my-path]
    Possible reason(s):
    LabVIEW: The VI is not executable."
    My application works in a development-environment! What's wrong?
    Thanks Mareike

    Hello Mareike,
    It's while ago that i upgraded from 6 to 7 but I don't recall that there where many problem. (At least not as many I have now stepping over to 8)
    Can you post your VI (or part) so we can look at it?

  • Downconvert from labview 9.0 to labview 8.5

    Hi everybody,
    Please help me to downconvert the attached file from LV9.0 to LV8.5 (or LV8.0)
    Thank you for your help in advance!
    Attachments:
    PVCAM take3.zip ‏1501 KB
    pl exp setup cont.vi ‏16 KB

    You might have to do some relinking, but they have been saved in 8.5.
    There are only two ways to tell somebody thanks: Kudos and Marked Solutions
    Unofficial Forum Rules and Guidelines
    Attachments:
    PVCAM.zip ‏1899 KB

  • Serial port: from 6i without visa to 7express with visa ?????

    upgrading from NT4 6i max 2.5 to 2000 7exp max3.1 my pzt on PC serial port do not move anymore. The DA converter do not understand the instructions.
    Running max on the coms: done OK
    Looping back the visa instructions: done instructions OK
    Trying hyperterminal: done OK (the DAC move)
    the coms are in function but the DAC do not move while driving with visa...any suggestion??

    I also upgraded from LV6.1 to LV7 and use serial communication. I now use VISA (and prefer it). However, for the older functions.. they should work..
    Have you looked into the VISA Advanced controls under Interface Specific and under "Serial". You may find the functions you need to "upgrade" your serial comm vi's.
    -JLV-

  • How to check the existence of file without any error dialog?

    Hi everybody,
    I am trying update some labview programs from LV6.1 to LV7.1, I used the
    function "File/Dictionary Info" to check if the file
    exists or not (if the size=0 then file does not exist), and it ran well with
    LV6.1, but now it shows every time a labview error dialog
    about "LabView: file not found..." with 7.1, if this file dosn't exist.
    Sometimes I feel that it is really stupid to show the dialog, because I
    can write handling by myself, if the error should be handled, and
    I don't want all the process is interrupted because of such dialogs. Is
    there any way to shut the dialog down or check the existence of
    file smoothly?
    Thanks a lot!
    L.Wang

    Hello,
    The dialog is probably appearing because you have Auto Error Handling turned on.  This feature is turned on by default in LabVIEW 7.0.  You should go to VI Properties (Ctrl-I) > Execution and deselect "Enable automatic error handling".  Also you should go to Tools > Options > New and Changed in LabVIEW 7.x and deselect "Enable automatic error handling in new VIs".  If you never want to see one of those dialogs again, you can also deselect "Enaeble automatic error handling dialogs"...I wouldn't recommend this, however, as you would never know if one of your VIs had this setting enabled...you would only find out once somebody else tried to use your VI on another LabVIEW install.
    -D
    Darren Nattinger, CLA
    LabVIEW Artisan and Nugget Penman

  • Error reports converting a vi from LV8 to LV7.1

    Neatly working VI in LV8.0 for some reason I am converting it into earlier version of LV7.1. When I opened from LV7.1, I got the error message (report attached).
    Hope somebody help me out to avoid coding from scratch.
    Kousy

    NO Blk diag_LV8.vi - this has no block diagram but i could not find any problem saving it into earlier version 7.1
    Perf Print Report.vi - this is the vi i have not able to save it into 7.1 version. Even I have tried removing all the graphs I have used + printing options etc. still it is throwing out the same error msg.
    Kousy
    Attachments:
    NO Blk diag_LV8.vi ‏13 KB
    Perf Print Report.vi ‏520 KB

  • Error in calling LV7.1 dll from VS2003

    Hi everyone,
                       I developed a dll in LV7.1. I am trying to call this dll from VS2003. When a function that is in the dll is called, it throws an exception (Unhandled exception at 0x7a04f1e9 in numtest.exe: User breakpoint).
    Some help will be appreciated.

    WS Binding: exception durign SOAP invocation: java.util.NoSuchElementException
    Looks like the error is in the data sent to or expected from the service in your composite. Check that audit logs and composite flow to make sure your soap message when using soapui matches what you are working with in soa suite.

  • Dinosaur needs help changing version of this smtp llb from LV7.1 to LV7.0

    I know I am a dinosaur still using LV7.0 but if there is anyone who could help I would really appreciate it.
    Could you save the attached library in LV version 7.0?
    This is the smtp library originally from openg.org that supports SMTP authentication and has since been modified to resolve some linefeed issues and then saved as LV version 7.1
    Thanks very much!
    Bernie
    Attachments:
    OGIC_SMTP.zip ‏201 KB

    hi
    yes i can. i hope thats what you want.
    Mike
    Attachments:
    70.zip ‏164 KB

  • Bug in "Unflatten from String" (LV7)

    I have binary files with different versions of a certain datatype. When loading a file, I try to unflatten the data using the newest dataversion. If I get an error, I try the 2nd newest dataversion and so on until I found the right datatype. This methode was ok up to LV6.01.
    Now I updated to LV7.0ger and I found following bug:
    When unflatting certain binary datas from string I get an error msg window "Nicht genügend Speicher zum Abschließen dieser Operation". The error-output of the vi is incorrect.
    Does anybody know a workaround of that bug?
    You can test the bug with the attached vi. Include also the two typedefs.
    Attachments:
    f_mancalib_UnflattenTypeCalibList.vi ‏184 KB
    f_mancalib_TypeCalibrationParams.ctl ‏24 KB
    f_mancalib_TypeCalibrationList.ctl ‏28 KB

    Hi,
    From the LV's help: "National Instruments recommends reworking any
    application that uses the Convert 4.x Data mode as a long term solution.".
    Data types may vary with differenct versions of LabVIEW. So, if types are
    not the same, this does not need to be a bug. Right click the Unflatten From
    String, and select Convert 4.x Data. This might not work, because the data
    is stored with Lv 5 or 6, but when you get it working, it will keep working
    for future versions of LV.
    The attached VI shows that a sting in a cluster does not convert to the same
    type string for lv4.x and lv7. Perhaps they are the same for lv4.x and lv6.
    If so, using convert 4.x data would be sufficient. If not, you need to read
    the data in 6, save the binary 4.x strings
    , and use 4.x from then on.
    You might also do the following: (also from the help) "If you use this
    function to flatten data from a custom control or indicator that you saved
    as a type definition, the function strips the type definition of its type
    definition wrapper. If you do not want to strip this wrapper, right-click
    the function and select Expose Typedefs from the shortcut menu."
    Regards,
    Wiebe.
    "albertz" wrote in message
    news:[email protected]..
    I allready told this to a NI tech support in Germany. They told me,
    the bug is known, but they do?nt have a workaround.
    So I hope for LV7.1 or maybe LV7.01.
    [Attachment Different Types.vi, see below]
    Attachments:
    Different_Types.vi ‏22 KB

  • How do I read a range of data from an open and "live" Excel file using LV7.0 Express

    I need to interface with software which continuously (once per second) writes a new array to a fixed location in an open Excel file. I would like to read this data into Labview from where I can do what I like with it. I am relatively new to LabView and have tried all "Read Data" examples that come with the product, Active examples seem very unclear. Anyone got any samples/suggestions to get me started?
    Attachments:
    Changing_Excel_file.xls ‏17 KB

    It is possible but might be a little bit complicated. Does your application opens the Excel file or Excel file was opened through Excel or another application already?
    In the first senario, once the excel is opened, start reading the data, do not close the report file (dispose the report) or close the excel file
    In the second senario, it is a little bit more complicated. You need to use low level Excel ActiveX functions. The procedure is:
    1. Open reference to Excel
    2. Activate the desired workbook if it is already opened
    or open a new file
    3. Activate the sheet containing the data
    4. Read the data
    5. Loop if necessary (step 2 if diff wb, step 3 if diff sht, 4 if same sheet)
    6. Close Excel reference (Very important, close the
    ref only, do not use Application.Exit to exit Excel).
    Hope this helps,
    -Joe

  • Importing vi from LV7.1. to LV2010 is OK but I can not buid exe

    Hello,
    Last month I installed LabView 2010. Before I used LV7.1.
    I tried to import my odl VI's into 2010 and thay work when loaded in Labview, but when I want to create an .exe file I get the the message below.
    Can you please help me what to do.
    Regards,
    Damir
     This is what I get on my screen: 
    Possible reason(s):
    LabVIEW:  Unexpected file type.
    Complete call chain:
         Get LV Class Default Value.vi
         AB_UI_Initialize_Framework.vi
         AB_UI_FRAMEWORK.vi
         AB_Item_OnDoProperties.vi
         AB_Item_OnDoProperties.vi.ProxyCaller
    LabVIEW attempted to load the class at this path:
    <Empty Path
    Attachments:
    LV_exe.doc ‏37 KB

    Hi,
    Did you try to mass compile your VIs before building your EXE ? This may help : Tools>>Advanced>>Mass Compile .
    Regards,
    Da Helmut

Maybe you are looking for