Products > Test Equipment

Has anybody enabled Tracking Gen on Agilent N9340B?

<< < (11/16) > >>

tv84:

--- Quote from: abyrvalg on August 21, 2020, 03:21:07 pm ---Done, here is full list with corresponding handler functions:
https://pastebin.com/Ue5WtKm8

"CMD=" form means "CMD with parameters"

--- End quote ---

@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.

abyrvalg:
Yes, some commands don't look good definitely. Digged the parser a bit deeper - it is much more complicated than I've thought:
- functions specified by func_idx are called for all matching intermediate keywords too (not just for leaves) and they can affect further parsing by setting/clearing some flags (i.e. s_bool, s_unbool), checking for some conditions etc
- the current state is checked for some specific values and some parsing actions are taken right in parser loop
So just walking those state arrays is not enough, much more manual work is required (check for each of those intermediate flags-changing funcs in script logic to take some actions, check for special states etc). Doable, but it doesn't look like fun anymore, this is closer to "harvesting a field" than to "hunting" already ;D
The same tree with intermediate functions: https://pastebin.com/xgi3wkcd

tv84:

--- Quote from: abyrvalg on August 22, 2020, 11:03:08 pm ---- functions specified by func_idx are called for all matching intermediate keywords too (not just for leaves) and they can affect further parsing by setting/clearing some flags (i.e. s_bool, s_unbool), checking for some conditions etc

--- End quote ---

I thought you has previously studied that part. :)

I had that question myself from the beginning but decided to close my eyes to that. Nonetheless, the last func is the important one.


--- Quote from: abyrvalg on August 22, 2020, 11:03:08 pm ---Doable, but it doesn't look like fun anymore, this is closer to "harvesting a field" than to "hunting" already ;D

--- End quote ---

 :-+ I'll have a look to see if I can add something valid.

tv84:
New SCPI command list with lower/upper cases. Includes 322 different commands.

I've filtered all the repeated commands.

For me, this is the final command list. Fun's over.

@abyrvalg, the intermediate "functions" allow for the parsing of what I did manually in this filtering. Not worth the trouble of reversing.

analogRF:
confirmed:
DEBUG:REMOTE:OPTION:CLEAR works
with DEBUG:REMOTE:OPTION you can enable/disable individual options

EDIT: DO NOT try undocumented options  :o

Navigation

[0] Message Index

[#] Next page

[*] Previous page

There was an error while thanking
Thanking...
Go to full version
Powered by SMFPacks Advanced Attachments Uploader Mod