Elevator maintenance device

Abstract

This universal update device comprises: a storage for storing a program that is to update a target device, and at least one communication protocol used in the target device; a first connector connected to a connector of the target device through a cable, the first connector including a plurality of connection elements, the plurality of connection elements including a first connection element group connected to a first interface of the target device and a second connection element group connected to a second interface, which is different from the first interface, of the target device; and a controller for periodically scanning the first connector, the controller receiving, in response to detecting that the first connector is connected to the first or second interface, a communication protocol of the connected first or second interface and information of a microcontroller unit that corresponds to the connected first or second interface, and updating the microcontroller unit on the basis of the received communication protocol and information.

Description

Elevator maintenance device

[0001] The present disclosure relates to an elevator maintenance device.

[0002] In order to update the program of the elevator system (e.g., control panel) that controls the operation of the elevator car, 1) the elevator manufacturer or management company internally transmits the program for performing the update to the on-site technician via email, etc., 2) the on-site technician saves the program in an update device, and 3) visits the site, connects the update device to the control panel, and updates the program of the control panel.

[0003] Figure 1 is a block diagram illustrating a method for updating a program in a conventional elevator control panel. Referring to Figure 1, each of the multiple control panels may use a printed circuit board (PCB) of a different standard. For example, each control panel may have different interfaces, connectors, and protocols. In one example, not only the control panel but also the inverter and door inverter that drive the elevator may use printed circuit boards (PCBs) of different standards.

[0004] Updating programs on PCBs with different specifications requires the use of update devices tailored to each specification. Therefore, the need for multiple update devices presents a challenge. Furthermore, the update program must be stored on each update device, and the update device containing the program must be transported to the control panel. Furthermore, sharing the program for performing the update via email can pose security concerns.

[0005] Prior literature

[0006] Korean Patent No. 10-0346282

[0007] Korean Patent No. 10-2230118

[0008] Korean Patent Publication No. 10-2001-0009830

[0009] Korean Patent Publication No. 10-2018-0005690

[0010] The present disclosure provides an elevator maintenance device capable of responding to various substrates constituting a control panel, for example, a universal update device.

[0011] In one aspect of the present disclosure, a universal update device includes: a storage configured to store a program for updating a target device and at least one communication protocol used in the target device; a first connector configured to be connected to a connector of the target device via a cable, the first connector including a plurality of connection elements, the plurality of connection elements including a first group of connection elements configured to be connected to a first interface of the target device and a second group of connection elements configured to be connected to a second interface of the target device different from the first interface, wherein the first group of connection elements and the second group of connection elements share at least one connection element; a controller configured to periodically scan the first connector, the controller receiving, in response to detecting that the first connector is connected to the first or second interface, a communication protocol of the connected first or second interface and information of a microcontroller unit corresponding to the connected first or second interface, and updating the microcontroller unit based on the received communication protocol and the information.

[0012] In one embodiment, the universal update device further comprises a second connector configured to be connected to a connector interface different from the first and second interfaces, and the controller may be further configured to periodically scan the second connector while periodically scanning the first connector, and, in response to detecting that the second connector is connected to the connector interface, receive a communication protocol of the connected connector interface and information of a microcontroller unit corresponding to the connected connector interface, and update the microcontroller unit based on the received communication protocol and the information.

[0013] In one embodiment, the plurality of connecting elements further include a third group of connecting elements, wherein the third group of connecting elements may not share connecting elements with the first and second groups of connecting elements.

[0014] In one embodiment, the third group of connecting elements may be configured to monitor the target device and be used for configuration of the target device.

[0015] In one embodiment, the third group of connecting elements may be configured to connect to the target device, receive authentication information of the target device, and use it to verify whether the target device is a valid terminal.

[0016] In one embodiment, the controller may be configured to update a microcontroller unit corresponding to the first interface in response to the first group of connecting elements being connected to the first interface, and to update a microcontroller unit corresponding to the interface in response to the third group of connecting elements being connected to the corresponding interface.

[0017] In one embodiment, the first group of connecting elements and the second group of connecting elements may be connecting elements for using different protocols.

[0018] In one embodiment, the first group of connecting elements and the second group of connecting elements may be connecting elements for using the same protocol.

[0019] In one embodiment, the controller may be configured to update a microcontroller unit corresponding to the first interface in response to the first group of connecting elements being connected to the first interface, and to update a microcontroller unit corresponding to the second interface in response to the second group of connecting elements being connected to the second interface.

[0020] In one aspect of the present disclosure, a method for updating a microcontroller unit included in a target device includes: periodically scanning, by a controller, a first connector of an update device, wherein the first connector includes a plurality of connecting elements, the plurality of connecting elements including a first group of connecting elements configured to be connected with a first interface of the target device and a second group of connecting elements configured to be connected with a second interface of the target device different from the first interface, wherein the first group of connecting elements and the second group of connecting elements share at least one connecting element; detecting, by the controller, that the first group of connecting elements is electrically connected to the first interface; stopping, by the controller, a scan of the first group of connecting elements in response to the detection; continuously performing, by the controller, a scan of the second group of connecting elements; and updating, by the controller, a microcontroller unit corresponding to the first interface via the first group of connecting elements.

[0021] In one embodiment, the method may further include: after the step of continuously performing a scan for the second group of connecting elements by the controller, the step of detecting, by the controller, that the second group of connecting elements is electrically connected to the second interface; the step of stopping, by the controller, the scan for the second group of connecting elements in response to the detection; and the step of updating, by the controller, a microcontroller unit corresponding to the first interface through the second group of connecting elements.

[0022] In one embodiment, the step of updating the microcontroller unit corresponding to the first interface through the first connection element group by the controller may include the step of receiving a communication protocol of the first interface and information of the microcontroller unit through the first interface; and the step of automatically updating the microcontroller unit based on the communication protocol and the information.

