CABLE CONNECTION VERIFICATION SYSTEM, METHOD, AND PROGRAM

[0001] This application is based upon and claims the benefit of priority from Japanese Patient application No. 2014-207992, filed on Oct. 9, 2014, the entire contents of each of which are incorporated herein by reference.

[0002] 1. Technical Field

[0003] Embodiments of the present invention relate to a cable connection verification technique for use in an operation of electrically cable-connecting contacts on terminal blocks spaced away from each other.

[0004] 2. Description of the Related Art

[0005] In field work and inspection at a power plant and the like, an operation of electrically connecting pieces of equipment by thousands of cables is carried out.

[0006] Such a cable connection verification operation is carried out by operators positioned at opposite ends of the cables. The operators locate the cables to be checked and test the cables using a circuit tester while communicating each other through voice communication devices.

[0007] When a detection value of the circuit tester matches a resistance value of the cable, continuity between contacts is verified and a drawing (connection diagram) is marked out, thereby leaving evidence of the operation.

[0008] Also, a technique is proposed which verifies cable connection by affixing tags from which ID information such as a two-dimensional code or RFID is extractable near contacts on terminal blocks or near cable terminals (see, for example, Japanese Patent Laid-Open No. 2009-273347).

[0009] The above-mentioned connection verification performed by extracting the ID information from the tags affixed to a cable or terminal blocks merely proves that cable terminals and terminal block contacts are combined and connected according to design specifications. Conventionally, for evidence which confirms the continuity of connected cables, a record of the connection diagrams marked out by operators is relied on giving low objectivity in proving continuity and giving rise to the possibility of human errors.

[0010] Embodiments of the present invention have been implemented in view of the above circumstances and have an object to provide a cable connection verification technique capable of bearing out continuity between contacts on two terminal blocks coupled via terminals on opposite ends of cables, and thereby leaving evidence.

[0011] A cable connection verification system according to an embodiment of the present invention includes: a transmitter configured to transmit an inspection signal to a first terminal of a cable, the cable being configured to connect a first contact on a first terminal block with the first terminal and to connect a second contact on a second terminal block with a second terminal; a receiver configured to receive the inspection signal from the second terminal of the cable; and a tag generator configured to generate a tag containing ID information upon reception of the inspection signal at the receiver.

[0019] Embodiments of the present invention will be described below with reference to the accompanying drawings. The embodiments of the present invention provide a cable connection verification technique capable of bearing out continuity between contacts on two terminal blocks coupled via terminals on opposite ends of cables, and thereby leaving evidence.

[0020] As shown in FIG. 1, a cable connection verification system 10 according to a first embodiment includes: an inspection signal transmitter 21 configured to transmit an inspection signal to a first terminal 14a of a cable 13 connecting a contact 12a on a first terminal block 11a and a contact 12b on a second terminal block 11b with each other; an inspection signal receiver 22 configured to receive the inspection signal from a second terminal 14b of the cable 13; and a tag generator 24 configured to generate a tag 23 containing ID information upon reception of the inspection signal.

[0021] Inspection signal transmitter 21, inspection signal receiver 22 and tag generator 24 may be realized with a central processing unit (CPU) includes an electronic circuit that can execute predetermined program codes. Inspection signal transmitter 21, inspection signal receiver 22 and tag generator 24 may be configured as a unit or a computer that is realized by hardware processing with the use of an electronic circuit such as ASIC (application specific integrated circuit) or FPGA (field-programmable gate array), or may be configured as a unit or a computer that is realized by a combination of software and hardware processing. Furthermore, tag generator 24 may be realized with a hardware such as a printer, a printer and its associated electronic circuit including but not limited to an IC, a CPU, an ASIC and/or an FPGA.

[0022] The terminal blocks 11 (11a and 11b) are provided on control devices (not shown) or a distribution board (not shown) of a plant.

[0023] Each of the terminal blocks 11 (11a and 11b) is provided with plural contacts 12 (12a or 12b), which are connected with cable terminals 14 (14a or 14b).

[0024] Note that in the embodiment, the cable terminal 14 and terminal blocks 11 are shown, by example, as being attached and detached via threaded fastening, but are not particularly limited thereto, and a one-touch lock type, for example, may be used alternatively.

