Author Topic: SDS814X SCPI Trigger Issue (Firmware bug?)  (Read 387 times)

0 Members and 2 Guests are viewing this topic.

Offline Omega GloryTopic starter

  • Regular Contributor
  • *
  • Posts: 91
  • Country: us
    • Ezra's Robots
SDS814X SCPI Trigger Issue (Firmware bug?)
« on: April 10, 2024, 12:00:40 am »
When issuing SCPI commands via USB to an SDS814X, I am running into what appears to be a firmware issue involving single capture triggering, and retrieving the waveform data.

I can set the scope to single capture by issuing: "TRIG:MODE SING", but then when it comes time to retrieve the data by issuing "WAV:DATA?", while I'm able to capture data, it puts the scope back into RUN mode. This worries me because sometimes waveforms have to be transferred over with multiple calls to "WAV:DATA?" depending on how many sample points there are, and I worry that since the scope gets flipped into run mode, I might actually be retrieving chunks from different captures. Even if it is all coming from one capture, it doesn't seem like issuing "WAV:DATA?" should put the scope back into run mode.

Has anyone else encountered this problem?

Edit: Mods, I'm moving this to a different thread as suggested by tautech, please feel free to delete this.
« Last Edit: April 10, 2024, 12:59:46 am by Omega Glory »
 

Offline tautech

  • Super Contributor
  • ***
  • Posts: 29335
  • Country: nz
  • Taupaki Technologies Ltd. Siglent Distributor NZ.
    • Taupaki Technologies Ltd.
Re: SDS814X SCPI Trigger Issue (Firmware bug?)
« Reply #1 on: April 10, 2024, 12:03:43 am »
Best place for this is here where more eyes will get to see it:
https://www.eevblog.com/forum/testgear/sds800x-hd-bugswanted-features/
Avid Rabid Hobbyist.
Some stuff seen @ Siglent HQ cannot be shared.
 
The following users thanked this post: Omega Glory


Share me

Digg  Facebook  SlashDot  Delicious  Technorati  Twitter  Google  Yahoo
Smf