[0023] In one aspect of the present disclosure, a method for updating a microcontroller unit included in a target device includes: periodically scanning, by a controller, a first connector of the update device, wherein the first connector includes a plurality of connecting elements, the plurality of connecting elements including a first group of connecting elements configured to be connected with a first interface of the target device and a second group of connecting elements configured to be connected with a second interface of the target device different from the first interface, wherein the first group of connecting elements and the second group of connecting elements share at least one connecting element; detecting, by the controller, that the first group of connecting elements is electrically connected to the first interface; stopping, by the controller, a scan of the first group of connecting elements in response to the detection; continuously performing, by the controller, a scan of the second group of connecting elements; and providing, by the controller, a user interface that allows monitoring the target device and performing settings of the target device through the first group of connecting elements.

[0024] In one embodiment, the method may further include: after the step of continuously performing a scan for the second group of connecting elements by the controller, the step of detecting, by the controller, that the second group of connecting elements is electrically connected to the second interface; the step of stopping, by the controller, the scan for the second group of connecting elements in response to the detection; and the step of updating, by the controller, a microcontroller unit corresponding to the first interface through the second group of connecting elements.

[0025] By connecting to various boards of the control panel with a single update device, the program can be updated to improve user convenience.

[0026] You can manage log history and improve file security by updating the control panel program based on the cloud.

[0027] By enabling updates using a single device instead of multiple different devices, resource efficiency is improved, reducing raw material consumption and waste generation. Consequently, this contributes to reducing carbon emissions.

[0028] Figure 1 is a block diagram showing a method for updating a program of a conventional elevator control panel.

[0029] FIG. 2 is a block diagram showing a method for updating a program of a target device according to one embodiment of the present disclosure.

[0030] FIG. 3 is a block diagram of an update device according to one embodiment of the present disclosure.

[0031] FIG. 4 is a schematic diagram of a pin arrangement of a connector according to one embodiment of the present disclosure.

[0032] FIGS. 5a, 6a, 7a, 8a, 9a and 10a illustrate the concept of connection between a connector and a target device according to one embodiment of the present disclosure.

[0033] FIGS. 5b, 6b, 7b, 8b, 9b and 10b illustrate examples of signals applied to a connecting element of a connector according to one embodiment of the present disclosure.

[0034] FIGS. 5c to 5d, 6c, 7c, 8c to 8f, 9c to 9d and 10b illustrate examples of signals applied to a connecting element of a connector of a target device according to one embodiment of the present disclosure.

[0035] FIG. 11 is an example of a flowchart of a method for updating a program of a target device using an update device according to one embodiment of the present disclosure.

[0036] Below, with reference to the attached drawings, embodiments of the present disclosure are described in detail so that those skilled in the art can easily implement the present disclosure. However, the present disclosure may be implemented in various different forms and is not limited to the embodiments described herein.

[0037] And in order to clearly explain the present disclosure in the drawings, parts unrelated to the explanation are omitted, and similar parts are given similar drawing reference numerals throughout the specification.

[0038] Throughout the specification, whenever a part is said to "include" a component, this does not mean that it excludes other components, but rather that it may include other components, unless otherwise stated.

[0039] It should be understood that the technology described in this disclosure is not intended to be limited to a particular embodiment, but rather encompasses various modifications, equivalents, and / or alternatives of the embodiments of this disclosure.

[0040] The expression "configured to" as used herein may be used interchangeably with, for example, "suitable for", "having the capacity to", "designed to", "adapted to", "made to", or "capable of", depending on the context. The term "configured to" may not necessarily mean only something "specifically designed to" in terms of hardware. Instead, in some contexts, the expression "a device configured to" may mean that the device is "capable of" in conjunction with other devices or components.

[0041] The prior art documents described in this disclosure are incorporated herein by reference in their entirety, and it will be understood that the contents of the prior art documents can be applied by a person having ordinary skill in the art to the parts briefly described in this disclosure.

[0042] FIG. 2 is a block diagram illustrating a method for updating a program of a target device according to an embodiment of the present disclosure. Referring to FIG. 2, a universal update device according to the present disclosure can be connected to a plurality of target devices having different specifications, thereby enabling the updating of a plurality of target devices with a single universal update device. The target devices may include devices requiring program updates, such as a control panel, an inverter for driving an elevator, a door inverter, and the like. Devices requiring program updates, such as a control panel, an inverter for driving an elevator, and a door inverter, may each have different interfaces and communication protocols.

[0043] FIG. 3 is a block diagram of an update device (300) according to one embodiment of the present disclosure. Referring to FIG. 3, the update device (300) includes a first connector (310), a second connector (320), storage (330), a controller (350), and a communication module (360).

[0044] Storage (330) is configured to store instructions. When the instructions are executed by the controller (350), the controller (350) may cause the controller (350) to perform certain operations. Storage (330) may include computer-readable storage media, such as data storage devices that are accessible by the controller (350) and provide persistent storage of data and executable instructions (e.g., software applications, programs, functions, etc.). Storage (330) includes volatile memory and non-volatile memory, fixed and removable media devices, and any suitable memory device or electronic data store that maintains data for computing device access. Database (120) may include various embodiments of random access memory (RAM), read-only memory (ROM), flash memory, and other types of storage media in various memory device configurations.

[0045] The storage (330) may include a first memory (332) and a second memory (334). The first memory (332) may be configured to store a firmware file in a format supported by the target device. The second memory (334), for example, may be an external memory and may be configured to store firmware with a larger capacity than the first memory (332).

[0046] The controller (350) may be configured to control the operation of the configuration of the update device (300), for example, the storage (330), the communication module (360), and the first and second connectors (320). In one embodiment, the controller (350) may include a first processor (352) and a second processor (354) (auxiliary processor). In one embodiment, the first processor (352) may be configured to control the operation of the second connector (320), the storage (330), the communication module (360), and the second processor (354). The first processor (352) may be configured to control the communication module (360) to perform communication with the target device. The second processor (354) may control the operation of the first connector (310) under the control of the first processor (352). The first processor (352) may be configured to control the operation of the storage (330), the communication module (360), and the second connector (320).

