ConSys Computer Configurations at ISA
This document contains configuration and operational information for the ConSys computers at ISA. See the ConSys InstallNote for installation notes.
General:
Computer list by type:
- Servers
- ISAPDC - Primary domain server
- ISASQL - ConSys SQL database server
- KUPNU - backup server, ISA WWW server
- Front ends
- FEC01 - ASTRID electronics
- FEC02 - ASTRID center ring hall
- FEC03 - ELISA
- FEC04 - ASTRID beamlines
- FEC05 - ASTRID virtual devices, electronics
- FEC06 - EBIS
- Consoles
- CIWEL - Control room ConSys System Computer (system maintenance)
- COIRO - Control room
- WRAMSA - Control room (server)
- VODNIS - Control room (display and machine services)
- MIRRAT - Control room diagnostic computer
- JEPDYT - El. Repos Console
- NAHOF - Mobile (truck) Computer
- CIDSIR - EBIS Console
- GHIMOC - ELISA Console
- HEGHAW - Miyake Console
- POJEBO - UV1 workstation
ConSys Computer Account Groups:
- Administrators: Manages Domain and computer
setups, Required to install ConSys.
Members: System Administrators. - Power Operators: Manages ConSys Setups.
(presently not fully implemented)
Members: ASTRID and ELISA machine operators. - Operators: Required to run the ConSys
control system.
Members: General operator account, associated operators (users)
Start all servers.
Start front-ends. ASTRID: Remark that the ConSys kernel on FEC01 and FEC02 must be running before starting the service/booting FEC05.
Start Consoles: ASTRID: Remember to start default programs running on CIWEL.
Computer list by machine:
- ASTRID:
ISAPDC, ISASQL,
KUPNU, FEC01, FEC02
, FEC04, FEC05, CIWEL,
COIRO, WRAMSA, VODNIS,
NAHOF, CIDSIR, MIRRAT,
JEPDYT
ASTRID BeamLines: HEGHAW, POJEBO
- ELISA:
ISAPDC, ISASQL, KUPNU, FEC03, GHIMOC
Servers:
ISAPDC - Primary domain server
REMARK: ISAPDC is presently also SQL server for ConSys - notes for the coming ISASQL server therefore also apply to ISAPDC at present.
Tasks: Windows NT Domain server, ConSys configuration server, ConSys data file storage server, User file server, print server.
Reboot consequences: Can be rebooted without consequences for ConSys.
ISASQL - ConSys SQL database server
Tasks: SQL database server for ConSys, Windows NT domain backup.
Reboot consequences: If the server is rebooted or the SQL database server is stopped and restarted all current connections to the ConSys database is lost. The following programs need to be restarted on console PC's in order to reconnect to the SQL database:
Data logger (default running on CIWEL).
The ConSys kernel and all other ConSys applications not mentioned above automatically reconnect to the database whenever a broken connection is discovered. (Note however that the Console may give a warning of a database error - this can be ignored)
KUPNU - backup server, ISA WWW server
Task: Windows NT domain backup, File backup server, backup printer server. Backup data from users is stored on the share '\\KUPNU\Backup' equivalent to 'd:\Backup'. This directory is backed up by IFA backup service maintained by Kurt Marcussen and Poul Bang Petersen, see backup status. The server has a build in 8 tape DATA backup drive. The 'Seagate Backup Exec' service is set up to do system backup on the domain. The system backup includes major server directories (SQL backup, ConSys related configuration data, etc.).
Reboot consequences: In most cases: None. If user backup script is running it will fail. If the Seagate backup script is running it will be aborted. The next rerun of the backup job should be checked in the Backup Exec program, and if needed run manually after a restart.
When the ConSys kernel has real or virtual devices
defined, the computer on which it is running is called a front-end computer.
All front-end computers have the ConSys kernel running as a Windows NT service.
Before a front-end can be booted successfully the network must be up, the
domain server (ISAPDC) and the SQL server (ISASQL) must running. Dependent on
the nature and settings for the individual devices, all control and data values
will be reset to database default values, restored from hardware, or loaded
from file (stored in the last controlled shut-down of the ConSys kernel
service.). Virtual devices and client programs connected to the front-end from
other computers will reconnect to the front-end when the ConSys service is
started.
Remark: In general, rebooting a front-end should be
avoided. If the ConSys kernel service is hanging or in other ways is not
performing correctly, the best solution is to try stopping and restarting the
service from the Windows NT control panel. If the service can not be stopped
from the service manager, then try to kill the ConSysKernel.exe from the task
manager. (At present starting and stopping services requires administrator
privileges, but we expect to reduce this to ConSys Power Operator). Although
possible it is not recommended to use front-end computers for other purposes,
including running ConSys applications (work as consoles).
General boot requirements for front-ends: Network OK, Windows NT domain server running (ISAPDC), and SQL server running (ISASQL).
General devices, reboot and service restart consequences.
General for Devices which uses file storage:
Many of the devices (especially the virtual devices) store their settings on the closure of their kernel, which mean that their settings are restored at the next load of the kernel. However in a crash of the kernel this setup file is not stored, which mean that (sometimes very) old values can be restored. Beware of this when restarting a kernel that has crashed.
PCDoct/G64 Crates:
Reboot: Depending on the device configuration, G64 crate command values can be stored/reloaded by the device during device shutdown/reload. Presently all G64 crates has been set up to store and reload command data values from file. Be aware that rebooting in the case of a crash of the kernel the setup file is not stored, which mean that (sometimes very) old values can be restored. Try to restart the kernel service instead - if this is possible the control values are loaded from the DOCT hardware instead of the initialisation files. If the kernel has crashed and you don’t has access rights to start the service again, then start the consysloader as an application. When the ConSysloader is fully up and running, close it again. This will store a new set of initialisation files (check the file date and times in the ConSys executable directory.) When the initialisation files are correctly stored the front-end can be rebooted safely.
Stopping and restarting the ConSys kernel service: When the ConSys kernel service is started without rebooting the computer, all settings in PCDOCT/G64 crates are restored from the running hardware. This implies that the ConSys kernel service can be stopped and restarted without loosing the current control values. Remark: Also works, if the ConSys service is hanging, and has to be terminated from the task manager.
Task: Main ConSys front-end for ASTRID on the electronics platform. Services all G64's on the electronic platform, a few G64's elsewhere and radiation monitors through RS422.
Reboot consequences, stop/restart ConSys service consequences: See general notes for G64 crates.
FEC02 - ASTRID centre ring hall
Task: Main ConSys front-end for ASTRID in the centre ring hall. Services: all G64's in the centre ring hall, the undulator through a specialised virtual device for the undulator, and a TableConnect for undu-gap to undu-energy.
Reboot consequences: G64 crates: see general notes for G64. Undulator: None (expect for a reset of Backlash settings). TableConversion: See general note.
Stopping and restarting the ConSys kernel from the service manager: G64 crates: see general notes. Undulator:
Task: ConSys front-end for ELISA. Devices: G64 crates, Virtual devices: Faraday current calc., Separator mass calc.
Reboot consequences, stop/restart ConSys service consequences: Virtual devices: No consequences, G64: See general notes.
Task: Front-end for beamlines in the ASTRID ring hall. Devices: G64 Crates, SMC serial motor devices for the MIYAKE beamline, mass calculation for the Miyake separator.
Reboot consequences: SMC serial motors: check status after restart,G64 crates: see general notes.
Stopping and restarting the ConSys kernel from the service manager: SMC serial motors: check status after restart. G64 crates: see general notes.
FEC05 - ASTRID virtual devices, electronics
Task: Contains almost all virtual devices needed for ASTRID and GPIB devices on the electronics platform. Major devices: SMYRF GPIB (CRE31SMY), ASTRID storage device for user parameters, TableConnect device for automatic conversion between undulator gab and excitation frequency (KEV31CNV), Beam current calculation, Multiplexer automation, Mass calculation for ion separator, Faraday cup automation, FAF conversion device, and a series of MultiConnect devices.
Reboot consequences: Most devices uses file storage - See general note. Beam current: None (except of lack of data while kernel not running). Lifetime Calc.: Being Reset.
Stopping and restarting the ConSys kernel from the service manager: See Reboot consequences.
Task: Front-end computer in the separator room (i.e., ASTRID separator and EBIS) - all devices is G64.
Reboot consequences: G64 crates: see general notes.
Stopping and restarting the ConSys kernel from the service manager: G64 crates: see general notes.
All computers used for ConSys applications are called consoles. There is no other difference between a console and a front-end computer except the fact that the console computers do contain devices or virtual devices. Most console computers will have the ConSys kernel running as a service like the front-end computers. The service can be stopped and restarted without consequences on all console computers. On some consoles, like office PC's, the ConSys kernel is not installed to run as a service. On these computers the ConSys kernel must be launched by the ConSysLoader in order to access the control system.
WRAMSA - ASTRID Control Room Server (and Operator Console)
Task: Control room operator console and
front-end server.
Devices: SMYRF GPIB (KEV31SMY -
Vertical Electron Excitation), ASTRID StateDevice.
Reboot consequences: Most devices uses file storage - See general note.
Stopping and restarting the ConSys kernel from the service manager: See Reboot consequences.
Task: Control Room ConSys System Computer (for system maintenance)
Applications, General (alvays):
DataLogger: Log to database
'ConSysLog9808'. Use configuration file '\\ISAPDC\Users\Astrid\Setups\Data Logs\DefaultLog.cdl'.
CSWebWriter: Writes data to the WWW server.
CSMail: Mail services program
Applications, Electron operation:
DataLogger: Log to database
'ConSysLog9808'. Use configuration file '\\ISAPDC\Users\Astrid\Setups\Data
Logs\Default-ElLog.cdl'.
CSplot: WWW current display. Use configuration file '\\ISAPDC\Users\Astrid\Setups\CSPlot\WWW-Plots\beamplot-WWW.csp'.
Reboot consequences: Default running applications must be started when the machine is restarted otherwise will there be no datalogning and no WEB update.
Task: ASTRID Control Room Display Computer and (some) Machine Services
Applications, Ion operation:
None.
Applications, Electron operation:
RampControl: Injection control. Setup file:
'\\ISAPDC\Users\Astrid\Setups\Ramps\Electrons\NewElSequence.RMP'
RampControl: AutoDumpLowCurrent. Setup file:
'\\ISAPDC\Users\Astrid\Setups\Ramps\Electrons\AutoDumpLowCurrent.RMP'
RangeControl: Plunger Control - Setup-file:
'\\ISAPDC\Users\Astrid\Setups\AstGeneral\plunger.rctrl'
Reboot consequences: Default running applications must be started when the machine is restarted.
Task: ASTRID Control Room Diagnostic Computer and Operator Console
Reboot consequences: None
Task: ASTRID Control Room Console, Usually running the DAFLoader program
Reboot consequences: None
Task: ASTRID El. Repos Console
Reboot consequences: None
Task: Mobile (truck) Computer
Reboot consequences: None
Task: ASTRID Separator and EBIS Console
Reboot consequences: None
Task: ELISA Console
Reboot consequences: None
Task: Miyake Console
Reboot consequences: None
Add hardware installed:
GPIB, National instruments PCI-GPIB
1 + 8 serial ports:
Com1: Default adr., Default IRQ
Com2: Mouse
Com3: Base IO: 340 IRQ 12
Com4: Base IO: 348 IRQ 12
Com5: Base IO: 350 IRQ 12
Com6: Base IO: 358 IRQ 12
Com7: Base IO: 380 IRQ 9
Com8: Base IO: 388 IRQ 9
Com9: Base IO: 390 IRQ 9
Com10: Base IO: 398 IRQ 9
Task: UV1 workstation
Reboot consequences: None
- Local (i.e. at the computer)
- Login with sufficient privileges. (Administrator or (hopefully soon) Power Operator)
- From the Control Panel select Services
- Select the ConSys kernel and click start. (To stop the services just click stop)
- Remote (only possible at selected computers (System consoles))
- Login with sufficient privileges. (Administrator or (hopefully soon) Power Operator)
- From the Client-based Network Tools in the Start-menu select the Server Manager
- Select the desired computer and choose Services in the Computer-Menu
- Select the ConSys kernel and click Start (or Stop)
Last Modified 28 April 2020