Rohde & Schwarz 1065.6000.20, Operating Manual

Page: 404 / 438

FSE Instrument Interfaces
1065.6016.12 8.11 E-15
Instruments with MS DOS controller:
Visual Basic:
’RSIB.BAS’ (D:/runtime/RSIB)
C:
’RSIBC.H’ (D:/runtime/RSIB)
Winword:
’RSIBWB.BAS’(D:/runtime/RSIB)
Thus, the RSIB directory features a program ‘RSIBCNTR.EXE’ with SCPI commands which can be sent
to the instrument by the RSIB interface. This program can be used as a test for the function of the
interface. Transit-time module VBRUN3200.DLL in the path or the Windows directory are required.
The control is performed with Visual C++ or Visual Basic programs. The local link to the internal
controller is established with the name '@local'.If a remote controller is used, the instrument IP address
is to be indicated here.
Via VisualBasic: internal controller: ud = RSDLLibfind ("@local", ibsta, iberr, ibcntl)
remote controller: ud = RSDLLibfind ('82.1.1.200', ibsta, iberr, ibcntl)
The return to manual operation can be performed via the front panel (LOCAL key) or the RSIB interface.
Via RSIB: ...
ud = RSDLLibloc (ud, ibsta, iberr, ibcntl)
;
...
Unix Environment
In order to access the measuring equipment via the RSIB interface, copy the
librsib.so.X.Y
file to a
directory for which the control application has read rights.
X.Y
in the file name indicates the version
number of the library, for example
1.0
.
The
librsib.so.X.Y
library is created as a shared library. The applications using the library have
nothing to do with versions. They simply link the library with the
lrsib
option. The following instructions
have to be observed so that linking can be successfully performed and the library can be found during
the program run:
File link:
•
Use the operating system command In to create a file with the link name
librsib.so
and
pointing to
librsib.so.X.Y
in a directory for which the control application has read rights.
Example:
$ ln –s /usr/lib/librsib.so.1.0 /usr/lib/librsib.so
Linker options for creating applications:
•
-lrsib
: import library
•
-
Lxxx
: path information where the import library can be found. This is where the above file
link has been created. Example:
-L/usr/lib
.
Additional linker options for creating applications (only under Solaris):
•
-Rxxx
: path information where the library is searched for during the program run:
-R/usr/lib
.
Run-time environment:
•
Set environment variable
LD_RUN_PATH
to the directory in which the file link has been
created. This is necessary only if
librsib.so
cannot be found in the standard search path of
the operating system and the
-R
linker option (only Solaris) was not specified.
For C/C++ programming, the declarations of the library functions and the definition of error codes are
contained in:
C/C++:
'RSIB.H' (C:\R_S\Instr\RSIB)