Done, here is full list with corresponding handler functions:
https://pastebin.com/Ue5WtKm8
"CMD=" form means "CMD with parameters"
@abyrvalg,
I don't think this list is totally correct. It seems there are many commands which are not valid.
My comment is just from an analytical POV and not from commands experimentation and/or code analysis. I think Agilent/KS would never create commands like, for example:
STATUS:QUESTIONABLE:EVENT:INTEGRITY:EVENT:UNCALIBRATED:EVENT:NTRANSITION?
CALCULATE:MARKER:SET:SET:FCOUNT:STATE
Also, how could 1800+ commands generate only 300+ different functions?
I did my parsing, using this rules:
0xFF - means end of tree branch
0x00 - tree leaf
current_state_idx == next_state_idx - bypass
My output is attached. I could be missing something (or not) but, definitely, this list seems more like "usual" SCPI commands. Even though, it still generates 808 commands.
Edit: I just corrected the current_state_idx == next_state_idx processing because all already included the SET command. New file attached.
Edit1: New output in a later msg.