WO2019132095A1 - Interface apparatus and method of converting communication protocol - Google Patents

Interface apparatus and method of converting communication protocol Download PDF

Info

Publication number
WO2019132095A1
WO2019132095A1 PCT/KR2018/000780 KR2018000780W WO2019132095A1 WO 2019132095 A1 WO2019132095 A1 WO 2019132095A1 KR 2018000780 W KR2018000780 W KR 2018000780W WO 2019132095 A1 WO2019132095 A1 WO 2019132095A1
Authority
WO
WIPO (PCT)
Prior art keywords
data
interface apparatus
peripheral device
plc
information
Prior art date
Application number
PCT/KR2018/000780
Other languages
English (en)
French (fr)
Inventor
Sang Hun Lee
Original Assignee
Htcsystem Co.,Ltd
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 Htcsystem Co.,Ltd filed Critical Htcsystem Co.,Ltd
Publication of WO2019132095A1 publication Critical patent/WO2019132095A1/en

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/08—Protocols for interworking; Protocol conversion
    • H04L69/085—Protocols for interworking; Protocol conversion specially adapted for interworking of IP-based networks with other networks
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/12—Protocols specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks
    • 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/04—Programme control other than numerical control, i.e. in sequence controllers or logic controllers
    • G05B19/05—Programmable logic controllers, e.g. simulating logic interconnections of signals according to ladder diagrams or function charts
    • G05B19/054—Input/output
    • 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/4185—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 the network communication
    • G05B19/4186—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 the network communication by protocol, e.g. MAP, TOP
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/08—Protocols for interworking; Protocol conversion
    • 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/10—Plc systems
    • G05B2219/15—Plc structure of the system
    • G05B2219/15028—Controller and device have several formats and protocols, select common one
    • 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/20—Pc systems
    • G05B2219/25—Pc structure of the system
    • G05B2219/25204—Translate between different communication protocols
    • 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/20—Pc systems
    • G05B2219/25—Pc structure of the system
    • G05B2219/25217—Configure communication protocol, select between several

