cDAQ against RIO Ethernet expansion chassis

Similar Questions

• 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

• Satellite Pro U300 Expansion Chassis problem

  Hello fellow users.

  I am trying to use an expresscard with my satellite pro expansion chassis. Problem is that in Device Manager, I am getting error code 12 for PCI bridges in the chassis and the error code 31 for the PCI bridge on the card I want to use in the expansion chassis.

  I installed latest version of the BIOS but cannot solve the problem.

  Slot for Express card in my computer is fine because I use an Ethernet Express of 1 card G without problem.

  Hunting on the web, it seems that the problem is related to the BIOS being unable to handle the number of PCI bus in the system, refer to the knowledge base article 942959 Microsoft. This article explains the problem and how to Vista and W2008 reslove.

  I am running XP and work around, that they said, does not work. Upgrading to Vista is not really an option as software I want to use is not yet the version for Vista.

  My only options left at this stage are fresh install XP to see if it corrects the problem, or vista fresh install and hope I want to use drivers/software works under Vista.

  Has anyone else seen this problem, got any other suggestions.

  Thank you very much

  Hello

  your problem is unusual, but what I want to know is: which model / manufacturer, what is this expansion chassis?
  It would be interesting since without knowing what we´re talking expansion chassis, it would be difficult to know where exactly the problem could be...

  Greetings

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

  Our installation program runs VeriStand on a chassis 9081 cRIO using a FPGA personality. We wanted to add an ethercat expansion chassis 9144 to the system. Don't support the cRIO and expansion mode personality FPGA chassis runing VeriStand? I can't find much information about it, other than runing the system using the analytical engine.

  Initially, we tried to run our system uisng the analytical engine add on, but the system had problems with the NI 9213 16 Ch thermocouple card. If one of the inputs is open it read the rest of the channels open. For example, if channel 5 is open, the remainging channels 6 to 16 would also read as at the opening. For this reason, we configure an FPGA personality to read inputs and outputs.

  Thank you

  You can do it. But you need to compile the FPGA in a hybrid mode:

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

• No reconoce cDAQ-9188 via ethernet

  Hola Amigos

  Tengo el problema of Quebec able & Automation, me reconoce el chassis cDAQ-9188, pero no sus modulos he intentado todo lo, that will be replaced by Recomiendan en sesion http://digital.ni.com/public.nsf/allkb/DF65FCF0DD20D71686257949007ECAA7 pero esta no obtengo resultados positivos, alguien could orientarme...

  Lo agradeceria muchisimo

  PD: Editor lo me appears

  Hi pomontty,

  CDAQ networked systems requires a host booking, to avoid conflicts where multiple hosts on the network could attempt to access modules at the same time.  For this reason, you don't have access to your modules until you have selected the reserve chassis from the top of the window in the right-click menu or MAX on your device in the devices tree.  You cannot also self-test or reset the chassis when you have not booked, which is why you see the error that you have set.