[0047] In one embodiment, the first processor (352) may be electrically connected to the second connector (320). The second processor (354) may be electrically connected to the first connector (310). Depending on the design of the first processor (352), the first processor (352) may not be physically electrically connected to the first connector (310), in which case the update device may further include a second processor (354) that is electrically connected to the first connector (310) and controls the first connector (310).

[0048] In another embodiment, the first processor (352) and the second processor (354) may be integrated into one processor.

[0049] In one embodiment, the second processor (354) may be configured not to control the operation of the storage (330) and communication module (360). Having only the first processor (352) communicate with the external device may be more efficient than having multiple processors each communicate with the external device.

[0050] The communication module (360) includes a module for communicating with an external device (e.g., a central management server, a cloud server, an external device, etc.). The communication module (360) is configured to allow the update device to communicate with an external device or a cloud to receive information. The communication method of the communication module (360) may use a network constructed according to GSM (Global System for Mobile communication), CDMA (Code Division Multi Access), HSDPA (High Speed ​​Downlink Packet Access), HSUPA (High Speed ​​Uplink Packet Access), LTE (Long Term Evolution), LTE-A (Long Term Evolution-Advanced), etc.), WLAN (Wireless LAN), Wi-Fi (Wireless-Fidelity), Wi-Fi (Wireless Fidelity) Direct, DLNA (Digital Living Network Alliance), WiBro (Wireless Broadband), WiMAX (World Interoperability for Microwave Access), 5G wireless communication network, etc., but is not limited thereto and may include all transmission method standards to be developed in the future. It can include anything that can send and receive data via wired or wireless means.

[0051] In one embodiment, the communication module (360) may be configured to receive a firmware file and transmit / receive control and status information for performing a firmware update of the target device. For example, the communication module (360) may be configured to receive firmware data from an external device, such as a central management server or a cloud server, and transmit current firmware information of the update device (300) to the external device.

[0052] According to one embodiment, the first connector (310) and the second connector (320) may be configured to automatically recognize an interface, protocol, etc. used by the target device in response to being connected to the target device.

[0053] In one embodiment, the first connector (310) may be configured to connect with a connector of a target device (not shown). The first connector (310) may be configured to include a plurality of pins. Since the connector of the target device may be configured to have various interfaces, the plurality of pins may have an arrangement that allows them to be connected to various interfaces. In one embodiment, one first connector (310) may have an arrangement that allows them to be connected to target devices, each having a different interface. In one embodiment, one first connector (310) may have an arrangement that allows them to be connected to a plurality of different interfaces of one target device, respectively.

[0054] In one embodiment, the interface or communication protocol connected to the first connector (310) may include JTAG, SWD, ezPORT, UART, CAN, LCD-MATRIX. The interface connected to the second connector (320) may include UART.

[0055] The first connector (310) is configured to automatically recognize the target device in response to being connected to the target device via a cable (not shown). In one embodiment, the controller (350) is configured to periodically scan the first connector (310). For example, the second processor (354) is configured to periodically scan the first connector (310). In response to the target device being connected to the first connector (310) during the scan, the second processor (354) can receive the type, interface, protocol, etc. of the target device through the first connector (310). For example, the second processor (354) can receive the ID or user ID (UID) of the chip installed in the target device. In addition, the second processor (354) can receive the current program (e.g., firmware, etc.) information (e.g., version, whether update is required, etc.) of the target device from the target device. The second processor (354) can update the target device using firmware stored in the update device or firmware stored in an external device based on the type, interface, protocol, and program information of the target device and the current update device.

[0056] The second connector (320) is configured to automatically recognize the target device in response to being connected to the target device via a cable (not shown). The second connector (320) may be configured to be connected to a UART interface of the target device. In one embodiment, the controller (350) is configured to periodically scan the second connector (320). For example, the first processor (352) is configured to periodically scan the second connector (320). In response to the target device being connected to the second connector (320) during the scan, the first processor (352) may receive the type, interface, protocol, etc. of the target device through the second connector (320). For example, the first processor (352) may receive an ID (e.g., product ID) or user ID (UID) of a chip installed in the target device. In addition, the first processor (352) may receive current program (e.g., firmware, etc.) information of the target device from the target device. The first processor (352) can update the target device using firmware stored in the update device or firmware stored in an external device based on the type, interface, protocol, and program information of the target device and the current update device.

[0057] FIG. 4 is a schematic diagram of a pin arrangement of a connector (310) according to one embodiment of the present disclosure. Although FIG. 4 illustrates the first connector (310) as having 30 pins, it will be appreciated that the number of pins of the first connector (310) is exemplary and may vary. Furthermore, it will be appreciated that the pins of the first connector (310) may be replaced with pin holes into which the pins can be inserted. Accordingly, the pins of the first connector (310) may be referred to as connection elements. Referring to FIG. 4, a first connector (310) includes a housing (402) and connection elements (404). A plurality of connection elements (e.g., pins or pin holes) are arranged within the housing (402). The housing is attached to a substrate (not shown) of the update device (300). It will be appreciated that the connection elements are numbered in FIG. 4 for illustrative purposes.

[0058] Figures 5a, 6a, 7a, 8a, 9a, and 10a illustrate concepts of connection between a connector and a target device according to one embodiment of the present disclosure. Figures 5b, 6b, 7b, 8b, 9b, and 10b illustrate examples of signals applied to a connection element of a connector according to one embodiment of the present disclosure. Figures 5c to 5d, 6c, 7c, 8c to 8f, 9c to 9d, and 10b illustrate examples of signals applied to a connection element of a connector of a target device according to one embodiment of the present disclosure.

