NiFgen Export Signal

I am using niFgen Export Signal with LabVIEW 8.6F. I am trying to set up a software trigger and route it to PFI0 on a PXI-5421 AWG, however, I keep getting the error "Invalid value for signal name" when using any of the Defined Values as found in the niFgen Export Signal help menu under "Signal", specifically "NIFGEN_VAL_START_TRIGGER". I cannot find any niFGEN VI examples that contain the niFgen Export Signal VI. Might anyone have any exporting trigger example VIs that I could take a look at? Is there a primer somewhere on trigger set-up? Thanks.

Hi pfast21,
I believe a software trigger does not need to be routed. For the niFgen Configure Trigger VI, the Start Software Edge version does not require a Source input while the Start Digital Edge version does. If you want to send a software trigger, you use the niFgen Send Software Trigger Edge VI. If you need to use a digital trigger, then you would not need to export the signal. Instead, you just point the trigger VI to the source.
You can find more information about configuring triggers in the NI Signal Generators Help file. This can be found at Start->All Programs->National Instruments->NI FGEN->Documentation.
Regards
Josh Y.
Applications Engineer
National Instruments

Similar Messages

Can I use the 'Export Signal Property Node' on a quadrature encoder?

Hi,
So I don't know which counter board I'd be using yet for this (it's used in conjunction with a PCI-6280--the PCI-6280's counter inputs are all taken and so I need another board), but assuming this is possible at all in DAQmx I wouldn't mind knowing whether, say, the PCI-6601 (or any other timer board for that matter) could do this. I'm programming this in LabVIEW 2010 by the way.
I want to have a counter which counts the number of pulses on one channel (I'll call this the 'clock' channel) between when another channel goes from low to high (which I'll call the trigger). It's basically a pulse width measurement, but I only care if there are more than n clock pulses between triggers. I need to have a hardware-timed digital signal which goes from low to high if there are ever more than n pulses between trigger changing state from low to high.
What I am planning to do is this:
Wire 'trigger' to the z-input of the quadrature encoder, and set the z-input value to some arbitrary large value such that, at the quadrature encoder counter task's settings, the counter reaches terminal count in n pulses.
Configure the quadrature encoder counter using DAQmx Export Signal Property Node (tutorial I was looking at is here: http://zone.ni.com/devzone/cda/tut/p/id/5387 ) to toggle a digital channel ('counter event output') from low to high if the counter reaches terminal count (ie, if the encoder reads n pulses).
If the encoder ever reads n pulses on 'clock' between two rising pulses on 'trigger', it sets counter event output high.
Is this possible? Reading through the manual of M series PCI-62xx devices, the index pulse loads the counter with a particular value so it seems like you could conceivably set the counter to the terminal count if you wanted. My only real problem is whether DAQmx Export Signal Property Node works on all counter tasks or just on edge counting tasks.
Thanks in advance for your help. If this isn't possible, I can reply with more details on the problem this is supposed to solve so that you can help me figure out an alternate method.
Solved!
Go to Solution.

There is probably a way to do it, but it it may be easier to use an X-series board for the job. They support a new counter capability for count reset on a digital edge without needing to be configured in encoder position mode. I am not sure exactly how that feature's been implemented however, so maybe it won't make things easier after all.
The plan based on the hoped-for behavior:
1. Configure an X-series counter for pulse generation based on "ticks" of your clock channel.
2. Set both initial delay and low time to the critical # of ticks.
3. Configure for count reset on a digital edge (if possible in pulse generation mode)
4. Configure the count reset value to be the critical # (or possibly 1 less, if possible in pulse generation mode)
5. If you want the output to remain high indefinitely, configure the counter task to use its own output as a
pause trigger, and pause while high.
The way pulse generation works is to preload a # of "low time" ticks into the count register. Then every source edge will decrement the count. When the count reaches terminal count (0), the counter's output is toggled (or can be configured to pulse). The register is then loaded with the # of "high time" ticks and the process continues.
You would be perpetually interrupting the count-down process as long as you got your triggers in time. The count would keep getting reset to the # of low counts, keep decrementing toward 0 without reaching it, and so on. If ever you did reach 0, the output state would toggle high, then the high state would prevent subsequent clock signals from decrementing the count.
You can conceivably do a similar thing with a 6601, but I'm pretty sure you'd need 2 counters working together to get it working.
-Kevin P

How to determine exported signals?

Hello All,
I'm programming the 6602 using the DAQmx 7.4 ANSI C API. I was wondering if there is a programmatic way to determine which signals have been exported within a task? The purpose is to provide access to the exported signal attriburtes when a task is being loaded from MAX via DAQmxLoadTask( ).
Jeff

Hi Jeff,
The "DAQmxGetTaskChannels" function will return the list of physical channels within the task. Also, the "List of Channel Properties" section lists functions that will return specified attributes of channels. More information about both of these functions is available in the NI-DAQmx C Properties section of the NI-DAQmx C Reference Help. You can navigate to the help manual by going to Start>>All Programs>>National Instruments>> NI-DAQ>> NI-DAQmx C Reference Help.
Regards,
Hal L.

Ni 5122 export signal

Hi, all.
I am developing my own window application and thus using niScope API
My system accepts external digital trigger signal from a function generator 1 (DS345) through PFI line 0
and needs to import a delayed version of the signal to function generator 2 (also DS345). I tried to do this
by using the function niScope_ExportSignal and setting the parameter signal to NISCOPE_VAL_REF_TRIGGER.
I tried to observe the pulses generated on oscilloscope each time trigger is detected but I couldn't. Can anybody help me?

Joohnoon,
If you've configured your NI-Scope acquisition to look for a reference trigger (not a start trigger) on PFI 0, you can then also configure the session to route the reference trigger out to PFI 1. After the session is initiated and the board is waiting for a reference trigger, any subsequent reference pulse on PFI 0 will cause a "reference trigger" to occur and a pulse will occur on the output PFI 1. You can also route the trigger signal to your PXI backplane.
I hope that this is helpful. Please let me know if you have any follow-up questions.
Best Regards,
Alan L
Applications Engineer
National Instruments

Synchronizing multiple NI-5411s

Hello all,
I have a recent project that involves simultaneous generation of waveforms across multiple NI-5411s (PCI version). These 5411s will generate a set of waveforms continuously until the user stops the program.
My initial idea was to have one of the 5411 as a "master" device, which will output a start trigger pulse to the other three "slave" 5411s. The implementation will be similar to this example program here.
As I was looking around for alternative implementation / additional information, I found one possible alternative, where the "master" 5411 will send a SYNC pulse (not a start trigger) to the "slave" 5411s via RTSI, by using the "niFgen Export Signal" VI. Of interest is the option to output a "Synchronization Pulse" that promises "absolute synchronization between two or more signal generators (5404/5411/5431 only)." The "slave" 5411s will call the "niFgen Configure Synchronization" VI to read in the synchronization pulse. However, I am not able to find any related example programs in LabVIEW or on the NI website.
My questions are:
1) What is the difference between using a start trigger and using the "synchronization pulse"?
2) Are there any examples that demonstrate the use of this "synchronization pulse" to synchronize the generation of multiple 5411s?
3) Is there a benchmark that shows how tight the synchronization is for this "synchronization pulse", say versus a normal start trigger?
Thanks in advance!
Best regards,
Victor

