cDAQ

Similar Questions

• LabVIEW 2014 does support CDAQ 9136

  I use LV 2014 SP1, I wanted to buy CDAQ 9136 Windows controller for one of my projects. I'd like to figure out if I can use the SP1 of 2014 LV with DAQmx15.1 in the program for this controller? User manual CDAQ 9136 does not say anything on the support of LV, just said that DAQmx 15.1 is supported.

  When I tried to add a target CDAQ in SP1 LV2014 with DAQmx15.1, it does not show the CDAQ 9136. I won't use the real time of the CDAQ 9136 version, but I'm confused. Any help would be greatly appreciated.

  

  Nanda,

  I would like to clarify the compatibility for the NOR-9136. It is compatible with DAQmx, starting with DAQmx 15.1. In other words, it can be used as a normal cDAQ chassis in any version of LabVIEW with DAQmx 15.1 or later installed (within reasonable limits). However, compatibility in real-time with the cDAQ-9136 has not introduced before LabVIEW time real 2015 module, which is only compatible with LabVIEW 2015. Thus, to use the cDAQ-9136 as a real-time controller, you will need 2015-LabVIEW and the module time real LabVIEW 2015 or later. This note can be found in DAQmx 15.1 notes for supported devices.

• XNET Signal list control deployed to target RT OR-cDAQ-9133

  I develop a VI to read and record the signals from the engine CAN. One of the requirements is that it will be a stand-alone application which runs on the target device, a device of real-time OR-cDAQ-9133 with a module NI9861. It also has a module analog thermocouple which is read and recorded alongside the CAN signals.

  in any case, I did the front panel so that the user can choose the CAN signals of a drop-down list of all signals in the XNET database and then run the VI to display and record the signals. On the development of PC, it works as expected, I can change the signals before you run the VI.

  When I build and deploy the project I am no longer able to do. The drop-down boxes are grayed out and do not respond to clicks. How to allow the user to choose signals to read and log?

  I've attached a picture to better explain the control of front panel, I have for the user to choose the signals. Nothing complicated just to select the node and right click to create the control. The image is what it looks like on the development of PC, I have not a screen capture of the target device.

  I was able to find a work around. I used an array of enum on the front panel controls that are then wired in a case surrounded by a loop structure for. This generates the signals XNET list based on the table of the enum. Probably not a more elegant solution, but it works and allows the CAN signals to choose in the front panel on the target of RT.

• Impossible to get more than 1 channel to read with DAQmx cDAQ-9172 under Windows 7

  I have the cell load, voltage, and input thermocouple connected to a cDAQ-9172. My sensors entries have been scaled and verified in MAX, and all of them work.  DASYLab 13, the driver is "dcDASY.dll" and the hardware configuration is "NI MAX.

  When I add a task NEITHER-DAQmx Analog Input (that is, a set of scales) it appears correctly. If I add a second channel of the task and select it, I get this message:
  'Channel of task name saved with the module is not available. DASYLab resets the module parameters for usable first channel name task. »
  The name of the task remains the same for each new channel I have Add. If I change the name of the task by using the tab to the drop down menu, it says:
  "You have configured several ways out for the module. If you modify the task, you lose the settings. You want to change the task? »
  Both display the same data channels, and I can't work simultaneously several channels. It seems I missed something obvious, but I can't.

  The parameters are:

  Measurement and Automation Explorer 4.6.1
  NOR-DAQmx 9.0

  Material:-cDAQ-9172
  Slot 1 - NOR 9215 (0-10 Vdc analog voltage)
  Slot 2 - NEITHER 9211 (thermocouple)
  slot 3 - NI 9481 (relay)
  slot 4 - NI 9237 (entry deck w / excitement)
  housing 5 - OR 9402 (DIO)
  slot 6 - NI 9263 (0-10 Vdc output analog)

  Thank you

  You can't perform different tasks (continuous) HERE on a single chassis. The first tasks that starts will be 'the resource booking '.

  Combine the AIs of the various modules in a single task (see photo): start by creating the task of thermocouple. Then add AIs 9237 (e.g. Kraft) and 9215 (volts) using the button with the blue, symbol. Set the mode of synchronization of the task of "continue". Save the task, start DASYLab (second photo).

  Change a task (adding channels, etc.) to the MAX while DASYLab works always, will result in unexpected behavior. To synchronize the configuration of MAX with DASYLab, you will need to close/restart DASYLab or use the 'sync' of the function (see photo 3 "syncmax.jpg"). You can set this function as a shortcut by right-clicking on one of the eight green or grey circle things.

  You should think about an update of the MAX/DAqmx drivers. 9.x is a little outdated.

  Updated at least DAQmx 9.9, better 14.x or 15. 0 (stay far 15 1.x).

