Configuring FOPI - Slow Control Version 3.1
In the following documents one can find a short (but hopefully complete) description what is necessary to configure for the FOPI Slow Control based on CS 2.10d4. Please refer to the Configuration Instruction in
FopiCsComputers first!
Where to start?
- CS Developer should refer to the CS 3.1 Documentation first.
- Next one should read the configuration instruction in FopiCsComputers and FopiDataLoggingSupervisoryControlModule as well as FopiCs210Configuration.
- Then you can come back here.
Installation and configuration of CS 3.1 for FOPI
The following list item refer to the CS 3.1 Documentation. FOPI details are added in subsequent sections.
- Getting Started - Basic Level
- Getting Started - Medium Level
- Getting Started - Advanced Level
- Getting Started - Profibus, OPC, ...
- ODBC Data Source
- Database and Tag Tools
- Linux
- Real-Time
- Archive DSC Files
DIM
DIM configuration details:
- DIM_DNS_NODE = kp1pc065.gsi.de
- PATH
- Windows:
E:\Program Files\dim\bin
- Linux: ?
- FOPI central control system server:
In principle DNS.exe has to be started. I put a symbolic link in the Autostart menu.
CS 3.0 Executables
- The production executable programms are installed in:
- PATH = F:\CS30_Applications\Production\bin
- CS30.exe;
- CSSQLServer.exe
- CSDBTools.exe
- DMSClient.exe
- DMSServer.exe
- DMSViewer.exe
- NodeMon.exe
- PATH = E:\Program Files\National Instruments\LabVIEW DSC Run-Time System 7.1
- CS_DSC_P3.exe: The DSC-DIM-Gateway is installed on the FOPI central control system server. This is the executable that contains Patch 3.
- Enter a unique text string in systemID in the startup dialog, if not corrreclty preconfigured.
Database & CSSQLServer
- The ODBC data source name is CS3DB_FOPI and refers to F:\CS30_Applications\Production\config\CS3DB_FOPI.mdb
- CSDBTools.exe can be used to edit the database entries
- The CSSQLServer should be started on the FOPI central control system server
DomainManagementSystem
- The CSDomainName for the FOPI control system is FOPI_CS.
- The DMSClient.exe should be started on all FOPI CS computer
- Commandline paramater: -- FOPI_CS kp1pc065
- I created a sympolic link with correct commandline parameter: DMSServer_FOPI in the Autostart
- The DMSServer.exe should be started on the FOPI CS central control system server
- Commandline paramater: -- FOPI_CS
- I created a sympolic link with correct commandline parameter: DMSServer_FOPI
DMSServer Configuration
The configuration for the DMSServer is stored in F:\CS30_Applications\Production\config\DMSServer_FOPI.XML
CS Systems
All PC names are volatile. Use the DMSViewer to get the correct node information. Following CS systems are designed to perform a specific task.
CentralServer
This system is designed to run on
KP1PC065. It is the central FOPI CS system. It can be used for monitoring and supervisory control. Its system name is now LV_RPCT_CAMAC.
DSCBackend
This system is designed to run on DEPC221 during upgrading to CS 3.0, later it will be moved to
KP1PC065. It is the gateway between DIM and the DSC SCADA backend for alarming and trending.
Current desired config: DSC-Dim_FOPI_20080229.xml. Please check the FOPI_CS Database for the real value!
DSC_DIM_Gateway
This system is designed to run on
KP1PC065. It is the gateway between DIM and OPC.
GasMixer
This system is designed to run on
KP1PC077. It is used for monitoring and control of the Brook0154 gas mixer which is connected to COM1.
Viasalla
This system is designed to run on
KP1PC087. It is used for monitoring the parameter (ppmV, T/°C, RH/%) measured with a
Viasala device which is connected to COM1.
CountingRoom
This system is designed to run on
KP1PC058. It can be used for monitoring and control.
CS_Dev058
This system is designed to run on
KP1PC085. It will be used for local development and bug fixing.
This system is designed to run on DENBG014. It will be used for monitoring only.
This system is designed to run on DEPC221. It will be used for development.
Where to go next?
Control the FOPI detector. Good Luck!
--
HolgerBrand - 02 Nov 2006