Hi Victor
I think you are on the right track:
I have just one more question about the configuration - does this mean that instead of exporting the normal start trigger from the master, we export the synchronization pulse instead, and tell the slaves to use this as the substitute start trigger?
1) Configure 20MHz local clock from master to be shared with slaves for PLL.
2) Configure synchronization pulse to be shared from master to slaves on RTSI0 (for example)
3) Configure start trigger for all slaves on their RTSI0.
4) Start generation.
If you look at the section that begins with "To phase lock NI PXI-5411/5431 signal generators, complete the following steps" on the instructions that James provided here: http://zone.ni.com/reference/en-XX/help/370524R-01/siggenhelp/master_slave_operation/, it is pretty much as you are describing above except with PXI devices.
We should be able to do the same with PCI devices as follows:
Set the master device to send any valid Reference clock to the PLL reference input connector.
Set up the slave devices with the I/O connector as the PLL reference source.
Set the PLL reference frequency parameter to the clock frequency sent by the master. The devices are now frequency locked to the master.
To further phase lock the devices, set up the master to send the trigger signal on one of the RTSI trigger lines.
Set up the slaves to receive their trigger signal on the RTSI trigger line.
Set up the master to send the device_SYNC signal on the RTSI trigger line and the slaves to receive the device_SYNC signal on the same RTSI trigger line.
Start the waveform generation on all the slaves.
Start the waveform generation on the master.
Keep in mind that the 5411 was End-of-Lifed around 2008 and is based on our older software architecture known as TDAQ, so there is not that much example code floating around anymore (if there were even any to begin with).
Jason L.

