WO2013014793A1 - 通信装置 - Google Patents
通信装置 Download PDFInfo
- Publication number
- WO2013014793A1 WO2013014793A1 PCT/JP2011/067322 JP2011067322W WO2013014793A1 WO 2013014793 A1 WO2013014793 A1 WO 2013014793A1 JP 2011067322 W JP2011067322 W JP 2011067322W WO 2013014793 A1 WO2013014793 A1 WO 2013014793A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- unit
- plc
- bus
- storage unit
- error
- Prior art date
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/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/058—Safety, monitoring
-
- 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
-
- 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/048—Monitoring; Safety
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F13/00—Interconnection of, or transfer of information or other signals between, memories, input/output devices or central processing units
- G06F13/14—Handling requests for interconnection or transfer
Definitions
- the present invention relates to a communication device that is mounted on a programmable controller (PLC) and connects PLCs over a network.
- PLC programmable controller
- Some PLCs are configured with one or more functional units connected to the base unit.
- the functional unit includes a CPU unit that performs overall control of the PLC, an input / output unit that performs input / output with a controlled device, a network unit as a communication device that performs communication with other PLCs, and the like.
- the user can prepare a PLC by combining desired functional units.
- the base unit has a built-in bus, and a plurality of functional units mounted on the base unit can transmit / receive data to / from each other via the bus.
- distributed control of the FA system is performed using a plurality of PLCs.
- Each PLC is equipped with a network unit, and cooperates to control the FA system by transmitting and receiving control data to and from each other via the network unit.
- an access error (hereinafter referred to as a bus error) may occur between the CPU unit and another functional unit. Error information describing the contents of the bus error is recorded in a storage unit provided in the CPU unit mounted on the PLC in which the bus error has occurred.
- Patent Document 1 there is a PLC that can store information necessary for analyzing a bus error or the like in the FA link module.
- Patent Document 2 Patent Document 3
- Patent Document 4 Patent Document 4
- Patent Document 1 when the network unit holds the error information of the own PLC, or when the error information of the own PLC is recorded in the recording unit of the CPU unit, the bus error When this occurs, the user needs to check each PLC one by one in order to obtain the corresponding error information, and there is a problem that it takes time and effort to investigate the cause.
- Patent Documents 2 to 4 when the technologies disclosed in Patent Documents 2 to 4 are applied to a PLC system, when a bus error occurs, the user needs to check the remote monitoring device for each network unit one by one. There is a problem that it takes time.
- the present invention has been made in view of the above, and an object of the present invention is to obtain a communication device that can easily specify a location where a bus error occurs.
- the present invention is connected to a bus, configures a programmable controller (PLC) with the bus, and connects the own PLC and another PLC over a network to form a PLC system.
- PLC programmable controller
- a communication device to be constructed wherein a first storage unit, an error detection unit for detecting a bus error occurring in a bus of the own PLC, and the number of times the error detection unit has detected a bus error are counted.
- An error count unit that records a count value in the first storage unit, and a count value that is recorded by the error count unit that is recorded in the first storage unit is transmitted to all other PLCs that belong to the same PLC system.
- Receive the count value transmitted from the transmitting unit to transmit and other PLCs belonging to the same PLC system, and the received count value Xinyuan the PLC is characterized in that it comprises a a receiving section that storable in the first storage unit identification.
- the communication apparatus can confirm the bus error of all the PLCs constituting the PLC system by confirming any PLC among the PLCs constituting the PLC system. It can be easily identified.
- FIG. 1 is a diagram illustrating a configuration of a PLC system configured using the network unit according to the first embodiment.
- FIG. 2 is a diagram illustrating an internal configuration of the network unit according to the first embodiment.
- FIG. 3 is a diagram for explaining the operation of the PLC system according to the first embodiment.
- FIG. 4 is a flowchart for explaining the operation of the network unit of the first embodiment provided in the PLC on the error information transmission side.
- FIG. 5 is a flowchart for explaining the operation of the network unit according to the first embodiment provided in the PLC on the error information receiving side.
- FIG. 6 is a diagram illustrating a configuration of a PLC system configured using the communication apparatus according to the second embodiment.
- FIG. 7 is a diagram illustrating an internal configuration of a functional unit according to the second embodiment.
- FIG. 8 is a diagram illustrating the internal configuration of the network unit according to the second embodiment.
- FIG. 1 is a diagram illustrating a configuration of a PLC system configured using a network unit to which the communication device according to the first embodiment of the present invention is applied.
- the PLC system 1 is configured by connecting a plurality of PLCs (here, three PLCs 300, 301, and 302) in a daisy chain with a cable 130.
- the PLC 300, the PLC 301, and the PLC 302 can transmit / receive data to / from each other using a token passing communication method.
- the PLC system 1 is assumed to have a line network topology, but the network topology that can be adopted is not limited to a line shape. For example, it may be a star shape or a ring shape.
- the description of the configuration of the PLCs 300 to 302 is represented by the description of the configuration of the PLC 300.
- the PLC 300 includes a network unit 100 that communicates with other PLCs via the cable 130, a CPU unit 110 that controls the entire PLC 300, and a bus 120 that electrically connects the network unit 100 and the CPU unit 110. It has. In addition to the network unit 100, various functional units can be connected to the bus 120. Functional units connected to the bus 120 are controlled by the CPU unit 110.
- FIG. 2 is a diagram showing an internal configuration of the network unit 100.
- the network unit 100 transmits and receives data to and from the CPU unit 110 connected to the same bus 120, and also detects a bus error occurring on the bus 120.
- a bus error count unit 20 that counts the number of detected bus errors
- a storage unit (first storage unit) 30 that stores a count value of the bus error as error information related to the own PLC 300, and other PLCs are transmitted.
- the receiver 40 that receives the received frame via the cable 130 and the error information related to the own PLC 300 stored in the storage 30 via all the other PLCs belonging to the same PLC system 1 as the destination via the cable 130
- the receiving unit 40 receives error information transmitted from another PLC, and records the received error information related to the other PLC in the storage unit 30. In other words, not only the error information of the own PLC but also the error information of another PLC is recorded in the storage unit 30. It is assumed that each error information stored in the storage unit 30 can identify which PLC error information. For example, PLC identification information may be added to the error information. For example, the receiving unit 40 may give the identification information, or may be given by the bus error count unit 20 of the PLC that generated the error information.
- the CPU unit 110 includes a storage unit (second storage unit) 200 configured by a rewritable storage device.
- the bus connection unit 10 transfers error information for each PLC stored in the storage unit 30 to the storage unit 200 included in the CPU unit 110 via the bus 120.
- the bus connection unit 10 causes the CPU unit 110 to read out error information for each PLC from the storage unit 30, and issues a signal to the CPU unit 110 to store the read error information in the storage unit 200. Shall be applied.
- the peripheral unit 150 is connected to the CPU unit 110 included in the PLC 301 via a cable 140.
- the peripheral device 150 is a tool realized by executing a predetermined program on a personal computer, and can set the CPU unit 110 to be connected.
- the peripheral device 150 can refer to the storage unit 200 included in the CPU unit 110. That is, the user connects the peripheral device 150 to the CPU unit 110 included in any PLC among the PLCs 300 to 302 and refers to the error information recorded in the storage unit 200 of the connected CPU unit 110. Thus, it is possible to check a bus error that has occurred in all the PLCs 300 to 302.
- a part or all of the bus connection unit 10, the bus error count unit 20, the reception unit 40, and the transmission unit 50 included in the network unit 100 is realized as either hardware or software, or a combination of both. You may do it.
- Realization by software means that in a computer having an arithmetic device and a storage device, a program module corresponding to a component is stored in the storage device, and the arithmetic device executes the program module stored in the storage device. It is to realize the function of the component.
- the storage unit 30 is configured by a rewritable storage device.
- FIG. 3 is a diagram for explaining the operation of the PLC system 1
- FIG. 4 is a flowchart for explaining the operation of the network unit 100 provided in the PLC on the error transmission side.
- the PLC 300 is a PLC that transmits error information
- the PLC 301 is a PLC that receives error information.
- the bus connection unit 10 monitors the bus 120 and determines whether or not a bus error is detected (step S1). In the bus access between the CPU unit 110 of the PLC 300 and the network unit 100, for example, when an access error 160 occurs due to electrical noise or vibration, the bus connection unit 10 detects an error from a signal on the bus 120. A bus error can be detected by reading the location.
- step S1 When a bus error is detected (step S1, Yes), the bus error count unit 20 counts up the count value stored as error information in the storage unit 30 (step S2). When no bus error is detected (No at Step S1), the process at Step S2 is skipped.
- step S3 determines whether or not a free token has been received.
- step S3 No the process of step S1 is executed.
- the transmission unit 50 reads out the error information related to the own PLC 300 stored in the storage unit 30 (step S4), and transmits a frame 170 holding the read error information. All other PLCs 301 and 302 are transmitted as destinations via the cable 130 (step S5).
- the network unit 100 of the PLC 300 executes the process of step S1 after the process of step S5.
- FIG. 5 is a flowchart for explaining the operation of the network unit 100 included in the PLC 301 on the error information receiving side.
- the PLC 301 receives the frame transmitted by the PLC 300 first.
- the receiving unit 40 receives the frame 170 holding the error information of the PLC 300 (step S11)
- it reads out the bus error information of the PLC 300 from the frame 170 and reads the read error information. Is stored in the storage unit 30 (step S12).
- the bus connection unit 10 reads out the error information for each PLC stored in the storage unit 30 and generates a signal 180 for storing the read error information for each PLC in the storage unit 200.
- the signal 180 is transmitted to the CPU unit 110 of the PLC unit 301 (step S13).
- the transmission unit 50 transmits the frame 170 received by the reception unit 40 to the PLC 302 (step S14), and the operation ends.
- the CPU unit 110 When the CPU unit 110 receives the signal 180, the CPU unit 110 reads error information for each PLC stored in the storage unit 30, and stores the read error information for each PLC in the storage unit 200.
- the bus connection unit 10 issues the signal 180 every time the receiving unit 40 stores the error information received from another PLC in the storage unit 30, the user connects the peripheral device 150 to any of the PLCs 300 to 302. Even when connected to the CPU unit 110 provided, all bus errors occurring on the bus 120 on the PLCs 300, 301, and 302 can be monitored (ie, monitored) in substantially real time.
- the timing at which the bus connection unit 10 transfers the error information is not limited to when the receiving unit 40 stores the error information received from another PLC in the storage unit 30.
- the peripheral device 150 may issue a command to transfer the error information, and the command may be transferred at the timing received via the CPU unit 110 and the bus 120. Also good.
- the communication method between PLCs is not limited to the token-passing method.
- the storage unit 30, the bus connection unit 10 as a bus error detection unit that detects a bus error that occurs in the bus of the own PLC, and the bus connection unit 10. Counts the number of times the bus error is detected, and records the bus error count value in the storage unit 30 as error information and the error information recorded in the storage unit 30 to the same PLC system 1
- the transmission unit 50 that transmits to all other PLCs to which it belongs and the error information transmitted from other PLCs connected to the same PLC system 1 are received, and the received PLC receives the received error information. Since the receiving unit 40 is stored in the storage unit 30 so as to be identifiable, the user can connect the PLCs 300, 301, 302 constituting the PLC system 1. Since it is possible to check the bus error that has occurred in all the PLCs 300 to 302 simply by checking any of these PLCs, it is possible to easily identify the location where the bus error has occurred compared to the case of checking each PLC. .
- the network unit is configured to detect and count the bus error.
- the function for detecting the bus error and the function for counting the number of times the bus error is detected are provided in a functional unit other than the network unit. You may make it comprise.
- FIG. 6 is a diagram illustrating a configuration of a PLC system configured using a network unit to which the communication device according to the second embodiment of the present invention is applied.
- symbol is attached
- the PLC system 2 is configured by connecting a PLC 400, a PLC 301, and a PLC 302 in a daisy chain with a cable 130.
- the PLC 400 includes a CPU unit 110, a functional unit 220, a network unit 240, and a bus 120 that electrically connects these units.
- the functional unit 220 is a functional unit excluding the network unit 240 and the CPU unit 110 and may be any unit, for example, an A / D conversion unit.
- the functional unit 220 operates based on a control signal 210 that the CPU unit 110 transmits via the bus 120.
- FIG. 7 is a diagram showing an internal configuration of the functional unit 220. Here, only functional components common to the functional units to which the second embodiment is applied will be described.
- the functional unit 220 includes a bus connection unit 60, a bus error count unit 70, and a storage unit 80.
- the bus connection unit 60 receives the control signal 210, returns a response to the CPU unit 110, and can detect the generated bus error when an error (that is, a bus error 260) occurs in the transmission of the control signal 210. it can.
- the bus error count unit 70 counts the number of bus errors detected by the bus connection unit 60 and records the count value in the storage unit 80 as error information. Note that some and all of the bus connection unit 60 and the bus error count unit 70 may be realized as either hardware or software, or a combination of both.
- the storage unit 80 is configured by a rewritable storage device.
- the network unit 240 acquires error information from the functional unit 220, and transmits the acquired error information to another PLC.
- FIG. 8 is a diagram illustrating the internal configuration of the network unit 240.
- the network unit 240 includes a bus connection unit 11 that acquires error information from the functional unit 220, a storage unit 31 in which error information acquired from the functional unit 220 is recorded, a reception unit 40, and a transmission unit 50. ing.
- the operation of the PLC system 2 according to the second embodiment will be described with reference to FIG. Since the operation of the PLC on the error information receiving side is the same as that of the first embodiment, only the operation of the PLC on the error information transmitting side will be described.
- the PLC 400 corresponds to the PLC on the side that transmits error information.
- the bus connection unit 11 included in the network unit 240 transmits a monitoring signal 230 for monitoring the presence or absence of a bus error toward the bus connection unit 60 included in the functional unit 220, and a monitoring response signal is transmitted. 231 is received.
- the bus connection unit 60 adds the error information to the monitoring response signal 231 when a bus error has occurred and error information is recorded in the storage unit 80, and the network unit 240 It transmits to the bus connection part 11 which comprises.
- the bus connection unit 11 when the bus connection unit 11 receives the monitoring response signal 231, the bus connection unit 11 reads the error information added to the received monitoring response signal 231 and stores the read error information in the storage unit 31.
- the operation in which the transmission unit 50 transmits the error information stored in the storage unit 31 to the PLC 301 is the same as that in the first embodiment.
- bus connection unit 60 of the functional unit 220 may actively transmit the error information recorded in the storage unit 80 to the network unit 240 as the signal 232 that holds the error information.
- the functional unit 220 includes the bus connection unit 60 serving as an error detection unit that detects a bus error occurring in the bus 120 and the bus connection unit 60 generates a bus error.
- a bus error count unit 70 that counts the detected number of times is provided, and the network unit 240 acquires a count value of the bus error from the functional unit 220 and records the acquired count value in the storage unit 31 as error information.
- the same as the bus connection unit 11 as the acquisition unit and the transmission unit 50 that transmits the error information acquired from the functional unit 220 recorded in the storage unit 31 to all other PLCs belonging to the same PLC system 2 The error information received from another PLC belonging to the PLC system 2 is received and the received error is received.
- the receiving unit 40 that stores the information in the storage unit 31 so that the PLC of the transmission source can identify the information, so that the user can select any one of the PLCs 400, 301, and 302 that constitute the PLC system 2
- the peripheral device 150 By connecting the peripheral device 150, it is possible to check the bus error that has occurred in all the PLCs 400, 301, 302, so that the location where the bus error has occurred can be easily identified.
- the communication apparatus is suitable for application to a network unit that is mounted on a PLC and connects PLCs over a network.
Abstract
Description
図1は、本発明の実施の形態1の通信装置を適用したネットワークユニットを用いて構成されるPLCシステムの構成を示す図である。図示するように、PLCシステム1は、複数のPLC(ここではPLC300、PLC301、およびPLC302の3つ)がケーブル130でデイジーチェーン状に接続されて構成されている。PLC300、PLC301およびPLC302は、トークンパッシング方式の通信方式で相互にデータを送受信することができる。なお、当該PLCシステム1は、ライン状のネットワークトポロジを備えているものとしているが、採用可能なネットワークトポロジはライン状だけに限定されない。例えば、スター状やリング状であってもよい。
実施の形態1においては、ネットワークユニットがバスエラーを検知・カウントする構成を具備するようにしたが、バスエラーを検知する機能やバスエラーの検知回数をカウントする機能はネットワークユニット以外の機能ユニットに具備するようにしてもよい。
10、11、60 バス接続部
20、70 バスエラーカウント部
30、31、80、200 記憶部
40 受信部
50 送信部
100、240 ネットワークユニット
110 CPUユニット
120 バス
130、140 ケーブル
150 周辺機器
160 アクセスエラー
170 フレーム
180 信号
210 制御信号
220 機能ユニット
230 監視信号
231 監視応答信号
232 信号
Claims (8)
- バスに接続され、当該バスとともにプログラマブルコントローラ(PLC)を構成し、自PLCと他のPLCとをネットワーク接続してPLCシステムを構築する通信装置であって、
第1の記憶部と、
自PLCのバスで発生するバスエラーを検知するエラー検知部と、
前記エラー検知部がバスエラーを検知した回数をカウントし、バスエラーのカウント値を前記第1の記憶部に記録するエラーカウント部と、
前記第1の記憶部に記録されている前記エラーカウント部がカウントしたカウント値を同一のPLCシステムに属する他の全てのPLCに送信する送信部と、
同一のPLCシステムに属する他のPLCから送信されてきたカウント値を受信して、前記受信したカウント値を送信元のPLCが識別可能に前記第1の記憶部に格納する受信部と、
を備えることを特徴とする通信装置。 - 周辺機器から参照可能な第2の記憶部を備えるCPUユニットが前記バスに接続され、
前記第1の記憶部に格納されているPLC毎のカウント値を前記バスを介して前記第2の記憶部に転送するバス接続部をさらに備える、
ことを特徴とする請求項1に記載の通信装置。 - 前記バス接続部は、前記受信部が他のPLCから送信されてきたカウント値を前記第1の記憶部に格納する毎に前記第1の記憶部に格納されているPLC毎のカウント値を前記第2の記憶部に転送する、
ことを特徴とする請求項2に記載の通信装置。 - 前記送信部および前記受信部は、他のPLCとの間でトークンパッシング方式の通信を行う、ことを特徴とする請求項1乃至請求項3のうちの何れか一項に記載の通信装置。
- バスに接続され、前記バスと、前記バスで発生するバスエラーを検知するエラー検知部および前記エラー検知部がバスエラーを検知した回数をカウントするエラーカウント部を備える、前記バスに接続される機能ユニットとともにプログラマブルコントローラ(PLC)を構成し、自PLCと他のPLCとネットワーク接続してPLCシステムを構築する通信装置であって、
第1の記憶部と、
前記エラーカウント部のカウント値を前記機能ユニットから取得して、前記取得したカウント値を前記第1の記憶部に記録するカウント値取得部と、
前記第1の記憶部に記録されているカウント値を同一のPLCシステムに属する他の全てのPLCに送信する送信部と、
同一のPLCシステムに属する他のPLCから送信されてきたカウント値を受信して、前記受信したカウント値を送信元のPLCが識別可能に前記第1の記憶部に格納する受信部と、
を備えることを特徴とする通信装置。 - 周辺機器から参照可能な第2の記憶部を備えるCPUユニットが前記バスに接続され、
前記第1の記憶部に格納されているPLC毎のカウント値を前記バスを介して前記第2の記憶部に転送するバス接続部をさらに備える、
ことを特徴とする請求項5に記載の通信装置。 - 前記バス接続部は、前記受信部が他のPLCから送信されてきたカウント値を前記第1の記憶部に格納する毎に前記第1の記憶部に格納されているPLC毎のカウント値を前記第2の記憶部に転送する、
ことを特徴とする請求項6に記載の通信装置。 - 前記送信部および前記受信部は、他のPLCとの間でトークンパッシング方式の通信を行う、ことを特徴とする請求項5乃至請求項7のうちの何れか一項に記載の通信装置。
Priority Applications (7)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US13/500,454 US20130031426A1 (en) | 2011-07-28 | 2011-07-28 | Communication apparatus |
DE112011105472.6T DE112011105472T5 (de) | 2011-07-28 | 2011-07-28 | Kommunikationsvorrichtung |
PCT/JP2011/067322 WO2013014793A1 (ja) | 2011-07-28 | 2011-07-28 | 通信装置 |
CN2011800041913A CN103026308A (zh) | 2011-07-28 | 2011-07-28 | 通信装置 |
JP2011546359A JP4902823B1 (ja) | 2011-07-28 | 2011-07-28 | 通信装置 |
KR1020127007061A KR101302861B1 (ko) | 2011-07-28 | 2011-07-28 | 통신 장치 |
TW100135193A TW201305755A (zh) | 2011-07-28 | 2011-09-29 | 通信裝置 |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
PCT/JP2011/067322 WO2013014793A1 (ja) | 2011-07-28 | 2011-07-28 | 通信装置 |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2013014793A1 true WO2013014793A1 (ja) | 2013-01-31 |
Family
ID=46060725
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/JP2011/067322 WO2013014793A1 (ja) | 2011-07-28 | 2011-07-28 | 通信装置 |
Country Status (7)
Country | Link |
---|---|
US (1) | US20130031426A1 (ja) |
JP (1) | JP4902823B1 (ja) |
KR (1) | KR101302861B1 (ja) |
CN (1) | CN103026308A (ja) |
DE (1) | DE112011105472T5 (ja) |
TW (1) | TW201305755A (ja) |
WO (1) | WO2013014793A1 (ja) |
Families Citing this family (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2014196078A1 (ja) * | 2013-06-07 | 2014-12-11 | 三菱電機株式会社 | プログラマブルコントローラシステムおよびエンジニアリングツール |
US20170048728A1 (en) * | 2015-08-10 | 2017-02-16 | Network Performance Research Group Llc | Method and apparatus for directed adaptive control of access point-to-client interaction in wireless networks |
KR20170114643A (ko) * | 2016-04-05 | 2017-10-16 | 엘에스산전 주식회사 | Plc용 통신 시스템 |
KR102219387B1 (ko) * | 2019-09-11 | 2021-02-23 | 엘에스일렉트릭(주) | 피엘씨 시스템의 오류 상태 제어방법 |
Citations (6)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JPH0690238A (ja) * | 1992-06-29 | 1994-03-29 | Yokogawa Electric Corp | 二重化通信制御装置 |
JPH11306109A (ja) * | 1998-04-16 | 1999-11-05 | Fuji Electric Co Ltd | バス監視表示器 |
JP2002057744A (ja) * | 2000-08-07 | 2002-02-22 | Yaskawa Electric Corp | 通信伝送路の異常検出方法 |
JP2002344453A (ja) * | 2001-05-21 | 2002-11-29 | Omron Corp | 通信エラーモニタシステムおよびスレーブユニットおよびネットワークコンフィグレータ |
JP2004171481A (ja) * | 2002-11-22 | 2004-06-17 | Yaskawa Electric Corp | 入出力装置 |
JP2008054040A (ja) * | 2006-08-24 | 2008-03-06 | Fanuc Ltd | データ転送方式及びデータ転送装置 |
Family Cites Families (12)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US4769761A (en) * | 1986-10-09 | 1988-09-06 | International Business Machines Corporation | Apparatus and method for isolating and predicting errors in a local area network |
US4992926A (en) * | 1988-04-11 | 1991-02-12 | Square D Company | Peer-to-peer register exchange controller for industrial programmable controllers |
EP0580938B1 (en) * | 1992-06-26 | 2001-09-26 | Yokogawa Electric Corporation | Duplex communication control device |
US5673390A (en) * | 1992-09-03 | 1997-09-30 | International Business Machines Corporation | Method and system for displaying error messages |
KR100919206B1 (ko) | 2005-06-30 | 2009-09-28 | 엘에스산전 주식회사 | 통신 프로토콜의 결정 스케줄 방법 |
US8274901B1 (en) * | 2005-09-06 | 2012-09-25 | Packet Design, Inc. | System and method for assisting in troubleshooting a network handling voice over internet protocol traffic |
JP4952228B2 (ja) * | 2006-12-18 | 2012-06-13 | 株式会社ジェイテクト | Plc分散制御システム |
KR100867872B1 (ko) | 2006-12-29 | 2008-11-07 | 엘에스산전 주식회사 | Plc에서의 복수의 모듈간의 통신속도 매칭 방법 |
JP4407752B2 (ja) * | 2008-01-10 | 2010-02-03 | トヨタ自動車株式会社 | 故障箇所検出装置及び通信装置並びに故障箇所検出方法 |
US8046444B2 (en) * | 2009-03-30 | 2011-10-25 | Rockwell Automation Technologies, Inc. | Universal network adapter for industrial control networks |
JP2010267003A (ja) | 2009-05-13 | 2010-11-25 | Mitsubishi Electric Corp | プログラマブルコントローラ |
KR101431301B1 (ko) * | 2010-01-20 | 2014-08-20 | 엘에스산전 주식회사 | 안전 증설 베이스 및 그의 제어방법 |
-
2011
- 2011-07-28 US US13/500,454 patent/US20130031426A1/en not_active Abandoned
- 2011-07-28 DE DE112011105472.6T patent/DE112011105472T5/de not_active Withdrawn
- 2011-07-28 WO PCT/JP2011/067322 patent/WO2013014793A1/ja active Application Filing
- 2011-07-28 KR KR1020127007061A patent/KR101302861B1/ko not_active IP Right Cessation
- 2011-07-28 CN CN2011800041913A patent/CN103026308A/zh active Pending
- 2011-07-28 JP JP2011546359A patent/JP4902823B1/ja not_active Expired - Fee Related
- 2011-09-29 TW TW100135193A patent/TW201305755A/zh unknown
Patent Citations (6)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JPH0690238A (ja) * | 1992-06-29 | 1994-03-29 | Yokogawa Electric Corp | 二重化通信制御装置 |
JPH11306109A (ja) * | 1998-04-16 | 1999-11-05 | Fuji Electric Co Ltd | バス監視表示器 |
JP2002057744A (ja) * | 2000-08-07 | 2002-02-22 | Yaskawa Electric Corp | 通信伝送路の異常検出方法 |
JP2002344453A (ja) * | 2001-05-21 | 2002-11-29 | Omron Corp | 通信エラーモニタシステムおよびスレーブユニットおよびネットワークコンフィグレータ |
JP2004171481A (ja) * | 2002-11-22 | 2004-06-17 | Yaskawa Electric Corp | 入出力装置 |
JP2008054040A (ja) * | 2006-08-24 | 2008-03-06 | Fanuc Ltd | データ転送方式及びデータ転送装置 |
Also Published As
Publication number | Publication date |
---|---|
TW201305755A (zh) | 2013-02-01 |
KR101302861B1 (ko) | 2013-09-02 |
JPWO2013014793A1 (ja) | 2015-02-23 |
KR20130023190A (ko) | 2013-03-07 |
DE112011105472T5 (de) | 2014-05-15 |
CN103026308A (zh) | 2013-04-03 |
US20130031426A1 (en) | 2013-01-31 |
JP4902823B1 (ja) | 2012-03-21 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US11016463B2 (en) | Control and data-transfer system, gateway module, I/O module, and method for process control | |
JP6772531B2 (ja) | 制御システム、制御方法、制御プログラム、および記録媒体 | |
US20090103441A1 (en) | Communication apparatus and switching device | |
US8732536B2 (en) | Communication system and communication apparatus state determining method | |
JP4902823B1 (ja) | 通信装置 | |
KR101855753B1 (ko) | 차량 진단 게이트웨이 장치 및 이를 포함하는 시스템 | |
JP5365234B2 (ja) | 端末装置間のトークン異常検出/回復方式 | |
JP5665723B2 (ja) | パケット中継装置およびシステム、障害検出方法 | |
JP4205138B2 (ja) | Ioユニットのステータス情報の取得方法 | |
JP2014191724A (ja) | 入出力制御装置 | |
JP5193162B2 (ja) | 無線通信状態取得方法および無線局 | |
CN111373700B (zh) | 通信系统、被控制设备以及通信系统的控制方法 | |
US11675717B2 (en) | Transmission of diagnostic and/or parameter data between a control module and an input/output module | |
US20170212821A1 (en) | Communication setting notification apparatus | |
JP2017120960A (ja) | 通信経路異常監視装置 | |
US11736318B2 (en) | Initialization of data bus subscribers | |
US11080061B2 (en) | Pre-loading of instructions | |
JP2011223199A (ja) | ゲートウェイ装置 | |
JP2013168850A (ja) | 分散型制御システム | |
US7457308B2 (en) | Method and data processing system for transmitting data via a data transmission unit | |
WO2014196078A1 (ja) | プログラマブルコントローラシステムおよびエンジニアリングツール | |
JP2016019059A (ja) | データ伝送装置およびデータ伝送システム | |
JP2011130371A (ja) | 通信ノード及び通信システム | |
JP2009194677A (ja) | 監視システム、中継装置およびパケット中継方法 | |
JP2006157835A (ja) | ネットワーク通信システムおよび障害検出通知方法 |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
WWE | Wipo information: entry into national phase |
Ref document number: 201180004191.3 Country of ref document: CN |
|
ENP | Entry into the national phase |
Ref document number: 2011546359 Country of ref document: JP Kind code of ref document: A |
|
ENP | Entry into the national phase |
Ref document number: 20127007061 Country of ref document: KR Kind code of ref document: A |
|
WWE | Wipo information: entry into national phase |
Ref document number: 13500454 Country of ref document: US |
|
121 | Ep: the epo has been informed by wipo that ep was designated in this application |
Ref document number: 11870063 Country of ref document: EP Kind code of ref document: A1 |
|
WWE | Wipo information: entry into national phase |
Ref document number: 1120111054726 Country of ref document: DE Ref document number: 112011105472 Country of ref document: DE |
|
122 | Ep: pct application non-entry in european phase |
Ref document number: 11870063 Country of ref document: EP Kind code of ref document: A1 |