PXI-6251 vs pxi-6221 - tall order?

I write code LabVIEW and TestStand to a certain number of test devices.  Some of the devices have PXI-6251 daq cards, and some have maps daq, PXI-6221.  These cards have very similar characteristics, and the stitching of the connections of e/s is nearly identical.  They * are * identical with respect to the signals that I care.

So the system has a NI PXI-6221 data acquisition.  System B has a daq, PXI-6251.  I have 10 k potentiometers wiper connected to AI2 on maps, while the ends of the pots are connected to the + 5v and ground.  Very simple analog test input.

Right click on the chart-> measure of e / s-> NI - DAQmx-> DAQ help.  Place the DAQ help on the diagram.  Configure for analog input voltage, ai2,-1v to + 6v.

I run a bunch of samples, and the daq cards read tensions.  I can see them change as I adjust the pot.  Works very well.

The problem is that a such VI built on system don't work on system B, and vice versa.  When the express VI creates, he knows the current material and makes the appropriate adjustments.

Is it possible to write screws that can be portable between systems A and B?  Is it possible in 'building block' these express screws?

Thanks for your suggestions.

-Mark

Hi Mark,

The same express VI should work as long as devices have the same name able and Automation Explorer.  The 6251 has some features not supported by the 6221 (analog trigger, faster sampling rate), but as long as you don't use these should not be a problem.

That said, you can switch to the lower level API of DAQmx to give control of frontage on the device that you select this option to run your task.

Some examples of use of the DAQmx API:

Analog acquisition continues with a Timing Software

Analog acquisition continues with internal clock

To sum up, one of the two approaches should work:

  1. Rename the measurement and Automation Explorer unit so that it is always the same (for example ' Dev1').  You should be able to use the DAQ Assistant even this way.
  2. Use the DAQmx API rather than the DAQ Assistant.  The user would then select the channel in a drop down menu on the front panel.

The option can be done programmatically as well:

  1. You can rename the features of programming using the API of System Configuration with DAQmx 9.2 or later.
  2. You can use a node of system DAQmx property to query the devices that are present in the system and the information on these devices (see example).  You will use this device name to programmatically build your channel name (e.g. 'Dev1' + ' / ai0 ' = "Dev1/ai0").

