Experion PKS Process Knowledge System
Thread Content
Experion high-performance server: The server is the core of the PKS system, and a redundant configuration is available to provide higher reliability. A pair of servers with identical configurations are used to support each other in a primary/secondary configuration. When the main server fails, the backup server automatically takes over as the main server, collects data from the controller or RTU (Remote Terminal Unit), and provides data services to the operation station. Under normal conditions, the primary server transmits all data processing information from the database to the secondary server via a redundant network, thereby ensuring synchronization between the primary and secondary servers. The core component of the Experion system server is the system’s real-time database (RTDB – Real Time Database). This real-time database resides in the server’s memory and stores process data, historical data, configuration data, user data, alarms and events, as well as the system status. The server saves the real-time database stored in memory to the hard drive, ensuring minimal data loss in the event of a power failure. Experion operator station: FLEX operator station (Station F): All the information that the operator sees at Station F comes from the server’s RTDB database. Advantages: Low price, flexible and convenient. Disadvantage: If the server fails, the F operation station will have no information and display a blank screen. Console operation station (Station C): It contains an RTDB database, but this database stores only process data; the process data comes from the controllers, while all other data originates from the servers. Advantage: Monitoring of process data can continue in the event of a server failure. Disadvantages: High price; the C station must be on the FTE network, making it unsuitable for long distances. Console Extension operation station (CE station): All information comes from the C station; one C station can be connected to 3 CE stations. C300 controller: Includes controller hardware, controller software CEE (Control Execution Environment), and FTE network interface. The five key functions of the C300: master communication, point-to-point communication, IOLINK1 IO communication, IOLINK2 IO communication, and a deterministic execution environment.
Has the original poster used Honey’s eServer? Do you have experience in this area?
FLEX operation station (F station): All the information that operators see at the F station comes from the server’s RTDB database. Advantages: Low price, flexible and convenient. Disadvantage: If the server fails, the F operation station will have no information and display a blank screen. Console operation station (Station C): It contains an RTDB database, but this database stores only process data; the process data comes from the controllers, while all other data originates from the servers. Advantage: Monitoring of process data can continue in the event of a server failure. Disadvantages: High price; the C station must be on the FTE network, making it unsuitable for long distances. Console Extension operation station (CE station): All information comes from the C station; one C station can be connected to 3 CE stations.
3# F123F456 – The one in use is Honeywell’s E SERVER.
Checkpoint files are used for saving and restoring control strategies. Generating a CheckPoint file can be done manually or automatically. Manually (Manual) generate a Checkpoint file: In the Monitoring window, select a controller, right-click the mouse, and choose Checkpoint. Select Save Checkpoint Manually. In the Save Checkpoint Manually window, add the controller for which a checkpoint is needed to the box, modify the checkpoint file name, and click SAVE to save it. Automatically generate Checkpoint files: In the Monitoring window, select a controller, right-click, and choose Checkpoint. Select Schedule Checkpoint Tasks, add the controllers that require checkpoints to the box, choose Automatic under Startup Type, and then define the date, time, and frequency at which checkpoints should be created.
Several backups in server configuration (1) CheckPoint backup method: Perform manual CheckPoint operations on all controllers on the main SERVER. And ensure that a message indicating successful checkpointing is shown in the Station’s Event. The backup path is: C:\Documents and Settings\All Users\Application Data\Honeywell\Experion PKS\ Checkpoint. (2) Backup of the ERDB database: For the ERDB database, open \"Administer the control strategy database\" in Configuration Studio to perform a backup of the ERDB database. The backup path is: C:\ProgramFiles\Honeywell\Experion PKS\Engineering Tools\System\ER \ps_erdb.mdf. (3) Method for backing up the EMDB database: Open \"Administer the system database\" in Configuration Studio to back up the EMDB database. Path: C:\ProgramFiles\Honeywell\Experion PKS\Engineering Tools\System\ER\epks_emdb.mdf. (4) Method for backing up Defalt and Factory in Station: Back up the Defalt and Factory files located in C:\ProgramFiles\Honeywell\Experion PKS\Client\Station. (5) Quick Builder program backup method: Copy the *.qdb files located in C:\ProgramFiles\Honeywell\Experion PKS\Server\data\qdb\. (6) Historical data backup Method: Regularly save and transfer the files backed up to C:\ProgramFiles\Honeywell\Experion PKS\Server\archive. (7) Event backup Method: Copy the files stored at the path C:\ProgramFiles\Honeywell\Experion PKS\Server\Data\evtarch\backup to create a backup. (8) Flowchart backup Method: Copy all files in the C:\ProgramFiles\Honeywell\Experion PKS\client\abstract folder. (9) For the GHOST files of the two servers and operation stations (each unit uses the same model; GHOST backups can be created for stations of the same type), a new GHOST backup needs to be created if significant changes are made.