How do you capture IQ data with RFSA vi's triggering from ext trg on digitizer?

I am trying to write an application using RFSA vis that will capture IQ data when triggered from the external trigger port on the digitizer card. This does not seem to be supported by the RFSA vis and I am not sure how to integrate ni-Scope and niRFSA in one application.

Hi Jltetzlaff,
The Clk in and Clk out ports on the 5142 can be used to input and
export a reference clock. You can import this as your sample clock
source over the Clk in by using a simple property node. This is
assuming your using LabVIEW. My main concern is regarding your clock.
If you take a look at page 20 of the reference manual here:
http://www.ni.com/pdf/manuals/374300c.pdf, you can see the PFI lines
follow a very specific digital logic specification (TTL). It looks like your
signal won't be recognized properly by these lines. The lines require
a voltage above 2.0V to register high. There is no minimum frequency
on these PFI lines. The problem is the logic levels. My
recommendation would be to export a start trigger with your AWG to
begin the RFSA session. If I'm misunderstanding the setup, could you
please give more details on devices (model numbers), development
enviroment (LabVIEW etc.), and what connections you require. From what
I understand, you want to sync the RFSA devices with the AWG and DUT.
Perhaps the session from the AWG that is generating the clock can also
export an event to start the AWG to start the RFSA device through PFI 0
or PFI 1. This can be done using the niFGEN Export Signals.vi. The
exported signals by this vi will follow the correct logic accepted by
the 5142 digitizer in the RFSA setup.
I hope this helps,
Paul C.

NI PXI-5421 PFI Port Output Usage

