cRIO 9081 to the 9144 expansion chassis. FPGA engine mode or scan?

Similar Questions

• ID of Module cRIO-9081

  I use a property of e/s FPGA node to get the serial number and the ID of the Module for each module in my cRIO-9081.  The serial numbers match exactly what I thought, it was in my cRIO.  The ID of the Module, however, makes no sense.  I thought that the ID of the Module would have been 9201 for a module OR-9201.  I got a number: 21754370963.

  What should be the ID of the Module?

  Hello Paul,

  The module ID returned by the property ID of Module is not the name of the actual module (e.g. 9201). It returns an ID that you can then associate with a specific module as described in the link below.

  C Series Module IDs:
  http://zone.NI.com/reference/en-XX/help/370984R-01/criodevicehelp/module_ids/

  Kind regards

  j_bou

• CAN the c series modules and drivers XNET and Ethernet expansion chassis cRIO compatibility issues

  Hello

  I encountered a problem with my current setup which was not picked up by the tool advise cRIO or by the engineer of applications OR that we used to check our configuration before starting the project.  It turns out that the NI 9853 CAN modules require a XNET driver that is not compatible with the NI 9149 expansion chassis.

  We currently have a system with a cRIO NI 9068 with general IO and some CAN controller and CAN open modules in a carrycot and an Ethernet NI9149 with more general IO expansion chassis and more CAN and CAN open an another pod remote modules and all of this should work under water, so I can not move the modules of the expansion chassis to the chassis controller without a lot of overhaul of the system and equip and a team of angry engineers and technicians.

  I have developed the FPGA code for the 9068 OR and have CAN and CAN open networks works with happiness.  Then I tried to copy the same FPGA code on the expansion chassis and it compiles, but when I try to launch it I get the error-63184 code.  After long calls OR support, and tries to install the missing drivers on the expansion chassis, we discovered that XNET is not compatible with this chassis.

  Can anyone suggest the best course of action?  Is there an expansion chassis Ethernet that will support XNET?  I have here no information online about this compatibility issue that I can't find?

  I'll be communication with DIRECTLY, but from previous experience of the "odd" questions, I know the community often hold the key.  Any suggestions gratefully received.

  Thank you, Ed

  It's official.  CAN open modules are not compatible with the expansion chassis.  I have them moved to RIO and will get the upgraded pods.

  Thank you

  Ed

• Get the absolute time on a chassis ethercat 9144 in labview fpga

  I'm testing the timing and synchronization of a distributed system, consisting of an OR-cRIO-9082 and two ethercat NI 9144 chassis.  Is it possible to access the system on the 9144 absolute time of in the FPGA?

  Thanks for the reply.  In fact, I just figured this out a few moments ago.  It is possible to add a timestamp to a variable that is defined for the user by selecting 'Enable Timestamping' on the user defined variables properties dialog box.  This timestamp does what I want, because it uses the absolute time of the 9144 (that is synchronized with the master clock), and this time can be read on the host/Master.

  At least I think it does what I want.  I'm in the process of coding and testing right now.

• Missing items from NI 9214 FPGA of e/s (cRIO-9030 / combo NI 9144)

  I have a new cRIO-9030 and the expansion chassis NI 9144 EtherCAT I configured and added to a project existing LabVIEW that contains a cRIO-9012. When I researched targets and devices, modules have been correctly detected (NI 9237, NI 9263 and NI 9265 on the cRIO-9030 and 9214 NI and NI 9477 on the NI 9144 chassis); However, the I/O items listed for the show of the NI 9214 module only 16 channels thermocouple (TC0 by TC15). Four additional channels do not appear (track and CJC0 through CJC2), although they did when the module has been previously configured for the cRIO-9012.  It is a known / compatibility problem with the NI 9144? or y at - it a configuration option, I'm missing? The terminal block must be set up on the module for these I/O elements appear?

  I think I have solved the problem. If I first add a FPGA target under the appliance NOR 9144, and then add the NI 9214 module under that, then additional channels appear. I guess that means that these elements of I/O are available when you use the NI 9144 FPGA mode?

  Sean