[0025] Two operators each carrying an inspection terminal 20 (20a or 20b) are deployed on the sides of the terminals 14a and 14b of the cable 13, respectively.

[0026] The two operators are positioned at locations where they cannot talk to each other directly and are supposed to talk through voice communication devices. Each of the inspection terminals 20a and 20b may be provided with a voice communication function allowing the two operators to talk to each other using the inspection terminal 20a or 20b.

[0027] The inspection terminal 20a carried by one of the operators is connected with an alligator clip 15a detachably connected to the cable terminal 14a.

[0028] Through the alligator clip 15a, an analog current or voltage signal is sent as an inspection signal from the transmitter 21.

[0029] The inspection terminal 20b carried by another operator is connected with an alligator clip 15b detachably connected to the cable terminal 14b.

[0030] When the inspection signal is received by the receiver 22 through the alligator clip 15b, the tag generator 24 generates and prints a tag 23 containing ID information supplied from an ID information generator 25 or prints the ID information directly on the cable. The ID information, which is unique information including, for example, information about an identification symbol unique to a cable, an identification symbol unique to a terminal block, and an identification symbol unique to a control board, is intended to distinguish the cable from other cables.

[0031] ID information generator 25 may be realized with a central processing unit (CPU) includes an electronic circuit that can execute predetermined program codes. ID information generator 25 may be configured as a unit or a computer that is realized by hardware processing with the use of an electronic circuit such as ASIC (application specific integrated circuit) or FPGA (field-programmable gate array), or may be configured as a unit or a computer that is realized by a combination of software and hardware processing.

[0032] When attached to the tag 23 and printed by the tag generator 24 or its associated hardware, the ID information is converted into a two-dimensional code as illustrated. Besides the two-dimensional code, the ID information may be converted into a one-dimensional code, a hologram, other image information, a character string, or color information and may be included therein, but is not particularly limited thereto, and any medium may be used as long as the ID information, which is unique information, can be distinguished from other information.

[0033] While talking to each other through voice communication devices, the two operators attach the alligator clips 15 (15a and 15b) to the respective contacts 12 (12a and 12b) to be connected with the help of existing design information.

[0034] Then, if the cable 13 is connected correctly to the contacts 12 (12a and 12b) according to design information, a label-like tag 23 is genenrated, and affixed to the cable 13 near the terminal 14a to give evidence of the operation.

[0035] Now, the inspection terminals 20 (20a and 20b) connected to opposite ends of the cable 13 in the first embodiment have separate configurations, but a variation such as described below may be adopted.

[0036] That is, the opposite ends of the cable 13 are connected with inspection terminals (not shown) having a common configuration which incorporates all of the inspection signal transmitter 21, receiver 22, tag generator 24, and ID information generator 25.

[0037] Then, inspection signals may be transmitted alternately from opposite ends of the cable 13 and received at the other ends, followed by issuance of the tag 23.

[0038] Note that in the present embodiment, the tag 23 generated by the tag generator 24 and containing the ID information may be made of paper, film, or a plastic plate instead of a label. Furthermore, an electronic circuit such as a memory chip, RFID tag, or IC tag may be used as the tag 23. Alternatively, the tag 23 may be a paint, impression, or ink itself making up a character string, image, pattern, or color, which is to be painted, impressed, or printed directly on the cable 13.

[0039] Next, a second embodiment will be described with reference to FIG. 2. In FIG. 2, components or functions in common with FIG. 1 are denoted by the same reference numerals as the corresponding components or functions in FIG. 1, and redundant description thereof will be omitted.

[0040] As shown in FIG. 2, in addition to the components shown in FIG. 1, a cable connection verification system 10 according to the second embodiment further includes a registration code database 16 configured to hold information about respective registration codes of the to-be-verified contacts 12a and 12b of the first terminal block 11a and second terminal block 11b, an registration code processor 26 configured to identify the registration codes in the inspection signal received by the receiver 22, and an information linking processor 27 configured to link the ID information of the tag 23 to the registration codes identified by the registration code processor 26.