[0059] In one embodiment, when a target device has two controller units (e.g., micro controller units (MCUs)) that need to be updated, a first connector (310) and connectors (515, 525) of the target device may be connected using a single cable (500) as illustrated in FIG. 5A. That is, each of the connectors (515, 525) of the target device may correspond to each of the MCUs of the target device. Referring to FIG. 5A, the cable (500) includes a connector (505) corresponding to the first connector (310), connectors (510, 520) corresponding to the connectors (515, 525) of the target device, lines (502) connected to the connector (505), and lines (512, 522) connected to each of the connectors (515, 525) of the target device.

[0060] The connector (510) may include connecting elements corresponding to and electrically connected to the connecting elements of the connector (515). Each connecting element of the connector (510) may be connected to lines (512) for transmitting / receiving electrical signals. The connector (520) may include connecting elements corresponding to and electrically connected to the connecting elements of the connector (525). Each connecting element of the connector (520) may be connected to lines (522) for transmitting / receiving electrical signals. As illustrated in FIGS. 5b to 5d, the pin numbers (PIN NO.) of the lines (502) and the cable numbers (CABLE NO.) of the lines (512, 522) may be electrically connected to correspond to each other.

[0061] In one embodiment, the connecting elements of the first connector (310) may be configured to perform the functions illustrated in FIG. 5B, corresponding to the first connector (310) being connected to the connector (515) and / or the connector (525) via the cable (500). The pin numbers in FIG. 5B may correspond to the numbers illustrated in FIG. 4. The cable numbers in FIG. 5B may correspond to the lines (502). The pin numbers in FIG. 5C may correspond to each of the connecting elements of the connector (515). The cable numbers in FIG. 5C may correspond to the pin numbers of the first connector (310). For example, the connecting elements of the connector (515) may be electrically connected to the connecting elements of the first connector (310) corresponding to the cable numbers in FIG. 5C. The pin numbers in FIG. 5D may correspond to each of the connecting elements of the connector (515). The cable number in FIG. 5d may correspond to the pin number of the first connector (310). For example, the connecting element of the connector (515) may be electrically connected to the connecting element of the first connector (310) corresponding to the cable number in FIG. 5d.

[0062] As can be seen in FIGS. 5C and 5D, the connector (515) and the connector (525) have different interfaces, and thus, the required protocols may be different. Referring to FIGS. 5A to 5C, the connection element of the first connector (310) may be electrically connected to the connector (515) and the connector (525) having different interfaces to perform communication. Referring to FIG. 5B, pin numbers 1, 11, 13, 17, and 29 of the first connector (310) may be commonly connected to the connector (515) and the connector (525). That is, the connector (515) and the connector (525) may be connected to share pin numbers 1, 11, 13, 17, and 29 of the first connector (310) using a cable (500).

[0063] In other words, in one embodiment, the connecting elements of the first connector (310) may include a group of connecting elements (e.g., pin numbers 1, 11, 13, 17, 29 here) that can be shared with a plurality of connectors (515, 525) having different interfaces, a group of connecting elements (e.g., pin numbers 7, 9, 15 here) that can be electrically connected to any one of the plurality of connectors (515, 525) having different interfaces, and a group of unused connecting elements (pin numbers corresponding to '-' in FIG. 5b).

[0064] Referring to FIG. 6A, when a target device has one controller unit (e.g., a micro controller unit (MCU)) that needs to be updated, a first connector (310) and a connector (615) of the target device can be connected using a single cable (600) as illustrated in FIG. 6A. The cable (600) includes a connector (605) corresponding to the first connector (310), a connector (610) corresponding to the connector (615) of the target device, lines (602) connected to the connector (605), and lines (612) connected to the connector (615) of the target device.

[0065] The connector (610) may include connecting elements corresponding to and electrically connected to the connecting elements of the connector (615). Each connecting element of the connector (610) may be connected to lines (612) for transmitting / receiving electrical signals. As illustrated in FIGS. 6b to 6c, the pin numbers (PIN NO.) of the lines (602) and the cable numbers (CABLE NO.) of the lines (612) may be electrically connected to correspond to each other.

[0066] In one embodiment, the connecting elements of the first connector (310) may be configured to perform the functions illustrated in FIG. 6B, corresponding to the first connector (310) being connected to the connector (615) via the cable (600). The pin numbers of FIG. 6B may correspond to the numbers illustrated in FIG. 4. The cable numbers of FIG. 6B may correspond to the lines (602). The pin numbers of FIG. 6C may correspond to each of the connecting elements of the connector (615). The cable numbers of FIG. 6C may correspond to the pin numbers of the first connector (310). For example, the connecting elements of the connector (615) may be electrically connected to the connecting elements of the first connector (310) corresponding to the cable numbers of FIG. 6C.

[0067] It will be appreciated that the functions of the connecting elements of the first connector (310) illustrated in FIG. 6B can be performed simultaneously with the functions of the connecting elements illustrated in FIG. 5B. That is, the first connector (310) can be connected simultaneously, individually, and sequentially with a time difference to the connectors (515, 525, and 615) illustrated in FIGS. 5A and 6A. Accordingly, it will be appreciated that when using the update device according to the present disclosure, multiple MCUs can be updated by simultaneously, individually, and sequentially connecting other connectors having different interfaces with a time difference using the first connector (310).

[0068] For example, the connection elements of the first connector (310) may include connection elements shared with a plurality of connectors (515, 525, 615) having different interfaces, a group of connection elements electrically connected to any two of the plurality of connectors (515, 525, 615) having different interfaces, a group of connection elements electrically connected to any one of the plurality of connectors (515, 525, 615) having different interfaces, and a group of connection elements that are not used.

