cRIO 9067 problem of chassis

Similar Questions

• Same code compiled for the cRIO-9074, but reports no diagram component calendar violation for cRIO-9067

  Hi, just got my new cRIO-9067. I have converted my project over the cRIO-9067 since the cRIO 9074. Same layout module, same engine, same scan code custom fpga, (hybrid mode).  I have no problem of compilation for the 9074, which is a lower performance FPGA architecting the 9067 FPGA.

  The final timetable for windows compilation shows that the timing is respected for all clocks - 40, 80 and 120 MHz (I use a clock derived for some code sctl). During the end of compilation, during the phase of gen bitfile, I get the dreaded time violation. Investigation of the breach indicates that it is not the custom code, it is not schema components. One of them seems to be linked to the card series OR 9870 I in the chassis.

  Why? Is there anything I can try with the compiler directives for this problem? You would think that it would be easier to compile for the highest performance FPGAS...

  OK, don't ask me how I thought this output - to run I changed nothing else than this: feed the I/O node a reference FPGA of e/s instead of configure the node via the menu "link to. It makes no sense, but the compilation succeeded when I did this.

  I know it is because I created a very simple test VI in my project and made sure it does not compile without it.

• cRIO 9067 to hired 7fh USB RS232

  Hello

  I have a cRIO 9067 and would like to interface with an instrument that has a converter USB-RS232 from SiLabs.  I can't comminicate with this instrument easily on a Windows PC.  I am able to see the device in MAX when its the cRIO connection.  IT appears under "Devices and Interfaces" as "USB0::0x1FB9:0 x 0100: 121A00A:RAW ' with model number and description of the device.

  I followed the description at this link, but I don't get a ttyUSB # devices.

  https://decibel.NI.com/content/docs/doc-34827

  Is it possible to get this working on the cRIO as a serial port?

  Thank you.

  After some research, talk with people, NOR google and to talk with people to lakeshore.com (provider of the device) this is what I have reconstitute on how to make this work:

  • Under Linux, usb devices are listed automatically, and by default, will appear as a USB RAW device
  
  
  • Once the USB device has been identified, it can then subsequently be linked to a driver
  
  
  • Linux determines if and when to link each device USB-based device Vendor ID (VID) and the model identifier (MID). It is usually 3-4 digit hex string.
  
  
  • In the case of the Lakeshore 121 power source, VID = MID 1FB9 = 100.       I could see in MAX for the Raw Device USB.
  
  
  • There are two levels of USB-serial device drivers. The first pilot: usbserial.ko is a generic driver that handles all USB-serial devices. This should be loaded for any USB-serial converter.
  
  
  • The second driver is specific to the chipset for the USB-serial device.       For the cRIO, there are three options which are pre-installed (DFT, 7fh and a few others)
  
  
  • The drivers can be found at /lib/modules/3.2.35-rt52-2.0.0f0/kernel/drivers/usb/serial/ (where the kernel version directory may vary)
  
  
  • Lakeshore 121 uses the TR labs CP210x chipset, so we chose this one.
  
  
  • Records of the device first of all need to be loaded by Linux. Linux can automatically do this by adding files of length zero in the module.autoload.d directory. To do this run the following:
  
  
  • CD /etc/modules.autoload.d
  
  
  • Touch usbserial
  
  
  • Touch cp210x
  
  
  • restart cRIO
  
  
  • run dmseg. grep usbserial to confirm that usbserial driver is responsible
  
  
  • run the dmesg | grep cp201x to confirm that the driver for cp210x is loaded
  
  
  • The next step is to associate the cp210x of our device USB device driver. Don't forget that linux associate unit to a pilot from the VID and moy. anyone installed linux cRIO base, I'm sure, knew nothing of the VID 121 Lakeshore and MID.
  
  
  • Lakeshore recommended to read the source code for cp210x, adding the VID and MID to the list of recognized devices, recompile the cp210x.ko file and install it on the cRIO. It would work, but it is beyond my current Linux capacity.
  
  
  • Linux offers the possibility to dynamically add MID, VID, so that a device can be recognized on the fly
  
  
  • When the driver CP210x is loaded, a struchture of the entire directory is created. There is a file because the directory structure called new_id where you can dynamically added VID, mid
  
  
  • Create a startup script to run the following command. Be aware of the problems of termination of cr/lf line between operating systems. It is generally easier to create the script on the cRIO with the VI editor to avoid any problems.
  
  
  • echo 1FB9 100 > / sys/bus/usb-serial/drivers/cp210x/new_id
  
  
  • Startup script Info: https://decibel.ni.com/content/docs/DOC-38960
  
  
  • Now, restart (or running the script), you will get a device/dev/ttyUSB [0-9]
  
  
  • Unfortunately, the creation of default of the unit ttyUSB [0-9] does not permission to write, so we have need create a UDEV rule to automatically grant writing
  
  
  • Add the following lines of code udef.conf in the folder/etc/udev

  #typical devices

  ttyUSB [0-9] * root: ATS 666

  • Create a file named 99 - ttyUSB.rules in the /etc/udev/rules.d folder
  
  
  • Add this line of code in this file:

  KERNEL == "ttyUSB [0-9]" * ", OWNER ="admin", MODE ="0666""

  • Restart the cRIO. This should be it! It worked for me.

