A control method for an IoT remote I / O system

Abstract

This application discloses a control method for an IoT remote I / O system, comprising: constructing an IoT remote I / O system including a third-party master station, one or more remote I / O modules, and an IoT cloud server; each remote I / O module, acting as a client, establishes a real-time communication connection with the IoT cloud server via an Ethernet communication protocol to report data and receive and store configuration requests for linkage rules sent by the IoT cloud server; simultaneously, each remote I / O module, acting as a slave station, establishes a communication connection with the third-party master station via a fieldbus and autonomously selects its operating mode based on the fieldbus connection status; each remote I / O module is configured with standby, offline, and online states, and switches between these states. This application enhances the security and reliability of I / O modules in system applications, possesses autonomous diagnostic, anomaly handling, and problem feedback capabilities, and improves the robustness of system applications.

Description

Technical Field

[0001] This invention relates to the field of industrial automation control technology, and in particular to a control method for an Internet of Things (IoT) remote I / O system. Background Technology

[0002] Commonly available I / O modules support fieldbus protocols and connect to field sensors and actuators via input / output points. Using I / O modules reduces the cost and workload of field wiring and lowers maintenance costs. As a slave device in the fieldbus, the I / O module receives control commands from the master station and responds to the master station's queries regarding field status. However, as a slave device, the I / O module lacks the ability to perform autonomous diagnostics, handle anomalies, and provide problem feedback. If the master station malfunctions or communication with the master station fails, the I / O module cannot activate the field sensors and actuators, posing a potential threat and bottleneck to the stability and reliability of the entire system. Summary of the Invention

[0003] The purpose of this invention is to provide a control method for an Internet of Things (IoT) remote I / O system to solve the problems mentioned in the above-mentioned technical background.

[0004] To achieve the above objectives, the present invention adopts the following technical solution:

[0005] A control method for an IoT remote I / O system includes:

[0006] Construct an IoT remote I / O system comprising a third-party master station (typically a PLC or PC), one or more remote I / O modules, and an IoT cloud server. Each remote I / O module acts as a client, establishing a real-time communication connection with the IoT cloud server via the Ethernet TCP / IP communication protocol to report data and receive and store configuration requests for linkage rules sent by the IoT cloud server. Simultaneously, each remote I / O module acts as a slave, establishing a communication connection with the third-party master station via a fieldbus and autonomously selecting its operating mode based on the fieldbus connection status.

[0007] Each of the remote I / O modules is configured with multiple states: standby, offline, and online, and the remote I / O module switches between these states:

[0008] When the system is powered on, the remote I / O module enters standby mode;

[0009] Upon receiving a registration response message from the IoT cloud server, the remote IO module changes from its standby state before initiating registration to its offline state.

[0010] When the communication between the remote IO module and the third-party master station is normal, the remote IO module switches from offline to online and enters the controlled working mode. In the controlled working mode, the remote IO module sends the sensor data sampled on site to the third-party master station and receives and executes the control commands sent by the third-party master station.

[0011] When communication between the remote IO module and the third-party master station fails, the remote IO module switches from online to offline and enters an automatic control mode. In the automatic control mode, the remote IO module runs preset process control logic or executes linkage control operations corresponding to the linkage rules configured by the IoT cloud server.

[0012] Preferably, the on-chip flash memory of each remote I / O module stores multiple linkage rule information configured by the IoT cloud server. Each linkage rule includes a rule number, rule type, delay judgment duration, event triggering condition, execution object, and response action; wherein,

[0013] The rule types include alarms and anomalies;

[0014] The delay judgment duration is used as the starting condition for the linkage control operation. That is, after the event triggering condition is met for the first time, the delay preset time is used for judgment again. If the event triggering condition is triggered again, it is considered that the event has occurred and the linkage control operation is executed.

[0015] The event triggering conditions include the range of parameters for event triggering.

[0016] More preferably, the linkage rules include single-condition triggering rules and multi-condition triggering rules; wherein, the single-condition triggering rule is: when a certain event triggering condition is met, one or more response actions corresponding to the event triggering condition are executed; the multi-condition triggering rule is: when two or more event triggering conditions are met at the same time, one or more response actions are executed.