[0069] Referring to FIGS. 5b, 5d, 6b to 6c, power-related connection elements (e.g., pin 1, pin 29) and reset signal connection elements (e.g., pin 17) are shared. However, data-transmitting connection elements (e.g., pin 9, pin 15, pin 21, pin 23) are not shared.

[0070] Referring to FIG. 7A, when a target device has one controller unit (e.g., a micro controller unit (MCU)) that needs to be updated, a first connector (310) and a connector (715) of the target device can be connected using a single cable (700) as illustrated in FIG. 7A. The interface of the connector (715) is different from the interface of the connector (615). The cable (700) includes a connector (705) corresponding to the first connector (310), a connector (710) corresponding to the connector (715) of the target device, lines (702) connected to the connector (705), and lines (712) connected to the connector (715) of the target device.

[0071] The connector (710) may include connecting elements corresponding to and electrically connected to the connecting elements of the connector (715). Each connecting element of the connector (710) may be connected to lines (712) for transmitting / receiving electrical signals. As illustrated in FIGS. 7b to 7c, the pin numbers (PIN NO.) of the lines (702) and the cable numbers (CABLE NO.) of the lines (712) may be electrically connected to correspond to each other.

[0072] It will be appreciated that the functions of the connecting elements of the first connector (310) illustrated in FIG. 7B can be performed simultaneously with the functions of the connecting elements illustrated in FIGS. 5B and / or 6B. That is, the first connector (310) can be connected simultaneously, individually, and sequentially with a time difference to the connectors (515, 525, 615, and 715) illustrated in FIGS. 5A, 6A, and 7A. Accordingly, it will be appreciated that when using the update device according to the present disclosure, multiple MCUs can be updated by simultaneously, individually, and sequentially connecting other connectors having different interfaces with a time difference using the first connector (310).

[0073] Referring to FIGS. 7a and 7b, the connector (715) is configured to use pin numbers 2, 4, 6, 8, 10, 12, 14, 16, 18, 20, 22, 24, and 29 of the first connector (310). Pin numbers 2, 4, 6, 8, 10, 12, 14, 16, 18, 20, 22, and 24 of the first connector (310) are not used for connection with the connectors (515, 525, and 615).

[0074] That is, in one embodiment, for example, the connection elements of the first connector (310) may include connection elements shared with a plurality of connectors (515, 525, 615) having different interfaces, connection elements electrically connected to any two of the plurality of connectors (515, 525, 615) having different interfaces, connection elements electrically connected to any one of the plurality of connectors (515, 525, 615, 715) having different interfaces, and unused connection elements. In addition, pin 29 for ground connection may be commonly used by the connectors (515, 525, 615, 715).

[0075] Referring to FIG. 8A, when a target device has five controller units (e.g., micro controller units (MCUs)) that need to be updated, the first connector (310) and four connectors (815, 825, 835, 845, 855) of the target device can be connected using one cable (800) as shown in FIG. 8A. Alternatively, when a target device has three controller units that need to be updated, the first connector (310) can be connected to any one of the connectors (815, 825) and the connectors (835, 845, 855) of the target device using one cable (800). The interfaces of the five connectors (815, 825, 835, 845, 855) are different from each other and also different from the interface of the connector (615). Connectors (835, 845, 855) are all connectors that use the CAN protocol, and only the interface may be different.

[0076] Referring to FIGS. 8A to 8F, connectors (835, 845, 855) can all be connected to pins 25 and 27 of the first connector (310) using the CAN protocol. Connectors (815, 825) can share some pins (e.g., 17 and 29) of the first connector (310).

[0077] In one embodiment, it will be appreciated that the functions of the connecting elements of the first connector (310) illustrated in FIG. 8B can be performed simultaneously with the functions of the connecting elements illustrated in FIGS. 5B, 6B, and / or 7B. That is, the first connector (310) can be connected simultaneously, individually, and sequentially with a time difference to at least two of the connectors (515, 525, 615, 715, 815, 826, 835, 845, 855) illustrated in FIGS. 5A, 6A, 7A, and 8A. Accordingly, it will be appreciated that when using the update device according to the present disclosure, multiple MCUs can be updated by simultaneously, individually, and sequentially connecting other connectors having different interfaces using the first connector (310) with a time difference.

[0078] Referring to FIG. 9A, when one target device has two controller units (e.g., micro controller units (MCUs)) that need to be updated, a first connector (310) and connectors (915, 925) of the target device can be connected using one cable (900) as illustrated in FIG. 9A. That is, each of the connectors (915, 925) of the target device can correspond to each of the MCUs of the target device. Referring to FIG. 9A, the cable (900) includes a connector (905) corresponding to the first connector (310), connectors (910, 920) corresponding to the connectors (915, 925) of the target device, lines (902) connected to the connector (905), and lines (912, 922) connected to each of the connectors (915, 925) of the target device.

[0079] The connector (910) may include connecting elements corresponding to and electrically connected to the connecting elements of the connector (915). Each connecting element of the connector (910) may be connected to lines (912) for transmitting / receiving electrical signals. The connector (920) may include connecting elements corresponding to and electrically connected to the connecting elements of the connector (925). Each connecting element of the connector (920) may be connected to lines (922) for transmitting / receiving electrical signals. As illustrated in FIGS. 9b to 9d, the pin numbers (PIN NO.) of the lines (902) and the cable numbers (CABLE NO.) of the lines (912, 922) may be electrically connected so as to correspond.

[0080] In one embodiment, the connecting elements of the first connector (310) may be configured to perform the functions illustrated in FIG. 5B, corresponding to the first connector (310) being connected to the connector (915) and / or the connector (925) via the cable (900). For example, the connecting elements of the connector (915) may be electrically connected to the connecting elements of the first connector (310) corresponding to the cable numbers of FIG. 9C. The pin numbers of FIG. 9D may correspond to each of the connecting elements of the connector (915). The cable numbers of FIG. 9D may correspond to the pin numbers of the first connector (910). For example, the connecting elements of the connector (915) may be electrically connected to the connecting elements of the first connector (310) corresponding to the cable numbers of FIG. 9D.

