Please select To the mobile version | Continue to access the desktop computer version

Electronic Engineer Discuss

View: 212|Reply: 0

Hantek DSO3254A SCPI

[Copy link]

1

Threads

1

Posts

1

Credits

新手上路

Rank: 1

Credits
1
Post time 2021-2-14 14:37:48 | Show all posts |Read mode
Edited by BenKi at 2021-2-14 14:40

Dear Sir or Maddam,

thank you for this product.

I have a question about the frame encoding using SCPI.
According to the manual "DSO3000B - SCPI Protocol document" at page 51 it is listed how to decode the response of a query like
  1. :WAVeform:DATA:DISP
Copy the Code
or
  1. :WAVeform:DATA:ALL
Copy the Code
As far as I understand this, all information within the "header" of the query response, which is the bytes from 0 to 127 should be ASCII encoded characters - Is this correct?

I'm asking this kindly because during implementation of a script to download data from the scope, I am faced with the situation that the query may also contain non-ASCII characters, which may be plain integer values.
See the following example for a real response after issuing the write of :
  1. > :WAVeform:DATA:DISP
  2. > 35, 57, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 0, 255, 10
Copy the Code

Number 35 decodes to ASCII-character '#' as expected and documented
Number 57 decodes to ASCII-character '9' as expected and documented
Number 10 at the end of the frame decodes to ASCII-character '\n' as expected

Now my trouble starts:
Number 0 decodes to ASCII-character 'NUL', which I did not expect, because, number 57 stated, that '9' character will follow which will give the number of bytes of the whole message. Surely all the  '9' characters might be  ASCII-character '0', which would be the number 48.

During further inspection it looks like that every time some information within this header evaluates to a plain integer number of value 0 it is not ASCII-encoded as '0' before send back via SCPI-protocol.
Here is the response of *IDN? for my scope
  1. > *IDN?
  2. > hantek, DSO3254A, DSO45001809, 20180601A
Copy the Code

Also a response of the query
  1. > :SYSTem:VERSion?
Copy the Code
looks like
  1. > `20180601A
Copy the Code
but according to document "DSO3000B - SCPI Protocol document" at page 32 it should rather look like
  1. > Ver001.001.001
Copy the Code
May these to issues are some bugs in the firmware of the scope? If so, would you be so kind to fix these and provide a new release of firmware for your customers?

Best regards and thank you very much






Reply

Use magic Report

You have to log in before you can reply Login | Register

Points Rules

QQ|Dark room|Mobile|Archiver|Electronic Engineer Discuss

2021-3-8 07:39 GMT+8 , Processed in 0.337101 second(s), 22 queries .

Powered by Discuz! X3.2

© 2001-2013 Comsenz Inc.

Quick Reply To Top Return to the list