Unable to install labview real-time

I just successfully installed labview v8.0 on a pc and this is my first time to ever use this application. I was trying to install labview real-time v7.1 for my cRIO.  Unfortunately, it failed to install. I received an error message saying that I needed to have LabView 7.1 prior to the installation. LabView 8.0 is working great and I dont understand why does LV real-time wants an older version.
Do I have to uninstall LabView v8.0 and order an older version to get labview v7.1 to get running?
Any insights for a newbie will be greatful.
Thanks 

What do you mean by "I was trying to install
labview real-time v7.1 for my cRIO"?  It is not clear if you got
the error when installing that piece of software in the cRIO RT
controller or when you were installing the software on your PC.
Nonetheless, if your intention is to use LabVIEW 8.0, then there is no
reason why you need to install anything that has to do with LV 7.1
(such as cRIO RT support for LV 7.1 on your PC or LV RT -real-time- on
the controller). In your case, it seems to be ok to ignore errors
related to LV 7.1; it could have been that the computer you are
installing NI software on had an older version of LV that was not
properly uninstalled.
BTW, the installers should be smart enough to install the right
versions you will need given you install LV 8.0 first. To ensure all
needed pieces are installed, make sure you run the installers in this
order: LabVIEW first, followed by LV RT and/or LV FPGA, and NI-RIO last.
Hope this helps.
JMota
National Instruments