[0041] Registration code processor 26 and linking processor 27 may be realized with a central processing unit (CPU) includes an electronic circuit that can execute predetermined program codes. Registration code processor 26 and linking processor 27 may be configured as a unit or a computer that is realized by hardware processing with the use of an electronic circuit such as ASIC (application specific integrated circuit) or FPGA (field-programmable gate array), or may be configured as a unit or a computer that is realized by a combination of software and hardware processing.

[0042] Registration code database 16 may be realized with a storage device, such as a semiconductor memory or a hard disk. Alternatively, registration code database 16 may be realized with an electronic circuit that executes predetermined program codes, such as a processor. Database 16 is not limited to software processing; registration code database 16 may be for example configured as a unit or a computer that is realized by hardware processing with the use of an electronic circuit such as ASIC (application specific integrated circuit) or FPGA (field-programmable gate array), or may be configured as a unit or a computer that is realized by a combination of software and hardware processing.

[0043] The registration codes, for example, are character symbols given beforehand as design information to identify the first terminal block contact 12a, cable 13, and second terminal block contact 12b as shown in FIG. 5.

[0044] The registration code database 16 (FIG. 2) holding the registration codes is installed in a management space 17 different from a field space which houses, for example, the terminal blocks 11 (11a and 11b) and the like.

[0045] FIG. 6 shows a display screen 30 in a display unit (not shown) of the inspection terminal 20.

[0046] A data transmitter/receiver 28a of the inspection terminal 20a (FIG. 2) acquires the registration codes (FIG. 5) of the contacts 12 from the registration code database 16 and displays the registration codes on the display screen 30. Data transmitter/receiver 28a may be an electronic circuit comprising an antenna and an IC or a processor capable of transmitting/receiving wireless signals such as radio waves, ultrasonic waves or optical signals. The processor of data transmitter/receiver 28b may be configured as a unit or a computer that is realized by hardware processing with the use of an electronic circuit such as ASIC (application specific integrated circuit) or FPGA (field-programmable gate array), or may be configured as a unit or a computer that is realized by a combination of software and hardware processing.

[0047] On the display screen 30, for the registration codes of the cables 13, the registration codes of the first cable terminals 14a are listed in a FROM field and the registration codes of the second cable terminals 14b are listed in a TO field.

[0048] When a pair of terminals 14 (14a and 14b) to be inspected is specified on the display screen 30 (FIG. 6), an inspection signal generator 29 generates an inspection signal by encoding the registration codes of the cable terminals 14 (14a and 14b) and cable 13.

[0049] Inspection signal generator 29 may be realized with a central processing unit (CPU) includes an electronic circuit that can execute predetermined program codes. Inspection signal generator 29 may be configured as a unit or a computer that is realized by hardware processing with the use of an electronic circuit such as ASIC (application specific integrated circuit) or FPGA (field-programmable gate array), or may be configured as a unit or a computer that is realized by a combination of software and hardware processing.

[0050] The inspection signal generated in this way is a pulsed digital signal, and is transmitted to the first cable terminal 14a from the transmitter 21 and received by the receiver 22 connected to the second cable terminal 14b.

[0051] When the inspection signal is received by the receiver 22, the tag generator 24 generates and prints the tag 23 containing the ID information supplied by the ID information generator 25.

[0052] At the same time, the registration code processor 26 identifies the registration codes of the cable terminals 14 (14a and 14b) and cable 13 included in the inspection signal received by the receiver 22.

[0053] Then, the information linking processor 27 links the identified registration codes to the ID information supplied by the ID information generator 25.

[0054] The link results are transmitted to the registration code database 16 by the data transmitter/receiver 28b, and the registration codes of the contacts 12 (12a and 12b) and the ID information of the tag 23 are held by being associated with each other as shown in FIG. 5. Data transmitter/receiver 28b may be an electronic circuit comprising an antenna and an IC or a processor capable of transmitting/receiving wireless signals such as radio waves, ultrasonic waves or optical signals. The processor of data transmitter/receiver 28b may be configured as a unit or a computer that is realized by hardware processing with the use of an electronic circuit such as ASIC (application specific integrated circuit) or FPGA (field-programmable gate array), or may be configured as a unit or a computer that is realized by a combination of software and hardware processing.