• Combine the cRIO 9076 and cRIO 9081

  I have two controllers time real FPGA: cRIO 9076 and cRIO 9081.  Due to not having the latest version of LabVIEW (2011), I am unable to use cRIO 9081.  CRIO 9076 not having only 4 slots for modules, I am using cRIO 9081 as a slave just to add more modules on its machines slot.  Will this work?  If so, how can I connect the cRIO 9081 to cRIO 9076. Any suggestion is appreciated.

  Hello ExcelX,

  Unfortunately, there is no meaningful way to interface with the 9081 without going through the correct versions of LabVIEW (at least 2011) and NOR-RIO (at least 4.0). It does not have windows, so you could theoretically it boots into Windows and plug a monitor on it, but you wouldn't be able to run any code on it.

  You can download the demo version of LabVIEW 2011 and use it with your 9081 for thirty days. But I recommend you just upgrade to LabVIEW 2011 - the 9081 is a powerful (and expensive) CompactRIO.

• Serial numbers for the cRIO-9081 Module

  Is there a way for the FPGA in the cRIO-9081 to read the serial number, date of calibration of the NOR-9201 module installed in the cRIO?

  I want to get this information and send it to my Host.vi, because we have a duty to provide information instrument document during a series of tests.

  Thank you

  Paul

  

  Use a property node of the module to read the number of series/VendorId... but the calibration date is not stored. (FPGA code example shows NI9205 data)

  Here a Fifo of DMA target host is used to send the data to the controller of the CR...

• Rename the cRIO-9081 with MAX 5.5

  We have several cRIO - 9081 s.  We have deployed the year last two and deploy at least 4 more this year.  Those deployed last year is MAX 5.4 running and we were able to give them an alias so that our code can work on both systems.

  4 new run MAX 5.5.  There is no option to rename or give them an alias so that they correspond to older machines.

  Why MAX 5.5 does not create an alias?  Y at - it a new version of MAX that allows us to perform the alias?

  I wouldn't waste your time to reset your database MAX.  This isn't the problem, and unfortunately, it gets more prescribed as a solution.  It seems to me that if you have the runtime OR RIO, but not the support of configuration installed on the second computer.

  In the past, MAX don't would not show the device at all if the configuration management does not been installed, Ute 5.5 now shows always the device, but you may be missing the views of configuration if you have no support for configuration of the devices installed.

  The safest thing would be to install the full OR-RIO and make sure you only select the CompactRIO support.

  http://www.NI.com/download/NI-Rio-14.5/5129/en/

  There may be a smaller distribution somewhere that understands what you need, however I know that we have everything.

• Mode of scanning/FPGA for a CRIO by Veristand

  Hello!

  I have a small error using my CRIO 9081 use with CAN communication, here's what I did:

  1. I use the CRIO with scan mode and customized it "Scan engine" and Ethercat for show my analog modules under VeriStand, it's ok

  2. I use the CRIO with FPGA Scan interface (together under Labview) to detect my modules CAN, also ok

  3 - then I wanted to see the CAN and analog modules, so I use this page:

  http://digital.NI.com/public.nsf/allkb/0DB7FEF37C26AF85862575C400531690

  And here's my problem:

  with this method I am able to see the two modules with the custom device 'analytical engine and ethercat", which is really nice, BUT, impossible project VeriStand, the error message asking me to turn the chassis using FPGA, but then I lost the analog module...

  So is it possible to run a project Veristand using both Scan and FPGA interface mode?

  Thank you very much

  Hi Vincent,.

  When you tried to implement, you use the procedure described in the following document in the section use of Scan Engine and EtherCAT with NI 986 x custom device modules XNET ?

  From what I remember, because you use a cRIO-9081, you will need to compile an empty bitfile for your target and place the controller in Mode FPGA hybrid mode on your chassis.

  Could you post a screenshot of the error of deployment, you see?

• Scan engine mode on RT does not not with EtherCAT NI 9144 chassis

  Hello

  I have problem with communication of the cRIO-9074 RT with NO 9144 via EtherCAT.
  I add the expansion with a NI 9203 module chassis to my system running on the cRIO-9074.
  I use it in engine scan mode. My PC application communicates with RT by network data stream. When I run only asks to RT, the RT is the reading of variables EtherCAT I/O chassis with no problems, but when I run the PC host application, RT probably go into configuration mode and interrupts communication with chassis EtherCAT - I can see that the LAN LED on expansion chassis stops flashing. "" Then, with still running application I click in the LabVIEW Project Explorer, the item target and select utilities ' Mode Scan Engine "pass back"Switch to active"Configuration, then it starts to communicate. I tried to do the same thing programmatically work with the Scan Engine VI Mode Set but it doesn´t so Runt-time it does not work as well.

  The behavior described above happened when I added the chassis extension in the project and only the module place entries in this chassis are affected, the rest modules 8 places directly in the cRIO-9074 work withou any problem.

  System:

  Professional Win7
  LabVIEW 2013 SP1
  OR-Industrial Communications for EtherCAT 2.7
  OR CompactRIO 13.1

  Hello

  problem solved. The reason was function RT Set Date and TIme.vi what casues on NOR-9144 error and blocked EtherCAT communication. I found that this function is no longer supported in LabVIEW. After the removal of this feature of application of RT, everything works fine.

  BR, Jan