Similar Messages

  • Unable to locate labview run time engine (lab view 8.5)

    Hello I have a problem whit the labview 8.5 installer. I have created I project with included a .vi file (a simple panel wich control a serial port, with parameters (baud rate, stop bits, ...)), then I have created an application for this file (.exe) and then the installer (I have included the labview run time engine 8.5). When I run the setup.exe  I have the following error message:
    Unable to locate labview run time engine, the application require a labview run time engine 8.5 or compatible...
    What I'm missing??
    Thanks
    Maurizio

    are there one other reasons why it would not work.  I have asimilar problem.
    I intsalled version 8 of run time engine and acrtivated software.  Now I am trying to run compiled application provided to me by third party.
    When I click on application it says
    Unable to locate LV run time engine
    Test server requires a version 6.0 or compatible LV engine.
    How do I know if the engine I installed and activated is running and is it supposed to be able to execute a program which is expectin rev 6 of the rund engine?

  • Do I have to use LabVIEW Real Time with a reflective memory node?

    For reference with an external data system that will be temporarily installed at a customer's site, they have asked that I tie into their data network to record data from their control system.  They apparently use a reflective memory network for data sharing.  I have no prior experience with reflective memory, but all references to it involve real time systems.  I do not need absolute determinism to acquire this data, I can be late by several milliseconds with no problem.  Do I still need to use LabVIEW Real Time to interface with the PXI reflective memory node?

    Hi AEI, 
    I have worked with that card briefly before. It has a Visa based driver and RT isn't required. However, I haven't worked with the card on a non-rt system and am not sure if there any issues to be aware of. 
    A lot of work has gone into integrating support for the card into Veristand, it may save you enough development time to use at an RT-Veristand system to be worth the extra cost. 
    Jesse Dennis
    Design Engineer
    Erdos Miller

  • How do I talk to 1-Wire devices with LabVIEW Real-Time?

    Hello, I'm trying to use LabVIEW Real-Time to talk to some older 1-Wire devices that my company has previously communicated with using C code.  We are currently developing on a cRIO and are trying to use a Dallas Semiconductor 2480 serial port device to talk to some iButtons and a secure SHA 1-Wire device.  I have run into a few problems where the 1-Wire device stops communicating and just repeats the data sent to it.  I was wondering if anyone has successfully created any VI's to talk with 1-Wire devices via the serial port that do NOT use any kind of Java or .NET or Windows based device drivers supplied by Dallas Semi.  A last resort would be that we keep the C code and place it in a block in LabVIEW and run it as is but I would prefer to have some LabVIEW-native code.  Any help would be greatly appreciated.  Thanks.

    Brian_T,
        Thanks for that link about compiling a shared library for use on a VxWorks cRIO.  The only thing they mention that I don't understand is this bit:
    "GNU toolchain distributed with Wind River VxWorks"
    I have been unable to locate a compiler for VxWorks so I am assuming that is located in this GNU toolchain thing?  Does that come with the cRIO?  I think I noticed a VxWorks C compiler somewhere else online but we're talking a totally different product I would have to purchase, assuming it would even work.  I guess once the stub and the shared library are all good to go, I just call the C functions in the shared library and when it comes time to talk to the serial port, just slap a VISA Read/Write VI on the block diagram.  I've been using a cRIO and COM1 access for some time now so I do understand at least that much.  Let me know how to get ahold of this "toolchain" thing.  Thanks.

  • Is Ardence RTX required when I use PCI-7831R with labview real-time module for RTX target

    I am new in the labview real-time field. I want to use labview real-time module for RTX target on only one desktop. My card is PCI-78331R.  Is Ardence RTX necessary? Why I cannot find my card in the MAX after I configured the RTX?
    Thank you very much.

    Hi Ziaozhongda,
    You must have the RTX runtime engine installed before the LabVIEW Real-Time RTX module will install.  Additionally, you should follow the instructions in the "Using the NI PCI-7831R with the LabVIEW Real-Time Module for RTX" section of Getting Started with the NI 7831R (page 8).
    Please see Configuring Hardware for Use with RTX.
    Also useful is "How Can I Validate That My PC Will Run RTX?

  • Difference entre Deployment License for Standard PC's- ETS RTOS et LabVIEW Real-Time Debug Deployment License

    Premier question j'ai develloper suite 2009 SP1.Avec a été fourni le Deployment License for Standard PC's- ETS RTOS sauf que c'est la version Labview Real Time 8.2 Pourquoi ce n'est pas 2009 SP1 ?
    Et la deuxieme question est : qu'est ce que LabVIEW Real-Time Debug Deployment License ?
    Merci

    Bonjour Lunik,
    Merci d'avoir posté sur le forum National Instruments.
    Il n'est en effet pas normal que vous ayez la version 8.2 du module RT si vous possédez la version de Developper Suite 2010 (qui inclus LabVIEW 2009 SP1). Si vous parlez bien du module LabVIEW RT, vous ne pouvez avoir une version antérieure que celle fournie avec la suite.
    Si vous aviez une ancienne version installé, je vous conseille, si ce n'est pas le cas, d'installer tous les modules dont vous avez besoin depuis les disques d'installation de la Developper Suite.
    Pour votre deuxième question, je vous renvois à cette page : ici.
    Ce logiciel permet de déployer une licence pour faire d'un PC une cible RT.
    Cordialement,
    Romain P.
    National Instruments France
    #adMrkt{text-align: center;font-size:11px; font-weight: bold;} #adMrkt a {text-decoration: none;} #adMrkt a:hover{font-size: 9px;} #adMrkt a span{display: none;} #adMrkt a:hover span{display: block;}
    >> NIDays 2011, le mardi 8 février au CNIT de Paris La Défense

  • To develop an VI to aquire data of thermocouples from a remote chamber in labVIEW real time, should use NIDAQ or NIDAQmx?

    Hai
    I need to develop an VI to aquire data at real time. Am using LabVIEW RT as the OS and i need to know, if i can use NIDAQ 7.0 or should i use NIDAQmx? what is the diffrence between the two? is it just that NIDAQmx makes job simpler?
    Also can anybody please tell me, how to access a channel in labVIEW? am not clear about the path to follow to get the physical channel as a virtual channel on the LabVIEW.
    I am using a 8186 PXI with labVIEW RT and a SCXI, with both scxi and daq card on the same chassis.
    the development will be done on Windows XP which will be the host machine.
    Thanx in advance for any answers
    Arun

    Arun,
    DAQmx is our new Data Acquisition driver and should be considered as the primary option when writing new applications because of supportability in the future.
    DAQmx does make Data Acquisition tasks much simpler, abstracting many of the board implementation details and giving you a common API for 99% of the tasks you might want to accomplish.
    There are a couple of minimum requirements for using DAQmx on LabVIEW Real Time:
    - You will need LabVIEW Real-Time 7.1 (or higher)
    - You will need DAQmx 7.2 (or higher)
    These requirements are mentioned in the following Knowledgebase:
    Is NI-DAQmx Supported in LabVIEW Real-Time?
    The other thing you might want to make sure of is that DAQmx supports the DAQ hardware you already have or are planning to use. DAQmx does support most of the existing DAQ and SCXI hardware products, and reading thermocouples should become a very simple task.
    With DAQmx you can use physical channels, Global Channels (Aliases for preconfigured physical channels, equivalent to the Traditional DAQ Virtual Channels) or DAQmx Tasks (Preconfigured Data Acquisition tasks that include channel, timing and triggering information). A good place to start to learn about these features could be:
    Advantages of NI-DAQmx
    The following link might be useful to check Hardware support:
    http://www.ni.com/support/daq/versions.htm
    The driver can be downloaded by following these links:
    ni.com -> Support -> Drivers and Updates -> Current Software Versions -> Multifunction DAQ -> NI-DAQ Version 7.3 for Windows 2000/NT/XP
    This includes the latest version of DAQmx and our Traditional DAQ driver. Please note that DAQmx base is also listed but that's our Register-Level Programming (RLP) driver, which provides DAQ support for previously unsupported platforms.
    I hope this helps,
    Alejandro

  • VI containing Event Structure will not receive front panel events in LabVIEW Real-Time.

    Hi again, I'm working in my first UI (attached VI).
    It works when running directly from PC. It doesn't when running from cRIO, there's the message "VI containing Event Structure will not receive front panel events in LabVIEW Real-Time". I've been reading and I found that "Event structures on RT targets do not support events associated with user interface objects, such as VI panels or controls. For example, associating the Value Change event with a control does not work. RT targets support only user events".
    Is that the problem? If it is, how can I create Mouse Up, Mouse Enter, Value Change (or other user interface events) user events?
    If I run my VI in FPGA mode should it run?
    Attachments:
    HMI.vi ‏33 KB

    Since it looks like you are new to the whole RT and machine control, I recommend giving this a good read: NI LabVIEW for CompactRIO Developer's Guide
    There are only two ways to tell somebody thanks: Kudos and Marked Solutions
    Unofficial Forum Rules and Guidelines

  • How come you can not use more than 126GB of a 1.5TB diskdrive with LabVIEW Real Time?

    How come you can not use more than 126GB of a 1.5TB diskdrive with LabVIEW Real Time?
    This is only 8.3% of the available disk drive space!
    http://digital.ni.com/public.nsf/allkb/E7E2F5657B6​026358625750B007201A6?OpenDocument
    National Instrument's solution is either reformat you drive to less than 126GB or replace the drive with one less than that size.
    Please NI, tell me you are going to fix your LabVIEW Real Time soon, and that we won't have to wait for LabVIEW RT 9.2.1 in 2011 for this one to be fixed.
    http://upload.wikimedia.org/wikipedia/commons/9/90​/Hard_drive_capacity_over_time.svg
    Drives as large as 126GB or more have been around since about mid 2002.  That's about 7 Years now and LabVIEW Real Time STILL can't use drives larger that 126GB!  Please NI.  Do something.
    We deserve fixes to the old versions of LabVIEW RT.  How about updates to LabVIEW RT.  Such as 7.0.2, 7.1.2, 7.6.2, 8.0.2, 8.2.2, 8.6.2.
    We don't need new features or versions of LabVIEW RT such as 9.0 until we have some of bugs fixed in the existing versions. 
    Kevin. 
    Message Edited by kmcdevitt on 05-29-2009 03:39 PM
    Solved!
    Go to Solution.

    Coq rouge wrote:
    NI is not making the Real Time OS in house. I do not remember which firm that is making it. Anyway you are allowed to use a hard drive that has been partitioned. And 126GB is some space is it not? I remember Bill Gates declared one time that 640Kb ram should be more than enough for any PC application also in the future 
    Coq Rouge (formerly t06afre),
    The RealTime OS is an NI Product that is purchased from NI.
    NI may or may not outsource design, developement, or manufacturing of the products that it sells under its own Company name.
    For this reason I would be concerned if I were a PXI Embedded Controller designer/developer in the United States. 
    Yes, 126GB is some space.  I see that there are now 2TB drives available.  126GB would be 6.3% of a new 2TB drive.  Should we all be happy with being able to use 6.3% of the available drive space.  Moore's Law seams to be alive and well.  Drives larger than 126GB have been readily available for 5 or 6 Years.  This should not be a surprise to NI.  Why don't they do something about it.
    Thanks for the trivia on Bill Gates.  I must have missed that one since I don't try to keep up with Microsoft.  I believe that he is a wonderful person and he and his family are doing wonders for the world in their "retirement".   The world needs more like him.
    What I do remember is Steve Jobs telling us that we would never need more that 128MB and that we would never to need to do anymore software development because everything was already in the "ToolBox".
    McKevin.  

  • Can I use Labview real time with PCI 6013?

    How much does Labview real time cost?
    Do i need to have some additional hardware to use labview real time with PCI 6013?

    You can not use the PCI-6013 board with LabVIEW Real-Time.
    We offer three platforms for LabVIEW Real-time. PXI embedded controllers, 7030 data-acquisition plug-in boards (7030/xxxx) and FieldPoint. For more information on these options go to www.ni.com/products and then choose Real-Time from the menu on the left. There are PCI versions of the 7030 boards. Each 7030 board has a data-acquistion board attached to it (6030E, 6040E or 6533). When you embed a LabVIEW Real-Time program on the 7030 you will be able to access the daughter board. You can not access other boards from the embedded program. If you want to use several daq cards in your real-time system I would recommend a PXI chassi and PXI daq boards.

  • Desktop PC as LabVIEW Real-Time Target and DAQ ISA card

    I want to use LabVIEW Real-Time (Desktop PC + OS Pharlap ETS) for operation with DAQ ISA card.
    Pharlap ETS supports operation from Windows dll and can supports Third Party Device PCI.
    Whether there is a possibility to work with ISA card in Pharlap ETS?
    I want to work for example with card PC20TR from BMC Messsysteme GmbH.
    Does anyone have tricks for using ISA card in Pharlap ETS?

    Hi,
    If you have reviewed the requirements for a Real-Time target and verified that your computer is compliant you might want to check out this article.  The main issue that people encounter when using PC's as RT targets is have the correct network card.  Make sure the card you have is on the supported devices list on the webpage that Christian posted.  You should be able to develop a driver using low level VISA commands but it is not an easy task.  Read over the developer zone article to learn more about it.
    Eric A.
    National Instruments
    Distributed I/O Product Support Engineer

  • Requirements for Desktop PCs as LabVIEW Real-Time Targets

    Hello
    I have read the Requirements for Desktop PCs as LabVIEW Real-Time Targets
    http://www.ni.com/white-paper/8239/en/
    and i have 2 questions:
    Supported Ethernet Chipsets:   Is Intel® i210AT Controller supported?
    Supported Processors: Is E3 and E5 Xeon Supported?
    thank you

    Dear goltnum9,
    Here some Whitepapers where you can read which Requirements must be given and also how do convert.
    Requirements for Desktop PCs as LabVIEW Real-Time Targets
    How do I Create a Desktop Real-Time System?
    Kind Regards,
    SG3 | Applications Engineering | National Instruments | NIG |

  • Can anyone provide me the suitable material for labview fpga &labview real time??

    Message Edited by Sithu on 05-27-2008 04:32 AM

    The following link includes training material for both LabVIEW Real-time and LabVIEW FPGA.
    http://zone.ni.com/devzone/cda/tut/p/id/6929
    If you are new to LabVIEW you should start from the LabVIEW Basics material available at the following link.
    http://cnx.org/content/col10241/latest/
    KostasB
    NIUK Applications Engineering

  • Installing LabVIEW Run-Time Engine 8.5.1

    I want to run saved VI's from one computer with LabVIEW 8.5 Professional Development (8.5) on another computer using the Run-Time Software.
    After installing LabVIEW Run-Time Engine 8.5 (LabVIEW85RuntimeEngineFull.exe from http://joule.ni.com/nidu/cds/view/p/id/861/lang/en), do I need to do anything else before running a saved VI created in LabVIEW 8.5 from another computer? I install the program, but the only options under programs-national instruments are:
    -data socket
    -License Manager
    When I installed LabVIEW DSC Run-Time System 7.1 on the same computer there was an shortcut under "programs-national instruments-" to LabVIEW DSC Run-Time System 7.1, which is what I need but for the Run-Time Engine 8.5 instead.

    Joseph is correct. The run-time engine is only for "stand-alone" executables created with the Application Builder (included in the Professional version or higher, or can be purchased separately if you have the Base package). To run a vi in the development environment, you need one of the LabView packages.
    Message Edited by Edjsch on 05-12-2008 01:48 PM
    Message Edited by Edjsch on 05-12-2008 01:48 PM

  • Can I use third party DAQ boards with Labview real time?

    I have an Adlink DAQ 2010 card that I curently use with labview. Will this card also work with Labview real time? What requironments are there for 3rd party cards to work with Labview real time?
    Thanks!

    Hello George,
         Here is a great link for you to take a look at: Can I Use a Third-Party Device with LabVIEW RT?
    Have a great day,
    NathanT

Maybe you are looking for

  • Problem in axis with log4j

    Hi , I am facing one problem in running WS with axis in tomcat. I am new to ws . I have downloaded apache-tomcat-4.1.34(apache-tomcat-4.1.34.zip) and axis-1_4(axis-bin-1_4.zip) from the site. Set Path, Classpath , catalina_home , java_home. I have te

  • CREATE SUBREGION IN REPORT

    All, I am trying to create a subregion in a report like the one here if you click http://actionet.homelinux.net/htmldb/f?p=LSPDEMO:3:1618354013978201::NO then under Products tab check the "PLUS/+" details column to see the subregion this is a good sa

  • RE: BEFW11S4 - the laptop works, the desktop doesn't.

    I'll start off by saying I'm not the sharpest tool in the shed when it comes to these things (I can see the eye-rolling now ) but I hope I can get some help here. I have searched previous threads here but could find none that detailed the exact probl

  • Blurry Illustrator images when zoomed in within AE?

    Hi, I'm animating images I created in Illustrator CS4 using After Effects CS4, and am having a problem with Illustrator images being blurry when I zoom way in using a camera layer within After Effects. I've tried hitting the 'Continuously Rasterize'

  • REUSE_ALV_FIELD_CATELOG_MERGE issue

    Hi , This mentioned FM is creating dump . dump is "READ_REPORT_LINE_TOO_LONG" . I don't know why . please tell me if u know   CALL FUNCTION 'REUSE_ALV_FIELDCATALOG_MERGE'     EXPORTING       i_program_name     = repname       i_internal_tabname = 'IT