RIO SB chassis temperature

Similar Questions

• Analysis of resources of RIO PXI chassis

  Hello

  I am trying to find a way to analyze all the resources of RIO in a PXI chassis programmatically.

  In my chassis PXI-1085, there FlexRIOs (7975R), but also the VSTs (5644R and 5646R).

  Using communication NI-VISA, I was able to communicate with all these modules, but only if an Alias is defined in NOR-MAX.

  I have'nt bee able to get RIO associated modules found resource name using 'VISA find resource' VI.

  Also, I have 2 questions:

  -Is it possible to communicate with my modules without defining an Alias in NOR-MAX?

  -How can I get the name of RIO resource programmatically?

  (I could put as an alias of VISA in NOR-MAX the same name as the resource name of RIO but it is very restrictive, the deployment of the application to other configurations)

  Thank you

  I'm guessing a bit here - but is it possible with the System Configuration screws? It's the library/tool box that allows you to get various information about a system (for example cRIOs - installed software) - there is a 'material to find' VI-I suppose you can point to your PXI and it will give you some information?

• 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

• read the temperature of the chassis of a cRIO in Scan Mode?

  I am trying to create a section for monitoring my VI which monitors the status of the cRIO 9022 and backplane (9104) I use. I understood how monitor memory, CPU utilization, and the input power voltage.

  I know that you can monitor the temperature of the chassis using the FPGA options, but I want to keep my cRIO in Scan mode. Is it possible to access the scan mode chassis temperature probe?

  I found the solution I was looking for. NOR has built a VI to get the temperature of the cRIO, but it's not easy to find or in the open air.

  It is located here:

  c:\Program Files\LabVIEW 8.6\examples\CompactRIO\Controller Specific\9022 voltage and temperature Monitor\cRIO-902 x Support files

  "The cRIO-902 x Support Files" is a library that contains 2 VI is used for the sub - VI voltage monitor, and a third VI called "get Council Temperature.vi.

  Drop in the cRIO app and the Vi shows the temperature of the CPU cRIO in ° C card.

• using slots chassis for general use cRIO

  Hello

  I have cRIO-9004 and cRIO-9103 Chassis, labview 2011...

  AFAIK, the cRIO chassis controls its slots if it present any module or not... If someone detect read EEPROM and so on...

  But how can I control the slots on the frame cRIO for my own general use without any module...

  When I create projects, it shows me just like I/O chassis

  * chassis temperature

  * LED FPGA

  * Scan clock

  * Sleep

  * the system reset

  I couldn't write anything of chassis slots and see to the oscilloscope screen, (for example: using a digital or analog output)...

  Didier...

  Try to follow the steps, you will create a new module. As in this example, but skip the part of the circuit.

  http://zone.NI.com/DevZone/CDA/tut/p/ID/7868

• variables of user-defined data transfer

  Hello

  I use the etherCAT 9144 chassis and is only supported by this hardware FIFO range target. After a search, I realized that the only way to transfer data from FPGA to the host by using user-defined variables. But these variables do not support the notion of FIFO. So which is the best practice to transfer data after measures (provable 10 Hz measurement of 15 values) to host VI?

  Thank you

  As mentioned, the 9144 only supports the analytical engine.

  In regards to what you do, it really depends on the entire application. For example, what is the master? Are there other systems at issue here? Etc. It's a good read, in general, although it might not help this second right: http://www.ni.com/white-paper/14151/en/

  A high level, you need to decide what you need. If you have need for deterministic communication, low-latency over long distances from a RT controller, the 9144 is probably the right choice. If you need low latency + streaming over short distances to a RT controller, you should look into the RIO MXI chassis. If you need mainly not deterministic low speed (10 hz) data mixed with low flow continuous over long distances to a windows or host RT, then ethernet expansion rio (9146,7,8,9) is probably the right choice. If you need high speed continuous with low control latency over long distances to a windows or RT host, you need a full cRIO controller. Based on what you've posted so far, its uncertain is the right person.

  Lets say you're stuck with the 9144 for now. As you can easily hit 1 kHz scanning cycles, it should be perfectly possible to data 'stream' to 10 Hz. If you run the scan at 1 kHz engine, then you are 100 x oversampling. Where it gets complicated is this requirement of sync. By default, acquisition input/output is synchronized to the clock of the scan (and you can see when the clock of scan is set by a knot of e/s FPGA). However, you can take complete control of a module in the FPGA and read inputs and outputs at any time if you please. In other words, you can set up so when DIO0 goes high you immediately enjoy all the values of AI 15. You can then transfer these values HAVE switched to the host using the user-defined variables.

