Instalacion ni real time module 2013 programa de 32 bits y computador de 64 bits

buenas noches al intentar instalar este modulo con programa labview 2013 de 32 bits y computador de 64 bits no me deja instalar no se porque razon si se supone que todos los modulos funcionan para la version del programa labview 2013 de 32 bits por favor espero respuesta o ayudaaa

Saludos david1348,
Gracias por utilizar los Foros de Discusión de National Instruments, me gustaría revisar el Software de NI que se encuentra instalado en su equipo, ¿podría compartir con nosotros un reporte técnico de NI MAX?, el siguiente link explica cómo generar dicho reporte:
Using MAX Technical Report to Document Measurement & Automation Explorer (MAX) Configuration Information:
http://digital.ni.com/public.nsf/allkb/271F252B4EF0A2E0862570E70056A1E4
Quedo al pendiente, saludos cordiales.
David P.
National Instruments
Applications Engineer
www.ni.com/soporte

Similar Messages

What are the limitations of using labview 8.5.1 developers suite verses a real-time module in field point applications?

What are the limitations of using labview 8.5.1 developers suite verses a real-time module in field point applications? Can an exe. be loaded onto a field point controller or does the controlling program have to reside on a PC for example?

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

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

Real-Time Module architecture

Hi, (I use LV RT DSC 8.2.1)
I want to learn how to use the Real-Time Module.
I have process that is running at a Real Time compact Field Point Target.
The process should be controlled and monitored by the Target but the triggering of the process should be available at the Host.
I also want to view the Process progression at the Host screen.
As far as I understand it I have several options :
Create a RT FIFO buffer and send the process data to that buffer, and then, use 'TCP Write' to send the buffer data to the Ethernet Network, where it is available to any Host PC at the Ethernet Network to view (by using TCP Read)
Create a Variable in the Project, and enable his RT FIFO at his properties.
Control the process at the Target with Shared Variables and read them at the Host.
Option 3 is the option I have been using so far, ignoring the RT property of the controllers, what are the advantages of using RT module ?
and when should I consider using them ?
What is the difference between 1 and 2 and what are their advantages ?
What important things do I need to consider when I use RT Module (just several tips if possible) ?
Sincerely Yours, Amitai Abramson.

Hi Amitai,
You could go through this link to know more about RT FIFO and its use. http://zone.ni.com/devzone/cda/tut/p/id/3934
and this for communication wizard http://zone.ni.com/devzone/cda/tut/p/id/4676
Message Edited by mallyaprs on 04-30-2009 03:53 AM
-Mallya
" Appreciate and motivate those who help"

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?

Real-Time Module Labview 64 bit

I have installed labview 2009 64 bit version to my laptop. And, i want to instal the real-time modul to this labview, but i can not do this since it needs labview 32 bit installed. Is it possible for me to install real-time module to 64 bit labview? Please help me with this problem.

The LabVIEW RT application will most likely always have to remain 32 bit for now. Most of the RT targets are to resource constrained to gain anything from moving them to a 64bit RT OS, in fact in trying to move them to 64 bit they would loose quite a bit of performance. For the Desktop and PXI RT systems, the problem is that they are based on Pharlap ETS and that is a pure 32 bit solution with no plans of ever moving to 64 bit anytime soon, AFAIK. And NI is not likely going to port that to 64 bit themselves, aside from the question if they could technically do so (not sure they have access to all of the source code) and legally (their license most likely does prevent them from changing the ETS software to run under different target systems than the one it was originally purchased for).
The only thing you can expect to come from NI in the near future is that the RT system also installs into 64 bit LabVIEW, and the actual cross compilation that happens already will simply target the 32 bit RT target. That however means that the RT application itself is still limited by the 32 bit constraints. Maybe there are some plans to add a 64 bit RT system to the mix for the high end PXI controller. What OS that would use is quite unclear. Pharlap ETS seems out of question for that, VxWorks is probably not a favorite solution at the moment and an Linux RT based system has its own legal and technical challenges.
Rolf Kalbermatter
CIT Engineering Netherlands
a division of Test & Measurement Solutions

Real Time Module, upgrading Labview 6.02 Base Development System?

