Change in gain on the PXI-6221

Similar Questions

• What is the maximum voltage of the members of the PXI 4461 gain 20 dB?

  I use a Board, PXI-4461 sample sine wave with an amplitude of slightly greater than 1 V peak (1.0005 V). The gain of the Board of Directors is set at 20 dB and the input range should be from-1 to + 1 V V! That's why I expect that see a saturation of the converter ADC when the input signal is greater than 1 V. However, I do not respect this saturation of the output value, and I don't understand why?

  Could someone explain that to me?

  Thank you in advance.

  Frédéric

  Hello Frederic,.

  almost all NI DAQ devices I know has a small "margin of safety" in each range given acquisition (usually about 0.5-2%), allowing you to accurately measure the voltage specified limit.

  The exact width of this margin is not explicitly mentioned, probably to prevent users to use this line on a regular basis.

  In short: there's a small safety margin, but do not count on it when designing measurement applications. ;-)

  Best regards
  Sebastian

• Problem with the PXI-6534 elimination change detection task

  I ran into the following problem.  I use a PXI-6534 and PXI-6602 with vb.net for detection with a timestamp of changes.  My code works fine and I get data exactly as I want, the problem comes when I try to call the task.dispose function.

  When I call him has, she throws an exception with error-200088 code, task does not exist.  But the task is still stopped and I can run my code again and everything works fine.  If I do not call the task.dispose, I get an error when I try to run my code again.  The material seems to have left in an unknown state, and I have to restart my computer to get it back. (the MAX NOR even reset the 6602, he says only that the Council does not exist).

  Interesting also is the exception thrown does not seem to be caught by the Try Catch method.  The code traverses the Try Catch without any problem (step by step in the code anyway), but with the exception, the message box appears, either immediately or when coming out of the subroutine.

  Also, I use TestStand 4.2 to call these functions, if that makes a difference.

  Any help would be greatly appreciated!  Its very frustrating that everything works and I get my data perfectly, but I can't run the code without exception popping up, and I can't seem to catch the exception.

  Here is the code I use:

      Public Sub StartChangeDetect_UUT1()
          If myCDrunningTaskA Is Nothing Then
              Try
                  ' Create the task
                  uut1ChangeDetectTask = New Task()
  
                  '************************ Create the digital input virtual channel alias
                  'Assign ports to digital virtual channel
                  uut1ChangeDetectTask.DIChannels.CreateChannel("Dev1/port0:3", "ChangeDetectUUT1", ChannelLineGrouping.OneChannelForAllLines)
                  'uut1ChangeDetectTask.DIChannels.All.DigitalFilterEnable = True
                  'uut1ChangeDetectTask.DIChannels.All.DigitalFilterMinimumPulseWidth = 0.000001
                  uut1ChangeDetectTask.DIChannels.All.InvertLines = True
                  uut1ChangeDetectTask.DIChannels.All.DataTransferMechanism = DIDataTransferMechanism.Dma
  
                  'Assign ports to monitor for change detection, both rising and falling edges
                  Dim rising As String
                  Dim falling As String
  
                  rising = "Dev1/port0:3"
                  falling = "Dev1/port0:3"
                  uut1ChangeDetectTask.Timing.ConfigureChangeDetection(rising, falling, SampleQuantityMode.ContinuousSamples, 4000000)
  
                  'export change detect event to PXI backplane so we can get timestamps from timer.
                  uut1ChangeDetectTask.ExportSignals.ChangeDetectionEventOutputTerminal = "/Dev1/PXI_Trig0"
                  uut1ChangeDetectTask.ExportSignals.ChangeDetectionEventPulsePolarity = ChangeDetectionEventPulsePolarity.ActiveHigh
  
                  'uut1ChangeDetectTask.Stream.Timeout = 20000
  
                  ' Verify the Task
                  uut1ChangeDetectTask.Control(TaskAction.Verify)
  
                  ' Set up the data table
                  Initializeuut1DataTable()
  
                  ' Create the readers for the DI and the CI
                  uut1ChangeDetectReader = New DigitalSingleChannelReader(uut1ChangeDetectTask.Stream)
  
                  uut1CDCallback = New AsyncCallback(AddressOf uut1ChangeDetectCallback)
                  uut1ChangeDetectReader.SynchronizeCallbacks = False
                  ' Set up our first callback
  
                  uut1ChangeDetectReader.BeginReadMultiSamplePortUInt32(-1, uut1CDCallback, uut1ChangeDetectTask)
                  myCDrunningTaskA = uut1ChangeDetectTask
  
                  'Set up Timer for time stamp
  
                  uut1TimeStampTask = New Task()
                  '****************set up PXI-6602 timer to get buffered change events.  ie capture timer output on  the PXI_Trig0
                  'we can then correlate this timer capture buffer to the change detect buffer to get the time stamps
  
                  uut1TimeStampTask.CIChannels.CreatePeriodChannel("Dev5/ctr0", "TimeStamp1", 0.0000001, 0.02, CIPeriodStartingEdge.Rising _
                               , CIPeriodMeasurementMethod.LowFrequencyOneCounter, 4, 4, CIPeriodUnits.Seconds)
                  uut1TimeStampTask.CIChannels.All.CounterTimebaseRate = 20000000.0
  
                  'Use exported change detect from 6534 board to take counter sample
                  uut1TimeStampTask.Timing.ConfigureImplicit(SampleQuantityMode.ContinuousSamples)
                  uut1TimeStampTask.CIChannels.All.PeriodTerminal = "/Dev5/PXI_trig0"
                  'uut1TimeStampTask.CIChannels.All.DuplicateCountPrevention = False
                  uut1TimeStampTask.CIChannels.All.DataTransferMechanism = CIDataTransferMechanism.Dma
  
                  ' Set timeout
                  'uut1TimeStampTask.Stream.Timeout = 20000
                  ' Verify the Task
                  uut1TimeStampTask.Control(TaskAction.Verify)
                  uut1TimeStampReader = New CounterReader(uut1TimeStampTask.Stream)
                  uut1TSCallback = New AsyncCallback(AddressOf uut1TimeStampCallback)
  
                  uut1TimeStampReader.SynchronizeCallbacks = False
                  uut1TimeStampReader.BeginReadMultiSampleDouble(-1, uut1TSCallback, uut1TimeStampTask)
                  myTSrunningTaskA = uut1TimeStampTask
  
              Catch exception As DaqException
                  ' Display Errors
                  MessageBox.Show(exception.Message)
                  uut1StopChangeDetection("C:\PT3771\TestResults\")
              End Try
          End If
      End Sub
  
      Private Sub uut1ChangeDetectCallback(ByVal result As IAsyncResult)
          Try
              'If runningTask Is ar.AsyncState Then
              If myCDrunningTaskA Is uut1ChangeDetectTask Then
                  ' Read the available data from the channels
                  Dim data As UInt32() = uut1ChangeDetectReader.EndReadMultiSamplePortUInt32(result)
  
                  Dim b As UInt32
                  For Each b In data
                      ' in TestData waveform Y axix is data, x axis is time 
  
                      uut1TestData.SetY(uut1ChangeDataIndex, b)
                      uut1ChangeDataIndex += 1
  
                  Next b
  
                  '' Set up a new callback
                  uut1ChangeDetectReader.BeginReadMultiSamplePortUInt32(-1, uut1CDCallback, uut1ChangeDetectTask)
              End If
          Catch exception As DaqException
              ' Display Errors
              MessageBox.Show(exception.Message)
              uut1StopChangeDetection("C:\PT3771\TestResults\")
          End Try
      End Sub 'DigitalCallback
  
      Private Sub uut1TimeStampCallback(ByVal result As IAsyncResult)
          Try
              'If runningTask Is ar.AsyncState Then
              If myTSrunningTaskA Is uut1TimeStampTask Then
                  ' Read the available data from the channels
                  Dim data2 As Double() = uut1TimeStampReader.EndReadMultiSampleDouble(result)
  
                  ' in TestData waveform Y axix is data, x axis is time
                  Dim b As Double
                  For Each b In data2
                      uut1TimeSum = uut1TimeSum + b
                      uut1TestData.SetX(uut1TimeStampIndex, uut1TimeSum)
                      uut1TimeStampIndex += 1
                  Next b
  
                  ' Set up a new callback
                  uut1TimeStampReader.BeginReadMultiSampleDouble(-1, uut1TSCallback, uut1TimeStampReader)
  
              End If
          Catch exception As DaqException
              ' Display Errors
              MessageBox.Show(exception.Message)
              uut1StopChangeDetection("C:\PT3771\TestResults\")
          End Try
      End Sub 'CounterCallback
  
      Public Sub uut1StopChangeDetection(ByVal location As String)
  
          Try
              If Not (myTSrunningTaskA Is Nothing) Then
                  uut1TimeStampTask.Dispose()
                  myTSrunningTaskA = Nothing
  
              End If
  
              If Not (myCDrunningTaskA Is Nothing) Then
                  uut1ChangeDetectTask.Dispose()
                  myCDrunningTaskA = Nothing
  
              End If
          Catch ex As Exception
              MessageBox.Show(ex.Message)
          End Try
  
          uut1TestData.UpdatePointCount()
          uut1TestData.SaveToDisk("C:\PT3771\TestResults\uut1TestWaveFile.csv")
          uut1TestData.SaveToDiskBinary("C:\PT3771\TestResults\uut1TestWaveFile")
      End Sub 'StopTask
  

  Joe,

  Last updated.  It seems that when the task.dispose is run, recalls seem to have called one last time.  I took the call to the stopUUT1ChangeDetect in the two recalls (so eliminate it would not enforce a second time), and no exception was thrown.

  Thanks for your help!  Although if you'd still answer my question on the PXI-6534 Digital input filtering, I'd appreciate it.

  Thanks again.

  Thad

• 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

• OR DC Soft Front Panel, minorbug, small bug with the PXI-4110

  Hello

  The NI DC Soft Front Panel V14.0, with the PXI-4110, scrolling to negative tension, works as expected to-10V, but then returns to 0. If we change from - 1V procedure, it goes...-8-9,-10, -1, -2... instead of-8-9,-10, -11, -12...

  Everything about her, a simple thing that I miss is a switch for all three voltages.

  (Also, IMO, it would be logical for negative tensions with the arrow pointing down, not more).

  My 2 c

  Hello Janaf,

  I completely agree with two of your statements, I tabled a report of corrective measures that you can monitor in the next versions of DCPower to see if this is fixed with the FPS. CAR number: 512257

  I've added notes that only manual insertion of numbers - less than 10 works and that it was not logical to use arrow increment or upward arrow to reduce the output voltage.

• Variation of thermal EMF of the PXI-2530 modules

  This message/question is a companion of my the most recent message in another thread.

  In addition to watching some resistance higher than expected that affected current measurements using modules PXI-2530 multiplexer 4W topology, I saw systematic variation in track-to-track blood pressure measurements. Tensions would increase gradually through the 16 channels in a configuration by measuring the voltage at the terminals a resistor 1.5 kOhm with 0.5 au crossing (75 uV). I've identified that the thermal EMF of the reed in the PXI2530 module switches is on the same order of magnitude of these measures and set out to quantify the differences EMF thermal track-to-track between my three modules.

  Test method: I have a TB-50 which is configured to mux the signals of tension for a DMM. I connected each of the four DB-50 one cable of 176 pins to this block and collected with a PXI-4071 pressure readings set to 7.5 digits precision in the range of 100 mV and > 10 GOhm impedance. For most channels, it took several minutes for the voltage stabilize - or at least appear that it was to stabilize.

  I enclose three graphs. Note that the vertical scale is the same on each.

  Data that triggered this survey was collected with MUX1, via connector P2 to voltage. The magnitude was not quite the same-probably related to the phenomenon of stabilization time, but obviously the worst group of channels three multiplexer modules.

  The three modules were all bought at the same time (about 2 years ago), but had only limited its use in the first year or more. The three now have various 'mileage' based on my use. But MUX1 clearly behaves differently two other modules. The

  I changed my test conditions to spend 0.5 au via a higher resistance to thermal EMF less important. The PXI-2530 sheets indicate that thermal EMF must be less than 50 uV. In most of my measurements, it is. But not for MUX1!

  Any thoughts?

  Thank you

  Jeff

  Hi Jeff,

  You can check that all the three modules are PXI-2530, not PXI-2530 b (while, as the PXI-2530 b parts slightly higher thermal emf)?

  Specification of emf thermal 50uV of the PXI-2530 is a typical value, is not a guarantee of spec.  See a few channels higher than the spec is not a cause for alarm, but it shows that we must take account of this in our measurement error.  Note that the industry standard for the technical measure thermal emf is to close the relay, wait a few minutes and then take a measure of tension.  For example, if you scan through a switch faster than a relay per minute or so, the thermal emf will be less predictable and stable.  A single module performs worse at these low voltages is not indicative that this module is a failure, etc. the module is fine.  Unfortunately, the reed relays have more emf thermal relay of the armature, mainly because of the many layers of metal in a Reed compared to a frame (each metal junction is a source of emf if these metals are not the same).

  Thermal EMF is proportional to the temperature, it may be interesting to note the position of the chassis of the less powerful module.  Placing hottest modules (scanners, Ara, RF, etc.) will reduce the thermal emf.

• Use the PXI-2630 terminal block in a matrix configuration?

  My apologies in advance for the length of this post!

  I use the PXI system with PXI-2530 switch modules, related to a series of USE with PXI-2632 (1W matrix 8 X 16) connector blocks and a PXI-4071 DMM for each switch module. My request, uses the PXI system for measurement of current and voltage external to verify and/or benefit from restraints of reliability. A requirement of the application, therefore, is that there must be a ride from DC through each USE with change of the minimum impedance as the application between its "bypass" mode switches and its mode 'measure '.

  I used this Setup with connector blocks of matrix in conjunction with one of our test systems, and I am satisfied with the results. I started working with the Test System, has no easy connection to catch HAD, I needed to build a kind of interface the PXI system and a resistive faced load HAD, it was not difficult to build in the wires that attach to the Terminal screw of the 2632. He did turn into a nest of a coded son rat I did my best to keep clean and tidy in different bundles, however. Fortunately for the cable fasteners!

  My next task is to use this application with system B Test, which has an interface of pines buck header with which each signal that goes to or from the DUT can be obtained. No welding or pass the wires through the openings where the designers have no intention of son to be stuffed. I intend to build a break-out Board that allows simple connections between the modules PXI and the number of Test B system which we have or will have in our laboratory. In order to simplify the configuration/installation, I want to reduce the number of connections to terminal block screw. Preferably, I would like to completely remove the screw terminals and use lever-based connections where I can't have mating of the headers. The PXI-2632 terminal blocks unfortunately use Terminal screw.

  In matrix mode 8 X 16, the closing of the PXI-2530 switch kcom1, 3, 5, 7, no matter what points in the array are connected. A link between the row of right and column C is done by closing the switch corresponding to k (16R-C). I checked using the Soft Front Panel.

  I also have a number of connector PXI-2630 blocks. These are intended to be used with the switch module in one of its MUX modes and include 8 banks of connections of the header 2 X 9 pins. In the the 2530 documentation and 2630, I identified that switch k-x is associated to chX output pin, ch0-15 related to the pins 1-16 from Bank 0, C16 - 31-associated pins 1-16 of Bank 1, etc.. X = 16 B + P-1. PIN 18 of each bank is used for independent MUX topology comX. Pines multiplexes sixteen seem to correspond to the sixteen columns of the matrix, with eight common lines corresponding to eight lines.

  Here's what I would do, but I would like to ping the forum to see if anyone tried something similar and wisdon to share the thought:

  • Make custom cables which connect the pins 1-16 of all eight banks 2630's header with a single Ribbon connections 16 son carrying the signals emitted by the interconnected banks (poles!).
  
  
  • The custom cable bundle will also include a wire connected to the pin18 of each of the eight banks (line connections!)
  
  
  • 24 total wires in the harness will end in the header connections who will probably partner by the lines that I currently connect to each object to be measured.
  
  
  • Make additional harnesses that interface with the Test System B header pins.
  
  
  • Make a map of derivation using band Council or a similar material to provide header pins to connect the two above custom cables and allow the connection of other elements such as resistors using Terminal level.

  I checked this concept using the Assembly of 176 pins four terminals, like a bunch of little pieces of wire and cable. Are there other issues that I have to configure, such as the elements of a terminal that establish physical components of the switching topologies? The bowels of the PXI-2632 provide more features than the interconnection of the sets of eight sixteen pins? The bowels of the PXI-2630 connect elements that do not allow my proposed scheme?

  I appreciate the suggestions and all entries!

  Thank you

  Jeff Zola

  Hi Jeff,

  First a correction to my previous post: 2632 Terminal has no reed relay protection resistors as I said earlier. The resistance that you were referring to the 2632 and those that I confused, is there to connect the columns of the switch. Resistances have a resistance value zero and act as the electrical connections. The 2632 connects columns c0 to c16, c17 c1, c2 to c18 and so on. Switch cards 2531 and 2532 have the protection relay reed on board resistors.

  As for resistance in the map that protect the reed relays, they are generally very low and do not significatly affect even small tensions that pass through the switch. The resistance won't affect all currents in the map. Any effect that the resistors have on tensions will be with the precision of the switch card specifications.

  Thus, to address the other issue in your post, there is no resistance in the connectors because they are not necessary.

• Acquire more than 2047 samples with the PXI-4461 instaled in SMU-1073

  Hi all, I would ask you for help with the buffer limit.

  I intend to buy digitizer PXI-4461 and he instal in SMU-1073 chassis, namely control via MXI Express of Labview installed on a separate computer.

  What I need:

  -to acquire data of a single channel of AI, but at least a sequence of 20 kS by a acquire task, in some situations until 200kS by a task to acquire.

  The question:

  - I can gain more than 2047 samples in a single sequence, like 200kS, with the PXI-4461 installed in SMU-1073?

  Internal buffer of the PXI-4461 is reserved to 2047 samples. So I'm not sure if Labview can download remotely via MXI Express the data in the buffer of the PXI-4461 via MXI Express fast enough without any affection of the sampling program.

  -in the case, this PXI-4461 with SMU-1073 isn't the right combination, what chassis and a controller can do?

  Thanks much for the reply

  Jan

  It will work for you.

  The on-board buffer 2047-sample is used only as a backup if the flow of data to the PC host (via MXI Express in this case) is not fast enough... that it will be (explained below).  DAQmx transfers data from the buffer of the device to the host PC as fast as he can and, in ideal conditions, should not save the buffer 2047 much at all.

  Let's just say you get 110 MB/s (randomly from a MXI data sheet) flow on your MXI connection.  The 4461 has 2 analog inputs, which will be at 24 bits, we just round 32-bit in case it transfers the data in this way.

  4 bytes/sample (32 bit) x 200,000 s/s x 2 (channels) = 1.6 MB/s, which is well below the 110 MB/s, which will make the MXI link.

  clear as mud?

  Germano-

• Connection of the PXI-4071 - can sound and LOs remain interconnected for the impedance of the cable 2, voltage DC/AC, frequency and waveform acquisition?

  Hello

  We use the DMM and SMU-6363 map to test a hardware device.  We will also use a PXI-2530 b switching matrix.  We will use the digital multimeter to perform the measurements of voltage, DC and AC, measurements of impedance (2-wire and 4-wire), frequency and waveform acquisition.  Can the PXI-4071 left be 4 wire connected (black jacks taken connected and red connected) mode and still be used to perform all other measures (including 2 impedance of the cable).  This would simplify the switch connections.

  Current measures use the son + and LO, but the HI and S-can remain connected.  The problem you are having is if you have an active device the digital multimeter and take you a 4-wire resistance and the measurement of voltage with all 4 wires connected and then change to a current... When you do this, short-circuit you the terminals of the DUT, on that you just take the measurement of the resistance.  If the terminal HAD, say, a power supply 10V, then you have just shorted out.  Of course, this isn't a problem if your Instrument is a passive device, or if you change just the unused two lead whenever there is an active device of low impedance.

  If you want to make voltage, current and 4-wire resistance, you need all 4 wires.  If you want to do the voltage and current, you will need 3 wires, but you could connect the s + Hi and then just do the two wires.  I vote running every 4 son to your DUT for maximum flexibility.

  2-wire resistance is a must if you are measuring resistance above 10 MOhm.  Alternatively, you can use 4-wire for all measures.

• Trip trying to rearm with the pxi-5122 times

  Hi all!
  This is my first discussion in this forum so I'm not sure this is the right place to post, because I'm using LabView, but maybe it's a hardware problem.

  Then... I have a problem to calculate the tripping time rearm to pxi 5122.
  Compared to data sheets, I read that it should be about 3 us with the CDT to the large or 12 US if on.
  But I need a precise measurement of the time out after each record measured so I decided to find it by myself...
  With the help of an acquisition program that I have previous written in LabView, I started only acquisitions of 10000 records and each record is composed of 128 samples; as signal I've used waves square with different frequencies, 10 volts peak-to-peak (my trigger was set on the first channel of 5122 with 1 volt in value of edge).

  First acquisition: wave of 50 kHz. Theoretically, I s 0,2 need to capture 10000 records without losing all the square wave signals. Choose a time of acquisition for a single record of 15.3 us, I found that the time required is 0.199998 , very similar to the one expected.
  Then by choosing a time of acquisition for a single record of 15.4 us, I found approximately 0.4 s.
  I can guess that this latter one each tops of two waves will lost so I held twice the capture of 10000 records time.

  Because the wave is 20 us I calculated a timeout of 20-15, 3 = 4.7 us.
  It wasn't like the 3 described us for the 5122 but I was not impressed and I went with my essay.

  Second wave: 20 kHz. I need 0.5 s to capture 10000 records without losing the square wave signals.
  What I found was that in this case, choose us an acquisition time for one record of 39.6 required 0.5 s to capture all vertices, then with 39.7 us I held about 1 second, once again, twice by the time.
  The previous example, I calculated the dead time: 50-39, 6 is 10.4 us.

  Very strange... idle time I'm supposed to be the trigger for rearmament (and thus fixed) did not differ in 2 cases.
  Tried with other wavelengths, the values are always different.

  This also the frequency of the square wave of fixing and changing the number of samples per record.
  For example, with 128 samples per files as I told before, I needed a measurement time of 15.3 US to collect all the consecutive summits, while 64 samples I need 12.8 us and so forth.

  So it seems to be a dependency between the dead after a record time (the trigger reset? now I'm not sure if I can call it that) and the sampling frequency of the pxi 5122.
  But I don't know why, the acquisition of data behave in this way.

  Is this good? Rearm time should be set, shouldn't it?

  I know it took some time to read my problem but I tried to be more precise, I could.
  Thank you in advance.

  Giacomo

  Yes that's correct.  However, I do not think that its acceptable rate of the nearest synchronization that is chosen.  I really think he goes to rate lowest according to acceptable timetable.  So, if a synchronization rate is 2 and another is 5, and you want a 4.9uS rate, the synchronization will be 2, while 5 is the closest.  (Or maybe it's the other way around)  That's why you see the double period during the change of rates by just a fraction.

• How to reset the indicator of County of Terminal on the PXI-6608

  Dear community,

  Is it possible to reset the terminal number on the PXI-6608 indicator? When I use Get Attribute.vi I have the time to correct value first, but unfortunately (unlike DAQmx) reading of the value is not reset it...

  I like to keep track of how many times he flipped. And I don't want to use another counter to do because I like to keep them free for other things.

  Thank you!
  Case No.

  Traditional DAQ doesn't have a way to reset the indicator terminal number, as far as I know. One thing you might be able to do is change the "output" in "toggle" mode and then read the "output status" to determine the reversals to determine when the State of the output has changed in your application.

  I hope this helps!
  Gus...

• Single channel match trigger speed model vs onset of edge on the PXI-6562

  I think that my question boils down to this: what function does the edge of trigger plan that is not provided by the model match trigger?

  As far as I know, the only differnece on the PXI-6562 is the edge trigger has its own pins dedicated (PFI pins and pins RSTI) to detect a trigger, while the model match trigger detects a rising edge or falling on a regular input pin.

  Is there a difference in performance (for example, the time to rearm)?

  Are both triggers synchronous types with the sample for dynamic acquisition clock?

  On my application:

  I acquire a signal off a SPI bus, triggering the CS line. I start to acquire data when the CS line going down and stops when the CS line is high. As I acquire data CS on a regular supply, it seems logical trigger on a pattern for this channel only match. I'm curious to know if there is any advantage to connect a PFI PIN to my CS of entry so that I can start using digital edge type.

  Thanks in advance,

  Arthur

  Arthur,

  There is no difference with regard to performance using a digital camera compared to a type of pattern match trigger. Specifications for rearm time reference to the trigger type (Start, reference, etc.) in the samples to rearm, and there is no difference with the performance when you use a digital advantage over a line/PFI line Trigger and a correspondence to the model used on the input signal. Change the source of the trigger itself will not change the performance of the material that occurs after the trigger is received. This behavior to sync with the clocks of acquisition regardless of the input source. We're just looking at different sources for the jury to look for a given trigger.

• Modules in the PXI-1033 chassis detection problem

  Hello

  I met difficulties in operating my PXI-1033, which installed two strips of XIA Pixie-4. Until recently the system was working properly, but now I am unable to detect and use modules using software of XIA, although according to Windows both modules are "working properly". Nothing has changed between the time it was working and now (that I know)!

  I suspect the problem involves the chassis, since when I place a module in slot 6, the chassis will not be powered. It will power-up with any other occupied housing.

  Any help would be appreciated.

  See you soon.

  Hello jnod,

  At these modules never appear in measurement and Automation Explorer (MAX), if so they appear actually now?

  Also if you have other material, I'd be interested to know if the PXI chassis will start when you have a module IN slot 6.

  The chassis won't start when either module Pixie-4 is in slot 6?

  You probably already know, but turn you on the chassis PXI before you have activated on your computer?

• changing PID gains

  I use the PID advanced VI to a pressure regulator and had tried to vary the winning entry proportional to the VI using an equation based on other settings, such as the behavior was similar to gain scheduling, only contiguous versus by steps.  Unfortunately, it seems that PID VI cannot handle the PID gains that are continuously variable from iteration to iteration.  The result is zero, and dig in the block diagram of the PID VI, it is barely readable, but seems to do something different in case of a detection of a change in gains of PID.  So my question is, is there a simple way to do what I'm trying to do with the provided screw OR, or am I limited to fixed PID gains?  I couldn't works around the problem by allowing the calculated algorithmically proportional gain will persist for a number of iterations before allowing an update?

  Hello

  Yes, you can.

  Don't forget: create your own copy of the VI before you change! Never change live in vi.lib!

• The original loop iteration after receiving the trigger of the PXI-6652 pulse

  Hello world

  I apologize if this has been answered somewhere else, but I'm having a hard time finding examples and tired after a long day of work.

  in any case, I use a PXI chassis with a PXI-7854R FPGA Board and module synchronization PXI-6652.  I have the FPGA biphasic pulses being generated at 8 analog channels.  I want to be able to do is to send a trigger (say at 1 Hz) for the PXI-6652, which begins at the exit of the biphasic pulse on the FPGA.  I'm running the FPGA through a host program as the variables on biphasic wave will change based on the current experience.

  So, in short, I was wondering how to generate a trigger of the PXI-6652 pulse and then use this trigger in a host of VI to start an iteration of a loop.  It seems simple enough, so any help would be appreciated.

  Thank you, and I can post the code tomorrow if necessary.

  To answer your second question, Yes, the driver NOR-SYNC 3.3 is available for download and use with LabVIEW 2011.

  As far as use the PXI-6652 to start the acquisition on an FPGA VI, we have enough good examples provided with LabVIEW that will show you how to proceed.  To actually generate a trigger with NO-Sync, there are several examples in the Finder for example of NOR (help > find examples) which send a trigger one of the PFI lines to be used with the other modules.  You can search for OR Sync and they all appear here.  You need this driver installed first before you see anything, however.

  Also, if you look through the viewfinder of the example under Hardware Input and Output > R Series > FPGA Fundamentals > triggers and guard dog, you will find an example of triggering good enough it for use in your FPGA code.

  This example uses NO-Sync to trigger a device of the M series, which is not relevant to what you are doing (he uses DAQmx), but there is a very good example of generation OR-Sync trigger here who I think can help.