Today is...
Monday, November 20, 2017
Welcome to Control.com, the global online
community of automation professionals.
Featured Video...
Featured Video
EtherCAT with CTC’s master lets your multivendor network play well together...
Our Advertisers
Help keep our servers running...
Patronize our advertisers!
Visit our Post Archive
Communication Between PLC and DCS
Student of Instrumentation eng. with final year project has a process loop control using DCS and PLC in master slave configuration.
By TanmayPatil on 19 October, 2017 - 12:10 pm

Hello,

I am student of Instrumentation engg. in V.C.E.T Vasai. My final year project is all about process loop control using DCS and PLC in master slave configuration.

As I said before my college is sponsored the DCS as well as PLC. We are using Honeywell HC900 (C30 CPU) as master and Siemens s7 200 (224 cpu) as slave with analog modules. As we are controlling level parameter of simple vessel we use modules for analog i/p (from level transmitter) & o/p (to I to P Converter). We are connecting pc (HNI) with DCS using MODBUS TCP/IP protocol via ethernet (straight) cable & DCS-PLC by RS232/485 cable. Both systems uses FBD. My question is all about is that possible to communicate between these two systems? If yes then How? Means what changes I should do in software setting while configuring for communication?

please give us your expert advise about this.

Thank you


I'm not quite sure what you are asking so I will just say this.
It's not normal to rely on intercommunications for part of a loop control or interlocks.

If the PLC is wired to the transmitters and the control valves it should also do the PID control. No part of the control loop should rely on the inter communications.

The DCS can be supervisory, send setpoints to the PLC and monitor the PLC. If, for example, someone were to chop the cable between DCS and PLC, the PLC should be capable of maintaining control and shutting down in a safe manner. PID setpoints should stay as before.

Having said that obviously if the DCS loses it's link to the PLC, the operator has no way of knowing what is happening in the PLC and you may want to shut down the process. In a case like that a Watchdog Timer is used to monitor the health of the communications.

Where there are interlocks required between the PLC and DCS, it's usual to hard wire discrete outputs of one system to discrete inputs of the other.

I'm sure others will comment on that.

I, too, am not quite sure why you would split loop control PID between an HC900 and a PLC, unless it is a purely academic exercise in Modbus. The HC-900 is technically a Process Automation Controller, a PAC; it is not a DCS.

If you are using the Honeywell brand "Control Station" as the HMI, then it talks a proprietary protocol over Ethernet, not Modbus. If you are using a 3rd party HMI, then the HMI is typically a Modbus/TCP client (master) and the HC-900 would be a Modbus/TCP server/slave.

There are restrictions on Modbus server/slave functionality that I can not recite off the top of my head, but it warrants your serious attention because that functionality, or lack of it, will determine whether the HC-900 or the PLC will be the Modbus Master/client or Server/slave.

The communications is fairly well documented in the HC-900 communications manual.
https://www.honeywellprocess.com/library/support/Public/Documents/51-52-25-111.pdf

There is a power point overview of the HC-900 Modbus functionality, in some respects a better overview than the manual:
http://tinyurl.com/m2j8eyq

The HC-900 has a fixed Modbus server/slave register map determined by the CPU, or a custom Modbus map where the custom is populated with only the registers desired.

A power point discussion of fixed vs custom map is here:
http://tinyurl.com/n3lv4se

Read Constant and Write Constant Function Blocks can be used to access or change values of elements internal to a Function block.

One drawback is the lack of a master/client Function Code 16, write multiple registers, particularly on the serial side.