4 System
4.2 I/O Config
See the example below, where the invalid command :SENS:BOGUS is sent:
Normal response to :SYST:ERR? (using the Telnet window):
SCPI> SENS:BOGUS
SCPI> SYST:ERR?
-113,"Undefined header"
After turning on Verbose SCPI:
SCPI> SYST:BOGUS
SCPI> SYST:ERR?
-113,"Undefined header;SYST:BOGUS<Err>"
Remote Command
:SYSTem:ERRor:VERBose OFF | ON | 0 | 1
:SYSTem:ERRor:VERBose?
Example
:SYST:ERR:VERB ON
Preset Unaffected by Preset, but set to OFF by Restore Defaults >"Misc" on page 1798
State Saved No
Range
OFF|ON
4.2.2.6 Device Clear on Disconnect
When using HiSLIP (High Speed LAN Instrument Protocol), Telnet, or Sockets, a
communication session with the instrument is opened when you connect, and
closed when you disconnect. This differs from other connections such as GPIB, USB
and VXI-11 connections, which are never actually closed but stay open as long as
the instrument is running.
When a session is closed, a Device Clear function is generated, which affects the
entire instrument, not just the current connection. Thus, when using HiSLIP, Telnet,
or Sockets, unexpected Device Clears may occur, which can disrupt measurements
in ways that GPIB and VXI-11 “sessions” do not.
Device Clear on Disconnect enables these auto-generated Device Clears for Telnet,
Socket, and HiSLIP sessions. For backwards compatibility, they are not generated
unless you explicitly enable them.
There is no change in VXI-11, USB, or GPIB session behavior. These sessions do not
close when you disconnect, have never generated Device Clear events, and still do
not generate Device Clear events, regardless of the setting of this switch.
Remote
Command
:SYSTem:COMMunicate:LAN:SCPI:EOSession:DCLEar:ENABle 0 | 1 | ON | OFF
:SYSTem:COMMunicate:LAN:SCPI:EOSession:DCLEar:ENABle?
Example
:SYST:COMM:LAN:SCPI:EOS:DCLE:ENAB ON
Preset Unaffected by Preset, but set to OFF by Restore Defaults >"Misc" on page 1798
Short Range Comms & IoT Mode User's &Programmer's Reference 1754
To Next Page
Loading...
Need help?
General