Hi,
I have Labview 6.02 Base Development System but I need the Real Time module.
Would it be possible to get it upgrading the Labview 6.02? Is the full development systemm needed?
Which could be the cheapest way to get Real Time module?
Thanks.

You can upgrade to the latest version of LabVIEW Real-Time version 7.1 by upgrading both LabVIEW and LabVIEW Real-Time. You can all about the new features of LabVIEW Real-Time at the following link. For more information, please contact us at .
Regards,
Kristi H
National Instruments
>

Real Time Module needed for hi speed digitizer PCI 5911 ?

Rookie question :
I run LV 7.1 , LV Run Time 8 ( whatever this Run Time Engine may be ) , MAX 4.0.0 , NiDaq 8 ( for my two Multi Function PCI Daq's ).
Question : does the PCI 5911 work under NI-Scope 3.3 ( supporting PCI 5911 ) without a Real Time Module ?
i.e. is the Real Time Module a separate ( hardware ? ) device, not necessarily needed for PCI 5911 ?
Sorry for this utter basic question.
I have not used a hi speed digitizer before, only multifunction NiDaq's.
Thanks for any help or reference.

You are probably referring to the LabVIEW Real-Time Module described here.
This is an extension to LabVIEW that allows you to run VIs on a
real-time, deterministic environment, usually on remote hardware. One
common configuration is to use a Windows system as your host, and
communicate to a remote PXI controller running LabVIEW RT.
The PCI-5911 is fully supported for "standard" LabVIEW running on Windows. You don't need LabVIEW RT to use it.
In fact, the PCI-5911 is not supported under LabVIEW RT.
Message Edited by psisterhen on 10-16-2007 09:50 AM

Is real time module necessary?

Hi,
I want to use cRIO-9073 for simple system control. Do I need Labview Real-time module if I don't need real-time support?
Thanks in advance.
Karpis

Hi Karpis,
This is the forums for IF-RIO, which is the PCI-5640R and PXIe-5641R devices. Please post your question to the cRIO forums found here:
http://forums.ni.com/t5/Real-Time-Measurement-and/bd-p/280
You can get faster response to your question there.
Best Regards,
Jignesh P
Applications 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

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

Measurement & Automatization Reconoce mi cFP pero no lo reconoce mi Project. Si tengo Real-Time Module

El problema que tengo es que Measurement & Automatization Reconoce mi cFP-2200 pero no lo reconoce mi Project osea que al tratar de agregar un nuevo Target and Device no lo encuentra en la red y me da el error de Bank is not responding. Tengo labVIEW 2009 y la version que posee el cFP 6.0.5. tengo el modulo de Real-Time.
Gracias

Hola Estel3an!
Lo primero que podemos hacer es verificar que no sea el firewall o el antivirus la razón por la quetu cFP no esté siendo detectado. MAX y LabVIEW son diferentes procesos en el sistema operativo y por tanto puede ser que lo veas en uno pero no en otro.
La forma más sencilla de verificar esto es desactivando el firewall y el antivirus y ver si puedes detectar el cFP correctamente en MAX. Si es así, entonces para no quedar sin protección necesitas permitir el acceso a red de LabVIEW desde tu firewall y desde tu antivirus.
La forma de descativar el firewall es directamente en el panel de control y el antivirus por lo general trae un administrador donde lo puedes deshabilitar.
Por favor haz esta prueba y me avisas tu resultado.
Que tengas un excelente día!!

Possible to make a real-time audio analysis program?

Hi, I was wondering if it is possible to use flash to create a swf file that detects audio levels (or certain frequencies) so that on this event it could trigger a movie clip, or timeline event, if not, does anyone know what could be used to do this?
Thanks!

The tree vi for the above are in these .llb. Thanks
Attachments:
6430 project unedited.llb ‏1267 KB
6487 project.llb ‏221 KB
3390 project.llb ‏2356 KB

Where I can download LabVIEW 2010 real time module?

I already tried to search in NI homepage but I did not get any usable results.

If you have an active SSP contract then you should be able to download it under the support page.
Else try this: http://search.ni.com/nisearch/app/main/p/ap/tech/lang/da/pg/1/sn/ssnavdl/

"Waiting for real-time target (RT PXI target) to respond" error when the program waits interrupts

Hi there,
I have developed an application to detect interrupts generated by a electronic card and act in consequence. The program has been developed in labview but it calls a dll; that was created with labwindows. The dll is programmed to open the visa communication, enable events and install the interrupt handler and when an interrupt is detected, it reads the value of the different registers of the card and returns it to labview to visualize them.
The problem is that when the program waits for an interrupt, a prompt appears with the message "Waiting for real-time target (RT PXI target) to respond" and the only option I have is to click on the button to disconnect from the pxi or just wait. If I wait and I generate an interrupt, the prompt disappears and the application visualize the data like it was expected.
To wait for the interrupt the following code has been programmed in the function:
while (flag == 0)
Sleep (1000);
When an interrupt occurs, the value of flag changes to 1 and the function continue without any problem. I am not really sure, but probably here is the problem and probably this is not the best way to wait for an interrupt because the sleep function suspends the thread for the configured time, but at least the computing load in the PXI is between 0% and 1%. I was wondering if somebody knows how to wait for an interrupt without "lost" the communication with the PXI and if there is a better way to do it.
Any answer will be welcome and thanks for them,
Jaime
Solved!
Go to Solution.

Hello Naity,
First of all, in which thread runs the waiting process? Is it scheduled in another thread than the function setting the flag?
It scheduled in the same thread that I use to configure the communications and configure the card. Anyway, here is the pseudo code of the function interrupt that I programmed under labwindows,.
char* interrupt(void)
1. Open visa communications
2.Install handler interrupt --> status = viInstallHandler (instr, VI_EVENT_PXI_INTR, IntrHandler, VI_NULL); // the function IntrHandler will be called when an interrupt occurs
3. Enable event PXI interrupt
4. Wait
while (flag == 0)
Sleep (1000);
5. Visualize the data coming from the interrupt (registers and values measured with the card)
6. Uninstall handler interrupt
7. Close visa session
The interrupt handler function IntrHandler is called immediately when an interrupt occurs and the pseudo code is like this
ViStatus _VI_FUNCH IntrHandler(ViSession instr, ViEventType etype, ViEvent event, ViAddr userhandle)
1. Disable some functions of the card to avoid damages.
2. Read registers and put them in a buffer
3. Change the value of flag ---> flag = 1;
In labview, I call the function interrupt with a call library function node (see the capture attached) and the program reads and saves the data from returned from the function.
Secondly, I am not sure this method is the most elegant. You could for example register an event with the function and, insteand of setting a flag to 1, trigger the event and schedule it in another thread (if the function is thread safe). This could reduce your CPU Load even more and seem a bit cleaner to me.
I've never used events before in labwindows but I will try to do it in this way. But anyway, I suppose that I should; somehow, wait the event to occurs in labview while the waiting for the event is programmed inside the dll...and probably the same prompt that i am trying to avoid is going to appear again, because I am not returning the "control" to labview (I mean, labview executes the dll and waits for the event to occur. Then the execution of the labview program is stopped in the call library function node executing the dll)
Third point, which environment of development are you using?
I am working with LV 2010 sp1 and Labwindows cv 10.0.1 and with the real time module.
I did also another test, I divided the program in different functions, one to initialize the communication, another to wait until a interrupt has been detected and the other to obtain the data from the interrupt and close communications. With labview I call first with the call library function node the function to initialize, later I call inside a while loop the wait function like this
int waitAseconds (double seconds, short stop_waiting)
if(flag==1 || stop_waiting == 1)
flag = 1; //to detect the stop_waiting button
printf("flagAA =1 stop waiting = %d time = %d\n", stop_waiting, clock());
return flag;
else
SleepUS(seconds*1000000);
//a++;
printf("flag a= %d stop waiting = %d time = %d\n", flag, stop_waiting, clock());
return flag;
and when the program detects an interrupt, the function returns to labview the flag and stops the loop. Finally, it reads the values and close communications.
In this way, the prompt appears but after running the application for 10 or 20 minutes and also i checked that there is a time gap between the executions in the loop.
Thanks for your reply and your help,
Jaime
Attachments:
capture.png ‏40 KB

Instalacion ni real time module 2013 programa de 32 bits y computador de 64 bits

Similar Messages

Maybe you are looking for