USB of cRIO 9022...

Hello,
I would like to use the USB port of my cRIO 9022 as a port to read a GPS or any other device. Is this possible or I can just use it for interfacing with USB -memories??
If it is possible, how ??
Thanks,
Hector.

Hello Hector,
The USB drives of VxWorks controllers like your cRIO only have software for using the USB slot for storage devices. It is possible to create a custom driver but you would need to develop this driver using a WindRiver VxWorks development seat. This KnowledgeBase has more information on this topic.
Regards,
Jon S.
National Instruments
LabVIEW R&D

Similar Messages

How can I use a USB camera with cRIO 9022. Please see my strange problem.

Hi,
I would like to use a USB camera with NI cRIO 9022. I used the same USB camera with NI USB 6216 DAQ device and developed a VI(within a PROJECT and outside it). So, It is working fine with NI USB 6216 device when I use the Vision Assistant Express VI and gets detected in its Initialization Window. Please see JPEG File 3 where I get NO ERROR.
I am facing a problem when I want to use it with NI cRIO 9022. What exactly I am doing in this case is:
1) Create a NEW PROJECT
2) Add Targets and Devices(NI cRIO 9022)
3) Use the Scan Interface mode
4) Create a NEW VI under the cRIO 9022 device
5) Use a Timed Loop(Synchronized with Scan Engine) for continuous Data Acquisition and Sending from the Analog I/O modules.
6) Use the Vision Assistant available through the NI Vision Acquisition 2010 Module(I get STUCK HERE! The Express VI opens the Initialization Window, but I don't see the USB camera like in JPEG File 3)
I am facing difficulties with this HOST COMPUTER, cRIO implementation differences. On my host computer I have the software packages as shown in JPEG File 1, and on my cRIO 9022 as shown in JPEG File 2.
Can someone guide me how to overcome this and get the USB camera detected when I am using NI cRIO 9022?
NOTE: If this is a problem with software mismatches on HOST and NI cRIO 9022 device, please see JPEG Files 1 and 2 for available software and Host and cRIO 9022.
Thanks.
Amar.
Attachments:
NI Vision Acquisition Express Error for NI cRIO 9022.JPG ‏39 KB
IMAQ and dx Modules Installed on my NI cRIO 9022 hardware(No NI Vision Acquisition 2010 SP1).JPG ‏82 KB
NI Vision Acquisition Express NO Error for NI cRIO 9022.JPG ‏48 KB

Only GigE comms are supported on the cRIO Real Time OS. Have a look at the following:
Machine Vision on NI CompactRIO and Single-Board RIO
Adnan Zafar
Certified LabVIEW Architect
Coleman Technologies

How can I use USB camera with NI cRIO 9022, please see my strange problem.

Hi,
I would like to use a USB camera with NI cRIO 9022. I used the same USB camera with NI USB 6216 DAQ device and developed a VI(within a PROJECT and outside it). So, It is working fine with NI USB 6216 device when I use the Vision Assistant Express VI and gets detected in its Initialization Window. Please see JPEG File 3 where I get NO ERROR.
I am facing a problem when I want to use it with NI cRIO 9022. What exactly I am doing in this case is:
1) Create a NEW PROJECT
2) Add Targets and Devices(NI cRIO 9022)
3) Use the Scan Interface mode
4) Create a NEW VI under the cRIO 9022 device
5) Use a Timed Loop(Synchronized with Scan Engine) for continuous Data Acquisition and Sending from the Analog I/O modules.
6) Use the Vision Assistant available through the NI Vision Acquisition 2010 Module(I get STUCK HERE! The Express VI opens the Initialization Window, but I don't see the USB camera like in JPEG File 3)
I am facing difficulties with this HOST COMPUTER, cRIO implementation differences. On my host computer I have the software packages as shown in JPEG File 1, and on my cRIO 9022 as shown in JPEG File 2.
Can someone guide me how to overcome this and get the USB camera detected when I am using NI cRIO 9022?
NOTE: If this is a problem with software mismatches on HOST and NI cRIO 9022 device, please see JPEG Files 1 and 2 for available software and Host and cRIO 9022.
Thanks.
Amar.
Attachments:
Host Computer Image or Vision Acquisition Software Installed.JPG ‏91 KB
IMAQ and dx Modules Installed on my NI cRIO 9022 hardware(No NI Vision Acquisition 2010 SP1).JPG ‏82 KB
NI Vision Acquisition Express NO Error for NI cRIO 9022.JPG ‏48 KB

When you select My Computer, you are running the program on the PC. In this case, the camera works because it is connected to the PC. The scan engine doesn't work because it needs to run on the cRIO, not the PC.
When you create the program on the cRIO, you can use the scan engine because the program is on the cRIO. You can't use the camera because it is back on the PC, and can't be found on the cRIO.
The project is a wonderful tool, but it may be making the programming seem too simple. It may not be clear to you that by moving a program to a different location (PC or cRIO), it is running in an entirely different environment on a totally different machine, even though it is just a little further down in the project. You can't easily access the hardware on one machine while running the program on the other.
So the summary is: The camera is attached to the PC. The scan engine runs on the cRIO. Never the twain shall meet.
Bruce
Bruce Ammons
Ammons Engineering

CANOpen Communication NI cRIO 9022 (9853 CAN module) - MAXON EPOS2

I'm implementing a velocity control loop on two Maxon EPOS2 70/10 control units, interfacing them with a NI cRIO 9022 (CAN module 9853). To this aim, I'm using the libraries from NI and they work quite well: for each EPOS2 I can read current, position and velocity using 2 PDO messages and set a desired velocity using 1 PDO message, all in a single timed loop on Labview Real-Time. My VI is based on a NI example included in the mentioned library. Even though the sampling time of the loop is set to 10 ms (as in the example file), I verified that all the operations were executed in about 30 ms.
My target is 1 ms sample time and I'd like to know if there is any chance to get this; are there some limitations in the software/communication protocol I'm using or is it possible to achieve 1 kHz control frequency? Based on the documentation, the EPOS2 CANopen driver is split as follows:
1.      Hardware Layer: VIs which interact with the CAN hardware (FPGA Interface folder).
2.      CAN Layer: VIs which construct/deconstruct CAN packets and handle communication between the Hardware Layer and the top level application (CAN folder).
3.      CANOpen Layer: Low level VIs which simplify the generation of the SDOs and PDOs used to communicate over the CAN bus (CANopen folder).
4.      EPOS2 Driver Layer: High level wrappers over the CANOpen Layer simplifying the control of EPOS2 drives (main folder).
It seems that the Layer that construct/deconstruct CAN packets is impelemented on the RT level. Is it correct? Do I need to move it to the FPGA level to improve performances?
I look forward to hearing any suggestions from you.
Best,
Nevio

Hi Nevio,
I am trying to simply read encoder values from my EPOS2 24/2 control units into Lavbiew. I have been through all the documentation however I am unable to establish communication between the EPOS2 and labview.
I am connecting the two using a USB connection. I can connect to and control the motors in EPOS Studio, but nothing in labview.
I am very new to Labview so I am probably not putting the correct blocks down for initialization.
Could you please help me by suggesting some good examples to look at or linking me to labview sample of initializing communication with the EPOS2 units.
Any help is greatly appreciated
Regards,
Kris

CANOpen Communication NI cRIO 9022 (9853 CAN module) and MAXON EPOS2

Hi all
I am trying to implement a velocity control loop on my Maxon EPOS2 motor controller, by using PDOs sent through my real-time controller (NI cRIO 9022) with a CAN module (9853).
I configured the PDO mapping in the object dictionary of the EPOS2, so that each new RxPDO1 contains the new desired velocity setting value, and I am trying to use the simple example contained in the National Instrument example directory criocanopenbaisc (freely downloadable here http://zone.ni.com/devzone/cda/epd/p/id/5474).
I can change manually in the object dictionary the value of desired velocity by using the EPOS studio tool by connecting via USB the EPOS2 to my computer, but when I connect the EPOS2 to the CAN0 port of cRIO the newly sent values does not make effect.
At the first try the .vi file hung on the Read PDO command, which is right after the Write PDO command. I suppose it means that no real PDO is sent over the CAN bus. However, I excluded the "Read PDO" from the diagram, now the file executes and terminates but no command is sent to the EPOS. I can verify through an oscilloscope that many similar digital waveforms are sent, just like if no ACK signal was received.
After various tentatives, I sent PDOs structured in the following way:
COB-ID (4 bytes containing the U32 representation of the COB-ID for RxPDO1: 531)
Updated value (4 bytes containing the representation of the desired velocity value, U32).
0 in U32
0 in U32.
The last two U32 are sent so to be coherent with the example of the NI library nicanopenbasic.
At the moment only one signal is sent (no more repetitive signals representing fault communication), but the values are not updated in the EPOS2...
Cheers
Solved!
Go to Solution.

Duplicated post

CANOpen Communication NI cRIO 9022 (9853 CAN module) and MAXON EPOS2

Hi all
I am trying to implement a velocity control loop on my Maxon EPOS2 motor controller, by using PDOs sent through my real-time controller (NI cRIO 9022) with a CAN module (9853).
I configured the PDO mapping in the object dictionary of the EPOS2, so that each new RxPDO1 contains the new desired velocity setting value, and I am trying to use the simple example contained in the National Instrument example directory criocanopenbaisc (freely downloadable here http://zone.ni.com/devzone/cda/epd/p/id/5474).
I can change manually in the object dictionary the value of desired velocity by using the EPOS studio tool by connecting via USB the EPOS2 to my computer, but when I connect the EPOS2 to the CAN0 port of cRIO the newly sent values does not make effect.
At the first try the .vi file hung on the Read PDO command, which is right after the Write PDO command. I suppose it means that no real PDO is sent over the CAN bus. However, I excluded the "Read PDO" from the diagram, now the file executes and terminates but no command is sent to the EPOS. I can verify through an oscilloscope that many similar digital waveforms are sent, just like if no ACK signal was received.
Looking forward to receiving any hint
Fabrizio

Some updates on the developments, since no one yet replied...
At the current time the PDO sent is structured in the following way:
COB-ID (4 bytes containing the U32 representation of the COB-ID for RxPDO1: 531)
Updated value (4 bytes containing the representation of the desired velocity value, U32).
0 in U32
0 in U32.
The last two U32 are sent so to be coherent with the example of the NI library nicanopenbasic.
At the moment only one signal is sent (no more repetitive signals representing fault communication), but the values are not updated in the EPOS2...
Cheers

Trouble saving images on cRIO-9022

I'm having trouble saving images on my RT target cRIO-9022 (VxWorks). I get "error 53 occurred at Write GIF File.vi LabView: Manager call not supported" when running the code. What I'm trying to do is save periodic snapshots of front panel charts/graphs locally on the cRIO and download them at a later time.
I've also tried some of the report generation VIs and had broken arrows and compile errors. from what I've read in help and online, It seems perhaps it is not possible to do what I'm trying to do with my particular target. Is there any reason that I shouln't be able to save images locally to the RT target? has anyone else had a similar problem generating reports or saving images on the cRIO-9022?
Thanks for any help you can provide,
truth204

I've run into similar problem before... I was unable, at the time, to find a good workaround for saving front panel images to file on RT because the necessary report generation functions were unsupported on the RT environment. If you are just saving data from charts and graphs, you might want to consider saving the data as a binary file or a spreadsheet/.csv style file. This is ultimately what I did in my RT application, and then I created a separate desktop application that would read the data from those exported files and reproduce the charts/graphs that were created on the RT target.
Here is a KB describing your error, for reference: http://digital.ni.com/public.nsf/allkb/39B5B135F32902388625723B00683B27
Cheers!
Logan

Trouble installing NI-TimeSync on cRIO-9022

Hello,
I have a PC with LabVIEW 2012 SP1, NI-RIO 13.0 and NI-TimeSync 1.3.0.
I'm trying to install NI-TimeSync on my cRIO-9022. I selected the "NI CompactRIO 13.0 - August 2013" Recommended Software Set, and started choosing add-ons. However, the only option I get for TimeSync is "NI-TimeSync 1.1.5", which is greyed out. MAX tells me "You cannot select NI-TimeSync 1.1.5 because only a newer version (1.3.0) is installed on your host."
However, I had installed "NI CompactRIO 13.0 - August 2013" and "NI-TimeSync 1.3.0" from the same device driver CD!
Is this expected? How should I proceed? Is it safe to use a Custom installation to add TimeSync 1.3.0?
Solved!
Go to Solution.

Hi JKSH
This is not an expected behavior, but keep in mind that the custom installation is safe, if MAX is able to install the NI –TimeSync 1.3 using that method is should be fine
If you get any other message or error I recommend you to format the cRIO and reinstall everything.
Regards
Esteban R.

Generate Square pulse Using DO module with cRIO 9022

Hello,
I want to generate square pulses of 400Hz using NI 9401 for cRIO 9022. I want to control the frequency from 1- 400Hz from PC using LAbview.

Hi Mekel,
most CompactRIO applications use three separate processors—a Windows PC, a real-time OS controller, and an FPGA. The CompactRIO controller uses the LabVIEW Real-Time OS instead of Windows. The FPGA does not use an operating system because the code is implemented directly in hardware.
The common tasks for the Windows host VI include the following:
• logging data to the PC
• accessing databases
• integrating with enterprise systems
• providing a human-machine (user) interface (HMI) and display
• supporting supervisory control.
The RT controller VI tasks typically include the following:
• processing data
• control
• logging data on the RT controller part of the CompactRIO system
The FPGA VI tasks include the following:
• I/O
• hardware-based timing and triggering
• low-level signal processing
• control
Communication between I/O modules and FPGA is digital because signal conditioning and ADC is done in the modules. Communication between the RT controller and FPGA uses the PCI bus in the CompactRIO. Communication between the Windows host VI and the RT controller VI normally occurs over the Ethernet.
Serena

FPGA. Which xilinx tool for Crio 9022 & 9030

Hi. I will be compiling fpga programs on the Crio 9022 & 9030. Do you need different xilinx compilers to do the task?
Using LV ver14
Crio 9022 requires xilinxs tool 14.7?
Crio 9030 requires the xilinx tools vivado 2013.4?
Thanks

Yes, this is because of the different series of FPGAs that are on the 9022's backplane and the 9030 cRIOs. You can see this KB and this KB to further see why.

My cRIO (9022 , chassis 9113, module NI 9225)

Hello, I hope you are doing great
I create a new project that detects my cRIO (9022 , chassis 9113, module NI 9225) and I copied cRIO both the FPGA VI and Host of the original project NI but problem persists: there appeared another error message at the Host.VI (see attached file).
I did not get to solve this problem can you help me to find a solution as soon as possible
thank you for advance for your help
Attachments:
erreur1.jpg ‏276 KB
erreur2.jpg ‏214 KB

Hi basmasag,
It looks like you need to specify a top level VI of the Build Specification you're trying to build. You'll need to select the Source Files Category on the left in the build specification properties menu. Then highlight your top level VI (in the example its called NI 9225 Getting Started (FPGA).vi) and select the blue arrow to set it to be the Top-Level VI. I've included and image to better illustrate what I mean.
I think the FIFO error your seeing may be due to the Type of FIFO you've configured the Data FIFO to be in your project. In the example it was Tartget to Host - DMA. Make sure that's set correctly by double clicking on the Data FIFO, and setting the type. The second picture I attached should better demonstrate what I mean.
It seems like you may be new to LabVIEW FPGA, I think you'll find a lot of useful information here: http://zone.ni.com/reference/en-XX/help/371599G-01/lvfpgahelp/fpga_getting_started/
Applications Engineer
National Instruments
CLD Certified
Attachments:
Top-Level.png ‏59 KB
fifo.png ‏48 KB

Does cRIO-9022 controller support LV RT 8.5.1?

Hi, everyone.
Does cRIO-9022 controller support LV RT 8.5.1?
Thanks.
Daniel R.
CLD
Solved!
Go to Solution.

I "believe" because I searched ni.com and couldn't find anything about software limitations with cRIO. I talked to a couple people I know that work with cRIO and they said that software version isn't a limitation. Basically you could run cRio with LV RT 7 without a problem.
However I'm not 100% sure about this.
My advice is:
Try it and see.
Good Luck!
Bruno Noronha
Certified LabVIEW Associate Developer
Using LabVIEW 8.6

CRIO 9022 date setting

Hello!
I would like to configure cRIO 9022, as first step I need to set the date on it because now it's about 1960 , can you give me a hint where to start with it? I don't have the hardware with me now, it's a part of a project. What kind of toolboxes do I need, is there any written tutorial? Thank you for your help in advance!

You should do the setup and all related things in MAX - once you connected the cRIO to your (local) network…
All that is described in the manual that comes with your cRIO!
Best regards,
GerdW
CLAD, using 2009SP1 + LV2011SP1 + LV2014SP1 on WinXP+Win7+cRIO
Kudos are welcome

How to achieve high usb data rate with cRIO-9022?

Hi all,
I read the datasheet of NI-9022 and know that USB data rate can be 480Mb/s.
I want to transfer data with rate 3.6MB/s which is much slower than the spec, but the result is time out error.
I check my FPGA and RT code by save to RT disk and the result is pass. So I think my code should be correct.
Is that because the USB driver not installed into RT?
Should I install the USB driver into RT?
Or is there any other issue I haven't find?
Thanks a lot.

According to this document: Data Storage Options for CompactRIO, depending on many conditions, such as complexity of processor
requirements, USB data can be transferred off the controller at
approximately 700 KB/s.
Also, you don't need a driver to get a USB mass storage device to work on the cRIO. Have a look at this document:
Utilizing Features of the USB Port on My cRIO-901x or My cFP-22xx Controller
Not sure if these issues are causing timeout errors. What happens when you transfer data at lower speeds? Do you get timeout errors then?
Adnan Zafar
Certified LabVIEW Architect
Coleman Technologies

Sine generation through crio 9022

hi...........
i am generating sine wave using simulation function. i am able to see waveforms in labview front panel but not in oscilloscope.

Hey pa1990,
Can you elaborate on what exactly it is you are trying to do, what you've tried, and what is not currenty working? The more information you can provide the easier it is for us to help you.
Thanks!
-Sam K
LabVIEW Hacker
Join / Follow the LabVIEW Hacker Group on google+

USB of cRIO 9022...

Similar Messages

Maybe you are looking for