[0017] More preferably, the events triggered by the event triggering conditions are divided into abnormal events and alarm events according to the rule type of the linkage rules. In the online state, when an abnormal event occurs, the remote IO module has a higher priority in handling the abnormal event than the third-party master station has a higher priority in controlling the remote IO module. The third-party master station has a higher priority in controlling the remote IO module than the remote IO module has a higher priority in handling alarm events. That is, in the online state, if an abnormal event is detected, the remote IO module will handle the abnormal event first. If an alarm event is detected, the remote IO module will not respond and will continue to receive and execute the control commands sent by the third-party master station.

[0018] Preferably, each of the remote IO modules is also configured with an abnormal state, which includes an offline abnormal state and an online abnormal state. The remote IO module performs timed or real-time detection on the event triggering conditions of the linkage rules configured on the IoT cloud server in both online and offline states.

[0019] When the current state of the remote I / O module is online, if the triggering condition of an abnormal event corresponding to a certain abnormal event parameter is detected, the remote I / O module will switch the current state from online to online abnormal state and execute the corresponding linkage control operation; if the abnormal situation is eliminated after the linkage control operation is executed, the remote I / O module will return the current state from online abnormal state to online state.

[0020] When the current state of the remote I / O module is offline, if the triggering condition of an abnormal event corresponding to a certain abnormal event parameter is detected, the remote I / O module will switch the current state from offline to offline abnormal state and execute the corresponding linkage control operation; if the abnormal situation is eliminated after the linkage control operation is executed, the remote I / O module will return the current state from offline abnormal state to offline state.

[0021] More preferably, the control method further includes:

[0022] When the current state of the remote IO module is offline, if the communication between the remote IO module and the third-party master station is restored to normal, the remote IO module will switch from offline to online.

[0023] When the current state of the remote IO module is online, if the communication between the remote IO module and the third-party master station is abnormal, the remote IO module will switch from online to offline.

[0024] When the current state of the remote I / O module is offline and the abnormal situation has not been resolved, if communication between the remote I / O module and the third-party master station returns to normal, the remote I / O module will switch from offline to online abnormal state; and

[0025] When the current state of the remote IO module is an online abnormal state and the abnormal situation has not been eliminated, if the communication between the remote IO module and the third-party master station is abnormal, the remote IO module will switch from the online abnormal state to the offline abnormal state.

[0026] Furthermore, if the current state of the remote IO module is an online abnormal state, and the control command of the third-party master station conflicts with the linkage control operation triggered by the linkage rules configured in the IoT cloud server, then the linkage control operation shall be executed first.

[0027] Preferably, the preset process control logic is a customized control logic, which is a binary program code customized and developed according to the process requirements of the customer's site. The binary program code is pre-programmed into the on-chip flash of the remote IO module.

[0028] More preferably, the executable file size of the preset process control logic does not exceed 16K.

[0029] Preferably, during communication with the IoT server, each of the remote IO modules reports data including sensor data sampled on-site, operating status machine, total device operating time, device operating events, and control enable duration of device digital output.

[0030] Preferably, each of the remote I / O modules further includes an SDIO controller, which can identify the storage area of ​​the card to store events, sensor sampling data, actuator execution data and state switching information during the operation of the remote I / O module, so as to realize real-time storage and backup of operation data and operation logs.

[0031] Compared with the prior art, the technical solution of the present invention has the following beneficial effects:

[0032] This application provides a control method for an IoT remote I / O system. The system comprises a third-party master station, one or more remote I / O modules, and an IoT cloud server. The remote I / O modules communicate via both fieldbus and Ethernet. This transforms the single-point control of existing technologies into multi-node control. Each remote I / O module acts as a node on a neural network, interacting with the third-party master station via fieldbus communication. During normal operation, it adheres to the control of the third-party master station. In case of anomalies, such as bus malfunctions, timely exception handling and reporting are possible. The remote I / O modules interact with the IoT cloud server via Ethernet communication. Through data reporting and management by the IoT cloud server, robust system monitoring is enhanced, allowing maintenance personnel to easily and quickly grasp the operational status of the remote I / O modules and key field parameters.

