No trigger seen!

[Alex_Dewar]

@Eddiie

I am stuck on trigger now. The only way I can get a trigger is in the code above. Which is “low” on tio2, my transmit. I think I need to change it to “high” on tio1? How do I know the trigger condition is valid?

I typically avoid using “high” or “low” trigger, since that means the trigger can happen on an idle trigger line.
You can typically tell if your trigger is okay by the power trace you collect - if you can see the same shapes, but they don’t line up, you can usually fix it by post processing. If every power trace you collect looks completely different, your trigger probably isn’t good.

@Eddiie

Is every call to scope.arm() setting up a new trace?

What is ending the capture in the current loop? Guess I need to go back and read scope again. There’s scope timeout and number of traces… if timeout is 10 and number of traces is 500, is that 500 traces over 10 seconds? I don’t think so.

scope.arm() basically tells the capture end to start looking for a trigger. Once it sees that trigger, it starts collecting samples (determined by scope.adc.samples) and, once it’s done collecting those samples, we transfer the samples from the board to the PC.

Alex