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.

Similar Messages

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 much interfaces can be driven in "real-time" with a VI in LABVIEW 6i

In my application I need to merged data from different devices hanging to my computer via different interface types. Each data set in to be specifically formatted in a file. Each data set comes a a rate of ~ 10 Hz.
As acquisition devices I do have
- 4 digitizers connected to the PCI bus and their labview driver are already given by the constructor
- an instrument from which data to be imported via a GPIB interface
- an instrument from which data are imported via a serial port
- and probably in the future, 2 devices mounted on two USB port
I wish to developp a LABVIEW 6i code which permit me to make the request to all instrument, to import the data and to merged them as quick as possible so
that I can store data set coming every 0,1 s. All data from all instruments must be recorded for the same event at the same time (in a triggered manner) before it performs the acquistions for the next event
I would like to know what is the best way to each my goal.
- Is it possible to control all this with one VI (containing lot of VIs) ?
- Should I execute a VI for each interface and run them at the same time and save all data set with a time stamps in a file and then, off-line, process all the files and merge my information.
In a general manner, are there any rules which indicate the maximum number of interface (according to their nature) which can be properly controled on a given platform from one computer.
Thanks you very much for any answers

Its been a couple of days with no reply....
Look at the occurence functions.
You can have one loop send occurences at teh rate you need.
Put each of the other functions in seperate loops that wait for the occurence on each interation.
Provided each of your loops runs fast enough this approach should serve you up till you run into the indeterminism of Windows. If the the indeterminism will be an issue, you may have to go with LV Real-Time.
Ben
Ben Rayner
I am currently active on.. MainStream Preppers
Rayner's Ridge is under construction

Can I use LabView Run-Time Engine on Windows XP?

An Application uses LV Run-Time Engine 5.1, i want to use this application on windows XP, can i use the same version of the RTE, if not, what is the solution??

To eleminate the possibility of errors, you need to convert the application to a version fully compatible with windows XP, like 6.1 or 7.0 (6.02 should do it)
Would version 5.1 work with XP, NI do not gaurantee that. However, I had installed apllications written in version 5.1.1 and worked fine under XP. In your case, just give a try, if it did not work as expected, you may have functuionality that may not be fully comptaible with XP.

Using JRockit Real Time with Large Heap

I want to know if JRockit Real Time can work with extremely large heap, e.g. 100G, to provide effective deterministic GC, before proceeding with evaluation for my application.
Thanks in advance!
Wing

Hi Wing,
In general, extremely large heaps can make all GCs slower. This is true for Deterministic GC as well. However, it is very application dependent. It is above our standard recommendation, but you can download JRockit Real Time and give it a try.

How can i use labview for communicating with pic18 microcontroller through usb port?

Hi all,
I want to make a DAQ card using pic 18 microcontroller which has a built-in usb protocol. I have the firmware of this
controller which will make it as a usb device. How can i receive the analog voltages from this DAQ card in Labview? or i mean to say that how i can communicate labview with the Pic 18 microcontroller through usb port? I have also the
mpusbapi.dll file which is for Visual C++. Can i make changes in this dll file to make it compatible with labview?

Which labview version do you have. Up to labview 7.1 it was no USB raw communication options. I have heard it did not work well in 7.1, but from 8.x most of the errors were fixed.
Here is a link it should be useful http://forums.ni.com/ni/board/message?board.id=170&message.id=340676&query.id=365864#M340676
Besides which, my opinion is that Express VIs Carthage must be destroyed deleted
(Sorry no Labview "brag list" so far)

Can I use Labview for linux with a student license?

I recently aquired a copy of Labview, student edition. The package only includes the Mac and Windows versions. Would it be possible for me to obtain/use the linux version under this license? How?

Hi, thanks for using the National Instruments' Forums,
I would recommend you to contact your technical representative in order to give you detailed information about the Linux version. From what country are you? I can help you contacting you and your technical representative.
Thanks again for using the Forum
NorSa
AE LATAM
NorSa
NI Applications Engineer Latin America
Para Soporte entra aquí

Why is it that I can no longer play Real Time with Bill Mayer on my IPad or IPod.

My IPad and IPod Touch software are up to date. This is the first time I have not been able to download; I've been listening to podcasts for several months.
Thanks, Juanita

The latest three episodes, released 20 June, do not play: there is no file on the server. This is his problem, not yours.

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?

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.

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

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/E7E2F5657B6026358625750B007201A6?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 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

The Problem about Monitoring Motion using PCI-7358 on LabVIEW Real Time Module