[0033] The fieldbus communication method in this application transforms the existing tree-like topology into a star-like topology. This changes the previous model where the controller or other field control layer devices of the fieldbus third-party master station uniformly reported to the supervisory layer. Instead, the fieldbus layer's IO modules directly send data to the supervisory layer, eliminating the need for a controller. This transforms the entire system from one where the IO modules are driven and controlled by the fieldbus third-party master station to one where control can be directly issued by the supervisory layer. In simpler applications, this eliminates reliance on the field control layer and reduces communication costs. The remote IO module in this application is configured with multiple states. When connected to the third-party master station, it operates in an online state; when disconnected, it operates in an offline state. This ensures that when connected, the remote IO module prioritizes control from the third-party master station, in addition to pre-set high-priority commands from the IoT cloud server. When disconnected, the remote IO module can execute its own pre-set control logic, including pre-set complex process control logic and configurations of linkage rules issued by the IoT cloud server. This application can enhance the security and reliability of the IO module in system applications. The remote IO module of this application has the ability to self-diagnose, handle exceptions and provide problem feedback. The technical solution of this application improves the robustness of system applications. Attached Figure Description

[0034] The accompanying drawings, which constitute a part of this application, are used to provide a further understanding of this application. The illustrative embodiments and descriptions of this application are used to explain this application and do not constitute an undue limitation of this application. In the drawings:

[0035] Figure 1 This is a block diagram of an IoT remote I / O system constructed according to the present invention;

[0036] Figure 2 This is a schematic diagram of the hardware structure of a remote I / O module according to the present invention;

[0037] Figure 3 This is a schematic diagram of the multi-state switching of the remote I / O module of the present invention. Detailed Implementation

[0038] To make the objectives, technical solutions, and effects of this invention clearer and more explicit, the invention will be further described in detail below with reference to the accompanying drawings and examples. It should be understood that the specific embodiments described herein are merely illustrative of the invention and are not intended to limit the invention.

[0039] It should be noted that the terms "first," "second," etc., in the specification, claims, and accompanying drawings of this invention are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that such data can be used interchangeably where appropriate. Furthermore, the terms "comprising" and "having," and any variations thereof, are intended to cover non-exclusive inclusion. For example, a process, method, system, product, or apparatus that comprises a series of steps or units is not necessarily limited to those steps or units explicitly listed, but may include other steps or units not explicitly listed or inherent to these processes, methods, products, or apparatuses.

[0040] Example 1

[0041] Figure 1 This is a block diagram of an IoT remote I / O system.

[0042] like Figure 1 As shown, this application constructs an IoT remote I / O system, including a third-party master station (generally a PLC or PC), one or more remote I / O modules, and an IoT cloud server. Each remote I / O module acts as a client, establishing a real-time communication connection with the IoT cloud server via the Ethernet TCP / IP communication protocol. This enables data reporting (including sensor data sampled on-site, operating state machine, total equipment operating time, equipment operating events, and control enable duration of equipment digital outputs), as well as receiving and storing configuration requests for linkage rules sent by the IoT cloud server. Simultaneously, each remote I / O module acts as a slave, establishing a communication connection with the third-party master station via a fieldbus and autonomously selecting its operating mode based on the fieldbus connection status.

[0043] Figure 2 A schematic diagram of the hardware structure of a remote I / O module is shown.

[0044] See Figure 2 As shown, each remote I / O module includes: a microcontroller, a fieldbus controller, an Ethernet controller, an input interface, an output interface, a debug interface, an SDIO controller, and a temperature sampling circuit, all electrically connected to the microcontroller, and a power supply unit that supplies power to the aforementioned components of the remote I / O module.

[0045] The SDIO controller in each of the aforementioned remote I / O modules is connected to the microcontroller. The SDIO controller controls the reading of data from the storage area of ​​the SDIO-identifiable card, storing critical runtime data and operation logs to facilitate information retrieval during operation in case of failure. The SDIO-identifiable card includes: SD card, TF card, MMC card, or eMMC card.

[0046] Each of the aforementioned remote I / O modules communicates via both fieldbus and Ethernet. The fieldbus can be Profinet, EtherCat, Profibus, DeviceNet, Canopen, or Modbus, preferably using the Modbus RTU bus protocol based on an RS485 interface.

[0047] Each of the aforementioned remote I / O modules includes a microcontroller comprising a processing unit. This processing unit performs one or more of the following: arithmetic operations, logical operations, discrete or enhanced PID algorithms, and control algorithms. Furthermore, the processing unit has a function for preset calculation parameters. These parameters can be written to the on-chip flash memory via Ethernet communication. The unit can then perform event judgments based on the preset parameters and execute event-driven actions according to the judgment results. The processing unit may also have a special control logic preset function, allowing customization of complex process control logic for different applications. This preset logic is achieved by writing to a special area of ​​the on-chip flash memory.

