Author Topic: Rigol MSO2202A SCPI Bug  (Read 154 times)

0 Members and 1 Guest are viewing this topic.

Offline PeterHouse

  • Contributor
  • Posts: 11
Rigol MSO2202A SCPI Bug
« on: August 21, 2019, 01:49:25 pm »
I am using EEZ Studio to communicate and send SCPI commands to the scope.

Unfortunately, If I send a single command with an unknown command, the scope will not respond to any other valid command until after a reboot.

Example:
*IDN? returns the instrument name and some other info.
*IDX? (invalid command) lock up the SCPI system completely until after a reboot.  The instrument remains connected but will not respond.  If disconnected, the instrument will refuse all further connections until after a reboot.

I know -
Patient: Doctor, it hurts when I raise my arm. 
Doctor: Don't raise your arm!

I am trying to find out how to configure the Analog Channel Labels using SCPI.  They are not documented in the manuals and I am experimenting trying to find them.  I have been using a SCPI terminal program to save and replay instrument configurations since the old IEEE-488 SCPI days for project documentation and test setup restoration.

My Opinion:  The scope should gracefully accept unknown invalid commands and simple ignore them.  Locking up is almost never a good behavior.
 

Offline tv84

  • Frequent Contributor
  • **
  • Posts: 862
  • Country: pt
 


Share me

Digg  Facebook  SlashDot  Delicious  Technorati  Twitter  Google  Yahoo
Smf