• Connect a cRIO-9081 a cDAQ-9178

  I want to connect a cDAQ-9178 chassis to a cRIO-9081USB port.

  The cRIO-9081 has Windows Embedded 7 on it.  I wrote a LabVIEW FPGA program that is loaded in the cRIO FPGA.  Once started the FPGA, FPGA ignores basically on the side of Windows, very minimal data exchange.

  I want to use the side WIndows to run a program cDAQ.  I have to do it this way because the cRIO has 7 modules inside and the cDAQ has 7 modules.

  Whenever I insert the 14.5 of NOR-DAQmx CD into a CD drive on the cRIO, I see that the cRIO drivers.  How can I get the cDAQ drivers installed?

  I was able to work around the problem by copying the DAXmx on a USB and install from there.

• Error 200220 CRIO 9081 and data acquisition modules

  Hello

  I try to use a CRIO 9081 with NI9206 modules. Max recognize the chassis, but not the module.

  When I try to add an acquisition of data associated with the NI9206 in Veristand, 200220 error message seems.

  I have the solution, finally he was required to add a custom device to search for new engines and detect modules. Then, it is possible to interact with modules.

  Thank you very much for your help!

• Chassis FPGA deployment problem

  Hello!

  I use cRIO 9024 with a voice coil actuator control modules.

  The problem I have is that when I run the FPGA code, he said "the chassis is in programming mode Interface to Scan. In order to run the FPGA screws, you must go to the property page of the chassis, select the FPGA programming mode and deploy settings. »

  So I checked the property, but it has been defined as "FPGA programming Mode. Also when I'm trying to deploy the chassis, I have error message "LabVIEW: (Hex 0x80DF0010) current deployment operation has a missing dependency."

  Since I'm not the one who wrote the code, I have no idea what causes this problem. This code is used for the different game with the same model of cRIO but different modules. I've already replaced modules that I use with those that are necessary for this code.

  Anyone know what is happening here, please?

  Thanks in advance to 1 million.

  Geehoon

  
  

• cDAQ against RIO Ethernet expansion chassis

  Could someone tell me if the NI 9146 Ethernet RIO expansion chassis can be used with Labview on a Windows PC without real-time or FPGA module? He would consider a network device in MAX? The cDAQ-9184 would probably my needs, but I would like the capacity of maximum temperature higher the 9146.

  Hello rdtech,

  You can use the expansion chassis NI 9146 Ethernet RIO with only LabVIEW on a host PC, and you don't need LabVIEW Real-time and FPGA module, however, you must the NI-RIO driver. In addition, the RIO Ethernet would be seen as a network device, that you expect.

  You will use the mode Scan Interface expansion chassis, which is a special configuration of FPGA, which is supplied with the driver that allows to browse through all the channels available on the chassis. This does not require the FPGA module because it is already compiled and included with the driver.

  One thing I want to emphasize is that the coding will be different than using a cDAQ and DAQmx drivers, you rather read individual channels directly instead of creating as DAQmx tasks. If you would like to, you can create a new project and start the host PC code for this system by adding in the 9146 and modules for the project without having them physically on the network

  If you are uncomfortable with the not using the DAQmx driver, I think that the 9146 OR would work well for distributed data acquisition and enjoy higher operating temperature.

  See you soon,.

  Joel

• How can I change the type of chassis in an existing CompactRIO project?

  Hello

  I have a built in LabView 8.2 for a chassis 9101 cRIO. Now, I want to bring to LabView 2009 and use it on a chassis of 9104. I would have thought this should be simple, but there is a VI on the FPGA itself. When you compile, I get the error "the device type that has been set up in this function does not match the actual type of the device. I don't want to have to remove the frame of the project & add it back (losing all the settings it can have) - is there a way just to change the type of target, but keeping the relevant parameters?

  Thanks for any help!

  Dave

  Hi Dave,.

  Once you've practiced it several times it is actually a piece of cake.

  Right click on the project select new target or device

  Rember just to specify rather than the current goal.

  Otherwise, you will have a conflict.

  The new target is initialized to the Ip (0,0,0,0) then re address assignment standard.

  Copy (drag) all the components for the new device (RT & FPGA if included)

  Note it's manual labor rather than you have to 'say' labview what material he must understand!

  concerning

  Xseadog