[0048] Example 2

[0049] The control method for an IoT remote I / O system constructed in Example 1 is as follows:

[0050] Each of the aforementioned remote I / O modules has a special control logic preset function, which can customize complex process control logic for different applications. This preset logic is achieved by writing to a special area of ​​the on-chip flash memory. The complex process control logic is customized control logic, consisting of binary program code developed specifically for the customer's on-site process requirements. This binary program code is pre-programmed into the on-chip flash memory of the remote I / O module, allowing the remote I / O module to better adapt to on-site needs in handling anomalies. For example, in a livestock farming environmental control system, to ensure that the air quality and temperature in different indoor areas reach a reasonable range, special customized control logic is required for multiple controlled objects. This logic needs to utilize advanced control algorithms such as PID control, and cannot be controlled by simple true / false conditional logic. Preferably, the executable file size of the customized complex process control logic does not exceed 16KB.

[0051] Each remote I / O module stores multiple linkage rule information configured by the IoT cloud server in its on-chip flash memory. Each linkage rule includes a rule number, rule type (alarm, exception), delay judgment duration, event triggering condition, execution object, and response action. The delay judgment duration is used as the initiation condition for the linkage control operation. That is, after the event triggering condition is met for the first time, a preset delay is performed for a second judgment. If the event triggering condition is triggered again, the event is considered to have occurred, and the linkage control operation is executed. The event triggering condition includes the parameter range for the event trigger; the response action includes the value that the execution object needs to be set at this time.

[0052] For example:

[0053] The IoT cloud server configures the linkage rules of remote I / O modules via Ethernet. The configuration includes:

[0054] 1) Event Name: Defined by the client;

[0055] 2) Event type: Alarm or anomaly;

[0056] 3) Event Number: Defined by the customer;

[0057] 4) Event trigger delay: This is the delay judgment duration, which is customized by the customer. When the delay judgment duration is written, the event will be judged again after the set time after the event trigger condition is met for the first time. If the trigger condition is still true, the condition is met and the linkage control operation is executed. If the trigger condition is not true at this time, the judgment ends.

[0058] 5) Event triggering conditions: Select a specific point on the remote I / O module as the judgment object, and write the judgment range of the point value;

[0059] 6) Event-linked control operation: Select a point on the remote IO module as the execution object, and write the execution value and the value type.

[0060] The remote I / O module reports location information to the IoT cloud server, including the type of input and output locations and the set parameters. When setting event trigger conditions, the trigger conditions can be preset for a specific location, such as specifying the parameter range within which the input value of input location A will trigger an event. Event linkage settings can include setting a value for output location B when an event occurs.

[0061] The above configuration is transmitted to the remote I / O module via a protocol and written to flash memory, ensuring that the configuration is not lost even when power is off. The remote I / O module will perform real-time judgments based on the configured event parameters. When the conditions are met, it will report the occurrence of the event and execute the corresponding control operation.

[0062] In one scenario, the linkage rule can be a single-condition triggering rule. That is, when a certain event triggering condition is met, one or more response actions corresponding to that event triggering condition are executed. For example, if the temperature reaches the lower limit, the hot air blower is activated while simultaneously reducing the air outlet opening. Or, if the temperature reaches the upper limit, the cooler is activated while simultaneously increasing the air outlet opening. In another scenario, the linkage rule can be a multi-condition triggering rule. That is, when two or more event triggering conditions are met simultaneously, one or more response actions are executed. For example, if the terminal carbon dioxide concentration and temperature are both too high, the terminal air outlet opening is increased.

[0063] Each of the aforementioned remote I / O modules is configured with multiple states and two operating modes. The multiple states include: standby state, offline state, online state, and abnormal state, wherein the abnormal state includes offline abnormal state and online abnormal state. The remote I / O module switches between these multiple states. The two operating modes are a controlled operating mode and a self-controlled operating mode. When the remote I / O module operates in the offline state or offline abnormal state, it is in the self-controlled operating mode; when the remote I / O module operates in the online state or online abnormal state, it is in the controlled operating mode.

