Setting support device, control method and program
The system addresses the challenge of configuring and testing motor drivers from different manufacturers by using a setting support device that simplifies the setup process through vendor-specific information and recommended parameter settings, enhancing compatibility and ease of use.
Patent Information
- Application Number
- JP2024005190
- Authority / Receiving Office
- JP · JP
- Patent Type
- Applications
- Current Assignee / Owner
- Priority Date
- 2023-05-22
- Filing Date
- 2024-01-17
- Publication Date
- 2024-12-04
AI Technical Summary
The challenge arises when different manufacturers' programmable logic controllers (PLCs) and motor drivers are used together, as the communication protocols and signal formats differ, making it difficult for users to configure and test run motors without referring to multiple manuals, especially when minimum control parameters vary by manufacturer.
A programmable logic controller system that includes a setting support device, which supports easier configuration by selecting a motor drive device through vendor-specific information, storing mapping information for communication targets, and setting recommended parameters via cyclic communication, using a configuration editing section to manage settings and write parameters to the motor drive device.
This system simplifies the setup process by providing a unified interface for multiple motor drivers from different manufacturers, reducing the complexity of configuring and testing motor drivers, and ensuring compatibility with the PLC.
Smart Images

Figure 2024167876000001_ABST
Abstract
Description
[Technical field]
[0001] The present invention relates to a setting assistance device, a control method, and a program. [Background technology]
[0002] In factory automation, a programmable logic controller (PLC) is a core controller that controls industrial machines. Most industrial machines use motors as a drive source to drive various loads. As described in Patent Document 1, a PLC communicates with a motor drive device (hereinafter referred to as a motor driver) and drives a motor connected to the motor driver. [Prior art documents] [Patent documents]
[0003] [Patent Document 1] JP 2015-012025 A Summary of the Invention [Problem to be solved by the invention]
[0004] Generally, it is recommended that the manufacturer of the PLC and the manufacturer of the motor driver are the same, but sometimes a user owns a motor driver manufactured by another manufacturer and wishes to connect it to a PLC. In this case, PLCs and multiple motor drivers manufactured by different manufacturers will be mixed. The PLC controls the motor by communicating with the motor driver, but it needs to know the communication protocol and the format of the communication signal. For example, the PLC needs to know what information is included in which bit of the communication signal. However, this becomes difficult when the manufacturer of the motor driver and the manufacturer of the PLC are different. For example, the user must refer to the PLC manual and the motor driver manual and properly set the motor driver so that the motor driver matches the PLC specifications. In particular, in order to test run a motor through a motor driver, the minimum control parameters that must be set and their recommended values differ for each motor driver or manufacturer, so it was difficult for users to mix PLCs and motor drivers manufactured by different manufacturers.
[0005] Therefore, an object of the present invention is to make it easier to set up a PLC and a motor driver than in the past. [Means for solving the problem]
[0006] The present invention relates to, for example, A programmable logic controller that acts as a master for cyclic communication; a motor drive device that functions as a slave in the cyclic communication and drives a motor based on motor control data transmitted from the master through the cyclic communication; A setting support device for supporting setting of a PLC system having a configuration editing unit that selects one of a plurality of motor driving devices, each of which is identified by vendor-specific information and product-specific information, and sets the selected motor driving device as the slave in the programmable logic controller that functions as the master; a storage unit that stores allocation information associated with vendor-specific information and multiple pieces of product-specific information, the allocation information including mapping information that maps data objects handled by the motor drive device as communication targets of the cyclic communication, and recommended values of setting parameters for the motor drive device (such as limit disable ON, a-contact, b-contact, etc.); a configuration setting unit that sets mapping of data objects to be transmitted by the master through the cyclic communication based on the mapping information included in the allocation information corresponding to a combination of vendor-specific information and product-specific information of the motor drive device set for the programmable logic controller by the configuration editing unit, and sets the master to write recommended values of the setting parameters included in the allocation information for the motor drive device to the motor drive device via message communication; The present invention provides a setting support device comprising: Effect of the Invention
[0007] According to the present invention, the setting of the PLC and the motor driver becomes easier than before. [Brief description of the drawings]
[0008] [Figure 1] Explains the PLC system. [Diagram 2] FIG. 2 is a diagram illustrating a setting support device. [Diagram 3] FIG. 2 is a diagram for explaining a basic unit. [Figure 4] FIG. 2 is a diagram for explaining a motor driver. [Diagram 5] A diagram explaining the functions of a CPU. [Figure 6] FIG. 4 is a diagram illustrating a parameter setting screen. [Figure 7] FIG. 4 is a diagram for explaining a list of parameters forming slave device information. [Figure 8] FIG. 4 is a diagram for explaining a list of options forming slave device information. [Figure 9] FIG. 11 is a diagram for explaining a list of operation sequences for forming slave device information. [Figure 10] 11 is a flowchart illustrating a parameter editing process. [Figure 11] FIG. 11 is a diagram for explaining an accompanying process associated with parameter transfer. [Figure 12] FIG. 13 is a diagram for explaining a UI associated with an associated process. [Figure 13] FIG. 4 is a diagram illustrating a parameter setting screen. [Figure 14] FIG. 4 is a diagram illustrating a parameter setting screen. [Figure 15] FIG. 4 is a diagram illustrating a parameter setting screen. [Figure 16] FIG. 4 is a diagram illustrating a parameter setting screen. [Figure 17] FIG. 4 is a diagram for explaining a list of parameters forming slave device information. [Figure 18] FIG. 4 is a diagram illustrating a parameter setting screen. [Figure 19] A diagram illustrating the UI for a single operation. [Figure 20] FIG. 4 is a diagram illustrating a tuning screen. [Figure 21] FIG. 4 is a diagram for explaining a list of tuning parameters. [Figure 22] FIG. 4 is a diagram illustrating a parameter setting screen. [Figure 23] FIG. [Figure 24] FIG. 13 is a diagram for explaining a test run screen (alarm display screen). [Diagram 25] FIG. 13 is a diagram for explaining a test run screen (alarm display screen). [Figure 26] 13 is a flowchart illustrating an alarm display process. [Figure 27] FIG. [Figure 28] FIG. [Figure 29] FIG. [Diagram 30] FIG. 2 is a diagram for explaining a communication format. [Diagram 31] FIG. 13 is a diagram illustrating a detailed setting screen. [Diagram 32] FIG. 13 is a diagram illustrating a detailed setting screen. [Diagram 33] FIG. 13 is a diagram illustrating a detailed setting screen. [Diagram 34] FIG. 13 is a diagram illustrating a detailed setting screen. [Diagram 35] FIG. [Diagram 36] FIG. 13 is a diagram illustrating a recommended value writing screen. [Figure 37] A diagram explaining the functions of a CPU. [Figure 38] 11 is a flowchart showing a communication setting method. [Figure 39] 11 is a flowchart showing a method for writing a recommended value. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS
[0009] Hereinafter, the embodiments will be described in detail with reference to the accompanying drawings. Note that the following embodiments do not limit the invention according to the claims, and not all combinations of features described in the embodiments are essential to the invention. Two or more features among the multiple features described in the embodiments may be arbitrarily combined. In addition, the same reference numbers are used for the same or similar configurations, and duplicated descriptions are omitted.
[0010] <PLCシステム> Fig. 1 shows an example of the configuration of a programmable logic controller system (hereinafter, referred to as a PLC system 1) according to an embodiment of the present invention. As shown in Fig. 1, this PLC system 1 includes a PC, which is a setting support device for editing user programs such as ladder programs, a basic unit 3, which is a PLC (Programmable Logic Controller) for comprehensively controlling various control devices installed in a factory or the like, and a plurality of motor drivers 4a to 4c. The plurality of motor drivers 4a to 4c drive motors 10a, 10b, and 10c, respectively.
[0011] The user program created by PC2, which is a setting support device, may be created using a graphical programming language such as a ladder language or a flowchart-format motion program, or may be created using a high-level programming language such as C.
[0012] In the PLC system 1, one or more extension units (for example, an I / O unit, an analog input unit, an analog output unit, a communication unit, etc.) are connected to the basic unit 3. The basic unit 3 is sometimes called a CPU unit.
[0013] The basic unit 3 has a display unit 5 and an operation unit 6. The display unit 5 can display the operating status of the motor drivers 4a to 4c. The display unit 5 may switch the display content according to the operation content of the operation unit 6. The display unit 5 usually displays the current value (device value) of the device in the PLC system 1 and error information (presence or absence of an alarm or warning) that has occurred in the PLC system 1. The device is a name that indicates an area in memory provided to store device values (device data), and may also be called a device memory. The device value is information that indicates the input state from the input device, the output state to the output device, and the state of an internal relay (auxiliary relay), timer, counter, data memory, etc. that are set on the user program. There are two types of device values: bit type and word type. A bit device stores a device value of 1 bit. A word device stores a device value of 1 word.
[0014] The motor drivers 4a to 4c are provided to extend the functions of the PLC system 1. The motors 10a to 10c are controlled by the motor drivers 4a to 4c, respectively. The motor drivers 4a to 4c supply power to the motors 10a to 10c and control the amount of rotation and the like in accordance with commands from the basic unit 3. The motors 10a to 10c are, for example, servo motors or stepping motors.
[0015] The PC2 is a computer that provides a development environment for the PLC system 1. The PC2 is, for example, a portable notebook or tablet type personal computer, and is equipped with a display unit 7 and an operation unit 8. A ladder program, which is an example of a user program for controlling the PLC system 1, is created using the PC2. The created ladder program is converted into a mnemonic code in the PC2. The PC2 is connected to the basic unit 3 of the PLC system 1 via a communication cable 9a such as a universal serial bus (USB), and sends the ladder program converted into the mnemonic code to the basic unit 3. The basic unit 3 converts the ladder program into a machine code and stores it in a memory provided in the basic unit 3. Note that, although the mnemonic code is transmitted to the basic unit 3 here, the present invention is not limited to this. For example, the PC2 may convert the mnemonic code into an intermediate code and transmit the intermediate code to the basic unit 3.
[0016] Although not shown in Fig. 1, the operation unit 8 of the PC 2 may include a pointing device such as a mouse connected to the PC 2. The PC 2 may be configured to be detachably connected to the base unit 3 via a communication cable 9a other than USB. The PC 2 may be connected wirelessly to the base unit 3 without the communication cable 9a. In this case, the communication cable 9a may be understood to represent a wireless link.
[0017] The basic unit 3 and the motor driver 4a are connected by a communication cable 9b, and can communicate with each other (e.g., cyclic communication, message communication) via the communication cable 9b. The motor drivers 4a and 4b are connected by a communication cable 9c, and can communicate with each other via the communication cable 9c. The motor driver 4b can communicate with the basic unit 3 via the communication cables 9b and 9c. The motor drivers 4b and 4c are connected by a communication cable 9d, and can communicate with each other via the communication cable 9d. In addition, the motor driver 4c can communicate with the basic unit 3 via the communication cables 9b, 9c, and 9d.
[0018] In this example, motor drivers 4a to 4b are connected, but the number of motor drivers 4 may be one or more. The manufacturers of the motor drivers 4a to 4c may be different or the same. For ease of explanation, it is assumed here that the manufacturers of the motor drivers 4a to 4c are different.
[0019] In the following, when matters common to the motor drivers 4a to 4c are described, they will be referred to as the motor driver 4. Similarly, when matters common to the motors 10a to 10c are described, they will be referred to as the motor 10.
[0020] <Setting support device> FIG. 2 is a block diagram for explaining the electrical configuration of the PC 2. As shown in FIG. 2, the PC 2 includes a CPU 11, a display unit 7, an operation unit 8, a storage device 12, and a communication unit 13. The display unit 7, the operation unit 8, the storage device 12, and the communication unit 13 are each electrically connected to the CPU 11. The storage device 12 includes a RAM, a ROM, an HDD, and an SSD, and may further include a removable memory card. CPU is an abbreviation for central processing unit. ROM is an abbreviation for read-only memory. RAM is an abbreviation for random access memory. HDD is an abbreviation for hard disk drive. SSD is an abbreviation for solid state drive.
[0021] A user of the PC 2 causes the CPU 11 to execute the setting support program 21 stored in the storage device 12, and edits the project data through the operation unit 8, executes the setting of each motor driver 4, and acquires alarm information from each motor driver 4 and displays it on the display unit 7. The PC 2 may be called an engineering tool. The project data includes one or more user programs (e.g., ladder programs) and configuration information of the basic unit 3, the motor driver 4, and the motor 10. The configuration information includes information indicating the connection positions of the multiple motor drivers 4 relative to the basic unit 3, information indicating the functions (e.g., communication function and positioning function) provided in the basic unit 3, information indicating the functions of the motor driver 4, and device allocation information. Here, editing of the project data includes creation and modification (re-editing) of the project data. The user reads out the project data stored in the storage device 12 as necessary, and modifies the project data using the setting support program 21. The communication unit 13 communicates with the basic unit 3 via the communication cable 9a. The CPU 11 transfers the project data to the basic unit 3 via the communication unit 13. The communication unit 13 includes a communication circuit capable of executing communication conforming to the USB standard, a communication circuit for wired LAN communication, and a communication circuit for wireless LAN communication. The communication unit 13 may communicate with the motor driver 4 via a communication cable. The communication unit 13 transmits, for example, a parameter read request or a read / write request, an alarm detail acquisition request, and the like to the basic unit 3. The communication protocol between the PC 2 and the basic unit 3 may be a general-purpose protocol or a unique protocol. However, the frame format includes information for the basic unit 3 to make various requests to the motor driver 4 via industrial Ethernet. The communication unit 13 is also capable of executing cyclic communication and message communication.
[0022] The basic unit 3 is called a master device. The motor driver 4 is an example of a slave device. The product database 22 includes identification information (vendor ID, product code, revision number) for identifying the slave device connected to the basic unit 3. The vendor ID is unique identification information (vendor specific information) of the manufacturer (vendor) that manufactures the slave device. The product code is unique identification information (product specific information or product identification information) within the vendor that is assigned to distinguish different slave devices provided by the same vendor. The revision number is identification information assigned to distinguish revisions of the same slave device. The product database 22 may be input by a user through the operation unit 8, or may be acquired from the slave device by communicating with the slave device via the basic unit 3 and stored in the storage device 12.
[0023] Furthermore, the CPU 11 may store in the storage device 12 the product database 22 of a slave device specified through the operation unit 8 in association with the connection position of the slave device. This may be managed as configuration information (other information 24) that is part of the project data.
[0024] The slave device information 23 includes various information related to the slave device (e.g., the motor driver 4). The slave device information 23 may include slave device specific information, parameter information, and alarm information. The slave device specific information may include product specification information (vendor ID, product code, revision number) registered in the product database 22, information indicating whether the device requires an explicit write operation to non-volatile memory after parameters are reflected, and information indicating how to obtain an alarm detail code. The parameter information may include a parameter list, an option list, and an operation sequence list, the details of which will be described later. The alarm information may include an alarm list, the details of which will be described later.
[0025] The slave device information 23 may be provided as a part of the development environment (the setting support program 21). The slave device information 23 may be downloaded from a vendor's website. The slave device information 23 may be provided through a transportable recording medium.
[0026] In this way, the storage device 12 functions as an allocation information storage unit that stores the slave device information 23, which is allocation information, in association with the slave device. The slave device (motor driver 4) is identified based on the vendor ID, product code, and revision number (product specification information / product identification information). Such a slave device has a plurality of setting parameters. The plurality of setting parameters include a plurality of recommended adjustment parameters that are recommended to be adjusted in order to make the slave device compatible with the master device (basic unit 3) and operate it. Therefore, the slave device information 23 is information that assigns the product specification information (product identification information) of the slave device to a plurality of recommended adjustment parameters.
[0027] <Basic unit (master device)> 3 shows the hardware configuration of the basic unit 3. The CPU 31 writes information to the memory 32 and reads information from the memory 32. The memory 32 includes a RAM, a ROM, a HDD, and an SSD, and may further include a removable memory card. The project storage unit 35 is a ROM area that stores project data created and transferred by the PC 2. The project data includes user programs and configuration information. Furthermore, the CPU 31 accepts input of information from the operation unit 6. The CPU 31 displays various information on the display unit 5.
[0028] The CPU 31 is connected to the PC 2 via the communication unit 33a, and is connected to the motor driver 4 via the communication unit 33b to perform communication. The communication unit 33a is, for example, a communication circuit compatible with USB. The communication unit 33b is a communication circuit capable of performing communication compatible with industrial Ethernet protocols (e.g., EtherCAT, EtherNet / IP, PROFINET, MECHATROLINK-III). The communication units 33a and 33b are capable of performing cyclic communication and message communication. The communication conversion unit 34 is a function realized by the CPU 31, and converts and relays communication signals between the PC 2 and the motor driver 4. For example, the communication conversion unit 34 converts a request from the PC 2 to the motor driver 4 so that it conforms to the industrial Ethernet protocol, and transmits the request to the motor driver 4 on behalf of the PC 2. The communication conversion unit 34 converts a response from the motor driver 4 so that it conforms to the communication protocol between the PC 2 and the basic unit 3, and transfers the response to the PC 2.
[0029] <Motor driver (slave device)> 4 shows the hardware configuration of the motor driver 4. The CPU 41 writes information to the memory 42 and reads information from the memory 42. The memory 42 includes a RAM, a ROM, a HDD, and an SSD, and may further include a removable memory card. The memory 42 includes a RAM area 46 and a ROM area 47.
[0030] The CPU 41 communicates with the basic unit 3 and other motor drivers 4 via the communication unit 43. The communication unit 43 is a communication circuit capable of executing communication compatible with industrial Ethernet protocols (e.g., EtherCAT, EtherNet / IP, PROFINET, MECHATROLINK-III). The communication unit 43 is capable of executing cyclic communication and message communication. Motor control data is transmitted from the basic unit 3 by cyclic communication.
[0031] The input / output unit 44 includes an input terminal and an input circuit to which a limit switch or the like is connected, and an output circuit and an output terminal that output information to the outside. The motor drive circuit 45 supplies power and a control signal for driving the motor 10 to the motor 10. Note that the power to the motor 10 may be supplied from an external power source.
[0032] The CPU 41 has a parameter management unit 48 and an alarm management unit 49. The parameter management unit 48 stores and manages various parameters required for controlling the motor 10 in the parameter storage area 51. The parameter management unit 48 may be secured in either or both of the RAM area 46 and the ROM area 47. The alarm management unit 49 stores and manages the alarm state in the motor driver 4 in the alarm state storage area 52. The alarm state storage area 52 is secured in the RAM area 46.
[0033] <Functions of the CPU 11 in the PC2> FIG. 5 shows the functions realized by the CPU 11 executing the setting support program 21.
[0034] The user program editing unit 501 displays a UI for editing a user program executed by the basic unit 3 on the display unit 7, accepts editing of the user program through the UI, and creates the user program. The configuration setting unit 502 creates configuration information indicating product information of the basic unit 3, the motor driver 4, and the motor 10 constituting the PLC system 1, and connection positions, etc. For example, the configuration setting unit 502 displays a product list on the display unit 7, and places a product selected from the product list at the dropped position by dropping it on the UI. For example, an icon resembling the basic unit 3 is displayed on the UI, and configuration information indicating that the motor driver 4a is connected next to the basic unit 3 is created by dropping the icon of the motor driver 4a next to the icon of the motor driver 4a. Also, configuration information indicating that the motor driver 4b is connected next to the motor driver 4a is created by dropping the icon of the motor driver 4b next to the icon of the motor driver 4a. In this way, the types of the master device and the multiple slave devices, and the connection positions are specified in the configuration setting unit 502 and managed by the configuration information.
[0035] The parameter setting unit 503 sets a plurality of parameters used to control the basic unit 3 and the motor driver 4. The alarm management unit 504 acquires alarm information generated in the basic unit 3 or the motor driver 4, and displays it on the display unit 7.
[0036] The configuration management unit 505 manages the product database 22. The device information management unit 506 manages the slave device information .
[0037] The parameter setting unit 503 has a display processing unit 521 in charge of display processing of a user interface (UI), a reception processing unit 522 in charge of receiving user input through the UI, an editing unit 523 in charge of editing parameter values, and a write processing unit 525 that transfers and writes edited parameters to the slave device. The editing unit 523 can read out the current value of the parameter written in the slave device at that time through a read processing unit 527. The collation unit 524 may collate the parameter value displayed on the parameter setting screen with the current value and display the collation result on the display unit 7. The reset unit 526 may remotely power on (restart) the slave device or remotely initialize the settings of the slave device to the factory settings. The write processing unit 525 may instruct the slave device to write the parameters held in the volatile memory to the non-volatile memory.
[0038] <Parameter setting screen> FIG. 6 shows a UI 600 that the parameter setting unit 503 displays on the display unit 7. The UI 600 is a user interface for setting and transferring parameters required for starting up the PLC system 1. The configuration display unit 601 shows the configuration of the PLC system 1 that is set through the configuration setting unit 502. The device selection unit 602 displays a list (pull-down menu) for selecting a device to be set and accepts the selection of the device. When a device is selected through the device selection unit 602, the configuration display unit 601 highlights the icon of the selected device. In this example, the icon of the selected device is surrounded by a dashed frame. The check box 603 is a button that is checked when transferring a recommended parameter that has been prepared in advance. The value setting unit 604 is a UI for selecting a parameter to be transferred to the selected device and setting the value of the parameter. The pull-down menu may be called a drop-down list or a combo box.
[0039] The current value read button 605 is a button for reading out the parameter values currently set for the selected device from the selected device through the PLC system 1 and reflecting them in the value setting unit 604. The recommended value reset button 606 is a button for overwriting the values set in the parameters with recommended values. The recommended values of each parameter are stored in advance in the storage device 12. For example, the recommended values may be part of the slave device information 23.
[0040] The transfer execution button 607 is a button for issuing an instruction to transfer the parameters selected by the value setting section 604 to the device selected by the device selection section 602. As a result, the parameters are written to the slave device.
[0041] Incidentally, the parameter information includes a parameter list, an option list, and an operation sequence list. The parameter list is a list of parameters that can be set for the slave device to be transferred through the parameter setting screen (UI600). The number of parameters that can be set for the slave device can be several hundred in many cases. However, the number of parameters that are generally used by many users is about ten to several tens of parameters. Therefore, the parameter list is limited to parameters that must be set and parameters that are generally used by many users. This reduces the complexity of the parameter setting screen. For example, the parameters included in the parameter list are as follows: (a) Parameters that must be set in advance according to the recommended settings on the master device (e.g. input allocation, polarity) (b) Parameters that need to be set according to the user's mechanical configuration (load driven by the motor 10) controlled by the PLC system 1 (e.g., the direction of rotation of the motor 10) (c) Parameters (e.g., mechanical stiffness, inertia ratio) that need to be adjusted (tuned) to match the user's mechanical configuration (load driven by the motor 10) controlled by the PLC system 1. By the way, the method of setting the value in the value setting unit 604 includes, for example, a method of directly inputting the value and a method of selecting the value from a pull-down menu 610. The value may be displayed in any of binary, decimal, and hexadecimal formats.
[0042] (1) Parameter list FIG. 7 shows an example of a parameter list. The display order refers to the display order of parameters in the list displayed in the value setting section 604. The category refers to the category of the parameter (e.g., for initial setting, for tuning). The category is a category that is unified among various slave devices. Therefore, even if a user uses multiple slave devices from different vendors, the user can easily understand which parameters should be set and adjusted at what timing. The parameter number name is a name that matches the display format of the parameter number of each slave device. As the parameter number name, a different notation (such as "xx.xx", "(xx-xx)", "Pxx.xx", etc.) is used for each slave device, and this is generally a name prepared by the vendor. Therefore, by using the parameter number name as it is on the parameter setting screen, it is possible to reduce user confusion. The parameter name is the name of the parameter of each slave device. The parameter name may be multilingual. In this case, the parameter name is displayed on the parameter setting screen in a language that matches the display language of the PLC development environment. The index / sub-index is an index specified on the slave device side when writing / reading each parameter. An index is usually present in any communication protocol, but whether a sub-index exists depends on the industrial Ethernet protocol.
[0043] The data type indicates the data type of the parameter. The data type is required as information (data size) specified in the communication of the write and read request. The minimum and maximum setting values indicate the range of values that can be set for the parameter. The minimum and maximum setting values do not necessarily match the range of the data type. The minimum and maximum setting values are set so that the user does not enter a value outside the setting range. The minimum and maximum setting values may also be used in error processing when a value outside the setting range is entered. The default value is the value (initial value) set at the factory by the vendor of the slave device. "Power cycle required to reflect" is used to display a warning on the parameter setting screen. If this is TRUE, the slave device will not reflect the changed value unless the power is cycled. FALSE means that the change is reflected immediately. The value display format / option ID indicates the display format of the value on the parameter setting screen. This display format may be a format specified by the vendor of the slave device, or may be a format that is easy for the user to understand (e.g. binary display, decimal display, hexadecimal display, option display, etc.). In the case of option display, there is an ID (option ID) that indicates which option list to use from the "option list" described below.
[0044] (2) List of options Figure 8 shows an example of a choice list. The choice list is a list of choices for the values of parameters whose "value display format" is set to choice display among multiple parameters included in the parameter list. The parameters in the choice list and the parameters in the parameter list are linked via choice IDs.
[0045] The display order refers to the display order of options in a pull-down menu that is operated when editing a parameter value on the parameter setting screen. The value is the value that corresponds to each option. The slave device is requested to write this value. The display text is the text for each option. The display text may also be multilingual. On the parameter setting screen, the display text is displayed in a language that matches the display language of the PLC development environment.
[0046] (3) Operation sequence list Figure 9 shows an example of an operation sequence list. The operation sequence list indicates the sequence in which to write and read parameters when executing a specific operation on a slave device. Examples of specific operations include the following: (a) Execute writing to non-volatile memory (b) Software reset (power cycle) (c) Absolute Encoder Reset (d) Initialize all parameters (resetting parameters to the factory default settings) In FIG. 9, the operation type ID is a number or phrase for identifying the operation type. "Supported slave device" indicates whether the slave device supports the operation type. The execution condition indicates the timing at which the operation can be executed in the slave device. For example, the execution condition may be "always", "not under motor control", or "servo OFF". The execution condition may also be used as data for error notification when an operation is executed at a timing when it cannot be executed. The sequence is a parameter that exists in the case of a slave device that supports the corresponding operation, and is set to either "write" or "standby". "Write" means to write a value to the index / subindex by the data size. "Standby" means to read a value to the index / subindex by the data size. For example, reading is repeated until the read value matches the specified value. The condition may be set to "wait until the specified value" or "wait until the value is other than the specified value".
[0047] According to Figure 9, writing to non-volatile memory (#EEPROM_WRITE) is performed in the following sequence: writing the value 0x12345678 to the parameter at 0x1010:00 with a data size of 4 bytes, then repeatedly reading the value of the parameter at 0x1010:00 (data size is 4 bytes), and once it is confirmed that the value is 0x00000001, the process is complete.
[0048] (4) Flowchart 10 is a flowchart showing a parameter setting method executed by CPU 11. CPU 11 executes the following processes in accordance with setting assistance program 21. (Parameter setting unit 503) refers to slave device information 23 of a slave device connected adjacent to basic unit 3, for example, creates UI 600, and displays it on display unit 7. In UI 600, each parameter may be set to an initial value included in slave device information 23, for example.
[0049] In S1, the CPU 11 (parameter setting unit 503) determines whether an instruction to start the UI 600 or an instruction to switch the slave device has been received through the operation unit 8. When an instruction to start the UI 600 is input or a different slave device is selected by the device selection unit 602, the CPU 11 proceeds from S1 to S2.
[0050] In S2, the CPU 11 (parameter setting unit 503) acquires identification information of the slave device selected by the device selection unit 602. For example, the parameter setting unit 503 transmits an acquisition request for product identification information (vendor ID, product code, revision code) of the nth slave device to the configuration management unit 505. The configuration management unit 505 reads the product identification information of the nth slave device identified by the acquisition request from the storage device 12, and transmits the product identification information to the parameter setting unit 503.
[0051] In S3, the CPU 11 (parameter setting unit 503) acquires slave device information corresponding to the product identification information. For example, the parameter setting unit 503 transmits an acquisition request for the slave device information 23 corresponding to the product identification information to the device information management unit 506. The device information management unit 506 reads out the slave device information 23 for the product identification information indicated by the acquisition request from the storage device 12 and transmits it to the parameter setting unit 503.
[0052] In S4, the CPU 11 (parameter setting section 503) updates the UI 600 based on the slave device information 23. The contents of the slave device information 23 are reflected in the value setting section 604 of the UI 600.
[0053] In S5, the CPU 11 (parameter setting unit 503) determines whether a request to read out a current value has been input. For example, the parameter setting unit 503 determines whether the current value read button 605 provided on the UI 600 has been operated. If the current value read button 605 has not been pressed, the CPU 11 proceeds from S5 to S8. On the other hand, if the current value read button 605 has been pressed, the CPU 11 proceeds from S5 to S6.
[0054] In S6, the CPU 11 (parameter setting unit 503) reads out the current value from the slave device selected by the device selection unit 602. For example, the parameter setting unit 503 creates a read request for the current value indicating the slave device selected by the device selection unit 602, and transmits it to the basic unit 3 through the communication unit 13. When the CPU 31 of the basic unit 3 receives the read request, it transfers the read request to the slave device selected by the device selection unit 602. The CPU 41 of the slave device (e.g., the motor driver 4) selected by the device selection unit 602 reads out the current value held in the parameter storage area 51 and transmits it to the basic unit 3. The CPU 31 of the basic unit 3 transmits a response including the current value to the PC 2. This allows the CPU 11 to obtain the current value of the parameter of the desired slave device.
[0055] In S7, the CPU 11 (parameter setting unit 503) updates the UI 600 based on the current values. In the value setting unit 604 of the UI 600, the acquired current values are reflected in each parameter.
[0056] In S8, the CPU 11 (parameter setting unit 503) determines whether or not a recommended value reset has been instructed via the operation unit 8. For example, the parameter setting unit 503 determines whether or not the recommended value reset button 606 provided on the UI 600 has been pressed. If the recommended value reset button 606 has not been pressed, the CPU 11 proceeds from S8 to S11. If the recommended value reset button 606 has been pressed, the CPU 11 proceeds from S8 to S9.
[0057] In S9, the CPU 11 (parameter setting unit 503) resets the parameters to the recommended values. The recommended values of the parameters may be included in the slave device information 23.
[0058] In S10, the CPU 11 (parameter setting unit 503) updates the UI 600 based on the recommended values. In the value setting unit 604 of the UI 600, the obtained recommended values are reflected in each parameter.
[0059] In S 11 , the CPU 11 (parameter setting unit 503 ) edits the parameters in the value setting unit 604 based on an instruction input via the operation unit 8 .
[0060] In S12, the CPU 11 (parameter setting unit 503) determines whether or not the transfer execution button 607 has been pressed. If the transfer execution button 607 has not been pressed, the CPU 11 returns from S12 to S5. If the transfer execution button 607 has been pressed, the CPU 11 advances from S12 to S13.
[0061] In S13, the CPU 11 (parameter setting unit 503) transfers the parameters set through the UI 600 to the slave device. The parameter setting unit 503 creates a parameter write request and transmits it to the basic unit 3 through the communication unit 13. The write request includes, for example, the index of the parameter to be written, the write size, and the value to be written. The basic unit 3 transmits the write request to the slave device (motor driver 4) designated as the write target. The CPU 41 (parameter management unit 48) of the motor driver 4 writes the value to the parameter stored in the parameter storage area 51 in accordance with the write request.
[0062] (5) Writing to non-volatile memory Fig. 11 is a flowchart showing writing to the non-volatile memory (ROM area 47). Fig. 12 shows UIs 1200a to 1200e that function as writing screens. When the transfer execution button 607 is pressed, the parameter setting unit 503 displays the UI 1200a on the display unit 7. The UI 1200a includes a doughnut graph 1201 that indicates the progress of the transfer. When the transfer of the parameters is completed, the CPU 11 executes the following process.
[0063] In S21, the CPU 11 (parameter setting unit 503) determines whether the parameter whose value has been changed via the UI 600 is a parameter that needs to be written to non-volatile memory. The slave device information 23 includes information indicating whether or not writing to non-volatile memory is required for each parameter. The parameter setting unit 503 makes the determination based on the slave device information 23. If a parameter that needs to be written to non-volatile memory has been changed, the CPU 11 proceeds from S21 to S22. If a parameter that needs to be written to non-volatile memory has not been changed, the CPU 11 proceeds from S21 to S25.
[0064] In S22, the CPU 11 (parameter setting unit 503) displays a screen for writing to the non-volatile memory.
[0065] 12, UI1200b shows an example of a screen for writing to non-volatile memory. Message 1202 is a message that informs the user that it is necessary to write the parameters to non-volatile memory in order for the motor driver 4 to hold the parameters even when the motor driver 4 is powered off. Write button 1203 is a button for instructing the motor driver 4 to write to the non-volatile memory. Button 1204 is a button for closing UI1200b without writing to the non-volatile memory.
[0066] In S23, the CPU 11 (parameter setting unit 503) determines whether or not a write instruction has been input via the write button 1203 of the UI 1200b. If a write instruction has not been input, the CPU 11 proceeds from S23 to S25. If a write instruction has been input, the CPU 11 proceeds from S23 to S24.
[0067] In S24, the CPU 11 (parameter setting unit 503) executes writing of parameters to the non-volatile memory. For example, the parameter setting unit 503 creates a write request to the non-volatile memory, and transmits the write request to the slave device (motor driver 4) via the basic unit 3. The CPU 41 (parameter management unit 48) writes the parameters temporarily written in the RAM area 46 to the ROM area 47. In this case, the parameter storage area 51 exists in both the RAM area 46 and the ROM area 47.
[0068] In S25, the CPU 11 (parameter setting unit 503) determines whether the slave device needs to be powered on again in order to reflect the changed parameter in the slave device. The parameter setting unit 503 makes this determination by referring to the item "Does power need to be powered on again to reflect?" in the slave device information 23 shown in Fig. 7. If power re-activation is not required, the CPU 11 proceeds from S25 to S31 and displays a write completion message.
[0069] 12, a UI 1200e is a UI that displays a writing completion message. When an OK button 1206 is pressed, the CPU 11 closes the UI 1200e.
[0070] On the other hand, if it is necessary to restart the power, the CPU 11 proceeds from S25 to S26.
[0071] In S26, the CPU 11 (parameter setting unit 503) determines whether or not a power-on command can be issued remotely. The command can be issued remotely from the PC 2 via the basic unit 3 to the slave device (motor driver 4) to power on again.
[0072] If the power cycle cannot be instructed remotely, the CPU 11 proceeds from S26 to S30, and displays a message for guiding the user to manually cycle the power on the display unit 7. In Fig. 12, the UI 1200d includes a message 1202 for guiding the user to manually cycle the power. Upon seeing this message 1202, the user presses the OK button 1206 to close the UI 1200d and manually cycle the power of the slave device.
[0073] If a power cycle can be instructed remotely, the CPU 11 proceeds from S26 to S27. In S27, the CPU 11 (parameter setting unit 503) displays a remote power cycle screen on the display unit 7. In Fig. 12, UI1200c is an example of the remote power cycle screen. A message 1207 is a message for guiding the user to remotely power cycle the slave device by pressing the software reset button 1205.
[0074] In S28, the CPU 11 (parameter setting unit 503) determines whether an instruction to execute a remote restart has been input. For example, the parameter setting unit 503 determines whether the software reset button 1205 has been pressed. If the software reset button 1205 has been pressed, the CPU 11 proceeds from S28 to S29. If the software reset button 1205 has not been pressed, the CPU 11 skips S29.
[0075] In S29, the CPU 11 (parameter setting unit 503) executes a remote power cycle. For example, the parameter setting unit 503 creates a power cycle request and transmits the power cycle request to the slave device (motor driver 4) via the basic unit 3. When the CPU 41 of the motor driver 4 receives the power cycle request, it executes power cycle of the motor driver 4. Note that when the restart is completed, the CPU 41 may create a completion notification and transmit the completion notification to the PC 2 via the basic unit 3.
[0076] (6) Another example of the parameter setting screen (6-1) Batch setting screen for multiple slave devices of the same type 13 shows a UI1300, which is an example of a batch setting screen for multiple slave devices of the same type (same model). In the UI1300, the same reference numerals are given to the parts common to the UI600, and the description thereof will be omitted.
[0077] The model selection section 1301 is a pull-down menu for selecting the model of the slave device. The CPU 11 (parameter setting section 503) refers to the configuration information of the PLC system 1, extracts multiple slave devices of the same type selected by the model selection section 1301, creates a UI 1300, and displays it on the display section 7.
[0078] The transfer destination selection unit 1302 displays multiple slave devices of the same type selected by the model selection unit 1301 in a selectable manner. In this example, the parameter whose value has been set in the value setting unit 604 is transferred to the slave device (motor driver 4) whose check box is checked. In this example, the same parameter value is set for multiple slave devices of the same type selected by the model selection unit 1301.
[0079] Generally, the same parameters are set for multiple slave devices of the same type. Therefore, the UI 1300 can improve user convenience in any use case.
[0080] If some parameters need to be fine-tuned, the CPU 11 may transfer the same parameter values to multiple slave devices via the UI 1300, and then read out the current values via the UI 600 and fine-tune each parameter for each individual slave device. This would significantly reduce the time required for the work.
[0081] (6-2) Batch setting screen for multiple slave devices of different types FIG. 14 shows a UI 1400, which is an example of a batch setting screen for multiple slave devices of different types (different models). A list section 1401 displays multiple slave devices registered in the configuration information of the PLC system 1 in a list by type. In this example, it is illustrated that there are two types of slave devices, two slave devices of the first type, and one slave device of the second type. A slave device with a check mark in the list section 1401 is selected for parameter editing and transfer. The CPU 11 refers to the slave device information 23 of the slave device being selected in the list section 1401 and reflects it in the value setting section 604. The number of value editing sections provided in the value setting section 604 is the same as the number of slave devices with a check mark in the list section 1401. In other words, the value setting section 604 can set a value individually for each slave model.
[0082] The parameter read button 1402 is a button for reading out the current parameter values individually from all the slave devices that are checked in the list section 1401. The transfer execution button 607 is a button for transferring, in a lump, the parameters whose values have been individually set in the value setting section 604 to all the slave devices that are checked in the list section 1401.
[0083] Compared with the UI600 and UI1300, the UI1400 has the advantage that values can be edited and transferred to multiple slave devices of different types using a single UI.
[0084] (7) Comparison of set values and current values 15 shows a UI 1500 including a function for comparing the set value set in the value setting unit 604 with the current value set in the slave device at that time. When a comparison button 1501 is pressed, the CPU 11 (read processing unit 527, comparison unit 524) acquires the current value from each slave device for each parameter and determines whether it matches the set value set in the value setting unit 604. The CPU 11 (comparison unit 524, display processing unit 521) displays the comparison result for each parameter in the comparison result display unit 1502. Since the comparison result display unit 1502 displays the set value and the current value side by side, the user will be able to clearly understand the difference between them.
[0085] (8) Relationship between slave devices and motion axis numbers Positioning a load using a motor is sometimes called motion control. In this case, each slave device is given not only a slave name but also a motion axis number.
[0086] Axis number 0001: Slave device 001 Axis number 0002: Slave device 003 Axis number 0003: Slave device 004 Axis number 0004: Slave device 002 16 shows a UI1600 for identifying slave devices by axis numbers. In the UI600, the device selection section 602 was a pull-down menu listing slave numbers. On the other hand, in the UI1600, the device selection section 602 is replaced with an axis selection section 1602. The axis selection section 1602 is also a pull-down menu listing axis numbers in a selectable manner. The other parts of the UI1600 are common to the UI1600.
[0087] The CPU 11 has a table in which axis numbers and slave numbers correspond to each other in the storage device 12. The CPU 11 refers to this table, replaces the axis number with the slave number, and executes the various processes described above.
[0088] Incidentally, there are cases where a single slave device can control a multi-axis motor 10. In this case, multiple axis numbers are associated with one slave number. In such a slave device, there may be parameters common to all axes and individual parameters for each axis.
[0089] The UI 1600 displays the parameters of the axis selected by the axis selection unit 1602 in the value setting unit 604. When the user edits a parameter common to multiple axes on one axis, the CPU 11 (editing unit 523) reflects the editing results on the other axes. In other words, the editing results are reflected on the other axes in the background without the user having to select the other axes by the axis selection unit 1602 to edit the parameters. This makes the user's editing work more efficient. However, for parameters individual to each axis, the CPU 11 (editing unit 523) accepts editing of values individually.
[0090] (9) When the parameter size is less than the rewritable unit The size of the parameter to be written may be small compared to the payload size of the communication frame that can be sent to the slave device. In this case, multiple parameters may be included in one payload. For example, a certain parameter may take a value in the range of 2 bytes without a sign (0000H to 0FFFH). However, a parameter with a different meaning may be assigned to each nibble (= 4 bits) of these 2 bytes. In other words, 4 parameters may be assigned to 2 bytes. In this case, it was necessary to always read and write the 4 parameters together.
[0091] Therefore, a UI that can specify multiple parameters as transfer targets all at once is required, as well as a UI that can edit multiple parameters individually.
[0092] 17 shows a parameter list to which information indicating the starting bit position and bit width has been added. In this way, by clearly indicating the starting bit position and bit width of each parameter, the user can read and write the parameters easily and without mistakes.
[0093] FIG. 18 shows a UI1800, which is an example of a parameter setting screen. The parts described above are given the same reference numerals, and the description thereof will be omitted. The value setting unit 1804 has a check box 1820 for designating a transfer target, similar to the value setting unit 604, but the check box 1820 of the value setting unit 1804 is provided in common for a plurality of parameters. In other words, a single check box 1820 is provided for a plurality of parameters that need to be read / written together. On the other hand, the value setting unit 1804 can accept editing of the values of a plurality of parameters individually, as before.
[0094] 17, and creates data to be transferred by assembling the values of multiple parameters to which the same index / subindex is assigned. The parameter setting unit 503 transmits a request to write transfer data to the index / subindex of the parameter to be transferred to the slave device via the basic unit 3.
[0095] The same applies when reading a current value from a slave device. The CPU 11 transmits a read request for the index / subindex of the parameter to be read to the slave device via the basic unit 3. The CPU 11 obtains the start bit position and bit width from the parameter list shown in Fig. 17, and based on this, breaks down the data received from the slave device into multiple parameters and reflects them in the UI 1800.
[0096] (10) Operation execution screen The above-mentioned parameter setting screen (UI600, etc.) allows the user to write parameters to non-volatile memory and perform software reset in a series of operation flow through the parameter setting screen. As shown in FIG. 12, when the transfer of parameters to the slave device is completed, the parameters held in the volatile memory are written to the non-volatile memory by pressing a write button 1203. Also, according to FIG. 12, when the transfer of parameters to the slave device is completed, a software reset button 1205 is displayed, and pressing this button turns the slave device back on. However, the user may wish to perform these operations independently of the transfer of parameters. Similarly, the user may wish to perform operations such as absolute encoder reset and resetting to the factory default (factory reset) on a one-off basis.
[0097] 19 shows a menu screen UI1900. The UI1900 has a plurality of tabs 1901 to 1904. The tab 1901 is a tab for calling a startup parameter transfer screen (parameter setting screen) such as the above-mentioned UI600. The tab 1902 is a tab for calling a UI for independently executing various operations. The tab 1903 is a tab for instructing auto-tuning of parameters. The tab 1904 is a tab for reading and writing parameters one by one.
[0098] 19, a tab 1902 is activated. The tab 1902 includes the above-mentioned button 1203 for instructing writing of parameters to the non-volatile memory and a software reset button 1205 for software resetting the PLC system 1. Furthermore, the tab 1902 includes a button 1905 for instructing an absolute encoder reset and a button 1906 for instructing initialization of the PLC system 1 to the factory settings.
[0099] In the UI 1900, four buttons are displayed in an operable state. However, some slave devices may not support remote operations. In such cases, the display processing unit 521 hides or grays out the buttons for unsupported operations so that the user cannot operate them. The CPU 11 refers to the list of operation sequences stored in the storage device 12, and controls the display / non-display (graying out) of these buttons according to the value of "slave device compatible with remote operations."
[0100] When a user presses a button, the sequence of requests issued through the UI 1900 may differ depending on the slave device. In this case, the CPU 11 executes the transmission of requests and the reception of responses in accordance with a "sequence" in the operation sequence list stored in the storage device 12.
[0101] The UI 1900 is displayed after the user selects one of the slave devices included in the configuration information. However, the CPU 11 may accept the selection of multiple slave devices and execute the same operation on the selected multiple slave devices at once.
[0102] (11) Tuning screen Slave device parameters include parameters for adjusting the responsiveness of the servo system, such as mechanical stiffness and inertia ratio. Since these parameters require delicate adjustment, it is convenient for users if a dedicated UI exists.
[0103] 20 shows a UI 2000 for tuning a parameter. This UI 2000 may be displayed via a tab 1903. The device selection section 602 is a pull-down menu for selecting one of the multiple slave devices included in the PLC system 1.
[0104] The auto-tuning setting section 2001 is a pull-down menu for selecting one of a plurality of auto-tuning modes. The reflect button 2002 is a button for reflecting the auto-tuning mode selected by the auto-tuning setting section 2001 in the slave device. In other words, unless the reflect button 2002 is pressed, the auto-tuning mode selected by the auto-tuning setting section 2001 is not reflected in the slave device.
[0105] The mechanical stiffness setting section 2003 is a slide bar for setting the mechanical stiffness of the load connected to the slave device. The set value display section 2004 displays the set value of the mechanical stiffness set by the mechanical stiffness setting section 2003. The mechanical stiffness is immediately set for the slave device.
[0106] The inertia ratio setting section 2005 includes a plus button, a minus button and a set value display section for setting the inertia ratio of the load of the slave device. The inertia ratio is also reflected in the slave device immediately.
[0107] 20 is merely an example. CPU 11 changes the tuning target parameter name, index, number of parameters, and options according to the slave device selected by device selection unit 602. In other words, CPU 11 references parameter information corresponding to the slave device selected by device selection unit 602 and creates UI 2000.
[0108] FIG. 21 is a list of tuning parameters, which are part of the parameter information. Parameter names may be provided in both English and Japanese. Furthermore, the above-mentioned index / sub-index, data type, minimum / maximum setting value, value display format, and option ID may be included. Parameter type indicates whether the parameter is a "mode selection parameter" or a "gain adjustment parameter." Control type indicates the type of control (object) for adjusting the parameter. ComboBox indicates a pull-down menu type UI. TrackBar indicates a slider type UI. NumericUpDown indicates a numeric input type UI.
[0109] A non-tunable value is data that only the "mode selection parameter" has, and is a value that cannot be set from the UI 2000 that is provided in common to multiple slave devices. In this case, the CPU 11 displays a message to the user urging the user to start software or a UI that is provided specifically for that slave device and adjust the parameter. The CPU 11 may provide the UI 2000 so that the user can also adjust the "gain adjustment parameter" in the UI 2000.
[0110] (12) Parameter backup and restore function The CPU 11 may export the parameter values set through the parameter setting screen to a file, etc., to back them up. The CPU 11 may also import the parameter values from a backup file to restore them to the parameters.
[0111] 22 shows another example of a parameter setting screen UI2200. Compared to the UI600, the UI2200 has an export button 2201 and an import button 2202.
[0112] When the export button 2201 is pressed, the CPU 11 writes the parameter values displayed on the UI 2200 to individual backup files or project data for each slave device. These files are stored in the storage device 12.
[0113] When the import button 2202 is pressed, the CPU 11 reads out parameter values from a backup file associated with the slave device selected by the device selection unit 602 and stored in the storage device 12, and reflects the parameter values in the UI 2200.
[0114] Note that backup may be performed collectively for multiple slave devices included in the PLC system 1. Alternatively, the CPU 11 may display a selection screen for the slave devices to be backed up among the multiple slave devices, and allow the user to select the slave device. The CPU 11 may read out the current values of parameters from the selected slave device and back them up.
[0115] Similarly, the CPU 11 may identify a plurality of slave devices whose parameters are backed up in a backup file by referring to the backup file, have the user select one or more of the identified plurality of slave devices, read the parameters of the selected slave device from the backup file, and write the parameters of the selected slave device to the selected slave device. In such a restoration, the parameters are often held in the RAM area of the slave device. Therefore, when the restoration is completed, the CPU 11 may inquire whether or not to write the parameters to the non-volatile memory. If the user wishes to write the parameters to the non-volatile memory, the CPU 11 writes the parameters to the non-volatile memory. Similarly, if a software reset is necessary, the CPU 11 may display a message prompting the user to perform a software reset or may remotely execute the software reset. The CPU 11 may inquire of the user whether or not to remotely execute a software reset, and execute the software reset according to the result of the inquiry.
[0116] <Alarm display> As described above, the PLC system 1 may include multiple slave devices provided by different vendors. Conventionally, it was not possible to check the details of an alarm unless a monitoring tool prepared by each vendor was connected to each slave device. Therefore, this embodiment realizes a common alarm display UI for multiple slave devices.
[0117] FIG. 23 shows a list of alarms in the alarm information, which is a part of the slave device information 23. The main number / sub number is an alarm detail code that identifies each alarm. The alarm detail code may be composed of only the main number or may be composed of the main number and the sub number. The alarm message is a statement that explains the alarm content. If the alarm message supports multiple languages, the alarm message for each language is stored. The display unit 7 displays the alarm message in a language that matches the display language of the PLC development environment. The alarm number display character string is a raw character string defined by the vendor of the slave device. The notation method of the above-mentioned alarm detail code may differ for each vendor or each slave device. For example, the notation method may be decimal or hexadecimal. In addition, the main number and the sub number may be connected with a hyphen, or the sub number may not exist. Therefore, an alarm number display character string may be provided in order to display the alarm number display character string on the common UI.
[0118] FIG. 24 shows a common UI 2400 for displaying an alarm. The common UI 2400 is displayed on the display unit 7 when multiple slave devices are test-run. The operation content display unit 2401 is a display area showing information on the slave devices in operation. The alarm display unit 2402 displays the "series name of the slave device", the "alarm detail code", and the "alarm message". The details button 2403 is a button for displaying detailed contents of the alarm. When the details button 2403 is pressed, the CPU 11 accesses a link destination of the manual associated with the details button 2403, and displays a page on which detailed information of the alarm is described on the display unit 7. The alarm detail information may include, for example, the occurrence conditions of the alarm and a method of solving the alarm. The test run operation unit 2420 has multiple control objects for operating the test run of the slave devices. The JOG operation refers to an operation method for continuously operating a motion unit or a motor. The inching refers to moving the motion unit or the motor in a predetermined direction for a short period of time. The return to origin refers to returning the motion unit, the motor, or the like to the origin. Point operation refers to moving a motion unit or motor to a specified point number among multiple preset points. Point parameters required for point operation include point number, axis number, operation mode, target coordinates, speed, next point number, etc. In particular, the next point number is a kind of pointer, indicating the point number following a certain point number. For example, if the point numbers are set as 1->2->3->4->5->6->7->8->1..., multiple point parameters are applied repeatedly in order. Teaching refers to learning the machine coordinates corresponding to the specified point number. Continuous operation refers to continuously operating a motion unit or motor according to a user program or multiple point numbers, etc.
[0119] 25 shows another common UI 2500 for displaying an alarm. In this example, each slave device is linked to an axis number. An information display unit 2501 displays an operating state and the like for each axis number. An alarm display unit 2520 displays "series name of slave device," "alarm detail code," and "alarm message." Although a details button 2403 is not shown here, the details button 2403 may also be provided in the common UI 2500.
[0120] 26 is a flowchart showing a method for displaying alarm information in the common UIs 2400 and 2500. Here, it is assumed that the display unit 7 has already acquired the common UIs 2400 and 2500.
[0121] In S41, the CPU 11 (alarm management section 504) attempts to detect an alarm from each of the multiple slave devices (motor drivers 4) via the basic unit 3.
[0122] In S42, the CPU 11 (alarm management unit 504) determines whether an alarm has been detected for any of the slave devices. If no alarm has occurred, the CPU 11 returns from S42 to S41. If an alarm has occurred, the CPU 11 proceeds from S42 to S43.
[0123] In S43, the CPU 11 (alarm management unit 504) identifies a method for acquiring an alarm detail code for the slave device in which an alarm was detected. The CPU 11 acquires the method for acquiring the alarm detail code from the slave device specific information of the slave device information of the slave device in which an alarm was detected. The acquisition method may differ depending on the vendor and the slave device. The alarm code acquired from the slave device may be the alarm detail code itself. In cyclic communication being performed between the slave device and the master device, the alarm detail code may be stored in a field different from the field in which the alarm code is stored. The slave device may also transmit the alarm detail code to the master device by message communication.
[0124] In S44, the CPU 11 (alarm management unit 504) acquires the alarm detail code according to the method for acquiring the alarm detail code.
[0125] In S45, the CPU 11 (alarm management unit 504) acquires alarm information corresponding to the alarm detail code from the storage device 12, etc. As shown in Fig. 23, the alarm list of the alarm information includes information for explaining the alarm in more detail.
[0126] In S46, the CPU 11 (alarm management unit 504) reflects the alarm information in the common UIs 2400 and 2500.
[0127] <Write recommended value> For each parameter set in a slave device, an optimal or appropriate value (recommended value) for the master device may be determined. Therefore, the recommended value varies depending on the master device, but it is difficult for a user to read and understand the recommended value that is appropriate for the master device from the manual of the slave device. Therefore, the parameter list of the parameter information stored in the storage device 12 also holds the "recommended value" of each parameter. The CPU 11 identifies the slave device (motor driver 4) connected to the basic unit 3 from the configuration information, reads out the recommended value of each parameter required to start up the slave device from the parameter list of the parameter information of the slave device stored in the storage device 12, displays the recommended value on the parameter setting screen, and transfers and writes the recommended value to each slave device.
[0128] This allows the slave devices to be started up from the master device, as the recommended values appropriate for the master device are set in the slave devices, significantly reducing the user's workload.
[0129] (1) Automatic setting of recommended values When the vendor of the master device (basic unit 3) and the vendor of the slave device (motor driver 4) are different, the communication settings and control parameters of the slave device (motor driver 4) must be set to match the specifications of the master device (basic unit 3). Conventionally, users would connect a dedicated setting support device to the motor driver 4, compare the manuals for the basic unit 3 and the motor driver 4, and set up the motor driver 4 so that it could be controlled from the basic unit 3, but this was an extremely difficult task.
[0130] Therefore, in this embodiment, the master device vendor checks the specifications of the slave devices of other vendors, determines the recommended values of the parameters of the slave devices of other vendors that match the specifications of the master device of the vendor, creates allocation information, and provides it to the PC2, which is a setting support device. The allocation information is associated with vendor specific information and product specific information for identifying each slave device. The vendor specific information may be a part of the product specific information. Furthermore, the allocation information has a recommended value associated with the vendor specific information and the product specific information. Therefore, the PC2 reads out the allocation information corresponding to the slave device selected by the user from the storage device 12, obtains the recommended value, and transfers and writes the recommended value to the slave device via the master device. This makes it possible to control the slave device from the master device even if the master device and the slave device are from different vendors.
[0131] (2) User Interface FIG. 27 shows a UI2700, which is an example of a configuration setting screen (communication setting screen) displayed on the display unit 7 by the configuration setting unit 502. In the configuration setting area 2701, icons of the PLC (basic unit 3) constituting the PLC system 1 and icons of a plurality of extension units (motor drivers 4, but written as servos here) are displayed. In this example, each slave device is assigned an axis number and managed. The device list 2702 is a list of master devices and slave devices that can be set by the PC 2, and the master devices and slave devices are classified by vendor. The user can add master devices and slave devices to the device list 2702 by dragging and dropping or importing electronic files 2710 (e.g., EDS files, ESI files) provided by the vendors that manufacture and sell the slave devices for each slave device onto the device list 2702.
[0132] The device information display section 2703 displays the axis number, product name (or product code), vendor name, and performance information (encoder resolution, maximum motor speed, maximum motor torque, etc.) of the slave device (e.g., axis 2) selected by the user. The detailed settings button 2704 is a button for calling up a detailed settings UI for the selected slave device. The recommended value write button 2705 is enabled when the selected device supports writing of recommended values, and is a button for calling up a recommended value write UI (parameter setting screen).
[0133] 28 shows how a slave device has been added to a device list 2702 by dragging and dropping an electronic file 2710. In this state, if the added slave device is further dragged and dropped into the configuration setting area 2701, an icon of the slave device is added to the configuration setting area 2701.
[0134] 29 shows a state in which an icon of a slave device has been added to the configuration setting area 2701. The added slave device may be changed to a selected state. In this case, the device information display section 2703 displays the axis number (axis 3), product name (or product code), vendor name, and performance information (encoder resolution, maximum motor speed, maximum motor torque, etc.) of the selected slave device. In this example, the slave device (axis 3) supports writing of recommended values, so the recommended value write button 2705 is changed from disabled to enabled.
[0135] (3) Communication format (packet format) FIG. 30 shows the communication format used in cyclic communication between master and slave devices in industrial Ethernet. As an example, EtherCAT is used as industrial Ethernet. The communication format of the physical layer of EtherCAT complies with the communication format specified in IEEE802.3. One packet consists of an Ethernet header (22 bytes), EtherCAT data (46 bytes to 150 bytes), FCS (frame check sequence): CRC (cyclic redundancy check code) (4 bytes), and packet interval (IPG) (12 bytes). The EtherCAT data includes a frame header and a data section for each slave device (axis). The data section for each slave device (axis) consists of an EtherCAT header, axis data, and a working counter (for detecting unauthorized processing). Furthermore, the axis data includes output data and input data from the slave device of that axis number. As can be seen from FIG. 30, the master device can exchange data with all slave devices using one packet, achieving ultra-high-speed communication. Therefore, control data for the master device to control the slave devices is transmitted and received by cyclic communication.
[0136] (4) Advanced settings screen (manual settings screen) FIG. 31 shows UI3100, which is an example of a detailed setting screen displayed on the display unit 7 by pressing the detailed setting button 2704. The CPU 11 generates and displays UI3100 based on the electronic file 2710. A tab 3101 displays basic information of the selected slave device. The basic information includes type information, axis number, number of occupied axes (number of axes when multiple axes are supported), vendor name, vendor ID, product code, revision number, etc. The check at the start of communication is a list of items to be used to identify the slave among the information transmitted from the slave device when the master device and the slave device start cyclic communication. In FIG. 31, "Yes" means that the corresponding item is included in the identification of the slave to be communicated with. "No" means that the corresponding item is not included in the identification of the slave to be communicated with.
[0137] FIG. 32 shows details of the tab 3102. The tab 3102 is a tab for setting PDO mapping. Information generated by PDO mapping may be called mapping information. In this example, the names (PDO entry names) of parameters (objects) transmitted and received in cyclic communication (PDO communication), object indexes, and data sizes of the parameters (objects) are set. The user can add and delete objects on an object-by-object basis. The user must add and delete objects, and set the PDO entry names, indexes, and data sizes in accordance with the specifications of the master device. Therefore, this manual setting is difficult for the user.
[0138] Figure 33 shows details of tab 3102 for other slave devices. As Figure 33 shows, the initial values of each object are different for each slave device, so adding and deleting objects, and setting PDO entry names, indexes, and data sizes must be set according to the specifications of the master device.
[0139] 34 shows details of tab 3103 for setting the motion function. In tab 3103, elements of the motion function are linked to objects of PDO communication. In this example, the object (object index) in which the result of the motion calculation (target position) is stored is assigned to the object 607A:00 set in association with the PDO. The signal that the motion function of the master device regards as the forward direction limit is assigned to the 0th bit of 60FD:00 set in association with the PDO.
[0140] In order to control a slave device using the motion functions of the master device in this way, it is also necessary to connect a dedicated configuration support device to the slave device in order to determine which functions (limits, origin sensor, etc.) should be assigned to which input pins of the slave device, and whether to reverse the direction of motor rotation, etc.
[0141] The user also performs a test run of the user program using the UI2400 illustrated in Fig. 24. At that time, the user connects the motor 10 to a load and checks whether the motor rotation direction is as expected by the user, whether the positive limit sensor, the negative limit sensor, and the origin sensor are operating normally, and whether the coordinate conversion is correct (whether the load actually moves 10 mm in response to a 10 mm movement command). Therefore, with manual settings alone, the user would have to repeat settings and test runs, which was a very tedious task for the user.
[0142] The settings required to control a slave device using the motion function of the master device include the following:
[0143] - Input allocation and polarity settings to leave limit control to the master device -Setting the input allocation and polarity of the signals used in the origin return - Input assignment and polarity settings for executing coordinate capture when the sensor is turned on Due to model-specific circumstances, all control modes (position control, speed control, torque control) cannot be used unless the specified control mode is selected. When a user performs manual configuration, the user must manually confirm the required specifications from the master device to the slave device and the parameter specifications of the slave device.
[0144] Therefore, the automatic setting function of this embodiment supports the automation of PDO setting and motion function setting, and the writing of recommended parameter values, thereby significantly reducing the burden on the user.
[0145] (5) Automatic setting Fig. 35 shows an example of allocation information 3500 required for automatic setting. The allocation information 3500 has a vendor ID, a product code, and a revision number for identifying each slave device. Furthermore, the allocation information 3500 has a PDO setting, a motion function setting, and a recommended value linked to these identification information. The PDO setting indicates the index of an object communicated by PDO communication (cyclic communication). The motion function setting indicates to which object (index) a motion function is assigned. The recommended value is a recommended value of the parameter of the motion function described above.
[0146] 36 shows UI1600, which is an example of a recommended value write screen that is displayed when the recommended value write button 2705 is pressed. As described above, UI1600 has check box 603 for selecting whether or not to transfer the recommended parameter values. When the recommended value write button 2705 is pressed, UI1600 is displayed on the display unit 7 with the check box 603 checked. UI1600 is merely an example, and other parameter setting screens such as UI600 may be displayed.
[0147] (6) CPU function of the configuration support device 37 shows functions realized by the CPU 11 executing the setting assistance program 21. In addition to the functions already described, the following functions are further added.
[0148] The configuration setting unit 502 includes a display processing unit 531, a reception processing unit 532, a configuration editing unit 533, an import unit 535, a determination unit 536, a manual setting unit 537, and an automatic setting unit 540. The display processing unit 531 displays the UI 2700 on the display unit 7. The reception processing unit 532 receives user input through the operation unit 8. The configuration editing unit 533 processes addition and deletion of the master device and the slave device displayed on the UI 2700. The import unit 535 is responsible for importing the electronic file 2710, and updates the device list 2702 according to the electronic file 2710. The determination unit 536 determines whether the slave device can automatically perform communication setting based on the electronic file 2710 and the allocation information 3500, and determines whether the slave device supports automatic writing of recommended values. The manual setting unit 537 manually performs PDO setting and motion function setting based on user input through the UI 3100. Automatic setting unit 540 has a PDO automatic setting unit 541 and a motion function automatic setting unit 542. PDO automatic setting unit 541 refers to allocation information 3500, acquires PDO settings linked to the product identification information (vendor ID, product code, revision number) of the selected slave device, and reflects them in the configuration information of PLC system 1. Motion function automatic setting unit 542 refers to allocation information 3500, acquires motion function settings linked to the product identification information (vendor ID, product code, revision number) of the selected slave device, and reflects them in the configuration information of PLC system 1.
[0149] The parameter setting unit 503 further includes a recommended value setting unit 543. The recommended value setting unit 543 obtains recommended values of parameters linked to the product identification information (vendor ID, product code, revision number) of the selected slave device, and transfers and writes the recommended values to the selected slave device.
[0150] The motor access unit 550 has the above-mentioned alarm management unit 504 and a motor control command unit 551. The motor control command unit 551 executes a test run of a user program using, for example, a UI 2400 illustrated in Fig. 24. The test run may include any of a JOG run, a point run, and a return to origin.
[0151] (7) Flowchart 38 shows a method for setting cyclic communication which is executed by the CPU 11 in accordance with the setting assistance program 21. It is assumed that the UI 2700 is already displayed on the display unit 7.
[0152] In S51, the CPU 11 (import unit 535) imports the electronic file 2710 in response to a user operation.
[0153] In S 52 , the CPU 11 (import unit 535 ) displays the device list 2702 to which the information on the slave devices has been added in accordance with the contents of the electronic file 2710 .
[0154] In S53, the CPU 11 (configuration editing unit 533) arranges in the configuration setting area 2701 the slave devices selected in the device list 2702 in accordance with a user operation.
[0155] In S54, the CPU 11 (determination unit 536) determines whether the slave device selected by the user is a target for setting the recommended value. For example, the determination unit 536 may determine whether an entry linked by the product identification information (vendor ID, product code, revision number) of the slave device selected by the user is included in the allocation information 3500. If an entry linked by the product identification information of the slave device selected by the user is included in the allocation information 3500, the CPU 11 determines that the slave device is a target for setting the recommended value. Then, the CPU 11 proceeds from S54 to S55. If an entry linked by the product identification information of the slave device selected by the user is not included in the allocation information 3500, the CPU 11 determines that the slave device is not a target for setting the recommended value. Then, the CPU 11 proceeds from S54 to S57.
[0156] In S55, the CPU 11 (PDO automatic setting unit 541) reads the PDO setting associated with the slave device from the allocation information 3500, and automatically sets the PDO. For example, an object to be communicated is added according to the PDO setting read from the allocation information 3500. This associates the control command (e.g., control word, target position, status word) of the communication target with the object index (e.g., 0x6040:00, 0x607A:00, 0x60FF:00). This identifies the communication content in the cyclic communication.
[0157] In S56, the CPU 11 (motion function automatic setting unit 542) reads out the motion function setting associated with the slave device from the allocation information 3500, and automatically sets the motion function. For example, the motion function (e.g., control word, target position) and the object index (e.g., 0x6040:00, 0x607A:00) are linked in accordance with the motion function setting read out from the allocation information 3500. This identifies which object index is used to realize the motion function.
[0158] In S57, the CPU 11 (manual setting unit 537) manually sets the PDO in accordance with a user operation. For example, the PDO is manually set via the tab 3102.
[0159] In S58, the CPU 11 (manual setting unit 537) manually sets the motion function in accordance with a user operation. For example, the motion function is manually set via the tab 3103.
[0160] 39 shows a method of writing recommended values that is executed by the CPU 11 in accordance with the setting assistance program 21. It is assumed that the UI 2700 is already displayed on the display unit 7.
[0161] In S61, the CPU 11 (recommended value setting unit 543) accepts the selection of a slave device. For example, the recommended value setting unit 543 accepts the selection of a slave device via the device list 2702.
[0162] In S62, the CPU 11 (recommended value setting unit 543) determines whether the slave device selected by the user is a target for setting a recommended value. For example, the recommended value setting unit 543 may determine whether the allocation information 3500 includes a recommended value linked by the product identification information (vendor ID, product code, revision number) of the slave device selected by the user. If the slave device selected by the user is a target for setting a recommended value, the CPU 11 proceeds from S62 to S63. On the other hand, if the slave device selected by the user is not a target for setting a recommended value, the CPU 11 proceeds from S62 to S69 and disables writing of the recommended value. For example, the CPU 11 hides or grays out the recommended value write button 2705.
[0163] In S63, the CPU 11 (recommended value setting unit 543) enables writing of the recommended value. For example, the CPU 11 displays the recommended value write button 2705 so that it is operable by the user.
[0164] In S64, the CPU 11 (recommended value setting unit 543) determines whether or not the user has input an instruction to start the UI 1600. When an instruction to start the UI 1600 has been input, the CPU 11 proceeds from S64 to S65.
[0165] In S65, the CPU 11 (recommended value setting unit 543) reads the recommended value of the slave device selected by the user from the allocation information 3500. As described above, the product identification information of the slave device selected by the user is associated with the recommended value. Therefore, the recommended value can be easily identified based on the product identification information.
[0166] In S66, the CPU 11 (recommended value setting unit 543) creates the UI 1600 reflecting the recommended values, and starts up the UI 1600. As a result, the UI 1600 is displayed on the display unit 7.
[0167] In S67, the CPU 11 (recommended value setting unit 543) determines whether or not a transfer instruction has been input using the transfer execution button 607. When a transfer instruction has been input, the CPU 11 advances from S67 to S68.
[0168] In S68, the CPU 11 (recommended value setting unit 543) transfers and writes the recommended parameter value to the slave device selected by the user. This transfer of the recommended parameter value is executed by message communication (SDO communication). That is, the PC 2 sets the basic unit 3 so that the recommended value is transferred to the slave device by message communication and written. The basic unit 3 transfers the recommended value to the slave device in accordance with a write request from the PC 2. The slave device writes the recommended value to the parameter in accordance with the write request. A supplementary explanation of the recommended value in this embodiment will be given. Normally, the parameters of the slave device are set to optimal initial values (default values) according to the design philosophy of each company. For example, it is assumed that the slave device of company A has a specific parameter set to initial value A that is difficult to operate on its own in order to obtain a higher sense of security, while the slave device of company B has a specific parameter set to initial value B that is easy to operate even at the expense of some sense of security. When slave devices of company A and company B are mixed as multiple slave devices connected to a PLC, the whole system may not operate as expected (such as a motor not working for some reason). This is because the design concepts of the slave devices are not aligned. In other words, the initial value A is optimized for the slave devices of company A, and the initial value B is merely optimized for the slave devices of company B. In a PLC system in which slave devices of company A and company B are mixed, the user must look at the manual and try and error to see whether a value equivalent to the initial value A or a value equivalent to the initial value B should be set for each slave device. Therefore, in the setting support device according to this embodiment, the design concepts of the slave devices of the whole PLC system can be aligned by writing a recommended value that is optimal for the specifications of the PLC system to each slave device. This makes it easy to set the slave devices.
[0169] <Other> The PC 2 may read device values, buffer values, variable values, camera images, and the like from the basic unit 3 and the expansion unit (e.g., the motor driver 4) in real time to create graphs and display them on the display unit 7. This allows the user to monitor the current state of the PLC system 1.
[0170] On the other hand, when an event such as an error or alarm occurs, the base unit 3 or the expansion unit may record device values, buffer values, variable values, and camera images before and after the occurrence time to create history data. The PC 2 may obtain the history data by communication or via a memory card, and create graphs as necessary to display on the display unit 7.
[0171] In this way, PC2 has two types of monitor functions. Because these two monitor functions are independent, the display targets for each monitor function are unrelated. Therefore, when the user activates one of the two monitor functions, he or she must set the devices, etc. to be monitored by the activated monitor function. Also, when the user switches from one monitor function to the other, the user must reset the devices, etc. to be monitored by the other monitor function.
[0172] Therefore, in this embodiment, a PC2 (engineering tool) is provided that can transfer the monitoring target of one monitoring function to another monitoring function.
[0173] (1) Base unit The CPU 31 reads out the current values of devices stored in the device memory secured in the memory 32 and the current values of variables stored in the variable memory, and displays them on the PC 2 through the communication unit 33a. The CPU 31 acquires history data (e.g., device values, buffer values, image data, error information) from the basic unit 3 and the expansion unit 4, and stores it in the memory 32, stores it on a memory card, or transmits it to the PC 2 through the communication unit 33a. The CPU 31 may execute acquisition of history data using a predetermined event (e.g., occurrence of an error or alarm) as a trigger. The CPU 31 assigns time information indicating the time when the history data was acquired to each piece of history data.
[0174] (2) Expansion unit (2-1) Expansion units such as motion units The CPU 41 writes information to the memory 42 and reads information from the memory 42. The memory 42 may have a buffer memory. In the buffer memory, for example, coordinates of a load controlled by the motor 10 and data used for calculations executed inside the motor driver 4 are stored.
[0175] The CPU 41 acquires the current buffer value (current data) stored in the buffer memory 46, and transmits it to the PC 2 through the communication unit 43. The CPU 41 may also transmit image data acquired by a camera to the PC 2 through the communication unit 43.
[0176] (2-2) Expansion unit as a data collection unit The CPU 41 may function as a history data providing unit or a history acquiring unit instead of the basic unit 3. The CPU 41 (history acquiring unit) communicates with the basic unit 3 and other expansion units via the communication unit 43, acquires device values, variable values, buffer values, image data, etc., and stores them in the memory 42 or writes them to a memory card. The CPU 41 (history data providing unit) communicates with the PC 2 via the communication unit 43, reads out history data from the memory 42, and transmits it to the PC 2. The CPU 41 may include image data acquired by a camera in the history data.
[0177] (3) <Function of the CPU of the PC> The CPU 11 (reception unit) receives the designation of input / output data to be monitored, which is input by the user through the operation unit 8. The CPU 11 (current data acquisition unit) sequentially acquires the current input / output data (e.g., device values, buffer values, image data) in the PLC system 1. This input / output data is acquired, for example, from the basic unit 3 or the expansion unit. The CPU 11 (history data acquisition unit) acquires, as history data, the input / output data recorded in time series together with time information based on the occurrence of a predetermined event. This history data is acquired, for example, from the basic unit 3, the data collection unit, or the memory card. The CPU 11 (UI unit) generates a graph from the current data and the history data and displays the graph on the display unit 7. UI is an abbreviation for user interface. The CPU 11 (UI unit) may have a plurality of display modes. For example, in the first mode (e.g., current value mode), the CPU 11 (UI unit) has a CPU 11 (current graph generation unit) that sequentially acquires the input / output data specified through the CPU 11 (reception unit) by the CPU 11 (current data acquisition unit) and graphically displays the input / output data in time series. The CPU 11 (UI unit) may have a CPU 11 (history graph generation unit) that generates a graph screen for graphically displaying the history data acquired by the CPU 11 (history data acquisition unit) in time series in the second mode (e.g., history mode). The CPU 11 (history graph generation unit) may generate a graph screen for graphically displaying, in time series, the input / output data specified through the CPU 11 (reception unit) among the history data in the second mode (e.g., history mode). The first mode may be called the normal mode or the current value mode. The second mode may be called the history mode or the replay mode.
[0178] A user instructs switching from one of the first and second modes to the other mode through the operation unit 8. At that time, the CPU 11 (management unit) may take over information specifying a monitor target in one mode to the other mode, and may match the monitor target between the one mode and the other mode based on the information. In general, a user can select a desired mode from a plurality of modes and specify data to be monitored on a display screen of the desired mode, thereby displaying a graph of the desired data on the display screen. Therefore, when switching from one mode to the other mode is executed, the user must again specify data to be monitored on the display screen of the other mode. Requesting the user to specify a large number of monitor targets every time the mode is switched would lack usability. Therefore, usability is improved by the CPU 11 (management unit) performing a process of taking over the monitor targets. In other words, the burden on the user associated with re-specifying the monitor targets when switching modes is reduced.
[0179] The CPU 11 (management unit) may specify input / output data to be monitored in one mode based on information specifying a monitor target for the other mode. The CPU 11 (management unit) may determine whether the specified input / output data can be acquired in the other mode. For example, a current value of a certain device may be acquired, but historical data of the device may not be recorded. This is because setting of a historical target related to the historical data has been performed in the past. In this way, when the specified input / output data cannot be acquired in the other mode, the CPU 11 (management unit) may modify or create information specifying a monitor target for the other mode to exclude the specified input / output data from the monitor target in the other mode.
[0180] In this way, when one mode is the first mode (current value mode) and the other mode is the second mode (history mode), input / output data that cannot be acquired in the other mode is input / output data that is not included in the history data.
[0181] The CPU 11 (management unit) displays various screens on the display unit 7 through the CPU 11 (UI unit). The CPU 11 (management unit) may identify multiple input / output data to be monitored in one mode based on information specifying the monitor target for the other mode, and display a confirmation screen for confirming with the user whether or not to monitor each of the multiple input / output data. The CPU 11 (management unit) and the CPU 11 (reception unit) may receive, through the confirmation screen, designation of input / output data to be monitored or input / output data to be deleted from the monitor targets. Some users may wish to change some of the monitor targets between the mode before switching and the mode after switching. For this reason, the user may be given an opportunity to select the monitor targets through the confirmation screen.
[0182] The CPU 11 (UI unit) may display a graph screen for one mode and then display a graph screen for the other mode. In other words, the CPU 11 (UI unit) may display a graph screen for one mode on the display unit 7 while continuing to display the graph screen for the other mode. This will allow the user to easily compare the current data and the history data.
[0183] The CPU 11 (UI unit) may generate a graph screen in which input / output data to be monitored in one mode is overlaid with the same input / output data to be monitored in the other mode, allowing the user to easily compare the current data with the historical data.
[0184] Among the device values and buffer values, some may be obtainable from the CPU 11 (current data acquisition unit) and some may not be obtainable from the CPU 11 (current data acquisition unit). In this case, a mode displaying current data obtainable from the CPU 11 (current data acquisition unit) may be called a normal mode. Also, a mode displaying current data obtainable by the CPU 11 (special data acquisition unit) but not obtainable from the CPU 11 (current data acquisition unit) may be called a special mode. The CPU 11 (special data acquisition unit) may function as a restricted data acquisition unit that sequentially acquires input / output data that is restricted from being acquired by the CPU 11 (current data acquisition unit) among the current input / output data in the PLC system 1. The CPU 11 (current graph generation unit) of the CPU 11 (UI unit) is configured to generate a graph screen that displays, in a time series graph, input / output data designated through the CPU 11 (reception unit) among the input / output data obtained by the CPU 11 (special data acquisition unit) in the third mode (e.g., special mode). When switching from one of the current value mode, history mode, and special mode to the other mode, the CPU 11 (management unit) may transfer information specifying a monitor target in the one mode to the other mode, and may match the monitor target between the one mode and the other mode based on the information. This reduces the burden on the user of specifying a monitor target when switching between the three display modes. The range of data accessible by the current value mode may be a part of the range of data accessible by the special mode. In this case, the special mode can access all of the data accessible by the current value mode. On the other hand, the range of data accessible by the special mode may be a part of the range of data accessible by the current value mode. Alternatively, the current value mode and the special mode may have a common accessible range, but each mode may have its own unique range that only it can access. For example, one mode may be able to access both the device memory and the buffer memory, while the other mode may be able to access the device memory but not the buffer memory.Alternatively, the data memory may be divided into a first group, a second group and a third group, and one mode may only access the first group and the second group, and the other mode may only access the second group and the third group.
[0185] The information specifying the monitor target includes display settings indicating at least one of the display format of the graph of the monitor target on the graph screen, the display color of the monitor target, the display range of the monitor target, the display position of the graph of the monitor target, and the scale of the graph of the monitor target. The display settings may be stored in the storage device 12 as part of the setting data. The CPU 11 (management unit) may transfer the display settings of the monitor target in one mode to the display settings of the other mode.
[0186] <Technical ideas derived from examples> [Point A] [Perspective A1] The basic unit 3 is an example of a programmable logic controller that functions as a master of network communication. The motor driver 4 is an example of a motor driving device that functions as a slave of network communication and drives a motor based on motor control data transmitted from the master by cyclic communication. The PC 2 is an example of a setting support device that supports the setting of the PLC system 1. The storage device 12 functions as an allocation information storage unit that stores, as allocation information, a plurality of recommended adjustment parameters that are recommended to be adjusted to make the motor driving device compatible with the master and operate it, among a plurality of setting parameters for the motor driving device identified based on vendor identification information (e.g., vendor ID) and product identification information (e.g., product code and revision number), in association with the motor driving device. The display unit 7 and the display processing unit 521 are examples of a display unit that displays a list of a plurality of motor driving devices (e.g., a pull-down menu of the device selection unit 602) associated with the vendor identification information and the product identification information, respectively. The reception processing unit 522 and the device selection unit 602 are examples of a reception unit that receives the selection of one motor driving device from the list displayed on the display unit. The editing unit 523 functions as a parameter value editing unit that displays, on the display unit, an editing user interface (e.g., UI600) that is an editing user interface for adjustment-recommended parameters corresponding to a motor driving device selected by the receiving unit based on allocation information (e.g., slave device information 23) stored in the allocation information storage unit, and is common to a plurality of motor driving devices having different combinations of vendor-specific information and product-specific information, receives user operations through the editing user interface, and edits the parameter values of the adjustment-recommended parameters in accordance with the user operations. The write processing unit 525 is an example of a write processing unit that writes the parameter values edited by the parameter value editing unit to the motor driving device selected by the receiving unit.
[0187] In this way, a common parameter editing user interface is provided for multiple motor drivers manufactured by different manufacturers. This makes it easier to set up multiple motor drivers than ever before. Although a motor driver is used as an example here, this embodiment can also be applied to a slave device that operates with a PLC as a master.
[0188] [Perspective A2] The parameter value editing unit (e.g., parameter setting unit 503) may display a list of only the recommended adjustment parameters corresponding to the motor driving device selected by the reception unit (e.g., reception processing unit 522, device selection unit 602) in the editing user interface. As shown in Fig. 6 etc., the CPU 11 (display processing unit 521 of parameter setting unit 503) displays a list of only the recommended adjustment parameters corresponding to the selected motor driving device in the UI 600. This reduces the number of parameters displayed in the editing user interface, realizing a UI that is easy for the user to see and edit.
[0189] [Perspective A3] The editing user interface (e.g., UI 600) may display initial values (e.g., factory settings (default values), or values used in the previous setting) as adjustment-recommended parameters corresponding to the motor driving device selected by the reception unit (e.g., reception processing unit 522, device selection unit 602). The parameter value editing unit (e.g., editing unit 523 of parameter setting unit 503) may change the adjustment-recommended parameters from the initial values in accordance with a user operation. This allows the user to know the initial values that serve as the basis for parameter setting, making it easier to change the parameters.
[0190] [Perspective A4] The adjustment recommended parameters include at least one of the following: assignment of functions to input terminals of the motor drive device, polarity of the input terminals, whether or not to enable connection of limit switches to the input terminals, and the type of contacts related to position control or speed control. These parameters are almost essential for test running the motor driver 4, so it is recommended that the user adjust them.
[0191] [Perspective A5] The adjustment recommended parameters may further include the type of encoder method (e.g., incremental, absolute) in the motor drive device. If the encoder method is unknown, the values obtained by the encoder will be misinterpreted, making it impossible to control the motor driver 4 correctly. Therefore, by setting the type of encoder method, it becomes possible to control the motor driver 4 correctly.
[0192] [Point of View A6] A parameter value reading unit (e.g., read processing unit 527) may be further provided that reads, from the motor driving device selected by the reception unit, parameter values (e.g., current values) of parameters recommended for adjustment that are set in the motor driving device at that time. A parameter value editing unit (e.g., editing unit 523, display processing unit 521) may display the parameter values read by the parameter value reading unit on an editing user interface (e.g., UI 600). By knowing the current values of the parameters, the user will be able to correctly adjust the parameters based on the current values.
[0193] [Point of View A7] The parameter value editing unit (e.g., the comparison unit 524) may compare the parameter values edited by the parameter value editing unit with the parameter values read by the parameter value reading unit, and display the comparison result on the display unit 7. This will enable the user to compare the difference between the parameter value he or she is about to set and the current value.
[0194] [Point of View A8] When the motor drive device needs to be restarted in order to enable the adjustment-recommended parameters edited through the editing user interface in the motor drive device, the display unit 7 and the display processing unit 521 may display a message (e.g., FIG. 12) instructing the user to restart the motor drive device. As described above, unless the motor driver 4 is restarted, the parameter values may not be reflected in the motor driver 4. In such a case, by prompting the user to restart the motor driver 4, it becomes possible to reflect the parameter values in the motor driver 4.
[0195] [Point of View A9] When it is necessary to restart the motor driving device in order to enable the recommended adjustment parameters edited through the editing user interface in the motor driving device, the display unit 7 and the display processing unit 521 may display a control object (e.g., software reset button 1205) for instructing the motor driving device to be restarted remotely. This enables the user to restart the motor driver 4 remotely.
[0196] [Point of View A10] When a user operation (e.g., pressing down the write button 1203) is input that explicitly instructs writing the parameter values edited by the parameter value editing unit to the non-volatile memory of the motor drive device selected by the reception unit, the write processing unit 525 may execute writing of the parameter values to the non-volatile memory. This allows the edited parameter values to continue to be held in the motor driver 4 even if the motor driver 4 is powered off. There are slave devices in which parameter values are written to the non-volatile memory without an explicit instruction, and slave devices in which parameter values are written to the non-volatile memory based on an explicit instruction. In the latter case, by prompting the user to write, the editing results will be held in the motor driver 4 even after the power is turned off.
[0197] [Point of View A11] The adjustment recommended parameters include parameters required for test run of the motor drive device. Users often connect multiple slave devices made by different manufacturers to the basic unit 3 and check their behavior through test runs. To do this, it is necessary to set multiple slave devices to a state where they can be test run. In this embodiment, the parameters required for test run can be set through a common parameter setting screen, which is very convenient for users.
[0198] [Point of View A12] The test run may include any of the JOG run, the point run, and the home return. As described in relation to Fig. 24, the JOG run, the point run, and the home return are parts of the test run. Therefore, parameters required to execute the JOG run, the point run, and the home return are set through the parameter setting screen.
[0199] [Point of View A13] The parameter value editing unit (e.g., editing unit 523, reception processing unit 522) may accept editing of other parameters different from the adjustment-recommended parameters together with the adjustment-recommended parameters through the editing user interface. In the above description, the adjustment-recommended parameters are adjusted on the common parameter setting screen, but other parameters different from these may also be adjusted on the common parameter setting screen. For example, other parameters not required for test run may be edited on UI 600 or the like. Note that the adjustment-recommended parameters and other parameters may need to be written at the same time due to processing unit issues. In this case, the adjustment-recommended parameters and other parameters different from the adjustment-recommended parameters are transferred and written together.
[0200] [Point of View A14] The alarm management unit 504 is an example of an alarm processing unit that acquires an alarm code from the motor drive device and displays alarm information corresponding to the alarm code on the display unit 7. The alarm code may be identification information (e.g., an alarm detail code) that is transmitted from the motor driver 4 by cyclic communication or message communication and that can identify an alarm occurring in the motor driver 4.
[0201] [Point of View A15] 24 and 25, the alarm information includes at least one of the following: the name of the motor drive device (e.g., ABC XXX series) linked to the alarm code, an alarm detail code (e.g., 14-0) that includes only an index or an index and a sub-index, and an alarm message (e.g., overcurrent protection) that is text information. Conventionally, only the presence or absence of an alarm was displayed, but in this embodiment, more detailed information is displayed, so the user will be able to immediately understand the contents of the alarm without having to consult a manual or the like.
[0202] [Point of View A16] When the display language of the alarm message is multilingual, the display unit 7 and the alarm management unit 504 display the alarm message in the display language of the setting support device. This will save the user the trouble of specifying in which language the alarm message is to be displayed.
[0203] [Point of View A17] A programmable logic controller that acts as a master for network communication; a motor drive device that functions as a slave in network communication and drives a motor based on motor control data transmitted from the master through cyclic communication; The present invention provides a method for controlling a setting support device that supports settings for a system having the above-mentioned configuration. storing, in an allocation information storage unit, a plurality of adjustment-recommended parameters, among a plurality of setting parameters for a motor drive device identified based on the vendor-specific information and the product-specific information, which are recommended to be adjusted in order to make the motor drive device compatible with a master and operate the motor drive device, as allocation information, in association with the motor drive device; displaying on a display unit a list of a plurality of motor driving devices each associated with vendor specific information and product specific information; accepting a selection of one motor driving device from the list displayed on the display unit; displaying, on a display unit, an editing user interface for adjustment-recommended parameters corresponding to a selected motor driving device based on the allocation information stored in an allocation information storage unit, the editing user interface being common to a plurality of motor driving devices having different combinations of vendor-specific information and product-specific information, accepting a user operation through the editing user interface, and editing parameter values of the adjustment-recommended parameters in accordance with the user operation; writing the edited parameter values to the selected motor drive; may include.
[0204] [Point of View A18] There is provided a program (eg, setting support program 21) for causing a processor (eg, CPU 11) to execute the control method for the setting support device according to the seventeenth aspect.
[0205] [Point of View B] [Perspective B1] The basic unit 3 is an example of a programmable logic controller that functions as a master of network communication. The motor driver 4 is an example of a motor driving device that functions as a slave of network communication and drives a motor based on motor control data transmitted from the master by cyclic communication. The PC 2 is an example of a setting support device that supports the setting of the PLC system 1. The CPU 11, the configuration setting unit 502, and the configuration editing unit 533 are examples of a configuration editing unit that selects one of a plurality of motor driving devices identified by vendor specific information (e.g., vendor ID) and product specific information (e.g., product code, revision number), and sets the selected motor driving device as a slave for the programmable logic controller that functions as a master. The storage device 12 is an example of a storage unit that stores allocation information (e.g., allocation information 3500) associated with the vendor specific information and the plurality of product specific information. The allocation information may include mapping information (e.g., PDO setting) that maps a data object handled by the motor driving device as a communication target of cyclic communication, and a recommended value of a setting parameter for the motor driving device. The configuration setting unit 502 sets the mapping of data objects to be transmitted by the master through cyclic communication based on mapping information included in the allocation information corresponding to the combination of vendor-specific information and product-specific information of the motor drive device set for the programmable logic controller by the configuration editing unit. Furthermore, the configuration setting unit 502 sets the master to write the recommended values of the setting parameters included in the allocation information for the motor drive device to the motor drive device through message communication. This makes it easier to set up cyclic communication and write the recommended values. In other words, it makes it easier to set up the PLC and the motor driver than before. The recommended values are, for example, connecting a limit switch to the basic unit 3 and disabling the limit input terminal in the motor driver 4, whether the contact type is an a-contact or a b-contact, etc.
[0206] [Perspective B2] The storage unit (storage device 12) may further be configured to store mapping information, recommended values of setting parameters, and motion function settings in association with each other in response to a combination of vendor-specific information and product-specific information. As illustrated in Fig. 35, the motion function settings indicate which bits of a data object transmitted by cyclic communication are assigned to control data for controlling functions of the motor drive device. This identifies the data object for realizing the motion function.
[0207] [Perspective B3] The recommended values of the setting parameters include recommended values that enable the test run of the motor drive device through the master (basic unit 3). This allows the user to easily start the test run.
[0208] [Perspective B4] As described in relation to Fig. 24, the test run may include a JOG operation in which the motor drive device is operated for the number of times or while a rotation instruction button (e.g., - direction button / + direction button in Fig. 24) is pressed. The test run may include a point operation in which the motor drive device is operated so that the load moves to a plurality of pre-specified points. The test run may include a point-return operation in which the load returns to the origin.
[0209] [Point of View B5] The setting parameters may include at least one of a value for enabling or disabling the limit switch and information indicating the type of contact related to position control or speed control (eg, a-contact, b-contact).
[0210] [Point of View B6] The CPU 11 (import unit 535) may function as a generating unit that reads out the electronic file 2710 corresponding to the selected motor driving device and generates mapping information (PDO settings) based on the electronic file. This saves the user the trouble of manually creating mapping information.
[0211] [Point of View B7] The generating unit (CPU 11, import unit 535) may read an electronic file corresponding to the selected motor driving device, and determine whether or not the selected motor driving device is a motor driving device that requires recommended values of setting parameters based on the electronic file. If the selected motor driving device is a motor driving device that requires recommended values of setting parameters, the generating unit (CPU 11, import unit 535) reads the recommended values of setting parameters from the electronic file or allocation information 3500 and writes them to the selected motor driving device. In this way, the mapping information may be created by analyzing the electronic file provided by the vendor. This will further reduce the user's efforts.
[0212] [Point of View B8] The cyclic communication is any one of ETHERCAT communication, ETHERNET / IP communication, PROFINET communication, and MODBUS communication. Note that these are only examples of cyclic communication, and other types of cyclic communication may be adopted.
[0213] [Point of View B9] A programmable logic controller that acts as a master for cyclic communication; a motor drive device that functions as a slave in cyclic communication and drives a motor based on motor control data transmitted from the master through the cyclic communication; A control method for a setting support device that supports settings for a PLC system having the above-mentioned is also provided. selecting one of a plurality of motor driving devices, each of which is identified by the vendor-specific information and the product-specific information, and setting the selected motor driving device as a slave for the programmable logic controller functioning as a master; storing in a storage unit allocation information associated with each of the vendor-specific information and the multiple pieces of product-specific information, the allocation information including mapping information for mapping data objects handled by the motor drive device as communication targets of cyclic communication, and recommended values of setting parameters for the motor drive device; setting mapping of data objects to be transmitted by the master through cyclic communication based on mapping information included in allocation information corresponding to a combination of vendor-specific information and product-specific information of the motor drive device set in the programmable logic controller, and setting the master to write recommended values of setting parameters included in the allocation information for the motor drive device to the motor drive device via message communication; has.
[0214] [Point of View B10] The setting support program 21 is an example of a program that causes a processor to execute the control method of the setting support device described in Viewpoint B9.
[0215] The invention is not limited to the above-described embodiment, and various modifications and variations are possible within the scope of the gist of the invention.
Claims
1. A programmable logic controller that acts as a master for cyclic communication; a motor drive device that functions as a slave in the cyclic communication and drives a motor based on motor control data transmitted from the master through the cyclic communication; A setting support device for supporting settings for a PLC system having a configuration editing unit that selects one of a plurality of motor driving devices, each of which is identified by vendor-specific information and product-specific information, and sets the selected motor driving device as the slave in the programmable logic controller that functions as the master; a storage unit that stores allocation information associated with vendor-specific information and a plurality of pieces of product-specific information, the allocation information including mapping information that maps data objects handled by the motor drive device as communication targets of the cyclic communication, and recommended values of setting parameters for the motor drive device; a configuration setting unit that sets mapping of data objects to be transmitted by the master through the cyclic communication based on the mapping information included in the allocation information corresponding to a combination of vendor-specific information and product-specific information of the motor drive device set for the programmable logic controller by the configuration editing unit, and sets the master to write recommended values of the setting parameters included in the allocation information for the motor drive device to the motor drive device via message communication; A setting support device comprising:
2. the storage unit is further configured to store the mapping information, the recommended setting parameter values, and the motion function settings in association with each other in response to a combination of vendor-specific information and product-specific information; The setting assistance device according to claim 1 , wherein the motion function setting indicates to which bit of a data object transmitted by the cyclic communication control data for controlling a function of the motor drive device is assigned.
3. 2. The setting assistance device according to claim 1, wherein the recommended values of the setting parameters are recommended values that enable a test run of the motor drive device through the master.
4. The trial run is JOG operation in which the motor drive device is operated for the number of times or while the rotation instruction button is pressed; A point operation in which the motor drive device is operated so as to move a load to a plurality of pre-specified points; A decrement return operation for returning the load to the origin; 4. The setting support device according to claim 3, wherein the setting support device is any one of the following:
5. The setting support device according to claim 1 , wherein the setting parameters include at least one of a value for enabling or disabling a limit switch and information indicating a type of contact related to position control or speed control.
6. The setting support device according to claim 1 , further comprising a generating unit that reads an electronic file corresponding to the selected motor drive device and generates the mapping information based on the electronic file.
7. 7. The setting support device according to claim 6, wherein the generation unit reads out an electronic file corresponding to the selected motor driving device, determines based on the electronic file whether the selected motor driving device is a motor driving device that requires the recommended value of the setting parameter, and if the selected motor driving device is a motor driving device that requires the recommended value of the setting parameter, reads out the recommended value of the setting parameter from the allocation information and writes it to the selected motor driving device.
8. 2. The setting support device according to claim 1, wherein the cyclic communication is any one of ETHERCAT communication, ETHERNET / IP communication, PROFINET communication, and MODBUS communication.
9. A programmable logic controller that acts as a master for cyclic communication; a motor drive device that functions as a slave in the cyclic communication and drives a motor based on motor control data transmitted from the master through the cyclic communication; A control method for a setting support device that supports setting of a PLC system having the following features: selecting one of a plurality of motor driving devices, each of which is identified by vendor-specific information and product-specific information, and setting the selected motor driving device as the slave for the programmable logic controller functioning as the master; storing allocation information associated with each of the vendor-specific information and a plurality of pieces of product-specific information in a storage unit, the allocation information including mapping information for mapping data objects handled by the motor drive device as communication targets of the cyclic communication, and recommended values of setting parameters for the motor drive device; setting mapping of data objects to be transmitted by the master through the cyclic communication based on the mapping information included in the allocation information corresponding to a combination of vendor-specific information and product-specific information of the motor drive device set for the programmable logic controller, and setting the master to write recommended values of the setting parameters included in the allocation information for the motor drive device to the motor drive device via message communication; A control method for a setting assistance device comprising:
10. A program causing a processor to execute the control method for the setting support device according to claim 9.
Citation Information
Patent Citations
Motor drive device
JP2015012025A
