Labview Real-Time and CompactRIO questions

Hi
everyone! We have new troubles about CompactRio and Real Time module:
-We want to
translate into real-time module a VI we have done with Labview 8 .2. In order
to do that we have discovered an option placed in Project Explorer (Tools->Real-Time
module->Communication Wizard) that seems to translate automatically into Real-Time
language. Is it true?
- If it was
true we would want to do a transmitter VI in CompactRio (RT target) and a receiver VI in the Host. But the
Communication Wizard creates a VI in the Host and a VI in the RT target (in
Real Time language) for each VI we enter to translate ( so we obtain 4 VI’s in
the same project , two of them as transmitter, and two of them as receiver)
-We have
tried to deploy some VI’s to the CompactRio and we get always an error.
CompactRio’s configuration is allright and it is well recognized by MAX. Why
does the error appear, and how can we work it out?
We
need to configure the Serial Port placed in CompactRio in order to adjust some
features, such us bauds value. MAX recognized the CompactRio’s Serial Port, but
all the opctions to configure them are disabled.
I hope you
can answer these questions. Thank you.
Ander

Hi again,
Still didn't find the problem on my side. Here's a picture of my code. If I put the code surrended in red at place (1), I don't get the error, but if I put the code at place (2), I get the error. Why oh why....?
I get the error when I close the browser or click Back button of the browser or Stop the application with the red dot or stop the application with the Quit button on my front panel.
This morning I found a post on this forum about getting an error using Property node and Remote panel (http://forums.ni.com/ni/board/message?board.id=170&message.id=252705). I did what they suggest: wire the property output to an indicator and it works (disable "Enable automatic error handling dialod" didn't work... I don't know why)... until I put extra code in my VI.
I really need help please!
Thank you
Stephanie
Attachments:
MemoryManager line 437 error.JPG ‏228 KB

Similar Messages

LabVIEW Real-Time and Remote Front Panel MemoryManager.cpp line 437 error

Hi all,
I'm using a smartcamera (NI 1742) with LabVIEW Real-Time 8.6.
When I look at the Front Panel with the web browser and I close the browser or I Stop the executable, I always get this error: MemoryManager.cpp line 437. I've checked if someone else had this error, but I guess I'm the only person who got this error. I saw someone who had the MemoryManager.cpp line 406, but mine isn't on this line.
The application works well, but when I got the error, I need to reboot the smartcam to get it works. In my application, I use the Modbus library and I read/write binary file in the hard disk of the smartcam....
Anyone knows the solution?
Thank you very much
Stephanie

Hi again,
Still didn't find the problem on my side. Here's a picture of my code. If I put the code surrended in red at place (1), I don't get the error, but if I put the code at place (2), I get the error. Why oh why....?
I get the error when I close the browser or click Back button of the browser or Stop the application with the red dot or stop the application with the Quit button on my front panel.
This morning I found a post on this forum about getting an error using Property node and Remote panel (http://forums.ni.com/ni/board/message?board.id=170&message.id=252705). I did what they suggest: wire the property output to an indicator and it works (disable "Enable automatic error handling dialod" didn't work... I don't know why)... until I put extra code in my VI.
I really need help please!
Thank you
Stephanie
Attachments:
MemoryManager line 437 error.JPG ‏228 KB

Labview real-time and simpowersystems toolbx from matlab

Hello,
I have a simulink model built with SimPowerSystems toolbox. I want to run this model on a RT target which is a desktop ETS in this case. I follwoed the instructions on how to create and deploy the DLL. There are two problems I am facing--
1. The host screen grays out even though the mapping is correct. (This is verfied by using a similar working file.)
2. The RT target hangs and then the connection is lost. I don't get any error message and after some time as there is no communication, I get error 66/63 etc network related error.
The questions are:
1. Is SimPowerSystem toolbox supported in SIT? ( I read that the SimMechanics is not supported.)
2. Is there any limitation on how many nodes I can use so that the RT system can run the model without getting hung up.
The versions I'm using are:
LabView 8.2, SIT 3.0.2
Matlab R2006b, SIMULINK 6.5, Real-time workshop 6.5
microsoft visual C/C++ 6.0
Please let me know ASAP if anyone has faced this problem before or if someone can answer my questions.
Thanks,
Gayatri

Signals also can be removed when the code is generated and compiled due to optimizations. Right clicking on a signal and making it a testpoint forces RTW to include that signal in the compiled code signal list. The appropriate discussion is posted below.
Models Using Signal Storage Reuse, Block Reduction Optimization, or Virtual Blocks
Mappings might appear invalid if the model uses either Signal Storage Reuse or Block Reduction Optimization. These items are options you can set in the Simulink application software to reduce the memory footprint of the model. Disabling these options for the entire model makes all signals available for probing but increases the memory footprint of the model. You can mark individual signals as test points to maintain a reduced memory footprint while keeping certain signals available for probing. To make this change, load the model in the Simulink application software and perform the following actions:
For The MathWorks, Inc. MATLAB® application software release 13, right-click a signal and select Signal properties from the shortcut menu. Place a checkmark in the SimulinkGlobal(Test Point) checkbox and click the OK button to save changes.
For the MATLAB® application software release 14 and later, right-click a signal and select Signal properties from the shortcut menu. Click the Logging and accessibility tab, place a checkmark in the Test point checkbox, and click the OK button to save changes.
Note If you previously converted this model to a model DLL, you must convert the model to a model DLL again after marking signals as test points.
Similarly, you might not be able to probe signals from Virtual Blocks such as Mux, Demux, Bus Selector, and so on. Marking signals from these blocks as test points makes the signals available for probing.
Refer to the Simulink documentation for information about Signal Storage Reuse, Block Reduction Optimization, Virtual Blocks, and test points.
Models Using Inline Parameters
You might not be able to manipulate model parameters if that model uses the Inline parameters option in the Simulink application software. This option writes a constant value to each model parameter. You must launch the Simulink application software and disable this option so the Simulation Interface Toolkit can manipulate the model parameters.
Refer to the Simulink documentation for information about inline parameters.
Models Containing Linked or Masked Subsystems
You can create mappings to parameters and signals of masked subsystems. However, if a subsystem is linked, or linked and masked, any mappings to parameters and signals of that subsystem appear invalid. Refer to the Simulink documentation for information about linked and masked subsystems.
Subsystems without Parameters or Signals
If a model contains a subsystem that does not have any parameters or signals, that subsystem appears in the model tree when you create mappings. However, you cannot create mappings to/from that subsystem.
<SCRIPT type=text/javascript>
if (typeof(Print_Link)=="function") {
Print_Link();
</SCRIPT>

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

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

Could I use two regular computer to achieve realtime communication using the Ethercat and Labview Real Time Module?

Could I use two regular computers (one acts master , another one acts as slave using the Ethercat Internet Card) to achieve realtime communication using the Ethercat and Labview Real Time Module? if it could, what hardware should I purchase from the NI ?
Thank you!

Hi Xiaolin,
NI doesn't offer Windows based Ethercat master or slave software. Only LabVIEW RT can run the Ethercat driver.
However, you could use a LabVIEW RT target as an Ethercat master and use the Ethercat Internet Card with a slave PC (note: I think this will work from the Beckhoff description of the card you are describing. The card should integrate like any other non-NI slave. However I haven't tested the setup and don't advise saying it will work until you have tried).
You can use any NI RT target with two ethernet ports as the Ethercat master. This could be a cRIO, PXI or RT Desktop.
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

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 |

Qual a diferença do LabVIEW FPGA e o LabVIEW REAL- TIME?

Hello,
Could anyone help me? This question arose in my work and could not answer. Does anyone know tell me?
Thank you.
Solved!
Go to Solution.

Olá,
Com o LabVIEW FPGA você programa diretamente o chip FPGA presente no chassis cRIO, placas da NI Série R e single Board RIO. Você programa as E/S diretamente no chip, sendo assim uma programação de mais baixo nível. A grande vantagem do FPGA é o "paralelismo real", o que garante altas velocidades na execução das rotinas programadas.
Assista ao webcast Introduction to LabVIEW FPGA
Com o LabVIEW Real-Time você desenvolve aplicações que são críticas em relação a "tempo". Chamamos de aplicações "deterministicas". A idéia é que, se você tem uma rotina que deve ser executada em um tempo determinado, a diferença entre o tempo real e o que você programou seja o menor possível. Aplicações em Computadores comuns não são deterministicas, pois enquanto o LabVIEW executa uma certa rotina programada, o Windows está executando outras tarefas, monitorando a utilização de periféricos, atualizando a tela, etc.
Real time não significa "Velocidade", mas "Confiabilidade".
Assista ao webcast LabVIEW Real-Time: Graphical Development, Hard Real-Time Performance
Hello,
With LabVIEW FPGA you program the FPGA chip itself. The FPGA chip is found into cRIO chassis, NI R-Series Boards, and NI Single board RIO. You program the I/O directly in the chip, so we consider this as a low level programing. The main FPGA advantage is the "Real Paralelism", which guarantees high speed execution programming.
Whatch Introduction to LabVIEW FPGA webcast
With LabVIEW Real-Time you develop called "time crictical" or "Deterministics" applications. In case of you routine must be executed in a specified period of time, the difference between the real time execution and the time you programmed is as low as possible. Commom computers programming are not deterministic, because in the meantime of executing a certain programmed routine, the OS (e.g. Windows) is running other appication tasks, monitoring peripherals like mouse and keyboard, uptading screen, etc.
Real-Time doesn't mean "faster" but "reliable".
Watch LabVIEW Real-Time: Graphical Development, Hard Real-Time Performance webcast
I hope the information helps you!
Best Regards
Felipe Flores
Engenharia de Aplicações
National Instruments Brasil

Real-time and Developement System

I have a very premitive question. what is real-time OS? what are differences between real-time and Developement labview.

Real-Time in general is not about speed, it's about guaranteeing, that a specific function will be executed within a specified time window.
Imagine a car with some sort of fieldbus. You want the brakes to be working at any time within a time limit (say, 1ms). That's Real-Time.
Windows for example uses some sort of scheduler to distribute CPU time to the different threads with a granularity of - i think 1 ms. So each thread gets 1 ms, then it is interrupted and the next thread gets its 1 ms. Of course there are priorities which thread gets a little more time (or more "slots") and which thread gets less. BUT: You cannot tell in Windows, that your application will execute in a specified time window - at any time, it can be interrupted and therefore delayed and theres nothing you can do about it.
Real Time OS make sure, that - if some specified event happens - it will be executed within a specified time window.

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

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

Read data in real time and save as an excel file

Hi,
I want to write a LabVIEW progarmme which able to read data in real time and save it as an excel file from Varian Vacuum muli-gauge.
It is using RS232 port.
Can anyone give me some examples or point me in the right direction?
I am a beginner of LabVIEW. Hope anyone can help me.
Thank you very much!!
Joanne

Thanks for your reply.
I just use MAX to verify that the rs232 port is operational.
However, there is an error (please refer to the attachment).
One possible reason is in MAX I am trying to do the default command *idn? ...but it doesn't work.
I read the vacuum multi-gauge manual but I don't know which command should I use...
I attached the manual and can you tell me which command should I use?
Or can you tell me other possible reason for this error code?
Thank you very much.
Joan
Attachments:
Varian Multi-Gauge Controller.pdf ‏2747 KB
error1.JPG ‏111 KB

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

Labview Real-Time and CompactRIO questions

Similar Messages

Maybe you are looking for