• install software failures on cRIO 9067

  OK, I got a new cRIO 9067 and I noticed, while installing software on it well as MAX, everything works as long as I CHOOSE NEITHER WATCHDOG 14.0.0.  If I do, I get the following error. It's very repetitive.

  

  This is another so that I installed, otherwise:

  

  Hi Mark,

  The driver OR Watchdog is part of LabVIEW Real-time, sounds like something might be wrong with your installation of the Module LabVIEW Real-time on your computer.

  Can you uninstall and reinstall the Module LabVIEW Real-time and see if that fixes the problem?

• error when trying ot read more large block memory on cRIO 9067 LVRT 2014

  I get error "-2147220623" when you run the following code on a cRIO 9067. It works on the cRIO 9074

  

  
  

• Support for LabVIEW 2014 and CanOPEN cRIO-9067

  Hello

  We have NEITHER 9881 CANOpen communication module and cRIO-9067.

  According to the NI 9881 product description page the module should work with cRIO-9067. However, does not support the latest NOR-Industrial Communications for CANopen 1.0.3 2014 LabVIEW and NI RIO 14.0. This means that we cannot use cRIO-9067, can we? If so, when the next version of the pilot will be available? It will work with the cRIO-9030?

  Thank you in advance,

  Nikita.

  Hi Nikita,

  I wanted to let you know that support for the cRIO-9067 is available: http://www.ni.com/download/ni-industrial-communications-for-canopen-14.5/5234/en/

  Thank you!

• acquisition of images to remote USB vision cRIO 9067

  I have a 9067 linked to a camera USB from Basler.  I am able to correctly display images via MAX and the example of Grab until I run the Grab sample on the target of RT.  However, I need not to images processed on the RT or FPGA in this application.  Is it possible to open a connection to distance from the camera to my computer using IMAQdx host?

  I was hoping I could use something like "[cRIO IP address]: cam0 ' in-camera address, but that doesn't seem to work.

  Is this possible or do I pipeline manually the images of the RT target?

  Thank you

  Omar

  Hello Omar.

  You can access the camera image directly addressing it through the cRIO. You will need to implement the transfer of images between the host PC and the cRIO. Fortunately, you can do this quite easily by using a variable flow or shared network image.