It is probably easier to use the DAQmx API rather than the DAQ Assistant for your case (except if you're OK with manually rename MAX devices or enter the DAQ Assistant each time to reconfigure your specific device name).  If you want the user to select the device in a drop-down menu, then you can probably just use a direct navigation example.  If you want to programmatically generate the name of the channel, then you can use the node property system DAQmx to see what is called the unit and go from there.

Best regards

Tags: NI Hardware

Similar Questions

  • Change in gain on the PXI-6221

    Hi all

    I apologize in advance for a newbee question. I recently started to work on the measurement of force in the laboratory of fluid mechanics. We got a load cell 3 - axis with 0.5 mV/V, power per channel, which I hung on SG24, which sits on SC-2345, connected to the PXI-6221.

    As far as I understand, after the signal comes out SG24 unit, it is amplified to 500mV and powered to PXI card, which in turn have 4 possible gains of 0.2V, 1V, 5V, 10V. To keep the resolution as fine as possible, I'd be interested take a +/-200mV gain, which in turn cut my signal more then half but keep a resolution ~ 6.1uV, I like not having the range, my forces expected fall shorter reach.

    The problem is that I can't find neither manual or MAX a way how truly change the gain. If I open MAX > NOR-DAQmx devices > PXI-6221, I see no possibility to change the input voltage. I can see +/-10V in the Test Panel, but if I change to +/-200 m it resets at + /-10, after I close and reopen again.

    Can someone help please on this issue?

    Thanks in advance

    Hi Chris,

    You made my day )

    Thanks a bunch!

  • PXI-1033 not detected until the pc is rebooted

    We have a chassis NI PXI-1033 with a PXI-5114 and PXI-4072-PXI-6221, fist, that he had failed to recognize and install drivers for motherboards. The search in the knowledge base, I tried workaround by disabling the PCIe mode ' bcdedit/set pciexpress forcedisable' command and rebooted the pc. Then the system recognized and installed the drivers for all the hardware.

    Disabled the PXI system at the end of the day. The next day, after activating the system, he did not recognize the hardware, returned changes to aid 'bcdedit/set pciexpress by default', then restarted the pc. Once again the material have been recognized.

    I tried to change the configuration on the PC BIOS, without success. The PC is an ACP-4000 of Advantech. We need to restart PC after a cold start so he could recognize the hardware and load drivers.

    Is this normal?

    Concerning

    The PC is under Windows 7 Pro. I searched on google for similar problems, where I found one where someone said that the culprit is that the chipset of the motherboard not give not the PCIe card delay what he needs on a start cold in order to be recognized. A reboot gives the time required and the card works.

  • Can not use the card PXI controlling SCXI for something else

    Hi all

    We have a hybrid chassis of 1052 with a PXI-6221 (control of the special SCXI version) into the slot of the 8th and, while it allows us to access map of the SCXI-1540 module without problem, if I try to add the NI PXI-6221 to the list of data acquisition cards to read the definition of system files or I make reference to any channel in a task of analog input (custom device) it is telling me that the resource is reserved. When I list the card in the system definition file, it gives the error message even if I turn off the single-point support timed by the hardware.

    I went back to the documentation for the Web site and I couldn't find a place where it says you need a card PXI for controlling SCXI cards but that the PXI card controls became useless.

    I'm doing something wrong?

    Thank you.

    Dear Claudio_G,

    That should really be a limitation in VS2011 because there are future news added since VS2011.

    And the reason why it works in the custom device could be the one custom unit as PXI6221 and SCXI1540 are separated internally in which the task and VS that it works in the same task.

    Then when it works properly in the custom device I recommend to use this way or other wise update to VS2013.

    Kind regards

    Oleg Scherling, mengg | Engineering applications. National Instruments | NIG. |

  • withdrawal of a th ack PXI module

    I need to send some PXI modules for calibration but am unable to get off the PXI rack PXI modules and rather

    to force these and potentially break.

    I googled for how to remove the PXI modules, but unfortunately, I can only find online information about how to install the PXI modules.

    Can someone send me a link to any documentation OR how to uninstall the PXI modules from a PXI square?

    Thank you

    Too bad...

    I just found out that National Instruments skillfully hid a mounting screws out of sight under the level of edjector

    and then took the trouble of this document anywhere on how to remove a PXI module in order to improve the

    customer experience.

    ...

  • Derives from the system time when calling OR-Motion screw on PXI controllers

    Hello

    Just an email to avoid others wasting time when they are facing in this fantasy bug:

    We use PXI systems with Controllers NI PXI running Windows 7 and the 7340 family cards (PXI-7344). We have noticed that when the calls when it's through screws OR-Motion to question the different registers of the State (e.g. position, ADC value, general axis or the reference state) axis, the (Windows) system clock runs FASTER either. OR-Motion calls most are performed per second, faster windows clock works. When you get into the status for 4 axes 10 times per second (lines 100 ms rate), the drift is greater than 5%!

    I include here an example of program that reproduces this behavior.

    It is an essential question, for example if save you data with or from the timestamps, and it gets even worse if Windows is configured to periodically synchronize its own clock to a server via the NTP Protocol (it's how we noticed this problem in the first place). In this case, you see large discontinuities in your data every once in a while. Our systems must be running automatically and record data continuously throughout the year, so this bug is a real challenge.

    People at NOR been able to reproduce this bug too and are working on it (no idea of any CAR # yet). Note that this problem has not been seen on a DC non - OR Office running Windows 7 64 bit...

    The exact configuration is the following:

    Chassis PXI-1036

    PXI-8101 (or PXI-8102 on another system) controller

    4 PXI-7340 axes into the Groove 4, no physical connection for this test

    (PXI-6221 in slot 2, not used in this sample program)

    Windows 7 Enterprise SP1 32-bit English

    LabVIEW 2011 SP1 32-bit English

    OR-Motion 8.3

    2.6.2 PXI platform services

    (all software OR additional distribution 2012 DS1)

    Controller BIOS: improved 1.3.1 to 2.0.1f0, problem given the two versions of the BIOS

    I'll try to post here as soon as we receive news of NEITHER.

    Kind regards

    Vincent

    Hi all

    I wanted to let you know that the driver OR Motion 8.4 coming should solve this problem.

    Best regards

  • PXI-6527 digital i/o ports does not

    I couldn't get my two PXI-6527 work.

    In MAX, my devices are recognized, they pass the self test, and I can set high or low output on a specific port and a line on the PXI-6527 using the test Panel. When I take a measure to that line, say-5,7 to + 5.7 (port 5, line 7), I do not read any voltage. I tried the same thing by using one of the digital outputs LabView examples, without a bit of luck. I tried several different ports and lines on maps two PXI-6527.

    When I measure the PIN "GND" to the "+ 5V" pine, I read 5V on my multimeter.

    I have several other DAQ with e/s digital equipment on them (PXI-6025E, PXI-6704, PXI-6221), and I managed to create on the digital I/o output voltages.

    Y at - it something that I do bring my digital output signals to PXI-6527 maps.

    Hey Jake,

    The output of a device 6527 channels are static relays with a LED and two MOSFETS connected together to form a two-way switch. The output channels will not output a TTL 5 V signal without providing an external source. Using the V + 5 of unit 6527 line allows you to use it as a TTL level with power not isolated output device. See sections 3-10, 3-11 6527 user manual as a reference for the above information.

    Thanks for choosing National instruments.

    Kind regards

    Glenn

    Technical sales engineer

    National Instruments

  • Delay between angle and entered analog on a 6221

    Hello

    my test setup consists of a (8184 current run LabVIEW RT) embedded PXI controller which uses a PXI-6221 of data acquisition. One of the outputs analog of the 6221 creates a demand for speed that is sent to a servo controller. the servo drives then the test configuration. Between the servo and the remaining test configuration, a quadrature encoder is located. Both the 6221 meters are used to measure the position of the servo (using the trains of pulses A and B) as well as the speed of the servo (frequency of A pulse train). In addition to these counter inputs, some analog inputs of the 6221 serve as well to recored the configuration of test signals.

    In this configuration, one of the analog signal has a frequency of n periods per revolution of servo (determined by the mechanical design of the test facility). But when I leave the servo turn to for example 100 rpm, then decelerate from status quo with a constant deceleration and then draw the analog signal against the measured angle, I see clearly that as long as the speed is telling, I n periods per turn (or a passage from my analog AC to zero each 1/2n towers); However, as soon as the slowdown begins, the plot gets stretched along the axis of the angle (so the plot tells me there are less than n analog periods per turn, which is impossible because it would require the mechanical destruction of the facility).
    However, I can calculate a position based on speed information signal, as I got to the second counter (by integration of the speed). When I do this for the above velocity profile and draw the analog signal against the calculated angle, I see exactly n times / revolution, no matter how fast the installation program is rotating (just the expected behavior).

    So, apparently, the speed measured is "in phase" with analog signals, while the measured angle has a "phase error. Draw the angles measured and calculated against the time tells me the same thing: the measured angle is always late (compared to the calculated angle). The period is not constant throughout the measurement; I've seen values between 30 and 170 ms within a single record. Due to this change of variable, inserting a delay for all channels, but the angle is not a great idea.

    Unfortunately, calculation of the position of the speed signal is no option for me, because the direction of rotation is changed during measurement; because speed information I have based simply on a frequency of pulse train, it contains no information management, therefore a calculated position would be unaware of the changes of direction.

    Does anyone have an idea whence thios delay and what I can do to fix this problem?
    Try a position different methods of decoding or exchanging the meter channels has not made a difference.

    Thank you!

    Hey Kevin,

    attached you will find the last block diagram (no new translation this time, since no changes have been made that require a), which includes your last suggestions (explicitly start the task of AI, remove the excess constraints) with a flat sequence structure that applies all the preparations of task to finish before the start of the first task (I know I could have achieved the same effect of intelligent routing of the signal error, but I think the code is) better readable this way).

    Without OPI, LabVIEW tends to start to have, ao and tasks of the angle of the very different moments, which (for some reason that I don't understand - we have a sample clock based calendar here, and the sample clock is run, well after the three mentioned tasks...) tends to cause delays in the order of several 10-100 ms between tasks. With the structure, this problem is eliminated.

    The Sub - VI just above DAQmx writing contains the "conduct" code that I used in the last screen shot to "serialize" the requested speeds - in this way, the table that contains the requirements of speed does not need to be rebuilt.

    The code that creates a weather channel frequency implicitly timed measure left the VI shown here in a second VI that is running on the host computer, because everything that involves a calculation and does not require any intzeraction with the DAQ hardware is better placed there (the 850 MHz on the PXI controller celeton is slower than 2 definitiely something host GHz Dual-Core system).

    The behavior you mentioned for the task "not started" HERE is what wrote using LabVIEW. I thought the block of relaxation that I had at the beginning would treat the start of the task - at least, the code like this figure repeatedly in the examples that come with LabVIEW.

    I don't really understand what has caused the problems I've had - it seems that it was the combination of the measure quickly loop iteration with the start of task based on trigger HERE, but I do not understand what are the mechanisms in the background caused the problem (too forced loop was not the cause; the same block diagram works well with an additional loop timer).

    If the solution was composed of the following steps:

    -remove the old code calculating speed, replace it with a better code out of the main loop. This allows to

    -reduce considerably the frequency of the main loop.

    -Pull the DAQmx writing out of the loop, and

    s ' ensure that all tasks are started explicitly just before the main loop starts to run.

    -Possibly remove excess constraints of the main loop.

  • low Harmonic frequencies in the signal strength

    Hi all

    I try to know what are the causes of noise in my signal, whether it's a faulty hardware or my lack of knowledge.

    The system that I'm actually consist of two engines not to not (parker HV232) that provide the uprising due to frost harmonic + pitch motion with phase shift of 90 degrees (a kind of movement of fish tail beat). I have a load cell 3 - axes attached to the shaft of the motor, pitch, and it measures up, drag and torque on a plateau which oscillates in the tunnel water (oscillation is provided by these two Steps). Tunnel to provide the incoming stream.

    Signals of strength are captured through SG-23 + PXI-6221 daq card, I put the gain on the last of them to +/-200 mV for better resolution.

    When the engines are turned off, the noise level on the static signal is the threshold of resolution, and nothing strange is not shown in the signal, and its ghosts.

    The problems begin when I initialize the motion on the steppers, FFT of the watch signal of the low frequency spikes that are exact multiplies the frequency of oscillation, I have attached a PDF for example.

    Disengage amplifier/filter which was suggested by manufacturing, and suspect I have observed could be due to this I'm not sure at 100%. The VI I use filter band-pass data in the 0.2 to 6 Hz, but somehow I can still see noise beyond 6 Hz.

    I was wandering perhaps someone has experience with similar issues and can suggest a solution on how to get rid of these harmonics.

    Thanks in advance

    I'm not an expert in the dynamics of the tunnel, but from what you say, it looks like they can't be noise but components generated due to the rotation of a mechanical Assembly. Normally people refer to these harmonics in the form of 'order', which means that they are a multiple of the frequency of rotation.

    So maybe it's the attacker

    1. check by an expert (the one that includes the mechanical system that you are using) that to the point where you measure the force will not get the components of the order.

    2. understand what exactly is the measurand. What exactly do you want to do with the measured signal (RMS, FFT etc..) Then you will be able to figureout if components of the order may affect your measurement.

    Oleks wrote:

    Disengage amplifier/filter which was suggested by manufacturing, and suspect I have observed could be due to this I'm not sure at 100%. The VI I use filter band-pass data in the 0.2 to 6 Hz, but somehow I can still see noise beyond 6 Hz.

    During filtration, the attenuation in the band determines how fast the signals will be thinning of the hard shoulder.

  • SCC-FT01 definition for external trigger

    Hello

    I currently hit the wall with this little device, SCC-FT01, who told me can accomplish my task. What I need to do is to send TTL(0-5V) a signal square Imaging via a BNC cable system in order to start recording.

    My facility includes sc-2345 carrier and map DAQ, PXI-6221, I think it's type M.

    I followed manual & quick start guide of the FT01 and put the wiring according to her, unity in itself is in the slot of J10. But when I connect to a voltmetter to what I read 0V. My guess is that I need somehow 'set up' 1 of 7 bit for output to allow FT mode generate signal. Unfortunately I can't find details on how to actually do. Article "knowledge base" on this topic is not very useful.

    If someone with practical experience with this unit for similar task can help, I would be very happy.

    Thanks in advance

    Apparently, it was really easy to code, I was stupid problem solved!

  • readings of Veristand instruments with a remote system

    I'm new to the National Instruments and Veristand material and I'm trying to use an instrument with Veristand to see if I can get readings of this instrument. I use a PC with Windows Vista and I am connected via a network to a PXI-8108 controller in a PXI-1050 chasiss chassis. The instrument is just a thermocouple which I use to become familiar with everything. The thermocouple is connected and the connection SCB-68 block which is connected to a PXI-6221 multifunction data acquisition in the chassis. I am able to create a task in MAX under remote system and everything seems to work. What I want to do is to get the readings in Veristand, and I don't know if I need to create a custom device that is related to the acquisition of data somehow, or if there is another way to do it. I created the DAQ hardware in the system Explorer, but I see no way to link the real DAQ hardware on the remote system. I wonder if anyone can help with this.

    All advice is appreciated.

    Thank you

    You can read the value of your thermocouple directly from VeriStand channel, but the process is different than using MAX.

    In the system Explorer, add your DAQ hardware that is wired to your SCB-68. Make sure that you specify the same name (i.e. ' Dev1'), which is the make up something, you also that you have imported the peripheral canal which hangs to the thermocouple (i.e. "ai0"). There is no way in System Explorer to specify that this channel should be scaling of thermocouple. VeriStand initially served this string value value brute power. However, you can set the limit high and low for this channel to something small as +/-1V, since thermocouples have very small readings.

    You add the balance to your system separately after the deployment of the system definition, you have created the target of RT. For this to connect to the target using the workspace and select the tool to the workspace on the Tools menu called channel scaling and Calibration Manager.

    In this dialog box, you will see your TV listed DAQ. Navigate in the dialog box assign an appropriate scale of thermocouple to your channel. Once this is done, the target will remember the scale for this channel until what crush you.

    I would like to know how it goes...

  • DAQ in Veristand readings do not match the MAX readings

    I have three accelerometers attached to a block of SCB-68 connection that is connected to an NI PXI-6221 data acquisition on a RT system. I have created a task for each accelerometer in MAX and have tested each one to see that it works and gives appropriate readings. Veristand, I created a workspace file to test the accelerometers and I the acquisition of data created in the system Explorer. After the deployment of the system definition and running workspace, I created three simple graphics and connected ways appropriate to each curve. I reduced tensions in the same way exactly, I put on the scale the to the MAX, but for some reason, one of the accelerometers gives tensions that are far away from where they should be. The other two accelerometers work perfectly and one that does not works perfectly in MAX. So I don't think that there is a problem with the accelerometer, it just would not work in Veristand for some reason any. I wonder if there is someone who can at least have an idea of why something like this could happen. I have all three accelerometers that are related to the same connector block and I wonder if put too much in a block would do something like that.

    Any help would be appreciated.

    Thank you

    For all those who can do I understand what the problem is. The default setting in Veristand read channels of differential measures, so anything connected to channels 8 or below is mapped to both channels, (e) and has (n + 8), where n is the number of the channel. For me to use the accelerometers in the way I set up the I just need to go to unique benchmark measures ended (CSR) in the system Explorer.

    Once again thanks for your help.

  • Problems VeriStand 2011 RT and SCXI-1540

    Good afternoon

    As in the topic, we have problems with our card module SCXI-1540 that we use to acquire a mixed selection of RVDT and resolvers.

    Specifically, we have our facility on Veristand 2011 on a target of RT who has a device custom control map SCXI chassis PXI-1050 and the NI PXI-6221 card, everything is fine but every now and then the map 1540 suddenly start showing a rolling measure of angle for resolution programs.

    By checking with an oscilloscope, resolvers entries are good, but we notice that when the event occurs, the excitement somehow pass set 5 kHz to 10 kHz and even by the cancellation of the deployment and redeploy the project and verify that the property node DAQmx channel used to set the frequency of excitation is the correct setting of 5 kHz and does not return an error There is no way to get the channel back to 5 kHz, and it remains stuck at 10 kHz. The only way to be able to control the frequency of excitation again is through a power cycle of the RT/chassis.

    We checked also by adding debug code in the custom feature event is the channel of sin or cos channel starts showing a rolling measure voltage so our measure of angle begins to roll too.

    So far, this behaviour seems to have manifested only with programs of resolution that we mainly tested those and synchronize us excitement between a sin / cos pair.

    Please notify

    I just noticed that I never gave a solution for this.

    The problem was current flyback to another causing system glitches of EMI on the lines of resolvers somehow mess with map of 1540, which essentially stopped decoding of the resoulvers of entry correctly, I added a Reset custom device close the file and that fixed the not being able to get out of the excitement of 10 Khz on the redeployment. However the final fix was adding flyback diodes to the tokill power system high seeds. So beware of your configuration as module SCXI-1540 cards seems to be sensitive to such events.

  • NOR-FGEN Arb Express reactivity

    Hello

    I'm playing with the VI Express NOR ANY Arb (with the NI PXI-5421) in order to learn how to create my own VI to generate impulses of the arbitrary.  However, I find that when I click on "Run" in the Express window, my o-scope seems never to receive the waveform correctly.  I use the sine wave sample and when I click on 'Run' with him put "Start continuous" the o-scope screen updates a few seconds later with a fragment of a sine wave, and it does not always up-to-date.  The Test panels for the 5421 work very well with the o-scope, so I don't know what goes wrong.

    Any help is appreciated.

    Thank you
    Billy Maier

    EDIT: Never mind, the problem itself.  I don't know how to remove the wires.

    Glad to hear that you have found an answer to your probem a little extra tip is to go beyond the express VIs as quickly as possible. The simplified interface they provide comes at a price. Banely, these screws will be nake laying of assumptions that do not always work in your favor.

    Mike...

  • Good resolution of the device

    Hi all

    I'm trying to understand if I set the resolution of my appropriate cell. If anyone has a spare time could you please give me some comments.

    That's what I know: rated power LC is +/-0.5348 mV/V and requires 10 v excitation.  Applied load of +/-115N offers (Max) + / 5 out of LC .348mV.

    So 1µV = 0.021N.

    What I'm confused about is this. After that I connect LC SG24 unit with excitation 10V and gain 100, should I even when the relationship between µV and Newtons as before or should I recalculate it according to this 100 gain, such as:

    Applied load of +/-115N (Max) provide 1µV and +/-534 .8mV LC output = 0.000021N?

    Sg24 signal will pxi-6221, which has 4 lines/res., so my understanding is once the relationship µV and Newtons is correctly calculated to get the resolution of LC in some range of PXI unit, say (+/-200 mV-> 6.4µV resolution), I just need to multiply my value of 6.4 1µV.

    Thanks in advance

    There is a gain of 100 on the SCC-SG24 but it will be transparent to the voltage, you will see when to acquire in your program.  The reason for the amplification is to use the full range of the ADC on the PXI-6221.  Thus, your input signal, seen by the NI PXI-6221 will (max) 5.348mV * 100 = 534.8mV.  If you set the range to the PXI-6221 of +/-1V, then you will be able to have a very high resolution on the signal amplified (2V/2 ^ 16 = 30.5 uV).  However, the output signal, you will see will be is scalable down into the 5.348mV software was seen initially by the SG24.  No conversion is necessary.

Maybe you are looking for