Use of NOR-9161 & 9215 in SE 2.5

Similar Questions

• I can implement using the NOR-6221 SPI? When I try to generate using ctr0 make an error indicating 'Sample clock' is not a supported option.

  I'm trying to use a NOR-USB-6221 to implement SPI in a C++ application.  When I try to configure a digital output task that uses ctr0 as the clock, I get an error stating that 'Sample clock' is not supported and use instead "on demand".  I would be able to use the NOR-6221 and if so how to do this?  Thank you.

  Hi IntAndTest,

  Maybe silly question: are you sure that you have a USB-6221 and not a USB-6212? The USB-6221 supports clocked DIO, but the USB-6212 is not working.

  A problem with your code: when you specify a terminal DAQmx name, it must be is compared to the device (such as 'Ctr0InternalOutput', "AI/SampleClock" or "PFI0") or contains a slash before the device name (like "/ Dev1/Ctr0InternalOutput", "/ Dev1/AI/SampleClock ', or ' Dev1 / / PFI0"). This does not apply to the names of physical channel (like ' Dev1/port0' or "Dev1/ctr0").

  The error is returned from code that you have not displayed? Your says error message DAQmxCreateDIChan failed, but the code you posted does not call this function. In addition, I don't see a call to DAQmxStartTask or DAQmxWriteDigitalU8, U16, U32, whatever.

  Also, what NOR-DAQmx version are you using?

  Brad

• Jitter in response to signal generator of digital dashboard by using trigger nor tclk with digitizer

  I've written a VI that uses NEITHER tclk to synchronize a generator (PXI-5422 named FGEN1) and a digitizer (PXI-5122 named DIGITIZER1).  There is also a clock card TIMING3 generating a digital camera.

  It seems that can probably be explained by the way TCLK to synchronize, but I don't understand all the details.  Could someone help explain this to me?

  You are right. NOR-TClk ensures that all synchronized devices start at almost at the same time, to the same sample clock, with timing very tight. Sometimes, the level of synchronization with the devices OR TClk-synchronized beats at the level of the synchronization of the instruments of some competitor channels in the same device. But this is not free, there are compromises and added additional jitter for trigger response time is one of them. Here is an attempt to explain why:

  When you use NEITHER-TClk and send a trigger, the devices will respond to relax on the next cycle of the clock once made the trigger signal to the device. Let's say you have several devices all of them even configured with the same clock frequency. You block the signal of PXI_Clk10 using their PLL, so they drift out. But each unit's clock edge will be off, clock +-0.5 cycles. If you send a trigger to each of them, they will respond on the next clock cycle whenever it is, after the arrival of the relaxation to each device with different propagation times, whatever they may be. You get a single clock cycle of jitter on reaction of device to set it off.

  When you use NEITHER-TClk, several things happen: all devices are locked on the PXI_Clk10 signal to eliminate drift. The device clocks are then adjusted to a period level secondary clock. Very very tight. Then a clock signal common, slower called TClk is produced inside the devices. All the generation of trigger are delayed to be sent to the next rising edge TClk, and all consumption trigger is delayed to be received at the next front descending TClk. This way you make sure that propagation delays don't mean one of the devices does not react to the trigger until the next clock cycle.

  That's why you see jitter above the reaction time of relaxation. When you add devices with different clock settings, so the frequency of the TClk can be slower for a divisible frequency in the device clock frequencies everything is possible. This causes the trigger jitter of reaction time be even slower!

  I hope this helps you understand what you see.

• Cannot use the NOR-IMAQdx with 3 USB camera driver

  I have a system WIN7 64-bit I would use with two USB 3 Vision cameras (both are 24UJ003 from The Imaging Source DFK), which works very well with the software IC software. The camera can be opened with IC software but will be visible only with a cadence of 1fps, any size I put it.

  I can open them able and Automation Explorer, but they do not appear under NOR-IMAQdx in the tree.  When I click on the software in MAX tree below, NOR-IMAQdx revealed as being installed (14.5). The camera (and OR) instructions say change the camera driver to that found in C:\Program NIUninstaller Instruments\NI - IMAQdx\Staging\NI USB3 Vision, but my driver is located in C:\Program Files (x 86) \National Instruments\NI - IMAQdx\Staging\NI USB3 Vision.

  Attempts to install the driver displays the following message is displayed:

  "The folder you specified contains a compatible software driver for your device.  If the folder contains a driver, make sure that it is designed to work with Windows for x 64 systems".

  This makes it sound like the driver is in the wrong place or it does not for a 64 bit OS.  Any advice on how to switch them TIS drivers to drivers OR-IMAQdx and also how increase the pace of the second camera would be very much appreciated.

  I tried to connect the cameras individually, and they both have the same performance as when they are connected together (we have good pace, and the other has only 1 fps).

  Are you sure that the camera is Vision compatible USB3? Nothing that I do not see in the marketing material says it is compatible. Is it possible you need a firmware update to make it compatible?

  The installer put IMAQdx driver in the space provided for an x 64 system and he always puts the number of correct bits of the driver down to the system that you have installed. My hunch is that the camera is not to expose a USB3 Vision interface for the driver to bind.

