Robot control system and control method
The robot control system coordinates multiple robots and devices within a production facility by using a network-connected first and second control device, ensuring efficient and scalable control through setting information transmission and command generation.
Patent Information
- Application Number
- JP2020044122
- Authority / Receiving Office
- JP · JP
- Patent Type
- Patents
- Current Assignee / Owner
- Filing Date
- 2020-03-13
- Publication Date
- 2024-12-03
- Estimated Expiration
- 2040-03-13
AI Technical Summary
Existing robot control systems are inadequate for managing multiple robots and integrated production equipment, as they do not account for the coordination and control of various devices and machines within a production facility.
A robot control system comprising a first control device and a second control device connected via a network, where the first control device stores setting information and generates commands for the second control device, allowing for coordinated control of robots and other equipment through a communication unit.
The system enables reliable control of multiple robots and devices within a production environment, distributing processing loads and enhancing scalability, while ensuring appropriate setting information is transmitted efficiently.
Smart Images

Figure 0007592975000001 
Figure 0007592975000002 
Figure 0007592975000003
Abstract
Description
[Technical field]
[0001] The present technology relates to a robot control system and a control method. [Background technology]
[0002] 2. Description of the Related Art Robots have traditionally been used in a variety of applications in the field of factory automation (FA).
[0003] Generally, a program written in a specific programming language is used to control a robot. In order to simplify the control of a robot, for example, Japanese Patent Application Laid-Open No. 2018-196908 (Patent Document 1) discloses a configuration for constructing an automated facility using a robot at low cost without having to learn a robot language. [Prior art documents] [Patent documents]
[0004] [Patent Document 1] JP 2018-196908 A Summary of the Invention [Problem to be solved by the invention]
[0005] The configuration shown in the above-mentioned prior art documents reduces construction costs by controlling the robot's operation by inputting parameters to a robot controller, rather than simply creating a program written in a robot language.
[0006] However, in actual production facilities, multiple robots are often installed. The configurations shown in the above-mentioned prior art documents do not assume the case where multiple robots are installed. Furthermore, actual production facilities are not limited to robots, and various devices and machines are combined.
[0007] The present technology aims to provide a robot control system suitable for production facilities that include one or more robots. [Means for solving the problem]
[0008] A robot control system according to an embodiment of the present technology includes a first control device and a second control device connected to the first control device via a network for controlling a robot. The first control device includes a storage unit for storing setting information related to a robot controlled by the second control device, a command generation unit for executing a robot program to sequentially generate commands to be given to the second control device, and a communication unit for transmitting the setting information and the sequentially generated commands to the second control device. The second control device includes a command value generation unit for sequentially generating command values for driving each axis of the robot according to a command from the first control device, with reference to the setting information transmitted in advance from the first control device.
[0009] According to this configuration, the first control device provides the setting information necessary for the second control device to generate command values, thereby ensuring control of the robot in coordination with the first control device and the second control device.
[0010] The first control device may transmit the setting information to the second control device when a predetermined condition is satisfied. According to this configuration, when transmission of the setting information is required, the setting information can be transmitted.
[0011] The predetermined condition may include that the first control device has started up. With this configuration, when the first control device starts up, the setting information can be reliably transmitted to the second control device.
[0012] The predetermined condition may include that the second control device is connected to the first control device via a network. According to this configuration, when the second control device is connected to the first control device via a network, the setting information can be reliably transmitted to the second control device.
[0013] The first control device may transmit the setting information to the second control device in accordance with a command from an external device connected to the first control device. With this configuration, when a command is received from the external device, the setting information can be reliably transmitted to the second control device.
[0014] The first control device may transmit the setting information stored in the storage unit of the first control device to the second control device, even if the setting information is stored in advance in the second control device. With this configuration, appropriate setting information can be provided to the second control device without evaluating the suitability of the setting information stored in advance in the second control device.
[0015] The first control device may transmit to the second control device a difference between the setting information previously stored in the second control device and the setting information to be stored in the second control device. With this configuration, the amount of data of information transmitted from the first control device to the second control device can be reduced.
[0016] The robot control system may include a plurality of second control devices. The storage unit of the first control device may store setting information for each of the plurality of second control devices. With this configuration, even if the plurality of second control devices are connected to a network, appropriate setting information can be provided to each of the second control devices.
[0017] A control method according to an embodiment of the present technology is directed to a robot control system including a first control device and a second control device connected to the first control device via a network for controlling a robot. The control method includes a step in which the first control device transmits setting information related to a robot controlled by the second control device to the second control device, a step in which the first control device executes a robot program to sequentially generate commands to be given to the second control device, a step in which the first control device transmits the setting information and the sequentially generated commands to the second control device, and a step in which the second control device sequentially generates command values for driving each axis of the robot by referring to the setting information in accordance with the commands from the first control device. Effect of the Invention
[0018] According to the present technology, it is possible to realize a robot control system suitable for production equipment including one or more robots. [Brief description of the drawings]
[0019] [Figure 1] 1 is a schematic diagram showing an overview of a robot control system according to an embodiment of the present invention; [Diagram 2] 1 is a schematic diagram showing a configuration example of a robot control system according to an embodiment of the present invention; [Diagram 3] FIG. 2 is a schematic diagram showing an example of a hardware configuration of a control device that constitutes the robot control system according to the present embodiment. [Figure 4] FIG. 2 is a schematic diagram showing an example of a hardware configuration of a robot constituting the robot control system according to the present embodiment. [Diagram 5] FIG. 11 is a schematic diagram showing another example of the hardware configuration of the robot constituting the robot control system according to the present embodiment. [Figure 6] 2 is a schematic diagram showing an example of a hardware configuration of an operation pendant that constitutes the robot control system according to the present embodiment. FIG. [Figure 7] FIG. 2 is a schematic diagram illustrating an example of a hardware configuration of a support device that constitutes the robot control system according to the present embodiment. [Figure 8] FIG. 2 is a schematic diagram showing an example of a functional configuration for controlling the behavior of a robot in the robot control system according to the present embodiment. [Figure 9] FIG. 2 is a diagram showing an example of an IEC program and a robot program executed by a control device constituting the robot control system according to the present embodiment. [Figure 10] 4 is a time chart showing an example of program execution in a control device constituting the robot control system according to the present embodiment. [Figure 11] FIG. 2 is a schematic diagram outlining data processing in an initial state in the robot control system according to the present embodiment. [Figure 12] It is a schematic diagram outlining data processing in the operating state in the robot control system according to this embodiment. [Figure 13] It is a diagram showing an example of setting information used in the robot control system according to this embodiment. [Figure 14] It is a diagram showing another example of setting information used in the robot control system according to this embodiment. [Figure 15] It is a diagram showing an example of transmission conditions in the robot control system according to this embodiment. [Figure 16] It is a diagram showing another example of transmission conditions in the robot control system according to this embodiment. [Figure 17] It is a diagram showing yet another example of transmission conditions in the robot control system according to this embodiment. [Figure 18] It is a sequence diagram showing the transmission process of setting information in the robot control system according to this embodiment. [Figure 19] It is a flowchart showing the processing procedure during operation in the control device constituting the robot control system according to this embodiment. [Figure 20] It is a flowchart showing the processing procedure during operation in the robot controller constituting the robot control system according to this embodiment.
Embodiments for Carrying Out the Invention
[0020] Embodiments of this technology will be described in detail with reference to the drawings. For the same or corresponding parts in the drawings, the same reference numerals are given and their descriptions will not be repeated.
[0021] <A. Application Examples> First, an example of the scenario to which this technology is applied will be described. FIG. 1 is a schematic diagram showing an overview of the robot control system 1 according to this embodiment.
[0022] 1, the robot control system 1 includes a control device 100 (first control device) and a robot controller 250 (second control device) that is network-connected to the control device 100 via a field network 20 and controls a robot 200. Note that a plurality of robot controllers 250 may be connected to the control device 100.
[0023] In the following description, a configuration example of the robot control system 1 that mainly controls the robot 200 is shown, but the control target of the robot control system 1 is not limited to the robot 200. For example, the control device 100 can control, in addition to the robot 200, various devices and machines that constitute a production facility including the robot 200. Furthermore, the control device 100 may be linked to a safety controller that monitors the operation of the robot 200. In other words, in this specification, the term "robot control system" is used to mean a system that has a function of controlling a robot, and does not exclude the control of things other than robots.
[0024] The control device 100 has a storage 110 (storage unit) that stores setting information 2704 related to the robot 200 controlled by the robot controller 250. The storage 110 may also store a robot program 1108. The robot program 1108 is provided to a robot program execution engine 152 (command generation unit). The robot program execution engine 152 executes the robot program 1108 to sequentially generate commands 158 to be provided to the robot controller 250.
[0025] The control device 100 has a communication unit 50 (comprised of a field network controller 108, a communication control module 160, a communication driver 162, etc., which will be described later) that transmits the setting information 2704 and the sequentially generated commands 158 to the robot controller 250.
[0026] The robot controller 250 has a command value generation module 290 (command value generation unit) that sequentially generates command values for driving each axis of the robot with reference to the setting information 2704 transmitted in advance from the control device 100 according to the command 158 from the control device 100.
[0027] Note that since the axes of the robot 200 may constitute joints, in the following description, they are also referred to as "axes or joints" of the robot 200. That is, in this specification, the term "axis" of the robot 200 is used in a meaning that includes axes and joints.
[0028] In the robot control system 1 according to the present embodiment, the control device 100 and the robot controller 250 cooperate to control the behavior of the robot 200. In adopting such a configuration, before transmitting the command 158 from the control device 100, the setting information 2704 regarding the robot 200 controlled by the robot controller 250 is transmitted to the robot controller 250, which is the transmission destination of the command 158. Thereby, the control of the robot 200 in which the control device 100 and the robot controller 250 cooperate can be surely realized.
[0029] Also, by adopting the configuration of the robot control system 1 according to the present embodiment, the processing load can be dispersed. As a result, even if the processing capacity of the control device 100 is not high, the behaviors of a plurality of robots 200 can be controlled. In addition, since the resources of the control device 100 required to control the behavior of the robot 200 can be relatively reduced, in the control device 100, not only the processing related to the behavior of the robot 200 but also other processing can be executed, and the expandability of the system can be enhanced.
[0030] <B. System configuration example> Next, a configuration example of the robot control system 1 according to the present embodiment will be described.
[0031] FIG. 2 is a schematic diagram showing a configuration example of the robot control system 1 according to the present embodiment. Referring to FIG. 2, the robot control system 1 according to the present embodiment includes a control device 100 and one or more robots 200 connected to the control device 100 via a field network 20.
[0032] Each of the robots 200 has its behavior controlled by a robot controller 250. The robot controller 250 is network-connected to the control device 100 and controls the robot 200. More specifically, the robot controller 250 outputs a command value for controlling the robot 200 according to a command (command 158 described later) from the control device 100. As the robot 200, a custom robot 200A having one or more axes or joints arbitrarily created according to the application may be used. Further, as the robot 200, any general-purpose robot 200B such as a horizontal articulated (scalar) robot, a vertical articulated robot, a parallel link robot, or an orthogonal robot may be used.
[0033] Any devices such as an I / O unit, a safety I / O unit, and a safety controller may be connected to the field network 20. In the configuration example shown in FIG. 2, an operation pendant 300 for operating the robot 200 is connected to the field network 20.
[0034] Protocols for industrial networks such as EtherCAT (registered trademark) and EtherNet / IP can be used for the field network 20.
[0035] The control device 100 may be connected to a support device 400, a display device 500, and a server device 600 via a host network 12. Protocols for industrial networks such as EtherNet / IP can be used for the host network 12.
[0036] <C. Hardware Configuration Example> Next, an example of the hardware configuration of the main devices constituting the robot control system 1 shown in FIG. 2 will be described.
[0037] (c1: control device 100) Fig. 3 is a schematic diagram showing an example of a hardware configuration of a control device 100 constituting a robot control system 1 according to the present embodiment. Referring to Fig. 3, the control device 100 includes a processor 102, a main memory 104, a storage 110, a memory card interface 112, a host network controller 106, a field network controller 108, a local bus controller 116, and a USB controller 120 providing a USB (Universal Serial Bus) interface. These components are connected via a processor bus 118.
[0038] The processor 102 corresponds to an arithmetic processing unit that executes control calculations, and is composed of a CPU (Central Processing Unit), a GPU (Graphics Processing Unit), etc. Specifically, the processor 102 reads out a program stored in the storage 110, expands it in the main memory 104, and executes it to realize control calculations for a control target.
[0039] The main memory 104 is configured with a volatile storage device such as a dynamic random access memory (DRAM) or a static random access memory (SRAM). The storage 110 is configured with a non-volatile storage device such as a solid state drive (SSD) or a hard disk drive (HDD).
[0040] A system program 1102 for implementing basic functions, an IEC program 1104 created according to a control target, etc. are stored in the storage 110. The IEC program 1104 may include sequence instructions and / or motion instructions.
[0041] In this specification, the term "IEC program" refers to a program that defines the processing executed by a general PLC (Programmable Logic Controller). Typically, the IEC program refers to a program written in any of the languages defined in IEC 61131-3 established by the International Electrotechnical Commission (IEC). However, the IEC program may also include a program written in a manufacturer's own language other than the languages defined in IEC 61131-3.
[0042] The storage 110 may further store a robot program 1108 and setting information 1106 for controlling the behavior of the robot 200. As described below, the robot program 1108 may be written in a predetermined programming language (for example, a programming language for robot control such as V+ language or a programming language related to NC control such as G-code). The setting information 1106 includes various setting values related to the execution of the IEC program 1104 and the robot program 1108.
[0043] The storage 110 may further store a setting information group 2701, which is a collection of setting information used by the robot controller 250. The setting information constituting the setting information group 2701 is related to the robot 200 controlled by the robot controller 250, and includes various parameters for the robot 200. As will be described later, when a predetermined condition is established, the control device 100 transmits corresponding setting information from the setting information group 2701 to the robot controller 250.
[0044] The memory card interface 112 accepts a memory card 114, which is an example of a removable storage medium. The memory card interface 112 is capable of reading and writing any data from and to the memory card 114.
[0045] The upper network controller 106 is 12Data is exchanged between any information processing device (such as the support device 400, the display device 500, or the server device 600 shown in FIG. 2) via the above.
[0046] The field network controller 108 exchanges data with any device such as the robot 200 via the field network 20. In the example system configuration shown in FIG.
[0047] The local bus controller 116 transmits and receives data to and from any of the functional units 130 constituting the control device 100 via the local bus 122. The functional units 130 include, for example, an analog I / O unit responsible for input and / or output of analog signals, a digital I / O unit responsible for input and / or output of digital signals, and a counter unit that receives pulses from an encoder or the like.
[0048] The USB controller 120 transmits and receives data to and from any information processing device via a USB connection.
[0049] The functions related to the control of the robot 200 provided by the control device 100 will be described later. (c2: robot 200 and robot controller 250) Fig. 4 is a schematic diagram showing an example of the hardware configuration of the robot 200 constituting the robot control system 1 according to this embodiment. Fig. 4 shows an example of the configuration in which a custom robot 200A is adopted as the robot 200.
[0050] 4, the custom robot 200A is connected to a robot controller 250. The custom robot 200A and the robot controller 250 may be configured integrally or separately.
[0051] Custom robot 200A includes drive circuits 220 corresponding to the number of axes or joints, and motors 230 driven by drive circuits 220. Each drive circuit 220 includes a converter circuit, an inverter circuit, etc., and generates power of a specified voltage, current, and phase according to a command value from robot controller 250, and supplies it to motor 230.
[0052] Each of the motors 230 is mechanically coupled to one of the axes or joints of the arm section 210 that constitutes the custom robot 200A, and is an actuator that drives the corresponding axis or joint by the rotation of the motor 230.
[0053] As the motor 230, a motor having characteristics according to the arm unit 210 to be driven can be adopted. For example, any of an induction motor, a synchronous motor, a permanent magnet motor, and a reluctance motor may be adopted as the motor 230, and not only a rotary motor but also a linear motor may be adopted. A drive circuit 220 according to the motor 230 to be driven is adopted.
[0054] The robot controller 250 includes a field network controller 252 and a control processing circuit 260 .
[0055] The field network controller 252 mainly exchanges data with the control device 100 via the field network 20 .
[0056] The control processing circuit 260 executes calculation processing necessary to drive the custom robot 200A. As an example, the control processing circuit 260 includes a processor 262, a main memory 266, a storage 270, and an interface circuit 268.
[0057] The processor 262 executes control calculations for driving the custom robot 200A. The main memory 266 is composed of a volatile storage device such as a DRAM or an SRAM. The storage 270 is composed of a non-volatile storage device such as an SSD or an HDD.
[0058] The storage 270 stores a robot system program 2702 for implementing control for driving the robot 200, and setting information 2704 including a set of setting parameters required for processing by the robot controller 250.
[0059] The interface circuit 268 provides command values to each of the drive circuits 220. The interface circuit 268 and the drive circuits 220 may be electrically connected by a hard wire, or may be connected by a data link.
[0060] Fig. 5 is a schematic diagram showing another example of the hardware configuration of the robot 200 constituting the robot control system 1 according to the present embodiment. Fig. 5 shows an example of the configuration in which a general-purpose robot 200B is used as the robot 200.
[0061] Referring to FIG. 5, the general-purpose robot 200B incorporates one or more motors and drive circuits (not shown), and when a target trajectory for the general-purpose robot 200B is specified, it drives one or more motors according to the specified target trajectory.
[0062] When driving the custom robot 200A shown in FIG. 4, it is necessary to give command values to the drive circuits 220 corresponding to the axes or joints, whereas when driving the general-purpose robot 200B shown in FIG. 5, it is only necessary to specify the target trajectory of the general-purpose robot 200B.
[0063] The functions related to the control of the robot 200 provided by the robot controller 250 will be described later.
[0064] (c3: Operation pendant 300) 6 is a schematic diagram showing an example of a hardware configuration of an operation pendant 300 constituting the robot control system 1 according to the present embodiment. Referring to FIG. 6, the operation pendant 300 includes a field network controller 352, a control processing circuit 360, and an operation key group 380.
[0065] The field network controller 352 mainly exchanges data with the control device 100 via the field network 20 .
[0066] The control processing circuit 360 includes a processor 362 , a main memory 366 , firmware 370 , and an interface circuit 368 .
[0067] The processor 362 executes the firmware 370 to realize the processes required for the operation pendant 300. The main memory 366 is configured with a volatile storage device such as a DRAM or an SRAM, for example.
[0068] The interface circuit 368 exchanges signals with an operation key group 380 . The operation key group 380 is an input device that accepts user operations. The operation key group 380 may include an indicator that indicates an input state.
[0069] (c4: Support device 400) 7 is a schematic diagram showing an example of a hardware configuration of the support device 400 constituting the robot control system 1 according to this embodiment. As an example, the support device 400 may be realized using a general-purpose personal computer.
[0070] 7, the support device 400 includes a processor 402, a main memory 404, an input unit 406, a display unit 408, a storage 410, an optical drive 412, a USB controller 420, and a communication controller 422. These components are connected via a processor bus 418.
[0071] The processor 402 is composed of a CPU, GPU, etc., and realizes various functions required for the support device 400 by reading programs (for example, an OS 4102 and a development program 4104) stored in the storage 410, expanding them into the main memory 404, and executing them.
[0072] The main memory 404 is, for example, a volatile storage device such as a DRAM or an SRAM. The storage 410 is, for example, a non-volatile storage device such as an HDD or an SSD.
[0073] The storage 410 stores an OS 4102 for implementing basic functions, a development program 4104 for implementing a development environment, and the like. In the development environment, it is possible to create a program to be executed by the control device 100, debug the program, set up settings related to the operation of the control device 100, set up settings for the operation of devices connected to the control device 100, set up settings related to the field network 20, and the like.
[0074] The input unit 406 is configured with a keyboard, a mouse, etc., and accepts user operations. The display unit 408 is configured with a display, various indicators, etc., and displays the results of processing by the processor 402, etc.
[0075] The USB controller 420 exchanges data with the control device 100 etc. via a USB connection. The communication controller 422 exchanges data with an arbitrary information processing device via the higher level network 12.
[0076] The support device 400 has an optical drive 412, and a program stored therein is read from a storage medium 414 (e.g., an optical storage medium such as a DVD (Digital Versatile Disc)) that non-transiently stores a computer-readable program, and installed in storage 410, etc.
[0077] The development program 4104 executed by the support device 400 may be installed via a computer-readable storage medium 414, or may be installed by downloading from a server device on a network. The functions provided by the support device 400 according to this embodiment may be realized by utilizing some of the modules provided by the OS 4102.
[0078] It should be noted that the support device 400 may be detached from the control device 100 while the robot control system 1 is in operation.
[0079] (c5:Display device 500) The display device 500 constituting the robot control system 1 according to the present embodiment may be realized by using a general-purpose personal computer, for example. The basic hardware configuration of the display device 500 is similar to the hardware configuration of the support device 400 shown in Fig. 7, so a detailed description will not be given here.
[0080] (c6: server device 600) The server device 600 constituting the robot control system 1 according to the present embodiment may be realized by using a general-purpose personal computer, for example. The basic hardware configuration of the server device 600 is similar to that of the support device 400 shown in Fig. 7, and therefore will not be described in detail here.
[0081] (c7:Other forms) Although Figures 3 to 7 show configuration examples in which required functions are provided by one or more processors executing programs, some or all of these provided functions may be implemented using dedicated hardware circuits (e.g., an ASIC (Application Specific Integrated Circuit) or an FPGA (Field-Programmable Gate Array)).
[0082] The main part of the control device 100 may be realized using hardware that follows a general-purpose architecture (for example, an industrial personal computer based on a general-purpose personal computer). In this case, virtualization technology may be used to execute a plurality of operating systems with different applications in parallel and to execute the necessary applications on each operating system. Furthermore, a configuration in which functions such as the support device 400 and the display device 500 are integrated into the control device 100 may be adopted.
[0083] <D. Functional Configuration Example> An example of the functional configuration for controlling the robot 200 will be described.
[0084] FIG. 8 is a schematic diagram showing an example of the functional configuration for controlling the behavior of the robot 200 in the robot control system 1 according to the present embodiment. Referring to FIG. 8, commands 158 and the like for controlling the robot 200 are exchanged between the control device 100 and one or more robot controllers 250.
[0085] The control device 100 includes an IEC program execution engine 150, a robot program execution engine 152, a communication control module 160, a communication driver 162, and an external communication interface 164. These elements may typically be realized by the processor 102 of the control device 100 executing the system program 1102.
[0086] The IEC program execution engine 150 executes the IEC program 1104 to periodically generate output values to be given to the robot controller 250. More specifically, the IEC program execution engine 150 cyclically executes the IEC program 1104 at a predetermined control period. The control period of the control device 100 is typically assumed to be approximately several hundred μsec to several hundred msec. In accordance with the execution of the IEC program 1104, the IEC program execution engine 150 outputs internal commands (e.g., start and stop transmission of the command 158) to the robot program execution engine 152 and / or acquires status values (e.g., status of the robot program 1108 executed by the robot program execution engine 152) from the robot program execution engine 152.
[0087] The robot program execution engine 152 executes the robot program 1108 to sequentially generate commands 158 to be provided to the robot controller 250. The sequentially generated commands 158 instruct the behavior of the robot 200. In this manner, the robot program execution engine 152 sequentially executes the robot program 1108 to transmit the commands 158 for controlling the robot 200 to one or more robot controllers 250. More specifically, the robot program execution engine 152 includes a robot program interpretation module 154 and a command generation module 156.
[0088] The robot program interpretation module 154 sequentially reads and parses the robot program 1108, and outputs the internal commands obtained by parsing to the command generation module 156. The robot program interpretation module 154 can interpret commands related to signal input / output, file access, and communication in addition to commands related to the behavior of the robot 200 described in a programming language included in the robot program 1108.
[0089] The start and stop of reading the robot program 1108 by the robot program interpretation module 154 may be controlled by the command generation module 156.
[0090] The command generation module 156 generates commands 158 for each of the robot controllers 250 according to the internal commands from the robot program interpretation module 154 .
[0091] The command generation module 156 acts as a host for one or more connected robot controllers 250. More specifically, the command generation module 156 controls the start and stop of execution of the robot program 1108 in the robot program interpretation module 154 and the start and stop of generation of commands 158 for the robot controllers 250 in response to internal commands exchanged with the IEC program execution engine 150 and / or with the support device 400 via the external communication interface 164.
[0092] The command generation module 156 may collect information such as status values and errors from the robot controller 250.
[0093] For convenience of explanation, an example of a configuration in which the robot program interpretation module 154 and the command generation module 156 are separated is shown, but these modules may be implemented integrally without being separated.
[0094] The communication control module 160 and the communication driver 162 correspond to a communication unit that transmits the setting information 2704 and the sequentially generated commands 158 to the robot controller 250. The communication control module 160 and the communication driver 162 transmit the output values from the IEC program execution engine 150 and the commands 158 from the robot program execution engine 152 to the robot controller 250.
[0095] The communication control module 160 manages data exchange with one or more connected robot controllers 250. The communication control module 160 may generate a communication instance that manages data communication for each connected robot controller 250, and manage the data communication using the generated communication instance.
[0096] The communication driver 162 is an internal interface that performs data communication with one or more robot controllers 250 connected thereto, using the field network controller 108 (see FIG. 3).
[0097] Each of the robot controllers 250 includes a communication control module 280, a communication driver 282, a robot drive engine 284, and a signal output driver 292. These elements may be typically realized by the processor 262 (control processing circuit 260) of the robot controller 250 executing a robot system program 2702.
[0098] The communication control module 280 manages data exchange with the connected control device 100. The communication control module 280 may generate a communication instance that manages data communication with the connected control device 100, and manage the data communication using the generated communication instance.
[0099] The communication driver 282 is an internal interface that performs data communication with the connected control device 100 by utilizing the field network controller 252 (see FIG. 4).
[0100] The robot driving engine 284 sequentially generates command values for driving each axis of the robot 200 (including the custom robot 200A and / or the general-purpose robot 200B) in accordance with the command 158 from the control device 100 and with reference to the setting information 2704 transmitted in advance from the control device 100. More specifically, the robot driving engine 284 includes a management module 286, a target trajectory generation module 288, and a command value generation module 290.
[0101] The management module 286 corresponds to a process execution unit that executes processes according to output values from the control device 100. More specifically, the management module 286 manages the control mode and the start / end of generation of a target trajectory from the command 158 according to the output values from the control device 100. The management module 286 may hold setting information 2704 provided by the control device 100.
[0102] The target trajectory generation module 288 (target trajectory generation unit) generates a target trajectory of the robot 200 (including the custom robot 200A and / or the general-purpose robot 200B) to be controlled, in accordance with the command 158 from the control device 100 and with reference to the setting information 2704. The generated target trajectory typically includes the position of the tip of the robot 200 over time (change in position over time) and / or the speed of the tip of the robot 200 over time (change in speed over time).
[0103] The target trajectory generating module 288 may output the generated target trajectory to a command value generating module 290 (typically when driving a custom robot 200A shown in FIG. 4), or may output it directly to the robot 200 via a signal output driver 292 (typically when driving a general-purpose robot 200B shown in FIG. 5).
[0104] The command value generating module 290 sequentially generates command values for driving each axis of the robot 200 so as to realize a behavior instructed by the command 158 from the control device 100. More specifically, the command value generating module 290 sequentially generates command values for each motor 230 constituting the robot 200 to be controlled, in accordance with the target trajectory generated by the target trajectory generating module 288, while referring to the setting information 2704. The command value generating module 290 may update the command values at every predetermined control period or every predetermined event.
[0105] The command value generation module 290 calculates each command value to be given to the motor 230 for driving the robot 200 along a target trajectory based on the kinematics of the robot 200 to be controlled. The command value generation module 290 calculates a target position (change in position / angle over time), a target velocity (change in velocity / angular velocity over time), a target acceleration (change in acceleration / angular acceleration over time), and / or a target acceleration (change in acceleration / angular acceleration over time) as the command value to be given to the motor 230. Canada Calculate velocity (change in jerk / angular jerk over time), etc.
[0106] The control period of the target trajectory generating module 288 of the robot controller 250 is typically assumed to be approximately several hundred μsec to several hundred msec, which is similar to the control period of the control device 100. On the other hand, the control period of the command value generating module 290 of the robot controller 250 is assumed to be faster (for example, several to several tens of times faster) than the control period of the target trajectory generating module 288.
[0107] For convenience of explanation, an example configuration in which the target trajectory generating module 288 and the command value generating module 290 are separated is shown, but these modules may be implemented integrally without being separated.
[0108] The signal output driver 292 is an internal interface for outputting command values and / or target trajectories to one or more connected drive circuits 220 and / or robots 200 by using the interface circuit 268 (see FIG. 4).
[0109] <E. Processing Executed by Control Device 100> As described above, the robot program 1108 is a program for controlling the behavior of the robot 200. However, in order to control the behavior of the robot 200, for example, it is also necessary to control the timing of starting / stopping the operation of the robot 200, the conditions for operating the robot 200 (e.g., linkage with equipment in the previous or subsequent processes), and the safety conditions related to the robot 200.
[0110] Therefore, in the control device 100, not only the robot program 1108 but also the IEC program 1104 may be executed in parallel. The IEC program 1104 may include logic for collecting state values related to the operation of the robot 200 and determining the timing of starting / stopping the operation of the robot 200.
[0111] FIG. 9 is a diagram showing an example of the IEC program 1104 and the robot program 1108 executed by the control device 100 constituting the robot control system 1 according to the present embodiment.
[0112] FIG. 9(A) shows an example of the IEC program 1104 described in ladder diagram (LD language). The example of the IEC program 1104 shown in FIG. 9(A) includes instructions related to the process of turning on the power of the robot 200 to be controlled and the process of executing calibration of the robot 200 to be controlled.
[0113] As shown in FIG. 9(A), the IEC program 1104 may include function blocks as elements. Furthermore, the IEC program 1104 may include code described in structured text (ST language).
[0114] 9B shows an example of a robot program 1108 written in the V+ language. As shown in FIG. 9B, the V+ language is a kind of high-level language for controlling the behavior of the robot 200.
[0115] Next, the parallel execution of the IEC program 1104 and the robot program 1108 in the control device 100 will be described.
[0116] Fig. 10 is a time chart showing an example of program execution in the control device 100 constituting the robot control system 1 according to this embodiment. As shown in Fig. 10, in the control device 100, the IEC program execution engine 150 and the robot program execution engine 152 (robot program interpretation module 154 and command generation module 156) each execute processing independently.
[0117] The IEC program execution engine 150 cyclically executes (repeatedly executes) the IEC program 1104 at every predetermined control period T1. The cyclic execution of the IEC program 1104 includes an output update process 1502 and an input update process 1504.
[0118] The output update process 1502 includes a process of reflecting the output value determined by the execution of the IEC program 1104 in the internal variables and / or the target device. In particular, the output value for the device connected via the field network 20 is stored in a communication frame and transmitted onto the field network 20.
[0119] The input update process 1504 includes a process of acquiring input values (state values) required for executing the IEC program 1104 from internal variables and / or target devices. In particular, input values from devices connected via the field network 20 are acquired from communication frames propagating on the field network 20.
[0120] The communication control module 160 transmits a communication frame onto the field network 20 in synchronization with the control period T1, and receives the communication frame that has circulated around the field network 20 and returned. The communication control module 160 stores the output value generated by the IEC program execution engine 150 and / or the command 158 generated by the command generation module 156 in the communication frame, and retains the input value (status value) included in the returned communication frame so that the IEC program execution engine 150 and the command generation module 156 can refer to it.
[0121] The command generation module 156 generates the command 158 according to the internal command from the robot program interpretation module 154. Typically, the timing at which the command generation module 156 generates the command 158 is determined by an output value from the IEC program execution engine 150. In the example shown in Fig. 10, the IEC program execution engine 150 generates the command 158 in response to an output value from the IEC program execution engine 150. The generation of the command 158 by the IEC program execution engine 150 may be synchronized with the timing of the output update process 1502 of the IEC program execution engine 150.
[0122] The robot program interpretation module 154 typically executes the robot program 1108 independently of the control period T1. The start / stop of the execution of the robot program 1108 by the robot program interpretation module 154 may be controlled by the command generation module 156.
[0123] 10, the robot program execution engine 152 sequentially executes the robot program 1108. The IEC program execution engine 150 cyclically executes the IEC program 1104 independently of the execution of the robot program 1108 by the robot program execution engine 152.
[0124] <Data exchange between the control device 100 and the robot controller 250> Next, the data exchange between the control device 100 and the robot controller 250 will be described.
[0125] FIG. 11 is a schematic diagram outlining data processing in the initial state in the robot control system 1 according to the present embodiment.
[0126] Referring to FIG. 11, setting information 2704 prepared in advance for each robot 200 (robot controller 250) is input to the robot program execution engine 152 of the control device 100. When a predetermined condition is satisfied, the command generation module 156 of the robot program execution engine 152 transmits the corresponding setting information 2704 to each of the robot controllers 250. The robot drive engine 284 of the robot controller 250 stores the setting information 2704 transmitted from the control device 100.
[0127] By storing the setting information 2704 in the robot controller 250, the robot controller 250 can control the robot 200. In the operating state where the robot controller 250 controls the robot 200, a command 158 is transmitted from the control device 100 to the robot controller 250.
[0128] FIG. 12 is a schematic diagram outlining data processing in the operating state in the robot control system 1 according to the present embodiment. Referring to FIG. 12, a robot program 1108 described in a predetermined programming language is input to the robot program execution engine 152 of the control device 100.
[0129] For example, in a production facility in which a plurality of robots 200 are arranged on the same production line and each robot 200 performs a different task, a different robot program 1108 is input to the robot program execution engine 152 for each robot 200. In a production facility in which a plurality of identical production lines are arranged in parallel and each production line has a robot 200 performing the same task, a common robot program 1108 may be input to the robot program execution engine 152. However, the generated commands 158 may be transmitted to the robot controller 250 independently.
[0130] Furthermore, multiple robot programs 1108 written in different programming languages (for example, V+ language and G-code) may be input to the robot program execution engine 152. Even when robot programs 1108 written in different programming languages are input, the robot program execution engine 152 can generate commands 158 written according to a common command system.
[0131] In this way, the robot program execution engine 152 may be configured to be able to interpret multiple programming languages. In this case, the robot program execution engine 152 may generate commands 158 that comply with a predetermined command system, without depending on the programming language.
[0132] The robot program execution engine 152 (robot program interpretation module 154) interprets the input robot program 1108 and generates internal commands. Furthermore, the robot program execution engine 152 (command generation module 156) generates commands 158 for controlling the behavior of the robot 200 according to the generated internal commands.
[0133] The commands 158 may be generated for one or more connected robot controllers 250, respectively.
[0134] The generated command 158 is transmitted to the corresponding robot controller 250 via the field network 20 (see FIG. 2). When the control device 100 is network-connected to a plurality of robot controllers 250, the communication unit 50 of the control device 100 (composed of a field network controller 108, a communication control module 160, a communication driver 162, etc.) transmits the command 158 to each of the plurality of robot controllers 250.
[0135] The target trajectory generation module 288 of the robot controller 250 generates a target trajectory according to the command 158 from the control device 100. The generated target trajectory may be directly output to the general-purpose robot 200B.
[0136] On the other hand, the command value generation module 290 of the robot controller 250 generates command values for the respective motors 230 constituting the robot 200 to be controlled according to the generated target trajectory.
[0137] Note that any command system can be adopted as the command system for defining the command 158. From the viewpoint of reducing the processing related to the generation of the command 158, it is preferable to adopt a command group that can be easily generated from the instructions described in the robot program 1108.
[0138] <G. Specific Examples of Setting Information> Next, specific examples of the setting information 2704 referred to by the robot controller 250 will be described.
[0139] FIG. 13 is a diagram showing an example of the setting information 2704 used in the robot control system 1 according to the present embodiment. Referring to FIG. 13, the setting information 2704 referred to by the robot controller 250 includes parameters related to the robot 200 controlled by the robot controller 250.
[0140] For example, the setting information 2704 includes a robot type indicating the type of robot or the robot model, the number of axes of each robot, parameters of each axis, parameters of the server that drives each axis (including the number of rotations and the reduction ratio, etc.). Furthermore, the setting information 2704 includes a limit value of the robot 200. (example For example, the speed limit, the acceleration limit, the jerk limit, etc.
[0141] The setting information group 2701 stored in the control device 100 is made up of one or more pieces of setting information 2704. When a predetermined condition is met, the control device 100 transmits corresponding setting information 2704 from the setting information group 2701 to a target robot controller 250. In this way, when the robot control system 1 has multiple robot controllers 250, the setting information group 2701 made up of setting information 2704 for each of the multiple robot controllers 250 is stored in the storage 110 of the control device 100.
[0142] The robot controller 250 refers to the setting information 2704 to generate a target trajectory and / or generate a command value.
[0143] As shown in FIG. 13, setting information 2704 corresponding to each of the robot controllers 250 connected to the control device 100 may be predefined and prepared. However, if the contents of the setting information 2704 are similar to each other, default setting information may be prepared and only the difference from the default setting information may be transmitted.
[0144] Fig. 14 is a diagram showing another example of setting information used in the robot control system 1 according to this embodiment. As shown in Fig. 14, default setting information 2704A is stored in advance for each robot controller 250. Then, difference information 2704B from the default setting information 2704A may be transmitted so as to become setting information appropriate for each robot controller 250.
[0145] The robot controller 250 can generate and refer to the setting information according to the robot 200 to be controlled by applying the difference information 2704B to the default setting information 2704A.
[0146] In this way, only the difference information 2704B may be transmitted from the control device 100 to the robot controller 250. That is, the control device 100 may transmit the difference information 2704B, which is the difference between the default setting information 2704A pre-stored in the robot controller 250 and the setting information 2704 to be stored in the robot controller 250, to the robot controller 250. In the case where the default setting information 2704A is not stored in the robot controller 250, the control device 100 may transmit the default setting information 2704A to the robot controller 250.
[0147] <H. Transmission Conditions of Setting Information> As described above, when a predetermined condition (hereinafter also referred to as "transmission condition") is satisfied, the control device 100 transmits the setting information 2704 to the robot controller 250. An example of the transmission condition when the control device 100 transmits the setting information 2704 will be described.
[0148] (h1: Startup of the control device 100) For example, the startup of the control device 100 can be set as the transmission condition. That is, the transmission condition may include the startup of the control device 100. In this case, the control device 100 transmits the setting information 2704 to the robot controller 250 in the initial state immediately after the system startup.
[0149] FIG. 15 is a diagram showing an example of the transmission condition in the robot control system 1 according to the present embodiment. Referring to FIG. 15, it is assumed that the power of the control device 100 is turned on and the system starts up. At the same time, the robot controller 250 also starts up. It is assumed that the robot controller 250 is in a ready state immediately after the system startup.
[0150] The control device 100 then transmits the setting information 2704 to the robot controller 250. The robot controller 250 stores the received setting information 2704 and transitions from the ready state to the operating state. The transition to the operating state enables the robot controller 250 to control the robot 200.
[0151] (h2: Network connection) Also, the transmission condition may be that the robot 200 (robot controller 250) is connected to the network. That is, the transmission condition may include that the robot controller 250 is connected to the control device 100 through the network. More specifically, when any robot controller 250 is newly connected or reconnected to the field network 20, this triggers the control device 100 to transmit the setting information 2704 to the robot controller 250.
[0152] Fig. 16 is a diagram showing another example of the transmission conditions in the robot control system 1 according to this embodiment. With reference to Fig. 16, it is assumed that the robot 200 (robot controller 250) is connected to the field network 20 and the robot controller 250 starts up the system. It is assumed that the robot controller 250 is in a ready state immediately after the system starts up.
[0153] The control device 100 then transmits the setting information 2704 to the robot controller 250. The robot controller 250 stores the received setting information 2704 and transitions from the ready state to the operating state. The transition to the operating state enables the robot controller 250 to control the robot 200.
[0154] (h3: Instructions from external devices) Also, the transmission condition may be that an instruction is given from an external device to the control device 100. That is, the control device 100 may transmit the setting information 2704 to the robot controller 250 according to a command from an external device connected to the control device 100. For example, when an explicit instruction is given from the support device 400 to the control device 100, the control device 100 transmits the setting information 2704 to the robot controller 250 according to the instruction.
[0155] Fig. 17 is a diagram showing yet another example of the transmission conditions in the robot control system 1 according to this embodiment. Referring to Fig. 17, when a user operates the support device 400, an instruction to transmit the setting information 2704 is given to the control device 100. It is assumed that the robot controller 250 is in a ready state immediately after the system is started up.
[0156] In response to the transmission instruction from the support device 400, the control device 100 transmits the setting information 2704 to the robot controller 250. The robot controller 250 stores the received setting information 2704 and transitions from the ready state to the operating state. The transition to the operating state enables the robot controller 250 to control the robot 200.
[0157] The trigger for issuing a transmission instruction from the support device 400 to the control device 100 may be a user operation or an application executed on the support device 400. For example, after the support device 400 transfers the IEC program 1104 and the robot program 1108 to the control device 100, an instruction to transmit the setting information 2704 may also be issued to the control device 100.
[0158] (h4: Application executed by the control device 100) Alternatively, the IEC program 1104 executed by the control device 100 may satisfy the transmission condition. That is, an application executed by the control device 100 may generate a trigger for transmitting the setting information 2704.
[0159] For example, logic corresponding to the transmission condition of the setting information 2704 may be incorporated in the IEC program 1104, and when the incorporated transmission condition is satisfied, the setting information 2704 may be transmitted. In this case, any transmission condition can be specified.
[0160] (h5: Existing setting information) In the process of transmitting the setting information 2704 described above, the setting information 2704 may be transmitted regardless of whether the setting information 2704 has already been stored in the destination robot controller 250. In other words, even if the setting information 2704 has been stored in advance in the robot controller 250, the control device 100 may transmit the setting information 2704 stored in the storage 110 of the control device 100 to the robot controller 250.
[0161] On the other hand, it may be possible to determine whether or not the correct setting information 2704 is stored in the destination robot controller 250, and only if the correct setting information 2704 is not stored, transmit the setting information 2704 from the control device 100 to the robot controller 250. In this case, the control device 100 acquires information on the setting information 2704 stored in the robot controller 250 to which the setting information 2704 is to be transmitted from the robot controller 250, and transmits the setting information 2704 to the robot controller 250 if the setting information 2704 is not stored or if the stored setting information 2704 differs from the setting information 2704 to be transmitted.
[0162] In this way, the transmission condition may include a condition that the correct setting information 2704 is not stored in the destination robot controller 250.
[0163] (h6:Other) The transmission conditions are not limited to those described above, and any desired transmission conditions may be used. In addition, any desired combination of the above transmission conditions may be used. Furthermore, the transmission conditions may be different for each robot controller 250.
[0164] <I. Processing Procedure> Next, the processing procedure in the robot control system 1 according to the present embodiment will be described.
[0165] (i1: Transmission of Setting Information 2704) First, the processing related to the transmission of the setting information 2704 will be described.
[0166] FIG. 18 is a sequence diagram showing the transmission process of the setting information 2704 in the robot control system 1 according to the present embodiment. The processing of the control device 100 shown in FIG. 18 is typically realized by the processor 102 of the control device 100 executing the system program 1102. Also, the processing of the robot controller 250 shown in FIG. 18 is typically realized by the processor 262 executing the robot system program 2702.
[0167] Referring to FIG. 18, it is assumed that the robot controller 250 is in a ready state after system startup (sequence SQ200).
[0168] The control device 100 determines whether a predetermined condition (transmission condition) for transmitting the setting information 2704 is satisfied (sequence SQ100). When determining whether the transmission condition is satisfied, the control device 100 may acquire necessary information from the robot controller 250. If the transmission condition is not satisfied (NO in sequence SQ100), the following processing is skipped.
[0169] If the transmission condition is satisfied (YES in sequence SQ100), the control device 100 identifies the target robot controller 250 to be transmitted (sequence SQ102), and transmits the setting information 2704 corresponding to the identified robot controller 250 (sequence SQ104). Then, it waits for a reception completion notification from the robot controller 250 (sequence SQ106).
[0170] When the robot controller 250 receives the setting information 2704 from the control device 100 (sequence SQ202), it stores the received setting information 2704 (sequence SQ204). Then, the robot controller 250 notifies the control device 100 that reception of the setting information 2704 has been completed (sequence SQ206). Then, the robot controller 250 transitions from the ready state to the operating state (sequence SQ208).
[0171] When the control device 100 receives a reception completion notification from the robot controller 250 (YES in sequence SQ106), it ends the transmission process of the setting information 2704.
[0172] (i2: Working) Next, the process during operation after the process relating to the transmission of the setting information 2704 as described above is completed will be described.
[0173] Fig. 19 is a flowchart showing a processing procedure during operation of the control device 100 constituting the robot control system 1 according to this embodiment. Typically, each step shown in Fig. 19 may be realized by the processor 102 of the control device 100 executing the system program 1102. As shown in Fig. 19, in the control device 100, processing by the IEC program execution engine 150 and processing by the robot program execution engine 152 (robot program interpretation module 154 and command generation module 156) are executed in parallel.
[0174] As a process related to the IEC program execution engine 150, the control device 100 judges whether or not the next control period has arrived (step S100). If the next control period has not arrived (NO in step S100), the control device 100 waits for the process to arrive at the next control period.
[0175] If the next control cycle has arrived (YES in step S100), the control device 100 outputs the output value determined by the execution of the IEC program 1104 in the previous control cycle (step S102). The process of outputting the output value includes the process of outputting the output value to the robot program execution engine 152.
[0176] Next, the control device 100 acquires the latest input value (step S104), and executes the IEC program 1104 using the acquired latest input value to determine the output value (step S106). Then, the process from step S100 onward is repeated.
[0177] On the other hand, as a process related to the robot program execution engine 152, the control device 100 judges whether or not a condition for starting to read the robot program 1108 is satisfied (step S150). The condition for starting to read the robot program 1108 may be specified by appropriately combining an output value from the IEC program execution engine 150, an input value from the robot controller 250 (for example, the robot controller 250 is in an operating state), an instruction from the support device 400, and any other information.
[0178] If the condition for starting reading of the robot program 1108 is not met (NO in step S150), the control device 100 skips the processes of steps S152 and S154.
[0179] If the condition for starting to read the robot program 1108 is met (YES in step S150), the control device 100 executes the robot program 1108 to generate commands 158 instructing the robot's behavior to be given to the robot controller 250, and transmits the generated commands 158 to the robot controller 250 (steps S152 to S160).
[0180] More specifically, the control device 100 sequentially reads the target robot programs 1108 (step S152), parses the read robot programs 1108, and generates internal commands (step S154).
[0181] The control device 100 judges whether or not the output start condition of the command 158 is satisfied (step S156). The output start condition of the command 158 may be specified by appropriately combining the output value from the IEC program execution engine 150, the input value from the robot controller 250, an instruction from the support device 400, and any other information.
[0182] If the output start condition of the command 158 is satisfied (YES in step S156), the control device 100 judges whether the next control period has arrived (step S158). If the next control period has not arrived (NO in step S158), the control device 100 waits for the next control period to arrive before carrying out processing.
[0183] If the next control cycle has arrived (YES in step S158), the control device 100 generates and outputs the command 158 in accordance with a previously generated internal command (step S160).
[0184] If the output start condition of the command 158 is not satisfied (NO in step S156), the control device 100 skips the processes of steps S158 and S160.
[0185] Then, the processes from step S150 onwards are repeated. 20 is a flowchart showing a processing procedure during operation of the robot controller 250 constituting the robot control system 1 according to this embodiment. Each step shown in FIG. 20 may be realized by the processor 262 (control processing circuit 260) of the robot controller 250 executing the robot system program 2702.
[0186] As shown in Fig. 20, in the robot controller 250, a process by the target trajectory generating module 288 and a process by the command value generating module 290 are executed in parallel. The process shown in Fig. 20 is executed when the robot controller 250 is in an operating state. In other words, it is executed only when the setting information 2704 from the control device 100 is stored.
[0187] As part of the process related to the target trajectory generating module 288, the robot controller 250 determines whether or not the command 158 has been received from the control device 100 (step S200). If the command 158 has not been received from the control device 100 (NO in step S200), the robot controller 250 repeats the process of step S200.
[0188] If the command 158 has been received from the control device 100 (YES in step S200), the robot controller 250 judges whether or not the entire command 158 has been received (step S202). If only a part of the command 158 has been received (NO in step S202), the robot controller 250 repeats the processes from step S200 onward.
[0189] If all of the commands 158 have been received (YES in step S202), the robot controller 250 generates a target trajectory in accordance with the received commands 158 while referring to the setting information 2704 (step S204). Then, the processes from step S200 onwards are repeated.
[0190] On the other hand, as a process related to the command value generating module 290, the robot controller 250 judges whether the next control period has arrived (step S250). If the next control period has not arrived (NO in step S250), the robot controller 250 waits for the process to arrive at the next control period.
[0191] If the next control cycle has arrived (YES in step S250), the robot controller 250 stores a predetermined latest input value in the communication frame To and transmits it to the control device 100 (step S252). Then, the robot controller 250 acquires the latest output value transmitted from the control device 100 with reference to the communication frame 40 (step S254). Then, the robot controller 250 determines whether or not the output condition of the command value for the robot 200 is satisfied (step S256). The output condition of the command value for the robot 200 may be defined by appropriately combining the latest output value transmitted from the control device 100, the state value held by the management module 286, the state value acquired by the robot controller 250, and any other information.
[0192] If the output condition of the command value for the robot 200 is not satisfied (NO in step S256), the robot controller 250 skips the processes of steps S258 and S260.
[0193] If the output condition of the command value for the robot 200 is satisfied (YES in step S256), the robot controller 250 sequentially generates command values for driving each axis of the robot 200 so as to realize the behavior instructed by the command 158 from the control device 100 (steps S258 to S260). More specifically, the robot controller 250 generates command values for each motor 230 constituting the robot 200 to be controlled while referring to the setting information 2704 according to the target trajectory generated in advance (step S258). Then, the robot controller 250 outputs each generated command value (step S260).
[0194] Then, the processes below step S250 are repeated. <J. Appendix> The present embodiment as described above includes the following technical ideas.
[0195] [Configuration 1] A robot control system (1), A first control device (100); a second control device (250) connected to the first control device through a network for controlling the robot; The first control device includes: A storage unit (110) for storing setting information (2704) related to a robot (200) controlled by the second control device; a command generation unit (152) for sequentially generating commands (158) to be given to the second control device by executing a robot program (1108); a communication unit (50) that transmits the setting information and the sequentially generated commands to the second control device; The second control device includes: a command value generating unit (290) that sequentially generates command values for driving each axis of the robot in accordance with a command from the first control device and with reference to setting information transmitted in advance from the first control device.
[0196] [Configuration 2] 2. The robot control system of claim 1, wherein the first control device transmits the setting information to the second control device when a predetermined condition is satisfied.
[0197] [Configuration 3] 3. The robot control system of claim 2, wherein the predetermined condition includes that the first control device has been started up.
[0198] [Configuration 4] 4. The robot control system of configuration 2 or 3, wherein the predetermined condition includes that the second control device is network-connected to the first control device.
[0199] [Configuration 5] The robot control system according to any one of configurations 1 to 4, wherein the first control device transmits the setting information to the second control device in accordance with an instruction from an external device (400) connected to the first control device.
[0200] [Configuration 6] The robot control system according to any one of configurations 1 to 5, wherein the first control device transmits setting information stored in the memory unit of the first control device to the second control device even if setting information is stored in advance in the second control device.
[0201] [Configuration 7] The robot control system according to any one of configurations 1 to 5, wherein the first control device transmits to the second control device a difference (2704B) between setting information (2704A) pre-stored in the second control device and setting information to be stored in the second control device.
[0202] [Configuration 8] the robot control system includes a plurality of the second control devices, 8. The robot control system according to any one of configurations 1 to 7, wherein the storage unit of the first control device stores setting information for each of the plurality of second control devices.
[0203] [Configuration 9] A control method for a robot control system (1) including a first control device (100) and a second control device (250) connected to the first control device via a network and for controlling a robot (200), comprising: A step (SQ104) in which the first control device transmits setting information (2704) related to the robot controlled by the second control device to the second control device; A step (S160) in which the first control device executes a robot program (1108) to sequentially generate commands (158) to be given to the second control device; A step (S160) in which the first control device transmits the setting information and the sequentially generated commands to the second control device; The control method includes steps (S258, S260) in which the second control device sequentially generates command values for driving each axis of the robot with reference to the setting information according to a command from the first control device.
[0204] <K. Advantage> In the robot control system 1 according to the present embodiment, the control device 100 and the robot controller 250 cooperate to control the behavior of the robot 200. When adopting such a configuration, before transmitting the command 158 from the control device 100, the setting information 2704 regarding the robot 200 controlled by the robot controller 250 is transmitted to the robot controller 250 which is the transmission destination of the command 158. Thereby, the control of the robot 200 in which the control device 100 and the robot controller 250 cooperate can be surely realized.
[0205] The embodiments disclosed this time should be considered as illustrative in all respects and not restrictive. The scope of the present invention is shown not by the above description but by the claims, and it is intended that all modifications within the meaning and scope equivalent to the claims are included.
Explanation of Reference Numerals
[0206] 1 Robot control system, 12 Upper-level network, 20 Field network 、50 Communication unit, 100 Control device, 102, 262, 362, 402 Processor, 104, 266, 366, 404 Main memory, 106 Upper network controller, 108, 252, 352 Field network controller, 110, 270, 410 Storage, 112 Memory card interface, 114 Memory card, 116 Local bus controller, 118, 418 Processor bus, 120, 420 USB controller, 122 Local bus, 130 Functional unit, 150 IEC program execution engine, 152 Robot program execution engine, 154 Robot program interpretation module, 156 Command generation module, 158 Command, 160, 280 Communication control module, 162, 282 Communication driver, 164 External communication interface, 200 Robot, 200A Custom robot, 200B General-purpose robot, 210 Arm unit, 220 Drive circuit, 230 Motor, 250 Robot controller, 260, 360 Control processing circuit, 268, 368 Interface circuit, 284 Robot drive engine, 286 Management module, 288 Target trajectory generating module, 290 Command value generating module, 292 Signal output driver, 300 Operation pendant, 370 Firmware, 380 Operation key group, 400 Support device, 406 Input unit, 408 Display unit, 412 Optical drive, 414 Storage medium, 422 Communication controller, 500 Display device, 600 Server device, 1102 System program, 1104 IEC program, 1106, 2704, 2704A Setting information, 1108 Robot program, 1502 Output update processing, 1504 Input update processing, 2701 Setting information group, 2702 Robot system program, 2704B Difference information, 4104 Development program, T1 control cycle.
Claims
1. 1. A robot control system, comprising: A first control device; a second control device connected to the first control device through a network for controlling the robot; The first control device includes: A storage unit that stores setting information related to a robot controlled by the second control device; a command generation unit that executes a robot program to sequentially generate commands to be provided to the second control device; a communication unit that transmits the setting information and the sequentially generated commands to the second control device; The second control device includes: a command value generating unit that sequentially generates command values for driving each axis of the robot in accordance with a command from the first control device and with reference to setting information transmitted in advance from the first control device; When a predetermined condition is satisfied, the first control device transmits the setting information to the second control device; A robot control system, wherein the predetermined condition includes at least one of the first control device being started up and the second control device being network-connected to the first control device.
2. The robot control system according to claim 1 , wherein the first control device transmits the setting information to the second control device in accordance with a command from an external device connected to the first control device.
3. 3. The robot control system according to claim 1, wherein the first control device transmits setting information stored in the memory unit of the first control device to the second control device even if setting information is stored in advance in the second control device.
4. The robot control system according to any one of claims 1 to 3, wherein the first control device transmits to the second control device a difference between setting information pre-stored in the second control device and setting information to be stored in the second control device.
5. the robot control system includes a plurality of the second control devices, 5. The robot control system according to claim 1, wherein the storage unit of the first control device stores setting information for each of the plurality of second control devices.
6. A control method for a robot control system including a first control device and a second control device that is connected to the first control device via a network and controls a robot, comprising: The first control device stores setting information related to a robot controlled by the second control device; The first control device executes a robot program to sequentially generate commands to be provided to the second control device; the first control device transmitting the configuration information and the sequentially generated commands to the second control device; a step of the second control device referring to the setting information in accordance with a command from the first control device and sequentially generating command values for driving each axis of the robot; the step of the first control device transmitting the setting information and the sequentially generated commands to the second control device includes a step of transmitting the setting information to the second control device when a predetermined condition is satisfied; A control method, wherein the predetermined condition includes at least one of the first control device being started up and the second control device being connected to the first control device via a network.
Citation Information
Patent Citations
Controller for industrial robot
JP1992279901A
Control method for robot
JP1993204439A
Robot control apparatus, holding unit control device, robot, holding unit, robot control method and program
JP2015186834A
Control system and mounting device
JP2018196908A
Control device
JP2019036043A