[0064] In this invention, the definitions of the above states are based on fieldbus communication. In the offline state and the offline abnormal state, the communication between the remote I / O module and the third-party master station is abnormal, meaning the remote I / O module is not connected to the third-party master station. In the online state and the online abnormal state, the communication between the remote I / O module and the third-party master station is normal, meaning the remote I / O module is connected to the third-party master station. In both the online and offline states, the remote I / O module performs periodic or real-time detection of the event triggering conditions of the linkage rules configured on the IoT cloud server.

[0065] Figure 3 This is a schematic diagram of the multi-state switching of the remote IO module described in this invention. The main device shown in the figure is the third-party main station mentioned in the context, and the cloud shown is the IoT cloud server mentioned in the context.

[0066] The status switch of the remote IO module is autonomously switched according to specific operating conditions. After registering with the Internet of Things cloud server (i.e., the cloud), the standby state will enter the offline state; in the offline state, the remote IO module executes linkage control operations through the linkage rules configured by the Internet of Things cloud server, or executes preset complex process control logics. In the offline state, after the remote IO module is connected to the third-party master station, it enters the online state. In the online state, the remote IO module executes the control requirements sent by the third-party master station. In both the online state and the offline state, the event trigger conditions configured by the Internet of Things cloud server are judged. When the event trigger conditions are triggered, the status of the remote IO module will switch to the online abnormal state or the offline abnormal state.

[0067] Specifically, as shown in Figure 3 the above-mentioned status switch processes are as follows:

[0068] When the system is powered on, the remote IO module enters the standby state.

[0069] After receiving the registration response message from the Internet of Things cloud server, the remote IO module is updated from the standby state before initiating registration to the offline state.

[0070] (1) Controlled working mode

[0071] When the communication between the remote IO module and the third-party master station is normal, the remote IO module switches from the offline state to the online state, and the remote IO module enters the controlled working mode. In the controlled working mode, the remote IO module sends the sensor data sampled on-site to the third-party master station and receives and executes the control instructions sent by the third-party master station.

[0072] When the current status of the remote IO module is the online state, if it is detected that the abnormal event trigger condition corresponding to a certain abnormal event parameter is triggered, the remote IO module switches its current status from the online state to the online abnormal state and executes the corresponding linkage control operation; if the abnormal situation is eliminated after executing the linkage control operation, the remote IO module returns its current status from the online abnormal state to the online state.

[0073] It should be noted that when the current status of the remote IO module is the online abnormal state, if the control instruction of the third-party master station conflicts with the linkage control operation triggered by the linkage rules configured by the Internet of Things cloud server, the linkage control operation is preferentially executed.

[0074] (2) Self-controlled working mode

[0075] When communication between the remote IO module and the third-party master station fails, the remote IO module switches from online to offline and enters an automatic control mode. In the automatic control mode, the remote IO module runs preset process control logic or executes linkage control operations corresponding to the linkage rules configured by the IoT cloud server.

[0076] When the current state of the remote I / O module is offline, if the triggering condition of an abnormal event corresponding to a certain abnormal event parameter is detected, the remote I / O module will switch the current state from offline to offline abnormal state and execute the corresponding linkage control operation; if the abnormal situation is eliminated after the linkage control operation is executed, the remote I / O module will return the current state from offline abnormal state to offline state.

[0077] (3) Switching between automatic control mode and controlled operation mode

[0078] When the current state of the remote IO module is offline, if the communication between the remote IO module and the third-party master station is restored to normal, the remote IO module will switch from offline to online, and the working mode will switch from self-controlled working mode to controlled working mode.

[0079] When the remote I / O module is currently online, if an abnormality occurs in the communication between the remote I / O module and the third-party master station, the remote I / O module will switch from online to offline, and the working mode will switch from controlled working mode to self-controlled working mode.

[0080] When the current state of the remote IO module is offline and the abnormal situation has not been eliminated, if the communication between the remote IO module and the third-party master station is restored to normal, the remote IO module will switch from offline abnormal state to online abnormal state, and the working mode will switch from self-controlled working mode to controlled working mode.

[0081] When the current state of the remote IO module is an online abnormal state and the abnormal situation has not been eliminated, if the communication between the remote IO module and the third-party master station is abnormal, the remote IO module will switch from the online abnormal state to the offline abnormal state, and the working mode will switch from the controlled working mode to the self-controlled working mode.