[0055] As a variation, opposite ends of the cable 13 may be connected with inspection terminals (not shown) having a common configuration which incorporates all of the inspection signal transmitter 21, inspection signal generator 29, receiver 22, tag generator 24, ID information generator 25, registration code processor 26, information linking processor 27, and data transmitter/receiver 28, and inspection signals may be transmitted alternately from the opposite ends of the cable 13 and received at the other ends, followed by issuance of the tag 23.

[0056] Thus, the second embodiment can leave evidence of a cable connection verification operation in conjunction with registration codes, which provide design information.

[0057] Next, a third embodiment will be described with reference to FIG. 3. In FIG. 3, components or functions in common with FIG. 1 are denoted by the same reference numerals as the corresponding components or functions in FIG. 1, and redundant description thereof will be omitted.

[0058] In a cable connection verification system 10 according to the third embodiment, the inspection terminal 20a connected to the first terminal 14a of the cable 13 includes a registration code database 16 configured to hold information about respective registration codes of the to-be-verified contacts 12a and 12b of the first terminal block 11a and second terminal block 11b, a generator 29 configured to generate an inspection signal by encoding the registration codes, a transmitter 21a configured to transmit the inspection signal to the first cable terminal 14a, a receiver 22a configured to receive the inspection signal returned from the second cable terminal 14b on the first cable terminal 14a, a tag generator 24 configured to generate a tag 23 containing ID information upon reception of the inspection signal, an registration code processor 26 configured to identify the registration codes in the inspection signal received by the receiver 22a, and an information linking processor 27 configured to link the ID information of the tag 23 to the registration codes identified by the registration code processor 26.

[0059] An interface 31a transmits the inspection signal transmitted from the transmitter 21a to the clip 15a and transmits the inspection signal transmitted from the inspection terminal 20b connected to the second cable terminal 14b, to the receiver 22a. Interface 31a may be realized with a circuit board comprising an input port, an output port and an electronic circuit, or a central processing unit (CPU) includes an electronic circuit that can execute predetermined program codes. Interface 31a may be configured as a unit or a computer that is realized by hardware processing with the use of an electronic circuit such as ASIC (application specific integrated circuit) or FPGA (field-programmable gate array), or may be configured as a unit or a computer that is realized by a combination of software and hardware processing.

[0060] The inspection terminal 20b includes a receiver 22b configured to receive the inspection signal transmitted from the first cable terminal 14a on the second cable terminal 14b and a transmitter 21b configured to return the inspection signal to the first cable terminal 14a upon reception of the inspection signal by the receiver 22b.

[0061] An interface 31b transmits the inspection signal transmitted from the transmitter 21b to the clip 15b and transmits the inspection signal transmitted from the clip 15a to the receiver 22b. Interface 31b may be realized with a circuit board comprising an input port and an output port, or a central processing unit (CPU) includes an electronic circuit that can execute predetermined program codes. Interface 31b may be configured as a unit or a computer that is realized by hardware processing with the use of an electronic circuit such as ASIC (application specific integrated circuit) or FPGA (field-programmable gate array), or may be configured as a unit or a computer that is realized by a combination of software and hardware processing.

[0062] Also, although not illustrated, the inspection terminal 20b may also be provided with a tag generator configured to generate and print a tag containing ID information upon reception of an inspection signal.

[0063] The registration code database 16 may be used for data communications by being installed externally instead of being installed in the inspection terminal 20a.

[0064] Thus, according to the third embodiment, by merely transmitting an inspection signal from the first terminal 14a, bidirectional signal propagation can be verified, making it possible to leave evidence of a cable connection verification operation.

[0065] Next, a fourth embodiment will be described with reference to FIG. 4. In FIG. 4, components or functions in common with FIG. 1 are denoted by the same reference numerals as the corresponding components or functions in FIG. 1, and redundant description thereof will be omitted.

[0066] A cable connection verification system 10 according to the fourth embodiment is equipped with a verification terminal 40 which includes an image generator 41 configured to pick up image data of the tag 23 affixed near the cable terminal 14, an ID information processor 42 configured to extract ID information from the image data, and a comparator 44 configured to determine whether the ID information extracted from the image data is consistent or inconsistent with the ID information held in the registration code database 16 and linked to the registration code.