• RT or-9148 how to build a distributed measurement system

  Hello!

  I just intend to build such a system, based on the cRIO 9014 and 9148. My problem is that I don't know how to link these two devices by Ethernet. Cannot add the Chassis 9148 to cRIO9014 (it may have a single chassis). All modules IO 9148 Chassis are managed by FPGA and FPGA is to read the data of these modules. How do I send data via Ethernet to another controller cRIO?

  Is there a technical sheet or training touch?

  There is something that I don't know everything.

  Help

  Przemek

  Hi przemmo,

  I think that this tutorial will be useful for you:

  Getting started with the NI 9148 Ethernet RIO expansion chassis

  If you want more details, let me know!

  Gábor

• creation of structures: state machine with controls

  Hello, I wonder if someone can help me with something. I have a sequence, followed by the event structure / while loop.

  someone can help me. I want to create a STATE MACHINE.

  Here's a basic outline of the current structure, I. and this is what I want it to be. I wonder if its possible and how.

  I'm using labview 7.0.

  Thank you

  

  This is what I want?

  

  I looked at your Executive VI.  I don't have an easy way to save in LV 7 now so I'll try to describe in words how I would approach this mess.

  I think it can be done with two loops, a structure of the event, a case structure and not global or local variables.  In fact, there is probably some small business structures and lines inside some of the case, but nothing like as layers of ~ 12 nesting, you're struggling now.

  Look at the design model of producer/consumer (events) as a starting point.

  The loop of producer (event loop) will have the structure of the event.  It will be a case for each control that requires immediate action.  Those that I could identify: get telemetry, side, open Journal printing, abandon, press tank Mode (?) Temp tank (?), Scan, Stop, wait, Step (?) unique, continue and Execute. Most of the buttons must be set on the mechanical action of locking and placed terminals in the case of the event appropriate. So no local population is necessary to reset them.  Those with (?) have no event.  You can have a case of timeout to display Date and time, eliminating which (painful to my eyes) loop.  I don't know about the other stuff in the case of a timeout, but most likely, it is up to the other loop.  If the room 1, 2,... buttons change during trips, they may also need event.  Inside of each event is exactly one element: the Enqueue function.  Create an enum command and make it a typedef. Enqueue this enum value. The queue will be read in the loop of consumer where all the action happens.

  The consumer is your state machine. It has a Dequeue function to get a new order for the structure of the event.  It has several shift registers to transfer data from one case to the other.  These removes your global and local variables.  I'd shift for each of the following registers: the State (typedef enum), cluster of error, temperature (table), pressure (table), results (table), Stat results (table grapes) and a big cluster Indicators_Flags (typedef).  The cluster Indicators_Flags everything that is in the cluster you initialize in the black image sequence (and then never reuse) would have more all indicators except the berries in Maj separate records as well as all your globals and no status indicator, you might need.

  The structure of matter is the heart of the state machine.  All shift registers through it.  It will be the case for what the program does.  Everything in this black initialization setting in about 15 cases of Init.  The while loop to the right of the boot image goes away, but the case inside to become some of the cases of the state machine.  Chassis temperature cycling code goes into 1-3 cases. Mode code pump and read the pressure of your case of timeout event are 1-3 cases.  Code of telemetry: 2 cases.  Print the Page before: 1 case.  Excel code.  Abandonment of code.  Temperature and pressure cycling code of main program: 5-20 cases.  Graphics, record in file: more cases.  Break: 1-2 cases.

  I would like to make a list on paper anyway, you think that you may need and allows to create a typedef enum to control cases.  By making a typedef, it is easy to change without running all over the code looking for the constant in all cases of change.  Enum names will appear on the structure of matter as strings.  Create the loop, shift registers and the structure of the case.  Moving is part of both the original thread can duplicate the case until you have a case for each value in the enumeration of the State.  (Do not use the case of the mark for each value option because it will empty cases that you will then need to wire through.)

  Then copy code from various places in your existing code in the case in the new VI.  Try to avoid copying inhabitants that it will create new controls.  Name bundle to get data in and out of the big bend cluster registry and use ungroup by name.  This provides a free documentation of the data used.

  Check in a month when you have other problems. This will not be a quick fix.  But it will be useful to have a program that works and is easy to manage.

  Lynn