The NI-5421 Specs Manual (http://www.ni.com/pdf/manuals/371477d.pdf) says that the PFI ports can be used to send a trigger externally. I haven't been able to find a way to do this. I want to test the potential of external triggering with my device, but for the sake of convenience I would prefer to be able to use one of the PFI ports to send a trigger to the other PFI port, for simplicity of testing (no need for additional pulse generation).
Any advice is appreciated.
Thanks,
Billy Maier

You can use the niFgen Export Signal VI to route triggers on your device to the PFI line.
http://zone.ni.com/reference/en-XX/help/370524P-01/nifgenlv/nifgen_export_signal/
Regards,
Jason L.
Product Support Engineer
National Instruments

How to acquire analog signal and send a TTL pulse at the same time based on PXI 6123

Hi,
I am using a PXI-6123 data acquisition card, as the picture show in the attachment ,I want to acquire the analog signal of ai0 through reference analog window and at the same time send a TTL signal to trigger my camera. I have tried two methods, one is using the DAQmx Export signal.vi another is using DAQmx connect terminals, but when the data acquisition card acquire the analog signal, the DAQmx Export signal.vi and the DAQmx connect terminals sometime can send an TTL pulse ,sometime can not.
I don’t know why? or some other method that can achieve my arm is appreciated.
Regards
chunlei
Attachments:
method export signal.vi ‏21 KB
method connect terminal.vi ‏36 KB
Send a TTL pulse.JPG ‏288 KB

Hi,
Have things changed over the years?
I need to syncronise a digital output (Modul NI9474) and an analoge input (AI-Modul NI9203) module. I need to measure time intervals from a flank in signal A to a flank in signal B. I would like accuracies of the order of 1 ms. Currently, the signals are not synchronised, with errors of the order of 2 times the block length (block size x sample rate), sometimes much higher. The best I got so far was a block size of around 20 with a sample rate of 1 kHz.
If I use the master and slave settings on the RTSL settings, my program doesn't run properly.
If I use digital signals for input and output, I can syncronise them with RTSL settings and everything is good, but I can't always do that.
Also, if I do anything in the GUI (such as scrollowing something or going to another window), my output gets screwed up properly.
1. What can be done to synchronise AI with DO?
2. Is there something that can be done to avoid messing up the output when something happens in the user interface? (I know that I am messing up the outputs as they make some valves switch and that is loud).
Thanks in advance!

How do I export a counter from a task with multiple counters

Hi All,
I have a quadrature output VI that works 100%, outputting the frequency on the default pins (I'm using a NI-6284, so the default CTR0 and CTR1 pins are PFI12 and PFI13). During my development, I made a silly mistake and routed the encoder pins to PFI 12 and PFI14.
What I need is to move the signal from the PFI13 to PFI 14, which is supposed to be simple.
I've tried a few ways of doing it, including DAQmx dis/connect terminals (very clunky), and DAQmx Export Signal which gives me trouble because there are two counters in the task and the function can only export 1 counter.
Please take a look at the attached VI and let me know what solution I should implement.
Best,
Adrian

Hi S,
Thanks for the reply. I also came to that page, which is helpful.
What I've ended up doing is using the counter property node to specify the output pin of the counter that I need to move, and left the other counter at the default.
I'm not sure if this is the best or most elegant solution, but I haven't had any problems with it as yet.
I was hoping to hear from the community what the safest and most elegant solution would be, as the "Export Signal" VI looks like quite a nice option, but may well be overkill for my purposes.
Thanks!

How to export counter to rtsi?

I am generating a counter frequency out signal on a pci-6220 m-series card. I want to then share this signal with other cards over an RTSI line, and therefore, I use export signal VI. However, right after a computer reboot this VI will not produce a counter signal. If I then generate a signal using MAX, I can go back and run this VI fine until the computer is rebooted again. If I remove the export signal VI, then everything runs fine.
It seems like the inclusion of the export signal VI makes it not workafter reboot until it is initialized using MAX. I am quite confused.
Thanks for your help,
Pat
Solved!
Go to Solution.
Attachments:
laser trigger.vi ‏19 KB

Hi Pat,
Are you getting counter output on RTSI0 but not on PFI12? This sounds like a bug that was reported to R&D as CAR #44655 and fixed in NI-DAQmx 8.8. Normally DAQmx uses the value of the CO.Pulse.Term channel property (which defaults to PFI12 for ctr0) to control the counter output route, but exporting the Counter Output Event signal caused CO.Pulse.Term to be ignored. In DAQmx 8.8 and later, the values of both properties should be combined.
Why would creating a pulse generation task in MAX seem to fix the problem? When a DAQmx task routes signals to PFI lines, they stay routed until you reboot, reset the device, or reconfigure that PFI line for a different purpose (a different output signal, or an input).
If you're using 8.7.x or older, I'd recommend upgrading to the latest version, NI-DAQmx 8.9. If you can't upgrade, or if that doesn't fix the problem, I would try passing "/Dev2/RTSI0,/Dev2/PFI12" to the DAQmx Export Signal VI. Alternately, you could change your VI to create, start, stop, and clear a second task to emulate what the pulse generation task in MAX is doing.
Brad
Brad Keryan
NI R&D

Preventing a glitch during signal generation

I’ve got two high speed digital IO cards (NI PCI-6541) generating simultaneous waveforms, and I’m getting a 120 – 150 ns glitch from one during the generation process. The waveforms have ~ 200k samples at a sampling rate of about ~ 20 MHz.
For each board, I call this sequence of functions:
niHSDIO Init Generation Session.vi
niHSDIO Assign Dynamic Channels.vi
niHSDIO Configure Sample Clock.vi
niHSDIO Export Signal.vi
niHSDIO Configure Generation Mode.vi
niHSDIO Export Signal.vi
niHSDIO Configure Generation Repeat.vi
niHSDIO Write Named Waveform (1D U32).vi
niHSDIO Write Script.vi
niHSDIO Get Session Reference.vi
It’s the “niHSDIO Write Named Waveform (1D U32).vi” function that causes the glitch. I’ve run into a similar thing before and it was the signals briefly going to a high impedance state during an initialization call; is there some way to prevent that?

Hello All,
This issue was resolved by changing the initial state in the niHSDIO Init Generation Session.vi. The "glitch" occurred because the niHSDIO Init Generation Session.vi was configured to reset the device at the begining of the program. This set the device into a high impedance state. By changing the input so that the device did not reset we were able to eliminate the problem.
Matt Anderson
Hardware Services Marketing Manager
National Instruments

How to export from multism to matlab

I need to export signal (output of opamp ) from multism to matlab to calculate SNR
Solved!
Go to Solution.

fouda,
Have you considered using the native capability of doing LabVIEW based measurements directly in the Multisim simulation rather than an external math analysis tool?  Here is a LabVIEW VI that incorporates 2 methods of calculating Signal to Noise ratio (SNR) based on posts that have been done in the LabVIEW forums.
Here are the NI links describing the 2 slighly different methods used for calculating SNR...
Method 1 -> Reference: http://zone.ni.com/devzone/cda/tut/p/id/2058
Method 2 -> Reference: http://forums.ni.com/t5/Dynamic-Signal-Acquisition/SNR-measurement-VI/m-p/224168
There are some assumptions that are built into these calculation methods, so please look through the definitions for more information.
To use, place the contents of the zip folder in the folder "C:\Program Files\National Instruments\Circuit Design Suite 11.0\lvinstruments".   Relaunch Multisim and the SNR instrument will be available from the LabVIEW drop down icon on the right (or top) of the screen for use in your own circuit simulations.
I provided 2 simple Multisim v11 examples to try.
This instrument was created with LV 2010; to use previous versions of LabVIEW instruments, check here:
http://zone.ni.com/devzone/cda/tut/p/id/5639
For information on how to create your own Multisim VIs, check here:
http://zone.ni.com/devzone/cda/tut/p/id/5635
Enjoy!
Regards,
Pat Noonan
National Instruments
Attachments:
SNRv1.zip ‏1052 KB
SNR_Test_1.ms11 ‏35 KB
SNR_Test_2.ms11 ‏63 KB

Export "AI Convert Clock" of 4472 to a PXI_Trig line

i have 11 pxi4472 on the same pxi1006 chassis. previouslly, i routed the "AI Convert" signal of the master 4472 card to an RTSI line, so that whenever there is an A/D convertion it can be timestamped by another card listening to this RTSI line. i used DAQ originally and everything works fine.
recently, i rewrote all my code using DAQmx. but somehow when i use the "DAQmx Export Signal (Most Signal).vi" to export "AI Convert Clock" to a pxi_trig line, labview complains about a -200375 error: "Signal type requested to be exported is not supported for the specified task running on the given device". so seems like "AI Convert clock" is no longer valid in DAQmx? i tried every other signal that DAQmx allows me to e
xport, but nothing seems to be the right one.

To export the Sample Clock from the PXI-4472, use the DAQmx Export Signal property node. Specify the Sample Clock Output Terminal property (Clocks / Sample Clock / Output Terminal), and create a constant or control that specifies the desired PXI trigger line. During an acquisition, the sample clock will be exported as 100ns wide pulses at the specified sample rate.

Generate PXI Trigger Signals with PXI-6115

Hello,
I have a question.
I have a PXI-6115 and some other card in my mainframe.
These other cards nee 10 Mhz pulses on line PXI-Star1 and 2.5 MHz on PXI_trg7.
So I thought to apply (somewhere on my PXI 6115 card) 10 MHz, divide the 10 MHz with a counter to 4 and route all this things to the backplane.
But I don't understand how to do this.
There are no good examples.
And as far as I know the PXI-6115 isn't yet supported by DAQ-MX.
Can anybody give me some good advises or tips, white paper or so to make me solve my problem ???
Thanks Ruediger

I don't have time to write any example snippets right now, but I'll try to provide you the general idea and hopefully you can take it from there.
First, it's not clear whether you want to generate the 10 MHz from the 6115 and send it to other devices in the system or accept the 10 MHz externally and route it to the rest of the system. If you're bringing in the signal externally, I would simply using the DAQmx Connect Terminals VI to route the signal from a PFI line on the front connector of the board to one of the PXI trigger bus lines in the backplane. Check out the routing table in MAX to see what routes are possible. To perform this route, the driver will have to route through Counter 0 so you won't be able to use Counter 0 for anything else.
If you want to generate 10 MHz from the 6115, I would create a continuous pulse train task on Counter 0 using the CO Pulse Ticks version of the Create Channel VI with a value of 2 for both the high ticks and low ticks input. However, to achieve 10 MHz clock on a PXI trigger line, you'll have to perform a couple of modifications that typically aren't done with counter tasks. First, you'll need to use the DAQmx Export Signal Property Node to route the Counter Output Event to the desired PXI trigger line. You can find this property by navigating the following menu hierarchy Events->Counter Output Event->Output Terminal. By default, the driver routes this event to the Ctr0Output pin on the front connector of the board. Using this property will override this behavior and route the output of the counter to a PXI trigger line instead. Second, you will need to change the output behavior of the Counter Output Event from toggle to pulse. This can be through the Events->Counter Output Event->Output Behavior property. Normally, when generating pulse trains, the high ticks and low ticks parameters from the Create Channel VI determine the frequency and duty cycle of the pulse train. When the high ticks count expires, the output of the counter toggles. The low ticks value is then loaded into the counter, and the counter output toggles again when the low ticks value expires. This process repeats to produce a pulse train of the desired frequency and duty cycle. Since the counter uses a 20 MHz timebase and has a minimum low ticks and high ticks value of 2, you can only produce at maximum a 5 MHz pulse train using the toggle behavior. However, by changing the output behavior from toggle to pulse, the counter output will issue a short pulse each time the high ticks and low ticks counts expire yielding a 10 MHz clock signal.
Now that you have the 10 MHz signal taken care of, you need to generate a 2.5 MHz signal from it. My guess is that since you have a 6115, you already have plans for the AI engine so I'll describe a route that uses AO instead. First, create an AO task to perform continous waveform generation. Use the DAQmx Channel Property Node and set the Use Only Onboard Memory property to true. Setting this to true will cause the driver to download the waveform once upon starting the task and replay the waveform from the onboard FIFO. Since you're only using this task to generate a clock, you don't really care about the data and this will prevent unneccessary traffic across the PCI bus. Next, use the DAQmx Timing Property Node to set the Sample Clock->Timebase->Source to the PXI Trigger line that you're generating the 10 MHz clock on, and set the Sample Clock->Timebase Divisor to 4 (10 MHz / 4 should give you a 2.5 MHz sample clock). Last, use the DAQmx Export Signal Property Node to set the Clocks->Sample Clock->Output Terminal to the PXI Trigger Line you want to generate the 2.5 MHz signal on.
It requires some creative programming, but you should now have a 10 MHz and 2.5 MHz signal routed onto two different PXI Trigger lines. I know this solution is a bit involved so if you have any further questions be sure to post back.

Remove unwanted signal after data acquision

i'm doing data acquision using ACH0 and ACH1 of PCI-6025E. ACH0(reference sinewave) should give me a 50Hz sinewave and ACH 1(spike) should give me a series of spikes, however the spikes are riding on the sinewave-like signal.
1. why is the spike waveform riding on another signal? i had double checked the signal on the oscilloscope, and verify that it is just a series of spikes. and i don't face this problem if i acquire the 2 signals separately by using acquire waveform.vi instead of the acquire waveforms.vi. synchronising these 2 waveforms is a must for my application hence i need to use acquire wavefroms.vi that provided me synchronism.
2. what can i do to remove the sinewave-like signal?
3. i tried using
filter however it don't seem to work as when i view the frequency content (using FFT spectrum mag-phase.vi)of the 'spike signal riding on the sinewave-like' signal, i got an output waveform that i cannot interpret.
4. why can't view the frequency components of the signal measured in qn 3. Uisng the extract single tone information.vi it shows that the frequency of the spike signal is around 50Hz.
Attachments:
Test_acquire_2_analog_channel1.vi ‏504 KB

Different questions and suggestions.
First, an attempt to solve the problem in the acquisition:
1) Overload: It looks like the sine tone you are acquiring is extremelly overloaded (it clips at 10 Volt). This could be disturbing your measurement. Can you by any way avoid this overload?
2) cross-talk between channels: you are running your board at a scan-rate of 200 kHz. This is over the specifications of the settling time of the board. Try to decrease your scan rate and see if this fixes your problem (or at least reduces it).
3) Is the problem still there if you only acquire channel 1? If yes, the problem is not cause by scanning issues but most likely be due to bad connectivity, grounding issues, common mode problems, single-end / Differential co
nnection. This depends on the way your signals are connected.
Removing the problem in post-processing:
4) if everything else fails, you can remove the sine tone from your "spike signal" as follow: On the sub-VI "Extract Single Tone Information.vi" create a constant "Residual signal" for the control "Export signal". The time signal exported (on top of the VI) will then be what you are looking for, that is your signal with the detected 50 Hz sine tone removed.

NiFgen Export Signal

Similar Messages

Maybe you are looking for