PSI System Controls and Diagnostics
F3200E User Manual
F3200E_UM_180726 Page 63 of 107
13.2 Installing and Configuring IG2
The IG2 package is available to users of Pyramid products. A version supporting the F3200E
will be added in a forthcoming release. It is supplied as a zip file which should be de-
compressed and the entire folder moved to the computer that will act as the server. The server
and the user interface computer can be the same machine. The F3200E, the server and the user
interface computer should be able to communicate with each other over your network.
In the folders you have saved, there is an xml file that needs to be edited to customize your
particular setup. IG2 looks for the file system.xml in the \service subdirectory to establish the
configuration of the system. You can locate system.xml elsewhere than the default location, or
give it a different name, in which case you need to specify the name and path by means of an
argument in the command line that launches IG2. The system.xml file includes all the
information about your setup, including all the process variables that you want to expose, and
what you want to call them. Since the names must be unique, it is a good idea to include the
device name and the process variable description in the name.
The system file comprises a header section on the xml schema, which does not need to change.
Then comes a description of the user interface host computer, descriptions of the fiber optic loop
controller devices in your system and descriptions of the devices attached to loops. The F3200E
is a loop controller, because it has the capability to support multiple slave devices through its
fiber optic port. You don’t have to describe every device and every input/output point that is
present in your system, but only the ones that you expose in the system file will be visible to
EPICS. The following system.xml example corresponds to the CSS GUI shown in the previous
figure.
