Anyone that has experience with Label List in R&S RTB2000 series oscilloscopes?

[RBBVNL9]

Hi everyone,

For a project, I am trying to use a label list for a serial protocol on the RTB2004. But even when I try to load the label list example provided in the instrument's manual, it does not seem to work.

So, the CAN protocol label list example in the most recent RTB2000 manual (page 242) is as follows:

# ---------------------------------------------------------------------------- @FILE_VERSION = 1.00 @PROTOCOL_NAME = can # --------------------------------------------------------------------------- # Labels for CAN protocol # Column order: Identifier type, Identifier value, Label # --------------------------------------------------------------------------- 11,064h,Diag_Response 11,1E5h,EngineData 11,0A2h,Ignition_Info 11,1BCh,TP_Console 11,333h,ABSdata 11,313h,Door_Left 11,314h,Door_Right 29,01A54321h,Throttle 29,13A00FA2h,LightState 29,0630ABCDh,Engine_Status 29,03B1C002h,Airbag_Status 29,01234ABCh,NM_Gateway # ----------------------------------------------------------------------------

And, according the manual, it should result in a loaded table list like this:

[ Specified attachment is not available ]
Yet, when I load that example into my own oscilloscope, I get the following instead:

[ Specified attachment is not available ]

The IDs and addresses are not the same... Now if we look at the one with label 'ABSdata', we note that the  data file specifies value '333h', where the suffix 'h' indicates this is a HEX value (see also the manual, page 307). But in the actually loaded table, we see '014D', which is the HEX equivalent for the decimal number 333d.

It seems as if when the instrument is instructed to read HEX values, yet it reads them as if they were DEC values (and ignores anything with characters A thru F).

Anyone experiences using the label list feature, or anyone willing to test the above example to see whether he or she gets the same list?

[RBBVNL9]

Just figured out that, for my current project, I can of course just manually compute all HEX numbers into DEC numbers and instead put these into the input file for the RTB, and thus 'fool' the instrument. It's a nuisance and a loss of time (especially for longer ranges of numbers), but it works.

But I feel would still be preferable that the instrument would process the input file as specified in the documentation, and the sample code that Rohde and Schwarz provides in its manual actual works on the instrument...