Fully Integrated Modbus Communication Functions on STARDOM PLC/RTU

下载 (1.3 MB)

Introduction

With its open and simple specifications, the Modbus protocol is widely used to control device communications in industrial applications. As indicated in the following table, Modbus modes and functions differ depending on cable type.

Cable type Serial Ethernet
Mode ASCII RTU TCP
Functions Master/slave Master/slave Client/server

Project Overview

Yokogawa Engineering Asia Pte. Ltd. was engaged in an upstream supervisory control and data acquisition (SCADA) system project where there was a requirement for Modbus systems that could operate simultaneously as master and slave nodes. As STARDOM field control node (FCN) autonomous controllers allow both Modbus master and slave functions to run simultaneously, they were selected for this project.

While functioning as a Modbus master mode in this application, the FCN polls the fire and gas system (FGS) to obtain data. As a Modbus slave node, it then transmits FGS data to the Yokogawa FAST/TOOLS SCADA system via a Modbus gateway and a WAN. This gateway converts the Modbus RTU protocol to Modbus TCP protocol for communication over the WAN. The serial modules are duplexed for network redundancy.

System Configuration

Figure: System Configuration

Expected benefits

Port name definition in Resource Configurator

Figure: Port name definition in Resource Configurator

The NFLR121 FCN serial communications module has two ports for either RS-422 or RS-485 communications, and each can be configured as slave or master. By installing two of these modules, the second module is made to be a backup.

With STARDOM, the following benefits are expected:

  • Reduced installation costs
  • Simplified system configuration
  • Increased system reliability

STARDOM Engineering

Setting of virtual name for port in POU
Figure: Setting of virtual name for port in POU

STARDOM supports the IEC61131-3 programming language. The following two engineering tools are available:

  • Resource Configurator: for hardware settings
  • Logic Designer: for application logic

By keeping the application logic separate from the physical addresses, engineers can write programs for specific applications without having to consider the hardware configuration. This allows programs to be reused and improves engineering efficiency. The following screenshot from the Resource Configurator tool shows how the virtual name for a physical port is defined. In this case, SERIAL 1 is set for port1 and SERIAL 2 is set for port2 of the NFLR121 module.

By setting a virtual name for the program organization unit (POU) parameter, it is possible to link the physical hardware and the application logic. In the following figure, SERIAL 1 is set for SD_CMDBSM_BM_OPEN, which executes a Modbus master task. This specifies that port1 on an NFLR121 module is used as the communications port.

Application Overview

The NFLR121 FCN serial communications module has two ports for either RS-422 or RS-485 communications that support communication speeds between 300 bps and 115.2 kbps. In this project, one port was set as a Modbus master and the other as a Modbus slave. For redundancy purposes, two modules are installed in the following side-by-side configuration:

PSU Power Supply Unit PSU Power Supply Unit CPU CPU Spare AI DI DO COM COM

Figure: Unit Configuration

NFLR121

NFLR121

For this application, the following tasks were carried out in the sequence shown:

  1. Port configuration
  2. Modbus RTU master and slave programming for the same module
  3. Redundant Modbus RTU slave programming

 

 

 

Port Configuration

Setting of wiring method for port 2 on NFLR121
Figure: Setting of wiring method for port 2 on NFLR121

With the Resource Configurator, the following communication settings were made for each port:

  • Port name
  • Wiring method (2 wire/ 4 wire connection)
  • Half duplex / full duplex
  • Baud rate
  • Data bits
  • Parity setting

 

Programming the Same Module as Modbus RTU Master and Slave

Port name definition with Resource Configurator
Figure: Port name definition with Resource Configurator

For this application, port name SERIAL 1 was set to port 1 and port name SERIAL 2 was set to port 2 for the NFLR121 module in slot 9.

As shown below, two POUs were used in this application: SD_CMDBSM_BM_OPEN POU for the Modbus RTU master node and SD_CMDBSM_BS_OPEN POU for the slave node. Port 1 on the NFLR121 module was used for communication as a Modbus RTU master node and port 2 was used as a slave node.

