1031 DC pxi star trigger

Similar Questions

• Star trigger for pxi REPOST 1031 DC - obsolete

  Hello colleagues LV coders.

  I've looked everywhere and can't find the answer to the following question: How can I access a trigger in Star in a PXI 1031 DC chassis?  I know this must be through SLOT2.

  I currently have a micro controller PXI - 8102 SLOT1, an arbitrary generator (AWG) pxi-5422 the SLOT2 and a PXI-7954r FPGA with a digitizer 5761 nor in SLOT4.  I know that activitate the outbreak in Star, a "Timing and synchronization' card must be in the SLOT2.  Is it possible that I can use either the microntroller in SLOT1 or the Working Group in the SLOT2 for access to the relaxation of Star?  I think that the microcontroller will probably be able to reach, but what about the Working Group?

  Follow-up on issues is as follows: suppose that I am able to implement this Star trigger correctly, once the working group receives the signal to send its chirp 10usec by having the Star trigger go HIGH, is there a way of simultaneously to adjust the line of PFI0 HIGH in the Working Group and a time that the 10usec is completely sent to set the PFI0 on the BASS line in the generator of signals for usec then 90? This could be repeated indefinitely and the PFI0 line is used to control a switch via a cable.  In addition, this PFI0 of the GTS line will always be equal to "output mode".

  Thanks in advance a ton.  If I found the answer elsewhere, I'll make sure to update here.

  -Daniel

  Repost tothis forum.

• How to delay a PXI-5122 trigger before routed to string of PFI

  Hello world

  I use a PXI-5122 in a PXI chassis. I want to synchronize with two external devices. The first will send a trigger (with a 10 Hz repetition rate) for PXI-5122. Then PXI will generate a trigger (with a constant delay) in the second.

  It seems that I need to generate a trigger, then export this trigger to PFI 0 line, but I do not know how to delay triggers with a timeframe of 4µs. I read that there is a slight delay between a trigger on the PFI and the first sample. And the length of the cable is also an important factor to consider.

  Could someone give me some suggestions?

  Wednesday,

  Thanks for the drawings, that helps a lot!  Somehow, I see this work (how to set up the scanner):

  1. set up the record length to be 12us (4us trigger samples, 8us after outbreak).  If the sampling frequency is 100 ms/s, that would be a record length of 1200 samples.

  2 configure the position of record reference to 33%.  That's how the digitizer breaks 1200 400 samples according to trigger before triggers and 800 samples.

  3. configuration of triggering immediate reference.  This will allow the acquisition of trigger the moment she gained 400 before triggering samples.

  4. export the "reference trigger (Stop)" to send to Device_2.  This output pulse is of variable width, so if you want consistency, you will need to the Device_2 trigger the rising edge of the pulse, did not not fall m.  Once 400-pre-trigger samples are acquired, this impulse will be sent, and then the scanner will be immediately habitable after initiation of sampling.

  5 configure the trigger of the entrance of Device_1 (10 Hz trigger), as the 'Advance trigger' and 'Start Trigger'.  This will make the digitizer wait this impulse to start sampling before the next record.  We set up, the relaxation of beginning to the 1st record and the trigger in advance for all subsequent records.

  This facility should allow a pretty decent timing, but please test to be sure that it will be sufficient for your application.

  Kind regards

  Nathan

• PXI external trigger jitter

  Hi all

  I use a Board PXI-5422 generator of finished generation mode signals to generate an external trigger signal (PFI0) about every 5ms. There is a nominal 1.7µs delay of the input trigger for the start of the generation. That in itself isn't a problem (I can compensate for the delay), but there are up to 50ns jitter on this period, which is a problem. Does anyone know if there is anything I can do to minimize this jitter? (Incidentally, PFI1 exhibits the same behavior, but it is not a surprise)

  Thank you very much

  Hello GVR123,

  I had a glance at the manual for the PXI-5422 and I found the note for the ' delay of start CH 0 analog output Trigger "which is indicated as"65 sample clock periods + 110 ns. With this information, I calculated that

  1.7 - 0, 110 = 1.59

  and

  1.59/65=0.025 (bulk)

  that points to a clock of 40 MHz. So I guess that's what you use.

  25ns deviation (40 MHz) each side (50ns total), you see the expectation, as there is no way to ensure that the trigger falls exactly on a rising edge of the sample clock.

  I hope this helps.

  Kind regards

  Michael S.
  Technical sales engineer
  NEITHER UK & Ireland

