Keithley 4200A-SCS, Reference Manual

Page: 703 / 1381

Section 8: Keithley User Library Tool (KULT) Model 4200A-SCS Parameter Analyzer Reference Manual
8-58 4200A-901-01 Rev. C / February 2017
Compile, set dependencies for, and build the Level 0 user module and user library:
1. Compile the saved Test user module, which is in the
liba
user library.
2. Set the dependencies for the test user module:
a. Select Options > Library Dependencies .
b. Select liba1 from the Library Dependencies list box.
c. Click Apply .
3. Build the
liba
user library.
This reverse hierarchical build order results in a linking scheme that satisfies the dynamic linking
requirements of Microsoft
®
Windows
®
.
Understanding user-module locking
When a user module is first opened, KULT creates a temporary lock file in the directory
%KI_KULT_PATH%\< library_name >\lock
. This lock file prevents other users from saving the
user module while it is open, unless they rename it. Another user may still access and edit the user
module but cannot save the edited module without changing its name.
Edit locking
When a user tries to access a user module that is already open, a message box opens with the
message that another user has locked the module. For example, if two users attempt to access the
VSweep
user module in the
my_2nd_lib
user library (created in Tutorial 2: Creating a user module
that returns data arrays (on page 8-28)), the second user sees the message "This library cannot be
built because it is currently locked."
After the second user clicks OK , the user module opens normally. However, if the second user edits
the module while it is locked by the first user, the second user must save it under a new name, using
the KULT
File > Copy Module menu selection. The new name must be unique; it cannot be the
name as any other user module that is in the
%KI_KULT_PATH%
directory . Otherwise, KULT will not
allow the user module to be saved.
The lock file is named as follows:
%KI_KULT_PATH%\< library_name >\lock\< module_name >.lck
For example, when a user opens the
VSweep
user module in the
my_2nd_lib
user library, the
following lock file is created:
%KI_KULT_PATH%\my_2nd_lib\lock\VSweep.lck
An example of this lock file, which stores information textually, contains:
PID: 162
USER: kiadmin
HOST: S4200-P3
TIME: Tuesday, 10/27/2015, 17:28:40
LIB: my_2nd_lib
MOD: VSweep.c
FILE: C:\s4200\kiuser\usrlib\my_2nd_lib\lock\my_2nd_lib_VSweep.lck
KULT automatically deletes an edit lock file when the corresponding user module is closed.