Commands in DSR Application Subsystems
:SYSTem:CLIent Subsystem
84
Agilent 81250 Parallel Bit Error Ratio Tester, Programming Reference, March 2006
:SYSTem:CLIent Subsystem
Syntax
:<Handle>:SYSTem:CLIent
More than one client can simultaneously operate with the firmware
server (for example, GUI-client, GPIB-client, VEE-client, …).
To avoid conflicts, the commands in this subsystem control the
firmware access. These commands allow using a system (virtual
instrument) exclusively. There are two locking commands, which
differ in the reaction of the locked application:
• If a system is locked by a client using the LOCK command, any
access by another client returns an error code.
• If a system is locked by a client using the BLOCK command, any
access by another client will simply wait until the system is
unlocked, thus blocking the client. No error code is returned.
:<Handle>:SYSTem:CLIent[:HANDle]?
Syntax
:<Handle>:SYSTem:CLIent[:HANDle]?
Return Value
This query returns the name of the client that has currently locked the
server. An empty string is returned if the server is not locked.
Example
:_test:SYST:CLI?
might return for example:
_GPIB
:<Handle>:SYSTem:CLIent:LOCK
Syntax
:<Handle>:SYSTem:CLIent:LOCK
This command can be used to take over the control of the virtual
instrument explicitly.
If another client tries to access a locked virtual instrument, the error
code -19, “ANOTHER_CLIENT_USES_APPLICATION” is returned.
N O T E
A locked virtual instrument can be blocked by calling:
SYSTem:CLIent:BLOCk
.
Example
:_test:SYST:CLI:LOCK
Artisan Technology Group - Quality Instrumentation ... Guaranteed | (888) 88-SOURCE | www.artisantg.com