SD_CMDBSM_BM_OPEN POU for the Modbus RTU master node and SD_CMDBSM_BS_OPEN POU for the slave node

Redundant Modbus RTU Slave Programming

Figure: Port name definition with Resource Configurator
Figure: Port name definition with Resource Configurator

NFLR121 modules were installed in slots 9 and 10. In this application, port name SERIAL 3 was set to port 1 and SERIAL 4 was set to port 2 for the redundant NFLR121 module in slot 10.

The two SD_CMDBSM_BS_OPEN POUs shown below were used in this application. Port 2 of the NFLR121 module in slot 9 and port 2 of the NFLR121 module in slot 10 were used for communication as a Modbus RTU slave node. In the event of a failure of port 2 on the NFLR121 module in slot 9, communication would not be disrupted.

Port 2 of the NFLR121 module in slot 9 and port 2 of the NFLR121 module in slot 10 were used for communication as a Modbus RTU slave node

Conclusion

Each of the communications modules on a STARDOM FCN autonomous controller can simultaneously function as Modbus master and slave nodes without affecting the other settings in the customer site. The use of two modules makes communications fully redundant.

In this application, the FCN Modbus master node simultaneously polls data from the FGS while the Modbus slave node transmits the FGS data to FAST/TOOLS. This keeps installation costs to a minimum. Furthermore, the use of the redundant module configuration ensures that there will be no interruption in the communications between FAST/TOOLS and the FCN autonomous controller.

行业

  • 上游

     上游行业包含海上和陆上活动,包括井口自动化、分馏、完井和分离,回收和制备地下或水下原油和天然气

    当石油被带到地表时,在运输之前必须将其分离。在三相分离中,一级和二级分离阶段通常分布有气体流量、水流量和油流量。气体的输送需要管道,并且在输送之前的上游阶段需要进行分馏。液体需要通过罐和管道输送并处理,这就需要精确的液位测量

    更多
  • 水和废水

    横河电机通过开发更节能的技术,帮助减少运营的碳排放,以及构建保护环境免受污染的坚固建筑,为可持续水生产提供控制解决方案。横河凭借先进的技术和广泛的应用专业知识与客户合作,提供可持续水生产的解决方案,促进客户的业务,并让整个工厂在生命周期中增加价值。横河的技术和产品可提高工厂的性能,确保它们在当今的水处理领域中具有竞争力,并降低运营成本。横河支持市政和工业水处理领域的各种水控制方面的应用。

    更多
  • 水处理

    横河电机提供理想的解决方案,以改善水处理厂的运行,使其更加可靠。这些解决方案包括复杂的技术、过硬的产品质量和贯穿生命周期的广泛应用技巧。

    更多
  • 污水处理

    污水处理厂使用大量的电动机、泵、鼓风机等,因此降低其耗电量以降低运营成本是十分重要的。横河电机提供控制解决方案,以提高能源效率。

    更多
  • 近海 (FPSO FLNG & FSRU)

    近海的勘探和生产需要在恶劣的条件下最大限度地保障正常运行时间。载人和无人驾驶设施需要可靠的综合控制和安全系统(ICSS),并且需要具有先进的远程监控能力。横河电机拥有先进技术和丰富经验,可以执行各种规模及自动化程度复杂的离岸项目。

    更多

相关产品&解决方案

  • FCJ All-in-one PLC/RTU

    The brick type model FCJ autonomous controller fulfills the basic requirements of the utility control. It also provides the reliability for the SCADA communication with network redundant capability.

    更多
  • SCADA软件(FAST/TOOLS)

    FAST/TOOLS始于灵活的先进系统技术(FAST)项目,如今已发展为综合且完全集成的SCADA应用套包。强大且灵活的FAST/TOOLS可以为各种应用提供安装服务,从50点的单元过程到数百万点的海上生产,以及延伸数千英里的管道系统。

    更多
  • SCADA 系统

    横河电机的物联网兼容监测控制及数据采集(SCADA)系统,优化了整个企业的自动化和监控。

    更多

置顶
WeChat QR Code
横河电机(中国)有限公司