:MEASure:JITTer:ESYMbols?
Query Syntax
:MEASure:JITTer:ESYMbols?
Description
Returns an ordered list of edge symbol numbers returned as definite-length block data. Each value is the number of the symbol in the pattern preceding the edge transition and is in the range of 0 to pattern length minus 1. Only the edges of the type specified by the command :MEASure:JITTer:DEFine:EDGE are included in the list.This query will return an incomplete list of edges if all of the data needed to determine the pattern has not yet been acquired. Use the :MEASure:JITTer:DDJSymbol? query to return the DDJ values. Use the :MEASure:JITTer:PATTern? query to return the edge type values.
For example, the following symbol numbers could be returned : 4, 6, 10, 11, 12, 13, 17, 19, 22, 23, 28, 29, 32, 33, 34, 35, 36, 37, 43, 44, 45, 46, 47, 48, 52, 55, 68, 69, 76, 77, 80, 82, 86, 87, 93, 94, 97, 99, 102, 103, 106, 107, 108, 109, 116, 119, 125, 126.
This query produces an error if jitter signal type is set to clock signal (:MEASure:JITTer:DEFine:SIGNal CLOCk).
Requires FlexDCA revision A.05.60 and above.
This command replaces deprecated command :MEASure:JITTer:EBITs.
Returned Data Type
The :MEASure:JITTer:ESYMbols? query returns long int (unsigned) values as binary definite-length block data queries binary definite-length block data queries binary definite-length block data queries. You must specify this data type in your program language's command that you use to query the data. The specifier for this data type in your programming language will likely be "L" and it is identified in this example with red text. Confirm this with your programming language's documentation. The following is an example of the command used in Python using pyvisa.
Flex.read_termination = ''
Flex.write_termination = ''
endianness = Flex.query(':SYSTem:BORDER?')
Flex.write(':SYSTem:BORDER LENDian')
data = Flex.query_binary_values(':MEASure:JITTer:ESYMbols?',
datatype='L',
container=list,
is_big_endian=False,
header_fmt='ieee')
Flex.write(':SYSTem:BORDER ' + endianness)
Endianness of Returned Definite-Length Block Data
To correctly interpret definite-length block data, you must know the endianness (byte order) of the returned data (integers or real) from FlexDCA and you will must likely need specify this same endianness in your program language's command that is used to query the data. Endianness can be set to "little endian" order in which the least significant byte is sent first and the most significant byte sent last. Or, the endianness can be set to "big endian" order in which the most significant byte is sent first and the least significant byte sent last.
To specify or query the endianness setting for binary block data, use the :SYSTem:BORDer command. The endiannes setting applies to all binary queries except for :DISK:FILE:READ? query.
If you plan to change FlexDCA's current endian setting, it is a good practice to query FlexDCA's current endian setting and restore the setting when your program completes. This will avoid other programs having errors due to assuming a particular endianness setting.
After a factory preset (:SYSTem:FACTory), sets little endian. A default setup (:SYSTem:DEFault) does not affect endianness.
Be aware that VXI plug-and-play drivers can change the endianness setting. As a result always explicitly set the endianness in your program before transferring any binary data.
The ability to specify endianness requires FlexDCA revision A.04.00 and above. Prior to revision A.04.00, the endianness of returned block data was always LSB (Least Significant Byte) first.
Example Command Sequence
:SYSTem:MODE JITTer :MEASure:JITTer:DJ:SOURce CHAN1A :MEASure:JITTer:DEFine:EDGe REDGe :MEASure:JITTer:ESYMbols? :MEASure:JITTer:DDJSymbol?