• UDP communication via secondary ethernet port on the cRIO-9074 problem.

  Hi guys.

  I connected my host pc running LV 2010 my cRIO-9074 port using a main ethernet crossover cable. I want to use the second port ethernet on the cRIO-9074 to read UDP messages, and I want to access these messages on my host. UDP messages are sent from a local network, but for testing I also use a second pc running LV 2010 to send UDP messages.

  I configured the ethernet on the cRIO-9074 ports according to this tutorial: "knowledge base 4E0DGASK: Configure the Ports of double Ethernet on real-time controllers'." " My host and primary ethernet port belong to 'Subnet A' while the second port and the second computer, sending UDP messages belong to 'Subnet B' (at the end of my post I will list the masks of ip addresses and the subnet).

  For simplicity, I used the VI´s of this example as a basis for UDP communication. The "UDPServerOnRemoteTarget.vi", which broadcast messages UDP, will run on the secondary computer. The "UDPClientOnRemoteTarget.vi", which reads messages UDP, will work on my host pc.

  Now, in the 'UDPServerOnRemoteTarget' VI, you must specify two IP addresses (port # remained unchanged at 3363):

  1: the IP address of the ethernet port that will be broadcast UDP messages.

  2: the IP address of the ethernet port that will receive the messages.

  In the #1 case I put the IP address to the IP address of the ethernet on the secondary pc port.

  At the #2 I tried to set the intellectual property: a) IP address of the secondary ethernet port on the cRIO, b) IP address of the ethernet on my host computer port and c) IP address of the primary ethernet port on the cRIO.

  None of the parameters produced results. I also tried to change the port number, which did not help.

  However, if I bypass the cRIO and connect the host pc and the secondary computer directly (by using a cable crossed a regular cat5 ethernet cable), I am able to send and receive UDP messages (the two stand-alone always are on different subnets). I guess that this at least excludes any fault in the VI´s code.

  Does anyone know what I'm doing wrong here? Is it possible at all to read the UDP messages that are sent to the secondary ethernet port on the cRIO my host pc?

  I have searched the entire site OR and forums, but didn't come through all that solved my problem. Most of the other tutorials configuration resembling my case is to import the device sends UDP messages in the project, but which is clearly not possible in my case, or is it?

  My IP settings are:

  cRIO 9074:

  Primary ethernet port: 169.254.62.215

  Secondary ethernet port: 192.168.0.102 (static)

  Host PC: 169.254.58.4

  Secondary PC: 192.168.0.144 (static)

  SubnetMask on all ports are the value 255.255.0.0

  I hope someone out there can help me out.

  Kind regards

  Phat

  Solved.

  Stupid mistake. I was running the VI on the host instead of the cRIO pc, which explains why direct communication between the computers worked. Everything works well when it is compiled for the cRIO.

  Kind regards

  Phat

• cRIO deployment problem error:-1967357951

  Hello

  When I connect to my cRIO-9073 an error message appear that he could not find any libraries.

  When I ignore it and continue I can't load my VI on the host PC and target in real time.

  I think I installed all the necessary software on the cRIO.

  A description of the problem can be found in the attached PDF file.
  The labview program can be found in attachment.

  Best regards

  Jasper

  Hello, Jasper.

  I've seen this problem before in combination with a problem of memory (availible) on the controller. I see that you have many installed on the controller for cRIO. The cRIO-9073 is around already for a couple of years and is limited in terms of memory avaiable by comparing our new controllers. I noticed you use LabVIEW 2013, which has a larger footprint versions of LabVIEW that where around when the cRIO-9073 saw the light of day. I recommend to format the controller and only install the bare minimum that your application needs for the controller and try again. In this way, we can check if this arrizes cause a memory issue or something else.

  Kind regards

• Compliling VI in LabVIEW with cRIO-9004 controller and chassis cRIO-9104

  I tried to compile in LabVIEW with cRIO 9004 and cRIo-9104 connected.

  It has three options

  (1) use the server local compilation.

  (2) to connect to the network compile Server

  (3) to connect to the service of LabVIEW FPGA cloud compile

  But I'm unable to compile my program using one of these.

  How can I get my compilation made? Help, please.

  Thanks YouCp

  Service provider shared's Standard Service program is an annual fee of NOR, which in turn allow you to update your modules and LabVIEW and benefiting from the support of NEITHER.

  https://www.NI.com/services/software_benefits.htm

• Why the memory usage of my place of cRIO until the accident?

  Olla and servus Hello,

  I have another problem with my test setup!
  A cRIO-9014 with 9118 chassis and modules.

  The problem manifests itself in a way the cRIO hangs after some time. During this time, I went up to now that it is the use of the memory of the controller! This is the beginning of the Proggramms RT to ~ 40% but continues to increase. Until there are about 98%, and the connection is lost to the target system.

  Do you have any idea what may be the reason.

  Thank you very much for your answers!

  MaJahn

  
  

• cRIO - creation and deployment of real-time independent startup application troubleshooting

  I use cRIO-9024 with a chassis 9112 for a control system. I use LV2011 SP1. When you run the system in development mode (by pressing the run button), everything seems to work properly. When the autonomous real-time construction and running in startup application, something stops working.

  In order to know if the application is running or not, I toggle the user LED on the cRIO using this code:

  

  When I turn off all the code in the main VI except this loop, the application deploys and runs at startup without problem (the LED flashes). I then add progressively more loops that I want to run (by disabling the code less and less), and the problem seems to be in the open FPGA VI reference block. If I disable this block, the slopes of autonomous real-time application (I guess the error 63195, handful of peripheral communication not valid, will spread along the line, but I know that the app works because the LED flashes).

  

  I tried several configurations for this block open FPGA VI and mixed results. For example, if I set it up this way:

  

  The application in real-time to start runs with the reference block opened VI FPGA active but work stoppages as soon as I turn on a code that makes use of this reference in the subVIs .

  Someone at - it an idea of what could go wrong? I have explored the messages thrown by cRIO at startup but can not see the error messages (in fact, the console output is the same when I managed to deploy an application that is running (by disabling the code). I also tried to explore the error logs (via right click on target Utilities > view error log) but cannot decrypt any useful info on their part.

  

  Any ideas will be greatly appreciated.

  Hi kkguner,

  My problem is that the code runs (apparently) ok in development mode, but it seems that, when it is deployed as a stand-alone application in real time, it does not at all. As I was not able to get messages through to watch the console output when restarting my cRIO or explore the Project Explorer error logs or error, I can only imagine what is happening.

  I feel that QFang suggestions go in the right direction, but I've yet to be able to determine the exact cause and the solution of the problem.

  The solution I set it with has been to deploy my application as a source with a start VI distribution instead of as a stand-alone application in real time. You can try this option.

  What I could try when I have some time is to clean my system from LV (whether in mass compilation or by reinstalling completely). I tried a massive compilation of vi.lib and I got a good amount of (UN) insanities, the wrong screws and several other unfortunate messages.

  kkguner, let us know what you discover in your inquiry, or if none of the suggestions solves your problem.

  Thank you QFang and xseadog for your help. Best regards!

  --

  Raúl

• CAN 985 x and cRIO 9012

  I have a cRIO-9012 controller and chassis 9101.  I can't perform the basic examples.  My question revolves around game upward.

  Background: I have 8.6 with time real/fpga, NIRIO 3.0, NICAN2.6, as well as the 985 x software 1.3.2.  I loaded up the most recent 2008 of NIRIO3.0.0August on my RIO, however running example base reception/emission FPGAs cause time-out errors.  I added another module (9472) just to make sure I can turn some of the visible lights.  However as soon as my typing the CAN node loop this loop freezes all my lights are flashing away.

  This morning I thought that to run the example, channel CAN Receive.  I've loaded and sent the channel config in RIO.  I try to deploy the host VI and receive the following:

  Deployment RIO0 (the goal settings successfully deployed)
  Deployment ncConfigCANNet.vi
  Cannot download ncConfigCANNet.vi

  LabVIEW: Unable to load the shared library nican. *: ncConfig:C on the target RT device.

  Here's where I'm confused.  I thought that the VX works system does not support the CAN.  I see not everything CAN be supported under the NIRIO3.0.0August 2008 software, but this error of downloading indicates miss me a driver (or else...)  Someone had a similar problem, I'm missing the software on my controller?  Any suggestion is welcome.

  Thank you.

  I have found a new 9853, we received last month.  I could put in the 4 Groove and using my reception and transmit programs successfully.  I could watch the heart CAN, in addition to performing a loop of CAN1 to CAN0 test.

  The original 9853 headed on an RMA for NEITHER.  This module is apparently 1 year old.

• CRIO not visible under MAX

  Hello

  I use a CRIO 9081 which worked well with MAX/VeriStand, but recently, I've reconfigured MAX and now, the chassis is more visible in remote system when I refreshed it...

  What I need to reconfigure the CRIO or reset the chassis and the IP to see him again?

  I tried the automated discovery system troubleshooting remotely , but it does not work.

  You have an idea?

  Hello

  Have you tried:

  -disable the firewall

  -reset the compactrio system ip

  -Reinstall MAX

  This link explains how to reinstall MAX.

  http://digital.NI.com/public.nsf/allkb/D1F1D3FC80E4FFDF86256B410059DE31

  Best regards.

• cRIO-9004

  I have configured my cRIO 9004 with the chassis to my PC. But with the acquisition of data assistancce, I am unable to acquire data.

  What can the reason for this possible?

  Hey, Vinayak,.

  The VI of Express Assistant DAQ uses the DAQmx driver and will communicate only with devices supported by DAQmx. (Devices like CompactDAQ, DAQ, of the series M and X series DAQ USB or PCI)

  CompactRIO is an incredible product, but it's much more complicated program. You will need to add it as a remote device to your project and specify at least one additional VI to run on the processor in real time (if not a third run on the FPGA).

  Google image search "getting started with compactRIO" for a starting point.