CompactRio 9074 y ni 9234

Hola, estoy instalando compactRio 9074, pero al momento que estoy solicitando el ni 9234 no me aparece como device de opcion en la pantalla de MAX,
no se si se tiene que instalar con anterioridad o solo se inserta en el compactRio, al igual intente mandarlo llamar desde labview pero me marca NO DEVICE
Solved!
Go to Solution.

Hola
Las tarjetas de la serie C conectadas al cRIO, como la 9234, no aparecerán debajo de Devices and Interfaces de MAX. Siempre y cuando puedas ver el cRIO en MAX con la leyenda "Connected and Running" no tendrás ningun problema
PAra poder tener acceso a ellas debe de ser mediante el Distributed System Manager o desde LabVIEW.
Desde LV deberás crear un nuevo proyecto, y después agregar el target . (click derecho al proyecto>>New>>Target &Device. mDesde ahí podrás seleccionar el 9074, tranajar con el ScanInterface y esto de manera automática descubrirá los módulos que estén conectados al chassis.. aquí un ejemplo
Para hacerlo desde DSM (distributed system manager) sigue este tutorial.
Espero esta info te sea útil
Saludos

Similar Messages

Plusieurs trames CAN fifo compactRio

Bonjour à tous,
J'utilise un compactRio 9074 avec labview 2010 et un module 9853.
Je dois faire l'acquisition de données sur un bus CAN. Mon problème est le suivant: Lorsque je spécifie une seule trame depuis la DBC, j'obtiens les valeurs souhaitées. Mais quand je veux lire des données de plusieurs trames cela ne foncitonne plus.
Je ne sais pas comment lire plusieurs trames au niveau du FPGA. (Dans ma fifo se trouvent uniquement les données d'une trame)
Voir les captures d'écran jointes.
Merci d'avance.
Pièces jointes :
CAN FPGA.jpg ‏91 KB
CAN RT.jpg ‏129 KB

I am not aware that using the Scan Engine is blocking any access to a transfer FIFO. But please reread this from your quoted KB:
Secondly, the number of DMA FIFO's that can be used in the FPGA code will be reduced, since the scan engine uses two DMA FIFO's. Most FPGAs have 3 DMA FIFO's, so there will only be one DMA channel left to use in the FPGA code.
This means, you have only a single DMA FIFO left which is either Target to Host or Host to Target.
Make sure that you configured the FIFO to be the correct direction for your needs...
hope this helps,
Norbert
CEO: What exactly is stopping us from doing this?
Expert: Geometry
Marketing Manager: Just ignore it.

Compactrio RS232 question

I have Compactrio 9074. How do I setup the rs232 port setting. I try to run"LabVIEW 2009\vi.lib\Instr\_visa.llb\VISA Configure Serial Port (Instr).vi" to setup the port I get a error. I would like to communicate over RS23 with the compactRIO.
Port name = RIO0::INSTR
error code = -1073807331
Error desciption
Error -1073807331 occurred at Property Node (arg 2) in VISA Configure Serial Port (Instr).vi
Possible reason(s):
VISA: (Hex 0xBFFF001D) The specified attribute is not defined or supported by the referenced resource.
Sam

I have written LabVIEW for serial communication. I have the Serial
software that communicates between the instrument and computer. I want to
run the RS232 communication software on the CompactRIO. I got everything
working on the CompactRIO but the RS232 port. The RS232 software is fine
because I can run it on a computer talking to the instrument.
LabVIEW has a RS232 configure serial Port. If I call out the wrong
port, I should and get an error. If I call out the correct port, I should
not get an error even if the instrument is not connected. All I'm doing
is trying to initialize the port configuration.
On the compactRIO, I have NI-RIO 3.2.0(minimal) installed. I'm trying
to initialize the baud rate before I talk to the instrument. Attached is
the init vi I'm using.
Thanks for the response
Sam
Attachments:
InitSerial.vi ‏11 KB

RT: 9512 modules fault when using hybrid mode

Hello, I am having an issue with my cRIO hyrbid setup. I am currently using Labview 2010, cRIO 9074, x1 NI 9234, and x3 NI 9512.
Summary:
What you are trying to accomplish?
-I have built two VIs. One that acquired data from an NI 9234. This vi is the one that uses the FPGA due to 51.2kHz sampling frequency needs. The other is to control the motion and encoder reading of three NI 9512s (scan mode). They both work fine separately (on the same FPGA bitfile), but when I copy and paste the VI for the NI 9234 into the VI for the x3 9512s and click run, the motors fault out.
What steps are necessary to reproduce any problems?
click run on the attached (prepared program_2VItesting.vi).
What steps, if any, you have taken to solve any problems and the results of your attempts
-I have confirmed that if i run the two VIs separately, they work fine. The very first time i combine the two VIs the 9512s work for a second (i.e. the motors move a little). Then it faults. I then used distribution manager to clear the fault and run it again (note: there is no fault code, i just clear the red light on the module by changing to configuration mode then active mode). Every time after the first time the motors do not move at all.
- I have confirmed that i did correctly setup the hybrid mode based on this kB:
http://digital.ni.com/public.nsf/allkb/0DB7FEF37C26AF85862575C400531690
I have attached the vi of the two VIs combined together(prepare program_2VITesting.vi). The top half is the copied and pasted FPGA program (as noted by the open VI reference) and the bottom is the scan mode (as noted by the timed loop). I also attached the seperate VIs (JustDAQ and prepared program) that can both function right now by justing pressing run.
Am i just missing something simple here?
Thanks,
Troy
Solved!
Go to Solution.
Attachments:
prepared program_2VITESTING.vi ‏1369 KB
prepared program_ThisWORKS.vi ‏445 KB
JustDAQ.vi ‏930 KB

Hello Troy_B,
Thanks for the post, here is a useful KB describing how to use Scan Engine and FPGA simultaneously. Please take a look at this documentation and make sure you have everything configured correctly for Hybrid Mode.
http://digital.ni.com/public.nsf/allkb/0DB7FEF37C26AF85862575C400531690
Note:
Hybrid Mode has longer compile time because the compiler has to combine the RIO Scan Interface bitfile and the FPGA code into one bitfile.
The number of DMA FIFO's available for FPGA code is reduced since the scan engine uses 2 DMA FIFO's.
Here is an example of what your final project should look like with Mod1 in Scan Mode and Mod2 in FPGA Mode:
Hope this helps!
Paul-B
Applications Engineer
National Instruments

Reactivar compact rio en max por red

Saludos a todos!!
espero me puedan ayudar..
realicé un reinició del MAX en mi pc ya que marcaba algunos errores, por lo cual se borraron todos los registros y todas las tarjetas y módulos que estaba utilizando. ahora quiero volver a integrar el modulo compactRIO-9074 que ya tenia por medio de la IP. pero al momento de intentar agregarla, primero con el hostname dice "Unable to initialize connection to remote target(s)" y por medio de la IP me dice lo siguiente "The device at this adress is not supported by the drives installed on this host". solo puedo aclarar que mi pc requiere permisos de administrador para todas las instalaciones, ademas no he desinstalado drivers ni nada por el estilo. solo realice el reinicio del MAX debido a los problemas que presentaba. el compact rio sigue con su misma IP ya que puedo monitorearla por internet. espero me puedan ayudar con esto. gracias.
Rene Eduardo Guerrero Recio
Ing. Electrónico
COMIMSA, Saltillo.

Buenos días Reno32
Le puedo platicar lo siguiente en relación a los dos mensajes que le arroja MAX al momento de conectarse por medio de "Remote Device (not on the local subnet)"
"Unable to initialize connection to remote target(s)"
Este problema se debe a que la computadora no se pudo conectar con el dispositivo, ya sea que por que la IP ingresada sea incorrecta o bien que el firewall de la computadora pudiera estar interfiriendo con la comunicación.
"The device at this adress is not supported by the drives installed on this host"
Este problema pudiera estar ligado con los drivers. Cuando trabajamos con un dispositivo en tiempo real, tanto el modulo de Real Time instalado en la computadora, y el software instalado en el controlador, deben de ser de la misma versión.
Como troubleshooting me gustaría preguntarle
- Que módulo de Real Time es con el que esta trabajando ?
- Que versión de LabVIEW es la que esta utilizando ?
- Que versión de NI RIO tiene instalada ? (esta la puede revisar en la pestaña de software dentro de MAX)
- Cuando menciona "el compact rio sigue con su misma IP ya que puedo monitorearla por internet", Qué herramienta esta utilizando para monitorearlo? o bien le aparece debajo de Remote Systems ?
Como recomendación le puedo sugrerir:
- Asegurarnos que el firewall del computador se encuentre desactivado.
- Conectar directamente el cRIO a la computadora de desarrollo por medio de un cable Ethernet (en caso de que no este conectado directamente).
- Colocar la computadora de desarrollo en la misma red que el controlador, e intentar reconocerlo en MAX.
- Si es posible agregar el controlador en MAX, actualizar el software del cRIO para asegurarnos que la versión de drivers instalada en el cRIO coincida con la versión del Módulo de Real Time instalada en la computadora.
Como referencia puede seguir los pasos de la página 6 'Installing Software on and Configuring the Controller' del manual de Getting Started
http://www.ni.com/pdf/manuals/372596b.pdf
o bien tomar como referencia el siguiente video
https://www.youtube.com/watch?v=ksaeXq84PAg
Espero que esta información le resulte últil. Estamos a sus órdenes.
Omar R.
Applications Engineer

CRIO: error while compiling real-time application

My code can be run when the cRIO is connected to PC with Ethernet cable.
But when I want to compile (build) my code, I get the following massage.
Also the picture of the massage is shown below.
Visit the Request Support page at ni.com/ask to learn more about resolving this problem. Use the following information as a reference:
Error 6 occurred at Copy in AB_Targetfile.lvclassostBuild.vi->AB_Application.lvclassostBuild.vi->AB_Engine_Build.vi->AB_Build_Invoke.vi->AB_Build_Invoke.vi.ProxyCaller
Possible reason(s):
LabVIEW: Generic file I/O error.
E:\2013_05_23a_research\2013_05_27a_Richard's\exercise\2013_07_07_exampleFinder_1DMAFIFO\examples\CompactRIO\Module Specific\NI 9234\builds\NI 9234 Getting Started\NI-cRIO9024-UConn\My Real-Time Application\c
Solved!
Go to Solution.

Hi Cashany,
What version of LabVIEW Real-Time are you working with? What cRIO are you deploying to? What version of the NI-RIO Drivers are you using?
Behind your error dialog you have a Load Save Warnings dialog. What is the full expected path that LabVIEW is expecting to find this VI at? Have you tried correcting this conflict by moving the file to the expected path or changing your project to expect it from the new path?
Also I notice that the paths that are listed are rather long. Is it possible that your problem is related to this KnowledgeBase, Error 6 Occurs at Create Folder When I Build my Real-Time Executable?
Miles G.
National Instruments
Applications Engineer

Frequency of signal from anemometer

hello,
I 've to the output of an anemometer, an AC voltage whose frequency is related to the wind speed. unfortunately I did not get my signal frequency. I'm using the CompactRIO 9074 with NI9221 module. I see my good signal but I can not seem to extract its frequency. Have you any idea of VI? This is urgent.
Thank you.

Hi,
I put a screen capture of the code as an attachment. I read my signal from the anemometer on the AI2 port NI 9221. For my range-measuring sensor, I have to measure frequencies from 0 Hz to 125 Hz. Documentation of the anemometer is attached too.
Thanks
Attachments:
code.jpg ‏65 KB
NRG40C.pdf ‏121 KB

Mesure de la fréquence d'un signal issu d'un anémometre avec crio9074

Bonjour,
j'ai à la sortie d'un anémomètre, une tension AC dont la fréquence est relié à la vitesse du vent. malheureusement je narrive pas à obtenir la fréquence de mon signal.J'utilise le compactRIO 9074 avec le module NI9205. j'observe bien mon signal mais je n'arrive pas à extraire sa fréquence.Avez vous une idée de VI? C'est urgent.
Merci.

Bonjour Levla,
Pour récupérer la fréquence de votre signal, peut etre pourriez vous utiliser une FFT.
Je vous joins un exemple avec des VIs express.
Cordialement,
Eloise
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;}
LabVIEW Tour
Journées Techniques dans 10 villes en France, du 4 au 20 novembre 2014
Pièces jointes :
Express VI - Spectral Measurements.vi ‏61 KB

NI 9505 encoder resolution?

Hello,
I have the following hardware setup:
- compactRIO 9074 controller with one NI 9505 (DC Brushed Servo Drive) and NI 9263 (Analog Outputs).
- Maxon Motor RE 40 (no load speed ~ 7500rpm)
- Gurley Encoder R137 (180000 cycles/rev = 720000 counts/rev after quadrature) --> the signal from the encoder is connected to the NI 9505 motor drive on the specific slot for encoder.
The problem that I am facing is that the NI 9505 module cannot detect velocities higher than approx. 1130rpm. I tried with a much smaller resolution encoder (2000 counts/rev) and it works just fine. It seems to me that somehow the resolution the NI 9505 module is reading in the counts is not large enough or something similar. Has anyone experienced a similar problem? What are the exact characteristics I should look for in the datasheets to try to match the encoder resolution with the card resolution?
Thank you,
Bogdan
Solved!
Go to Solution.

Hello Bogdan,
please have a look into the "NI 9505 Operating Instructions and Specifications" (http://digital.ni.com/manuals.nsf/websearch/8F6DCAB89D6B9BAD862576850075EA18). On page 29 you will find in "Encoder Input Characteristics" the value for "Maximum quadrature frequency". That frequency is for the NI 9505 f=5MHz.
Regards,
Johannes Graeper
Applications Engineer
National Instruments

RT & FPGA Modules – I am missing a fundamental concept

Recently I have been asked to program a compactRIO 9074 and in the midst of researching how to do that, I have become thoroughly confused…
I understand that the RT module is used for precise timing (i.e low jitter) and somehow it interfaces with the host computer (i.e. computer with the VI). I also understand the FPGA module allows you to, and forgive the simplicity, recreate the circuit on the chip, thus allowing virtually true multithreading and really fast speeds. Also, the FPGA interacts with the IO modules/ports.
The thing that I am unclear about is:
When you program the compactRIO 9074, do you select only one module (RT, FPGA) and ignore the other?
-or-
Do you use both modules - the RT module for the embedded hardware and the FPGA module for the FPGA bitstream? If so, how does the embedded hardware talk to the FPGA? Is this something you have to manually program? Any literature/tutorials on this?
-or-
I’ve even read something to the effect- the embedded module gets programmed with the RT module when the cRIO boots up for the first time. If that’s true, then does RT module get used only that only time and all programming thereafter is done with the FPGA module? Is the one-time RT module provided by NI or is this something I would have to create?
I think that I am missing something so fundamentally simple that this whole project is becoming so unnecessarily complicated.
Thanks in advance for the help.
Joe T.

It is a bit complicated, but powerful and flexible. If your needs are simple, NI provides tools (such as the scan engine) so you may not need to get into all the details.
The cRIO is almost a full computer, running a dedicated, real-time operating system (either PharLap ETS or VxWorks, depending on your cRIO). On top of that, there's the LabVIEW runtime. That computer also contains an FPGA, similar to if you bought one of the NI PCI FPGA cards and installed it in your PC.
The FPGA talks to the processor in the cRIO. If you need full control over the FPGA, then you write that code yourself and use DMA FIFOs and front-panel controls to transfer data between the cRIO and FPGA. If you just need access to the IO, you can use the Scan Engine, as previously noted. You also need a way for the cRIO to talk to your computer. Again, you can write code yourself, or use the NI-provided tools such as network shared variables. If you don't need the cRIO to do anything other than act as an expensive data acquisition device, you can link a shared variable to an I/O channel and access it directly from your PC, or share your IO variables over the network. Run a search on the NI site for "network shared variable scan engine" for more information.
You write separate code for the cRIO and the FPGA. You can run your VIs on the cRIO within the LabVIEW development environment and use most of the standard debugging tools, it will just be a bit slower to respond than when the LabVIEW code runs on your PC. When you have a working program, you can build an application and deploy it to the cRIO so that it will run at startup. You can do this as many times as you like. The LabVIEW program on the cRIO may contain an FPGA bitstream embedded in it. Writing code for the FPGA is more complicated - there are limitations, and you must compile the code before you can run it (no interactive debugging unless it's running in simulation).

Test Sorties / Entrées Compact RIO

Bonjour,
je suis un élève de terminale STIDD et nous avons un projet à faire pour la fin de cette année qui sera présenté.
Notre groupe fait un système de gestion semi-automatique de scène pour l'éclairage en analysant les fréquences sonores et en agissant directement sur les différents projecteurs.
Nous utilisons donc un CompactRIO 9074 avec des modules Entrée / Sortie Analogique, j'aimerais tester ces sorties seulement je ne sais pas comment faire, j'ai crée un VI avec les sorties analogiques et un potentiomètre pour faire varier une tension en sortie du module cependant lorsque le VI est placé dans le compact et est lancé via le PC, rien ne se passe sur le multimètre.
Je suis désolé si cette question a déjà été posé mais je dois avouer que les forums NI sont un peu chiants niveau recherche :x

Bonjour,
D'accord avec Cindy. Il faut nous en dire plus sur votre organisation logicielle.
Francis M | Voir mon profil
Certified LabVIEW Developer

Connecting directly to CompactRio from a Matlab program

Hello
I'm working at Control lab of the Aerospace Faculty in Technion - Israel Institute of Technology in Haifa
we are working on a new project that we require to establish Computerized control system for Vehicles and Quad-helicopters. we required to develop the control in Matlab.
the current situation is that the data is sent with help of LabView to CompactRio device that been use only as DAC (Digital-to-analog converter). Then the analog signal connected to the remotes of the vehicles .
The CompactRIO model name is NI cRio-9074
The device is connected by Lan directly to the computer operating the Labview and Matlab.
a module is installed on the CompactRio in order to supply analog outputs
the module model name is NI 9264
we wish to simplified the process and let Matlab comuincate dircetly with the CompactRio.
but we not sure how we should approach it and if it possible to communicate directly with CompcatRIo.
Thank you
Or Hirshfeld
http://il.linkedin.com/pub/or-hirshfeld/4b/79/577

Hello OrHirshfeld,
You may want to start by understanding how the cRIO functions. It is a target for code developed in LabVIEW (and C, if you know how) to be deployed to. Any functionality such as UDP, TCP/IP, etc should be implemented in the code so you can pass data to/from a Host PC. It may be worth looking through our NI CompactRIO Developers Guide to gain some insight on the things you can and should not do with a CompactRIO device.
Let us know if you have any specific questions. Our Example Finder in LabVIEW should have a lot of things you can look at as well. You can locate it by going to Help>>Find Examples in any window in LabVIEW.
| Zach J. | Applications Engineer | National Instruments |

Synchronize DSA modules and 40 MHz clock on CompactRIO

Hello.
We are using CompactRIO to perform vibration and counter measurements. We are using DSA modules (9234, 9229) for analog signals and 9411 modules as digital input for counter period measurement. We need to perform these measurements in sync over a period of 24 hours.
DSA modules use the internal 13.xx MHz of one of them as master, while counter measurements use the FPGA 40MHz clock. The problem is that after a couple of minutes we see a noticeable drift between them.
Two questions:
1. Is it possible to derive a 13.xx MHz clock from the FPGA 40 MHz clock, and use it as a master for DSA modules?
2. Is it possible to export the DSA master 13.xx MHz clock and use it as an input to the FPGA? This way we could quantify the drift between both clocks.
We found this post: http://forums.ni.com/t5/LabVIEW/Export-FPGA-Onboard-clock-to-io-modules/td-p/1149080, but it's not exactly the same situation.
Kind regards,
Daniel Ramírez
CLD - CADETECH S.A.
Chile

Yes - there is a method of calculating speed on the FPGA and with reference to the oversample clock. Consider this document:
http://www.ni.com/example/31301/en/
It uses a high speed analog, yet it time stamps level detection - a digital output - to the DSA oversample clock.
Then in the LabVIEW Sound and Vibration Measurement Suite Order Analysis tools, you can find the digital tachometer VI used to prepare the speed pulses for resampling and order analysis.
Let us know how this works.
Preston Johnson
Principal Sales Engineer
Condition Monitoring Systems
Vibration Analyst III - www.vibinst.org, www.mobiusinstitute.com
National Instruments
[email protected]
www.ni.com/mcm
www.ni.com/soundandvibration
www.ni.com/biganalogdata
512-683-5444

Custom device / I am trying to use a vehicle controller model developed in LabVIEW with compactRIO (cRIO-9024)

Now I have developed a vehile controller model with LabVIEW so as to run on VxWorks operating system. ( compactRIO cRIO-9024)
And I converted a controller model of labview into *.lvmodel in order to use it as I did with simulink models.
However, converted *.lvmodel was not supported for VxWorks operating system. so after searching for this, I found out that I have to use a custom device.
I am now studying the custom device, but it looks diffcult because I dont have much experience in real-time system.
Here are my questions.
1. Simulation model in VeriStand
Should I convert a labview controller model into *.lvmodel even if I use the custom device in order to run on VxWorks operating system?
If not, what should I do after building a controller model with labview?
2. Operating system
It is silly question. anyway, as long as I run a controller model on compactRIO cRIO-9024, the operating system always has to be set to VxWorks. Is it right?
3. Custom device
This is the most difficult thing. I dont know even what to do. What functions should be inside a custom device template tool? The controller model send output signals to a vehicle model, and receive input signals from a vehicle model.
Thank you in advance.
Hognjun

Hi,
You should post this on the Veristand Forum.
http://forums.ni.com/t5/NI-VeriStand/bd-p/440
Ravi

Auto deploy a VI onto compactRIO or pop-up a vi on target in main VI

Hello
I have a main program where i have event structure and 2 state machines which do DAQ and Video. in a different project i have a pid controlled heater program that will be deployed on compactRIO. how do i program the main VI to auto deploy the heater program to target and get values from there to the main program. (for graph values can i use global varible between realtime program and normal main program)
I am thinking if i use the shared variable that is update by AI of a module on Compactrio in the main program, will it auto deploy it detecting that shared variables belong to target, but i want only the heater part of the program to get deployed not the event strucute, statemachines on the mian program. please help
If i can put a button on main program that when clicked can pop-up the heater program on compact RIO to adjust the PID parameters and close it and run with new values. is this possible?
Thanks in advance

Hi freemason,
I'm still a bit unclear on what you need. If you are able to develop your project such that all the VIs are located in thier respective locations (i.e. on the cRIO, RT or Windows Host), and you just want to change controls before running the FPGA vi, we can do that. Essentially, you use a read/write control VI before running the FPGA VI using the Run invoke node. You'll have to make sure to change the FPGA open reference options to not run the VI automatically (right click on it and select "Configure Open FPGA VI Reference...", uncheck the run option).
If you want to look at an example involving PID in the LabVIEW example finder, one that might be of particular interest is called "Template Multichannel PID". You can find this in through Help>Find Examples. Navigate to Hardware Input and Output>CompactRIO>FPGA Fundamentals>Analysis and Control.
You can use the execution of your host VI to start and stop the FPGA vi using the Read/Write Control VI and the Run invoke node. Also, you can use an invoke node to Abort the VI if that is necessary, but creating a stop control in the FPGA VI that allows the Host VI to stop using programming flow is usually more desirable.
I hope these suggestions help, but please clarify your question if you're still confused.
Also, Pablo. Try setting the VI to run as a start up application. A guide of how to do that is here.
Message Edited by Verne D on 04-06-2010 01:07 PM
Message Edited by Verne D on 04-06-2010 01:07 PM
Verne D. // LabVIEW & SignalExpress Product Support Engineer // National Instruments

CompactRio 9074 y ni 9234

Similar Messages

Maybe you are looking for