[0081] As can be seen in FIGS. 9C and 9D , connectors (915) and connectors (925) have different interfaces and thus may require different protocols. In one embodiment, connectors (915) and connectors (925) may not share the pins of the first connector (310).

[0082] In one embodiment, the arrangement of the connecting elements of the connectors (515, 525, 615, 715, 815, 826, 835, 845, 855, 915, 925) illustrated in FIGS. 5a, 6a, 7a, 8a, 9a may be combined. In addition, the connectors (515, 525, 615, 715, 815, 826, 835, 845, 855, 915, 925) illustrated in FIGS. 5a, 6a, 7a, 8a, 9a may be selectively installed in the target device. In any case, according to the arrangement of the connecting elements of the first connector (310) of the present disclosure, connectors having different interfaces can be connected simultaneously and sequentially.

[0083] Referring to FIG. 10A, the second connector (320) is connected to the connector (1015) of the target device using a cable (1000). The second connector (320) may have a standardized interface. For example, the second connector (320) may have a UART interface. The cable (1000) may have a connector (1012) corresponding to the second connector (320), a connector (1004) corresponding to the connector (1015), and a connection line (1005). Referring to FIGS. 10B and 10C, the cable numbers in FIG. 10C may correspond to the pin numbers of the second connector (320). As can be seen in FIGS. 10B and 10C, the second connector (320) and the connector (1015) may have the same interface.

[0084] Referring again to FIGS. 4 to 10c, the plurality of connection elements of the first connector (310) may include at least one group of connection elements from among a first group of connection elements used to communicate with the target device via a first communication protocol and / or a first interface (of the target device), a second group of connection elements used to communicate with the target device via a second communication protocol and / or a second interface (of the target device), a third group of connection elements used to communicate with the target device via a third communication protocol and / or a third interface (of the target device), and a fourth group of connection elements used to communicate with the target device via a fourth communication protocol and / or a fourth interface (of the target device). In one embodiment, the first to fourth communication protocols may be different. In one embodiment, the first to fourth interfaces may be different.

[0085] In one embodiment, at least two of the first to fourth connection element groups can share connection elements included in each group. For example, at least one connection element of the first connection element group can belong to any one of the second to fourth connection element groups. For example, at least one connection element (e.g., referred to as a shared connection element) of the first connection element group can be electrically connected to the first interface and the second interface of the target device. That is, the shared connection element can be used for both the first communication protocol used for the first interface and the second communication protocol used for the second interface.

[0086] In one embodiment, a group of connection elements may not share connection elements with another group of connection elements.

[0087] In one embodiment, the interfaces of the target devices may be different even if the same communication protocol is used (e.g., see FIG. 8a).

[0088] In one embodiment, any one of the first to fourth interfaces may be an interface for connecting the update device to the target device to monitor the target device and configure the target device. For example, the target device further includes a display (not shown), and when connected to the first connector of the update device via any one of the first to fourth interfaces, a user can monitor the target device and configure the target device via the display. The plurality of connection elements may include a group of connection elements corresponding to any one of the first to fourth interfaces.

[0089] In one embodiment, any one of the first to fourth interfaces may be an interface for connecting the update device to the target device, receiving authentication information of the target device, and verifying whether the target device is a valid terminal. Accordingly, the plurality of connection elements may include a group of connection elements corresponding to any one of the first to fourth interfaces.

[0090] FIG. 11 is an example flowchart of a method for updating a program of a target device using an update device according to one embodiment of the present disclosure. It will be appreciated that the method illustrated in FIG. 11 can be implemented not only by the update device described in the present disclosure, but also by other update devices. For the sake of clarity, the drawing symbols used in the present disclosure are used in the following description.

[0091] Referring to FIG. 11, in block S1105, the controller (350) periodically scans the connection elements of the first connector (310). The controller (350) may periodically scan the connection elements of the first connector (310) to detect whether the first connector (310) is connected to at least one of various connectors (515, 525, 615, 715, 815, 826, 835, 845, 855, 915, 925) of the target device. In one embodiment, the first processor (352) or the second processor (354) may scan the connection elements of the first connector (310).

[0092] In one embodiment, scanning of pins related to power may not be performed.

[0093] In block S1110, the controller (350) determines that at least one of the connectors (515, 525, 615, 715, 815, 826, 835, 845, 855, 915, 925) of the target device is connected to the connection element of the first connector (310). In response to the controller (350) determining that at least one of the connectors (515, 525, 615, 715, 815, 826, 835, 845, 855, 915, 925) of the target device is not connected to the connection element of the first connector (310), the controller (350) returns to block S1105 and periodically scans the connection elements of the first connector (310). In response to the controller (350) determining that at least one of the connectors (515, 525, 615, 715, 815, 826, 835, 845, 855, 915, 925) of the target device is connected to the connecting element of the first connector (310), the controller (350) performs blocks S1115 and S1120.

[0094] In block S1115, the controller (350) stops scanning for a connection element connected to at least one of the connectors (515, 525, 615, 715, 815, 826, 835, 845, 855, 915, 925) of the target device. In block S1120, the controller (350) continuously performs scanning without stopping for a connection element not connected to at least one of the connectors (515, 525, 615, 715, 815, 826, 835, 845, 855, 915, 925) of the target device.

[0095] In block S1125, (following the example described above), communication is performed with the corresponding target device through the connection element connected to the connector (715) of the target device by the controller (350). In one embodiment, the controller (350) receives information of the target device through the connection element and cable (700) connected to the connector (715) of the target device. For example, one target device may include a plurality of MCUs and connectors corresponding to each of the MCUs. Accordingly, the information of the target device received by the controller (350) may mean information of the MCU corresponding to the connector (715) of the target device connected to the first connector (310).