• How will impact using LV 8.5 on my use of NOR-RIO 3.1.0

  I just started using the NI Compact Rio device and while I was installing NOR-RIO 3.1.0 he gave me the message that I really need to use at least LV 8.5.1.  At the moment I am unable to use LV 8.5.1 because I work in a regulated environment and I'm stuck at 8.5 at the moment.  What it will really affect me or I'll probably be OK?  Thanks for any idea that you can provide.

  You should be fine with RIO 3.1 and LabVIEW 8.5. Please note that 3.1.1 is available on our Web site at http://joule.ni.com/nidu/cds/view/p/id/1289/lang/en and you will see in the Readme that passed the version of LabVIEW 8.0 are supported.

  To check the minimum software for your hardware, versions of LabVIEW and RIO see this link:

  FTP://FTP.NI.com/pub/DevZone/tut/crio_software_versions.htm

  Let us know if you have any problems. Don't forget to install RIO after all modules and toolkits.

  Kind regards

  Anna K.

• Need to read a 30, 1.5 a analog input using a NOR-9205

  Problem: I need to read two analog inputs with good resolution using a C-Series card. The two beaches of signal are 0-30 V @ 1.5 and 0-5 V (not sure of the current). I need to be able to read the signal 5V with a precision of mV (or 16-bit resolution).

  I looked at the module-9221, which works very well with the 30V, signal, but does not have enough resolution for the 5V signal. The 9221 is 12 bits on the beach of 60V.

  I looked at the NOR-9205, which works very well with the 5V signal, but it cannot process the higher V 60 signal.

  If a voltage divider circuit comes to mind, but has anyone found a good solution to this (other than to get both modules)?

  Well, the current should not question.  The entrance of the analog device (ideally) should draw no current and everything running on the source will cross the UUT.

  A 4:1 voltage divider should evolve the signal to 9205 AI as long as you do not violate the absolute maximum voltage between a pin of the device and the Earth.

• Use of NOR-8451 talk to TI BQ20Z60-> question address Chip

  I'm working on the product test this chipset use the TI LI-ON "gas gauge".  The chip talk bus smb and chip address 0 x 17.  In order to access some features you need to do a series of Scriptures to register 0 x 77 with the data 0 x 48, followed by a reading of the register 0 x 78.

  I can talk all day to the device using the smb TI-2300 adapter but can't seem to understand the sequence necessary to specify address 0 x 17, then the address of register 0 x 77 & 0 x 78.

  So I guess that the line background question how do you manage the addresses of the chip with the NOR-8451?

  I found the answer.  The chip required a PEC byte at the end.  I had to calculate the CRC and add it to the transaction among other things.

• Can I use a NOR-9244 for measuring single-phase AC 2-wire 480V?

  As the 9244 module is rated for a maximum of 400 v L - N and L - L 800V, to measure 480V, I would need to connect to AI0 AI1 and let the neutral entry floating. Manual outlines all single phase measures referred to the input neutral and has some instructions on the conversion of L - N L - L measures, but it is expressed not bad so I don't know if it tells me that I can directly measure the voltage through AI0 AI1, or not.

  Can anyone confirm that I can make measurements with 9244 cable in this configuration, until I drop the $$$ to buy it?

  Hello MStewart,

  A distinction must be made between Vpk and Vrms.

  @GerdW is correct that the input device is ~ 1000Vpk (997.5Vpk). However, this translates into ~352.6 Vrms

  The side of 800 Vrms for line (L - L) measures is for multiphase applications.

  As you take a single-phase measure, you would use an AIx-neutral (L - N) connection.

  The diagram for this is detailed in figure 12 on page 25 of the Manual:

  <>http://www.NI.com/PDF/manuals/376131b.PDF >

  So to measure above 400Vrms on this unit, you will need to use a power supply external to resign from the tension, as mentioned in the white paper in (specifically the section of voltage):

  <>http://www.NI.com/white-paper/8198/en/ >

  In summary the 9244 cannot directly measure 480Vrms.  You can set before the signal to less than or equal to 400Vrms

  I hope this helps to clarify your question!

  See you soon,.

  -ChristophersonJ

• Which DLL to use for the use of NOR-PCI-6703? (nicaiu.dll or nidaq32.dll)

  Hello! I'm programming ATEasy (from Geotest Inc.). I have to incorporate a Council OR-PCI-6703 and I need the driver for it. I do not know what .dll file to use: nicaiu.dll or nidaq32.dll. What is the difference between these 2 files? What is the best for me to use? Please help me!

  It depends on if you use the traditional DAQ driver or the driver DAQmx. If you use the DAQmx driver you want to use the nicaiu.dll. This link will explain the necessary information to be able to use for your application.

  David has.

