Redeclenchables buffered count task of edge

Hi all

I worked on 'Buffered Retriggerable counting task dashboard' on a single window input channel, let me describe what I want to achieve:

Create a CI to count the rising edges finished with the (for example external sample clock Dev1/di/SampleClock) at some rate of sampling and CI.edge.Term together in a PFI which is wired to another channel of digital input. In addition, I would like to define "start redeclenchables trigger" for this CI by another PFI line.

It turns out that I can put only 'arms start trigger' on this channel of entry of the counter, instead of "start trigger" since the 200452 error: attribute not supported in the context of task showed up at the beginning of digital edge trigger configuration. It seems that I can put only 'start redeclenchables trigger' on output special counter and use two counters to reach above, but I was wondering if there is a way to accomplish through single window. Any suggestion is appreciated.

Set the THIS ongoing task - it won't take samples when the task finished di which is actually the same thing as having a task over redeclenchables CI triggered.

If you want the count to reset each trigger, you could configure the entry as a Reset counter line well trigger.

Best regards

Tags: NI Hardware

Similar Questions

  • NI9403 for counting of pulses

    How to use the NI9403 module for counting of pulse device? We test engine GE ECM and provides a signal of 32 pulses per revolution.

    Hi Change_Air,

    In short, you might want to consider another module (probably a 9401 or 9402 according to the type of desired connector and/or the number of lines required).

    Modules with 8 lines or less (e.g. 9401, 9402) use a dedicated line to transfer the data from each of its inputs on the chassis backplane and are therefore capable of routing of external signals such as timing/triggering signals (for example one of the counters on a backplane cDAQ).  However, modules with more than 8 lines must transfer the data serial to chassis backplane and so tickets are not available for routing.

    Assuming you are using a bottom of basket cDAQ newest (any carrier except the x 9172 or 916 cDAQ), from 9.3 DAQmx you can configure a sample clock and acquire a digital input buffered on modules that transfer data in series (I think the 9403 can taste up to 1/7 US = ~ 142 kHz).  So you could end up with a table in the data buffer (for example [0 0 0 0 0 1 1 1 1 1 1 0 0 0 0 1 1 1...]) which you could then analyze to determine the number of edges.  Of course, the impulses must stay high for at least a period of your sample clock to ensure that you are able to detect.

    If you're on cRIO you could set up something similar, but the same restriction applies always - the limit is the maximum rate that data can be transferred in series of the 9403 inside of basket.

    Thus, although it is probably possible to get what you want with the 9403 (according to your pulse width), a "parallel" module would be much more effective in the detection of the short pulses (if it was a requirement) and would be simpler to program as well - you could just set up a task of edge with a meter count (assuming that the cDAQ).  There's a Developer Zone article containing a list of all series C, but it seems to be incorrect for several modules (perhaps an employee NOR will see this) about the nature of the series/parallel data transfer for the DIO modules.   I am not aware of any exceptions (and do not think that there should be none) to the rule that modules DIO with 8 lines or fewer are 'parallel modules' and DIO modules with more than 8 lines are "serial modules" (there are rows of data exactly 8 connector d - SUB between each module and chassis).

    Best regards

  • Traditional DAQ against DAQmx Counter

    I'm trying to convert an existing legacy application written in LabVIEW LabVIEW 2012 6. I have a problem with a traditional Daq counter. Specicically the VI "event or time meter Config.vi. In the attached VI, you can see that 1 meter is configured to count the cycles of an internal signal, not a PIN counter SOURCE signal. This configuration generates an integer for each cycle of the internal signal: every 10 microseconds in this case. I can't find a way to replicate this feature in DAQmx. I use a DAQCard-6062E (PCMCIA Slot) card in a Dell D620 Laptop. I tried to attach a fully functional VI, but get the error 'the content of the attachment does not match the type of file.' to fix this I had to fix a JPG image. I've included comments in VI to clarify things. Any help appreciated. Thank you.

    In DAQmx you can achieve the same result by setting the terminal entrance for a task of edge to the time base County internal 100 kHz:

    The 100 kHz Timebase is considered to be a "Advanced terminal" (don't get started me on the topic) so see in the dropdown menu, you must right-click on the control / constant and select the appropriate name of I/O filtering option.

    Best regards

  • the use of two meters: one for the generation of regenerable impulses, one as a counter

    I'm new on use the counters. I use an NI PCI-6110 multifunction data acquisition card. I want to count a digital input (on the connector of the PFI 2) pulse and also using the entrance to trigger another counter to generate impulses. So I configured the first counter (task 1) to generate digital pulses with PFI2 as a source of relaxation and redeclenchables award; and set up the other counter (task 2) to count the number of edges of the digital signal with.... But after the two tasks began, the first task was an error 50103 (or the possible reasons: NI Platform Services: the specified resource is reserved.) The operation could not be performed as indicated.) The block diagram is attached. Thank you.

    Your Board uses very-old-in-electronic-standards-DAQ - STC a smart meter that requires a little secretly * two * counters work together to make a finite pulse train.  He is not actually secret if you read the right parts to the right documentation, but it's not hard to miss if you are unsure you should look.  It has been a while since I've done a lot with these counters, but I have this nagging thought that they may not support redeclenchables finishes pulse train generation at all.  I would caution you to at least check this.

    In any case, it is the reason for the error.  The finite impulse generation task uses only the counter that you specify, but there was also this one to help.  A couple of new generations of smart meter (NOR-TIO, DAQ-STC2) continues to have this limitation, but the * more * recent it is no longer made.

    X series boards use the chip "NOR-STC3" that give you 4 programmable counters by the user instead of 2 * AND * everyone can generate pulse trains finish without using a help desk.  You may want a pair of them upward with your 6110, assuming that you need simultaneous sampling analog 6110's capabilities.

    -Kevin P

  • redeclenchables strange behavior digital output

    I created a redeclenchables digital dashboard task (finished) digital output as follows: (in DAQmx C)

    DAQmxCreateTask("",&_taskHandle);
    DAQmxCreateDOChan(_taskHandle,"/Dev2/port0/line6","",DAQmx_Val_ChanPerLine);
    DAQmxCfgSampClkTiming (_taskHandle, "" / Dev2/Ctr0InternalOutput ", _clockRate, DAQmx_Val_Rising, DAQmx_Val_FiniteSamps, static_cast (_sampleCount)");
    DAQmxCfgOutputBuffer (_taskHandle, static_cast (_sampleCount));
    DAQmxCfgDigEdgeStartTrig (_taskHandle, "/ Dev2/PFI4", DAQmx_Val_Rising ");
    DAQmxSetStartTrigRetriggerable (_taskHandle, true);
    DAQmxWriteDigitalLines (_taskHandle, static_cast(_sampleCount), FALSE,-1, DAQmx_Val_GroupByChannel, _pDigital, NULL, NULL);
    DAQmxStartTask (_taskHandle);

    sample clock:

    DAQmxCreateTask ("", & _taskHandleCO);
    DAQmxCreateCOPulseChanFreq (_taskHandleCO, "/ Dev2/ctr0","", DAQmx_Val_Hz, DAQmx_Val_Low, 0,0, _clockRate, 0.5 "");
    DAQmxCfgImplicitTiming (_taskHandleCO, DAQmx_Val_ContSamps, _numSamples);
    DAQmxStartTask (_taskHandleCO);

    When I run the task without redeclenchables parameter, it output a correct signal. However, if I run with redeclenchables it out almost exactly 2 times faster than normal. For example, a pulse whose width of 10 ms became 5 ms and repeats again to be 2 pulses of 5 ms. This is repeatable, no matter how much or how fast triggers provided.

    My card is PCIe-6363. I do not know what causes this strange behavior, and I hope someone can help on this.

    Thank you.

    It disappears after reset configuration. Might be interesting for future reviews.

  • using counter on NI 9401

    Hello

    We ordered the cRIO 9035 system with several Modules.

    One of them is the NI9401.

    I want to use this module to count the pulses of a flow meter.

    In front, I am a beginner and started just look at a lot of tutorials and created Basic VI

    1. This Module has onboard counters, or is it only possible to use the 'material' - counters in the chassis through this Module?

      I ask this, because I can put the Module via "Digital specialty Setup" as a counter.
      If I do, it would be possible to simply create a while loop, place the channel on the inside and tie him to a digital item?
      Or is the only way to count impulses (rising edge) to use VI as the 'edge counter VI' the example of VI?

    2. My flow meter uses a Hallsensor and produces rectangular pulses at 40 Hz max.
      It is absolutely necessary to use a FPGA or can I use a VI on the host computer?

    We use 4 of these flowmeters (and many more sensors like Termocouples (NI 9211), solenoid valves (NI 9482) or a AKD-servomotor (NI 9472).)

    All the measured data should be written to a file (for example, form exel).

    Magnetic valves must be triggered if a certain number of pulses is counted.

    Yet once, it is absolutely necessary to use a FPGA or can I use a VI on the host computer?

    I know there is a lot to do and I have to learn a lot more, but I'm on it (its for my Masterthesis).

    For now, the answers to questions about existing or not existing edge counter would be great.

    Thank you for your support.

    Greetings from the Germany,

    Lukas

    Lukus salvation,

    Greetings from Munich (since it is a public forum, I am obliged to answer in English, in any case).

    (1) when you use a cRIO you don't have a strict meter limitation (especially if you program the FPGA) for your digital inputs. Maybe read you something about that and that only applies to the cDAQs (because he (mostly) counters come from cDAQ chassis so they are more limited)

    "If I do, it would be possible to simply create a while loop, place the channel on the inside and tie him to a digital item?"

    FIX

    "Or is the only way to count impulses (rising edge) to use VI as the 'edge counter VI' the example of VI?

    I'm not sure which exact VI you are referring to, but on the FPGA you could implement a custom counter. That would work too.

    (2) you can do two ways (Scan Engine Mode and FPGA)

    If you write a master's thesis, you may be eligible for a greatly reduced price. The course Embedded Control and Monitoring (http://www.ni.com/training/embedded/) would be very useful for you:

    Forderprogramme as research, training und Lehre - National Instruments Germany GmbH
    http://Germany.NI.com/academic/training/programs/diplomand

    Best regards

    Christoph

  • A new attempt of an individual doesn't have a process task for all users of the IOM

    Hello

    We use IOM 11.1.1. One day, one of the systems was not available so all tasks in process for this system failed for a number of users. Is it possible to view the task process has failed and retry them together, there are more than 3000 users and it is not possible to pass by one by one.

    Any method via the console or programmatically do would be very useful.

    Thanks in advance.

    --
    UZ

    The ITO table has all the rejected task information. You can use it to bind to the user and the instances of the resource through the table Ouedraogo as well.

    You can then take the SCH_KEY and then use code like this to deal with them:

    public void completeTask() {}
    task of long [] = new [long] {123123,3242134,23432,43534,34656,456456};
    int counter = 0;
    for {(clé: travail très long)}
    try {}
    counter ++;
    provIntf.retryTask (key);
    System.out.println (counter + "|" + task.length);
    } catch (Exception e) {}
    }

    }
    }

    -Kevin

  • Triggering off the coast of beginning of Pulse Audio in question DAQmx...

    Hi guys,.

    First of all, it is more a matter of software than hardware, so I didn't post this specific question in the multifunction DAQ card...

    So I'll try to trigger an acquisition finished off the start of a pulse audio, however I have audio sync issues, due to the fact that it can be started before my VI runs. As noted below, the audio is generated and pulsed for 500ms on and 500 ms off the coast, and between these periods, a digital pulse is generated this way (shown in red). I have a problem to stay synchronized, due to the fact that I samples finished for 1 second of a data value, and if the USE EEG is faster than me, I can catch the pulse audio at Midway, rather than at the beginning.

    I'm trigger analog outboard of a sound signal of 50mV and capturing two audio channels simultaneously and consistently captures 3 digital channels when they receive the trigger of the beginning of analog input trigger reference digital edge. If digital are slaves and audio is the master in this configuration. The point of this is to get a delta timed material at the time rather than use the timestamps of windows.

    As I said, I use an Analog Edge Trigger Start to start my purchase, what triggers the digital task Digital Edge Start Trigger to start as well. How can I make sure that I start at the BEGINNING of a new pulse audio if I get out of sync, I can't understand this logic... Analog edge goes off just when it goes to the specified level, but maybe it's at half way through the 500ms pulse, so this is my problem...

    I need to be a trigger to start because I do 55 000 this test iterations in a QMH Prod/consumer model and need relaxation to be redeclenchables and start-up is only redeclenchables.

    The variability in timing you see at points 2 and 4 somewhat dictate against the possibility to set up a re-triggering precisely timed by the hardware configuration.  I think that you need to abandon the idea of making repeated sampling finished back to back and switch volleys in a mode of continuous acquisition and treatment.

    To help with this, I aim to capture the moments of digital via meter rather than DIO pulses and be ready to give up the acquisition rate noise much (if necessary) given that you said that your main concern is to distinguish between ON and OFF.

    I must configure the counter to use the Digital pulse as a sample clock and use the sample clock signal HAVE the "time base", i.e. the signal which the edges will be counted and buffered in memory.  This will give you 2 samples per second instead of 5 M and the values of the counter at these sampling points is the index in your AI data which occurred impulses.  Pretty neat and clean.  Just be sure to start the task of counter in front of the task to HAVE it.

    -Kevin P

  • Hardware timed CI/CO, operation of PCI, I / AO with specific execution order

    Hi all

    I work with a USB-6361 NI data acquisition hardware and I'm writing a LabView 2011 program which sends a signal to my output device and reads several values of various measuring devices. I have a ramp voltage signal (in a table format) and I need to sequentially send the elements of this array on my AO device with very precise timing (ideally timed material). As soon as the value is written to the device of the AO, I need my tasks HERE and CI to record all available data and my task to send a single impulse before the next array element is sent to the device AO. All this needs very precisely timed such that if I perform a measurement on 1000 points in my table of ramp with a timing of 1000 Hz, the program will have exactly 1 sec. to run (less overloading caused in initialization and closing tasks) and produce a table of data consisting of 1000 steps of AI and CI. I had initially tried to achieve this by using a structure of sequence within a timed loop software, but because I won't get into multiple channels of Amnesty International and CI and tables of data, this has proved to be excessively slow. The other danger that I fear I could run is the case in which the LabView program runs more slowly than the process of acquisition data itself, thus causing data to write to the buffer and the measures being lost.

    I didn't spend a lot of time working with the procedures, timing and synchronization, so I apologize if this is a rather naïve question - I'm having trouble reconciling restrict them inherent software and order of execution with the hardware timing. What is the best way to solve this problem? I can only think of two reasonable approaches to the problem:

    (1) should I try to trigger my CI tasks and HAVE run on the completion of the task of the AO (and if so, how)?

    (2) I have the CI and tasks run on a separate clock with a start delay initial light as to compensate for these tasks if they occur reliable after that each value AO is sent to my device?

    Finally, I build an identical for a real-time embedded controller program of SMU-8100. The approach will be different in this case?

    Thanks in advance for your answer.

    I can give you an overview of the steps you'll need, but be ready to spend experiment a little time and some of these individual pieces of troubleshooting before you put them all together.

    First of all, a X-series 63xx allows all you need to accomplish a very precise synchronization in hardware.  When you then switch to a real-time controller, you must include an X-series device in the chassis to maintain this capacity of equipment.

    Second, 1 kHz is not yet a challenge to LabVIEW to catch up with your hardware, even with powered lower RT controller.  You just need to program the DAQmx tasks to let the hardware & driver do most of the work.

    1. I would dedicate a counter of the 6361 to generate the clock shared for other DAQmx tasks.  I tend to create a clock and operating cycle of 90-95% for this type of application of stimulus / response to the response time & maximum stabilization.  Generate the stimulus at the cutting edge of the clock and gain response data on the edge of leak - before the next sample of stimulus.  Call it the task of the clock.

    2 set up a buffered AO task that uses the output of clock as the sample clock. Configure the polarity to be sensitive to the cutting edge (usually, this will be a rising edge).   Start the task AO * before * starting the task of the clock.

    3 configure tasks HERE and CI to use the output of clock as their clocks in the sample.  Configure the polarity to be sensitive at the trailing edge.  Start tasks I and CI * before * starting the task of the clock.

    4. the output pulse should be a task of meter output, configured to generate a single pulse redeclenchables.  Configure it to use the leading edge of the clock as the trigger signal output.  Set the time of 'low' and the 'initial period' to equal precision<1 msec="" delay="" you="" want="" to="" make="" sure="" that="" you="" get="" the="" same="" timing="" on="" every="" trigger.=""  be="" sure="" the="" high="" time="" allows="" the="" full="" pulse="" to="" fit="" within your="" clock="">

    5 examine the "producer-consumer" model so that you can separate your data from your CQI data processing.  You should stream to file continuous rather than it accumulates in large networks.  Write speed of file can be unpredictable, this is why access to the file must be in a separate loop that acts as a data consumer that the loop of CQI data produced.  When you spend real time, assign a lower priority in the process of writing file.

    -Kevin P

  • Multichannel synchrobized meter output daqmx c#

    Hello

    I am facing the following problem:

    I'm a piezocontroller operating to move a microscopic sample. The piezo allows me to scan XY of the sample areas. At each position analysis (to each "pixel"), I count photons for the image of the sample. Photon counting is a simple measure of pulsewidth and isn't important here.

    What is important is that I have two types of piezo controllers in different configurations. A controller is digital and I can send the coordinates of the area to be scanned. The controller then allows me to define 4 output triggers to synchronize movements piezo with other operations such as opening and closing of shutters, photon counting after each pass of the step to a new position etc...

    However, the second controller is an analog that only allows me to adjust the tension to move the scene. If I want to recreate the functionality of the digital controller I need to create four trigger lines myself.

    So, my solution should look like this:

    (a) I have a "clock" that ticks with a cycletime of 200 microseconds. At each tick of the clock tension in my piezo for X and Y motion are incremented. Master clock ticks are also triggers for the photon counting tasks at each position.

    (b) the firing in four, used for various purposes, should behave as described in the two attached screenshots (pictures say more than 1 million words!). If for example it takes 1000 the master clock ticks to complete one scan line, then the line 1 trigger should for example be placed high the first 500 ticks, trigger line 2 should be high ticks the next 500 while line 3 trigger must be high all the time. This behavior must be repeated each line scan etc etc...

    Is it possible to have this kind of coordination between the output of 4 meters to say, an edge of 6601?

    Any help would be greatly appreciated!


  • Analog pulse of a photon multiplier tube

    Hello

    I am trying to establish if it is possible to count random negative analog impulses of a tube of multiplier of photon (PMT) with multifunction data acquisition OR or boards of counters/timers?

    First of all, the properties of the PMT output are as follows (single photon response):

    • 1.5 ns FWHM

    • -50 mV to 400mv (random because of the amplification process in the PMT)

    • Up to 5 million pulses per second (higher cause the overload sensor) who arrive at random times.

    I would like to do is make the counting of simple events or events buffered count.

    All counters seem to only be able to count digital TTL pulses. In this case, I have some electronics in mind which will convert the pulse the pulse of positive 5V CMOS logic (which, according to this site, is suitable for counter inputs) external signal conditioning. It also contains a dicriminator circuit to ignore the pulse below a threshold. With this signal, I intend to send to a meter entry NI USB Multifunction DAQ BNC for counting of events event / buffered.

    However, in the hope to reduce the cost of my system, I was hoping it could be a way to define an analog trigger to create a pulse TTL of one of the of cards OR, therefore quite dodge the need for external signal conditioning?

    Any help would be welcome.

    Kind regards

    Sean

    You may need to strech the pulse to meet the minimum of the input of the meter.

    I know you want to do without extra signal conditioning... However, we are building a signalconditioner to our task with a comparator MAX961ESA provided... 5V-driven layout is in the technical sheet

    As a simple pulse strecher, I would try a simple low-pass RC before the entry comparer.

  • Eccentric MAX program?

    Sorry if wrong forum. I tried digital I/o, but no answer & I can't find a forum for MAX.

    I have a problem with a client computer which houses PCI-6071e & PCI-6043. In MAX test panels.

    I have lines of encoder quadrature clinging to PFI0 & PFI1. If I go to the counters, for number of edge, trigger = PFI0 (or PFI1) I count when I turn the encoder. But if I go into digital I/o I get no response from the encoder. All 8 lights remain lit.

    Tried it on another machine (with USB-6211) it works fine.

    MAX or drivers are right divide? Not possible to have good counters and signals through the PFI is bad, right?

    Walter donovan,

    I think you misquoted your second DAQ device model number - I do not think that we do a 6043.

    If you want to use a map of series E (6071E) with a quadrature encoder, you will have to plug a little differently. Most of quadrature encoders have at least two signals of the pulse output (and possibly a third, which is the output of the index). These two impulses, A and B, must be connected on the DAQ counter input source (PFI3 for PFI8 for Ctr Ctr 1 or 0) and the P0.6 of entry respectively. So I recommend that you configure a fast edge counting task to the MAX to verify that this configuration works ("outwardly controlled" use for management).

    The reason for which he worked a litte differently with your other card (USB-6211, M series) may be that the two card counters are different. M series supports the features of NOR-TIO meter, such as the separation of the two edges and quadrature encoding, and E series does not (for other differences, see this article). However, you can still use your card in the E series with a quadrature encoder as I've described. For more information,.

    The use of quadrature encoders with DAQ of E cards series

    I don't think that anything that is wrong with MAX or your drivers. The lights may or may not reflect the signal on your digital inputs according to the speed of the train of pulses from your encoder.

  • Encoder with PCI-6122

    Hello

    I have a card PCI-6122 and I would use one of the counters like angular encoder, but I got the code of error-200431. Is it possible to use this map against as encoder?

    Peter:

    Two main ideas:

    1. If you have unidirectional movement, you could set up an edge counting task and do your own conversion of angle.

    2. you should be able to configure your task to HAVE to use a digital TTL input as its sample clock signal.  If your encoder signal is TTL,

    It wire pins of the PFI input card and configure the task of the AI to use this entry PFI as the sample clock.   Furthermore, cela

    makes the edge with a little pointless, as the number of samples captured by the task to HAVE it * is * edge County.

    -Kevin P

  • With the help of the cDAQ timers to repeat an impulse of finite samples clocked by train clock material

    Hi all

    A complex project I have to implement an interface acquisition of material for a linear motion sensor using the output of the synchronous serial (SSI) commune in the control of the industrial movement. (I have a bit of experience in digital electronics, but I'm new to hardware synchronized timer e/s digital in LabVIEW).

    To do this, I need to create a clock timed by the busted hardware signal pulse train TTL. Each burst consists of 25 down transitions, with a period of complete cycle of 2.67 microseconds (375kHz). The output is then held high until the next outbreak, that produce at 1ms intervals.

    Using of cDAQ timers and a NI 9401 (based on the example http://www.ni.com/example/30256/en/), I was able to create the pulse train burst as described (see attached image VI). Then I need to configure another timer to set off this explosion to repeat at 1ms intervals.

    Someone at - it guidance on how best to accomplish the hardware timing for the repetition of the pulse train?

    Any suggestions of alternative strategies or observations about the way that my noobish code is stupid or ineffective are welcome as well!

    Thank you!

    Hello RyanBiggs,

    You will need to perform the following operations based on the code that you have joined.

    1. Set up a second output continuous counter task which will give an impulse to 1000 Hz.
    2. Set up your first task of meter output to start according to the configuration in the first step using the vi DAQmx trigger.
    3. Configure the first task of the meter output to redeclenchables via the property node so that the output meter pulses when he sees a rising from the second task of meter output.

    The implementation is shown below.

    Kind regards

    Izzy O.

    Product Support Engineer

    NI.com/support

  • signal analog aperiodic acquisition

    Dear Sirs,

    Excuse my English, this is not my mother tongue, but I can't get help on the forum in my language.

    I have LABVIEW courses are 2 but have not taught on DAQmx acquisition. I use LABVIEW2011, a card/CB68LP connector OR PCI-6229 and I want to buy an analog signal that should be considered as non-periodic.

    An engine is spindling to nominal 20 Hz with an uncertainty of 20%. 2 ara attached to this engine sensors and send digital signals:

    S1-> 1 rotation, reliable signal (f1 ~ 20 Hz)

    S2-> 1024 teeth in 1 revolution (f2 ~ 1024 * 20 Hz), but must consider lack of opportunity to teeth

    The analog signal must be acquired for periods of 20 or 40 (counter on S1) on every edges falling from S2 and I want to store each value with the time in microseconds (relatively at the beginning of the acquisition) and the index of the counter on S1. Is it possible to do without switching to LABVIEW RT?

    Have managed to acquire an analog signal from a function generator, I am unable to go further.

    Any help would be welcome to Setup Wizard DAQmx on these points:

    -Dev1/analog ai0 must be triggered by inputs of S1 or S2 PFI, trigger of reference? Advanced settings of the timing?

    -counter County entry/edge on S1?

    -line input / digital for the S2?

    Thanks in advance for your help,

    Stone

    The Basic (from the task) configuration would look like this:

    Task 2 and 3 are indeed very similar, using a PFI line for the source, while the other uses the time base of 80 MHz (or some time base internal you prefer).

    Best regards

Maybe you are looking for