sigrok - User contributions [en]

Hantek DSO3254A

2021-02-20T15:17:15Z

BenKi: Inserted link to SCPI document within Section Communication Protocol

{{Infobox logic analyzer
| image = [[File:DSO3254A.jpg|180px]]
| name = Hantek DSO3254A
| status = planned
| source_code_dir =
| channels = 4 analog, 16 digital
| samplerate = 250MHz
| samplerate_state = —
| triggers = edge, pulse, video, slope, timeout, external
| voltages = -0.5V — 400V
| memory = 128MSamples per channel
| compression = none
| website = [http://www.hantek.com/en/ProductDetail_2_134.html hantek.com]
}}

The '''Hantek DSO3254A''' is a USB-based signal acquisition device. It has 4 analog channels with 250MHz bandwidth and sampling rate of 1GSa/s. It comes with 16 channel logic analyzer with a maximum sampling rate of 250MHz and an arbritary waveform generator 200MSa/s.

See [[Hantek DSO3254A/Info]] for more details (such as '''lsusb -v''' output) about the device.

== Hardware ==

* S3C2416XH-40 System Controller (400 MHz ARM926EJ with 48 MHz and 12 MHz oscillators with 32.768 kHz RTC oscillator)
* D9SBJ System Memory (MT47H32M16NF-25E - 400 MHz 32MB x 16 DDR2-800)
* D9RZH Acquisition Memory (MT47H64M16NF-25E - 400 MHz 64MB x 16 DDR2-800)
* K9F1G08U0E 128MB x 8 NAND Flash
* 24L64 I2C EEPROM
* DM9000AEP LAN Controller
* USB Wi-Fi Module (optional)
* USB Hub (optional)
* XC6SLX16FTG256 Control FPGA (under heatsink - has JTAG)
* 1 GSPS 8-bit Quad ADC (under heatsink - Analog Devices?)
* ADF4905 Timebase Generator PLL (with 10 MHz reference oscillator)
* LTC2601 x2 (?) 12 Bit Offset DAC
* DAC902E 165 MSPS 12 Bit Waveform Generator DAC
* 74HC595 Channel Relay Switching (1 per channel)
* 74HC595 Offset Voltage Switching
* 74HC595 Trigger Source Selection
* 74HC4051 Offset Voltage Switching

== Photos ==

<gallery>
File:DSO3254A_Front.jpg|Device, front panel
File:DSO3254A_Back.jpg|Device, back panel
File:DSO3254A_FrontPCB.jpg|PCB, top
File:DSO3254A_BackPCB.jpg|PCB, bottom
File:DSO3254A_FrontEnd.jpg|PCB, front end
</gallery>

== Communication Protocol ==
Using the ethernet port of the DSO3254A the SCPI protocol is utilized for communication.
The general format of the protocol is described within the manual [http://www.hantek.com/down.aspx?url=http%3a%2f%2fwww.hantek.com%2fProduct%2fDSO3000(A)%2fDSO3000(A)_SCPI_EN.pdf SCPI Protocol Documentation ]. Hereinafter more detailed description based on experiments is given.

The official application provided by the vendor uses the following three commands in a loop to continously get data from the device.

* SETUp:ALL?
* SOURce:SETUp:ALL?
* WAV:DATA:DISP

The first query will be responded with current settings of the analog channels, the time base, the different trigger
settings and the settings for the digital channel aka logic analyzer.

The second query will be responded with current settings of the integrated signal generator.

The last command will be responded with current acquisition data. Interesstingly this query doesn't follow the common scheme for queries, which are terminated
by a question mark.

All frames are terminated by ASCII encoded '\n' (newline).

According to the description of the manual a data frame starts with '#' followed by the amount of characters which will contain the amount of bytes transferred.
Unfortunatly there seems to be a bug here as a data frame consists of a header, which should be all ASCII encoded characters, and the samples, which are binary
encoded. However during the experiments it turns out, that an empty data acquisition frame contains the valid '#' followed by an ASCII encoded '9', but all other
'characters' are plain binary 0x00. The 128 bytes of the header should always be ASCII encoded.

So an invalid encoded response header looks like
#9..............................................................................................................................
where a more valid encoded response header looks like
#9000003317110000032000000000000050-050000000005.0e-015.0e-011.0e-021.0e-0211002.000e+05000001..................000000..........
Here the '.' are plain binary 0x00 instead of ASCII encoded 0x30 (which would be '0').
Let's interpret the more valid encoded response header.
* 000003317 is the amount of payload bytes including header in this frame without '#9000003317'
* 1 is the current operating status
* 1 is the trigger status
* 000003200 amount of bytes total (so the amount of data bytes of this acquisition, depends on memory depth)
* 000000000 amount of bytes already uploaded in this acquisition (so none here, this is the first frame)
* 0050 is the "offset" of analog channel 1, the unit is digits, visible screen is from -100 digits to +100 digits (the unit is different from that of the manual)
* 0-50 is the "offset" of analog channel 2
* 0000 is the "offset" of analog channel 3
* 0000 is the "offset" of analog channel 4
* 5.0e-01 is the "scale" of analog channel 1, the unit is V/div
* 5.0e-01 is the "scale" of analog channel 2
* 1.0e-02 is the "scale" of analog channel 3
* 1.0e-02 is the "scale" of analog channel 4
* 1 means channel 1 is enabled
* 1 means channel 2 is enabled
* 0 means channel 3 is disabled
* 0 means channel 4 is disabled
* 2.000e+05 is the sampling rate in samples/seconds
* 000001 something about multiple sampling..., #fixme What does this mean?
* ......... this represents the current trigger time frame. As can been seen it is all binary 0x00 instead of ASCII '0', #fixme What does this mean?
* ......... something about aquistion time..., #fixme What does this mean?
* 000 is the ASCII encoded representation of what digital channels of POD 1 are enabled, here none, if digital channels D0 to D7 are enabled this is '255'
* 000 is the ASCII encoded representation of what digital channels of POD 2 are enabled, here none, if digital channels D8 to D15 are enabled this is '255'
* ......... reserved bits. As can be seen it is all binaray 0x00 instead of ASCII '0'
* . version, also encoded as binary instead of ASCII '0', #fixme What does this mean?

After the header, acquired data of the enabled channels will follow as plain binary values. The values of the analog channels are signed byte values, meaning
that values in the range from 0x80 to 0xFF are negative.
To calculate the voltage value accordingly to the binary value given, the formula is as follows.
voltage = ((raw - offset) * (1/25) * scale * probe)
Where
* voltage is the real world value
* raw is the signed byte value from the data frame, unit is digits
* offset is the offset of the analog channel, unit is digits
* (1/25) is a correctional factor. This comes from the fact that a div of the "screen" does have 25 digits, unit is 1/(digits/div)
* scale is the scale of the analog channel, unit is Volt/div
* probe is the scale of the probe (x1 or x10, for the probes shipped with the scope), unit is 1

So the formula and the units for a better understanding
voltage = ( raw - offset ) * (1 / 25 ) * scale * probe
[V] = ([digits] - [digits]) * [1 / (digits / div)] * [V / div] [1]

For digital channels the binary value of the frame represents the bit-pattern of the digital channels enabled.

If all channels are enabled, than the data in a frame is arranged as follows:
* Samples of analog channel 1
* Samples of analog channel 2
* Samples of analog channel 3
* Samples of analog channel 4
* Samples of digital channels D0-D7
* Samples of digital channels D8-D15

For a memory depth of 1600 Samples, there is only one frame to transfer. If memory depth is increased, then multiple frames may need to be
transfered to get all the samples out of the memory.
Each frame can have a maximum size of 12128 bytes including '#9'. The amount of bytes already transfered is sent with each frame. So it is
quite easy to keep track of the frames. Also the total amounts of bytes is given with each frame. This is indeed the number of samples requested, by the
given memory depth value. So maximum is 128MSamples multiplied with the amount of channels enabled.

The maximum amount of channels enabled is 6. This is because digital channels D0-D7 are packed as one byte, same for digital channels D8-D15.
So the maximum value of samples to transfer is 768MSamples, if all channels are enabled.
From experiments it can be stated that this amount of samples take quite a long time to be transfered, as 64000 frames (with 12000 payload bytes)
has to be received.

== Resources ==

* [http://www.hantek.com/down.aspx?url=http%3a%2f%2fwww.hantek.com%2fProduct%2fDSO3000(A)%2fDSO3000(A)_Manual_EN.pdf Manual]
* [http://www.hantek.com/down.aspx?url=http%3a%2f%2fwww.hantek.com%2fProduct%2fDSO3000(A)%2fDSO3000A_Firmware.zip Vendor firmware]
* [http://www.hantek.com/down.aspx?url=http%3a%2f%2fwww.hantek.com%2fProduct%2fDSO3000(A)%2fDSO3000(A)_SCPI_EN.pdf SCPI Protocol Documentation ]
* [http://www.hantek.com/down.aspx?url=http%3a%2f%2fwww.hantek.com%2fProduct%2fDSO3000(A)%2fDSO3000A_Software.zip Vendor Windows software]
* [http://www.hantek.com/download/DSO3000(A)_Linux.zip Vendor Linux firmware source]

[[Category:Device]]
[[Category:Oscilloscope]]
[[Category:Logic analyzer]]
[[Category:Planned]]

Hantek DSO3254A

2021-02-20T15:15:09Z

BenKi: /* Communication Protocol */

{{Infobox logic analyzer
| image = [[File:DSO3254A.jpg|180px]]
| name = Hantek DSO3254A
| status = planned
| source_code_dir =
| channels = 4 analog, 16 digital
| samplerate = 250MHz
| samplerate_state = —
| triggers = edge, pulse, video, slope, timeout, external
| voltages = -0.5V — 400V
| memory = 128MSamples per channel
| compression = none
| website = [http://www.hantek.com/en/ProductDetail_2_134.html hantek.com]
}}

The '''Hantek DSO3254A''' is a USB-based signal acquisition device. It has 4 analog channels with 250MHz bandwidth and sampling rate of 1GSa/s. It comes with 16 channel logic analyzer with a maximum sampling rate of 250MHz and an arbritary waveform generator 200MSa/s.

See [[Hantek DSO3254A/Info]] for more details (such as '''lsusb -v''' output) about the device.

== Hardware ==

* S3C2416XH-40 System Controller (400 MHz ARM926EJ with 48 MHz and 12 MHz oscillators with 32.768 kHz RTC oscillator)
* D9SBJ System Memory (MT47H32M16NF-25E - 400 MHz 32MB x 16 DDR2-800)
* D9RZH Acquisition Memory (MT47H64M16NF-25E - 400 MHz 64MB x 16 DDR2-800)
* K9F1G08U0E 128MB x 8 NAND Flash
* 24L64 I2C EEPROM
* DM9000AEP LAN Controller
* USB Wi-Fi Module (optional)
* USB Hub (optional)
* XC6SLX16FTG256 Control FPGA (under heatsink - has JTAG)
* 1 GSPS 8-bit Quad ADC (under heatsink - Analog Devices?)
* ADF4905 Timebase Generator PLL (with 10 MHz reference oscillator)
* LTC2601 x2 (?) 12 Bit Offset DAC
* DAC902E 165 MSPS 12 Bit Waveform Generator DAC
* 74HC595 Channel Relay Switching (1 per channel)
* 74HC595 Offset Voltage Switching
* 74HC595 Trigger Source Selection
* 74HC4051 Offset Voltage Switching

== Photos ==

<gallery>
File:DSO3254A_Front.jpg|Device, front panel
File:DSO3254A_Back.jpg|Device, back panel
File:DSO3254A_FrontPCB.jpg|PCB, top
File:DSO3254A_BackPCB.jpg|PCB, bottom
File:DSO3254A_FrontEnd.jpg|PCB, front end
</gallery>

== Communication Protocol ==
Using the ethernet port of the DSO3254A the SCPI protocol is utilized for communication.
The general format of the protocol is described within the manual [[]]. Hereinafter more detailed description based on experiments is given.

The official application provided by the vendor uses the following three commands in a loop to continously get data from the device.

* SETUp:ALL?
* SOURce:SETUp:ALL?
* WAV:DATA:DISP

The first query will be responded with current settings of the analog channels, the time base, the different trigger
settings and the settings for the digital channel aka logic analyzer.

The second query will be responded with current settings of the integrated signal generator.

The last command will be responded with current acquisition data. Interesstingly this query doesn't follow the common scheme for queries, which are terminated
by a question mark.

All frames are terminated by ASCII encoded '\n' (newline).

According to the description of the manual a data frame starts with '#' followed by the amount of characters which will contain the amount of bytes transferred.
Unfortunatly there seems to be a bug here as a data frame consists of a header, which should be all ASCII encoded characters, and the samples, which are binary
encoded. However during the experiments it turns out, that an empty data acquisition frame contains the valid '#' followed by an ASCII encoded '9', but all other
'characters' are plain binary 0x00. The 128 bytes of the header should always be ASCII encoded.

So an invalid encoded response header looks like
#9..............................................................................................................................
where a more valid encoded response header looks like
#9000003317110000032000000000000050-050000000005.0e-015.0e-011.0e-021.0e-0211002.000e+05000001..................000000..........
Here the '.' are plain binary 0x00 instead of ASCII encoded 0x30 (which would be '0').
Let's interpret the more valid encoded response header.
* 000003317 is the amount of payload bytes including header in this frame without '#9000003317'
* 1 is the current operating status
* 1 is the trigger status
* 000003200 amount of bytes total (so the amount of data bytes of this acquisition, depends on memory depth)
* 000000000 amount of bytes already uploaded in this acquisition (so none here, this is the first frame)
* 0050 is the "offset" of analog channel 1, the unit is digits, visible screen is from -100 digits to +100 digits (the unit is different from that of the manual)
* 0-50 is the "offset" of analog channel 2
* 0000 is the "offset" of analog channel 3
* 0000 is the "offset" of analog channel 4
* 5.0e-01 is the "scale" of analog channel 1, the unit is V/div
* 5.0e-01 is the "scale" of analog channel 2
* 1.0e-02 is the "scale" of analog channel 3
* 1.0e-02 is the "scale" of analog channel 4
* 1 means channel 1 is enabled
* 1 means channel 2 is enabled
* 0 means channel 3 is disabled
* 0 means channel 4 is disabled
* 2.000e+05 is the sampling rate in samples/seconds
* 000001 something about multiple sampling..., #fixme What does this mean?
* ......... this represents the current trigger time frame. As can been seen it is all binary 0x00 instead of ASCII '0', #fixme What does this mean?
* ......... something about aquistion time..., #fixme What does this mean?
* 000 is the ASCII encoded representation of what digital channels of POD 1 are enabled, here none, if digital channels D0 to D7 are enabled this is '255'
* 000 is the ASCII encoded representation of what digital channels of POD 2 are enabled, here none, if digital channels D8 to D15 are enabled this is '255'
* ......... reserved bits. As can be seen it is all binaray 0x00 instead of ASCII '0'
* . version, also encoded as binary instead of ASCII '0', #fixme What does this mean?

After the header, acquired data of the enabled channels will follow as plain binary values. The values of the analog channels are signed byte values, meaning
that values in the range from 0x80 to 0xFF are negative.
To calculate the voltage value accordingly to the binary value given, the formula is as follows.
voltage = ((raw - offset) * (1/25) * scale * probe)
Where
* voltage is the real world value
* raw is the signed byte value from the data frame, unit is digits
* offset is the offset of the analog channel, unit is digits
* (1/25) is a correctional factor. This comes from the fact that a div of the "screen" does have 25 digits, unit is 1/(digits/div)
* scale is the scale of the analog channel, unit is Volt/div
* probe is the scale of the probe (x1 or x10, for the probes shipped with the scope), unit is 1

So the formula and the units for a better understanding
voltage = ( raw - offset ) * (1 / 25 ) * scale * probe
[V] = ([digits] - [digits]) * [1 / (digits / div)] * [V / div] [1]

For digital channels the binary value of the frame represents the bit-pattern of the digital channels enabled.

If all channels are enabled, than the data in a frame is arranged as follows:
* Samples of analog channel 1
* Samples of analog channel 2
* Samples of analog channel 3
* Samples of analog channel 4
* Samples of digital channels D0-D7
* Samples of digital channels D8-D15

For a memory depth of 1600 Samples, there is only one frame to transfer. If memory depth is increased, then multiple frames may need to be
transfered to get all the samples out of the memory.
Each frame can have a maximum size of 12128 bytes including '#9'. The amount of bytes already transfered is sent with each frame. So it is
quite easy to keep track of the frames. Also the total amounts of bytes is given with each frame. This is indeed the number of samples requested, by the
given memory depth value. So maximum is 128MSamples multiplied with the amount of channels enabled.

The maximum amount of channels enabled is 6. This is because digital channels D0-D7 are packed as one byte, same for digital channels D8-D15.
So the maximum value of samples to transfer is 768MSamples, if all channels are enabled.
From experiments it can be stated that this amount of samples take quite a long time to be transfered, as 64000 frames (with 12000 payload bytes)
has to be received.

== Resources ==

* [http://www.hantek.com/down.aspx?url=http%3a%2f%2fwww.hantek.com%2fProduct%2fDSO3000(A)%2fDSO3000(A)_Manual_EN.pdf Manual]
* [http://www.hantek.com/down.aspx?url=http%3a%2f%2fwww.hantek.com%2fProduct%2fDSO3000(A)%2fDSO3000A_Firmware.zip Vendor firmware]
* [http://www.hantek.com/down.aspx?url=http%3a%2f%2fwww.hantek.com%2fProduct%2fDSO3000(A)%2fDSO3000(A)_SCPI_EN.pdf SCPI Protocol Documentation ]
* [http://www.hantek.com/down.aspx?url=http%3a%2f%2fwww.hantek.com%2fProduct%2fDSO3000(A)%2fDSO3000A_Software.zip Vendor Windows software]
* [http://www.hantek.com/download/DSO3000(A)_Linux.zip Vendor Linux firmware source]

[[Category:Device]]
[[Category:Oscilloscope]]
[[Category:Logic analyzer]]
[[Category:Planned]]

Hantek DSO3254A

2021-02-20T15:14:20Z

BenKi: Corrected memory to 128MSamples per channel

{{Infobox logic analyzer
| image = [[File:DSO3254A.jpg|180px]]
| name = Hantek DSO3254A
| status = planned
| source_code_dir =
| channels = 4 analog, 16 digital
| samplerate = 250MHz
| samplerate_state = —
| triggers = edge, pulse, video, slope, timeout, external
| voltages = -0.5V — 400V
| memory = 128MSamples per channel
| compression = none
| website = [http://www.hantek.com/en/ProductDetail_2_134.html hantek.com]
}}

The '''Hantek DSO3254A''' is a USB-based signal acquisition device. It has 4 analog channels with 250MHz bandwidth and sampling rate of 1GSa/s. It comes with 16 channel logic analyzer with a maximum sampling rate of 250MHz and an arbritary waveform generator 200MSa/s.

See [[Hantek DSO3254A/Info]] for more details (such as '''lsusb -v''' output) about the device.

== Hardware ==

* S3C2416XH-40 System Controller (400 MHz ARM926EJ with 48 MHz and 12 MHz oscillators with 32.768 kHz RTC oscillator)
* D9SBJ System Memory (MT47H32M16NF-25E - 400 MHz 32MB x 16 DDR2-800)
* D9RZH Acquisition Memory (MT47H64M16NF-25E - 400 MHz 64MB x 16 DDR2-800)
* K9F1G08U0E 128MB x 8 NAND Flash
* 24L64 I2C EEPROM
* DM9000AEP LAN Controller
* USB Wi-Fi Module (optional)
* USB Hub (optional)
* XC6SLX16FTG256 Control FPGA (under heatsink - has JTAG)
* 1 GSPS 8-bit Quad ADC (under heatsink - Analog Devices?)
* ADF4905 Timebase Generator PLL (with 10 MHz reference oscillator)
* LTC2601 x2 (?) 12 Bit Offset DAC
* DAC902E 165 MSPS 12 Bit Waveform Generator DAC
* 74HC595 Channel Relay Switching (1 per channel)
* 74HC595 Offset Voltage Switching
* 74HC595 Trigger Source Selection
* 74HC4051 Offset Voltage Switching

== Photos ==

<gallery>
File:DSO3254A_Front.jpg|Device, front panel
File:DSO3254A_Back.jpg|Device, back panel
File:DSO3254A_FrontPCB.jpg|PCB, top
File:DSO3254A_BackPCB.jpg|PCB, bottom
File:DSO3254A_FrontEnd.jpg|PCB, front end
</gallery>

== Communication Protocol ==
Using the ethernet port of the DSO3254A the SCPI is utilized for communication.
The general format of the protocol is described within the manual [[]]. Hereinafter more detailed description based on experiments is given.

The official application provided by the vendor uses the following three commands in a loop to continously get data from the device.

* SETUp:ALL?
* SOURce:SETUp:ALL?
* WAV:DATA:DISP

The first query will be responded with current settings of the analog channels, the time base, the different trigger
settings and the settings for the digital channel aka logic analyzer.

The second query will be responded with current settings of the integrated signal generator.

The last command will be responded with current acquisition data. Interesstingly this query doesn't follow the common scheme for queries, which are terminated
by a question mark.

All frames are terminated by ASCII encoded '\n' (newline).

According to the description of the manual a data frame starts with '#' followed by the amount of characters which will contain the amount of bytes transferred.
Unfortunatly there seems to be a bug here as a data frame consists of a header, which should be all ASCII encoded characters, and the samples, which are binary
encoded. However during the experiments it turns out, that an empty data acquisition frame contains the valid '#' followed by an ASCII encoded '9', but all other
'characters' are plain binary 0x00. The 128 bytes of the header should always be ASCII encoded.

So an invalid encoded response header looks like
#9..............................................................................................................................
where a more valid encoded response header looks like
#9000003317110000032000000000000050-050000000005.0e-015.0e-011.0e-021.0e-0211002.000e+05000001..................000000..........
Here the '.' are plain binary 0x00 instead of ASCII encoded 0x30 (which would be '0').
Let's interpret the more valid encoded response header.
* 000003317 is the amount of payload bytes including header in this frame without '#9000003317'
* 1 is the current operating status
* 1 is the trigger status
* 000003200 amount of bytes total (so the amount of data bytes of this acquisition, depends on memory depth)
* 000000000 amount of bytes already uploaded in this acquisition (so none here, this is the first frame)
* 0050 is the "offset" of analog channel 1, the unit is digits, visible screen is from -100 digits to +100 digits (the unit is different from that of the manual)
* 0-50 is the "offset" of analog channel 2
* 0000 is the "offset" of analog channel 3
* 0000 is the "offset" of analog channel 4
* 5.0e-01 is the "scale" of analog channel 1, the unit is V/div
* 5.0e-01 is the "scale" of analog channel 2
* 1.0e-02 is the "scale" of analog channel 3
* 1.0e-02 is the "scale" of analog channel 4
* 1 means channel 1 is enabled
* 1 means channel 2 is enabled
* 0 means channel 3 is disabled
* 0 means channel 4 is disabled
* 2.000e+05 is the sampling rate in samples/seconds
* 000001 something about multiple sampling..., #fixme What does this mean?
* ......... this represents the current trigger time frame. As can been seen it is all binary 0x00 instead of ASCII '0', #fixme What does this mean?
* ......... something about aquistion time..., #fixme What does this mean?
* 000 is the ASCII encoded representation of what digital channels of POD 1 are enabled, here none, if digital channels D0 to D7 are enabled this is '255'
* 000 is the ASCII encoded representation of what digital channels of POD 2 are enabled, here none, if digital channels D8 to D15 are enabled this is '255'
* ......... reserved bits. As can be seen it is all binaray 0x00 instead of ASCII '0'
* . version, also encoded as binary instead of ASCII '0', #fixme What does this mean?

After the header, acquired data of the enabled channels will follow as plain binary values. The values of the analog channels are signed byte values, meaning
that values in the range from 0x80 to 0xFF are negative.
To calculate the voltage value accordingly to the binary value given, the formula is as follows.
voltage = ((raw - offset) * (1/25) * scale * probe)
Where
* voltage is the real world value
* raw is the signed byte value from the data frame, unit is digits
* offset is the offset of the analog channel, unit is digits
* (1/25) is a correctional factor. This comes from the fact that a div of the "screen" does have 25 digits, unit is 1/(digits/div)
* scale is the scale of the analog channel, unit is Volt/div
* probe is the scale of the probe (x1 or x10, for the probes shipped with the scope), unit is 1

So the formula and the units for a better understanding
voltage = ( raw - offset ) * (1 / 25 ) * scale * probe
[V] = ([digits] - [digits]) * [1 / (digits / div)] * [V / div] [1]

For digital channels the binary value of the frame represents the bit-pattern of the digital channels enabled.

If all channels are enabled, than the data in a frame is arranged as follows:
* Samples of analog channel 1
* Samples of analog channel 2
* Samples of analog channel 3
* Samples of analog channel 4
* Samples of digital channels D0-D7
* Samples of digital channels D8-D15

For a memory depth of 1600 Samples, there is only one frame to transfer. If memory depth is increased, then multiple frames may need to be
transfered to get all the samples out of the memory.
Each frame can have a maximum size of 12128 bytes including '#9'. The amount of bytes already transfered is sent with each frame. So it is
quite easy to keep track of the frames. Also the total amounts of bytes is given with each frame. This is indeed the number of samples requested, by the
given memory depth value. So maximum is 128MSamples multiplied with the amount of channels enabled.

The maximum amount of channels enabled is 6. This is because digital channels D0-D7 are packed as one byte, same for digital channels D8-D15.
So the maximum value of samples to transfer is 768MSamples, if all channels are enabled.
From experiments it can be stated that this amount of samples take quite a long time to be transfered, as 64000 frames (with 12000 payload bytes)
has to be received.

== Resources ==

* [http://www.hantek.com/down.aspx?url=http%3a%2f%2fwww.hantek.com%2fProduct%2fDSO3000(A)%2fDSO3000(A)_Manual_EN.pdf Manual]
* [http://www.hantek.com/down.aspx?url=http%3a%2f%2fwww.hantek.com%2fProduct%2fDSO3000(A)%2fDSO3000A_Firmware.zip Vendor firmware]
* [http://www.hantek.com/down.aspx?url=http%3a%2f%2fwww.hantek.com%2fProduct%2fDSO3000(A)%2fDSO3000(A)_SCPI_EN.pdf SCPI Protocol Documentation ]
* [http://www.hantek.com/down.aspx?url=http%3a%2f%2fwww.hantek.com%2fProduct%2fDSO3000(A)%2fDSO3000A_Software.zip Vendor Windows software]
* [http://www.hantek.com/download/DSO3000(A)_Linux.zip Vendor Linux firmware source]

[[Category:Device]]
[[Category:Oscilloscope]]
[[Category:Logic analyzer]]
[[Category:Planned]]

Hantek DSO3254A

2021-02-20T15:13:23Z

BenKi: Added section Communication Protocol

{{Infobox logic analyzer
| image = [[File:DSO3254A.jpg|180px]]
| name = Hantek DSO3254A
| status = planned
| source_code_dir =
| channels = 4 analog, 16 digital
| samplerate = 250MHz
| samplerate_state = —
| triggers = edge, pulse, video, slope, timeout, external
| voltages = -0.5V — 400V
| memory = 128M
| compression = none
| website = [http://www.hantek.com/en/ProductDetail_2_134.html hantek.com]
}}

The '''Hantek DSO3254A''' is a USB-based signal acquisition device. It has 4 analog channels with 250MHz bandwidth and sampling rate of 1GSa/s. It comes with 16 channel logic analyzer with a maximum sampling rate of 250MHz and an arbritary waveform generator 200MSa/s.

See [[Hantek DSO3254A/Info]] for more details (such as '''lsusb -v''' output) about the device.

== Hardware ==

* S3C2416XH-40 System Controller (400 MHz ARM926EJ with 48 MHz and 12 MHz oscillators with 32.768 kHz RTC oscillator)
* D9SBJ System Memory (MT47H32M16NF-25E - 400 MHz 32MB x 16 DDR2-800)
* D9RZH Acquisition Memory (MT47H64M16NF-25E - 400 MHz 64MB x 16 DDR2-800)
* K9F1G08U0E 128MB x 8 NAND Flash
* 24L64 I2C EEPROM
* DM9000AEP LAN Controller
* USB Wi-Fi Module (optional)
* USB Hub (optional)
* XC6SLX16FTG256 Control FPGA (under heatsink - has JTAG)
* 1 GSPS 8-bit Quad ADC (under heatsink - Analog Devices?)
* ADF4905 Timebase Generator PLL (with 10 MHz reference oscillator)
* LTC2601 x2 (?) 12 Bit Offset DAC
* DAC902E 165 MSPS 12 Bit Waveform Generator DAC
* 74HC595 Channel Relay Switching (1 per channel)
* 74HC595 Offset Voltage Switching
* 74HC595 Trigger Source Selection
* 74HC4051 Offset Voltage Switching

== Photos ==

<gallery>
File:DSO3254A_Front.jpg|Device, front panel
File:DSO3254A_Back.jpg|Device, back panel
File:DSO3254A_FrontPCB.jpg|PCB, top
File:DSO3254A_BackPCB.jpg|PCB, bottom
File:DSO3254A_FrontEnd.jpg|PCB, front end
</gallery>

== Communication Protocol ==
Using the ethernet port of the DSO3254A the SCPI is utilized for communication.
The general format of the protocol is described within the manual [[]]. Hereinafter more detailed description based on experiments is given.

The official application provided by the vendor uses the following three commands in a loop to continously get data from the device.

* SETUp:ALL?
* SOURce:SETUp:ALL?
* WAV:DATA:DISP

The first query will be responded with current settings of the analog channels, the time base, the different trigger
settings and the settings for the digital channel aka logic analyzer.

The second query will be responded with current settings of the integrated signal generator.

The last command will be responded with current acquisition data. Interesstingly this query doesn't follow the common scheme for queries, which are terminated
by a question mark.

All frames are terminated by ASCII encoded '\n' (newline).

According to the description of the manual a data frame starts with '#' followed by the amount of characters which will contain the amount of bytes transferred.
Unfortunatly there seems to be a bug here as a data frame consists of a header, which should be all ASCII encoded characters, and the samples, which are binary
encoded. However during the experiments it turns out, that an empty data acquisition frame contains the valid '#' followed by an ASCII encoded '9', but all other
'characters' are plain binary 0x00. The 128 bytes of the header should always be ASCII encoded.

So an invalid encoded response header looks like
#9..............................................................................................................................
where a more valid encoded response header looks like
#9000003317110000032000000000000050-050000000005.0e-015.0e-011.0e-021.0e-0211002.000e+05000001..................000000..........
Here the '.' are plain binary 0x00 instead of ASCII encoded 0x30 (which would be '0').
Let's interpret the more valid encoded response header.
* 000003317 is the amount of payload bytes including header in this frame without '#9000003317'
* 1 is the current operating status
* 1 is the trigger status
* 000003200 amount of bytes total (so the amount of data bytes of this acquisition, depends on memory depth)
* 000000000 amount of bytes already uploaded in this acquisition (so none here, this is the first frame)
* 0050 is the "offset" of analog channel 1, the unit is digits, visible screen is from -100 digits to +100 digits (the unit is different from that of the manual)
* 0-50 is the "offset" of analog channel 2
* 0000 is the "offset" of analog channel 3
* 0000 is the "offset" of analog channel 4
* 5.0e-01 is the "scale" of analog channel 1, the unit is V/div
* 5.0e-01 is the "scale" of analog channel 2
* 1.0e-02 is the "scale" of analog channel 3
* 1.0e-02 is the "scale" of analog channel 4
* 1 means channel 1 is enabled
* 1 means channel 2 is enabled
* 0 means channel 3 is disabled
* 0 means channel 4 is disabled
* 2.000e+05 is the sampling rate in samples/seconds
* 000001 something about multiple sampling..., #fixme What does this mean?
* ......... this represents the current trigger time frame. As can been seen it is all binary 0x00 instead of ASCII '0', #fixme What does this mean?
* ......... something about aquistion time..., #fixme What does this mean?
* 000 is the ASCII encoded representation of what digital channels of POD 1 are enabled, here none, if digital channels D0 to D7 are enabled this is '255'
* 000 is the ASCII encoded representation of what digital channels of POD 2 are enabled, here none, if digital channels D8 to D15 are enabled this is '255'
* ......... reserved bits. As can be seen it is all binaray 0x00 instead of ASCII '0'
* . version, also encoded as binary instead of ASCII '0', #fixme What does this mean?

After the header, acquired data of the enabled channels will follow as plain binary values. The values of the analog channels are signed byte values, meaning
that values in the range from 0x80 to 0xFF are negative.
To calculate the voltage value accordingly to the binary value given, the formula is as follows.
voltage = ((raw - offset) * (1/25) * scale * probe)
Where
* voltage is the real world value
* raw is the signed byte value from the data frame, unit is digits
* offset is the offset of the analog channel, unit is digits
* (1/25) is a correctional factor. This comes from the fact that a div of the "screen" does have 25 digits, unit is 1/(digits/div)
* scale is the scale of the analog channel, unit is Volt/div
* probe is the scale of the probe (x1 or x10, for the probes shipped with the scope), unit is 1

So the formula and the units for a better understanding
voltage = ( raw - offset ) * (1 / 25 ) * scale * probe
[V] = ([digits] - [digits]) * [1 / (digits / div)] * [V / div] [1]

For digital channels the binary value of the frame represents the bit-pattern of the digital channels enabled.

If all channels are enabled, than the data in a frame is arranged as follows:
* Samples of analog channel 1
* Samples of analog channel 2
* Samples of analog channel 3
* Samples of analog channel 4
* Samples of digital channels D0-D7
* Samples of digital channels D8-D15

For a memory depth of 1600 Samples, there is only one frame to transfer. If memory depth is increased, then multiple frames may need to be
transfered to get all the samples out of the memory.
Each frame can have a maximum size of 12128 bytes including '#9'. The amount of bytes already transfered is sent with each frame. So it is
quite easy to keep track of the frames. Also the total amounts of bytes is given with each frame. This is indeed the number of samples requested, by the
given memory depth value. So maximum is 128MSamples multiplied with the amount of channels enabled.

The maximum amount of channels enabled is 6. This is because digital channels D0-D7 are packed as one byte, same for digital channels D8-D15.
So the maximum value of samples to transfer is 768MSamples, if all channels are enabled.
From experiments it can be stated that this amount of samples take quite a long time to be transfered, as 64000 frames (with 12000 payload bytes)
has to be received.

== Resources ==

* [http://www.hantek.com/down.aspx?url=http%3a%2f%2fwww.hantek.com%2fProduct%2fDSO3000(A)%2fDSO3000(A)_Manual_EN.pdf Manual]
* [http://www.hantek.com/down.aspx?url=http%3a%2f%2fwww.hantek.com%2fProduct%2fDSO3000(A)%2fDSO3000A_Firmware.zip Vendor firmware]
* [http://www.hantek.com/down.aspx?url=http%3a%2f%2fwww.hantek.com%2fProduct%2fDSO3000(A)%2fDSO3000(A)_SCPI_EN.pdf SCPI Protocol Documentation ]
* [http://www.hantek.com/down.aspx?url=http%3a%2f%2fwww.hantek.com%2fProduct%2fDSO3000(A)%2fDSO3000A_Software.zip Vendor Windows software]
* [http://www.hantek.com/download/DSO3000(A)_Linux.zip Vendor Linux firmware source]

[[Category:Device]]
[[Category:Oscilloscope]]
[[Category:Logic analyzer]]
[[Category:Planned]]

Agilent U12xxx series

2020-12-06T18:51:18Z

BenKi: Added IDN string of Agilent 1253B

The Agilent U12xxx series are handheld digital multimeters, ranging from inexpensive all-purpose meters to industrial meters.

{| border="0" style="width: 40em; font-size: smaller" class="alternategrey sigroktable"
|-
! style="widthx: 5em; text-align: left;" | Model
! style="widthx: 4em; text-align: left;" | Counts
! style="widthx: 4em; text-align: left;" | Supported
|-
| U1231A
| 6000
| style="background-color: lime" | Yes
|-
| [[Agilent U1232A|U1232A]]
| 6000
| style="background-color: lime" | Yes
|-
| U1233A
| 6000
| style="background-color: lime" | Yes
|-
| U1241A / U1241B
| 10000
| style="background-color: lime" | Yes
|-
| U1241C
| 10000
| style="background-color: lime" | Yes
|-
| U1242A / U1242B
| 10000
| style="background-color: lime" | Yes
|-
| [[Keysight_U1242C|U1242C]]
| 10000
| style="background-color: lime" | Yes
|-
| U1251A / U1251B
| 50000
| style="background-color: lime" | Yes
|-
| U1252A / U1252B
| 50000
| style="background-color: lime" | Yes
|-
| U1253A / U1253B
| 50000
| style="background-color: lime" | Yes
|-
| U1271A
| 30000
| style="background-color: lime" | Yes
|-
| [[Agilent U1272A|U1272A]]
| 30000
| style="background-color: lime" | Yes
|-
| U1273A
| 30000
| style="background-color: lime" | Yes
|-
| U1273AX
| 30000
| style="background-color: lime" | Yes
|-
| U1281A
| 60000
| style="background-color: lime" | Yes
|-
| U1282A
| 60000
| style="background-color: lime" | Yes
|}

Is your model not supported yet? Get in touch! We need people to help us test other models in this series, and getting a new model supported is generally quick & easy.

== Connection ==

All models communicate via an optically isolated serial connection, usually at 9600 bps, 8 bits, no parity, and 1 stop bit (9600/8n1). Some models allow the user to change the serial parameters (e.g. the U1272A supports 9600/19200 baud, 7/8bits, parity odd/even/none).

Connecting to the devices can be done either via USB ([[Device cables#Agilent_U1173A|U1173A cable]] or [[Device cables#Agilent_U1173B|U1173B cable]]) or Bluetooth ([[Device cables#Agilent_U1177A|U1177A interface]]).

== Protocol ==
All models in this series use generally the same protocol, with only minor differences between models – and none within the same range.

The meters will respond to commands, which consist of a short ASCII string followed by either LF or CR+LF. The meter will either send no response at all, some ASCII text followed by CR+LF, or <code>*E</code> followed by CR+LF if the command given was invalid.

Some events (such as turning the rotary switch) will cause spontaneous transmissions of event notifiers. These consist of a <code>*</code> character, a single character and CR+LF.

=== *IDN? ===
Sending the command <code>*IDN?</code> causes the device to return a comma-separated four-field string, compatible with the identical GPIB command. The four fields are vendor name, model name, serial number and version:

Agilent Technologies,U1232A,MY52020136,V1.00
Agilent Technologies,U1253B,MY5''xxxxxxx'',V2.26
Agilent Technologies,U1272A,MY5''xxxxxxx'',V2.04
Keysight Technologies,U1242C,MY5''xxxxxxx'',V1.20
Keysight Technologies,U1282A,MY5''xxxxxxx'',V1.03

=== *RST ===
Sending the command <code>*RST</code> causes the device to reset. The response is an asterisk followed by the current dial position, for example <code>*1</code> indicates the first position.

=== SYST:BATT? ===
The command <code>SYST:BATT?</code> returns a value indicating the device's battery level. The value is in a different format depending on the model series:

The U123xx, U124xC, U127xx and U128xx models return a percentage value, like this:
36%

The U124xx and U125xx models return a value like this:
+1.04200000E+02

=== SYST:BEEP ===
The command <code>SYST:BEEP</code> or <code>SYST:BEEP TONE</code> makes the multimeter emit a beep.

=== SYST:BLIT ===
The commands <code>SYST:BLIT 1</code> and <code>SYST:BLIT 0</code> turn the screen backlight on and off. There is no response. The backlight timer will still run and turn the backlight back off again if it is enabled.

The U127x devices don't seem to support this command.

=== FETC? ===
The <code>FETC?</code> command returns the current measured value, as a floating point ASCII string, as in the following examples:

+9.25000000E-03
+0.00000000E+00
-1.01140000E+00
-9.10200000E-01

The sign characters are always present, and the value is always in normalized scientific format. This applies even when in a mode that uses integer numbers, 11 would be transmitted as <code>+1.10000000E+01</code>. If no valid measurement is available, i.e. the display shows "OL" or "-OL", the transmitted value is either <code>+9.90000000E+37</code> and <code>-9.90000000E+37</code> respectively.

For models with dual display, the <code>FETC? @2</code> command returns the current value from the secondary display, in the same format.

=== CONF: ===
The <code>CONF:</code> commands can be used to change modes and ranges on the multimeter. It is not to be confused with the <code>CONF?</code> query described below.

For a given rotary switch position, only those CONF: commands work that switch to modes that can be reached by pressing the range or shift buttons.

==== U123xx models ====
{| border="0" width="95%" style="font-size: smaller" class="alternategrey sortable sigroktable"
|-
! style="width: 12em;" | Command
! style="width: 15em;" | Rotary Switch Setting
! Meaning

|-
| <code>CONF:VOLT:AC</code>
| Any voltage mode
| Switch to Volts AC mode with autoranging

|-
| <code>CONF:VOLT:DC</code>
| Any voltage mode
| Switch to Volts DC mode with autoranging

|-
| <code>CONF:VOLT:AC 600</code>
| Any voltage mode
| Switch to Volts AC mode and 600V range. Valid ranges are: 600, 60, 6, 0.6

|-
| <code>CONF:VOLT:AC 600</code>
| Any voltage mode
| Switch to Volts AC mode and 600V range. Valid ranges are: 600, 60, 6, 0.6

|-
| <code>CONF:CURR:AC</code>
| Any current mode
| Switch to AC current measurement mode with autoranging

|-
| <code>CONF:CURR:DC</code>
| Any current mode
| Switch to DC current measurement mode with autoranging

|-
| <code>CONF:CURR:AC 60u</code>
| Any current mode
| Switch to AC current measurement mode and 60uA range. Valid ranges are 10, 6 for A mode, and 600u, 60u for uA mode.

|-
| <code>CONF:CURR:DC 60u</code>
| Any current mode
| Switch to DC current measurement mode and 60uA range. Valid ranges are 10, 6 for A mode, and 600u, 60u for uA mode.

|-
| <code>CONF:FREQ</code>
| VZlow, AC voltage or any current mode
| Switch to frequency measurement mode. No manual ranges are available.

|-
| <code>CONF:CONT</code>
| Resistance
| Switch to continuity mode.

|-
| <code>CONF:RES</code>
| Resistance
| Switch to resistance mode with autoranging.

|-
| <code>CONF:RES 6M</code>
| Resistance
| Switch to resistance mode and 6MΩ range. Valid ranges are 60M, 6M, 600k, 60k 6k, 600

|-
| <code>CONF:CAP</code>
| Capacitance
| Switch to capacitance mode with autoranging.

|-
| <code>CONF:CAP 1000n</code>
| Capacitance
| Switch to capacitance mode and 1000nF range. Valid ranges are: 10m, 1000u, 100u, 10u, 1000n

|}

==== U124xx/U125xx models ====

Same as above for the U123xx, except for different ranges.

=== CONF? ===
The <code>CONF?</code> command queries the device's current measurement configuration.

==== U123xx models ====
This can be either one, two or three comma-separated fields. The number of fields depends on the first field's value, but the second field always denotes the measurement mode's range and resolution, and the third field is the current type (AC or DC). For example, this indicates AC voltage in the 600mV range:
V,0,AC

{| border="0" width="95%" style="font-size: smaller" class="alternategrey sortable sigroktable"
|-
! style="width: 3em;" | Mode
! style="width: 3em;" | Resolution
! style="width: 3em;" | Current
! Meaning

|-
| V
| y
| y
| '''Volts'''

|-
|
| 0
|
| Range 600mV, resolution 0.1mV

|-
|
| 1
|
| Range 6V, resolution 1mV

|-
|
| 2
|
| Range 60V, resolution 0.01V

|-
|
| 3
|
| Range 600V, resolution 0.1V

|-
| MV
| y
| y
| '''Millivolts'''

|-
|
| 1
|
| Range 600mV, resolution 0.1mV

|-
| A
| y
| y
| '''Ampere'''

|-
|
| 0
|
| Range 6A, resolution 1mA

|-
|
| 1
|
| Range 10A, resolution 0.01A

|-
| UA
| y
| y
| '''Microampere'''

|-
|
| 0
|
| Range 60μA, resolution 0.01μA

|-
|
| 1
|
| Range 600μA, resolution 0.1μA

|-
| FREQ
| y
| y
| '''AC frequency'''

|-
|
| 0
|
| Range 99.9 Hz, resolution 0.01 Hz

|-
|
| 1
|
| Range 999.9 Hz, resolution 0.1 Hz

|-
|
| 2
|
| Range 9.999 kHz, resolution 1 Hz

|-
|
| 3
|
| Range 99.99 kHz, resolution 10 Hz

|-
|
| 4
|
| Range 200 kHz, resolution 100 Hz

|-
| RES
| y
| n
| '''Resistance'''

|-
|
| 0
|
| Range 600Ω, resolution 0.1Ω

|-
|
| 1
|
| Range 6kΩ, resolution 0.001kΩ

|-
|
| 2
|
| Range 60kΩ, resolution 0.01kΩ

|-
|
| 3
|
| Range 600kΩ, resolution 0.1kΩ

|-
|
| 4
|
| Range 6MΩ, resolution 0.001MΩ

|-
|
| 5
|
| Range 60MΩ, resolution 0.01MΩ

|-
| CAP
| y
| n
| '''Capacitance'''

|-
|
| 0
|
| Range 1000nF, resolution 1nF

|-
|
| 1
|
| Range 10μF, resolution 0.01μF

|-
|
| 2
|
| Range 100μF, resolution 0.1μF

|-
|
| 3
|
| Range 1000μF, resolution 1μF

|-
|
| 4
|
| Range 10mF, resolution 0.01mF

|-
| DIOD
| n
| n
| '''Diode'''

|}

==== U124xx and U125xx models ====
The output consists of a quoted string with the meter's mode, followed by a space, two values, separated by a comma, denoting the current range, and the value of one count. The mode may optionally include a colon followed by a code denoting a submode relevant to that major mode.
For example, AC voltage mode with 1000mV range on a 10000-count U1241B would be given as:
"VOLT:AC +1.000000E+00,+1.000000E-04"

{| border="0" width="95%" style="font-size: smaller" class="alternategrey sortable sigroktable"
|-
! style="width: 5em;" | Mode
! Meaning
|-
| <code>VOLT</code>
| DC voltage
|-
| <code>VOLT:AC</code>
| AC voltage
|-
| <code>CURR</code>
| DC current
|-
| <code>CURR:AC</code>
| AC current
|-
| <code>FREQ</code>
| Frequency counter
|-
| <code>DIOD</code>
| Diode check. No range values are given.
|-
| <code>CONT</code>
| Continuity. No range values are given.
|-
| <code>RES</code>
| Resistance
|-
| <code>CAP</code>
| Capacitance
|-
| <code>SCOU</code>
| Switch counter. No range values are given.
|-
| <code>CPER:0-20mA</code>
| Current loop, 0-20mA setting
|-
| <code>CPER:4-20mA</code>
| Current loop, 4-20mA setting
|-
| <code>T1:K</code> or <code>T2:K</code>
| Temperature on T1 or T2, submode can be K or J, denoting the thermocouple type. Instead of range values, <code>CEL</code> or <code>FAR</code> is given, denoting the measurement is in degrees Celsius or Fahrenheit. The full response might thus be: <code>"T1:K CEL"</code>.
|}

==== U124xC ====
The output is very similar to the U124xx and U125xx models with a few differences and additions.

{| border="0" width="95%" style="font-size: smaller" class="alternategrey sortable sigroktable"
|-
! style="width: 5em;" | Mode
! Meaning
|-
| <code>VOLT</code>
| DC voltage
|-
| <code>VOLT:AC</code>
| AC voltage
|-
| <code>VOLT:HRAT</code>
| Harmonic Ratio
|-
| <code>CURR</code>
| DC current
|-
| <code>CURR:AC</code>
| AC current
|-
| <code>FREQ</code> <code>FREQ:AC</code>
| Frequency
|-
| <code>DIOD</code>
| Diode check. No range values are given.
|-
| <code>CONT</code>
| Continuity
|-
| <code>RES</code>
| Resistance
|-
| <code>CAP</code>
| Capacitance
|-
| <code>CPER:0-20mA</code>
| Current loop, 0-20mA setting
|-
| <code>CPER:4-20mA</code>
| Current loop, 4-20mA setting
|-
| <code>TEMP</code>
| Internal temperature. No range values are given.
|-
| <code>TEMP:K</code>
| Temperature, submode can be K or J, denoting the thermocouple type. Instead of range values, <code>CEL</code> or <code>FAR</code> is given, denoting the measurement is in degrees Celsius or Fahrenheit. The full response might thus be: <code>"TEMP:K CEL"</code>.
|-
| <code>NCV</code>
| Vsense (Non-contact Voltage). Instead of range values, <code>HI</code> or <code>LO</code> is given, denoting High sensivity or Low sensivity. The full response might thus be: <code>"NCV HI"</code>.
|}

==== U128xx ====
The output is very similar to the U124xC model with a few additions.

{| border="0" width="95%" style="font-size: smaller" class="alternategrey sortable sigroktable"
|-
! style="width: 5em;" | Mode
! Meaning
|-
| <code>VOLT</code>
| DC voltage
|-
| <code>VOLT:AC</code>
| AC voltage
|-
| <code>VOLT:ACDC</code>
| AC+DC voltage
|-
| <code>CURR</code>
| DC current
|-
| <code>CURR:AC</code>
| AC current
|-
| <code>CURR:ACDC</code>
| AC+DC current
|-
| <code>FREQ</code> <code>FREQ:AC</code>
| Frequency
|-
| <code>PULS:PWID</code> <code>PULS:PWID:AC</code>
| Pulse width
|-
| <code>PULS:PDUT</code>
| Duty cycle. No range values are given.
|-
| <code>FC1</code>
| Frequency counter (0.5 Hz to 10 MHz)
|-
| <code>FC100</code>
| Frequency counter (1 MHz to 100 MHz)
|-
| <code>DIOD</code>
| Diode check. No range values are given.
|-
| <code>CONT</code>
| Continuity
|-
| <code>RES</code>
| Resistance
|-
| <code>COND</code>
| Conductance
|-
| <code>CAP</code>
| Capacitance
|-
| <code>CPER:0-20mA</code>
| Current loop, 0-20mA setting
|-
| <code>CPER:4-20mA</code>
| Current loop, 4-20mA setting
|-
| <code>TEMP</code>
| Internal temperature. No range values are given.
|-
| <code>TEMP:K</code>
| Temperature, submode can be K or J, denoting the thermocouple type. Instead of range values, <code>CEL</code> or <code>FAR</code> is given, denoting the measurement is in degrees Celsius or Fahrenheit. The full response might thus be: <code>"TEMP:K CEL"</code>.
|-
| <code>SQU</code>
| Square wave output. No range values are given.
|-
| <code>NCV</code>
| Vsense (Non-contact Voltage). Instead of range values, <code>HIGH</code> or <code>LOW</code> is given, denoting High sensivity or Low sensivity. The full response might thus be: <code>"NCV HIGH"</code>.
|}

=== STAT? ===

The <code>STAT?</code> command is used to query the current state of the device. The response is a quoted 21-byte string, like this:

"000000000110L00000000"

==== U123xx models ====
{| border="0" width="95%" style="font-size: smaller" class="alternategrey sortable sigroktable"
|-
! style="width: 3em;" | Byte
! style="width: 3em;" | Value
! Meaning

|-
| 1
|
| '''Max/min/avg mode'''
|-
| || 0 || Off
|-
| || 1 || On

|-
| 2
|
| '''Relative measurement'''. The last value returned from FETC? before this mode was enabled denotes the stored reference value.
|-
| || 0 || Off
|-
| || 1 || On

|-
| 3
|
| '''Trig hold-log'''
|-
| || 0 || Off
|-
| || 1 || On

|-
| 4
|
| '''Auto hold-log'''
|-
| || 0 || Off
|-
| || 1 || On

|-
| 5
|
| '''LED flashlight'''
|-
| || 0 || Off
|-
| || 1 || On

|-
| 6
|
| '''LCD backlight'''
|-
| || 0 || Off
|-
| || 1 || On

|-
| 7
|
| '''Smoothing'''
|-
| || 0 || Off
|-
| || 1 || On

|-
| 8
|
| '''Temp/aux mode'''. When on and rotary switch is in position 5 (capacitance), CONF? returns <code>MV,1,DC</code>, but the value returned from FETC? instead denotes the temperature, in the unit (F or C) according to the meter's configuration.
|-
| || 0 || Off
|-
| || 1 || On

|- style="background-color: red;"
| 9
|
| ''Unknown (always 0)''

|-
| 10
|
| '''Beep frequency'''
|-
|
| 0
| 4.2kHz
|-
|
| 1
| 3.8kHz (default)
|-
|
| 2
| 3.4kHz
|-
|
| 3
| 3.2kHz
|-
|
| 4
| Off

|-
| 11
|
| '''Auto power-off''' (APO)
|-
| || 0 || Off
|-
| || 1 || On

|- style="background-color: red;"
| 12
|
| ''Unknown (always 0)''

|- style="background-color: red;"
| 13
|
| ''Unknown (always L)''

|- style="background-color: red;"
| 14-15
|
| ''Unknown (always 0)''

|-
| 16
|
| '''Rotary switch position'''
|-
|
| 0
| V/Zlow
|-
|
| 1
| Voltage AC
|-
|
| 2
| Voltage DC
|-
|
| 3
| Resistance
|-
|
| 4
| Diode
|-
|
| 5
| Capacitance
|-
|
| 6
| Current
|-
|
| 7
| Microcurrent

|-
| 17
|
| '''Continuity mode'''. When enabled, the value returned from FETC? is either NAN (no continuity) or any real value to denote continuity.
|-
| || 0 || Off
|-
| || 1 || On

|- style="background-color: red;"
| 18
|
| ''Unknown (always 0)''

|-
| 19
|
| '''Battery low indicator'''
|-
| || 0 || Battery OK
|-
| || 1 || Battery low

|- style="background-color: red;"
| 20-21
|
| ''Unknown (always 0)''

|}

==== U124xx models ====
{| border="0" width="95%" style="font-size: smaller" class="alternategrey sortable sigroktable"
|-
! style="width: 3em;" | Byte
! style="width: 3em;" | Value
! Meaning

|-
| 1 || || '''Max/min/avg mode'''
|-
| || 0 || Off
|-
| || 1 || On

|-
| 2 || || '''Relative measurement'''. The last value returned from FETC? before this mode was enabled denotes the stored reference value.
|-
| || 0 || Off
|-
| || 1 || On

|- style="background-color: red;"
| 3 || || ''Unknown''

|- style="background-color: red;"
| 4 || || ''Unknown''

|- style="background-color: red;"
| 5 || || ''Unknown''

|-
| 6 || || '''Current loop mode'''
|-
| || 0 || 0-20mA mode
|-
| || 1 || 4-20mA mode

|- style="background-color: red;"
| 7 || || ''Unknown (always I)''

|-
| 8 || || '''Hold mode'''.
|-
| || 0 || Off
|-
| || 1 || On

|- style="background-color: red;"
| 9 || || ''Unknown''

|-
| 10 || || '''Beep frequency'''
|-
| || 0 || Off (no beeps)
|-
| || C || 300Hz
|-
| || F || 600Hz
|-
| || 1 || 1200Hz
|-
| || 2 || 2400Hz

|-
| 11 || || '''Auto power-off''' (APO)
|-
| || 0 || Off
|-
| || 1 || On

|-
| 12 || || '''LCD backlight'''
|-
| || 0 || Off
|-
| || 1 || On

|- style="background-color: red;"
| 13 || || ''Unknown (always L)''

|- style="background-color: red;"
| 14 || || ''Unknown''

|- style="background-color: red;"
| 15 || || ''Unknown''

|-
| 16 || || '''Rotary switch position'''
|-
| || 0 || Voltage
|-
| || 1 || Diode
|-
| || 2 || Resistance
|-
| || 3 || Capacitance
|-
| || 4 || uA
|-
| || 5 || mA
|-
| || 6 || A
|-
| || 7 || Temperature

|- style="background-color: red;"
| 17 || || ''Unknown''

|- style="background-color: red;"
| 18 || || ''Unknown (always 1)''

|- style="background-color: red;"
| 19 || || ''Unknown''

|-
| 20 || || '''Switch counter mode'''
|-
| || 0 || increase count on rising flank (initially low)
|-
| || 1 || increase count on falling flank (initially high)

|-
| 21 || || '''Auto range'''
|-
| || 0 || Off
|-
| || 1 || On

|}

==== U124xC models ====
{| border="0" width="95%" style="font-size: smaller" class="alternategrey sortable sigroktable"
|-
! style="width: 3em;" | Byte
! style="width: 3em;" | Value
! Meaning

|-
| 1
|
| '''Max/min/avg/maxminavg mode'''
|-
| || 0 || Off
|-
| || 1 || On

|-
| 2
|
| '''Relative measurement'''. The last value returned from FETC? before this mode was enabled denotes the stored reference value.
|-
| || 0 || Off
|-
| || 1 || On

|-
| 3
|
| '''Flashlight'''
|-
| || 0 || Off
|-
| || 1 || On

|-
| 4
|
| '''Probe socket connexion alert'''
|-
| || 0 || Off
|-
| || 1 || On

|- style="background-color: red;"
| 5
|
|''Unknown''

|- style="background-color: red;"
| 6
|
|''Unknown''

|-
| 7
|
| '''Smooth mode'''
|-
| || 0 || Off
|-
| || 1 || On

|-
| 8
|
| '''Trigger Hold'''
|-
| || 0 || Off
|-
| || 1 || On

|-
| 9
|
| '''0°C Temperature compensation'''
|-
| || 0 || Off
|-
| || 1 || On

|-
| 10 || || '''Beep frequency'''
|-
| || 0 || Off (no beeps)
|-
| || 1 || 3200 Hz
|-
| || 2 || 3268 Hz
|-
| || 3 || 3339 Hz
|-
| || 4 || 3413 Hz
|-
| || 5 || 3491 Hz
|-
| || 6 || 4572 Hz
|-
| || 7 || 3657 Hz
|-
| || 8 || 3746 Hz
|-
| || 9 || 3840 Hz
|-
| || A || 3938 Hz
|-
| || B || 4042 Hz
|-
| || C || 4151 Hz
|-
| || D || 4267 Hz

|-
| 11
|
| '''Auto power-off status'''
|-
| || 0 || Off
|-
| || 1 || On

|-
| 12
|
| '''Auto Hold'''
|-
| || 0 || Off
|-
| || 1 || On

|-
| 13
|
| '''Meter mode'''
|-
| || L || Normal
|-
| || C || Calibration

|- style="background-color: red;"
| 14
|
|''Unknown''

|-
| 15
|
| ''Reserved''

|-
| 16
|
| '''Rotary switch position'''
|-
|
| 0
| Zlow Voltage AC / DC (V)
|-
|
| 1
| Voltage AC (V) / H%
|-
|
| 2
| Voltage DC (V)
|-
|
| 3
| Resistance / continuity
|-
|
| 4
| Diode / capacitance
|-
|
| 5
| Current DC / AC (µA/mA)
|-
|
| 6
| Current DC / AC (A)
|-
|
| 7
| Temperature

|-
| 17
|
| '''Battery type'''
|-
| || 0 || Primary
|-
| || 1 || Secondary (rechargeable)

|-
| 18
|
| '''Battery low or Current percent'''
|-
| || 0 || Off
|-
| || 1 || Battery low or 4-20 mA mode
|-
| || 2 || 0-20 mA mode and not Battery low

|- style="background-color: red;"
| 19
|
|''Unknown''

|- style="background-color: red;"
| 20
|
|''Unknown''

|-
| 21
|
| '''DC filter (LPF)'''
|-
| || 0 || Off
|-
| || 1 || On

|}

==== U125xx models ====
{| border="0" width="95%" style="font-size: smaller" class="alternategrey sortable sigroktable"
|-
! style="width: 3em;" | Byte
! style="width: 3em;" | Value
! Meaning

|-
| 1
|
| '''Max/min/avg mode'''
|-
| || 0 || Off
|-
| || 1 || On

|-
| 2
|
| '''Relative measurement'''. The last value returned from FETC? before this mode was enabled denotes the stored reference value.
|-
| || 0 || Off
|-
| || 1 || On

|-
| 3
|
| '''dB mode'''
|-
| || 0 || Off
|-
| || m || dBm
|-
| || V || dBV

|- style="background-color: red;"
| 4
|
| ''Unknown''

|-
| 5
|
| '''Peak hold mode'''
|-
| || 0 || Off
|-
| || 1 || On

|-
| 6
|
| '''Current percent'''
|-
| || 0 || 0-20mA
|-
| || 1 || 4-20mA

|- style="background-color: red;"
| 7
|
| ''Triggerhold I/B ?''

|-
| 8
|
| '''Triggered hold mode'''.
|-
| || 0 || Off
|-
| || 1 || On

|- style="background-color: red;"
| 9
|
| ''Zero temperature compensation?''

|- style="background-color: red;"
| 10
|
| ''Beep selection ?''

|-
| 11
|
| '''Auto power-off''' (APO)
|-
| || 0 || Off
|-
| || 1 || On

|-
| 12
|
| '''LCD backlight'''
|-
| || 0 || Off
|-
| || 1 || On

|- style="background-color: red;"
| 13
|
| ''Unknown (always L)''

|- style="background-color: red;"
| 14
|
| ''Unknown (always 0)''

|- style="background-color: red;"
| 15
|
| ''Unknown''

|- style="background-color: red;"
| 16
|
| ''Rotary position ?''

|- style="background-color: red;"
| 17
|
| ''Output status active/standby ?''

|- style="background-color: red;"
| 18
|
| ''Unknown''

|-
| 19
|
| '''Battery low indicator'''
|-
| || 0 || Battery OK
|-
| || 1 || Battery low

|-
| 20
|
| '''Frequency counter prescaler'''
|-
| || 0 || No prescaling
|-
| || 1 || Divide by 100

|-
| 21
|
| '''Auto range'''
|-
| || 0 || Manual range
|-
| || 1 || Auto range

|}

==== U127xx models ====
{| border="0" width="95%" style="font-size: smaller" class="alternategrey sortable sigroktable"
|-
! style="width: 3em;" | Byte
! style="width: 3em;" | Value
! Meaning

|-
| 1
|
| '''Max/min/avg/maxminavg mode'''
|-
| || 0 || Off
|-
| || 1 || On

|-
| 2
|
| '''Relative measurement'''. The last value returned from FETC? before this mode was enabled denotes the stored reference value.
|-
| || 0 || Off
|-
| || 1 || On

|- style="background-color: red;"
| 3
|
| ''Unknown''

|- style="background-color: red;"
| 4
|
| ''Unknown''

|- style="background-color: red;"
| 5
|
| ''Unknown''

|- style="background-color: red;"
| 6
|
| ''Unknown''

|- style="background-color: red;"
| 7
|
| ''Unknown''

|- style="background-color: red;"
| 8
|
| ''Unknown''

|- style="background-color: red;"
| 9
|
| ''Unknown''

|-
| 10 || || '''Beep frequency'''
|-
| || 0 || Off (no beeps)
|-
| || 1 || 3200Hz
|-
| || 2 || 3491Hz
|-
| || 3 || 3840Hz
|-
| || 4 || 4267Hz

|- style="background-color: red;"
| 11
|
| ''Unknown''

|- style="background-color: red;"
| 12
|
| ''Unknown''

|- style="background-color: red;"
| 13
|
| ''Unknown (always L)''

|- style="background-color: red;"
| 14
|
| ''Unknown''

|- style="background-color: red;"
| 15
|
| ''Unknown''

|-
| 16
|
| '''Rotary switch position'''
|-
|
| 0
| Zlow, V AC/DC
|-
|
| 1
| ''N/A (this is the "OFF" position)''
|-
|
| 2
| Voltage AC (V) / LPF
|-
|
| 3
| Voltage AC (mV) / LPF
|-
|
| 4
| Voltage DC / AC (V)
|-
|
| 5
| Voltage DC / AC (mV)
|-
|
| 6
| Resistance / "smart resistance" / continuity
|-
|
| 7
| Diode / Auto
|-
|
| 8
| Capacitance / temperature
|-
|
| 9
| Current DC / AC (mA/A)
|-
|
| A
| Current DC / AC (µA) '''Note:''' This is "A" in the "STAT?" reply, but "*10" in the event notifiers (see below).

|-
| 17
|
| '''Continuity mode'''. When enabled, the value returned from FETC? is either NAN (no continuity) or any real value to denote continuity.
|-
| || 0 || Off
|-
| || 1 || On

|-
| 18
|
| '''Smart Ohm mode''' ("O'Comp" icon active on the display).
|-
| || 0 || Off
|-
| || 1 || On

|- style="background-color: red;"
| 19
|
| ''Unknown''

|-
| 20
|
| '''LPF'''
|-
| || 0 || Off
|-
| || 1 || On

|-
| 21
|
| '''DC filter'''
|-
| || 0 || Off
|-
| || 1 || On

|}

==== U128xx models ====
{| border="0" width="95%" style="font-size: smaller" class="alternategrey sortable sigroktable"
|-
! style="width: 3em;" | Byte
! style="width: 3em;" | Value
! Meaning

|-
| 1
|
| '''Max/min/avg/maxminavg mode'''
|-
| || 0 || Off
|-
| || 1 || On

|-
| 2
|
| '''Relative measurement'''. The last value returned from FETC? before this mode was enabled denotes the stored reference value.
|-
| || 0 || Off
|-
| || 1 || On

|-
| 3
|
| '''dB function'''
|-
| || 0 || Off
|-
| || M || dBm
|-
| || V || dBV

|-
| 4
|
| '''Probe socket connexion alert'''
|-
| || 0 || Off
|-
| || 1 || On

|-
| 5
|
| '''Peak-hold'''
|-
| || 0 || Off
|-
| || 1 || On

|-
| 6
|
| '''Current percent'''
|-
| || 0 || Off
|-
| || 1 || 4-20 mA
|-
| || 2 || 0-20 mA

|-
| 7
|
| '''Pulse width and duty cycle trigger level'''
|-
| || 0 || Negative
|-
| || 1 || Positive

|-
| 8
|
| '''Trigger Hold'''
|-
| || 0 || Off
|-
| || 1 || On

|-
| 9
|
| '''0°C Temperature compensation'''
|-
| || 0 || Off
|-
| || 1 || On

|-
| 10 || || '''Beep frequency'''
|-
| || 0 || Off (no beeps)
|-
| || 1 || 3200 Hz
|-
| || 2 || 3268 Hz
|-
| || 3 || 3339 Hz
|-
| || 4 || 3413 Hz
|-
| || 5 || 3491 Hz
|-
| || 6 || 4572 Hz
|-
| || 7 || 3657 Hz
|-
| || 8 || 3746 Hz
|-
| || 9 || 3840 Hz
|-
| || A || 3938 Hz
|-
| || B || 4042 Hz
|-
| || C || 4151 Hz
|-
| || D || 4267 Hz

|-
| 11
|
| '''Auto power-off status'''
|-
| || 0 || Off
|-
| || 1 || On

|-
| 12
|
| '''Auto Hold'''
|-
| || 0 || Off
|-
| || 1 || On

|-
| 13
|
| '''Meter mode'''
|-
| || L || Normal
|-
| || C || Calibration

|-
| 14
|
| '''Voltage alert'''
|-
| || 0 || Off
|-
| || 1 || On

|-
| 15
|
| ''Reserved''

|-
| 16
|
| '''Rotary switch position'''
|-
|
| 0
| Voltage AC (V) / LPF
|-
|
| 1
| Voltage AC (mV) / LPF
|-
|
| 2
| Voltage DC / AC (V)
|-
|
| 3
| Voltage DC / AC (mV)
|-
|
| 4
| Resistance / continuity / conductance
|-
|
| 5
| Diode / frequency counter
|-
|
| 6
| Capacitance / temperature
|-
|
| 7
| Current DC / AC (µA/mA)
|-
|
| 8
| Current DC / AC (A)
|-
|
| 9
| Square wave output

|-
| 17
|
| '''Battery type'''
|-
| || 0 || Primary
|-
| || 1 || Secondary (rechargeable)

|-
| 18
|
| '''Battery low'''
|-
| || 0 || Off
|-
| || 1 || On

|-
| 19
|
| '''Resolution'''
|-
| || 0 || 5 digits
|-
| || 1 || 4 digits

|-
| 20
|
| '''LPF'''
|-
| || 0 || Off
|-
| || 1 || On

|-
| 21
|
| '''DC filter'''
|-
| || 0 || Off
|-
| || 1 || On

|}

=== LOG: ===

Different commands can be used to retrieve the content of the different log memories from the multimeter. Those commands allow to retrieve log entries one by one, specifying the index of the entry to retrieve each time. When the index is greater than the index of the last logged value, the multimeter will return an error (<code>*E</code>). The actual commands depends on the model.

The response is presented as a quoted string whose length depends on the model.

Note that each log entry is also emitted by the multimeter whenever a new value is captured to the log.

==== U123xx models ====

The valid commands to retrieve log entries are yet to be determined.

Log entries are 15 characters long. Here is an example of log entry:
"050000210000200"

Note that the position of the decimal point is not explicitly given, it must be discerned from the range.

{| border="0" width="95%" style="font-size: smaller" class="alternategrey sortable sigroktable"
|-
! style="width: 3em;" | Byte
! style="width: 3em;" | Value
! Meaning

|- style="background-color: red;"
| 1 || || ''Unknown (always 0)''

|-
| 2 || || '''Function'''
|-
||| 0 || AUX
|-
||| 1 || Voltage
|-
||| 2 || Microcurrent
|-
||| 4 || Current
|-
||| 5 || Resistance or continuity
|-
||| 6 || Diode
|-
||| 8 || Capacitance
|-
||| 9 || Frequency

|- style="background-color: red;"
| 3 || || ''Unknown (always 0)''

|-
| 4 || || '''First (most significant) digit of measurement'''

|-
| 5 || || '''Second digit of measurement'''

|-
| 6 || || '''Third digit of measurement'''

|-
| 7 || || '''Fourth (least significant) digit of measurement'''

|-
| 8 || || '''Mode bits''' (several can be set at once)
|-
||| 1 || Autoranging is enabled
|-
||| 2 || Value is negative

|-
| 9 || || '''Mode bits''' (several can be set at once)
|-
||| 1 || DC
|-
||| 2 || AC
|-
||| 4 || Overload

|-
| 10 || || '''Range''', values are the same as with <code>CONF?</code>

|- style="background-color: red;"
| 11 || || ''Unknown (always 0)''

|-
| 12 || || '''Temperature unit (probably)'''
|-
||| 0 || not in temperature mode
|- style="background-color: red;"
||| 1 || degrees Fahrenheit (not confirmed, need to check)
|-
||| 2 || degrees Celsius

|-
| 13 || || '''Mode bits''' (several can be set at once)
|-
||| 1 || Relative mode is enabled
|-
||| 2 || Trig Hold-Log mode is enabled
|-
||| 4 || Auto Hold-Log mode is enabled

|-
| 14 || || '''Capacitance/AUX mode'''
|-
||| 0 || Capacitance
|-
||| 1 || AUX temperature (mV setting in menu is off)
|-
||| 2 || AUX mV (mV setting in menu is on)

|- style="background-color: red;"
| 15 || || ''Unknown (always 0)''

|}

==== U124xC models ====

The valid commands to retrieve log entries are:
LOG:HAND <index>
LOG:TRIG <index>
LOG:AUTO <index>
LOG:EXPO <index>

Log entries are 14 characters long. Here is an example of log entry:
"01000241100100"

Note that the position of the decimal point is not explicitly given, it must be discerned from the active function and exponent.

{| border="0" width="95%" style="font-size: smaller" class="alternategrey sortable sigroktable"
|-
! style="width: 3em;" | Byte
! style="width: 3em;" | Value
! Meaning

|-
|1-2|| || '''Function'''
|-
||| 0 || Millivoltage
|-
||| 1 || Voltage (averaging sense if Alternative unit flag and AC mode)
|-
||| 2 || Microcurrent (averaging sense if Alternative unit flag and AC mode)
|-
||| 3 || Current (averaging sense if Alternative unit flag and AC mode)
|-
||| 4 || Resistance (Continuity if Alternative unit flag)
|-
||| 5 || Diode
|-
||| 6 || Temperature in °C (or °F if Alternative unit flag)
|-
||| 7 || Capacitance
|-
||| 8 || Frequency
|-
||| 9 || Harmonic ratio
|-
|||10 || %Scale of 4-20 mA (or 0-20 mA if Alternative unit flag)

|-
| 3 || || '''First (most significant) digit of measurement'''

|-
| 4 || || '''Second digit of measurement'''

|-
| 5 || || '''Third digit of measurement'''

|-
| 6 || || '''Fourth digit of measurement'''

|-
| 7 || || '''Fifth (least significant) digit of measurement'''

|-
| 8 || || '''Mode bits''' (several can be set at once)
|-
||| 1 || Autoranging is enabled
|-
||| 2 || Value is negative

|-
| 9 || || '''Mode bits''' (several can be set at once)
|-
||| 1 || DC
|-
||| 2 || AC
|-
||| 4 || Overload

|-
| 10 || || '''Exponent'''

|-
| 11 || || '''Mode bits (several can be set at once)'''
|-
||| 1 || Alternate unit flag
|-
||| 2 || Thermocouple type (0 = K, 1 = J)
|-
||| 4 || Zero temperature compensation

|-
| 12 || || '''Hold mode'''
|-
||| 1 || Trig-Hold mode
|-
||| 3 || Auto-Hold mode
|-
||| 4 || Relative mode is enabled (can be combined with *-Hold mode)

|-
| 13 || || '''Mode bits''' (several can be set at once)
|-
||| 1 || Average
|-
||| 2 || Min
|-
||| 4 || Max

|-
| 14 || || '''Data logging option'''
|-
||| 0 || Manual Log (Hand)
|-
||| 1 || Interval Log (Auto)
|-
||| 2 || Event Log (Trig)
|-
||| 3 || Export Log (Hold button)

|}

Default exponent to be applied to the value for the different functions, in addition to the Exponent field.

{| border="0" width="95%" style="font-size: smaller" class="alternategrey sortable sigroktable"
|-
! style="width: 3em;" | Exponent
! Function

|-
| 10e-5 || Millivoltage
|-
| 10e-4 || Voltage
|-
| 10e-7 || Microcurrent
|-
| 10e-3 || Current
|-
| 10e-2 || Resistance / Continuity
|-
| 10e-3 || Diode
|-
| 10e-1 || Temperature (both °C and °F)
|-
| 10e-10|| Capacitance
|-
| 10e-2 || Frequency
|-
| 10e-2 || Harmonic ratio
|-
| 10e-2 || %Scale of 4-20 mA / 0-20 mA

|}

==== U125xx models ====

The valid commands to retrieve log entries are:
LOG? H<index>
LOG? A<index>
Note that <index> must be exactly 3 digits

Log entries are 13 characters long. Here is an example of log entry:
"0522041404000"

Note that the position of the decimal point is not explicitly given, it must be discerned from the active function and exponent.

{| border="0" width="95%" style="font-size: smaller" class="alternategrey sortable sigroktable"
|-
! style="width: 3em;" | Byte
! style="width: 3em;" | Value
! Meaning

|-
|1-2|| || '''Function'''
|-
||| 0 || Millivoltage
|-
||| 1 || Voltage
|- style="background-color: red;"
||| 2 || ''Unknown''
|-
||| 3 || Current
|- style="background-color: red;"
||| 4 || ''Unknown''
|-
||| 5 || Resistance (Continuity if Alternative unit flag ?, Conductance if Locked / Manual ranging)
|-
||| 6 || Diode
|-
||| 7 || Temperature in °C (or °F if Alternative unit flag)
|-
||| 8 || Capacitance
|-
||| 9 || Frequency
|-
|||10 || Duty cycle
|-
|||11 || Pulse width
|- style="background-color: red;"
|||12 || ''Unknown''
|-
|||13 || dBm (or dBV if Alternative unit flag)
|-
|||14 || %Scale of 4-20 mA (or 0-20 mA if Alternative unit flag)

|-
| 3 || || '''First (most significant) digit of measurement'''

|-
| 4 || || '''Second digit of measurement'''

|-
| 5 || || '''Third digit of measurement'''

|-
| 6 || || '''Fourth digit of measurement'''

|-
| 7 || || '''Fifth (least significant) digit of measurement'''

|-
| 8 || || '''Mode bits''' (several can be set at once)
|- style="background-color: red;"
||| 1 || Locked ? Manual ranging is enabled ?
|-
||| 2 || Value is negative

|-
| 9 || || '''Mode bits''' (several can be set at once)
|-
||| 1 || DC
|-
||| 2 || AC
|-
||| 4 || Overload

|-
| 10 || || '''Exponent'''

|-
| 11 || || '''Mode bits (several can be set at once)'''
|-
||| 1 || Alternate unit flag
|-
||| 2 || Thermocouple type (0 = K, 1 = J)
|- style="background-color: red;"
||| 4 || Environment temperature compensation ?

|-
| 12 || || '''Hold mode'''
|- style="background-color: red;"
||| 1 || Trig-Hold mode ?
|- style="background-color: red;"
||| 2 || Peak-Hold mode ?
|- style="background-color: red;"
||| 3 || Auto-hold mode ?
|-
||| 4 || Relative mode is enabled (can be combined with *-Hold mode)

|-
| 13 || || '''Mode bits''' (several can be set at once)
|-
||| 1 || Average
|-
||| 2 || Min
|-
||| 4 || Max
|- style="background-color: red;"
||| 8 || "press" ?

|}

Default exponent to be applied to the value for the different functions, in addition to the Exponent field.

{| border="0" width="95%" style="font-size: smaller" class="alternategrey sortable sigroktable"
|-
! style="width: 3em;" | Exponent
! Function

|-
| 10-7 || Millivoltage
|-
| 10-5 || Voltage
|-
| 10-7 || Current
|-
| 10-3 || Resistance / Continuity
|-
| 10-19|| Conductance
|-
| 10-5 || Diode
|-
| 10-2 || Temperature
|-
| 10-13|| Capacitance
|-
| 10-3 || Frequency
|-
| 10-5 || Duty cycle
|-
| 10-5 || Pulse width
|-
| 10-3 || dBm / dBV
|-
| 10-3 || %Scale of 4-20 mA / 0-20 mA

|}

==== U128xx models ====

The valid commands to retrieve log entries are:
LOG:HAND <index>
LOG:TRIG <index>
LOG:AUTO <index>
LOG:EXPO <index>

Log entries are 14 characters long. Here is an example of log entry:
"04235201470002"

Note that the position of the decimal point is not explicitly given, it must be discerned from the active function and exponent.

{| border="0" width="95%" style="font-size: smaller" class="alternategrey sortable sigroktable"
|-
! style="width: 3em;" | Byte
! style="width: 3em;" | Value
! Meaning

|-
|1-2|| || '''Function'''
|-
||| 0 || Millivoltage
|-
||| 1 || Voltage
|-
||| 2 || Microcurrent
|-
||| 3 || Current
|-
||| 4 || Resistance (Continuity if Alternative unit flag)
|-
||| 5 || Diode
|-
||| 6 || Temperature in °C (or °F if Alternative unit flag)
|-
||| 7 || Capacitance
|-
||| 8 || Frequency
|-
||| 9 || Duty cycle (positive pulse, or negative if Alternative unit flag)
|-
|||10 || Pulse width (positive pulse, or negative if Alternative unit flag)
|-
|||11 || dBm (or dBV if Alternative unit flag)
|-
|||12 || %Scale of 4-20 mA (or 0-20 mA if Alternative unit flag)
|-
|||13 || Conductance

|-
| 3 || || '''First (most significant) digit of measurement'''

|-
| 4 || || '''Second digit of measurement'''

|-
| 5 || || '''Third digit of measurement'''

|-
| 6 || || '''Fourth digit of measurement'''

|-
| 7 || || '''Fifth (least significant) digit of measurement'''

|-
| 8 || || '''Mode bits''' (several can be set at once)
|-
||| 1 || Autoranging is enabled
|-
||| 2 || Value is negative

|-
| 9 || || '''Mode bits''' (several can be set at once)
|-
||| 1 || DC
|-
||| 2 || AC
|-
||| 4 || Overload

|-
| 10 || || '''Exponent'''

|-
| 11 || || '''Mode bits (several can be set at once)'''
|-
||| 1 || Alternate unit flag
|-
||| 2 || Thermocouple type (0 = K, 1 = J)
|-
||| 4 || Zero temperature compensation

|-
| 12 || || '''Hold mode'''
|-
||| 1 || Trig-Hold mode
|-
||| 2 || Peak-Hold mode
|-
||| 3 || Auto-hold mode
|-
||| 4 || Relative mode is enabled (can be combined with *-Hold mode)

|-
| 13 || || '''Mode bits''' (several can be set at once)
|-
||| 1 || Average
|-
||| 2 || Min
|-
||| 4 || Max

|-
| 14 || || '''Data logging option'''
|-
||| 0 || Manual Log (Hand)
|-
||| 1 || Event Log (Trig)
|-
||| 2 || Interval Log (Auto)
|-
||| 3 || Export Log (Hold button)

|}

Default exponent to be applied to the value for the different functions, in addition to the Exponent field.

{| border="0" width="95%" style="font-size: smaller" class="alternategrey sortable sigroktable"
|-
! style="width: 3em;" | Exponent
! Function

|-
| 10-6 || Millivoltage
|-
| 10-4 || Voltage
|-
| 10-9 || Microcurrent
|-
| 10-4 || Current
|-
| 10-3 || Resistance / Continuity
|-
| 10-4 || Diode
|-
| 10-1 || Temperature °C
|-
| 10-2 || Temperature °F
|-
| 10-12|| Capacitance
|-
| 10-3 || Frequency
|-
| 10-3 || Duty cycle
|-
| 10-6 || Pulse width
|-
| 10-3 || dBm / dBV
|-
| 10-2 || %Scale of 4-20 mA / 0-20 mA
|-
| 10-11|| Conductance

|}

=== Event Notifiers ===
{| border="0" width="95%" style="font-size: smaller" class="alternategrey sortable sigroktable"
|-
! style="width: 3em;" | String
! Meaning

|-
| <code>*0</code> through <code>*7</code>
| Rotary switch position has changed. <code>*0</code> denotes the most counter-clockwise position (excluding the OFF position), then the value is increased by one for each step in the rotary switch's range. On the U127xx models the codes range from <code>*0</code> through <code>*10</code>.

|-
| <code>*B</code>
| Battery voltage dropped to "battery empty" level.

|-
| <code>*E</code>
| Invalid command.

|-
| <code>*I</code>
| Probes are connected to the wrong sockets for this mode, "Cerr" is shown on display (not supported on U123xx; it ''is'' supported on U124xC, U127xx and U128xx).

|-
| <code>*L</code>
| A button was pressed (not supported on U123xx, U124xC, U127xx and U128xx). This notifier is only sent once after a command, even if the user presses several buttons.
|}

== Resources ==
* [http://www.keysight.com/en/pc-1000004008%3Aepsg%3Apgr/handheld-digital-multimeter-clamp-and-calibrator-meters Series overview]
* [http://www.keysight.com/main/facet.jspx?c=181653.i.1&to=80029.k.0 Documentation]