• communication error occurred when the power VI

  Hi all

  I have a frustrating situation.  I am trying to run a few screws on a Compact RIO 9073 chassis, and each time I start or stop the VI, I get two pop-up windows: "Communication Error occurred" (spelling is like on the popup) follow-up by ' WARNING: connection to the target in time real (NOR-cRIO9073 blah blah) has been lost.

  If I then go to the project manager, right-click on the cRIO and select Connect, it connects again very well, and the VI is still running.  I then two same popups again when the VI stops.  In the meantime, I can communicate with the VI without any problem.  I tried to reinstall the software on the RIO to the but minimal, OR RIO 3.4.0 it did not help.

  The RIO I NI-VISA and Visa 4.6 LabVIEW time server real 9.0.1 and NOR-RIO 3.4.0.  Same numbers on the computer except that real-time is 9.0.0.

  Any suggestions would be greatly appreciated!

  See you soon,.

  ~ Ben

  : sigh:

  Never mind, I noticed myself when I realized that my RT versions differed.  (Seems that naming scheme would require a little tweaking si.0.1 is quite different for breaking things...).

  Not sure how I managed to get a version more recent of RT on the box as on the pc, but good.

• What chassis Compact of RIO and the controller to order 3 axes

  I already ordered and received a 9012 (128 MB, DRAM 64) controller and a 9102 (1 M).

  A little logic of digital I/o, 4 encoders high speed read, read slow encoders 1, 3 outputs similar.

  I'm a little afraid I'd run out of space? What do you think.

  Thank you
  Patrick

  Hi Patrick,

  with a background of basket door 3 m, it is possible to implement the 6 complete recommended axes, each race with its own PID regulator. If you use the same PID controller in a loop (which requires a memory management to keep the internal States for each individual axis), it is possible to run 8 axes with a cRIO system.
  In this scenario, there is a ratio of 2.66 axes by 1 million doors. So I doubt that it is possible to implement the three axes of PID controlled with a FPGA 1 million.

  The best solution for your application in terms of price and performance should be the cRIO-9074 OR, which is a bottom of basket with a FPGA 2 million doors and a built-in controller. It is perhaps a good idea to contact your local branch of NOR and check if there is a way to exchange your cRIO system. This should provide enough room for your application.

  Kind regards
  Jochen Klier
  National Instruments