• Using instrumented hammer model PCB 086D 50 with the NI9234 module and chassis OR cDAQ 9188

  Hi all

  I need to try to shock with a PCB 086D 50 instrumented hammer hammer. I use the chassis OR cDAQ-9188 with the NI9205 and NI9234 modules. The hammer is connected to the NI9234 and accelerometers are connected to NI9205.

  When I test the modules in SignalExpress I get very good results for the dog, but the accelerometers are ok. Also, if I am controlled the hammer OR Max where I have the option to activate the IEPE the result is ok. In SignalExpress, I couldn't find the option to activate IEPE.

  I have no experience using software, but I started to learn. Does that mean that I need to program the system for my setup in LabVIEW? Also, the installer of the equipment makes sense, the modules that I plugged on the cDAQ can be used simultaneously? Should I have the additional device in order to use the hammer with cDAQ 9188?

  Thank you very much

  Emina

  You can enable IEPE in SignalExpress. Here is a configuration for a single power hammer and three accelerometers a 9234-related.

  

  You don't mention the model for accelerometers. They are also the IEPE sensors? If so, have what conditioning of signals you added before the 9205?

  The Assistant Sound and Vibration (built on SignalExpress) contains an example of Impact Test. The Sound and Vibration Toolkit comes with a sample project for the impact test. With free evaluation period, go ahead and look at how one of these examples is implementing the configuration and the triggered acquisition.

• Cannot acquire with cDAQ in hardware mode timed using DIAdem DAC

  Hi all

  I use DIAdem DAC to acquire the cDAQ + 9225 + 9219. 9219 acquires the use of single point mode that works very well. However, I tried to acquire waveforms 50 kHz 9225 with the file attached dac. However, I found a problem on the block of the clock, as shown below.

  

  How could I solve this problem and gain the waveform with 9225 using DIAdem DAC?

  Sincerely, Kate

  Hello Kate,

  You must connect the NIDAQ-In1 exit the Save block block. In addition, you must change the parameters of the horloge1 block. The material is always measured in mode "DAC-kernel". "The software clock" is used for frequencies of up to 10 kHz clock (depending on the material and the PC). If you want to measure more quickly, you can use the "Clock" mode

  Greetings

  Walter

• Power over Ethernet for cDAQ 913 x (Windows)

  Hi all

  We believe using a cDAQ system to capture and process the images of a GigE camera alongside a few other data acquisition. The camera, we have in mind supports power over ethernet (PoE) we could eliminate the need for an additional power supply of the bulky.

  So, can I use this device with built-in second ethernet port of, say, a cDAQ-9136 (Windows)? I have searched the manual but have not yet found anything...

  Hello pktl2k,

  at the moment our controller do not support the PoE. You can use the Poe injector to power the camera

  Using Power over Ethernet with the hardware OR

• cDAQ and NI 9205 NI9203 NI9225 problem with the detection of modules

  Hello

  We bought a cDAQ-9188 and modules NI 9205 NI9203 NI9225. My problem is that the MAX does not detect these modules.

  The cDAQ must be correctly installed and configured as it is in the list of devices. I checked the monitor of the device is running.

  If anyone knows help me? Thank you

  I've attached a screenshot of NI MAX.

  The reason for this is that the firewall blocks him ports NOR resolved max. by adding exceptions in the firewall

• Difference between the cDAQ-9174 and cDAQ-9178

  I have several cRIO-9081.  Each cRIO-9081 running NOR-DAQmx 15.5.  On four of the cRIO-9018 we show you cDAQ - 9178 with 8 modules.  Everything just worked.  On the fifth cRIO-9018, we tried to connect a cDAQ-9174.  The aircraft appeared in the Windows Device Manager and MAX, but MAX has indicated that the aircraft was missing (error-88705) and that Windows can't find a driver for the instrument.

  We then plugged a cDAQ-9178 in the fifth cRIO and everything just worked.

  What is the difference between a cDAQ-9174 and cDAQ-9178 other than the number of the module support?

  Paul

  Hi Paul,.

  It seems it could be a driver problem! What DAQmx version you have installed on two computers? Reinstall the latest version may be worth it because it looks like there may be corruption. You can find the latest version here: http://www.ni.com/download/ni-daqmx-15.5/5901/en/

  You can manually associate the device driver, here: http://digital.ni.com/public.nsf/allkb/5B80CAAA64413B4C86256C5E0000C1A7

  There are modules connected to the cDAQ chassis?

  Also, sometimes, this can happen if you do not restart your computer after the installation of the NOR-DAQmx driver. Restart your computer after the driver installation will allow you to reserve the device successfully. Here are a few others not to try:

  • Check the charger to device OR to see if it is running
  
  
  • Reset the service OR charger
  
  
  • Reset the MAX Configuration database
  
  
  • The system power cycle