[0082] It should be noted that the event types configured by the Internet of Things cloud server include alarms and exceptions. Whether in the online state or the offline state, the remote IO module gives the highest priority to the handling of exception events. For example, in the online state, when an exception event occurs, the priority of the remote IO module in handling the exception event is higher than the control of the third-party master station over the remote IO module. The remote IO module will first obtain control, switch the status to the online exception state, spontaneously handle the exception event, and execute the corresponding linkage response actions. In the offline state, when an exception event occurs, similarly, the remote IO module will switch the status to the offline exception state and execute the corresponding linkage response actions. The remote IO module gives a lower priority to the handling of alarm events. In the offline state, the remote IO module is not controlled by the third-party master station. When the event trigger condition of the preset alarm event is triggered, the remote IO module will respond and execute the corresponding linkage response actions. In the online state, the remote IO module is mainly controlled by the third-party master station. The alarm event itself is a status reminder. For example, a certain temperature value drops to a value that requires attention, but it does not belong to an abnormal situation. The priority of the alarm event itself is lower than the control of the third-party master station. Therefore, in the online state, if an alarm event is found to occur, the remote IO module does not respond.

[0083] In a preferred embodiment, considering the insecurity of Ethernet transmission, when the remote IO module communicates with the Internet of Things cloud server (cloud), the present application can use data encryption technology to encrypt the transmitted data to enhance the security of data transmission.

[0084] In summary, this application constructs an IoT remote I / O system based on remote I / O modules, changing the previous network topology structure of connecting I / O modules with third-party master stations. The original tree topology is transformed into a star topology. Specifically, the previous mode where the controller of the fieldbus master station or other field control layer devices uniformly reported to the supervisory layer is modified so that the fieldbus layer I / O modules directly send data to the supervisory layer. The control method changes from the original I / O modules being driven by the controller of the fieldbus master station to direct control from the supervisory layer or control via preset events, eliminating dependence on the field control layer and reducing communication costs. Furthermore, the communication methods of the remote I / O modules in this application include not only fieldbus communication but also Ethernet communication. In Ethernet communication, each remote I / O module acts as a client, establishing a real-time communication connection with the IoT cloud server via the Ethernet TCP / IP communication protocol. This enables data reporting and the receipt and storage of configuration requests for linkage rules sent by the IoT cloud server. When preset event triggering conditions are triggered, the module executes corresponding linkage control operations. In fieldbus communication, each remote I / O module acts as a slave, establishing a communication connection with a third-party master station via the fieldbus for data and command interaction. The remote I / O modules in this application are configured with multiple states. When connected to a third-party master station, they operate in an online state; when disconnected, they operate in an offline state. This ensures that when connected to a third-party master station, the remote I / O modules prioritize receiving control from the third-party master station, in addition to preset high-priority commands issued by the IoT cloud server. When disconnected, the remote I / O modules can execute their own preset control logic, including preset complex process control logic and configurations of linkage rules issued by the IoT cloud server. This application can enhance the security and reliability of the IO module in system applications, and has the function of autonomous diagnosis, exception handling and problem feedback, thereby improving the robustness of system applications.

[0085] The specific embodiments of the present invention have been described in detail above, but they are merely examples, and the present invention is not limited to the specific embodiments described above. For those skilled in the art, any equivalent modifications and substitutions to the present invention are also within the scope of the present invention. Therefore, all equivalent transformations and modifications made without departing from the spirit and scope of the present invention should be covered within the scope of the present invention.

Claims

