A PLC controller and its control system
By integrating the DNP3.0 substation function module into the PLC controller and communicating directly with the DNP3.0 master station, the problems of high cost and poor flexibility of PLC controller equipment are solved, and low-cost and efficient data interaction is achieved.
Patent Information
- Application Number
- CN202510618576.2
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2025-05-14
- Publication Date
- 2026-11-17
AI Technical Summary
Existing PLC controllers have high equipment costs and poor flexibility when interacting with the DNP3.0 master station, requiring a dedicated Modbus to DNP3.0 gateway device for protocol conversion.
The DNP3.0 distributed network protocol substation function module is integrated into the PLC controller, which directly establishes a communication connection with the DNP3.0 master station, eliminating the need for a dedicated gateway device, simplifying the protocol conversion process, and improving the real-time performance of communication.
It reduces equipment costs, simplifies the communication process, and improves the system's flexibility and scalability, adapting to multi-master station scenarios and diverse data interaction needs.
Smart Images

Figure CN123113640A_ABST
Abstract
Description
Technical Field
[0001] This application relates to the field of industrial automation technology, and in particular to a PLC controller and its control system. Background Technology
[0002] In the field of industrial automation control, programmable logic controllers (PLCs) are widely used as core control devices in various production processes and systems. They are responsible for collecting field data, executing control logic, and communicating with host computers or other devices. As a core control device, the communication capability of the PLC controller directly affects the system's integration efficiency and flexibility.
[0003] Current PLC controllers typically support common protocols such as Modbus. However, when needing to interact with the Distributed Network Protocol (DNP) 3.0 master platform software, a dedicated Modbus-to-DNP 3.0 gateway device is required. The main function of this gateway device is to convert between the Modbus and DNP 3.0 protocols, enabling the DNP 3.0 master station to recognize Modbus format data sent by the PLC controller, and simultaneously converting instructions issued by the DNP 3.0 master station into Modbus format for the PLC controller to execute. This method of communication using a gateway device results in high equipment costs and poor flexibility. Summary of the Invention
[0004] The purpose of this application is to provide a PLC controller and its control system, which aims to solve the problem of high equipment cost when the current PLC controller interacts with the DNP3.0 master station.
[0005] To achieve the above objectives, this application adopts the following technical solution:
[0006] This application provides a PLC controller, in which a distributed network protocol DNP3.0 substation function module is integrated in the running system of the PLC controller. The DNP3.0 substation function module is used to establish a communication connection with the DNP3.0 master station.
[0007] The PLC controller provided in this application integrates a DNP3.0 substation function module in the running system, which can directly establish a communication connection with the DNP3.0 master station without the need for additional dedicated gateway deployment, thus saving equipment costs. It also eliminates the need for frame encoding and decoding through dedicated gateway equipment, reducing the complexity of the communication process, and can also eliminate the processing delay in the protocol conversion stage, thereby improving the real-time performance of communication.
[0008] In some embodiments, the PLC controller further includes a configuration parameter parsing module for parsing configuration parameters from the engineer station, the configuration parameters being used to configure the DNP3.0 substation functions.
[0009] In this way, the PLC controller also supports remote distribution of configuration parameters such as network type and master / slave station address by the engineer station, and dynamically establishes the mapping relationship between the PLC variable data area and the DNP3.0 protocol address, so that the same PLC controller can flexibly adapt to multi-master station scenarios and diverse data interaction needs, improving system scalability and field adaptability.
[0010] In some embodiments, the configuration parameters include: network type, network port number, whether multiple master stations are supported, whether to automatically enable the address, whether to accept any IP address, and at least one of the following: IP address, master station address, and slave station address.
[0011] In some embodiments, the PLC controller further includes a variable management module for managing DNP3.0 slave variables in the PLC variable data area.
[0012] In some embodiments, the variable management module is also used to establish a mapping relationship between the PLC variable data area and the DNP3.0 protocol address.
[0013] In some embodiments, the DNP3.0 substation function module includes a data encoding unit for encoding the data in the PLC variable data area based on the DNP3.0 protocol object type to obtain encoded data.
[0014] In some embodiments, the DNP3.0 substation function module package instruction parsing unit is used to parse instructions issued by the DNP3.0 master station.
[0015] In some embodiments, the instructions are used to instruct the PLC controller to modify the data in the PLC variable data area.
[0016] This application embodiment also provides a control system for a PLC controller, the control system including a PLC controller and a DNP3.0 master station; wherein, the PLC controller's runtime system integrates a distributed network protocol DNP3.0 substation function module, and the PLC controller and the DNP3.0 master station establish a communication connection through the DNP3.0 substation function module.
[0017] In some embodiments, the control system further includes an engineering station for acquiring configuration parameters of the DNP3.0 substation function as indicated by the user and uploading the configuration parameters to the PLC controller; the PLC controller is also used to configure the DNP3.0 substation function module according to the configuration parameters. Attached Figure Description
[0018] To more clearly illustrate the technical solutions of the embodiments of this application, the drawings used in the description of the embodiments will be briefly introduced below. Obviously, the drawings described below are only some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.
[0019] Figure 1 A schematic diagram of a control system for a PLC controller provided in an embodiment of this application;
[0020] Figure 2 A schematic diagram of an engineer's workstation display interface provided in an embodiment of this application;
[0021] Figure 3 A schematic diagram of another engineer station display interface provided in an embodiment of this application;
[0022] Figure 4 A functional diagram of an engineer's workstation and a PLC controller provided in an embodiment of this application;
[0023] Figure 5 This is a functional diagram of a DNP3.0 substation provided in an embodiment of this application. Detailed Implementation
[0024] The technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, and not all embodiments. Based on the embodiments of this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.
[0025] In the description of this application, it should be understood that the terms "upper," "lower," "left," "right," "front," "rear," "inner," and "outer," etc., indicate the orientation or positional relationship based on the orientation or relative positional relationship shown in the accompanying drawings. They are used only for the convenience of describing this application and for simplification, and do not indicate or imply that the device or element referred to must have a specific orientation, or be constructed and operated in a specific orientation. Therefore, they should not be construed as limitations on this application. Unless otherwise specified, the above-mentioned orientational descriptions can be flexibly set in practical applications, provided that the relative positional relationships shown in the accompanying drawings are satisfied.
[0026] The terms "first" and "second" are used for descriptive purposes only and should not be construed as indicating or implying relative importance or implicitly specifying the number of technical features indicated. Therefore, a feature defined as "first" or "second" may explicitly or implicitly include one or more of that feature. In the description of this application, unless otherwise stated, "a plurality of" means two or more.
[0027] In the description of this application, it should be noted that, unless otherwise expressly specified and limited, the terms "installation," "connection," "linking," and "communication" should be interpreted broadly. For example, they can refer to a fixed connection, a detachable connection, or an integral connection. They can refer to a direct connection or an indirect connection through an intermediate medium, or a connection within two components. Those skilled in the art can understand the specific meaning of the above terms in this application according to the specific circumstances.
[0028] In embodiments of this application, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, article, or apparatus. Without further limitation, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, article, or apparatus that includes that element.
[0029] In the embodiments of this application, the terms "exemplary" or "for example" are used to indicate that something is an example, illustration, or description. Any embodiment or design that is described as "exemplary" or "for example" in the embodiments of this application should not be construed as being more preferred or advantageous than other embodiments or design. Specifically, the use of the terms "exemplary" or "for example" is intended to present the relevant concepts in a specific manner.
[0030] In the description of this specification, specific features, structures, materials, or characteristics may be combined in any suitable manner in one or more embodiments or examples.
[0031] A PLC controller is a digital control system designed specifically for industrial environments. It implements functions such as logic control, sequential control, timing and counting, and data acquisition and processing through programming. Its core advantages lie in its high reliability, strong anti-interference capability, modular design, and flexible programmability, making it widely used in automation fields such as manufacturing, power systems, and transportation facilities.
[0032] Among them, Modbus and DNP3.0 protocols are two common and important communication protocols in the field of industrial automation. Modbus, with its simplicity, openness, and ease of implementation, is widely used in numerous industrial devices. Therefore, the internal runtime software of PLC controllers typically supports the commonly used Modbus protocol to facilitate data interaction with many devices that support this protocol, meeting basic industrial control needs. However, in complex industrial scenarios involving power systems, water treatment, and oil and gas, where high reliability, real-time performance, and data integrity are required, the DNP3.0 protocol, with its powerful features such as support for multiple data types, a robust event logging and time synchronization mechanism, and high fault tolerance, has become the mainstream communication protocol widely adopted in these fields.
[0033] Currently, the method of using a dedicated Modbus to DNP3.0 gateway to enable interaction between the PLC controller and the master station platform is costly and lacks flexibility.
[0034] In view of this, embodiments of this application provide a control system for a PLC controller, such as... Figure 1 As shown, system 100 may include a PLC controller 10 and a DNP3.0 master station 20. The PLC controller 10 includes a DNP3.0 substation function module. The PLC controller 10 can establish a communication connection with the DNP3.0 master station 20, for example, via Ethernet.
[0035] It should be noted that the PLC controller integrates the DNP3.0 substation function module during system operation, which can directly establish a communication connection with the DNP3.0 master station without the need for additional dedicated gateway deployment, saving equipment costs. It also eliminates the need for frame encoding and decoding through dedicated gateway equipment, reducing the complexity of the communication process, and eliminating the processing delay in the protocol conversion stage, thus improving the real-time performance of communication.
[0036] It should be noted that the control system of the PLC controller provided in this application embodiment can be applied to oil and gas pipelines, real-time monitoring and scheduling of long-distance oil and gas pipelines, pipeline leak detection and emergency response, intelligent control of urban gas pipeline networks, etc. It can also be applied to power transmission and distribution monitoring, such as substation equipment status monitoring, which interfaces with the power dispatching master station through DNP3.0, and can also be applied to railway signaling systems, etc., which will not be listed here. Among them, the control system of the PLC controller is only an exemplary name. The system can also be called a data acquisition system, a high-reliability DNP3.0 data acquisition system for oil and gas pipelines, etc., and this application does not limit it in this way.
[0037] In some embodiments, such as Figure 1 As shown, system 100 may also include engineer station 30.
[0038] The engineer station 30 is used to obtain the configuration parameters of the DNP3.0 substation function as instructed by the user, and upload the configuration parameters to the PLC controller 10. The PLC controller 10 is also used to configure the DNP3.0 substation function module according to the configuration parameters.
[0039] For example, the engineer station 30 and the PLC controller 10 can also communicate via Ethernet.
[0040] For example, the runtime system of a PLC controller integrates the DNP3.0 substation function module. The runtime system is the core software architecture of the PLC controller responsible for real-time execution of control logic, management of data interaction, and coordination of hardware resources. It includes functions such as real-time task scheduling, memory management, protocol stack integration, and exception handling; it can also be referred to as runtime software.
[0041] The runtime system has an address mapping with the DNP3.0 substation.
[0042] For example, the engineering station 30 can be an industrial control computer, an engineering laptop, a cloud engineering platform, a dedicated HMI / engineering terminal, or other possible devices that can meet industrial-grade reliability and protocol processing capabilities. This application does not specifically limit the actual implementation device.
[0043] Optionally, the engineer station 30 can also be used to edit, compile, download, and monitor PLC programs. To support DNP3.0 protocol substation functions, the engineer station 30 can also perform DNP3.0 variable selection and attribute setting functions, DNP3.0 protocol station parameter configuration functions, and DNP3.0 related data download functions.
[0044] Among these, editing refers to the programming environment provided by the engineer station 30, allowing engineers to write and modify the PLC's control logic program. Compilation refers to performing syntax checks and compiling the written PLC program to generate executable machine code for the PLC. Downloading refers to downloading the compiled program to the PLC controller, enabling the PLC to execute the new control logic. Variable monitoring refers to real-time monitoring of PLC variable values.
[0045] The DNP3.0 variable selection function allows operators of the engineering station 30 to specify PLC variables as DNP3.0 slave variables through the engineering station software. The engineering station 30 can display the PLC variable selection interface, thereby allowing operators to select PLC variables based on the PLC variables specified by the operator through this interface.
[0046] like Figure 2As shown, this interface displays the index, name, description, data type, address, and initial value of various PLC variables, P2P. Therefore, the operator of the engineering station 30 can select a specific PLC variable from the PLC variable list on this interface and designate it as a DNP3.0 slave variable. For example... Figure 2 As shown, the operator of the engineering station 30 selects the "Add to NP3.0 Slave List" operation based on the selected PLC variable. For example, in this interface, the operator of the engineering station 30 can also select operations such as adding variables, inserting variables, deleting variables, exporting CSV, importing CSV, copying, cutting, pasting, restoring, undoing, adding to the OPC list (adding variables to the OPC (OLE for Process Control) list for data exchange with the OPC server), adding to the power-loss retention list (adding variables to the power-loss retention list to ensure that the variable's value is retained after a system power failure), adding to the Modbus slave list (adding variables to the Modbus slave device list for Modbus communication), adding to the IEC104 slave list (adding variables to the IEC104 slave device list for the IEC104 communication protocol), and adding to the allowed forced list.
[0047] The variable attribute setting function allows operators of the engineering station 30 to configure the basic attributes of DNP3.0 variables, including CLASS category, DNP3.0 protocol type and internal attributes, DNP3.0 protocol address, and for floating-point variables, scaling factor, upper limit value, lower limit value, and dead zone value. For example... Figure 3 As shown, the engineer station 30 can display the basic attribute configuration interface of DNP3.0 slave variables. This interface can include a list of DNP slave variables, station1, which includes multiple DNP slave variables, as well as the index, name, data type, description, scaling factor, lower limit value, upper limit value, dead zone setting, class, DNP3.0 protocol attribute, DNP3.0 protocol type, DNP3.0 protocol address, etc. of each DNP slave variable.
[0048] The DNP3.0 protocol station parameter configuration function allows operators to configure the basic parameters of DNP3.0 substations via an engineering workstation and then send these configuration parameters to the PLC controller. These configuration parameters may include at least one of the following: network type, network port number, whether multiple master stations are supported, whether to automatically enable the address, whether to accept any IP address, IP address, master station address, and slave station address.
[0049] For example, the engineering station 30 can provide the user (operator) with a configuration interface for all parameters. This configuration interface provides the user with a range of reference values, such as the attribute configuration table in Table 1. Table 1 may include the name, data type, value (which can be understood as the current setting value), maximum (the maximum value that can be set), and minimum (the minimum value that can be set) of each DNP parameter. For example, DNP parameters include network type, network port, Multiple Master, Self address enable, Accept anyIP, IP address, Master address, Master address1 to Master address4, Slave address, Datalink confirm, DL retries, DL timeout (ms), AFP timeout (ms*10), SBO timeout (sec), 0 to disable write timer... (0 indicates disable write time recording), URBE Overflow Number, MAX Fragment size, Analog event enable, Analog event size, Force URBE enable, Receive URBE command enable, and URBE Delivery. The network type has several data types: Unlimited (URBE transmission is unlimited), URBE Need confirm (URBE requires confirmation), 0 disables unsolicited delay, Class 1 urbe is enabled, Class 2 urbe is enabled, and Min class 2 num ofurbes is the minimum number of Class 2 URBEs. The network type data type is BOOL (Boolean) with a value of TCP. The network port data type is UINT (unsigned integer) with a value of 20000, a maximum of 65535, and a minimum of 0.The data type of MultipleMaster is BOOL, and the value is Disable. USINT refers to unsigned short integer, and so on.
[0050] If the user does not configure the parameters, the DNP3.0 substation in the PLC controller will initialize and run according to the default data.
[0051] Table 1
[0052]
[0053]
[0054] The data downloaded from the engineer station 30 to the PLC controller needs to be encoded according to a specific format to become a communication protocol between the upper and lower computers. The data type definitions of the PLC variables selected as DNP3.0 slave variables are shown in Table 2 below:
[0055] Table 2
[0056]
[0057]
[0058] Add a new CPU parameter download file to the 12 download files. The file FileID is kCPUCommConfig(25). Also, add two new data segments to the download data area, namely kDNPSlaveParam=28 and kDNPSlavelndex=29.
[0059] In some embodiments, the configuration parameter data definition of DNPSlave can be as shown in Table 3:
[0060] Table 3
[0061]
[0062]
[0063] In some embodiments, the DNP3.0 variable data definition can be as shown in Table 4:
[0064] Table 4
[0065]
[0066]
[0067] In some embodiments, the PLC controller 10 can realize DNP3.0 protocol substation configuration data parsing, DNP3.0 protocol substation functions, runtime software PLC variable data area, and communication functions between the DNP3.0 protocol substation and the DNP3.0 master station software. Figure 4 As shown, the engineer station 30 can provide DNP3.0 parameter configuration data and DNP3.0 selected variable information to the PLC controller 10. The PLC controller 10 can then receive and parse the downloaded data to obtain the parameter configuration information and selected variable information. Based on the parameter configuration information, it can configure the DNP3.0 substation and reinitialize it. Furthermore, it can save the selected variable information to a designated buffer.
[0068] For example, taking the application of system 100 to oil and gas pipelines as an example, PLC controller 10 can also be a dedicated PLC controller for oil and gas pipelines.
[0069] In some embodiments, the PLC controller further includes a configuration parameter parsing module for parsing configuration parameters from the engineer station, the configuration parameters being used to configure the DNP3.0 substation functions.
[0070] For example, DNP3.0 protocol substation configuration data parsing refers to the runtime software parsing the downloaded data segments according to the aforementioned upper and lower computer communication protocols and storing them in the corresponding buffers. The DNP configuration parameters are shown in Table 5 below:
[0071] Table 5
[0072] Serial Number Parameter name Data types 1 Network type UINT8 2 network port UINT16 3 Does it support multiple DNP master sites? UINT8 4 Does it support automatic enable address? UINT8 5 Accept any IP address UINT8 6 Main site IP address UINT32 7 Main site #0 address UINT16 8 Main site #1 address UINT16 9 Main site #2 address UINT16 10 Main site #3 address UINT16 11 Main site #4 address UINT16
[0073] In some embodiments, the PLC controller 10 further includes a variable management module for managing DNP3.0 slave variables in the PLC variable data area.
[0074] For example, the variable management module is also used to establish a mapping relationship between the PLC variable data area and the DNP3.0 protocol address.
[0075] For example, the runtime software PLC variable data area and the DNP3.0 protocol address can be implemented in the following way:
[0076] When the DNP protocol substation uploads data, it obtains the actual address, length, and data type of the PLC variable based on the cached variable information, and then uploads the data value to the main station platform.
[0077] After the DNP protocol substation receives downlink data, it obtains the actual address, length, and data type of the PLC variable based on the slave variable information in the cache, and writes the downlink data into the runtime software data area.
[0078] In some embodiments, the DNP3.0 substation function module includes a data encoding unit for encoding the data in the PLC variable data area based on the DNP3.0 protocol object type to obtain encoded data.
[0079] In some embodiments, the DNP3.0 substation function module package instruction parsing unit is used to parse instructions issued by the DNP3.0 master station 20. These instructions are used to instruct the PLC controller to modify data in the PLC variable data area.
[0080] For example, the DNP3.0 protocol substation function includes at least two parts: first, encoding the DNP3.0 slave variables according to the protocol format and uploading them to the DNP3.0 master station platform via Ethernet; second, receiving and parsing the specified DNP slave variable data from the DNP3.0 master station platform and storing the data in the runtime data area.
[0081] In this application, the DNP3.0 master site can also be referred to as the master site platform, the DNP3.0 master site platform, the DNP3.0 master site software, etc.
[0082] For example, such as Figure 5 As shown, the DNP3.0 protocol substation module can also perform operations such as creating a DNP3.0 server, initializing the SOE buffer, initializing DNP3.0 parameters, initializing DNP3.0 configuration, initializing the DNP3.0 server, and running DNP3.0 substation services.
[0083] In some embodiments, the DNP3.0 protocol substation completes initialization operations when the PLC controller starts, including creating a socket server, initializing the SOE buffer, initializing substation parameters, completing substation configuration, initializing and running the socket server, and running the DNP substation service.
[0084] This enables a new DNP3.0 data acquisition mode. By integrating the DNP3.0 protocol substation into the PLC controller's runtime software, the PLC controller can directly communicate and exchange data with the DNP3.0 master station platform. When the DNP3.0 master station platform communicates with the PLC controller, frame encoding and decoding no longer require a dedicated gateway device, simplifying equipment requirements during field deployment and reducing engineering costs. The engineering workstation can configure the DNP3.0 substation, offering greater flexibility in usage.
[0085] In addition, this application embodiment also provides a PLC controller, the PLC controller's runtime system integrating a distributed network protocol DNP3.0 substation function module, the DNP3.0 substation function module being used to establish a communication connection with the DNP3.0 master station.
[0086] In some embodiments, the PLC controller further includes a configuration parameter parsing module for parsing configuration parameters from the engineer station, the configuration parameters being used to configure the DNP3.0 substation functions.
[0087] In some embodiments, the configuration parameters include: network type, network port number, whether multiple master stations are supported, whether to automatically enable the address, whether to accept any IP address, and at least one of the following: IP address, master station address, and slave station address.
[0088] In some embodiments, the PLC controller further includes a variable management module for managing DNP3.0 slave variables in the PLC variable data area.
[0089] In some embodiments, the variable management module is also used to establish a mapping relationship between the PLC variable data area and the DNP3.0 protocol address.
[0090] In some embodiments, the DNP3.0 substation function module includes a data encoding unit for encoding the data in the PLC variable data area based on the DNP3.0 protocol object type to obtain encoded data.
[0091] In some embodiments, the DNP3.0 substation function module package instruction parsing unit is used to parse instructions issued by the DNP3.0 master station.
[0092] In some embodiments, the instructions are used to instruct the PLC controller to modify the data in the PLC variable data area.
[0093] In addition, for further information about the PLC controller, please refer to the relevant description of the PLC controller 10 in the above system 100, which will not be repeated here.
[0094] Based on the above embodiments, by directly integrating the DNP3.0 substation function module into the PLC controller's runtime system, end-to-end communication with the DNP3.0 master station platform is realized. Compared with the Modbus-DNP3.0 protocol conversion gateway, the equipment deployment cost and system complexity are significantly reduced, while eliminating the additional fault risks introduced by the gateway device.
[0095] Furthermore, it supports remote distribution of configuration parameters such as network type and master / slave station address by the engineer station, and dynamically establishes the mapping relationship between the PLC variable data area and the DNP3.0 protocol address, enabling the same PLC controller to flexibly adapt to multi-master station scenarios and diverse data interaction needs, thereby improving system scalability and field adaptability.
[0096] The above are merely specific embodiments of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.
Claims
1. A PLC controller, characterized in that, The PLC controller's runtime system integrates a distributed network protocol DNP3.0 substation function module, which is used to establish a communication connection with the DNP3.0 master station.
2. The PLC controller according to claim 1, characterized in that, The PLC controller also includes a configuration parameter parsing module, which is used to parse configuration parameters from the engineer station. These configuration parameters are used to configure the functions of the DNP3.0 substation.
3. The PLC controller according to claim 2, characterized in that, The configuration parameters include: network type, network port number, whether multiple master stations are supported, whether to automatically enable the address, whether to accept any IP address, and at least one of the following: IP address, master station address, and slave station address.
4. The PLC controller according to claim 1, characterized in that, The PLC controller also includes a variable management module for managing DNP3.0 slave variables in the PLC variable data area.
5. The PLC controller according to claim 4, characterized in that, The variable management module is also used to establish the mapping relationship between the PLC variable data area and the DNP3.0 protocol address.
6. The PLC controller according to claim 1, characterized in that, The DNP3.0 substation functional module includes a data encoding unit, which is used to encode the data in the PLC variable data area based on the DNP3.0 protocol object type to obtain the encoded data.
7. The PLC controller according to claim 1, characterized in that, The DNP3.0 substation function module package instruction parsing unit is used to parse the instructions issued by the DNP3.0 master station.
8. The PLC controller according to claim 7, characterized in that, The instruction is used to instruct the PLC controller to modify the data in the PLC variable data area.
9. A control system for a PLC controller, characterized in that, The control system includes a PLC controller and a DNP3.0 master station; wherein, the PLC controller integrates a distributed network protocol DNP3.0 substation function module in its runtime system, and the PLC controller and the DNP3.0 master station establish a communication connection through the DNP3.0 substation function module.
10. The control system according to claim 9, characterized in that, The control system also includes an engineer station, used to obtain configuration parameters of the DNP3.0 substation function as instructed by the user, and upload the configuration parameters to the PLC controller; The PLC controller is also used to configure the DNP3.0 substation function module according to the configuration parameters.