• cDAQ-9263 modules do not allow independent generation of waveform

  I have a client with a cDAQ-9178 crate with two 9263 modules. When it tries to start two independent signals on both modules build tasks, he gets an error in DAQmxWriteAnalogF64:

  device cDAQ1Mod2:-50103: NI Platform Services: the specified resource is reserved. The operation could not be performed as indicated.

  Extended Info:

  Platform AND Services: The specified resource is reserved. The operation could not be performed as indicated.

  Task name: cDAQ1Mod2AO

  State code:-50103

  It seems that it must be a driver bug-usually these "reserved resource" errors occur when you try to validate the task, but it comes from DAQmxWriteAnalogF64. It verifies that he can start two independent signals on two completely independent devices build tasks, but he cannot do it on two modules in his cage.

  Is it a kind of witch-hunt with modules in a box? or a driver bug? He tells me that he has updated the driver until his "last from the website of OR" with no luck.

  Thanks in advance!

  The cDAQ-9178 has only a simple timing analog; output engine You can't have a timed analog output generators of waveforms of the task at a time. Unfortunately, the mistakes of 'the specified resource is reserved' are not more descriptive.

  The call of DAQmxWriteAnalogF64 pushes the task as a 'reserve', which is where he tries to book the timing (and other resources) engine: the first task will succeed, but subsequent AO to the tasks will not be until the first has reserved resources.

  The two tasks are intended to operate simultaneously at the same speed? You can put chains of two modules in the same task by using a string of physicalChannel as cDAQ1Mod1 / ao0:3, cDAQ1Mod2 / ao0:3 with DAQmxCreateAOVoltageChan.

• 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.

  

• How many quadrature encoders may be read together with the cDAQ-9188 chassis?

  We will record position periodically 8 engines (at the same time as we are to the corresponding samples entered analog).  It seems that the 4 built-in counters limited chassis to 4 encoders.  Is this correct?  I am familiar with modules of counter PLC which manage high-speed counting, and then the CPU posts periodically to update the total values.  This is how the NI 9401 card would work?

  Hi jtrout,

  You are right the 4 built-in counters than the cDAQ-9188 chassis 4 encoders.  The following article deals with the use of the NI 9401 card for encoder measures: http://www.ni.com/tutorial/7109/en/.

• How to initialize a cDAQ Ethernet (9188) to autostart?

  Hello

  I have a LabVIEW program that performs tasks DAQmx (pre-configured via NI MAX). The material is a cDAQ-9188, connected directly to the laptop via an Ethernet cable. Both machines have static IPS (same subnet).

  Question

  Whenever we turn on the machines, NI MAX notes that the cDAQ-9188 is reserved and running. However, the C Series modules are reported as Absent (error-88705 code: "the specified device is not present or is not active in the system.) The device cannot be installed on this system, may have been disconnected or may not be installed correctly")

  As a result, the LabVIEW program generates an error, because the physical channels required by the DAQmx tasks are not.

  Workaround

  Each time we spend in the entire system, we're going to MAX OR -> my system-> devices and Interfaces-> devices network-> OR cDAQ-9188 and click "post."

  The test always succeeds and seems to be a sort of boot behind the scenes. After this step, the LabVIEW program works without any problem.

  Questions

  1. This behavior is expected? If this is not the case, what could cause this?
  2. Is there any way to automate this initialization, so that the user does not need to click on "Self test" after each cold start?

  Hi JKSH,

  You can the make a self-test program.

  I wouldn't say that it is an expected behavior. What has helped here, was a repair DAQmx and LabVIEW. But before do you I'll make sure that you have the latest drivers.

