【正文】
在這種情況下, OPC 更趨向于微軟的 DCOM 標(biāo)準(zhǔn)。 新的工業(yè)標(biāo)準(zhǔn),如 OPC,和 OPC 設(shè)施聯(lián)系,還和控制系統(tǒng)之間互相聯(lián)系。開放 API 或腳本支持有時有助于整合用戶的硬件。所有 SCADA 系 統(tǒng)在市場商業(yè)運(yùn)作中是可行的。編碼發(fā)電機(jī)可以產(chǎn)生 C 代碼。為復(fù)雜的啟動和關(guān)閉處理程序設(shè)立的頻率程序也可以運(yùn)行工作站。運(yùn)行時環(huán)境取決于相關(guān)代碼。對顯示和控件的屬性的支持是必不可少的。另外,這些嵌入式屬性修改是很難尋覓,因?yàn)槠渲猩婕皟蓚€或兩個以上軌道系統(tǒng)這可能是一個有力的論據(jù)是,為什么控制回路主要實(shí)施在 IOC 層面,而不是 PLC’ s 層 面。它的缺點(diǎn)就是復(fù)雜,難以達(dá)到控制屬性。 前端控制器: 對控制系統(tǒng)的核心要素之一,是前端控制器。但是,在極少數(shù)情況下,只通過商業(yè)的立場時難以回答的。 PLC’ s 和智能 I / O 子系統(tǒng)的差別正在消失。 智能 I / O: I / O 設(shè)備上的新發(fā)展允許在更小的群體中集群 I / O 并把這些集群 I / O渠道鏈接到控制系統(tǒng)。此外,定期執(zhí)行一個確定功能的基本特征也讓他們通過以太網(wǎng)通信,包括內(nèi)置的 HTTP 服務(wù)器和不同集合的通訊方案。后者大大降低了信息擁堵的情況 。靈活的命名方案,默認(rèn)的顯示和每個記錄的報(bào)警屬性緩和了運(yùn)作工具和 IOC 之間的連接。 作為一個 DCS 系統(tǒng)的 EPICS: 作為 SCADA 系統(tǒng)的基本組成部分, EPICS 還提供完整的輸入輸出控制器( IOC)。德國電子同步加速器研究所公用事業(yè)集團(tuán)已制定 了一套工具來創(chuàng)建 IOC數(shù)據(jù)庫和配置文件。所有這些都是基本的 SCADA功能。此外,如通道歸檔和圖形顯示( dm2k) 會 被使用。 作為一個 SCADA 系統(tǒng)的 EPICS: 該公共事業(yè)組(水,電,壓縮空氣,加熱和調(diào)溫)使用各種散布在整個德國電子同步加速器研究所網(wǎng)站上的 PLC。 EPICS 通過其完整的功能,運(yùn)用于沒有由 D / 3 系統(tǒng)控制的低溫冷藏系統(tǒng)。從成為低溫控制系統(tǒng)的數(shù)據(jù)收集器和數(shù)量控制器, EPICS 成為了德國電子同步加速器研究所公用事業(yè)集團(tuán)使用的核心系統(tǒng)。集成環(huán)境將努力克服這個限制。相比其他 SCADA系統(tǒng) PVSS 帶有一個基本特點(diǎn):它提供了 API 給設(shè)備的數(shù)據(jù)。它還提供附加的管理服務(wù),如:控制經(jīng)理,數(shù)據(jù)庫管理,用戶界面, API 經(jīng)理以及在建的 HTTP服務(wù)器。其核心元素叫做事件管理器。在 CERN 由聯(lián)合控制項(xiàng)目 [4]進(jìn)行的廣泛調(diào)查促使他們做出 使用 PVSS 作為代替品的決定。 SCADA( PVSS Ⅱ ): 在 HERA 加速器上的 H1 實(shí)驗(yàn)中,實(shí)驗(yàn)人員為升級他們的低速控制系統(tǒng),決定使用 PVSS Ⅱ。在 2021 年 3 月,此系統(tǒng)最后被付諸實(shí)踐。 最后,與 Orsi 公司的合同被取消了。所有的附加功能都必須添加進(jìn)去。第二個由現(xiàn)有 D / 3 系統(tǒng)復(fù)雜的功能造成的額外負(fù) 荷引起的。有兩個因素引起了這些問題。但是因?yàn)?HERA 試驗(yàn)原定時間是有限制的,所以技術(shù)問題和組織問題也迫使計(jì)劃提前。這包括 D / 3,以及德國電子同步加速器研究所的集成總線 SEDAC 和 VME 的溫度轉(zhuǎn)換器。由于急需給 Orsi 公司提供他們的產(chǎn)品, Cube 開始起作用了 [2]。而通信網(wǎng)絡(luò)的暢通與否取決于不存檔的數(shù)據(jù)總量,不取決于報(bào)警系統(tǒng)中配置的數(shù)據(jù)。在展示端和 I / O 端擴(kuò)展此系統(tǒng)的可能將有助于解決日益增加的 HERA 試驗(yàn)控制的要求。 德國電子同步加速器研究所對 過程管理系統(tǒng)的篩選 集散控制系統(tǒng)( D/ 3): 市場調(diào)查表明:來自 GSE 的 D / 3 系統(tǒng)被 HERA 低溫冷藏工廠選中。其操作系統(tǒng)是 VxWorks,而應(yīng)用程序是 EPICS。因?yàn)橐寻惭b的 D / 3 系統(tǒng) [1] 只提供了與多總線板串行連接,以實(shí)現(xiàn) DMA 與 VME 的連接并用其模擬多總線板的功能。此外,在實(shí)現(xiàn)對復(fù)雜的低溫 冷藏系統(tǒng)的開閉過程中,頻率項(xiàng)目顯得尤為重要。這項(xiàng)新技術(shù)是必需的,因?yàn)榈乾F(xiàn)有的硬件沒有能力來處理標(biāo)準(zhǔn)過程控制信號,如 4 至 20 毫安的電流輸入和輸出信號。本文介紹工業(yè)控制系統(tǒng), PlC controlled turn key系統(tǒng),和 CCS 工具,以及它們之間的操作。多年的操作經(jīng)驗(yàn)表明哪個解決方法是最主要的不重要,重要的是哪個可行。經(jīng)濟(jì)因素使決定趨向于協(xié)同工具。任何決定都有它的優(yōu)缺點(diǎn)。被應(yīng)用的控制系統(tǒng)的種類取決于技術(shù)要求。 configuration tools for the processing engine. The flexible naming scheme and the default display and alarm properties for each record ease the connection between the operator tools and the IOC?s. The flexible data acquisition supports the poll mode as well as the publish subscribe mode. The latter reduces the traffic drastically. PLC?s PLC?s provide nowadays the same rich functionality as it was known from stand alone control systems in the past. Besides the basic features like the periodic execution of a defined set of functions they also allow extensive munication over Ether including embedded servers and different sets of munication programs. Besides the munication processors, display processors can be linked to PLC?s to provide local displays which can be prised as touch panels for operator intervention and value settings. These kind of PLC?s are attractive for turn key systems which are missioned at the vendors site and later integrated into the customers control system. Intelligent I/O New developments in I/O devices allow to ?cluster? I/O in even smaller groups and connect theses clustered I/O channels directly to the control system. PLC?s are not any more necessary for distributed I/O. Simple munication processors for any kind of field buses or for Ether allow an easy integration into the existing controls infrastructure. Little local engines can run IEC 61131 programs. The differences between PLC?s and intelligent I/O subsystems fade away. FUNCTIONALITY The ever lasting question why control systems for accelerators and other highly specialized equipment are often home grown or at least developed in a collaboration but only in rare cases mercial shall not be answered here. We try to summarize here basic functionalities of different controls approaches. Frontend Controller One of the core elements of a control system is the frontend controller. PLC?s can be used to implement most of the functions to control the equipment. The disadvantage is the plicated access to the controls properties. For instance all of the properties of a control loop like the P, I and D parameter, but also the alarm limits and other additional properties must be addressed individually in order to identify them in the munication protocol and last not least in the display, alarm and archive programs. In addition any kind of modifications of these embedded properties is difficult to track because two or more systems are involved. This might be one strong argument why control loops are mainly implemented on the IOC level rather than PLC?s. 1 I/O and Control Loops Complex control algorithms and control loops are the domain of DCS alike control systems. The support for sets of predefined display and controls properties is essential. If not already available (like in DCS systems) such sets of generic properties are typically specified throughout a plete control system (see namespaces). 2 Sequence/ State programs Sequence programs can run on any processor in a control system. The runtime environment depends on the relevance of the code for the control system. Programs fulfilling watchdog functions have to run on the frontend processor directly. Sequence programs for plicated startup and shutdown procedures could be run on a workstation as well. The basic functionality of a state machine can be even implemented in IEC 61131. Code generators can produce ?C? code which can be piled for the runtime environment. 3 Supported Hardware The support for field buses and Ether based I/O is a basic functionality for SCADA type systems it is mercially available from any SCADA system on the market. The integration of specific hardware with specific drivers and data conversion is the hard part in a mercial environment. Open API?s or scripting support sometimes help to integrate custom hardware. If these tools are not provided for the control system it is dif