[0096] For example, assuming that the first connector (310) is connected to the connector (715) of the target device, the information of the target device received by the controller (350) may include product information of the MCU corresponding to the connector (715) (e.g., chip ID, user ID, etc.), the communication method (e.g., protocol, etc.) of the connector (715) connected to the first connector (310), etc.

[0097] In one embodiment, the controller (350) may receive information necessary for updating the MCU from an external device based on product information of the MCU corresponding to the connector connected to the received target device, for example, the first connector (310). Alternatively, the controller (350) may prepare information necessary for updating based on information stored in the storage (330) of the update device (300). The controller (350) may update the MCU using product information (for example, communication protocol, etc.) of the MCU corresponding to the connector connected to the first connector (310).

[0098] In one embodiment, the communication performed in block S1125 may include communication for monitoring the target device and configuring the target device. In one embodiment, the communication performed in block S1125 may include communication for connecting the update device to the target device, receiving authentication information of the target device, and verifying whether the target device is a valid terminal.

[0099] While block S1125 is being executed, block S1120, block S1130, block S1135, and block S1140 can be executed in parallel.

[0100] In block S1120, the controller (350) continuously performs a scan for connection elements that are not connected to the connector of the target device. For example, in block S1110, assuming that the controller (350) detects that the first connector (310) is connected to the connector (715) of the target device while periodically scanning pins 1 to 30, the controller (350) may stop scanning pins 4, 6, 8, 10, 12, 14, 16, 18, 20, 22, and 24, and may continue scanning the remaining pins in block S1120. In one embodiment, pins 2 and 29 are power-related pins and thus the scan may not be stopped. Alternatively, in one embodiment, pins 2 and 29 are power-related pins and thus may not require a separate scan.

[0101] In block S1130, the controller (350) determines whether another connector of the target device is connected to the connection element of the first connector (310). In response to the controller (350) determining that another connector of the target device is not connected to the connection element of the first connector (310), the controller returns to block S1120, and periodically scans the connection elements of the first connector (310) that are not connected to the connector of the target device. In response to the controller (350) determining that another connector of the target device is connected to the connection element of the first connector (310), the controller (350) performs blocks S1135 and S1140. In addition, although not shown in FIG. 11, it will be understood that the controller (350) periodically performs a scan for connection elements that are not connected to other connectors, excluding connection elements that are communicating with the target device in the S1125 block and the S1140 block, and that the MCU of the target device is updated in response to the connection of the connection elements of the first connector and the target device.

[0102] For example, in block S1135, the controller (350) may, in response to detecting that the connecting element of the connector and the connector (835) are connected, stop scanning for pins 25 and 27 and continue scanning for the remaining pins (as described above, in block S1115, scans for pins 2, 4, 6, 8, 10, 12, 14, 16, 18, 20, 22, 24, and 29 have already been stopped).

[0103] In block S1140, (following the example described above), communication is performed with the corresponding target device through the connection element connected to the connector (835) of the target device by the controller (350). In one embodiment, the controller (350) receives information of the target device through the connection element and cable (800) connected to the connector (835) of the target device. For example, one target device may include a plurality of MCUs and connectors corresponding to each of the MCUs. Accordingly, the information of the target device received by the controller (350) may mean information of the MCU corresponding to the connector (835) of the target device connected to the first connector (310).

[0104] For example, information of the target device received by the controller (350) may include product information (e.g., chip ID, user ID, etc.) of the MCU corresponding to the connector (715), a communication method (e.g., protocol, etc.) of the connector (835) connected to the first connector (310), etc.

[0105] In one embodiment, the controller (350) may receive information necessary for updating the MCU from an external device based on product information of the MCU corresponding to the connector connected to the received target device, for example, the first connector (310). Alternatively, the controller (350) may prepare information necessary for updating based on information stored in the storage (330) of the update device (300). The controller (350) may update the MCU using product information (for example, communication protocol, etc.) of the MCU corresponding to the connector connected to the first connector (310).

[0106] In one embodiment, the update device can receive data about the target device from the target device. For example, the update device can receive and store product information, program version information, and field information (e.g., address, elevator information, etc.) of the target device or transmit them to an external device. Accordingly, the update device can use the product information, program information, and field information of the target device to update or restore the information of the existing target device to the replaced target device even if the target device in the field is replaced.

[0107] The method according to the present disclosure can be implemented as a processor-readable code on a processor-readable recording medium provided in a server, system, equipment, computer, integrated control device, etc. used by a subject. The processor-readable recording medium includes all types of recording devices that store data that can be read by the processor. Examples of the processor-readable recording medium include ROM, RAM, CD-ROM, magnetic tape, floppy disk, optical data storage device, etc., and also includes those implemented in the form of a carrier wave, such as transmission via the Internet. In addition, the processor-readable recording medium can be distributed across network-connected computer systems, so that the processor-readable code can be stored and executed in a distributed manner.

[0108] The devices and methods described above may be implemented using hardware components, software components, and / or a combination of hardware components and software components. For example, the devices and components described in the embodiments may be implemented using one or more general-purpose computers or special-purpose computers, such as, for example, a processor, a controller (350), an arithmetic logic unit (ALU), a digital signal processor, a microcomputer, a field programmable array (FPA), a programmable logic unit (PLU), a microprocessor, or any other device capable of executing instructions and responding to them. The processing device may execute an operating system (OS) and one or more software applications running on the operating system. In addition, the processing device may access, store, manipulate, process, and generate data in response to the execution of the software. For ease of understanding, the processing device is sometimes described as being used alone; however, one of ordinary skill in the art will recognize that the processing device may include multiple processing elements and / or multiple types of processing elements. For example, the processing device may include multiple processors or one processor and one controller (350). Other processing configurations, such as parallel processors, are also possible.