1. A control method for an Internet of Things (IoT) remote I / O system, characterized in that, include: Construct an IoT remote I / O system comprising a third-party master station, one or more remote I / O modules, and an IoT cloud server. Each remote I / O module acts as a client, establishing a real-time communication connection with the IoT cloud server via the Ethernet TCP / IP communication protocol to report data and receive and store configuration requests for linkage rules sent by the IoT cloud server. Simultaneously, each remote I / O module acts as a slave station, establishing a communication connection with the third-party master station via a fieldbus and autonomously selecting its operating mode based on the fieldbus connection status. Each of the remote I / O modules is configured with multiple states: standby, offline, and online, and the remote I / O module switches between these states: When the system is powered on, the remote I / O module enters standby mode; Upon receiving a registration response message from the IoT cloud server, the remote IO module changes from its standby state before initiating registration to its offline state. When the communication between the remote IO module and the third-party master station is normal, the remote IO module switches from offline to online and enters the controlled working mode. In the controlled working mode, the remote IO module sends the sensor data sampled on site to the third-party master station and receives and executes the control commands sent by the third-party master station. When communication between the remote IO module and the third-party master station is abnormal, the remote IO module switches from online to offline and enters the automatic control mode. In the automatic control mode, the remote IO module runs the preset process control logic or executes the linkage control operation corresponding to the linkage rules configured by the IoT cloud server. Each of the remote I / O modules is also configured with an abnormal state, including an offline abnormal state and an online abnormal state. In both online and offline states, the remote I / O module periodically or in real-time detects the event triggering conditions of the linkage rules configured on the IoT cloud server. When the current state of the remote I / O module is online, if the abnormal event triggering condition corresponding to a certain abnormal event parameter is detected to be triggered, the remote I / O module switches its current state from online to online abnormal state. When the current state of the remote I / O module is offline, if the abnormal event triggering condition corresponding to a certain abnormal event parameter is detected to be triggered, the remote I / O module switches its current state from offline to offline abnormal state. When the current state of the remote IO module is an online abnormal state, if the control command of the third-party master station conflicts with the linkage control operation triggered by the linkage rules configured in the IoT cloud server, the linkage control operation shall be executed first.

2. The control method for an IoT remote I / O system according to claim 1, characterized in that, Each of the remote I / O modules stores multiple linkage rule information configured by the IoT cloud server in its on-chip flash memory. Each linkage rule includes a rule number, rule type, delay judgment duration, event triggering condition, execution object, and response action; among which, The rule types include alarms and anomalies; The delay judgment duration is used as the starting condition for the linkage control operation. That is, after the event triggering condition is met for the first time, the delay preset time is used for judgment again. If the event triggering condition is triggered again, it is considered that the event has occurred and the linkage control operation is executed. The event triggering conditions include the range of parameters for event triggering.

3. The control method for an IoT remote I / O system according to claim 2, characterized in that, The linkage rules include single-condition triggering rules and multi-condition triggering rules; wherein, the single-condition triggering rule is: when a certain event triggering condition is met, one or more response actions corresponding to the event triggering condition are executed; the multi-condition triggering rule is: when two or more event triggering conditions are met at the same time, one or more response actions are executed.

4. The control method for an IoT remote I / O system according to claim 1, characterized in that, When the remote I / O module is in an online abnormal state, it executes a corresponding linkage control operation; if the abnormal situation is eliminated after the linkage control operation is executed, the remote I / O module returns the current state from the online abnormal state to the online state. When the remote I / O module is in an offline abnormal state, it performs corresponding linkage control operations; If the abnormal situation is eliminated after the linkage control operation is performed, the remote IO module will return the current state from the offline abnormal state to the offline state.

5. The control method for an IoT remote I / O system according to claim 4, characterized in that, The control method further includes: When the current state of the remote IO module is offline, if the communication between the remote IO module and the third-party master station is restored to normal, the remote IO module will switch from offline to online. When the current state of the remote IO module is online, if the communication between the remote IO module and the third-party master station is abnormal, the remote IO module will switch from online to offline. When the current state of the remote I / O module is offline and the abnormal situation has not been resolved, if communication between the remote I / O module and the third-party master station returns to normal, the remote I / O module will switch from offline to online abnormal state; and When the current state of the remote IO module is an online abnormal state and the abnormal situation has not been eliminated, if the communication between the remote IO module and the third-party master station is abnormal, the remote IO module will switch from the online abnormal state to the offline abnormal state.

6. The control method for an IoT remote I / O system according to claim 1, characterized in that, The preset process control logic is a customized control logic, which is a binary program code customized and developed according to the process requirements of the customer's site. The binary program code is pre-burned into the on-chip flash of the remote IO module.

7. The control method for an IoT remote I / O system according to claim 6, characterized in that, The executable file size of the preset process control logic does not exceed 16K.

8. The control method for an IoT remote I / O system according to claim 1, characterized in that, During communication with the IoT server, each of the remote I / O modules reports data including sensor data sampled on-site, operating status machine, total device operating time, device operating events, and control enable duration of device digital outputs.

9. The control method for an IoT remote I / O system according to claim 1, characterized in that, Each of the remote I / O modules also includes an SDIO controller, which can recognize the storage area of ​​the card to store events, sensor sampling data, actuator execution data and state switching information during the operation of the remote I / O module, so as to realize real-time storage and backup of operation data and operation logs.

Images