Title says it all pretty much. It works in the “standard” waveform generator, which btw has also an option for internal triggering source, which would be a welcome feature on the AWG instr. as well.
Hi @mschuette,
I’m not able to reproduce this issue, are you able to share more information or screenshots of your setup?
To get the AWG to use the external trigger in burst mode I connected Output 1 of “Moku-000965” to the External trigger of “Devvy 96” and then connected Output 1 of “Devvy 96” to Input 1 of “Moku-000965” to view the signal in the Oscilloscope. The signal connected to the External trigger was a 1 Hz, 1 Vpp square wave with an offset of 500.0 mV to ensure it exceeded the 700 mV trigger threshold of the Ext. trigger. I’ve attached screenshots of this setup for you.
I hope this helps and please share more information about your setup if this does not help,
Indira
Dear Indira,
I’m using a 10Hz, 0-5V TTL trigger on the external input. I tested everything from 1us to 50% duty cycle. I think the 700mV trigger threshold does not apply to the external trigger, it is just the setting when using Inputs 1-4 for triggering and becomes inactive when the ext. trigger is selected. But since the trigger works on the standard waveform generator, I think this is not the problem.
Please try generating bursts of 4096 exponential decay pulses at 4.5MHz rep rate and 1.2Gsa/s with 256 manual points and 355° phase. Try doing this for output 1 and 2 simultaneously.
I’m really sorry you’re having this issue but I am still able to trigger the AWG with these parameters, see my screenshots below.
Firstly, it is important that the signal connected to the external trigger exceeds 700 mV as the external trigger BNC is a TTL trigger, which I’m sure you know means that it will consider signals below this value as “low” and above 700 mV as “high”, so needs to receive a signal above 700 mV to trigger. But I agree this does not sound like an issue if the signal you’ve connected to the external trigger is a 0-5 V signal.
Are you also using your Moku to generate the trigger signal or view the output of the AWG, or are you using other devices? If you set up your devices as below in Single or Multi-Instrument Mode what do you see?
Output 1 here is connected to the external trigger (using a 1 us pulse wave as ext. trigger):
Inputs from triggered AWG signal:
Outputs 1 and 2 are bring triggered by the external trigger and are connected via BNC to the inputs of the oscilloscope
Zoomed in view of the burst signal from the AWG (in this case square wave is used as ext. trigger):
Hi Indira, thanks for your effort to replicate the problem.
The only difference I can see now is that I’m using smaller signals amplitudes (300mV pk-pk). I’m using an external R&S Scope to check the output of the MOKU and some custom hardware to generate the trigger (which I also checked using the scope). I would have to check again, but I remember the trigger signal not quite dropping to zero, but if the ext. trigger input is indeed TTL (it’s not mentioned in the official spec sheet, but here), it should not matter. Also I’d like to mention again that the trigger works in the “standard” signal generator instrument.
Besides, you again mentioned 700mV high-logic on the ext. trigger, but TTL would be 2V. Can you confirm the actual specs of the ext. trigger input?
I’ll try multi-instrument mode when I find the time. Thanks.
Thanks for this further information, are you able to share with my what firmware version you are using?
I have just been made aware that there was a bug in a previous firmware where the external trigger does not work on the AWG but does work on the WG, as you are describing. In this case, I suggest upgrading to the latest firmware via the App or API, which you can find here.
Let me know how an update goes.
Hi Indira,
a FW upgrade indeed fixed the problem. Unfortunately the Mac OS app didn’t show an available update, but on your tip, I checked the iPad app, which indeed showed an update.
Cheers
1 Like