4 System
4.2 I/O Config
To help achieve this cooperative instrument sharing, the following remote
commands are provided:
–
"Lock Remote I/O Request (Remote Query only)" on page 449
–
"Unlock Remote I/O Session (Remote Command only)" on page 450
–
"Remote I/O Session Lock Name (Remote Query only)" on page 450
–
"Remote I/O Session Lock Owner (Remote Query only)" on page 451
Example Procedure for Lock Usage
Step Action
1 Each session tries to obtain a lock by sending :SYSTem:LOCK:REQuest?
This query can be sent simultaneously from multiple sessions
2 Only one session will be granted. The granted session receives 1 in response to its query
3 The granted session actively controls the instrument
Meanwhile, other sessions must wait, and must periodically send
:SYSTem:LOCK:REQuest?, requesting the lock
4 When the active session finishes its task, it releases the lock by sending
:SYSTem:LOCK:RELease
5 Now the lock has become available, so when one of the waiting sessions sends
:SYSTem:LOCK:REQuest?, it receives 1 in response, granting the lock to that
session
By repeating steps 3, 4, and 5 above, multiple sessions can share the same
instrument in a cooperative fashion.
NOTE
A session can query its own unique session name by sending
:SYSTem:LOCK:NAME?. This session name is determined by the instrument.
A session also can query the name of the currently granted session by sending
:SYSTem:LOCK:OWNer?.
NOTE
Remote I/O interfaces are grouped in two types: single-session interface and
multi-session interface. Both types of interfaces can be used for cooperative
instrument sharing.
The recommended interface is LAN HiSLIP.
Interface Single-session Multi-Session
GPIB ü
USB-488 ü
448 IQ Analyzer Mode User's &Programmer's Reference