• PXI-6254 trigger external start (error-200452)

  Hello

  I have a PXI-6254, I need to start with an external signal, so it is synced with another device, however, regardless of the source, I say to use as a trigger (a PFI, PXI_Trig or PXI_Star line), LabVIEW tells me "error-200452..." The specified property is not supported by the device or is not applicable to the task. "For example, I'm doing a digital output using the example of 'Write dig Chan - Int Clk - Dig Start.vi'.

  Is it really the case that this device cannot be triggered by an external signal? The manual for this device (http://www.ni.com/pdf/manuals/371291h.pdf) implies that it can be triggered externally, and if it is possible, what I am doing wrong?

  See you soon,.

  Simon Coop

  Hello Simon,.

  The error that you are running in as well as the solution is summarized by the following section in the M Series User Manual page 6-3.

  

  Kind regards

  Izzy O.

  Technical sales engineer

  National Instruments

  www.NI.com/support

• PXI Questions - trigger and save the Communication function

  I would like to use the VISA API for working with modules in my chassis SMU-1062 q. I have installed the following modules in the chassis:

  1 NI PXI-5102 (scope)

  2 NI PXI-5402 (fgen)

  Instruments based on the registry as PXI modules are new to me for example I only worked with instruments of message in office until now. I had a number of questions on how to work with these appliances with VISAS, let me start by two of the most pressing problems for me right now:

  1. I don't understand how material trigger works in a PXI chassis. For example, if I'm working with the PXI-5402 (fgen) and I want to make a hardware trigger on TTL0 that the PXI-5102 (scope) can listen, how to configure it? What I see in the NI-VISA support, the VI_ATTR_TRIG_ID attribute allows you to specify the trigger line of material (TTL0 - TTL7) for a device. Once this is done, I'm supposed to (apparently) use the function:

  viAssertTrigger

  with the value: VI_TRIG_PROT_RESERVE

  in order to 'book' in the line. It is clear to me as agglomerates that produces a trigger on TTL0. At this point, I guess if I wanted to the PXI-5102 to be triggered by the TTL0, then I put the VI_ATTR_TRIG_ID in TTL0 for this camera as well? In addition, what is the difference between the implementation of VI_ATTR_TRIG_ID in TTL0 for the device (INSTR resource) against the implementation of VI_ATTR_TRIG_ID to TTL0 to the chassis (substantive resource of BASKET). What happens when I use viAssertTrigger in each case?

  2. my other question concerns using the PXI modules using ONLY VISA orders (I rather not use NISCOPE and NIFGEN at the level of the API). I understand how to use ViPeekN (16.etc, N = 8) and ViPokeN for reading and writing to/from the registry of PXI Configuration. What I don't understand how to use functions such as ViMoveIn, ViMoveOut etc to run modules, for example, make the PXI-5402 generate a sine wave. In other words, where can I find an explanation of how to order the PXI modules and send data using the API of VISA. It seems that I need documentation that explains how to issue orders of these devices from the registry, which brings à la carte, at the place where to read data from the etc.

  Thank you

  I did some looking and unfortunately we do not have any support for programming level registry with our Modular Instruments.

• How to export via the trigger star pxi to several dvices

  Hello

  I have huge problems to do this work and free time to try rarely. Joined my unfinished VI (SyncTrig - Test.vi) who needs to synchronize 9 x PXI-4472 & 1 x PXI-6713 on PXI-1006 chassis (made up of bus 3 x 6 slots). Master ST in the #2 Groove is DSA (PXI-4472), the rest 8 x DSA are inserted in slot #3-#10, and MIO (PXI-6713) is in slot #11. I need MIO to generate signals of x AO 2 (ao0:1 or ao6:7) of arbitrary length. DSAS acquire 72 x channels HAVE simultaneously until the last pair of samples AO is triggered (AO and I work at the same pace).

  I understand there are 2 ways to cynchronize a all these devices - to use reference clock 10 MHz from backplane, or Star trigger bus. Trigger the beginning of ST control is supposed to start all 10 devices. I couldn't do the 'references', examples and I managed to do the "StarTrigger" example works with 2 devices so I decided to stay with the latter. Of course, I hardly expect export usable for the PXI-6713 SampleClock and we hope to get help on this forum.

  Here are my 3 questions/dilemmas:

  1 grouping DSAS more in a single task & export clock via ST each

  I've separated the master of ST in the UpperTask export SampleClockTimebase via the bus ST and StartTrigger through the spine. The rest of the DSA are grouped in a single MiddleTask since NEITHER-DAQmx makes it easier for this type of devices PXI. In VI, UpperTask exports in a single PXI location.

  Is it possible to format the string to export the clock via ST to the multiple (all the) SHAS so they can all receive it grouped together in the unique MiddleTask? Or should I use a loop for export the time base clock 8 times and feed it 8 times for all slots #3-10?

  Please be specific.

  2 synchronization MIO with DSA master ST via bus from ST

  How can I use the TimingNode to implement SampleClockTimebase division, so that the PXI-6713 can use it in the #11 slot (LowerTask)? If this is not possible via the ST bus, can someone please show me what TimingNode (s) to use to export usable St master clock and get to MIO to synchronize the HAVE and AO closely?

  3 triggers of PXI chassis

  I left 2-7 as 'Dynamics' triggers to be available for NOR-DAQmx. Is it enough for the configuration shown above, from PXI devices occupy 2 of 3 independent buses in PXI-1006?

  BTW, I tried a different approach (SyncTrig - No. AO.vi), but the mistake of resting LowerTask just after his TimingNode power.

  Ladies and gentlemen, I hope power affirmative responses because the documentation is completely absent on synchronization PXI DAQmx and are completely dependent on WEB resources.

  Thank you in advance,

  
  

• Impossible to send software trigger using 6682 and OR sync

  I can't send a trigger of global software to the PXI (PXI_Trig0) trigger using the PXI-6682 card and the software of synchronization OR (beta 3.0 and 3.1). I ran the example vi: route software Trigger.vi and chosen my 6682 and terminal of destination PXI_Trig0 resources. I get the error:-1074118606 was held at niSync Connect Software Trigger.vi, driver status: (Hex 0xBFFA4032) the terminal specified source is not valid for this operation. Looking at the terminal of the source, it is selected as the GlobalSoftwareTrigger. If this card does not support a software trigger (I can't imagine why), if not, how can I send a software inside of basket PXI trigger trigger?

  Any help would be great.

  Josh

  I found this one. Apparently the PXI-6682 card cannot do a software trigger, so I plugged internally PFI2 to PXI_Trig0, then an event of installation time (down, up, down) on PFI2. Time event fires a trigger on PFI2 that triggers a trigger on the backplane PXI PXI_Trig0. I will then put up to fire all stars fires instead of PXI_Trig0 to synchronize my two FPGAS.

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

  Dear community,

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

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

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

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

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

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

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

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

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

  Tips, comments or solutions are appreciated. Thank you!

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

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