[0067] Image generator 41 may be realized with a camera including a semiconductor chip such as CCD or COMS, an optical unit such as a series of lens and a central processing unit (CPU) includes an electronic circuit that can execute predetermined program codes. The processing unit of image generator 41 may be configured as a unit or a computer that is realized by hardware processing with the use of an electronic circuit such as ASIC (application specific integrated circuit) or FPGA (field-programmable gate array), or may be configured as a unit or a computer that is realized by a combination of software and hardware processing.

[0068] ID information generator 42 may be realized with a central processing unit (CPU) includes an electronic circuit that can execute predetermined program codes. Image generator 41 and ID information generator 42 may be configured as a unit or a computer that is realized by hardware processing with the use of an electronic circuit such as ASIC (application specific integrated circuit) or FPGA (field-programmable gate array), or may be configured as a unit or a computer that is realized by a combination of software and hardware processing.

[0069] Note that according to the fourth embodiment, besides the tag 23 of the cable 13, a tag 18 associated with the registration code of the contact 12 is affixed to the terminal block 11.

[0070] It is assumed that the registration code of the contact 12 and ID information of the tag 18 are associated with each other in advance and held in the registration code database 16. Here, the tag 18 may be something printed on a label, paper, a plate, or film; or a code, a character string, an image, or color information painted, impressed, or printed directly on the terminal block 11. Also, using image information obtained by photographing the terminal block 11 as the tag 18, position of the contact 12 may be read by comparing the image information with image information about the terminal block 11 held in the registration code database 16 in advance by being associated with the registration code of the contact 12.

[0071] The ID information associated with the terminal block contact 12 and the ID information associated with the cable terminal 14 have been linked to each other through a process of the second embodiment or third embodiment.

[0072] The verification terminal 40 is suitably implemented by a portable tablet terminal equipped with a camera (image generator 41) as well as with a monitor (display unit 30) configured to display video, but is not particularly limited thereto. In the case of a tablet terminal, for example, the image generator 41 and display unit 30 may be provided on opposite planes.

[0073] The image generator 41 picks up image data of states of the tags 23 affixed to plural cables 13 and plural tags 18 affixed to the contacts 12 of the terminal block 11.

[0074] Then, the image data is additionally registered in a registration code table (FIG. 5) in the registration code database 16 via the communications unit 28c and allowed to be viewed on the display unit 30 (see FIG. 6), leaving evidence of a cable connection verification operation.

[0075] The processor 42 extracts ID information from the tags 18 and 23 which, being contained in the image data picked up, have a correspondence with each other, links the ID information, and transmits the ID information to the comparator 44.

[0076] Note that although in the embodiment, each terminal block contact 12 is identified using a tag 18, the terminal block contact 12 may be identified by positional information in image data using a feature point.

[0077] The data transmitter/receiver 28c acquires ID information about the terminal block contact 12 and the ID information about cable terminals 14, linked to each other, from the registration code database 16 and transmits the ID information to the comparator 44.

[0078] The comparator 44 determines whether the pair of linked pieces of ID information transmitted from the processor 42 and the pair of linked pieces of ID information transmitted from the communications unit 28c are consistent or inconsistent with each other.

[0079] Comparator 44 may be realized with a central processing unit (CPU) includes an electronic circuit that can execute predetermined program codes. Comparator 44 may be configured as a unit or a computer that is realized by hardware processing with the use of an electronic circuit such as ASIC (application specific integrated circuit) or FPGA (field-programmable gate array), or may be configured as a unit or a computer that is realized by a combination of software and hardware processing.

[0080] Then, a consistency/inconsistency result is displayed on the display unit 30 via an output 45 and additionally registered in the registration code table (FIG. 5) in the registration code database 16 via the communications unit 28c.

[0081] If an inconsistency result is displayed here, the operator is reminded that a tag 23 generated by the tag generator 24 has been erroneously affixed to a wrong cable 13.

[0082] Note that in the embodiment, the inspection terminal 20 (FIGS. 2 and 3) and verification terminal 40 (FIG. 4) are configured to be separate members, but may be configured to be an integral member.