Definitions

  • One or more embodiments relate to communication apparatuses, and more particularly, to communication interface apparatuses and interface methods.
  • an industrial controller such as a programmable logic controller (PLC) or a DDC is used to efficiently control various industrial facilities installed in the industrial field.
  • PLC programmable logic controller
  • DDC digital converter
  • a protocol should be provided to integrally control various signals used in each device.
  • One or more embodiments include communication interface apparatuses capable of automatically converting a protocol for communication between devices using different protocols, and interface methods using the same.
  • FIG. 1 is a block diagram illustrating a configuration of an interface apparatus for converting a communication protocol, according to an embodiment
  • FIG. 2 is a flowchart illustrating a communication interface method of converting a communication protocol, according to an embodiment
  • FIG. 3 is a diagram illustrating an example of converting a protocol of information received from a PLC and transmitting the same to a peripheral device, according to an embodiment
  • FIG. 4 is a diagram illustrating an example of extracting information from data received from a peripheral device and transmitting the same to a PLC, according to an embodiment
  • FIG. 5 is a flowchart illustrating a method of generating a protocol through a user setting input when there is no protocol in an interface apparatus, according to an embodiment
  • FIG. 6 is a block diagram illustrating a further configuration of an interface apparatus according to an embodiment.
  • One or more embodiments include communication interface apparatuses capable of automatically converting a protocol for communication between devices using different protocols, and interface methods using the same.
  • an interface apparatus for converting a communication protocol includes a first communicator configured to communicate data with a programmable logic controller (PLC) included in an industrial process controller, a second communicator configured to communicate data with a plurality of peripheral devices including different protocols, a processor, and a memory configured to store instructions executable by the processor, wherein the processor executes the instructions to receive first data including information of a peripheral device to receive data and control information from the PLC through the first communicator, determine a protocol format corresponding to the information of the peripheral device acquired from the first data, generate transmission data by combining the first data with the protocol format, and transmit the generated transmission data to the peripheral device.
  • PLC programmable logic controller
  • an interface method of converting a communication protocol includes receiving first data including information of a peripheral device to receive data and control information from a PLC, determining a protocol format corresponding to the information of the peripheral device acquired from the first data, generating transmission data by combining the first data with the protocol format, and transmitting the generated transmission data to the peripheral device.
  • a non-transitory computer-readable recording medium stores a program that, when executed by a computer, performs the interface method of converting a communication protocol.
  • FIG. 1 is a block diagram illustrating a configuration of a communication interface apparatus according to an embodiment.
  • a communication interface apparatus 10 may perform a function of connecting a programmable logic controller (PLC) 20 used in an industrial field to a peripheral device 30 controlled by the PLC 20.
  • PLC programmable logic controller
  • the peripheral device 30 may include a plurality of peripheral devices 31, 32, and 33.
  • the plurality of peripheral devices 31, 32, and 33 may use different protocols respectively.
  • the plurality of peripheral devices 31, 32, and 33 of various types may use a protocol such as Transmission Control Protocol/Internet Protocol (TCP/IP), User Datagram Protocol (UDP), OLE for Process Control (OPC), DNP3, Modbus TCP, ProfiBus, Ethernet, RS-232, RS-485, Modbus 485, or BACNet.
  • TCP/IP Transmission Control Protocol/Internet Protocol
  • UDP User Datagram Protocol
  • OPC OLE for Process Control
  • DNP3 Modbus TCP
  • ProfiBus Ethernet
  • RS-232 RS-485
  • Modbus 485, or BACNet Modbus 485, or BACNet.
  • the plurality of peripheral devices 31, 32 and 33 may include, but is not limited to, a barcode reader, a nut runner, an electronic scale, an industrial process computer (PC), a human machine interface (HMI), a file server, an RFID reader, a facility workstation, a relay, an energy storage system (ESS), a battery energy storage system (BESS), a measuring instrument, a measurement sensor, a diesel engine, or an actuator.
  • a barcode reader e.g., a barcode reader, a nut runner, an electronic scale, an industrial process computer (PC), a human machine interface (HMI), a file server, an RFID reader, a facility workstation, a relay, an energy storage system (ESS), a battery energy storage system (BESS), a measuring instrument, a measurement sensor, a diesel engine, or an actuator.
  • PC industrial process computer
  • HMI human machine interface
  • ESS energy storage system
  • BESS battery energy storage system
  • the PLC 20 may be controlled by various types of terminals to control the plurality of peripheral devices 31, 32, and 33, and may receive communication data from the plurality of peripheral devices 31, 32, and 33 and transmit the same to various types of terminals.
  • the communication interface apparatus 10 may include a first communicator 110, a second communicator 120, a processor 130, and a memory 140.
  • the first communicator 110 and the second communicator 120 may perform a function of connecting industrial controllers and various facilities located in industrial fields.
  • the first communicator 110 may communicate data with a programmable logic controller (PLC) included in an industrial process controller.
  • PLC programmable logic controller
  • the first communicator 110 may include at least one of a CC-Link communication port, a ProfiBus communication port, and a DeviceNet communication port.
  • the first communicator 110 may include an Ethernet port for communicating with the PLC 20.
  • the communication interface apparatus 10 may be connected to the Internet network by using the Ethernet port.
  • the second communicator 120 may communicate data with a plurality of peripheral devices including different protocols. Also, the second communicator 120 may include at least one of an RS232 communication port and an RS485 communication port.
  • the second communicator 120 may include a plurality of second ports 121, 122, 123, and 124.
  • the plurality of second ports 121, 122, 123, and 124 may refer to a plurality of transmission ports and a plurality of reception ports for transmitting and receiving data.
  • the communication interface apparatus 10 may receive data from a plurality of peripheral devices through a plurality of reception ports included in the second communicator 120 and transmit data to a plurality of peripheral devices through a plurality of transmission ports.
  • the communication interface apparatus 10 may receive first data including information of a peripheral device to receive data and control information from the PLC through the first communicator 110. Also, the communication interface apparatus 10 may determine a protocol format corresponding to the information of the peripheral device acquired from the first data.
  • the processor 130 may generate transmission data by combining the first data with the protocol format.
  • the processor 130 may access a setting page through the Internet network by using the first communicator 110 when there is no a suitable protocol format in the communication interface apparatus 10.
  • the user may set the protocol by using the setting page.
  • the user may set the protocol by designating an identification code in a predetermined format of communication protocol.
  • the processor 130 may be mounted with a real-time operating system (RTOS) of an individual network connection, and when data transmission/reception is interrupted due to a communication error with respect to at least one peripheral device 30, communication may be attempted automatically after the lapse of a predetermined time. According to an embodiment, the processor 130 may automatically restore the communication after a certain period of time even when the communication is interrupted due to an error in the peripheral device 30.
  • RTOS real-time operating system
  • the processor 130 may monitor the communication state of the first communicator 110 and the second communicator 120 in real time. According to an embodiment, the processor 130 may control the communication based on the communication state of the first communicator 110 and the second communicator 120. According to an embodiment, the processor 130 may generate conversion data when both a first communication state value and a second communication state value are determined to be in a good communication state.
  • the processor 130 may detect the first communication state value through the first communicator 110. According to an embodiment, the processor 130 may determine that the communication is in a good state when the first communication state value is greater than or equal to a predetermined value and determine that the communication is in a poor state when the first communication state value is smaller than the predetermined value.
  • the processor 130 may detect the second communication state value through the second communicator 120. According to an embodiment, the processor 130 may determine that the communication is in a good state when the second communication state value is greater than or equal to a predetermined value and determine that the communication is in a poor state when the second communication state value is smaller than the predetermined value.
  • the memory 140 may store data executable by the processor 130. Also, the memory 140 may store transmission/reception data with respect to the PLC 20 and the peripheral device 30. Also, the memory 140 may store data converted by the processor 130.
  • the processor 130 may receive data through the second communicator 120. According to an embodiment, the processor 130 may convert only data in a particular region of the data received through the second communicator 120 into data in the form of ASCII (American Standard Code for Information Interchange) code. According to an embodiment, the processor 130 may transmit the data in the form of ASCII code through the first communicator 110 to the PLC 20.
  • ASCII American Standard Code for Information Interchange
  • the processor 130 may transmit a continuous data array received from the peripheral device 30 to the PLC 20 without processing. Also, the processor 130 may acquire only data in a necessary region of the data received from the peripheral device 30, convert the acquired data into an ASCII code form, and transmit the resulting data to the PLC 20.
  • the communication interface apparatus 10 may include a simulator module that periodically transmits pre-converted data to a plurality of peripheral devices 30 without communication with the PLC 20.
  • a simulator function may be set through the Internet network connected through the communication interface apparatus 10. The simulator function may set a communication period, a data array, a graph format, and the like.
  • the data generated by the simulator module may include a data transmission period, a data array, and identification information of a peripheral device.
  • FIG. 2 is a flowchart illustrating a communication interface method according to an embodiment.
  • the communication interface apparatus 10 may receive first data including information of a peripheral device to receive data and control information from the PLC through the first communicator 110.
  • the communication interface apparatus 10 may determine a protocol format corresponding to the information of the peripheral device acquired from the first data. For example, when the peripheral device is an RFID reader, it may import a stored RFID communication protocol.
  • the communication interface apparatus 10 may parse the first data received from the first communicator 110 to acquire control information for controlling the peripheral device and information about the peripheral device to receive data. According to an embodiment, the communication interface apparatus 10 may determine the communication protocol of the peripheral device from the information about the peripheral device and read the communication protocol from a storage unit.
  • the communication interface apparatus 10 may parse the data to acquire identification information (ID) of a transmitting-side device, identification information (ID) of a receiving-side device, detailed information (Tag Name) of the receiving-side device, information of a transmission protocol, information of a reception protocol, and information about the content included in a header region of the first data, the content included in a data region of the first data, and the content included in a trailer region of the first data.
  • ID identification information
  • ID identification information
  • ID identification information
  • Tag Name detailed information
  • the communication interface apparatus 10 may parse the data to acquire identification information (ID) of a transmitting-side device, identification information (ID) of a receiving-side device, detailed information (Tag Name) of the receiving-side device, information of a transmission protocol, information of a reception protocol, and information about the content included in a header region of the first data, the content included in a data region of the first data, and the content included in a trailer region of the first data.
  • the communication interface apparatus 10 may generate transmission data by combining the first data with the protocol format. According to an embodiment, the communication interface apparatus 10 may generate transmission data for transmitting control information to the peripheral device. In this case, the communication interface apparatus 10 may generate the first data received in a text form as the transmission data in the form of an ASCII code.
  • the communication interface apparatus 10 may transmit the generated transmission data to the peripheral device through the second communicator 120.
  • the peripheral device may communicate by using the RS232 communication port and the RS485 communication port.
  • FIG. 3 is a diagram illustrating an example of converting a protocol of information received from a PLC and transmitting the same to a peripheral device, according to an embodiment.
  • FIG. 3 is a diagram illustrating an example of converting a protocol to transmit the information received from the PLC 20 to an RFID 31 as a peripheral device.
  • the communication interface apparatus 10 may receive a message 301 containing a text signal of '0010' representing an RFID data address and a message 302 containing a text signal of '0002' representing 'control information (number of bytes to read)' from the PLC 20.
  • the communication interface apparatus 10 may identify the communication protocol of the RFID 31. According to an embodiment, the communication interface apparatus 10 may import Command Code, Method, Antenna No, and Terminator information as the communication protocol format of the RFID 31 from the memory. According to an embodiment, the communication interface apparatus 10 may combine the RFID data address and the control information with the Command Code, Method, Antenna No, and Terminator information imported from the memory.
  • the communication interface apparatus 10 may combine RD as Command Code, ST as Method, and H1 as Antenna No before 0010 (303) as the RFID data address. Also, the communication interface apparatus 10 may combine the control information (number of bytes to read) 0002 (304) after the RFID data address and generate the transmission data by combining *CR as a terminator indicating the end of the data length. Also, the communication interface apparatus 10 may generate data in an ASCII code corresponding to the text information.
  • the communication interface apparatus 10 may transmit a message 305 containing RDSTH100100002*CR (82,68,83,84,72,49,48,48,49,48,48,48,48,50,42,13) to the RFID 31.
  • the communication interface apparatus 10 may receive only the control information and the information about the peripheral device from the PLC and import and combine the communication protocol format itself, to generate data that may be communicated with the peripheral device without a separate communication protocol conversion device or conversion program.
  • FIG. 4 is a diagram illustrating an example of extracting information from data received from a peripheral device and transmitting the same to a PLC, according to an embodiment.
  • the communication interface apparatus 10 of the present disclosure may extract only necessary information among the information received from the peripheral device and transmit the extracted information to the PLC 20.
  • the communication interface apparatus 10 may receive a message 401 containing the data of RD00H100123456*CR (82,68,48,48,72,49,48,48,49,50,51,52,53,54,13) from the RFID 31.
  • the communication interface apparatus 10 may parse the received data to extract the information to be transmitted to the PLC 20.
  • the communication interface apparatus 10 may extract only the response information except the communication protocol.
  • the communication interface apparatus 10 may acquire the response information 402 of "00123456 (48,48,49,50,51,52,53,54).
  • the communication interface apparatus 10 may convert the acquired response information into response data in a form available in the PLC 20.
  • the communication interface apparatus 10 may transmit the response data to the PLC 20.
  • the communication interface apparatus 10 may transmit a message 403 containing the text information of "123456" to the PLC 20.
  • FIG. 5 is a flowchart illustrating a method of generating a protocol through a user setting input when there is no protocol in an interface apparatus, according to an embodiment.
  • the communication interface apparatus 10 may select a protocol format matching the communication protocol of the peripheral device, in order to transmit the first data received from the PLC to the peripheral device.
  • the communication interface apparatus 10 may determine whether information about the protocol format of the peripheral device is stored in a memory.
  • the memory may be included in the communication interface apparatus 10 or may be an external device connected to the communication interface apparatus 10.
  • the communication interface apparatus 10 may generate transmission data by using the protocol format when the information about the protocol format of the peripheral device is included in the memory.
  • the communication interface apparatus 10 may transmit the transmission data generated in accordance with the protocol format of the peripheral device to the peripheral device.
  • the communication interface apparatus 10 may access a setting page by using the Internet network when the information about the protocol format of the peripheral device is not included in the memory. According to an embodiment, the communication interface apparatus 10 may access the setting page through a connection with an external PC or through its own communication network.
  • the setting page may provide a user interface capable of combining protocol formats.
  • the communication interface apparatus 10 may visually display a protocol format corresponding to protocol information of a plurality of peripheral devices through the setting page.
  • the communication data since the user may designate the protocol format while viewing the protocol information displayed on the screen, the communication data may be easily generated.
  • the communication interface apparatus 10 may set the protocol through a user input.
  • a new protocol format may be generated by using characters, numbers, or the like selected by the user input.
  • communication with the peripheral device having the protocol not stored in the communication interface apparatus 10 may be easily started.
  • FIG. 6 is a block diagram illustrating a further configuration of a communication interface apparatus according to an embodiment.
  • the communication interface apparatus may further include a display 150 and a user input unit 160 in addition to the configuration illustrated in FIG. 1.
  • the display 150 may display the communication state of the PLC and the peripheral device through the communication interface apparatus 10 in real time. According to an embodiment, the display 150 may display information about a control command received from the PLC. Also, the display 150 may display the transmission data obtained by converting the control command received from the PLC into data available in the peripheral device. Also, the display 150 may display the data received from the peripheral device.
  • the display 150 may display an alarm notification when the protocol format of the desired peripheral device is not present in the memory. In this case, the user may recognize that the designation of the protocol format is required through the notification displayed on the display 150.
  • the display 150 may provide a setting page for setting the protocol format. The display 150 may visualize and display the format of the protocol in advance through the setting page, and may illustratively display a number or character for designating the format of the protocol.
  • the user may designate the format of the protocol through the user input unit 160. According to an embodiment, since the user may individually designate the format of a necessary protocol through the display 150, the user may quickly and accurately generate the protocol format.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • General Physics & Mathematics (AREA)
  • Automation & Control Theory (AREA)
  • Physics & Mathematics (AREA)
  • Computer Security & Cryptography (AREA)
  • Manufacturing & Machinery (AREA)
  • General Engineering & Computer Science (AREA)
  • Quality & Reliability (AREA)
  • Medical Informatics (AREA)
  • General Health & Medical Sciences (AREA)
  • Computing Systems (AREA)
  • Health & Medical Sciences (AREA)
  • Programmable Controllers (AREA)
  • Communication Control (AREA)
  • Computer And Data Communications (AREA)
