GE WES5302-111 DCS Control System

GE WES5302-111 DCS Control System

The GE WES5302-111 has optimised its core to handle more complex communication tasks and analogue I/O functions. A range of specially designed CPUs, including dual redundant CPUs, are optimised for queuing fast events and handling the demanding functions of simultaneous flashing of a large number of alarm dashboards. Effective alarm and event management systems must be able to handle avalanche conditions without losing event or time tracking, so at the heart of the Maxilarm system is an advanced SOE module that scans I/O at 200 microsecond intervals (the fastest) SER function in the industry) while providing front-end event filtering and queuing, eliminating the possibility of the main processor becoming overloaded in avalanche conditions. It is a well-known fact that system software is difficult to qualify. Each Maxilarm node comes preconfigured with full alarm signaller functionality, including any 27 alarm sequences of your choice, in accordance with ISA-18.1, ISA SP18.02 and EEMUA 191. By incorporating proven, full-featured alarm signallers, no software programming is required to configure the Maxilarm alarm and event functionality, thus improving the Maxilarm systems can be connected to a monitoring computer via Ethernet, but Omniflex offers an alternative to Conet industrial networks where dedicated network cabling is not possible or is too costly.

Omniflex offers a Conet industrial network alternative that allows users to seamlessly integrate additional high power digital and analogue I/O into the system. The user imports an EtherCAT I/O profile into the A3200 MotionPAC PLC module, making it available to all programmers. Users then use the MotionPAC mapping tool to connect EtherCAT I/O points to tags or variables. Connections are made by dragging and dropping EtherCAT I/O names onto tags or variables defined in MotionPAC, the operator interface, or any other module of the system.MotionPAC automatically manages the memory associated with EtherCAT I/O mapping. There is no need for the programmer to allocate memory addresses. While programmers are free to view memory allocations, they can also change or create them if desired.