DF1 Publish time 2021-3-16 04:16:32

DSO 2C10 SCPI

DSO 2C10 question
Where do I find the SCPI command reference?

wangshuang Publish time 2021-3-16 15:46:20




Please visit the product page of Hantek official website to download:
http://hantek.com/products/detail/17182

DF1 Publish time 2021-3-16 23:05:27

Thank you!

DF1 Publish time 2021-3-17 04:34:57

Edited by DF1 at 2021-3-17 22:39

I have some problems with the "WAV:DATA:ALL?" command, the first time it should return 127 bytes/chars, next time you should get 29 bytes/char and wbatever number of bytes indicated for the trace (4029 it seems) I suppose this is binary 8 bit data (unsigned uInt8), each representing a single point on the screen, or?
The first problem is the data for channels not used or not available in the scope.https://drive.google.com/file/d/19iJE1B_7F6dqCd-6V7yP1l1uCJahc28L/view?usp=sharing In the image, only channel 1 is ON, data in chars 47-53 is CH1 voltage, but seems wrong, CH2,3,4 all takes up 8 chars (one more than expected!) all with the value 4.9e-318 (8 chars), offsetting the remaining chars.

Will this be corrected?
Is there a command to read the error register in the scope?
Is there a command to clear the output buffer?
Thank you.
https://drive.google.com/file/d/ ... 8L/view?usp=sharing



DF1 Publish time 2021-3-17 04:36:08

Edited by DF1 at 2021-3-21 00:43

"WAV:DATA:ALL?" - dont know what happened there!
should be WAV: DATA:ALL? without the space before the D


Anyway, reading the vertical scale voltage also gives strange results, see the attached screen dump from IO Lib, not 1 as expected, but 9.881e-318
Any idea why?

BTW, this and other commands fail if used according to the SCPI specification.
CHANnel1:SCALe? works - althougt with a strange result.
CHAN1:SCAL? does not work - but it should, at least to give the same strange result!

OK, captured the IO traffic from the DigitalScope App, it shows the use of the "PRIVate:WAVeform:ALL?" command.
This command returns an IEEE488.2 BINBLOCK for NON-GPIB instruments (although with a header failure!), and it seems to work.

The SCPI Command Reference definitely is on need of some rework, and so does the command interpreter in the scope firmware!








Pages: [1]
View full version: DSO 2C10 SCPI