PCT/KR2018/000780 2017-12-27 2018-01-17 Interface apparatus and method of converting communication protocol WO2019132095A1 (en)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
KR10-2017-0181444 2017-12-27
KR1020170181444A KR102030012B1 (ko) 2017-12-27 2017-12-27 통신 프로토콜을 변환하는 인터페이스 장치 및 방법

Publications (1)

Publication Number Publication Date
WO2019132095A1 true WO2019132095A1 (en) 2019-07-04

Family

ID=67063885

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/KR2018/000780 WO2019132095A1 (en) 2017-12-27 2018-01-17 Interface apparatus and method of converting communication protocol

Country Status (2)

Country Link
KR (1) KR102030012B1 (ko)
WO (1) WO2019132095A1 (ko)

Cited By (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112953880A (zh) * 2019-11-26 2021-06-11 中车大连电力牵引研发中心有限公司 通信协议转换装置及方法
CN113170004A (zh) * 2021-03-15 2021-07-23 华为技术有限公司 数据传输方法、装置及系统
CN113381974A (zh) * 2021-05-06 2021-09-10 北京工业大学 一种应用于专用通信的现场总线与Modbus-TCP之间的协议转换方法
CN113572782A (zh) * 2021-07-30 2021-10-29 广东机电职业技术学院 一种支持多种传感网的物联网网关及其实现方法
CN114137923A (zh) * 2021-11-29 2022-03-04 航天新长征大道科技有限公司 工业生产现场数据采集与控制装置
CN114520729A (zh) * 2020-11-05 2022-05-20 北京广利核系统工程有限公司 一种通信隔离系统及通信隔离的方法
CN114578790A (zh) * 2022-03-04 2022-06-03 沃飞长空科技(成都)有限公司 一种无人机飞控自动测试方法、系统、设备和介质
CN114759942A (zh) * 2020-12-25 2022-07-15 杭州旗捷科技有限公司 一种芯片及数据转换方法

Families Citing this family (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR102262938B1 (ko) * 2019-07-24 2021-06-08 현덕환 Bus 구조를 가지는 공장 자동화 제어 시스템
CN110716518B (zh) * 2019-10-11 2021-12-07 北京航天长征飞行器研究所 多种总线通讯机制高可靠兼容型火工品控制平台
KR20230168536A (ko) 2022-06-07 2023-12-14 한국수력원자력 주식회사 안전등급의 가상 plc 간의 통신을 위한 sdl 또는 sdn의 이더넷 변환 장치 및 방법

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR100294633B1 (ko) * 1997-09-04 2001-07-12 이종수 피엘씨의시뮬레이터
KR20030000579A (ko) * 2001-06-26 2003-01-06 주식회사 엘지이아이 통신 프로토콜 변환장치 및 방법
KR20060010298A (ko) * 2004-07-27 2006-02-02 변효현 자동화 시스템 원격제어 및 관리를 위한 이기종 피엘씨간통신제어 시스템 및 방법
KR20150076753A (ko) * 2013-12-27 2015-07-07 주식회사 포스코아이씨티 통신 인터페이스 장치 및 이를 이용한 인터페이스 방법
KR20170071021A (ko) * 2015-12-15 2017-06-23 엘지전자 주식회사 이종 네트워크 간의 프로토콜 변환 장치 및 방법

Family Cites Families (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR100513525B1 (ko) 2003-06-05 2005-09-07 현대자동차주식회사 차량 조립 정보 확인 시스템

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR100294633B1 (ko) * 1997-09-04 2001-07-12 이종수 피엘씨의시뮬레이터
KR20030000579A (ko) * 2001-06-26 2003-01-06 주식회사 엘지이아이 통신 프로토콜 변환장치 및 방법
KR20060010298A (ko) * 2004-07-27 2006-02-02 변효현 자동화 시스템 원격제어 및 관리를 위한 이기종 피엘씨간통신제어 시스템 및 방법
KR20150076753A (ko) * 2013-12-27 2015-07-07 주식회사 포스코아이씨티 통신 인터페이스 장치 및 이를 이용한 인터페이스 방법
KR20170071021A (ko) * 2015-12-15 2017-06-23 엘지전자 주식회사 이종 네트워크 간의 프로토콜 변환 장치 및 방법

Cited By (11)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112953880A (zh) * 2019-11-26 2021-06-11 中车大连电力牵引研发中心有限公司 通信协议转换装置及方法
CN114520729A (zh) * 2020-11-05 2022-05-20 北京广利核系统工程有限公司 一种通信隔离系统及通信隔离的方法
CN114520729B (zh) * 2020-11-05 2024-01-19 北京广利核系统工程有限公司 一种通信隔离系统及通信隔离的方法
CN114759942A (zh) * 2020-12-25 2022-07-15 杭州旗捷科技有限公司 一种芯片及数据转换方法
CN113170004A (zh) * 2021-03-15 2021-07-23 华为技术有限公司 数据传输方法、装置及系统
CN113381974A (zh) * 2021-05-06 2021-09-10 北京工业大学 一种应用于专用通信的现场总线与Modbus-TCP之间的协议转换方法
CN113572782A (zh) * 2021-07-30 2021-10-29 广东机电职业技术学院 一种支持多种传感网的物联网网关及其实现方法
CN113572782B (zh) * 2021-07-30 2023-03-10 广东机电职业技术学院 一种支持多种传感网的物联网网关及其实现方法
CN114137923A (zh) * 2021-11-29 2022-03-04 航天新长征大道科技有限公司 工业生产现场数据采集与控制装置
CN114578790A (zh) * 2022-03-04 2022-06-03 沃飞长空科技(成都)有限公司 一种无人机飞控自动测试方法、系统、设备和介质
CN114578790B (zh) * 2022-03-04 2024-05-14 四川傲势科技有限公司 一种无人机飞控自动测试方法、系统、设备和介质

Also Published As

Publication number Publication date
KR102030012B1 (ko) 2019-11-08
KR20190079328A (ko) 2019-07-05

Similar Documents

Publication Publication Date Title
WO2019132095A1 (en) Interface apparatus and method of converting communication protocol
US20080004726A1 (en) Connection module for sensors
WO2018048219A1 (ko) 무선통신망을 이용한 공장설비 관리 시스템 및 방법
WO2012111892A1 (ko) 휴대단말기의 사용자 인터페이스 자동 생성과 이를 이용한 설비 제어시스템
US10805399B2 (en) Data server unit and communication system including master-slave management circuitry
WO2013094868A1 (ko) 이기종 수치제어장치를 위한 공작기계 정보 관리 장치 및 그 방법
US11500573B2 (en) Multiple interface data exchange application for use in process control
CN107547475A (zh) 一种支持多通讯规约转换的数据处理设备及其系统
WO2022014853A1 (ko) 기존 필드버스 기반 자동제어 시스템의 사물인터넷 연동 장치 및 방법
CN108696375B (zh) 工业网络信息获取装置、方法、监控系统及存储介质
CN106407139A (zh) 用于传输hart变量的方法和外围组件及cpu单元
CN210724830U (zh) 架接接口模块
CN103532686B (zh) 带有线序自适应功能的串行数据收发电路及其控制方法
Xu et al. Profibus automation technology and its application in DP slave development
US20150223286A1 (en) Sensor brain for simple sensors in a process control system
JP2010034809A (ja) フィールドバスシステム
CN109922096B (zh) 多个传感器通用接口的通信系统
CN114228083A (zh) 工业控制系统和注塑机
WO2022119111A1 (ko) 모듈화 센서 플랫폼 장치
WO2021125452A1 (ko) Hart 패스-스루 인터페이스를 포함하는 plc 아날로그 모듈
US20220206452A1 (en) Configuration-free output of user data contained in ethernet telegrams
WO2023101209A1 (ko) 모듈 확장 장치를 포함하는 스마트 배전반
CN214380908U (zh) 抗干扰的连铸机dp网络系统
US20100205338A1 (en) Network connection system
CN201243303Y (zh) 用于网络测控的ip传感器

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: 18895472

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: 18895472

Country of ref document: EP

Kind code of ref document: A1