Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Suggested Trigger enhancement #18

Open
damercer opened this issue Aug 29, 2019 · 0 comments
Open

Suggested Trigger enhancement #18

damercer opened this issue Aug 29, 2019 · 0 comments

Comments

@damercer
Copy link

Hi:
Here is a suggested enhancement to the analog trigger source options. Having the option to trigger / sync the analog input capture to the AWG output waveform. This could be done (might need addition to firmware) based on the AWG waveform buffer pointer. Easy obvious one is to trigger / syn off start of AWG buffer each time it repeats. Additionally you could provide an option to supply a time offset from the start of the buffer in AWG samples for example.

Why would this be useful? A common setup would have one of the scope channels connected to one of the AWG outputs to monitor the signal. You would then probably use that scope channel as the trigger source. The second scope channel might be then used to measure some other (output) node in the circuit. Given that m2k only has the two scope channels it might be desirable to not need to use one channel to trigger off the AWG output. With a way to syn directly off AWG waveform then both scope channels are free to use elsewhere in the circuit being investigated.

Also if you know where (how) in the AWG buffer the captured scope data aligns then you can plot the AWG waveform data along with the captured scope data i.e possible to plot a representation of the AWG outputs at the same time as the scope inputs without needing to physically connecting them together. Like having a "4" channel scope in some cases.

Any way just a suggestion. Maybe there is already a way to do this and it is just not documented yet.

Doug

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant