WO2022267358A1 - 一种零代码配置的工业设备数据采集系统 - Google Patents

一种零代码配置的工业设备数据采集系统 Download PDF

Info

Publication number
WO2022267358A1
WO2022267358A1 PCT/CN2021/135761 CN2021135761W WO2022267358A1 WO 2022267358 A1 WO2022267358 A1 WO 2022267358A1 CN 2021135761 W CN2021135761 W CN 2021135761W WO 2022267358 A1 WO2022267358 A1 WO 2022267358A1
Authority
WO
WIPO (PCT)
Prior art keywords
collection
rules
hardware
configuration
data
Prior art date
Application number
PCT/CN2021/135761
Other languages
English (en)
French (fr)
Inventor
魏娇娇
冯健
翁俊杰
刘言聪
孙玉辰
牟卫洋
孙金虎
朱濬
厉暘
Original Assignee
昆山罗亿智能科技有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 昆山罗亿智能科技有限公司 filed Critical 昆山罗亿智能科技有限公司
Publication of WO2022267358A1 publication Critical patent/WO2022267358A1/zh

Links

Images

Classifications

    • G—PHYSICS
    • G05—CONTROLLING; REGULATING
    • G05B—CONTROL OR REGULATING SYSTEMS IN GENERAL; FUNCTIONAL ELEMENTS OF SUCH SYSTEMS; MONITORING OR TESTING ARRANGEMENTS FOR SUCH SYSTEMS OR ELEMENTS
    • G05B19/00—Programme-control systems
    • G05B19/02—Programme-control systems electric
    • G05B19/418—Total factory control, i.e. centrally controlling a plurality of machines, e.g. direct or distributed numerical control [DNC], flexible manufacturing systems [FMS], integrated manufacturing systems [IMS] or computer integrated manufacturing [CIM]
    • G05B19/4183—Total factory control, i.e. centrally controlling a plurality of machines, e.g. direct or distributed numerical control [DNC], flexible manufacturing systems [FMS], integrated manufacturing systems [IMS] or computer integrated manufacturing [CIM] characterised by data acquisition, e.g. workpiece identification
    • G—PHYSICS
    • G05—CONTROLLING; REGULATING
    • G05B—CONTROL OR REGULATING SYSTEMS IN GENERAL; FUNCTIONAL ELEMENTS OF SUCH SYSTEMS; MONITORING OR TESTING ARRANGEMENTS FOR SUCH SYSTEMS OR ELEMENTS
    • G05B2219/00—Program-control systems
    • G05B2219/30—Nc systems
    • G05B2219/31—From computer integrated manufacturing till monitoring
    • G05B2219/31282—Data acquisition, BDE MDE
    • Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
    • Y02P—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN THE PRODUCTION OR PROCESSING OF GOODS
    • Y02P90/00—Enabling technologies with a potential contribution to greenhouse gas [GHG] emissions mitigation
    • Y02P90/02—Total factory control, e.g. smart factories, flexible manufacturing systems [FMS] or integrated manufacturing systems [IMS]

Definitions

  • the invention relates to the technical field of data acquisition, in particular to an industrial equipment data acquisition system with zero-code configuration.
  • Fragmentation of industrial equipment is serious. Specifically reflected in: 1. There are various types of industrial equipment, such as CNC, PLC, robots, sensors, etc.; there are many types of industrial equipment brands, such as Siemens, Fanuc, ABB, Schneider, etc.; various communication protocols used by industrial equipment, such as Modbus , OPC-UA, ProfiBus, EtherCat, etc. 2. The requirements for data collection of industrial equipment are different. Unlike home appliances, there are usually only simple operations such as switches.
  • the purpose of the present invention is to provide a zero-code configuration industrial equipment data collection system to solve the problem of low data collection efficiency in the prior art.
  • An industrial equipment data acquisition system with zero code configuration including a software end and a hardware end, the software end is used to model the external functions of the hardware end and standardize the model attributes of the hardware end;
  • the software end is used to collect configuration rules for the hardware end, and store the collection configuration rules through the JSON specification;
  • the software end is used to establish collection template rules for the hardware end;
  • the software end sends the collection template rules and set configuration rules to the application gateway to implement data collection on the hardware end.
  • the hardware end receives the collection template rules and set configuration rules issued by the software end through the application gateway, and performs storage data collection configuration on the received rules;
  • the hardware end configures the data reporting, and uploads the data reporting configuration to the software end through the application gateway.
  • the hardware end includes a general data processing framework, and the general data processing framework is used for reading application configuration files.
  • specification hardware model attributes include attribute name, value range, value unit, data type, and read/write type;
  • the numerical range includes a maximum value and a minimum value
  • the data type includes a positive attribute, a floating point type, a Boolean type, and a text type
  • the read-write type includes a read-only attribute, a write-only attribute, and a read-write attribute.
  • the collection configuration rules include collection time period, hardware interface used for collection, software communication protocol, details of software protocol rules and how to process the original collection data.
  • the software end sends the collection template rules and set configuration rules to the application gateway, including the pending status, execution status, success status and failure status.
  • collection configuration rules include general collection rules and communication protocol rules
  • the general collection rules include a collection cycle, a collection hardware interface type, a collection protocol and a collection data processing method;
  • the communication protocol rules include slave address, operation type, register address and original data type.
  • embodiments of the present invention at least have the following effects:
  • the present invention realizes data collection on the hardware end by establishing collection template rules and set configuration rules, and sends the collection rules to the application gateway, and the data collection efficiency is improved by nearly 90%; traditional programming to realize data collection involves many processes and It is error-prone, and it takes 5 hours to realize the data collection of an ordinary ModbusRTU protocol device, but this application only takes about 30 minutes to complete, saving nearly 90% of the time;
  • This application has high flexibility, for example, it can support very complex protocols or perform some customized device logic, covering 70-80% of the scenarios;
  • the acquisition system of this application supports more than 90% of the interface and protocol types in the market. Common hardware interfaces are supported, such as 485, 232, EtherNet, DI/AI, etc., and communication protocols support ModbusRTU/TCP, OPC-UA, ProfiNet, ProfiBus, etc.
  • Fig. 1 is a schematic diagram of the user interface of the attribute list in the specific embodiment of the present invention.
  • Fig. 2 is a schematic diagram of the user interface of attribute definition in the specific embodiment of the present invention.
  • Fig. 3 is a schematic diagram of the user interface of the acquisition configuration list in the specific embodiment of the present invention.
  • Fig. 4 is a schematic diagram of a user interface for collecting configuration details in a specific embodiment of the present invention.
  • Fig. 5 is a schematic diagram of the user interface of the acquisition configuration template in the specific embodiment of the present invention.
  • the general collection rules are separated from the specific communication protocol rules, providing a unified style configuration method, and can dynamically expand different types of protocols.
  • the general collection rules include collection period (or frequency), which hardware interface to use for collection, which software protocol to use for collection, and how to process the collected raw data (basic operations such as addition, subtraction, multiplication and division, and retention of decimal places).
  • the communication protocol rules will be different according to different protocols. Taking the mainstream Modbus protocol as an example, the details of the rules that need to be determined include slave address, operation type (function code), register address, and original data type. By separating the two, it can provide users with a unified style of configuration and interface. At the same time, because the specific communication protocol is separated, it can be used as a plug-in mechanism to realize the dynamic expansion of the protocol.
  • the collection template is separated from the specific collection configuration, which can not only realize the multiplexing of multiple devices, but also realize the customization of individual devices.
  • the device attribute set is the object of gateway data collection and configuration. With the general device attribute set, we abstract it into the concept of device model. On this basis, we expand the concept of collection template, which is aimed at specific device models and gateways (such as The collection templates of A device model and B model gateway can be reused on all A devices and B gateways). With the concept of collection templates, it can be applied to gateways in batches as collection configurations. At the same time, the collection configurations of each gateway can be configured and modified independently without affecting the collection configurations and collection templates of other gateways of the same category, realizing customization and specialization deal with.
  • a zero-code configuration industrial equipment data acquisition system includes a software end and a hardware end.
  • the software end is used to model the external functions of the hardware end and standardize the attributes of the hardware end model; when the hardware end model After the attribute specification is completed, the software end is used to collect configuration rules on the hardware end, and the collection configuration rules are stored through the JSON specification; when the hardware end model attribute specification is completed and the collection configuration rules are completed, the software end is used to collect templates on the hardware end Establishment of rules; when the collection template rules are established, the software side sends the collection template rules and set configuration rules to the application gateway to realize data collection on the hardware side.
  • the present invention realizes data collection on the hardware end by establishing collection template rules and set configuration rules, and sends the collection rules to the application gateway, and the data collection efficiency is improved by nearly 90%; traditional programming to realize data collection involves many processes and is error-prone , It takes 5 hours to realize the data acquisition of a common ModbusRTU protocol device, but this application only needs about 30 minutes to complete, saving nearly 90% of the time.
  • This application is divided into two parts: the software side and the hardware side, and the software side is divided into five parts: device model definition, device definition, collection configuration rules, collection template rules, and remote update (OTA); the hardware side is divided into application configuration There are three parts: files, general data processing framework and back-end communication protocol.
  • a device may be a hardware end or a related device connected to the hardware end.
  • the device model is the modeling of the external functions of the device, which is common to all devices under the device model, and the device model specification specifically refers to the device attributes.
  • the elements of device attributes can be divided into attribute name, value range (minimum value, maximum value), value unit, data type (positive attribute, floating point type, Boolean type, text type), read-write type (read-only attribute, write-only attribute, read-write attribute).
  • Device models are stored via the JSON specification.
  • the device concept here refers to the IoT device (with networking function and capable of reporting some device attribute data). It is usually composed of gateway hardware and traditional stand-alone equipment.
  • the collection configuration rule is specifically: the collection configuration rule is based on the attributes of the device model.
  • the device attribute describes the external characteristics of the attribute (name, scope, type, etc.), and the collection configuration rules describe how it is collected and implemented, specifically referring to the collection time period, the hardware interface used for collection, the software communication protocol, and the details of the software protocol rules (different Protocols are different), and how to process the original collected data (how to calculate, keep several decimal places, etc.).
  • the collection configuration will be stored through the JSON specification and converted into a format that is easy to read and process on the device side.
  • the collection template rule is specifically: the collection template rule is established on both the device model and the collection configuration, and describes which device attributes exist, how to collect these attributes, and which gateway model to use for collection. Collection templates can be applied to multiple gateways in batches, and can also be generated by exporting collection configuration rules.
  • the remote update is specifically: after the collection configuration and collection template rules are configured, they need to be delivered to the designated gateway or applied to the gateway in batches. At this time, the software platform needs to provide an OTA channel to realize the remote delivery of data. To ensure a good user experience, when the device is offline, the OTA task can also be triggered normally, but because the device is offline and in the suspended state, it will automatically synchronize when the device is online. The status of the OTA task has four statuses: pending, executing, successful and failed.
  • the application configuration file can be: the application configuration file stores data collection configuration and data reporting configuration, and the specific elements are hardware interface instance, hardware interface parameters, collection time period, specific protocol rules (different for each protocol), data reporting address, and reporting address connection Parameters, etc. (like connection strings).
  • the general data processing framework can be: the general data processing framework implements general data collection and responds to issued commands, it reads the application configuration file, and relies on the back-end communication protocol (built-in in the gateway APP), implements the data collection strategy by starting the cycle, and implements the data collection strategy through The queue mechanism realizes batch data acquisition processing or command response.
  • the back-end communication protocol can be implemented according to the interface of the general data processing framework, and completes core operations such as protocol package and unpack.

Landscapes

  • Engineering & Computer Science (AREA)
  • General Engineering & Computer Science (AREA)
  • Manufacturing & Machinery (AREA)
  • Quality & Reliability (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Automation & Control Theory (AREA)
  • Computer And Data Communications (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

一种零代码配置的工业设备数据采集系统，包括软件端和硬件端，软件端用于对硬件端的外部功能建模并规范硬件端模型属性；当硬件端模型属性规范完成，软件端用于对硬件端进行采集配置规则，并将采集配置规则通过JSON规范存储；当硬件端模型属性规范完成及采集配置规则完成后，软件端用于对硬件端进行采集模板规则的建立；当采集模板规则建立后，软件端将采集模板规则和采集配置规则下发至应用网关实现对硬件端的数据采集。通过建立采集模板规则和采集配置规则，并将采集的规则下发至应用网关实现对硬件端的数据采集。

Description

一种零代码配置的工业设备数据采集系统 技术领域
本发明涉及数据采集技术领域，具体涉及一种零代码配置的工业设备数据采集系统。
背景技术
工业物联网行业发展重要基础，是实现传统单机工业设备的联网与数据接入，但这个环节确实行业痛点与难点，具体表现在以下三点：
工业设备的碎片化十分严重。具体体现在：1.工业设备种类繁杂，如CNC、PLC、机器人、传感器等等；工业设备品牌种类丰富，如西门子、法那科、ABB、施耐德等；工业设备采用的通讯协议多样，如Modbus、OPC-UA、ProfiBus、EtherCat等。2.工业设备数据采集的需求不同。不同于家电类设备，通常只有开关等简单的操作。工业设备由于涉及到生产加工等环节，很多种类都是可以自编程的(像CNC、PLC、机器人等)，因此数据采集的需求就会不同，体现在要进行哪些数据的采集、根据什么频率采集、数据的读写类型是什么(只读、只写、读写)、采集的到的原始数据要做怎样的初步处理。3.工业设备数据采集困难。正因为以上两点，因此数据采集十分困难，通常都需要利用专业的网关设备，通过嵌入式工程师实现编程实现，具体实施流程很长，包括调研分析协议、PC端模拟、设备固件开发、烧录与测试等多个环节。
发明内容
本发明的目的在于提供一种零代码配置的工业设备数据采集系统，以解决现有技术中导致的数据采集效率低的问题。
为达到上述目的，本发明是采用下述技术方案实现的：
一种零代码配置的工业设备数据采集系统，包括软件端和硬件端，所述软件端用于对硬件端的外部功能建模并规范硬件端模型属性；
当所述硬件端模型属性规范完成，所述软件端用于对硬件端进行采集配置规则，并将所述采集配置规则通过JSON规范存储；
当所述硬件端模型属性规范完成及采集配置规则完成后，所述软件端用于对硬件端进行采集模板规则的建立；
当所述采集模板规则建立后，所述软件端将采集模板规则和集配置规则下发至应用网关实现对硬件端的数据采集。
进一步地，所述硬件端通过应用网关接收软件端下发的采集模板规则和集配置规则，并对接收的规则进行存储数据采集配置；
所述硬件端对数据上报配置，并将数据上报配置通过应用网关上传至软件端。
进一步地，所述硬件端包括通用数据处理框架，所述通用数据处理框架用于读取应用配置文件。
进一步地，所述规范硬件端模型属性包括属性名称、数值范围、数值单位、数据类型、和读写类型；
其中，所述数值范围包括最大值和最小值；所述数据类型包括正属性、浮点型、布尔型和文本型；所述读写类型包括只读属性、只写属性和读写属性。
进一步地，所述采集配置规则包括采集时间周期、采集所用的硬件接口、软件通信协议、软件协议规则细节以及原始采集数据如何处理。
进一步地，所述软件端将采集模板规则和集配置规则下发至应用网关包括挂起状态、执行状态、成功状态和失败状态。
进一步地，所述采集配置规则包括通用采集规则和通讯协议规则；
所述通用采集规则包括采集周期，采集所使用硬件接口类型，采集协议和采集数据处理方式；
所述通讯协议规则包括从机地址、操作类型、寄存器地址和原始数据类型。
根据上述技术方案，本发明的实施例至少具有以下效果：
1、本发明通过建立采集模板规则和集配置规则，并将采集的规则下发至应用网关实现对硬件端的数据采集，数据采集效率提升近90％；传统编程实现数据采集，涉及的流程多且易出错，实现一个普通ModbusRTU协议设备的数据采集要用5小时，而本申请只需30分钟左右即可完成，节约近90％的时间；
2、本申请灵活性高，比如可支持非常复杂的协议或进行一些定制化的设备逻辑，覆盖的场景已达70-80％；
3、本申请的采集系统支持市场90％+的接口和协议种类。常见硬件接口均支持，如485、232、EtherNet、DI/AI等，通讯协议支持ModbusRTU/TCP、OPC-UA、ProfiNet、ProfiBus等。
附图说明
图1为本发明具体实施方式中属性列表的使用界面示意图；
图2为本发明具体实施方式中属性定义的使用界面示意图；
图3为本发明具体实施方式中采集配置列表的使用界面示意图；
图4为本发明具体实施方式中采集配置详情的使用界面示意图；
图5为本发明具体实施方式中采集配置模板的使用界面示意图。
具体实施方式
为使本发明实现的技术手段、创作特征、达成目的与功效易于明白了解，下 面结合具体实施方式，进一步阐述本发明。
传统的解决方案开发门槛高，实现周期长，因此本专利提供一种零代码UI配置的方式实现工业设备数据采集，解决的技术问题包括以下三点的至少一点：
1.通用采集规则和具体通讯协议规则分离，提供统一风格配置方式，又可动态扩展不同种类协议。实现数据采集的过程中，可分解成为两种要素，一种是通用的采集规则(所有数采过程都需要的)，一种是特定的通讯协议(每个协议要求填写的规则都不同)。通用采集规则包括采集周期(或频率)，采集使用何种硬件接口，采集使用何种软件协议，如何对采集的原始数据做处理(加减乘除、保留小数位数等基本操作)。而通讯协议规则根据不同协议会不同，就主流的Modbus协议举例，需要确定的规则细节有，从机地址、操作类型(功能码)、寄存器地址、原始数据类型等。通过两者分离，可向用户提供统一风格的配置方式和界面，同时正因为将具体的通讯协议分离出来，可作为一种插件机制，实现协议的动态扩展。
2.根据所使用的网关动态加载其所支持的硬件接口和软件协议。不同的网关硬件产品所支持的采集接口和软件协议是不同的，因此在我们软件平台上，会根据用户当前所使用的硬件网关产品，自动加载出硬件接口列表和软件协议。
3.采集模版与具体的采集配置分离，既可实现多设备复用，又可实现单独设备定制化。设备属性集合是网关数据采集配置的对象，拥有通用设备属性集合我们抽象为设备模型的概念，在此基础上拓展了采集模版的概念，它是针对于具体的设备模型和网关而言的(比如A设备模型和B型号的网关的采集模版，可以复用在所有A设备和B网关上面)。有了采集模版的概念，就可以批量应用到网关上作为采集配置，同时每个网关的采集配置可单独配置修改，不影响同类别其 它的网关的采集配置和采集模版，实现定制化特殊化的处理。
如图1至图5所示，一种零代码配置的工业设备数据采集系统，包括软件端和硬件端，软件端用于对硬件端的外部功能建模并规范硬件端模型属性；当硬件端模型属性规范完成，软件端用于对硬件端进行采集配置规则，并将采集配置规则通过JSON规范存储；当硬件端模型属性规范完成及采集配置规则完成后，软件端用于对硬件端进行采集模板规则的建立；当采集模板规则建立后，软件端将采集模板规则和集配置规则下发至应用网关实现对硬件端的数据采集。
本发明通过建立采集模板规则和集配置规则，并将采集的规则下发至应用网关实现对硬件端的数据采集，数据采集效率提升近90％；传统编程实现数据采集，涉及的流程多且易出错，实现一个普通ModbusRTU协议设备的数据采集要用5小时，而本申请只需30分钟左右即可完成，节约近90％的时间。
本申请总共分为软件端和硬件端两大部分，而软件端又分为设备模型定义、设备定义、采集配置规则、采集模版规则和远程更新(OTA)五个部分；硬件端分为应用配置文件、通用数据处理框架和后端通信协议等三个部分。
设备可以是硬件端或与硬件端相连接的相关设备。
设备模型定义具体为：设备模型是对设备外部功能的建模，它是该设备模型下所有设备都共有的，设备模型规范具体是指设备属性。设备属性的要素可分为属性名称、数值范围(最小值、最大值)、数值单位、数据类型(正属性、浮点型、布尔型、文本型)、读写类型(只读属性、只写属性、读写属性)。设备模型会通过JSON规范进行存储。
设备定义具体位置：这里的设备概念指的的IoT设备(具备联网功能，且能上报若干设备属性数据)。它通常是由网关硬件和传统单机设备共同组成。
采集配置规则具体为：采集配置规则是建立在设备模型属性的基础上的。设备属性描述该属性的外部特征(名称、范围、类型等)，而采集配置规则描述它具体如何采集实现，具体指采集时间周期、采集所用的硬件接口、软件通信协议、软件协议规则细节(不同协议不同)、以及原始采集数据如何处理(怎么运算，保留几位小数等)。采集配置会通过JSON规范进行存储，同时转换为设备端易于读取且处理的格式。
采集模版规则具体为：采集模版规则建立在设备模型和采集配置两者之上，描述有哪些设备属性，这些属性如何做采集，且用哪个网关型号做采集。采集模版可批量应用到多个网关上，也可有采集配置规则导出生成。
远程更新具体为：采集配置和采集模版规则在配置好后，需要下发给指定网关或批量应用在网关上，这时就需要软件平台提供OTA的通道，实现数据的远程下发功能，同时为保证良好的用户体验，在设备离线状态下，OTA任务也能正常触发只不过由于设备离线处于挂起状态，当设备上线后会自动同步。OTA任务的状态有挂起、执行、成功和失败四种状态。
应用配置文件可以是：应用配置文件存储数据采集配置和数据上报配置，具体要素为硬件接口实例、硬件接口参数、采集时间周期、具体协议规则(每个协议不同)、数据上报地址、上报地址连接参数等(如连接字符串)。
通用数据处理框架可以是：通用数据处理框架实现通用数据采集和响应下发命令，它读取应用配置文件，并依赖于后端通信协议(网关APP内置)，通过启动循环实现数据采集策略，通过队列机制实现批量数采处理或命令响应。
后端通信协议可以是后端通信协议按照通用数据处理框架的接口进行实现，完成协议组包解包等核心操作。
由技术常识可知，本发明可以通过其它的不脱离其精神实质或必要特征的实施方案来实现。因此，上述公开的实施方案，就各方面而言，都只是举例说明，并不是仅有的。所有在本发明范围内或在等同于本发明的范围内的改变均被本发明包含。

Claims (7)

  1. 一种零代码配置的工业设备数据采集系统，其特征在于，包括软件端和硬件端，所述软件端用于对硬件端的外部功能建模并规范硬件端模型属性；
    当所述硬件端模型属性规范完成，所述软件端用于对硬件端进行采集配置规则，并将所述采集配置规则通过JSON规范存储；
    当所述硬件端模型属性规范完成及采集配置规则完成后，所述软件端用于对硬件端进行采集模板规则的建立；
    当所述采集模板规则建立后，所述软件端将采集模板规则和集配置规则下发至应用网关实现对硬件端的数据采集。
  2. 根据权利要求1所述的零代码配置的工业设备数据采集系统，其特征在于，所述硬件端通过应用网关接收软件端下发的采集模板规则和集配置规则，并对接收的规则进行存储数据采集配置；
    所述硬件端对数据上报配置，并将数据上报配置通过应用网关上传至软件端。
  3. 根据权利要求1所述的零代码配置的工业设备数据采集系统，其特征在于，所述硬件端包括通用数据处理框架，所述通用数据处理框架用于读取应用配置文件。
  4. 根据权利要求1所述的零代码配置的工业设备数据采集系统，其特征在于，所述规范硬件端模型属性包括属性名称、数值范围、数值单位、数据类型、和读写类型；
    其中，所述数值范围包括最大值和最小值；所述数据类型包括正属性、浮点型、布尔型和文本型；所述读写类型包括只读属性、只写属性和读写属性。
  5. 根据权利要求1所述的零代码配置的工业设备数据采集系统，其特征在于， 所述采集配置规则包括采集时间周期、采集所用的硬件接口、软件通信协议、软件协议规则细节以及原始采集数据如何处理。
  6. 根据权利要求1所述的零代码配置的工业设备数据采集系统，其特征在于，所述软件端将采集模板规则和集配置规则下发至应用网关包括挂起状态、执行状态、成功状态和失败状态。
  7. 根据权利要求1所述的零代码配置的工业设备数据采集系统，其特征在于，所述采集配置规则包括通用采集规则和通讯协议规则；
    所述通用采集规则包括采集周期，采集所使用硬件接口类型，采集协议和采集数据处理方式；
    所述通讯协议规则包括从机地址、操作类型、寄存器地址和原始数据类型。
PCT/CN2021/135761 2021-06-24 2021-12-06 一种零代码配置的工业设备数据采集系统 WO2022267358A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202110706725.2A CN113341900A (zh) 2021-06-24 2021-06-24 一种零代码配置的工业设备数据采集系统
CN202110706725.2 2021-06-24

Publications (1)

Publication Number Publication Date
WO2022267358A1 true WO2022267358A1 (zh) 2022-12-29

Family

ID=77478770

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2021/135761 WO2022267358A1 (zh) 2021-06-24 2021-12-06 一种零代码配置的工业设备数据采集系统

Country Status (2)

Country Link
CN (1) CN113341900A (zh)
WO (1) WO2022267358A1 (zh)

Families Citing this family (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113341900A (zh) * 2021-06-24 2021-09-03 昆山罗亿智能科技有限公司 一种零代码配置的工业设备数据采集系统
CN114244740B (zh) * 2021-12-22 2024-02-27 唯品会(广州)软件有限公司 一种网络数据采集方法及系统
CN114793191A (zh) * 2022-02-17 2022-07-26 江苏卓易信息科技股份有限公司 一种基于领域模型的物联网集成系统及方法
CN114546528A (zh) * 2022-02-24 2022-05-27 新奥数能科技有限公司 一种物联网设备的云端部署方法、装置及存储介质

Citations (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5974257A (en) * 1997-07-10 1999-10-26 National Instruments Corporation Data acquisition system with collection of hardware information for identifying hardware constraints during program development
CN107643932A (zh) * 2017-08-31 2018-01-30 深圳天珑无线科技有限公司 一种数据采集方法、采集装置以及存储装置
CN107992291A (zh) * 2017-11-16 2018-05-04 上海南潮信息科技有限公司 应用于嵌入式应用程序的Ruff OS物联网操作系统
CN109143940A (zh) * 2018-10-16 2019-01-04 苏州琅润达检测科技有限公司 一种通用数据采集装置
CN111651482A (zh) * 2020-04-16 2020-09-11 宁波吉利汽车研究开发有限公司 一种数据采集方法和装置
CN112688865A (zh) * 2020-12-10 2021-04-20 西安理工大学 一种图形化在线建模的opc ua网关的设计方法
CN113341900A (zh) * 2021-06-24 2021-09-03 昆山罗亿智能科技有限公司 一种零代码配置的工业设备数据采集系统

Family Cites Families (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106685815A (zh) * 2017-01-04 2017-05-17 上海建坤信息技术有限责任公司 一种多协议硬件采集网关系统
CN109873820A (zh) * 2019-02-21 2019-06-11 温瑭玮 一种可自定义数据传输协议的数据采集及执行方法
CN110995846A (zh) * 2019-12-10 2020-04-10 北京数知科技股份有限公司 物联网采集数据处理装置、方法及系统
CN112671637A (zh) * 2020-12-29 2021-04-16 南京衍构科技有限公司 一种支持多工业协议的数据采集网关系统和方法
CN112822171A (zh) * 2020-12-30 2021-05-18 南京南瑞继保电气有限公司 一种基于物联网协议的前置采集系统及方法

Patent Citations (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5974257A (en) * 1997-07-10 1999-10-26 National Instruments Corporation Data acquisition system with collection of hardware information for identifying hardware constraints during program development
CN107643932A (zh) * 2017-08-31 2018-01-30 深圳天珑无线科技有限公司 一种数据采集方法、采集装置以及存储装置
CN107992291A (zh) * 2017-11-16 2018-05-04 上海南潮信息科技有限公司 应用于嵌入式应用程序的Ruff OS物联网操作系统
CN109143940A (zh) * 2018-10-16 2019-01-04 苏州琅润达检测科技有限公司 一种通用数据采集装置
CN111651482A (zh) * 2020-04-16 2020-09-11 宁波吉利汽车研究开发有限公司 一种数据采集方法和装置
CN112688865A (zh) * 2020-12-10 2021-04-20 西安理工大学 一种图形化在线建模的opc ua网关的设计方法
CN113341900A (zh) * 2021-06-24 2021-09-03 昆山罗亿智能科技有限公司 一种零代码配置的工业设备数据采集系统

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
WEIXIN_39089033: " Nanchao IoT Brings Zero-Code Device Management Platform to Baidu Cloud Intelligence Summit", BLOG.CSDN.NET, 8 June 2021 (2021-06-08), pages 1 - 7, XP093016678, Retrieved from the Internet <URL:https://blog.csdn.net/weixin_39089033/article/details/117695789> [retrieved on 20230123] *

Also Published As

Publication number Publication date
CN113341900A (zh) 2021-09-03

Similar Documents

Publication Publication Date Title
WO2022267358A1 (zh) 一种零代码配置的工业设备数据采集系统
US7747416B2 (en) System and method for batch process control with diverse distributed control system protocols
US11385613B2 (en) Process image within controllers enabling visibility and accessibility of real world objects
EP2738632B1 (en) Input output cloning for industrial automation
EP2866108A1 (en) Control device
CN111555922A (zh) 物联网设备主动适配接入的方法、装置、设备及存储介质
WO2015034458A1 (en) Systems and methods for virtualizing a programmable logic controller
EP3758333B1 (en) Method for configuring an industrial automation system
CN111638690A (zh) 基于通用信息模型的数据采集方法、装置、系统和设备
WO2018179125A1 (ja) ネットワーク構成情報生成方法および通信機器
US11165745B2 (en) Control system, controller, and control method
Müller Using S-BPM for PLC code generation and extension of subject-oriented methodology to all layers of modern control systems
Elamanov et al. Interworking between Modbus and internet of things platform for industrial services
JPWO2008146477A1 (ja) 通信機能を有するｐｌｃ
WO2018174867A1 (en) Universal data access across devices
CN115826492A (zh) 通用的plc数据处理方法及装置
TW201944341A (zh) 資料處理裝置、資料處理方法及程式
CN114268650A (zh) 用于建立通信连接的配置方法及系统
JP2018010389A (ja) 制御アプリケーション生成支援装置、及び制御アプリケーション生成支援方法
WO2020166026A1 (ja) 管理装置、管理システム、管理方法及びプログラム
US9892011B2 (en) Apparatus and method for autodetection of HART devices over PROFIBUS
JP2019045900A (ja) 設定装置、ｆａシステム、制御プログラム、および設定装置の制御方法
US20230247115A1 (en) Protocol driver creating device
JP2018067191A (ja) プラント制御システム
EP4300295A1 (en) Method and apparatus for executing workflow task across control objects

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 21946834

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 21946834

Country of ref document: EP

Kind code of ref document: A1