• Possible to use labview with daq system not of NOR?

  Hello

  I have a daq system and the software from another company that NEITHER. But I want some changes in the software. If the opportunity was to make a new program with Labview.

  Is it possible to use the old system of data acquisition? Is this compatible with Labview? Or I have to buy new hardware?

  Thank you.

  Hi VIassaks,

  Good afternoon and I hope that your well today.

  Thanks for the post.

  LabVIEW can communicate with 3rd party hardware using the library function call is located in the tip under the functions Palette palette. If your equipment is equipped with a DLL at the driver level LabVIEW can communicate with the hardware. However, you must obtain documentation of the DLL so that you can create your own interface for the material of the part 3.

  Another option would be if the hardware manufacturer provided LabVIEW VIs that control their material. You will not be able to use the screws (National Instruments Data Acquisition DAQ) because these screws use the DLL OR-DAQ, which is our software at the level of the driver for our DAQ cards. Other companies use their own software to the driver level to control their own material. Only the National Instruments hardware uses the NOR-DAQ driver that allows you to use LabVIEW DAQ screws.

  Hope this helps,

• Looking for examples of 9184/9263/9215

  Well, obviously, I flood the forum tonight.

  I've never used NiDAQmx before, so I'm looking for examples of code in CVI for a cDAQ-9184 with AO 9263 module and an AI 9215 module. I imagine that there are examples of code for hardware compatible with different names, but after a quick search using [help] [NOR example Finder] I could not achieve what either.

  Thank you

  9184 chassis has no specific software.

  If you add the 9215 to loss of material select and check "Limit resusts to material", next search for 'analog', you will find a series of examples which can be executed on the module. It goes same for AO module you have.

  

• NOR-8452 Stream Mode more than 64 bit?

  I I hava an ADC SPINNAKER which I want to read using the streams API for high (using the NOR-8452) conversion rate but want to read back all 7 channels ADC in a multiple of SPI read command. The maximum number of bits the stream API seems to bear is 64-bit, where I need to really read about 232 (7 x 32 + 8 for the read command). Is there a way to get around this?

  I use the stream mode to detect a DRDY event, but once a single channel is read the output on the ADC chip is reset (so subsequent interruptions come from only on new data).

  Else seems quite limited.

  David,

  The payload you're trying to broadcast is not a standard for the SPI. We try to follow standards SPI and give you up to 64 bits to broadcast both. If you cannot split your readings at separate readings 64 bit, you will not be able to perform this operation with the 8452. If you had another interface, such as FPGAS, you my power to implement a protocol custom SPI on the FPGA. With 8452, however, you don't have these options.

• Y at - it a new version of NOR-VXI for Linux including Red Hat Enterprise 4?

  We now use the NOR-VXI 2.1 on kernel 2.6.19, it works very well. Now, we try to use on kernel 2.6.20, but it fails to compile the driver for nivxi, it seems not easy to resolve compile errors, do you know if there is a new NO-VXI software released for Linux?

  Thank you

  Huaqing Zhan

  mdsaero,

  According to this article in the knowledge baseon ni.com, our last official kernel that is supported is 2.6.15. This can be updated since you say that you can run on 2.6.19

  I'll check with R & D to see what the latest status of this driver.

  Thank you

• How to trace the temperature and voltage using the graph of Mixed Signal

  Hello

  I use the NOR cDAQ-9178, module NI 9214 (temperature) and the module NI 9201 (voltage). My program allows the user to choose among 3 different tasks, Masurement of temperature, voltage, or both. When you select the task for temperature and voltage measurement, I was drawing all channels on the same graph. I was invited to separate channels of temperature and voltage and draw on a split graph, using the same category axis. I tried stacking, but could not control where each parcel channel went. I think the Mixed Signal graph would work well. Everything works and records all the data of the channels to the files, but my plots appear not on the graph, although I can see the change in scale numbers. I think I can use the cluster incorrectly. Can someone tell me what I am doing wrong? I selected the 'Plot Visible' option, but the plot is not always displayed. I've attached a zip with all the screws needed to run my program. The main VI is "Voltage_Temperature_SingleTask_Measurements_MAIN.vi"... but everything must be downloaded to the program works. Please help... Thank you.

  Hi mzhlb,

  I complained only the expressVIs.

  

  Why not use simple IndexArray function to get bots waveforms of your waveform table? (I faked it your DAQmxRead with functions SigGen).

• Simultaneous sampling using two cards PXI-6562

  Hi all

  I was wondering if it is possible to have two examples of cards PXI-6562 (e/s LVDS high flow) at the same time using the same trigger?

  Thanks in advance,

  Nathan

  Hello

  You can synchronize certainly several MSC devices, including modular instruments to NI HSDIO.  The most effective way to proceed is to use the NOR-TClk synchronization API.  It is provided with several of our drivers of modular instruments and devices, including NOR-HSDIO.  The first part of this knowledge base explains the use of the NOR-TClk functions for that.  This tutorial gives a very thorough introduction timing and synchronization using the API OR-TClk.

  If you are more concerned with programming in fact such a request, I would check the NOR example Finder for some good examples.  "" "" Navigate up to material input and output "modular instruments and devices" NOR-HSDIO "synchronization" to several features of dynamic Acquisition (TClk) .vi

  Jon S