• Lenovo y40-80 temperature

  Hey everyone, I bought a new laptop to y40 - 80 a month ago. So far, I'm pretty happy with it, but I have a few questions about concerns about overheating.

  I have done a few games with it (namely Skyrim) and noticed that the fan gets very hard whenever running on the AMD Radeon GPU. The keyboard and the chassis also get very hot after about an hour (on the left side, where I presume the GPU's). The fan is also strong in general, even when opening things like Chrome and Skype for the first time, but it will usually calm down if I do only light web browsing.

  I used HW Monitor of CPUID to check out some of the internal temperature in the machine. With only a few (mostly inactive) programs, the CPU is averaged at about 39 C.

  During the execution of Skyrim, I noticed that it culminates at 70 C, maybe even more high, although he never exceeded 75 C I can say.

  I can't get the HW monitor to get a read on my GPU. In fact, all of the programs I've tried so far do not seem to support playback of temperature on the GPU - he's going or not appear at all, or it will give me C 511, which I know is impossible.

  I have downloaded the GPU driver directly from the site Web of Radeon, and I'm pretty confident that it is up-to-date, so I don't know what I can do to be able to get an accurate reading on the GPU temp.

  Is this cause for concern, or the y40 - 80 made to withstand these temperatures?

  Thank you.

  Did you try and download GPU - z?

  Time CPU for the games are fine as long as they are below 90 degrees celsius.

  My CPU times are between

  73-79 for Fallout New Vegas (evolving) - 79 max

  Dragon Age Inquisition - max 85 80-85

  75-80 for the shadow of Mordor

  for most other games of the CPU remains within the range of 70 to 75. Inquisition is the most intensive graphics of that game I play.

  Time GPU is generally between 75-85 depending on the game.

  My ambient time are higher at this time (28-30), resulting in these times.

  In short, your times are quite normal.

• 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

• Playback issues of Thermocouples a 9214 in EtherCAT 9144 chassis

  I have an SMU-1078 chassis with an SMU-8135 controller and chassis EtherCAT 9144 with multiple C-modules, including a couple of 9213 9214, running Veristand 2014 and 2014, inertia. I updated last week so I think I have the latest updates for the hardware and software.

  The problem I encounter is that I can read my Type K thermocouples with Thermocouple 9213 modules, but when I connect them to the Thermocouple 9214 module, I see only TC0 change and the rest of the TC 9214 channels are 0 ° c. tried to use high speed and high resolution modes, but no difference. I also moved the module in slot 8 in the EtherCAT chassis, also without success. Then I moved the 9214 with its connector and thermocouples to another machine with a chassis cDAQ in 9188XT and I have read all the thermocouples with NI MAX. This proves that the module is working and that the module connections are good.

  I need to use the 9214 because of his ability to handle the higher common mode voltages. I need help. Please, I beg you.

  Thank you in advance

  Richard

  It ended up that I had to download the last update, 14.0.1 for the NOR-RIO. This solves the problem. I did have to reinstall Veristand, Labview, or any other driver.

  Thank you very much for your answers.

• Problem sending trigger software through backplane PXI (chassis SMU-1082, SMU-6363 DAQ, SMU-6544-HS-DIO)

  Dear community,

  I am trying to implement a background basket (software) PXI trigger on a chassis NI SMU-1082 with LabView 2015 (32-bit) running on an SMU-8135:

  HS-DIO (SMU-6544) in slot 2,

  -Acquisition of data (SMU-6363) into the Groove 4,

  -Flex RIO (SMU-7962R + OR-6583) in the Groove 3.

  The trigger schema is explained in the attached file ' LV-PXItrig-HSDIO-DAQ - overview.jpg ".

  Scenario 1: written DAQ analog signal and sends signals trigger HS-DIO (software) through bottom of basket, after East of waveform of the complete signals to DAQ for acquisition.

  Scenario 2: logical impulse on an external port HS-DIO triggers signals HS-DIO, after HS-DIO waveform is complete DAQ triggered for the acquisition of the ADC by the backplane.

  In principle this breaks down to send a trigger of module A to B by PXI backplane. The SMU-1082 chassis has a bus trip with 8 lines (PXI_trigX, X = 0,..., 7) more a trigger in Star controlled the slot 2.

  I've linked to implement a software trigger, but I can't access the refreshing resource and execution, see the attachment. Other ways of implementation including the DAQmx Terminal / routine disconnect Terminal have not worked for me either. I am aware about the connection of trigger using the node property VISA but I can't make a trigger.

  Tips, comments or solutions are appreciated. Thank you!

  For scenario 1, you want to trigger the HSDIO acquisition to begin as soon as the analog output DAQ starts?  You can use DAQmx Export Signal to send the trigger for the start of one of the lines from the Trig PXI backplane. Then, you need to configure your HSDIO acquisition to use a trigger digital beginning on the same line of trigger. Take a look at the example of the "Dynamic hardware generation start trigger" in the Finder of the example (help > find examples)

  For scenario 2, looks like you do a dynamic unit HSDIO generation when a digital trigger arrives on one of the PFI lines. Once the build is complete, you want to send a trigger for the DAQ hardware to begin sampling. If this is the case, you again use a trigger to start material in your task of NOR-HSDIO, as you did for scenario 1, but use external trig line as the source, rather than the bottom of basket. There is no case of material when the build is finished, but you can use a marker in script mode event instead. The example of the Generation with dynamic event marker' in the example Finder gives a good starting point for this type of operation. You'll want to set the output terminal for the event to be a line of backplane trig, and then tap the DAQmx to start on the same line trig trigger.

• NOR-RIO Patch Nov 2013 on the PXI controller

  Hello

  We use SMU controllers like the LV RT 2012 SP1 8115. We have also a card FlexRIO in the chassis, and we use FIFO write often.

  From what I've read on the November 2013 Patch NOR-RIO (http://digital.ni.com/public.nsf/allkb/95CF25A09DB91FEE86257BE8006193B7?OpenDocument), we should update the systems of RT, but I do not see this option in MAX.

  After you have installed the patch, I have the documents mentioned 12.1.1 with a file mite.cdf inside. But Max, I don't see any updates to the target. I still have a single NOR-RIO mentioned 12.1 which is already installed on the RT system.

  So, how to install this hotfix on the SMU-8115 OR with LV RT 2012 SP1 and 12.1 OR RIO?

  Also strange: when using the OR update service again and expand the updates and Service Packs the Patch OR-RIO reappears in the list of critical updates.

  Thank you

  Daniel

  The component listed in the patch updated is unfortunately a component hidden which is automatically installed when you install your system remotely RIO.  Relocation of the NOR-RIO of MAX component to your remote system should be sufficient to force the patch to apply.

  Note recommended sets of software are not supported under PXI, where is expected.