C200/C200E Controller Overview PDF

C200/C200E Controller Overview 28 February 2024 11:23 C200/C200E Now Let's know more about C200/C200E or process controller. You have already learnt that there are two basic types of controllers in Experion - the C200/C200E and SCADA. The C200/C200E is different than SCADA in which it is fully...

C200/C200E Controller Overview 28 February 2024 11:23 C200/C200E Now Let's know more about C200/C200E or process controller. You have already learnt that there are two basic types of controllers in Experion - the C200/C200E and SCADA. The C200/C200E is different than SCADA in which it is fully integrated with the Experion Server. Now Experion has to be configured with the C200/C200E controller, and whenever download is needed we can download the controller configuration along with the Server database. It is a redundant-capable controller which is an optional feature. However, If you use redundancy there are two separate chassis so there is no single point of failure. You can also go with another option of a single chassis and a redundant power supply. The power supply is the component on the left. Instead of connecting the power supply there is an assembly that you can set, and it connects up to two separate power supplies. You have redundant networks, both in ControlNet and Fault Tolerant Ethernet. It has on-process migration as an option; which requires a redundant controller. Finally there is one control execution set in the C200/C200E. It is very flexible. It can have regulatory control, which includes logic and device control — it doesn't use ladder logic but uses function blocks —and it can have sequence control, which is batch type control. In addition, you can choose to execute as fast as 5ms. It has a 64 Input Output unit capacity. As long as you stay within the 64 Input Output unit limit, you can mix and match Input Output families into the same controller. We had a partner in the development of the C200/C200E - it was Allen Bradley we have the capability to do peer-to-peer with Allen Bradley devices and other ControlNet devices. C200/C200E and ACE Network Connections The C200/C200E controller communicates with the Experion Server and the Experion ACE node over two different types of networks. The Control Net, also referred to as CNet and the Fault Tolerant Ethernet, also referred to as FTE. EPKS L1 P2 Page 1 C200/C200E I/O Options Here we will discuss different Input Output options available with C200/C200E Controller. Here is a diagram that shows all the different devices. Let's talk about each one. We start off using ControlNet. Now let's discuss about the network for Input Output, not the supervisory network. So one of the devices that we have for Input Output is to use ControlNet and if we do that we are using Allen Bradley Input Output modules. Allen Bradley makes two series of rail Input Output - Series A and Series H. Series H is for hazardous environments. It's galvanically isolated. Either of them is available. Allen Bradley also makes a chassis Input Output series that fits in the same footprint as the C200/C200E. It also connects up using ControlNet. None of these options (Series A) is redundant. If you need redundant Input Output, we have an device that we have been using for many years in Honeywell with our other controllers, the PM device, and this same device of Input Output is now available for the C200/C200E. It uses an 10 link interface module and connects up to the PMIO. All the PMIO modules except DI, D016, LLAI, LLMUX, RHMUX can be redundant. We have the ability to configure Foundation Fieldbus devices. We have a Fieldbus Interface Module, or F I M, that connects up to a termination panel. The termination panel can have two Fieldbus links. Each link can have up to 16 devices. We can have several F I M's in one C200/C200E controller. Another type of device that we have connections to is a Hart device. A Hart device is similar to Fieldbus in which it supplies additional information besides the process signal. It differs from Fieldbus in which it uses a 4-20 ma signal and superimposes the additional information as a digital signal when you are using Hart. And we have chassis Input Output for Hart as well as PMIO which can be redundant. The Server has the ability to read the digital additional signals directly. You can use Profibus modules - in which you have Profibus interface module. There is also a DeviceNet interface module. All of these different devices come together into the C200/C200E as long as we stay within the 64 Input Output unit limit, we can mix and match these different devices into the same controller. EPKS L1 P2 Page 2 Experion Simulation Control Environment Experion PKS has the ability to simulate a C200E controller. It supports SCM and CM devices — those are the same type of devices and algorithms that we would use in a standard C200/C200E, which runs the C200/C200E functionality in a Windows machine. A Windows machine can have up to four C200E controllers. So you can simulate up to four C200E controllers in one box. We can simulate process Input Output either by doing a simplified tie-back model (tail-to-mouth) or can do more complex simulation. If you decide to take the controller implementation, we actually make use of the simulation with which we can become more advanced in control scheme using the simulation than we can just use hard-wired tail-to-mouth. We use a hard-wired tail-to-mouth. We use a spreadsheet that takes the data from the simulated controller, which does some calculations and sends the result back, and it looks like a process. So process Input Output can be complex. We use Control Builder — now we're going to open up Control Builder through Configuration Studio. Control Builder is the tool that we use for C200/C200E configuration and it also can be used for the simulation. However, when we are working in Control Builder, it is identical to setup and configure a controller. We can re-use the existing configuration and also move the configuration from the simulation into a real controller. Simulation of C200 Controller is not supported. Note that Simulation Control Environment is separately licensed and should be installed on a separate node — not a server, station, etc. EPKS L1 P2 Page 3 ACE Application Control Environment (ACE) is a Windows machine that connects up to the FTE. It is used for advance control and also for optimization. The software that the ACE executes is the same Control Execution Environment that runs on the C200/C200E,C300 and UOC/vUOC. If we know how to program a C200/C200E,C300 or UOC/vUOC, it's easy to program an ACE. Now the ACE does have some extra capability. It can have peer to peer communication with C200/C200E, C300, UOC/vUOC and their simulation except SIM-C200. It also has peer-to-peer connections with the FIM, the Fieldbus Interface Module. It has a connection to TPS so that we can do optimization in the ACE and write down to a controller on the L C N, and it has peer-to-peer with third party OPC Servers so we can use OPC data directly in the control scheme. The Custom Algorithm Block is the function block which can be used to write the customized control programs. It can be used on an ACE node. EPKS L1 P2 Page 4 SIM-ACE The SIM ACE is a simulated ACE node. It has a very specific purpose. It supports strategy checkout prior to going on-process. It has the ability to read from the system, all the different peer-to- peer options are available in the SIM ACE, but it does not have the ability to write. And it is used to debug VB.N ET CAB applications. It is highly recommended to checkout CAB strategies before going on-line with them, and the SIM ACE is used to do that. ` EPKS L1 P2 Page 5