maxwellfire

Members
  • Content Count

    3
  • Joined

  • Last visited

  1. Hi attila, Thanks for the response! I agree that the waveform commanded can be pretty different from the one actually output. I am interested more in the timing of the signals and what it was trying to output than of the exact value/distortion of the output waveform. Wiring the output temporarily up to the system and using it as a reference waveform is a good idea! I think there's probably a complicated triggering setup where this won't work, but I don't have that problem, so it should work. If I made a custom wavegen output signal, I could set it as both the wavegen output and
  2. The data pins must not change near where the clock has its sampling edge. For a mode 0 SPI setup, the data is sampled on the rising edge, not the falling edge. The data changes near the falling edge. Therefore your drawing is a bit misleading. MOSI isn't sampled just before a falling transition. It's sample a full half a clock pulse earlier. If MOSI is changing when the clock is also rising, the behavior is not well defined. Here's a diagram. Notice how IO is shown as changing somewhere in the middle between rising clock edges. Here's another diagram: t_
  3. Hey, Is there a way to use the value of the arbitrary waveform generator output in a script? I'm interested in comparing the signal the waveform generator or power supply is outputting and a signal that I'm getting from the oscilloscope measurement. I can set the two instruments to share a trigger, so their values should theoretically be aligned and known right? I could connect one of the scope inputs to the relevant output, but I don't have a scope input to spare (and just knowing what it thinks its outputting would be helpful.) It would also be nice just to be able to show the