• problem running example project USRP FPGA connected via Ethernet

  Hello

  I am trying to run the example project of USRP FPGA on a USRP-2940R connected to a PC windows using Ethernet. I have not made any changes to the FPGA VI or screw host and I'm tryign to run the host Rx in Streaming, VI. I get the error-63180 function Open Bitfile dynamic reference (called from the VI open device), with a possible reason for "the specified resource name is a reserved word or an invalid alias. Alias of RIO can only contain alphanumeric characters, '-' and '_ '. I specified an IP (192.168.10.2) for entry of address of device to function. I guess the address of the device is the problem. This who should I be specifying the address of device in this case. Any help would be greatly appreciated.

  Jerry

  jerrysydir wrote:

  The restriction you mentioned is specific to the USRP platform? The website NOR talk using Labview FPGA with a RIO Ethernet expansion chassis.  (http://www.ni.com/tutorial/11703/en/).

  LabVIEW FPGA on Ethernet is only available through LabVIEW RT. Behind the scenes of the target is still connected to the well RT via PCIe controller and then the RT controller is connected to the host via Ethernet. There are also some USB LabVIEW FPGA targets (http://www.ni.com/white-paper/14821/en/).

  For the RIO USRP, MXIe is currently the only bus taken in charge for LabVIEW FPGA.

• NOR does still cRIOs based on Windows?

  Hello

  I have a customer who wants only a small embedded PC that does the following:

  • Acquire data through a system of 3 rd-party over TCP and store them on disk
  • Show a video stream (and capture photos) a GigE camera
  • Drive a servo motor 2 axes
  • Launch the Windows 3 rd-party software

  The only part of the system that must be in real-time is the motor controller. It is also the only part that needs physical i/o; everything meets with your PC via TCP.

  The PC and other equipment must be installed in an industrial portable to take to different mining sites. The customer is happy to provide an external monitor, keyboard, and mouse.

  I thought that a chassis cRIO running Windows would be perfect for this job. The FPGA could drive the motor and check the limit switches, while the side Windows would do the rest (save data, capture videos images via IMAQdx, run the software 3 rd-party). However, only focused cRIOs on windows, that I could find are the cRIO-9081 and cRIO-9082, which are considered to be 'old' and have too much C-series slots. OR recommend the NOR-9039 instead of the cRIO-908 x, which does not support Windows...

  Issues related to the:

  1. Is it possible to run Windows on a non-traditional cRIO, 4 slots?
  2. Can you think of an alternative solution to meet the needs of my client? I have considered the following:
     • A system PXI, but which does not fit in the box.
     • A touchscreen computers for the part Windows + a cRIO RT separate to drive the engine, but the box has no space for a touchscreen.
     • A mini PC for the part Windows + a cRIO RT separate to drive the motor, but I'm not sure of the strength of the mini PC.
     • A cDAQ for the part Windows controller + a cRIO RT separate to drive the motor. It's possible, but wastes a lot of locations of the C series.
     • A controller cDAQ to make, but I don't know if Windows can handle fine motor skills.

  Any ideas would be very appreciated. Thank you!

  All course cRIOs use Linux RT.

  You should probably have a look at the CVS-1458.  It is an on-board with GigE Vision system built in.  There is a version of Windows Embedded 7.

  You can also consider a 9147 OR for the motor control.  It is officially called an Ethernet expansion chassis, but Windows can communicate directly with it using something a bit like shared variables.  This chassis is just an FPGA (no RT).

• Run vi without connected targets

  I added two targets in my project. A cRIO and an Ethernet expansion chassis.

  When they are turned on and connected to the network, I can run my vi in 'My Computer'.

  How can I feed my vi if they are not activated?

  I need to remove the project when I don't have access to them?

  

  Any code that references a VI on the missing target will cause your VI of does not work.  Its kinda like having a single target system and you try to run a VI after have 'removed' (deletion) one of the screws under it is.

  However, you certainly code peut launch a project that does not reference the lack of targeting.  For example, my real-time project includes several analysis routines that run on the host computer (including generate them Configuration file).  These will work fine, as well in development Mode and in compiled Mode, with my remote system is disabled (or otherwise not connected).

  Bob Schor

• How to 'book' an Ethernet cDAQ chassis based in software without using MAX?

  I am using a cDAQ 9188 with Ethernet interface. It works fine, but the Setup is a little more than I like for end-users. Users are all first go to MAX and do make a connection. After that, users must 'reserve' the chassis to ensure access to it. This isn't a problem except that I still have to find a way to make the code G. I have rather not in my documentation would include a series of steps require that the user enter MAX whenever they want to turn on the system. I would have preferred it is comparable to a USB DAQ experience where it works.

  All the examples there or suggest on properties, methods or screws to use for my situation?

  You'll want to use the DAQmx reserve Network Device.vi, under measures of e / s-> DAQmx--> DAQmx advanced-> configuration of the data acquisition system.

  

• data delays cDAQ-9184 HAVE AO

  Hello

  I 9184 cDAQ chassis with two modules installed: NEITHER 9215 (HAVE) and NI 9263 (AO).

  AO generates the signal of 5 kHz and bought it. Initially, all right, but after 20-30 seconds, it has delays (up to 30 seconds!) between the production and acquisition.

  Time lag depends on the speed of the DAC. If it 20 * 5000 = 100 kHz, delay = 15 sec, if it 10 * 5000 = 50 kHz, the delay is 30 sec.

  It works with the PCI - DAQ version, but I do not understand why he has these delays with ethernet chassis.

  I tested it on gigabit ethernet with chassis directly connected to the host. But I don't think that problem is on a network, because the net charge is 0.55% and ~ 1Mb\s data transfer. The processor is also low.

  And I think evil isn't in the generation, acquisition, as it evacuates all samples in buffer (number per channel in DAQmx read nearby 'availsamplesperchan') and because changing CAD rate influence on signal updates.

  In addition, it works fine without these big delays to signal lower rates, for example, sine wave 50 Hz generating.

  Example of code is to join. I read 100 times of 5 kHz sinusoid, 16 points per period (refresh rate = 80kHz, 1600samples). And 5 kHz sine generation of 100 periods with 20 points per period (rate is 100 kHz, 2000samples).

  

  Now, this works in two separate loops with the control "TotalSampPerChanGenerated".

  Problem was with a buffer too small mailing to cDAQ. 8 k samples and 4 caching works pretty stable buffers.

  Also, I checked the difference between 'CurrWritePos' & 'TotalSampPerChanGenerated' and the maximum value is 1 500 000. 1 sample is it DBL, it really means that the buffer size is 1.5 M * 8 bytes = 12 MB.

  Thanks for the thread.

• NEITHER 9219 fully supported on the RIO MXI-Express?

  I'm trying to choose for my RIO MXI-Express chassis cRIO modules and I fell on the NI 9219 universal module.  While reading the user guide, I noticed that it is said in two separate sections as the 'Digital mode' and "Mode of Contact open' is 'supported only in CompactRIO systems." As I don't have the actual hardware for me to test, I created a LabVIEW project using the FPGA Wizard and he had to instantiate a chassis of RIO MXI-Express (NI 9159) connected directly under 'my computer '.  I then load a NI 9219 module and set 0 "Digital In" mode and Channel 1 channel mode "open Contact".   After that I dragged & filed two channel nodes in my block diagram and I was happy to see that the LabVIEW compiler thinks that everything is OK.

  So my question is, whenever I read "is supported only on the CompactRIO systems" does also include MXI-Express RIO systems as well?  If so, it seems that some documentation for cRIO modules should be updated.

  NEITHER 9219 plug: http://sine.ni.com/nips/cds/view/p/lang/en/nid/208789

  NI 9219 user guide: http://www.ni.com/pdf/manuals/374473e.pdf

  Thank you

  Hi SeanDonner,

  Yes, the RIO MXI-Express is deemed part of the cRIO system.  In addition, for lovers of the future forum, the chassis Ethernet RIO and EtherCAT RIO are also part of the cRIO system.

• 1458RT CVS with 9144 chassis ethercat

  Hello

  I want to use a chassis with a CVS 1458RT EtherCAT. I'll have to dedicated to one of the three gige ports (1/3) to communicate with the 9144 chassis? Therefore 1 for my camera, 1 for gigE plant LAN and 1 for chassis EtherCAT?

  I know there are EtherCAT drive, I work with Allen Bradley, so I think to use a 9263 and a 9411 for analog player. Could you confirm that I will be able to control the analog output of the CVS at the EtherCAT frame to 4ms?

  Thank you

  Patrick

  As mentioned, you should be able to be in the 4 DC, you need. I will recommend you don't not to lower the engine of 1 ms... Also, you should be able to control the etherCAT carefree expansion chassis. However, you should be aware of the limits of the EtherCAT frame.

  This document is very useful:

  http://www.NI.com/white-paper/10555/en/

  You should also be aware that this chassis does not support interactive execution and only allows the use of the network variables. Also be aware that you must create the file bit FPGA and LabVIEW project deployment.

• 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

• I want to run an engine using the FPGA card 7851r 9474 C Rio 9151 pilot control is possible or can I do in LABVIEW, CVI

  Hello I want to run a Stepper with 7851 FPGA R card with driver 9474 crio chasis, but I'm not able to understand how to proceed. Or may choose this option by using view lab CVI

  Hi VHS.

  first of all, I would recommend that you want to use materials. Basically, to control a stepper motor, you have a controller of axes and a player.

  In fact I don't know why you want to use 7851 R card and cSeries 9474 module. In any case, you can connect the FPGA Board with an NI 9151 expansion chassis for

  Plug the 9474.

  In the following link, you will find basic concepts on control of engines with NO motion:

  Motion Control fundamentals

  http://www.NI.com/white-paper/3367/en

  In addition, you need a software application. NEITHER offers LabVIEW - graphical programming and LabWindows CVI language - it is a system of development in C-ANSCI

  for C programming.

  Kind regards

  RupiDo

• Installed windows 7, but the yellow mark! on Ethernet, network and video controller

  Dear,

  I installed the new windows 7 on my HP laptop, Mini. But there is yellow! panels against the Ethernet controller, network controller, and video controller under Device Manager. I can't access the internet.

  For these three hardware ID is:

  PCI\VEN_10EC & DEV_8136 & SUBSYS_3594103C & REV_05\4 & 7A 53824 & 0 & 00E0
  PCI\VEN_1814 & DEV_5390 & SUBSYS_1636103C & REV_00\4 & 7F2283C & 0 & 00E1
  PCI\VEN_8086 & DEV_A012 & SUBSYS_3594103C & REV_00\3 & 33FD14CA & 0 & 11

  Please help solve the problem.

  Thank you.

  You are the very welcome.

  Here are links to the drivers you need in the order you posted the material ID's

  http://h10025.www1.HP.com/ewfrf/wc/softwareDownloadIndex?softwareitem=ob-95247-1&cc=us&DLC=en&LC=en&OS=4062&product=5173007&sw_lang=

  http://h10025.www1.HP.com/ewfrf/wc/softwareDownloadIndex?softwareitem=ob-111718-1&cc=us&DLC=en&LC=en&OS=4062&product=5173007&sw_lang=

  http://h10025.www1.HP.com/ewfrf/wc/softwareDownloadIndex?softwareitem=ob-95476-1&cc=us&DLC=en&LC=en&OS=4062&product=5173007&sw_lang=