Will Labview VIs developed on a MacIntosh run on a Windows PC? How about visa versa?

Will Labview VIs developed on a MacIntosh run on a Windows PC?  How about visa versa?
Thanks,
Dennis U

As long as you don't use platform specific tools (such as IMAQ vision, ActiveX...), or advanced DAQmx functions, LabVIEW portability between platforms is excellent.
On MacIntosh, LabVIEW works fine with virtual PC, but is very slow (5-10 times...). Try it and see if it suits you needs.
Message Edité par chilly charly le 01-09-2006 09:19 AM
Chilly Charly    (aka CC)
         E-List Master - Kudos glutton - Press the yellow button on the left...        

Similar Messages

  • Will Adobe Photoshop Elements 8 install and run using Windows 8 OS

    Will Adobe Photoshop Elements 8 install and run correctly using Windows 8 OS?

    Hi regnis33,
    Please find the system requirement for installing Photoshop Elements 8: http://helpx.adobe.com/x-productkb/policy-pricing/system-requirements-photoshop-elements.h tml
    Regards,
    Romit Sinha

  • Are LabVIEW VISA functions supported by LabVIEW Run Time Engine?

    I have an executable file that I created using LabVIEWS Application Builder. When I run the application on another computer that does not have LabVIEW installed, it crashes with a Windows message stateing the my application has generated erros and will be shut down by Windows. I have isolated the problem as having something to to with VISA Reasource Names.
    Does anyone know if there has been any issues regarding the use of VISA function in LabVIEW Run Time Engine? The version of LabVIEW that I have is 6.0.2. The version of Run Time Engine is 6.0 .
    Dan

    Yes there are issues with the RTE 6.0 and VISA. Use the RTE 6.0.2
    LabVIEW, C'est LabVIEW

  • Will LabVIEW 5.1.1 run on Windows XP?

    Will LabVIEW version 5.1.1 run on the Windows XP operating system?

    We have recently installed it on WinXP, don't have a real feel for any possible issues, but the only noticeable issues was a little error message box "Wrong OS", which goes away when clicked. Good luck.
    Putnam Monroe
    Putnam
    Certified LabVIEW Developer
    Senior Test Engineer
    Currently using LV 6.1-LabVIEW 2012, RT8.5
    LabVIEW Champion

  • Will LabVIEW run in Windows Azure ?

    Will LabVIEW run in Windows Azure? If not, why not?

    Hi, I'm on the NI cloud team, and thought I'd chime in here even though the thread's old. We've been doing work with both the Amazon and Azure clouds.
    We have LabVIEW working on Amazon just fine, in fact the LabVIEW FPGA Compile Cloud that's in beta right now is hosted on Amazon EC2.
    We've been working with Microsoft Azure as well.  I haven't yet tried to deploy LabVIEW on it, it should be possible to try as of the Azure 1.3 release by using a startup task although those may have an eventual timeout (LV installs take a while). Azure role instances are not meant to be long running and the disk on them is completely ephemeral. Probably using a VM role would be better. This isn't guaranteed to work because various low level drive stuff may run afoul of the limitations (Azure isn't *quite* stock Win2008R2, it does have limitations). The wrinkle will probably be licensing.We had to bypass our own usual licensing scheme to work on the dynamic cloud for Amazon.
    This is a good candidate for the idea exchange, perhaps I'll add on there too.

  • Verify Labview Vis before starting execution in release mode

       I have a TestStand sequence that calls a number of Vis. When I switch from development mode to the run-time engine, sometimes the TestStand sequence crashes at certain Vis. I then find that when I switch back to developement mode and open the vi, it has a start next to the filename, which indicates that the file needs to be saved. When I save the files, that step works fine in run-time mode, but then the sequence crashes on the next step that has this problem.
       How can I find out which files need to be resaved before running something with the run-time engine? Is there a way to precompile everything so this doesn't happen?

    Steve,
    It sounds like you are running your VIs with the LabVIEW runtime engine.  For this operation, we recommend that you do a TestStand deployment using the Deployment Utility.  The TestStand Deployment utility will save all of your VIs and make sure that they are packaged correctly so you can call them from TestStand without the LabVIEW development environment installed.
    Please see Chapter 14 of the reference manual for detailed instructions for deployment.  You also might find this knowledge base helpful: Deploying TestStand Systems
    Josh W.
    Certified TestStand Architect
    Formerly blue

  • Stand alone labview application (.exe file) does not run properly

    Hi all,
    I am trying to make a stand alone labview application to run on another computer ( I have never done this before).
    I went through the tools->build application prompts and was able to build an exe file.
    the program is supposed to control a power meter and make power measurements then save them to a text file.
    When I run the exe file, on the same computer I compiled the exe file on, the program generates a text file to save data to but it can not communicate with the power meter.
    There are some sub-VIs and a dll file that are used to communicate with the power meter. Could it be that I am not telling labview to correctly
    include these files when I create an executable?
    What are some common problems that occur when generating stand alone applications that could be causing my issues?
    And does anyone know of any good tutorials on generating stand alone applications in labview other than the NI help files?
    Thanks for your help,
    Solved!
    Go to Solution.

    edCubed wrote:
    Hi Bill, thanks for your suggestions.
    I haven't tried to run this app on another computer yet. I'm just trying to run it on the computer it was developed on.
    The computer I developed it on has all the drivers/resources I need to control the power meter.
    Also, I don't know how to include the VISA runtime with my installer. could you explain how this is done?
    This is the first time IV tried to turn any labview programs into stand alone exe files so I don't anything about how to do it other than what I've seen in youtube videos and help files.
    If you know of any good tutorials that will help me figure this out I would appreciate it.
    Thanks,
    My fault - I didn't read that this was the same computer.  I know the very end of Core 3 studies shows how to build an executable and installer, but even that is very general.  I'm not sure if there exists a tutorial on how to do it.
    As for including the runtimes, when you build an installer, you have to include the runtimes that your executable will need.  It's fairly straightforward.
    Since it won't run on the machine that built it, I'll have to think about it a little bit...
    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.

  • Calling labview VIs from python in Linux

    Hello.
    I've spent some time searching for this but I haven't found exactly what I was hoping for.
    I'm involved in a project that we're starting now and it involves creating a complex software architecture in order to control a robot. This software will need to perform multiple tasks such as interfacing with hardware (which LabView is perfect for) as well as planning and high performance image processing (which LabView isn't as great for).
    I was hoping to be able to use a scripting language like python to manage high level stuff (planning, behavior, etc) by calling "subroutines" in other languages such as C++ for the high performance stuff and LabView VIs for the hardware interfacing. I would also like this to run on Linux.
    I've found a lot of suggestions on how to call Python scripts from within LabView but this is not what I want. I want exactly the opposite, invoke VIs from Python. I found some information on how to do this on Windows (http://zone.ni.com/devzone/cda/tut/p/id/5719) but this article seems to assume that Windows is being used.
    Does anybody have an idea on how to do this? 

    Unfortunately that's not an option. This is an interdisciplinary school project involving students from engineering (mechanical, electrical and more), computer science and more fields. Some of these students have gotten used to using Labview and this is the main reason I'm trying to accomplish this. I want to have the higher level architecture done in a scripting language such as python which will enable us to create modules in various different environments such as C++ for tasks requiring high performance (image processing for example), Labview for tasks that the people used to using that and even something running on the GPU if there's use for that. Python would make it easy to glue all these components together while maintaining an environment that would make it very easy to configure the whole software system in different ways.
    I'd also prefer that this all run on Linux.
    The more I look for this the more hopeless I get I'll find anything which is very frustrating. It's a bit hard to believe that Labview doesn't have "python bindings" for running the VIs from within python :-(

  • What is the best way to organize LabVIEW VIs to be used with TestStand?

    I'm using LabVIEW 8.6 with TestStand 4.1.1 and I'm trying to organize the VIs to later deploy them to a production PC. So, I organized them into a LV project and built a LLB with the "Source Distribution Tool". (Destination type: LLB)
    Some VIs in the LLB use the "Call Library Function" (user32.dll) to simulate keyboard events. But, when any of these VIs is called from TS, LabVIEW is suddenly terminated. When these same VIs are not in the LLB and are called from TS they do not have any problem.
    Is the LLB the best way to organize VIs to be used with TestStand? If so, What could I be doing wrong?
    I appreciate your help.
    H.P.
    Mfg. Test Engineer
    Certified LabVIEW Associate Developer
    Attachments:
    LabVIEW Problem.JPG ‏28 KB

    Hi Ray,
    I really appreciate your intention to help, but I believe I solved the problem already. However I still have some questions.
    The problem was that when I built the LLB the configuration of the "Call Library Function" changed. When the LLB is built it is also created a Support Directory named "data" that contains some dependencies including a new copy of the user32.dll. The "Library name or path" field in the "Call Library Function" changed to be linked to a new Dependency Path. ( ...\data\user32.dll.)
    What I did was select "Specify path on diagram" and create a path-constant ("C:\WINDOWS\system32\user32.dll"), so the "Call Library Function" will be always linked to the original user32.dll.
    I still don't know why the "Call Library Function doesn't work with the user32.dll copy in the New Dependency Path. And I'm not sure if the LLB is the best way to organize VIs to be used with TestStand.
    Do you know why?
    Thank you,
    H.P.
    Mfg. Test Engineer
    Certified LabVIEW Associate Developer

  • Logging data in a file using Labview VIs vs. Mathscript functions.

    Hello,
     I'm working on a data logger at 200 Hz frequency. I wanted to log the data to a file after eace sample received. When I used (fopen,fprintf,....) on Mathscript, the Labview started to log the data at a slower rate. I then used the Labview file VIs and it is working fine up till now.
    My questions are as follows:
    1- Are the file functions in the Mathscript slower than the Labview VIs ?
    2- Is saving the data to a file after each sample is received a good idea or is there a better idea ? I just don't want to keep the data in the memory and after all the data is logged, I flush them to a file ... because, it seems that the PC will run out of memory.
    Thank you,
     Walid

    wfarid wrote:
    Hello,
     I'm working on a data logger at 200 Hz frequency. I wanted to log the data to a file after eace sample received. When I used (fopen,fprintf,....) on Mathscript, the Labview started to log the data at a slower rate. I then used the Labview file VIs and it is working fine up till now.
    My questions are as follows:
    1- Are the file functions in the Mathscript slower than the Labview VIs ?
    Yes. That's because you're going through another layer of software. Why were you trying to use MathScript to log data to file in the first place? Are you a Matlab "aficionado"? 
    2- Is saving the data to a file after each sample is received a good idea or is there a better idea ? I just don't want to keep the data in the memory and after all the data is logged, I flush them to a file ... because, it seems that the PC will run out of memory.
    It doesn't make sense to save data after each sample. File I/O is an expensive operation in terms of time, and you have the operating system to deal with, so while you may be able to keep up the rate for some time, eventually it will be thrown off. You can do as suggested which is to wait until you have a certain amount and then write that to file, or you can set up a producer-consumer or master-slave architecture. Let one process/loop collect the data and put into a buffer, like a queue, and the other process/loop can stream it to disk at a more reasonable rate. You just have to make sure the buffer is large enough so that if the file I/O gets hung up you won't reach the buffer's limit.

  • Labview Full Developement System 8.2 on Windows 7

    Hi there,
    I have a question about the compatibility of Labview Full Developement System 8.2 and Windows 7.
    Is it possible to run this system without problems on a PC that is using Windows 7?
    I am also using the Labview DSC module (version 8.2.1).
    I'm just wondering if I will get problems when I am going to run programs that I made, in Windows 7.
    Or is there a new version of Labview that is compatible with Windows 7?
    If so, is it possible to use older versions of Labview in this new version (bij transfering the files).
    I hope to hear soon from some of you.
    Regards,
    Kenny

    LabVIEW 2009 is the first LabVIEW version officially compatible with Windows 7 (see also)
    Quote: Starting with 6.0.2, LabVIEW should run on newer, unlisted versions of Windows without error messages, but these are not officially supported.
    (However, I was able to run LabVIEW 8.2 just fine under windows 7 64 bit. I don't know if there are potential DSC issues. Another option is the windows XP compatibility mode virtual PC available for some version of Windows 7).
    LabVIEW 2009 and 2010 are fully compatible with Windows 7. You should be able to open your LabVIEW 8.2 files fin in any newer version. For details, have a look at the LabVIEW version compatibility matrix.
    LabVIEW Champion . Do more with less code and in less time .

  • Some errors when calling LabVIEW VIs Interactively from DIAdem

    Hi! I'm having some trouble using the "Calling LabVIEW VIs Interactively from DIAdem" found on:
    http://zone.ni.com/devzone/conceptd.nsf/webmain/1A98AB48E35D913086256E23004E6A22
    Following the troubleshooting section didn't resolve the issue. I
    recompiled and built the exe (DIAdemLabVIEW.exe) for version 7.1.1,
    which I am developing on. But still I got the same error message, after
    a waiting for about a minute, on a diadem popup window:
    Error in <MenuAdd...ctDo.vbs (row:1, column: 1)
    Error in <addmenuentry.vbs (row:14, column: 3)
    ActiveX component can't create object.: 'DIAdemLabWIEV.Application'
    Using the llb's and exe's that was included with the installer worked
    flawless, with the exception that LV 7.1.1 vi's didn't appear on the
    popup window(DIAdemLabWiev.vi). So I tried to recompile and build for
    the 7.1.1, with this result.
    I'd be very grateful for fixes or solutions for this problem!
    Regards
    Roger Isaksson

    Brad, thanks for the reply! Below is my (correct?) modification of your script. Have I got it right?
    Dim lvapp, vi, viPath, paramName(1), paramVal(1)
    Set lvapp = CreateObject("LabVIEW.Application")
    viPath = "C:\TEMP\Test.exe"
    Set vi = lvapp.GetVIReference(viPath)
    vi.FPWinOpen = True
    paramName(0) = "In Name"
    paramVal(0)  = "In Value"
    paramName(1) = "Ut Name"
    Call vi.Call(paramName, paramVal)
    Call lvapp.Quit()
    MsgBox "Parameter1 Value = " & paramVal(1)
    I am not sure about the format of the <paramName(0) = "In Name">.
    The control name is "In" and is a I32, the name for the indicator is
    "Ut" and has the same storage type as the control.
    Running the script gives an error in line 4, that is the <Set vi =
    lvapp.GetVIReference(viPath)>. I'll attach the exe and the error
    message.
    I have another question regarding the relatively large amount of RAM
    that diadem uses for export from my labview application to diadem. More
    than 10 times the size of the data is required for exporting to diadem.
    Since our application use relatively large files, actually up to
    several GB's, this soon becomes problematic. See the attached picture
    of the memory usage after exporting a 10MB segment (contains 42
    channels of measurement data). Your help in these matters would be
    appreciated!
    Regards
    Roger Isaksson, Damill AB
    Message Edited by Roger Isaksson on 09-09-2005 10:22 AM
    Message Edited by Roger Isaksson on 09-09-2005 10:22 AM
    Attachments:
    VBError.JPG ‏181 KB
    Test1.vi ‏9 KB

  • Certification Nugget: CLAD - Certified LabVIEW Associate Developer

    About the CLAD Exam:
    The clad_exam_prep_guide_english.pdf states that "A CLAD demonstrates a broad and complete understanding of the core features and functionality available in the LabVIEW Full Development System and possesses the ability to apply that knowledge to develop, debug, and maintain small LabVIEW modules."  In other words, you should be able to to string LabVIEW functions together into meaningful LabVIEW code in accordance with LabVIEW best practices.  You are mostly book-learned, but can develop and maintain small VIs, updating them as necessary.
    The test itself is a one-hour multiple-choice exam with a passing grade of 70% and is available at Pearson VUE testing centers or NI branch offices.  You'll get something to write on, and something to write with, in case you have to work out some problems.
    NI Preparation Information:
    The Certified LabVIEW Associate Developer (CLAD) Exam Preparation E-Kit is National Instrument's official CLAD exam prep kit.  You will find links to their exam prep guide, practice exams and other helpful items.
    My Journey to become an NI Certified LabVIEW Associate Developer:
    After quickly reviewing a sample CLAD test, in May of 2013 I walked into a test center, took the test and passed.  Simple, huh?  In truth, it was the culmination of about seven years of preparation - although I hadn't thought of it as such back then.  It was all about visiting the NI LabVIEW Forum at least once a day, even if I had no questions to ask.  Sometimes I just combed the forum looking for interesting topics.  If I didn't understand something, I wasn't afraid to ask questions.  I wasn't afraid to defend my position.  (And occasionally I was even right!)  Eventually I found that I was answering questions as well as asking them.  My next question to ask was to myself: "Why not try the CLAD test?"  So I glanced at a sample test, realized it felt more like a review than a test, walked into a test center, took the test and passed.
    The reason behind my getting certified was to have something on my resume to compete with LabVIEW developers that had twice as much experience - or more - than I did.  Seven years of experience may seem like a lot, but it's not.
    Since then, I had become a CLD.  With the CLAD, I showed that I knew basic LabVIEW concepts; with the CLD, I showed that, not only could I talk the talk, I could walk the walk.  (The CLA shows that you can talk the talk and walk the walk, all while chewing gum and juggling a few chainsaws.)
    My Personal Recommendations to Candidates:
    This section will be a bit different than the corresponding sections in the other certification nuggets because there are really no specific strategies to doing well on the test other than know how to do well on a multiple choice exam.  Instead, I will focus how to gather the LabVIEW knowledge necessary for you to pass the exam as well as discuss the path forward.  That being said:
    Check out the CLAD kit for sure, but I cannot stress enough the importance of being a regular visitor to the NI LabVIEW forum.  The LabVIEW Gurus live there.  Ask questions.  Ask for clarification.  Fill up from the information fire hose.  If you're like me, it will only make you thirstier.
    Follow the tutorials listed here (at the bottom, Looking for Free Training).
    If you own a copy of LabVIEW or have LabVIEW installed at work, check to see if there is an active SSP.  Oftentimes your employer doesn't even realize that the license includes free online training and is very glad to let you make use of it.  Just make sure you get permission.  It is their license, not yours.  With the SSP you can take the online equivalents of the LabVIEW CORE classes (1,2 and 3) as well as a host of other courses.
    Get the LabVIEW Home Bundle!  It's the LabVIEW FULL Development system - for $50!  You can't use it for commercial use, but heck.  FIFTY BUCKS!  Nothing like learning by doing.
    Use the CLAD as a stepping stone to your CLD.  You got your CLAD to distinguish yourself from the crowd only to learn that having a CLAD is like being a second lieutenant in the army.  (Hint: The army is full of them.)  Study hard and get that CLD!  Become a senior officer!  Show the world - and yourself - that you are serious about LabVIEW!
    Comments?
    I hope you found this nugget to be useful.  I invite you to share your CLAD experiences: "The thrill of victory and the agony of defeat," as it were.  To the candidates: Study hard.  Soak up the wealth of information from the NI LabVIEW forum.  Fear not the CLAD test.

    gregoryj wrote:
    I've been hesitant to take the CLAD because I've read that it really doesn't mean much, and should not be taken if you don't intend to take the CLD. In my current position, I never work in a team (on software) or make very large applications, so I'm not sure my experience would prepare me for the CLD.
    While it's true that it is a stepping stone to the CLD, it can also be used as a measuring stick to see how much you really know about LabVIEW.  I actually think it could benefit you greatly because it will really make you start thinking "LabVIEW" if you haven't already.  It's cheap and it's a short test.  It could be a wise investment.
    Plus, many places I've interviewed for give you a few questions right out of the practice exams to gauge your experience level.  If you show that you're a CLAD, they may waive that test.  In fact, some LabVIEW houses have been known to take a CLAD and train them up the a CLD - and pay for the test!

  • Is it possible to take a labview application and compile it to run on an embedded processor?

    Hi
    I was wondering if anybody out there knows if it is possible to take a labVIEW application and compile it to run on an embedded processor (e.g. ARM7)?
    If so does anybody know what the required capability of the target processor is (i.e. RAM, ROM etc.) and what tools I need.
    Many thanks
    Ash

    Ash,
    There is also another option for processors like the ARM7.  You can load a PDA OS on it and use the LabVIEW PDA toolkit.  The LabVIEW PDA toolkit is MUCH easier to use and is quite a bit less expensive.  You will have the problem of getting the OS correctly configured, but in the long run, it may still be cheaper and easier.  I use it quite a bit with my Dell Axim X51v which has this processor and Windows Mobile 5.  There are still problems to work out, but not nearly what there are with LabVIEW Embedded.
    If you want to go the LabVIEW Embedded route and you need some help, let us know on this forum.  There are several of us that have experience and can help to guide you.
    Hope that this helps,
    Bob Young
    Bob Young - Test Engineer - Lapsed Certified LabVIEW Developer
    DISTek Integration, Inc. - NI Alliance Member
    mailto:[email protected]

  • LabVIEW Base Development System for Windows

    Hello,
    I want to buy "LabVIEW Base Development System for Windows", but i have some questions, include this version functi...
    a)TDMS streaming VIs
    b)Wavefoem VIs
    and the last question, is it possible with this version do some executable code?
    thanks for all..

    Here is a decent list of the differences between the versions of LabVIEW.  Since you want to create executables, you will need to add the Application Builder.  If you find there are other functions that you may need, I would just bump up to the Professional version.
    There are only two ways to tell somebody thanks: Kudos and Marked Solutions
    Unofficial Forum Rules and Guidelines

Maybe you are looking for