Hello everyone,
I have a problem about monitoring the position of an axis. First let me give some details about the motion controller system I’m using.
I’m using PCI-7358 as controller and MID-7654 as servo driver, and I’m controlling a Maxon DC Brushed motor. I want to check the dynamic performance of the actuator system in a real time environment so I created a LabVIEW function and implemented it on LabVIEW Real Time module.
My function loads a target position (Load Target Position.vi) and starts the motion. (Start.vi) then in a timed loop I read the instantaneous position using Read Position.vi. When I graphed the data taken from the Read Position.vi, I saw that same values are taken for 5 sequential loops. I checked the total time required by Read Position.vi to complete its task and it’s 0.1ms. I arranged the loop that acquires the data as to complete its one run in 1ms. But the data shows that 5 sequential loops read the same data?

Read Position.flx can execute much faster than 5 ms but as it reads a register that is updated every 5 ms on the board, it reads the same value multiple times.
To get around this problem there are two methods:
Buffered High-Speed-Capturing (HSC)
With buffered HSC the board stores a position value in it's onboard buffer each time a trigger occurrs on the axis' trigger input. HSC allows a trigger rate of about 2 kHz. That means, you can store a position value every 500 µs. Please refer to the HSC examples. You may have to look into the buffered breakpoint examples to learn how to use a buffer, as there doesn't seem to be a buffered HSC example available. Please note that you need an external trigger-signal (e. g. from a counter of a DAQ board). Please note that the amount of position data that you can acquire in a single shot is limited to about 16.000 values.
Buffered position measurement with additional plugin-board
If you don't have a device that allows you to generate a repetitive trigger signal as required in method 1.), you will have to use an additional board, e. g. a PCI-6601. This board provides four counter/timers. You could either use this board to generate the trigger signal or you could use it to do the position capturing itself. A PCI-6601 (or an M-Series board) provides can run a buffered position acquisition with a rate of several hundred kHz and with virtually no limitation to the amount of data to be stored. You could even route the encoder signals from your 7350 to the PCI-6601 by using an internal RTSI cable (no external wiring required).
I hope this helps,
Jochen Klier
National Instruments

Can I acquire and analyse in real time with regular Labview?

I have to acquire samples (which vary cyclically in a roughly sinusoidal fashion) from a sensor, and check every sample to see if it is the minimum (the valley) of a cycle. If it is, and it does not fall within an expected range, I have to take a corrective action that involves rejecting the part that was just measured as well as a 30 more parts (to make sure that the defective part has been rejected). The signal from the sensor is not very noisy, but beause of the nature of the measured object, there could be local minima and maxima. To guard against that, a point is considered to be a valley only if subsequent readings deviate above that point by a certain amount. If a part is indeed defective,
a digital out put has to issued to reject that part.
Can all these be done using regular Labview (not RT)? I tried it out with a proto-type VI, using DAQmx vis, continously acquiring samples, but reading one sample at a time from within a loop (the VI I used is attached with this question). The result has been disappointing, since each time the loop executes there is a delay that keeps building up. Finally, even after the part feed has been turned off I can see Labview processing signals from parts that have long since gone past the measuring head.
Another perplexing thing I found is that the time taken to execute the while loop in the vi is not consistent; it takes anything from 6 to 50ms to execute.
I will need atleast 8-12 samples from a part to build its profile, and the feed rate is about 3000 parts per minute. I am using Labview 7.0 with an NI-6013 card in a Windows 2000 environment.
Thanks for any suggestions / recommendations.
Attachments:
find_trough_2.vi ‏378 KB

Hello,
Thank you for your suggestions; I had already resigned myself to going for a Real Time system, your answer convinced me to commit myself to it!
That said, your reply leads to a couple of (related) questions...
1. Your point regarding the use of Local Variables is well taken; I have been repeatedly told at various training sessions how the necessity of updating the LVs during each loop iteration slows the computation time. However, what alternative do we have when there are several controls to which we have to write AND read data multiple times during a loop iteration, and perform different computations based on the value held by these controls? (You have seen the VI I attached with the original question). Some of these conditional
computations further change the value of the controls. Does Labview have any other mechanism to store and manipulate the intermediate value from a computation?
2. I did a simple experiment to determine the average loop time, and the results were surprising. I placed the entire content of the VI I used (Find the Valley in cycle.vi) in a stacked sequence structure, and wired the index counter "i" to a control to count the number of iterations the loop executes. I placed a frame before this with a tick count instruction to get the start time of the loop, and a frame after this to get the end time of the loop. Dividng the difference of these with the number of iterations, I got the average loop time to be around 1.2ms! Am I interpreting my results incorrectly?
Thnaks once again for your response. I would really appreciate your views on the questions I have raised in this comment
Regards
Arun P. Madangarli

Can I use Labview real time with PCI 6013?

Similar Messages

Maybe you are looking for