[0109] Software may include a computer program, code, instructions, or a combination of one or more of these, which may configure a processing device to perform a desired operation or may, independently or collectively, command the processing device. The software and / or data may be permanently or temporarily embodied in any type of machine, component, physical device, virtual equipment, computer storage medium or device, or transmitted signal wave for interpretation by the processing device or for providing instructions or data to the processing device. The software may also be distributed over networked computer systems and stored or executed in a distributed manner. The software and data may be stored on one or more computer-readable recording media.

[0110] The described embodiments of the present disclosure can also be implemented in distributed computing environments, where certain tasks are performed by remote processing devices that are linked through a communications network. In a distributed computing environment, program modules may be located in both local and remote memory storage devices.

[0111] Although the embodiments described above have been described with limited drawings, those skilled in the art will appreciate that various technical modifications and variations can be applied based on the above. For example, appropriate results can still be achieved even if the described techniques are performed in a different order than described, and / or components of the described systems, structures, devices, circuits, etc. are combined or combined in a different manner than described, or are replaced or substituted with other components or equivalents.

[0112] Therefore, other implementations, other embodiments, and equivalents to the claims also fall within the scope of the claims set forth below.

Claims

1. A storage configured to store a program to update a target device and at least one communication protocol used in the target device; A first connector configured to be connected via a connector and a cable of a target device, wherein the first connector comprises a plurality of connecting elements, the plurality of connecting elements comprising a first group of connecting elements configured to be connected with a first interface of the target device and a second group of connecting elements configured to be connected with a second interface of the target device different from the first interface, wherein the first group of connecting elements and the second group of connecting elements share at least one connecting element; A controller configured to periodically scan the first connector, wherein the controller is configured to receive information of a microcontroller unit corresponding to the connected first or second interface in response to detecting that the first connector is connected to the first or second interface, and to update the microcontroller unit based on the information. Universal update device.

2. In paragraph 1, Further comprising a second connector configured to be connected to a connector interface different from the first and second interfaces; The above controller is further configured to periodically scan the first connector while periodically scanning the second connector, and, in response to detecting that the second connector is connected to the connector interface, receive information of a microcontroller unit corresponding to the connected connector interface, and update the microcontroller unit based on the information. A universal update device.

3. In paragraph 1, A universal update device, wherein the plurality of connecting elements further include a third connecting element group, wherein the third connecting element group does not share connecting elements with the first and second connecting element groups.

4. In paragraph 3, The third group of connecting elements is a universal update device configured to monitor the target device and be used for configuring the target device.

5. In paragraph 3, A universal update device configured to connect to the target device, receive authentication information of the target device, and use it to verify whether the target device is a valid terminal.

6. In paragraph 3, The above controller, In response to the first group of connecting elements being connected to the first interface, updating the microcontroller unit corresponding to the first interface, A universal update device configured to update a microcontroller unit corresponding to the interface in response to the third connecting element group being connected to the corresponding interface.

7. In paragraph 1, A universal update device, wherein the first connection element group and the second connection element group are connection elements for using different protocols.

8. In paragraph 1, A universal update device, wherein the first connection element group and the second connection element group are connection elements for using the same protocol.

9. In paragraph 1, The above controller, In response to the first group of connecting elements being connected to the first interface, updating the microcontroller unit corresponding to the first interface, A universal update device configured to update a microcontroller unit corresponding to the second interface in response to the second connection element group being connected to the second interface.

10. A step of periodically scanning, by a controller, a first connector of an update device, wherein the first connector comprises a plurality of connecting elements, the plurality of connecting elements comprising a first group of connecting elements configured to be connected with a first interface of a target device and a second group of connecting elements configured to be connected with a second interface of the target device different from the first interface, wherein the first group of connecting elements and the second group of connecting elements share at least one connecting element; A step of detecting, by the controller, that the first group of connecting elements is electrically connected to the first interface; A step of stopping scanning of the first group of connecting elements in response to the detection by the controller; - and; and - a step of sequentially performing a scan for the second group of connecting elements by the controller; A step of updating a microcontroller unit corresponding to the first interface through the first group of connecting elements by the controller, A method for updating the microcontroller unit included in the target device.

11. In paragraph 10, After the step of sequentially performing a scan for the second group of connecting elements by the above controller, A step of detecting, by the controller, that a second group of connecting elements is electrically connected to the second interface; A step of stopping scanning of the second group of connecting elements in response to the detection by the controller; Further comprising the step of updating a microcontroller unit corresponding to the first interface through the second group of connecting elements by the controller; How to update.

12. In paragraph 10, The step of updating the microcontroller unit corresponding to the first interface through the first connecting element group by the controller is: A step of receiving information of the microcontroller unit through the first interface; An update method comprising the step of automatically updating the microcontroller unit based on the above information.

13. A step of periodically scanning a first connector of an update device by a controller, wherein the first connector comprises a plurality of connecting elements, the plurality of connecting elements comprising a first group of connecting elements configured to be connected with a first interface of a target device and a second group of connecting elements configured to be connected with a second interface of the target device different from the first interface, wherein the first group of connecting elements and the second group of connecting elements share at least one connecting element; A step of detecting, by the controller, that the first group of connecting elements is electrically connected to the first interface; A step of stopping scanning of the first group of connecting elements in response to the detection by the controller; - and; and - a step of sequentially performing a scan for the second group of connecting elements by the controller; A step of providing a user interface that allows monitoring the target device and performing settings of the target device through the first group of connecting elements by the controller, A method for updating the microcontroller unit included in the target device.

14. In paragraph 13, After the step of sequentially performing a scan for the second group of connecting elements by the above controller, A step of detecting, by the controller, that a second group of connecting elements is electrically connected to the second interface; A step of stopping scanning of the second group of connecting elements in response to the detection by the controller; Further comprising the step of updating a microcontroller unit corresponding to the first interface through the second group of connecting elements by the controller; How to update.

Images