• 5154 PXI trigger on the external input

  I use a PXI-5154 and want to change my previous program to trigger the external source. I'm feeding the external source from source to V 2.5 and it seems to trigger fine. However when data acquisition the vertical range of the oscilloscope will 5 V which is too high as to my request I acquire in the millivolts range. I tried to show the vertical range of the channel I acquisition, but although I put it as the active channel I get the following error:

  Error 1074118616 has occurred to the property node (arg 1) in PD_measurements_v11_test.vi

  Get a base attribute value channel failed because the channels interviewed have different values.  Please specify a channel when you query a string based attribute.

  I enclose you a printsceen of the relevant part of the code.

  Kind regards

  Karavellas

  Dear Tunde

  I managed to make the changes you suggested and the works of the example. I'll look in my code and see what the problem is. I'll get back to you if it has been fixed in my code or not.

• Unable to trigger pxi-5105 exported signal pxi-4461

  Hello

  I use a chassis PXI-1033 with a PXI-4461 (daq) in slot 2 and 4-PXI-5105 in slots 3-6.  I want to use the 4461 to export a reference trigger signal to of the 5105, but when I try to run my program I get the following error:

  Error-89126 occurred at DAQmx Read (Analog DBL 1Chan 1Samp) .vi:1

  Possible reasons:

  Trigger line asked could not be booked because it is already in use.

  Property: RefTrig.OutputTerm
  Property: RefTrig.Pulse.Polarity
  Target unit: PXI1Slot2

  Task name: _unnamedTask<89>

  The Subvi I use to export the signal is built off an example I found.  At the moment it is only under the scope of my code mode (I'll take care of the datalog part later).  I'm not sure what I'm doing wrong, any help is greatly appreciated.

  Thank you

  John

  Hi John,.

  T Clk select a PXI_Trig lines used to deliver pulses of synchronization between devices.  Since that you configure T - Clk before configuring the signal to destination, the driver doesn't know that you plan to use PXI_Trig0 to export the reference trigger.  I guess that's to select PXI_Trig0 as the line to book the pulse of synchronization.

  I recommend that you try to export the signal to one of the other lines PXI_Trig - this should I hope to correct the problem but keep inform us if it is not.  Thanks for posting and have a great weekend!

  -John

• PXI-4071 sampling too slow when using a hardware trigger

  We use 3 PXI - 4071 s in parallel to measure with accuracy of high voltages. The program is written using LabVIEW 8.5.1.

  An additional test condition has been added which requires the use of a quadrature decoder and the synchronous DMM.

  We thought it would be simple, using backplane trigger 0.

  However, something odd happens.

  With a low-cut VI that uses a single DMM, we get 100 microseconds time to sample running with internal triggers. However, if the overall relaxation or trigger of the sample is set to TTL0, the sample time becomes so 5.1 milliseconds. It seems very strange that even just definition of overall relaxation, expected to affect only the time of the first sample, not the time between samples, has that effect. The plug for the DMM also said, that the maximum trigger rate is of 6 kHz.

  We have confirmed this reported sample time is independent of the speed of the clock actually connected to TTL0. If the clock is faster, it gets the reported sample time. If it's slower, the samples occur on the edges of the clock.

  Does anyone know if there is a parameter that has a default that changes based on the source of command and can be changed to work around this problem, you?

  I found the solution to this.

  Over time the value-1, the DMM uses a short value (less than 100 US) to set hour when, in modes triggered internally. However, he used much longer (about 5 ms) when the value - 1 and with the help of a hardware trigger.

  If the running-in is set to 1e-5, i.e. 10 microseconds, "the estimate" returned for conversion period goes from 5.1 ms 100, we and conversions actually occur at a rate set when clocked with trig 0-5 kHz

• RTSI PXI trigger

  Salvation;

  I have an SMU-1065 with the following modules: PXI-6529, PXI-6280, PXI-5114, & PXI-6713. I have 3 questions:

  1. how the RTSI is launched?

  2. how this trigger can be monitored?

  3. How can I create a task is triggered RTSI?

  I'm fairly new to LabVIEW but I work with other more experienced programmers.

  Thanks for any help.

  4BoysDad

  Hello 4BoysDad,

  Before talking about your questions, I will provide some information about the cards you because I think it will help me to answer the questions completely. First, the PXI-6529, the PXI-6280, PXI-6713 uses the DAQmx driver but the PXI-5114 is a digitizer and uses the driver NOR-Scope. Knowing this, I would focus on the passage of relaxing between 3 maps DAQmx first before thinking about the PXI-5114.

  At the same time, you have an SMU-1065 chassis. With this chassis, there are 3 segments of trigger bus essentially dividing backplane. If one of these cards is in a different segment, you'll have to correct bus together segments to spend relaxation through the bottom of basket. To see how backplane it broken up, please look at the Datasheet for the SMU-1065. I would recommend that you put them on a PXI trigger bus segment.

  With that in mind, here are my answers to the questions:

  1.) how is initiated the RTSI trigger? How to create a task is triggered RTSI?

  Before doing so, you will need to select a master device to the other slave devices. If the master device is a DAQmx device and you are passing to an another DAQmx slaves, here's a example of how to implement this. The relaxation will be initiated by the master device and in this example, the trigger is a beginning arm (for more information about this, please see the DAQmx help). Looking at this example, the RTSI trigger is managed in the synchronization of tasks - Trig Skew correction. With outbreak RTSI, this VI also allows you to synchronize the clocks of reference for each of the devices. Given that this example provides detailed notes as well as step-by-step instructions how it works, I will not repeat the information here.

  If you want to synchronize the card extended with DAQmx device or multiple devices, you will need to export the signal to the other card. This example explains how to implement the scope as a master and the DAQmx device as slave. As others explain, it provides a general explanation how to achieve this as well as step by step instructions how to implement this.

  2.) how this trigger will do?

  Regarding surveillance of relaxation, I looked in the DAQmx and the pilot of scope but also consulted with my colleagues, and it is not a function, we found who will tell you that the shutter has been sent. We found one way to check this is to use the timeout for task/sessions to see if they started. If they have not the trigger has not yet been sent to the other device. You are looking for this feature for debugging purposes or will you for use in your program somehow?

  If you have other questions about this, feel free to post.

