NI LabVIEW Real-Time for Desktop PCs compatibility!

Hello,
I'm pretending to acquire the NI LabVIEW Real-Time Deployment License for Desktop PCs. But before that, I need to be sure that this will work with other boards (not from NI).  
Currently, I still don´t have all the project details. But there's a possibility of one board be from other supplier. 
Can anyone tell me this, please. It's very urgent.
Best regards,
Paulo Carmo

Hi Paulo,
I guess that you will be disappointed but the response is clearly no.
When you boot a Desktop PC as RT target, it loads with the basic real-time operating system (including drivers for ethernet, for harddrive, memory....). When you want to add drivers on this embedded system, it will be only possible to add National Instruments drivers such as DAQmx, DAQ, VISA ... The possibility to add others drivers (from others providers) is not supported.
Hope it will help you,
Regards
David D. - Application Engineer - NI France

Similar Messages

  • 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 |

  • 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?

  • 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

  • What OS is best for LabView Real Time?

    Our computer will be dedicated to running a LabView program that will collect and display sensor information on the virtual instrument panel. What OS will provide the most reliable and compatable environment for LabView Real Time?

    hi, i wanna ask about win xp, in some posts people says is not suitable use rt on windows because of the difficulty of give priority to certain task over the other ones, i wanna know if i can work just with windows xp or must i use an real time OS.
    thanks for help
    Pedro Rivera
    .:. Pedro Rivera .:.
    i love to work and develop on labview, this is real fun!!!

  • Read CPU temperature of Desktop PC running LabVIEW Real-Time

    Is it possilbe to read the CPU temperature of a Desktop PC running LabVIEW Real-Time? I found an older example that allows to read the temperature of PXI systems (http://www.ni.com/example/29538/en/). Is there a possibility for Desktop Real-Time Machines as well?
    Regards,
    Steffen

    Hi this is heavily dependent from your specific Hardware. Which PC or more specific which main board do you use?
    I found several examples in the NI forum that try to access the CPU data.  
    I’m using a Dell machine and both temperature VI’s are not working for me.
    Hope you have more luck.
    Attachments:
    Temperatur_der_CPU.vi ‏13 KB
    WMI_GetTemperatureProbe[1].vi ‏26 KB
    WMI_Win32procesor[1].vi ‏41 KB

  • 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

  • NI-DAQmx 7.4 Changes for LabVIEW Real-Time

    Hello LabVIEW Real-Time and DAQmx users,
    National Instruments has recently released NI-DAQmx 7.4. Changes introduced in NI-DAQmx 7.4 provide increased flexibility when performing hardware-timed single-point operations on real-time platforms. The Developer Zone Tutorial: DAQmx Hardware-Timed Single Point Lateness Checking has been created to help explain these changes. Information is also available in the NI-DAQmx Help.
    In order to provide these changes in NI-DAQmx 7.4, the behavior of 'DAQmx Is Read or Write Late.vi', used in previous versions, had to be changed. In NI-DAQmx 7.4, the 'DAQmx Is Read or Write Late.vi' has been obsoleted and no longer performs any lateness checking. Applications being upgraded to NI-DAQmx 7.4 are recommended to use one of the lateness checking options discussed in the above tutorial.
    Regards,
    JR Andrews
    NI

    Hello,
    I changed the program and added a case structure to configure each channel according their type. In order to go through all the channels in the configuration file, I put a for structure. 
    It seems it is working, however, when I start acquisition, I only see one channel and that is last one which is configure. 
    Here is the original file, configures all, but only works for AI Voltage:
    Here is the modified one:
    What I am doing wrong? 
    Thanks!
    Attachments:
    ConfigureFor Channels.PNG ‏131 KB

  • 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

  • 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

  • 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.  

  • 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.

  • 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.

Maybe you are looking for