EEVblog Electronics Community Forum
Products => Test Equipment => Topic started by: tv84 on June 03, 2019, 07:45:11 pm
-
I'll try to gather here the lists of all SCPI commands available on Rigol stuff (even those that are not documented in the manual).
This info is taken directly from the .GEL/.SYS mapping tables.
MSO5000 and DS7000 were parsed from the .XML files.
Bugs or unlisted known commands:
Please report and I'll try to see why it happened.
-
Thank you! :-+
Now, the full list can be compared with the manual, and make a list containing only the hidden commands.
-
List of hidden commands for DP800:
:SYSTem:MAC
:SYSTem:PRINT?
:CALibration:SET
:CALibration:MEAS
:CALibration:STORe
:CALibration:CLEar
:CALibration:STARt
:CALibration:END
:CALibration:SENSE
:PROJect[:STATe]
:PROJect:SET
:PROJect:FAN
:PROJect:GET?
:PROJect:TEMP
:PROJect:TEMP?
:PROJect:OUTPut:STEP
:PROJect:OUTPut:STEP?
:PROJect:POWEron:OUTPut[:STATe]
:PROJect:POWEron:OUTPut[:STATe]?
:PROJect:POWEron:OUTPut:SAVE
:PROJect:MEMOry:WRITe
:PROJect:MEMOry:READ?
:PROJect:CALIbration:DATA:VOLTage:WRITe
:PROJect:CALIbration:DATA:VOLTage:READ?
:PROJect:CALIbration:DATA:CURRent:WRITe
:PROJect:CALIbration:DATA:CURRent:READ?
:PROJect:CALIbration:DATA:CURRent:ADDRess?
:PROJect:CALIbration:INFO:WRITe
:PROJect:CALIbration:INFO:READ?
:PROJect:CALIbration:INFO:ADDRess?
:DIGItal:IO:OUTPut
:DIGItal:IO:OUTPut?
:LIC:CLEAr
Think I got most of them. The PROJ ones are the most interesting of course. I think the CAL ones were around somewhere, but I didn't see where, as a user here had written a SCPI cal script.
List for DG800:
*TST?
:DISPlay:DATA?<n>
:MEMory:STATe:LOCK (lock is actually mentioned in the guide but they don't give the command)
:MMEMory:UPLoad? (same as load?)
:OUTPut<n>:MODE
:OUTPut<n>:MODE?
:OUTPut<n>:GATe:POLarity
:OUTPut<n>:GATe:POLarity?
[:SOURce<n>]:APPLy:ARBitrary
[:SOURce<n>]:CALibration:RANGNUM
[:SOURce<n>]:CALibration:SETVALUE
[:SOURce<n>]:CALibration:MEASVALUE
[:SOURce<n>]:CALibration:STORE
[:SOURce<n>]:CALibration:RECALL
[:SOURce<n>]:CALibration:PRESet
[:SOURce<n>]:CALibration:DATE
[:SOURce<n>]:CALibration:HIGHest
[:SOURce<n>]:FUNCtion:PULSe:HOLD
[:SOURce<n>]:FUNCtion:PULSe:HOLD?
[:SOURce<n>]:PULSe:HOLD
[:SOURce<n>]:PULSe:HOLD?
:SYSTem:KLOCk:STATe (probably same as :KLOCK)
:SYSTem:KLOCk:STATe?
:SYSTem:COMMunicate:LAN:HOSTname
:SYSTem:COMMunicate:LAN:HOSTname?
:SYSTem:COMMunicate:LAN:SOCKetport
:SYSTem:COMMunicate:LAN:SOCKetport?
:SYSTem:COMMunicate:LAN:SERVername
:SYSTem:COMMunicate:LAN:SERVername?
:SYSTem:COMMunicate:LAN:MAC?
:SYSTem:SECurity:IMMediate
:LICense:PUBKey
:LICense:PUBKey? (doesn't seem to work)
:PROJect[:STATe]
:PROJect:KEY
:PROJect:PWM:FREQuency
:PROJect:PWM:FREQuency?
:PROJect:PWM:FINe:CH
:PROJect:PWM:FINe:CH?
:PROJect:PWM:LEVel:CH
:PROJect:PWM:LEVel:CH?
:PROJect:DAC:AMP:CH
:PROJect:DAC:OFFSet:CH
:PROJect:MODE
:PROJect:SN
:LXI:RESet
:LXI:RESTart
-
Thank you very much. sir.
Can you modify the contents of mso5000?
I want to add 2k, 5k, and 20k of memory select.
This is related to the waveform update rate, and the update rate of the mso5000 is not fast as the specification.
If you see Rigol developers, I'd like you to fix them.
-
I'll try to gather here the lists of all SCPI commands available on Rigol stuff (even those that are not documented in the manual).
This info is taken directly from the .GEL/.SYS mapping tables.
MSO5000 and DS7000 were parsed from the .XML files.
Bugs or unlisted known commands:
Please report and I'll try to see why it happened.
Another thought:
If you want me to include one of instruments on the list into my tool,
please write exactly what command, what sequence and what format the screenshot uses. I can only test my stuff, thats why.
Thanks
-
is there a known conversion from file info in the MSO5000 xml table to a function offset in app entry?
im trying to dig into how some of these commands are implemented but i cant figure out how to locate them. the DM3058 had a giant table (3 actually) that contained the function pointer. appEntry loads the XML files but i cant seem to follow that to a function pointer.
-
is there a known conversion from file info in the MSO5000 xml table to a function offset in app entry?
I don't remember finding one. But there should be a table based on the xml indexes table, I would guess.
-
Afternoon all,
Does anyone know the commands to enter sense calibration points on DP800 series?
I only have a single point at 42V.
Grassy arse.
-
Anything I can do to help vis-a-vis RSA3000? If you let me know what to loook for, I'll see if I can find it... :)
-
Bump 8)
-
Bump 8)
Please don't bump technical threads.
Try opening a new topic instead, or just use more refined Google searches. For example put this in the search bar:
DP800 calibration site:eevblog.com"site:eevblog.com" will ask Google to search inside the EEVblog.com website only.
The second search result is this doc file: https://www.eevblog.com/forum/testgear/rigol-dp832-firmware-updates-and-bug-list/?action=dlattach;attach=120116 (https://www.eevblog.com/forum/testgear/rigol-dp832-firmware-updates-and-bug-list/?action=dlattach;attach=120116) (from this reply https://www.eevblog.com/forum/testgear/rigol-dp832-firmware-updates-and-bug-list/msg556101/#msg556101 (https://www.eevblog.com/forum/testgear/rigol-dp832-firmware-updates-and-bug-list/msg556101/#msg556101) ).
-
It was only a little bump. Nobody got seriously hurt.
I've been through every doc on the site, but found only one that mentions sense and that has nothing of any use.
Back to the grindstone.
-
The doc linked before has all the commands for calibrating the ADC and DAC, for both generating and measuring. Those should be enough to perform any calibration, IMO.
That is why opening a new thread about the particular thing you are looking for makes sense. You may want to explain there:
- what exactly are you trying to achieve
- why you don't like the results, why do you think they are wrong
- what you did/got so far, explained with screen captures and/or other performed measurements
- what are the results you were expecting but didn't get
-
It was only a little bump. Nobody got seriously hurt.
Thanking RoGeorge for the links also doesn't hurt.
BTW, they clearly show that you didn't go through "every doc on the site".
-
George,
Thanks for the links. tv84 thinks I'm a bellend for forgetting to thank you.... He may have a point.
Inputing cal points for V and I with scpi are not the problem.
:what exactly are you trying to achieve
What I would like to do is input cal points for the sense function.
I currently have just the one at 42V.
The only mention of sense I have found is :CALibration:SENSE . I need to find out what comes after that to set the points. No luck.
:why you don't like the results, why do you think they are wrong
The sense function is useless when I use it. i.e. when charging a battery, I have to increase the voltage to make up for the sense being inaccurate.
:what you did/got so far, explained with screen captures and/or other performed measurements
I've got a headache. I'll get some time away from the machine and come back with a clear head.
Cheers.
-
Hello,
SCPI command are quite pratictal.
Within the Rigol Sigma interface, no problem with my DG822. But when using VISA in another environnement (Excel for me, as I just need some macros), it does not work, either if the VISA-COm reference is well activated in VBA. I don't know yet if the problem is more Excel/windows/VISA or DG822.
Do someone either used VISA SCPI commands in VBA ?
Thanks !
-
Within the Rigol Sigma interface, no problem with my DG822. But when using VISA in another environnement (Excel for me, as I just need some macros), it does not work
I dont know if this is the same issue or not, but on a Rigol RSA3015, SCPI commands don't return readable responses if you simply telnet to the appropriate port. However, if you use PyVisa, everything is OK. Maybe you could try that: it is very easy to write a simple python program using PyVisa to e.g. collect values and write them to a CSV file.
-
That's strange. Python must also use SCPI messages, not ? I first tried, in VBA, with le VISA-COM lib installed with the rigol Sigma. It was VISA-COm rev 3.00 if I remember. Then I tried with more standard NI-VISA drivers that installed VISA-COM rev 5.12. I have to facilitate a test-operator life that today has to configure his instruments 20 times for a test and note the reports in Excel. And...I do not have the skills in Python right now :-(