• PXI-6562 Multiple trigger

  Hello

  I'm trying to trigger the capture of the PXI-6562 with multiple PFI.   Since I did not extract the available channels, I can't use pattern trigger.  My idea is to have PFI0 and PFI1 as a trigger. So, the DIO card begins to capture data when PFI0 = HI and PFI1 rising edge.

  I don't know if the PXI-6562 is able to do. I just want to avoid the construction of any additional hardware.

  Thank you!

  Andy

  Hi Andy,.

  Unfortunately, the PXI-6562 does not support the combination of trigger for the acquisition of the PFI lines you describe.  A trigger pattern to achieve match but only if you use a combination of the DIO lines.  Otherwise, for the generation, perhaps you could implement this with two separate script triggers and a condition statement.  For you the request, I would recommend using a simple gate circuit to let the relaxation through when the other line is high.  A door AND would also work.

  I would like to know if this helps, good luck!

• How can I use my PXI-6115 meter analog signal trigger to generate pulses of frequency

  I work on a PXI-6115 DAQ card and want to using the analog signal to trigger the counter it's generating frequency pulses. The manual says the analog trigger is supported, but I can't use an analog signal to trigger the start of work, in the test, I use the counter 0 to generate pulses and use the signal input port analog trigger PFI 0, can someone tell me what it is? My test VI. & error message appears in the attachment.

  Best regards

  If you read the error you can see digital triggers are the available trigger only when you use the output of the counter.

  You can work around this by setting up a dummy analog input task which will trigger an internal digital triggering when he sees the right analog trigger.

  See this thread for more details:

  http://forums.NI.com/T5/LabVIEW/DAQmx-start-trigger-analog-edge-VI-keeps-returning-error-200077/m-p/...