Some more command Info,
To dump the full decode memory use the command "DCLR", you have 2 options, "DCLR? HEAD" which looks to scrape the length of the decode table, and "DCLR? DATA" which dumps exactly what you see on the decode list (whitespace and all), with the entry number and timestamps.
I've dug furthur into the DeCo_PAram Command, It has keywords (BUS,LIST,FOMT,LSSC,B1LSFN,B2LSFN,LSMN) but not yet clear on what data should be passed for each.
Next up, the decoder commands, these commands are used to setup a decoder via SCPI, they have query's but they are set to return 1, so my best guess is the queries are "To be developed later",
B1:DCCN (Can Decoder for Bus 1), has the Keywords (DIS,CANH,CANHT,CANL,CANLT,SRC,BAUD)
B1:DCIC (I2C Decoder for Bus 1), has the Keywords (DIS,SCL,SCLT,SDA,SDAT,RW)
B1:DCLN (Lin Decoder for Bus 1), has the Keywords (DIS,SRC,SRCT,BAUD)
B1:DCSP (SPI Decoder for Bus 1), has the Keywords (DIS,CLK,CLKT,EDGE,MISO,MISOT,MOSI,MOSIT,CSTP,CS,CST,NCS,NCST,LMT,BTOD,DTLG)
B1:DCUT (Uart Decoder for Bus 1), has the Keywords (DIS,RX,RXT,TX,TXT,BAUD,DTLG,PRCK,STOP,IDLE,BTOD)
Now my feeling is for the Pairs, e.g. RX / RXT, RX is the input that channel is on, RXT is the trigger threshold for that channel. as for its full documentation, that may come later, just felt I would raise this as the decode buffer is something people have been after