How to make labview real time understand sequence context

Does anyone know how to make Labview RT to understand teststand sequence context? My sequence context is defined as "TS.SequenceContext" as the screenshot in the attachment.
If we need to point a VI for this Sequence Context then which VI from teststand to use? and do we need to add this VI to the Labview Projectr Explorer in RT System to build the project?
I'm using Labview 2009 and teststand 4.2.1.
Thank you very much
Solved!
Go to Solution.
Attachments:
LVRT_TS.SequenceContext error.doc ‏132 KB

LabVIEW RT does not support ActiveX which is required for TestStand.

Similar Messages

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.

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.

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.

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

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

End of memory. Labview + Real time module + Compact Field Point 2120

My name is Michele Ciampichetti, I'm writing from Italy.
Frist of all, excuse for my english.
This is my first experience with Labview, and the application is not so easy. We use Labview 8.2.1
Our system is costituited by two different parts: there is a Compact Field Point 2120 as remote target whit some I/O card, and a PC used to releave data and memorize them (host).
The comunication between the two targets is performed by ethernet lan with Shared Variables not bufferized and not real-time fifo.
The problem is this: the sistem requires a big number of Vis and Variables (about 20 Vis per target and 50 variables localizated in 5 different librarys all in the remote target), and it should store data, acquisited by the FieldPoint, on a database (SQL Server 2005), one time per minute. This storage is made by Labview Database Connectivity Toolkit, and it work correctly. The problem is an excessive consumption of RAM on the PC.
The question is this: The use of many shared variables or vis, bring the memory to always grow? I try to explain myself. When we start our application, after the first minute and registration on the database, the memory grow of approximately 1,3 Megabytes. This is repeated every minute, and after approximately two ours, Labview break down and display "Not enought memory".
We look the on-line help for one solution, and we have found that the variables (local and shared), the concatenate funcion, the array and Vi indicators copy in memory their older value when updated. Is possible that this is the cause of our problem? There is a method to avoid it? How labview uses memory? It is possible set it up for not maintain older value in memory?
We need to run the application up to 4 days for complete its work, is a long test for a climatic room.
We're looking forward to hearing from you.
Best regards
Michele

centerbolt is correct, you can't load a .exe or even run a program on the fieldPoint controller unless you have the Real Time module. However, that does not mean you can't use your FieldPoint bank without the Real Time module.
From LabVIEW for windows you can make calls to the fieldpoint IO using the fieldpoint read/write functions.
This program runs on the PC not the FieldPoint controller. If you loose network connection to the fieldpoint, your program will loose connection to the IO. For many data logging applications this type of arrangement can work just fine. However, if this is the only type of application you are ever going to run, then you may as well not buy the Real Time controller for your fieldpoint but the network controller only.
If your application requires more reliability, and/or greater determinism than can be achieved by running a program on windows, then you should use the LabVIEW Real Time module and develop a program that can run down on the FieldPoint controller independent of windows.
Message Edited by StevenA on 07-22-2008 04:14 PM
SteveA
CLD
FPGA/RT/PDA/TP/DSC
Attachments:
fp pallet.PNG ‏6 KB

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

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

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 |

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

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 to make labview program to get average value of 200 reading from multimeter (by using loop)

Hello
How to make labview program to get average value of 200 reading from multimeter (I using using loop) to read voltage from mulmeter but I like to get average value of all of 200 reding how can I do that?
Thanks
Wee
Solved!
Go to Solution.

Another idea with less programming - take advantage of the "free" array that comes with a Chart - i.e. the History Data.
1) Wire your DMM data to a Chart. (You can set the chart to invisible if you don't plan on using it in the GUI).
2) Set the Chart History Length to 200 (right click on the chart, click on Chart History Length...)
3) On the block diagram, use the History Data Property Node, wire it to Mean.vi, and you're done.
Easiest running average ever.
Message Edited by Broken Arrow on 04-07-2010 11:36 AM
Richard
Attachments:
EasyAvg.jpg ‏8 KB

How to make a real ENTER ??

hi,
i got problems using java and word..
if I use a /n in the code, it makes a shift+enter in word
how to make a real enter ??
thanxx

First you need to open the door :)

How to make labview real time understand sequence context

Similar Messages

Maybe you are looking for