• crash of the cDaq 9132

  I have 4 new cDAQ-9132 systems that go into the production thgis week.  During the last two weeks that these systems are running, they break.  Here's what's happening.

  1. the system runs our application, or in some cases, just sitting there running Windows 7

  2 the screen goes black, and there is no further response from the system.  The power light on the controller is running.

  Restart the monitor doesn't do anything, unplug and reinsert the VGA does nothing.  No response from the keyboard at all.

  3 press the RESET button or power cycle using the power button will restart the computer.  Windows error logs have no information at all at the time of the accident, clean everything up to the new entries to the log at startup.

  A strange thing about setting, is that there are very long VGA and USB cables.  16 feet.  Two USB cables go 16 feet each two separate powered USB hubs.  A hub has a touchscreen and keyboard, the other hub has a barcode scanner and a printer.

  Four of these systems have all have the same symptoms.  All four grids have a 9229 and a 9422 of each.

  I set the bios on a USB overcurrent in the operating system report and stay OFF If there is a power failure.  We used a stroke of luck using Min/Max to check the variability on power supply 24VDC used for controller, nothing was found.  The controller has its own dedicated to food.  Due to a quirk of the command, two system have a 24V supply type, the other two systems have a different provider supply.  All the supplies are more than adequate for the controller.

  You can provide any assistance is greatly appreciated!

  Hello Palickar,

  Is it possible to try to launch the cDAQs without long USB cables to exclude them as causes of accidents? If the chassis still crash without long cables USB, then maybe it might have something to do with the way in which power is supplied to the chassis.

  Could you confirm that your installation complies with the section titled "electrical wiring for the cDAQ-9132 OR? :

  http://www.NI.com/PDF/manuals/371801b_02.PDF

• cDAQ 9133 12 "MONITOR WHITE

  cDAQ 9133 race built into windows 7 and a monitor 12 "NOR connected to monitor port is empty after coming out of sleep mode. cDAQ 9133 State seeing a flashing yellow, press reset button, indicator light turns off, monitor indicates reboot and then turns off. OR 12 "monitor power LED blinks green. Press the button has no effect. Monitor remains blank. Must be able to cDAQ turned off, and then to restart windows and monitor to display normally.

  Currently, there is no update of the BIOS for the cDAQ-9133.

  The timer that is documented in the section of the Menu system of the TSM-101 x Series manual is a little misleading: it means actually how long the screen display remains visible after the last button an is pressed.  As you found with your test during the night, monitor screen saver and standby modes depend on the display of the operating system configuration.

  The behavior you have described - the impossibility of recovering the display when power off monitor and turn it back on - is a known issue that is currently under review.  For now, the recommended solution is to configure the display to be always active, just as you did.

• cDAQ-9178 & NI 9401 - ASM: incremental Rotary encoder works is not beyond a certain frequency

  I use a chassis with a NI 9401 DIO module 9178 cDAQ.  I'm trying to convert the output of a rotary incremental encoder ASM (in radians) to rpm.

  Sensing head (PMIS4-20-50-240kHz-TTL24V-Z0-2M-S)

  Snap ring (PMIR7N-20-50-M-20)

  The encoder outputs 2500 pulses per rev (output 5V TTL).  The maximum speed which will see the encoder is 2800 rpm, which is equivalent to 2800 RPM * 2500ppr/60 = 116,667.67 Hz in terms of frequency.

  Since the NI 9401 of the operations specifications:

  Maximum of the input signal switching frequency by the number of input channels, by channel

  8 input channels... 9 MHz
  4 input channels... 16 MHz
  2 input channels... 30 MHz

  I use only 1 channel, so I'm assuming that the 9401 should be more than capable of handling the 116kHz which the ASM encoder is spit.

  Everything works fine until about 2100 RPM (~ 87, 500 Hz) but then I begin to see a drop in rpm, followed by a flattened behavior, then a slight increase. But never more than 2100 RPM.  Our test unit is inspected for other reasons at the moment so I can't produce a plot of the behavior (I can reupload later).  I think this must be a matter of aliasing with the meter or something of the sort.  I have a digital filter set in place with a minimum of 4.0E pulse width - 6.  It is two times smaller than the width of minimum pulse at a frequency of 116kHz (0.0000085714).  I don't think this should have an impact on the calculation.

  Any suggestions? This value of RPM is essential to our application.

  Thanks in advance,

  -MB

  brown_ktr wrote:

  I have a digital filter set in place with a minimum of 4.0E pulse width - 6.  It is two times smaller than the width of minimum pulse at a frequency of 116kHz (0.0000085714).  I don't think this should have an impact on the calculation.

  A 116 kHz frequency, the period is ~8.57 us, but the pulse width half duty cycle of 50%.  Ascent/descent time factor, and it is quite possible that 4 US is too long for your encoder signal.

  The shape of this graph supports this theory, if we consider that there is variation in the exact pulse of each encoder pulse width.  The shortest pulse is ignored when the filter starts to kick in, and the speed of ROTATION increases pulses longer and longer are ignored then as well.

  Try to decrease the minimum pulse of digital filter (US 2 or even 1 US) width and see how it goes.

  Best regards