[0083] Furthermore, a fifth embodiment will be described with reference to FIG. 4.

[0084] According to the fifth embodiment, a tag 19 used to identify the inspection terminal 20 is affixed to the clip 15a connected to the terminal 14 to transmit an inspection signal to the cable 13.

[0085] Then, the processor 42 also extracts the ID information of the tag 19 affixed to the clip 15a from the image data picked up by the image generator 41.

[0086] The comparator 44 determines consistency/inconsistency of only a linked pair accompanied by the ID information of the tag 19 which identifies the clip 15a, and the display unit 30 displays a verification result.

[0087] Furthermore, at least one of the image generator 41, processor 42, and comparator 44 of the verification terminal 40 is configured to operate only during a period in which the tag 23 is generated and the transmitter 21a and receiver 22a (FIG. 3) are transmitting and receiving inspection signals.

[0088] Consequently, in a cable connection verification operation, since evidence is collected by keeping mechanical connections while inspection signals are being transmitted and received, it is possible to more securely prevent errors from getting mixed in the collected evidence.

[0089] Now, operation of the cable connection verification systems according to the third and fourth embodiments will be described with reference to a flow chart of FIG. 7 (see FIGS. 3 to 5 as appropriate).

[0090] During construction of a power plant, the contacts 12a and 12b of the terminal blocks 11a and 11b are connected via the cable 13 (S11). The operator connects the two terminals 14a and 14b of the cable 13 with the inspection terminals 20a and 20b, respectively (S12).

[0091] By referring to a table (FIG. 5) displayed on the screen, the operator selects the contacts 12a and 12b to be checked for continuity and acquires corresponding registration codes from the registration code database 16 (S13 and S14).

[0092] An inspection signal including the acquired registration codes is generated by the generator 29 and transmitted to the cable terminal 14a by the transmitter 21a (S15).

[0093] When the inspection signal returned from the inspection terminal 20b connected to the second cable terminal 14b is received by the receiver 22a of the inspection terminal 20a connected to the first cable terminal 14a (S16: Yes), continuity between the contacts 12a and 12b is verified.

[0094] When continuity between the contacts 12a and 12b is not confirmed, cable connection is checked again (S16: No; S11).

[0095] On the inspection terminal 20a which has received the returned inspection signal, the registration code processor 26 identifies registration codes included in the inspection signal (S17), and the tag generator 24 generates and prints a tag 23 containing ID information (S18). The ID information of the tag 23 is registered by being linked to the registration codes in the registration code database 16 (S19).

[0096] On the other hand, the operator affixes the generated tag 23 near the cable terminal 14a (S20), starts up the verification terminal 40, and picks up image data including the identification tag 18 of the contact 12 and identification tag 23 of the cable terminal 14 (S21).

[0097] Then, by extracting ID information of the identification tag 18 of the contact 12 and ID information of the identification tag 23 of the cable terminal 14 from the image data (S22), it is determined whether the extracted ID information is consistent or inconsistent with the pair of linked pieces of ID information in the registration code database 16 (S23).

[0098] If a determination result indicates consistency (S23: Yes), the result is additionally registered together with the registration codes in the registration code database 16 and left as evidence (S24).

[0099] On the other hand, if the determination result indicates inconsistency, it is likely that the tag 23 has been affixed to a wrong cable 13, and an error message is outputted, promoting the operator to affix the tag anew (S23: No; S25, S20).

[0100] As the tag generated by verifying transmission and reception of inspection signals is affixed to the connected cable, the cable connection verification system according to at least one of the embodiments described above can bear out continuity between contacts on two terminal blocks and thereby leave evidence.

[0101] Whereas a few embodiments of the present invention have been described, these embodiments are presented only by way of example, and not intended to limit the scope of the invention. These embodiments can be implemented in various other forms, and various omissions, replacements, changes, and combinations can be made without departing from the spirit of the invention. Such embodiments and modifications thereof are included in the spirit and scope of the invention as well as in the invention set forth in the appended claims and the scope of equivalents thereof.

[0102] Also, the components of the cable connection verification system can be implemented by a computer processor and operated by a cable connection verification program.