ML24xxA Native Commands GPIB Operation
8-62 PN: 10585-00001 Rev. P ML2437A/38A OM/PM
OFFTBR (Output an offset table)
OFFTBU (Updates an offset table)
Syntax: OFFTBR <val>
val: 1 to 5
Remarks: Outputs the selected offset table. The returned string is constructed as
follows:
OFFTBR
#<length><number_of_bytes>,<element1<element2><element>
Where <length> is the character size of the <number_of_bytes> field and
<number_of_bytes> is the number of bytes which make up the string
after the comma (,). For example:
OFFTBR #41600,<data...>
4 = number of character to read next for the data length
1600 = One thousand and six hundred bytes of data to read in,
representing 200 elements placed one after the other without commas.
Each <element> is made up of 8 bytes; the first four bytes are the
Frequency and the second four bytes are the corresponding dB value for
the Frequency. For example:
<data_element1><data_element2><data_element3> is equal to:
<freq1><dB1><freq2><dB2><freq3><dB3>... is equal to:
<4bytes1><4bytes1><4bytes2><4bytes2><4bytes3><4bytes3>
The 4 byte binary values are 4 bytes single precision floating point
binary data. The C programming example 'Binary output decoding'
shows how to extract the binary data.
Syntax: OFFTBU <val>,<bytes>,<binary_data...>
val: 1 to 5
bytes: number of bytes in the binary_data string
binary_data: frequency and dB offset
Remarks: This command updates the offset table specified by <val>.
<bytes> is the number of bytes in the binary_data string and
<binary_data> is a string which represents the frequency and the dB
offset to apply in the format of: <element1><element2><elementn...>,
where <elementn> has four bytes to represent the frequency and four
bytes to represent the dB value.
The four byte value can be created by multiplying the floating point
number by 1024 and converting the LONG number to an ASCII string.
For example: -10.234 becomes 10479, converted to hexadecimal
FFFFD711. See the programming examples for more detail.
To Next Page
Loading...
