[go: up one dir, main page]

WO2012124153A1 - Simulateur - Google Patents

Simulateur Download PDF

Info

Publication number
WO2012124153A1
WO2012124153A1 PCT/JP2011/056925 JP2011056925W WO2012124153A1 WO 2012124153 A1 WO2012124153 A1 WO 2012124153A1 JP 2011056925 W JP2011056925 W JP 2011056925W WO 2012124153 A1 WO2012124153 A1 WO 2012124153A1
Authority
WO
WIPO (PCT)
Prior art keywords
execution
program
task
unit
simulation
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Ceased
Application number
PCT/JP2011/056925
Other languages
English (en)
Japanese (ja)
Inventor
泰規 阪口
文明 成谷
義也 柴田
大谷　拓
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Omron Corp
Original Assignee
Omron Corp
Omron Tateisi Electronics Co
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Omron Corp, Omron Tateisi Electronics Co filed Critical Omron Corp
Publication of WO2012124153A1 publication Critical patent/WO2012124153A1/fr
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING OR CALCULATING; COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/36—Prevention of errors by analysis, debugging or testing of software
    • G06F11/3698—Environments for analysis, debugging or testing of software

Definitions

  • the present invention relates to a simulation apparatus.
  • FA Regenery Factory
  • various slave devices that collect and control data of production facilities installed in a factory and a master device that centrally manages a plurality of slave devices are connected via a communication bus.
  • the production facility is controlled by the network.
  • the master device controls a plurality of connected slave devices or acquires information from each slave device by executing a task including a plurality of programs.
  • FIG. 7 is a diagram showing a configuration example of a field network.
  • a master device 200 PLC: Programmable Logic Controller
  • a plurality of slave devices 300 are connected directly or indirectly via a cable 400 or an I / O unit 500 provided in the device. Is formed.
  • the slave device 300 includes a power supply unit, a motor unit, a counter unit, an image unit, a communication unit, an I / O unit, and the like.
  • the topology of the communication bus can take various topologies such as lines, daisy chains, trees, and stars, depending on the field network standard.
  • the master device 200 is configured so that the user can set the operation of the master device 200, display the operation status of the field network 100, design the network system (for example, determine the connection configuration between the master device and the slave device, and execute the master device 200)
  • a management apparatus 600 for performing task creation may be connected.
  • the management apparatus 600 is configured by a personal computer installed with a setting tool.
  • a general procedure for creating a task to be executed by a master device is as follows.
  • a development environment (programming tool) implemented in the management device 600 or the like, a plurality of program codes to be executed by the master device are created.
  • the program is described in, for example, a ladder language, SFC language, structured text, or the like. Recently, multiple languages are often mixed.
  • One executable file (task) is created by compiling and building a plurality of created programs together.
  • the created task is executed (simulated) by a simulator installed in the management device 600 or the like, and it is confirmed that the task has no defect (that is, the master device performs an intended operation). (4) If a defect is found, return to (2) to correct the program and execute the simulation of (3).
  • the object of the present invention is to provide a technique that enables only a part of programs included in a task to be executed in a small number of work steps and in a short time.
  • the present invention adopts the following configuration.
  • the simulation apparatus of the present invention is a simulation apparatus that simulates the operation of the apparatus, and includes a registration unit that causes a user to register a program group executed by the device as a task, and each task included in the task registered by the registration unit. Selection means for allowing a user to select execution / non-execution of a program; and execution means for executing only a program selected to be executed by the selection means among the programs included in the task registered by the registration means. It is characterized by that.
  • execution / non-execution of each program included in the task is selected by the user, and only the selected program is executed. This eliminates the need for tasks such as creating and rewriting tasks for simulation and creating an execution file for each simulation. As a result, only a part of the programs included in the task can be executed in a small number of work steps and in a short time.
  • the present invention may be regarded as a simulation apparatus having at least a part of the above means, or a simulation method including at least a part of the above process, or a simulation program for realizing such a method and a program thereof are recorded. It can also be regarded as a recording medium.
  • a simulation apparatus having at least a part of the above means, or a simulation method including at least a part of the above process, or a simulation program for realizing such a method and a program thereof are recorded. It can also be regarded as a recording medium.
  • FIG. 1 is a block diagram illustrating a schematic configuration of a design support system according to the embodiment.
  • FIG. 2 is a block diagram illustrating a schematic functional configuration of the PC according to the embodiment.
  • FIG. 3 is a block diagram showing an example of a functional configuration of the network system design support program (simulation program) according to the present embodiment.
  • FIG. 4 is a diagram illustrating an example of a GUI displayed on the display.
  • FIG. 5 is a diagram illustrating an example of a GUI displayed on the display.
  • FIG. 6 is a flowchart illustrating an example of a processing flow of the simulation apparatus according to the present embodiment.
  • FIG. 7 is a diagram illustrating a configuration example of a general field network.
  • FIG. 1 is a block diagram illustrating a schematic configuration of a design support system according to the present embodiment.
  • This design support system is a system for supporting the design of a network system configured by joining at least one slave device on a communication bus that draws a line, tree, or star topology starting from a master device.
  • This network system is an industrial field network configured by connecting ports provided in each of a master device and a slave device.
  • EtherCAT registered trademark
  • the ports provided in the slave device have two connection interfaces of an external bus (RJ45) and an internal bus (E-Bus).
  • RJ45 external bus
  • E-Bus internal bus
  • the design support system of the present embodiment is not limited to the design of an EtherCAT (registered trademark) network system, and there may be other types of port connection interfaces other than external and internal.
  • the design support system 1 includes a display 2 that displays a GUI (graphical user interface) for design support, a PC (personal computer) 3 that controls the GUI displayed on the display 2, and a command that allows the user to operate the GUI to the PC 3. And an input device 4 including a keyboard and a mouse for inputting.
  • the design support system 1 allows a user to design a network system offline.
  • the design support system 1 may be configured such that a user can input a command to an online network system by connecting to an actual device of the network system, for example, a master device (PLC).
  • PLC master device
  • FIG. 2 is a block diagram illustrating a schematic functional configuration of the PC 3 (simulation apparatus) according to the present embodiment.
  • the PC 3 includes a storage unit 31, an acquisition unit 32, an input unit 33, a generation unit 34, and an image output unit 35.
  • the storage unit 31 stores slave information data in which unique information of the slave device is described.
  • the slave information data is, for example, an XML format file that describes the model number of the slave device, vendor identification information, port information provided in the slave device, and the like.
  • the obtaining unit 32 obtains information on the port provided in the slave device from the slave information data stored in the storage unit 31.
  • the port information includes, for example, the number of ports provided in the slave device, the type of port connection interface (internal bus, external bus, etc.), and port identification information (name, etc.).
  • the input unit 33 receives a signal input from the input device 4 and inputs a command to the generation unit 34.
  • the generation unit 34 generates a design support GUI in accordance with the command input from the input unit 33. Further, image data that can be displayed on the display 2 is generated based on the generated GUI data, and is output to the image output means 35.
  • the GUI generated by the generation unit 34 will be described later.
  • the image output unit 35 outputs the image data input from the generation unit 34 to the display 2.
  • the PC 3 has a known configuration such as a CPU (not shown), memory, disk, various input / output interfaces, and a bus for connecting them. (Hard disk drive) etc.
  • the acquisition unit 32 and the generation unit 34 are realized by the CPU reading and executing the network system design support program installed in the HDD or the like from the disk.
  • the input unit 33 and the image output unit 35 are realized by a mouse connection terminal, a keyboard connection terminal, and a display connection terminal that are connected to a CPU or the like via a bus.
  • FIG. 3 is a block diagram illustrating an example of a functional configuration of the network system design support program (simulation program) according to the present embodiment (functions realized by the CPU of the PC 3 executing the program).
  • the operation of the master device is simulated by the CPU of the PC 3 executing the simulation program.
  • a simulation program 700 includes a program registration unit 701, an execution file creation unit 702, a setting file creation unit 703, a program selection unit 704, a program execution unit 705, and the like.
  • the program registration unit 701 causes the user to register a group of programs to be executed by the master device as a task. Specifically, the program registration unit 101 causes the user to create a task to be executed by the master device and add (register) the program to the created task.
  • a plurality of tasks can be created, and priority and execution cycle can be set for each task. For example, when a priority is set for a task, the tasks are executed in order from the task with the highest priority. When an execution cycle is set for the task, the task is repeatedly executed at the set execution cycle.
  • the task configuration is configured by a plurality of execution files obtained by compiling and building for each execution unit of the program and a setting file indicating the execution order of the plurality of execution files.
  • execution / non-execution of the program can be switched for each execution unit.
  • debugging work only the program to be checked (for example, the modified program) is compiled and built, and only the executable file created thereby is executed, so that development efficiency can be greatly improved compared to the conventional method.
  • Such a configuration is realized by an execution file creation unit 702, a setting file creation unit 703, a program selection unit 704, and a program execution unit 705 described below.
  • the execution file creation unit 702 creates an execution file for each program included in the task registered by the program registration unit 701. Specifically, the execution file creation unit 702 creates an execution file of the program registered by the program registration unit 701 in the minimum unit of the program. For example, when the program is a ladder program, the execution file is created in units of sections. That is, in the simulation program according to the present embodiment, an execution file is created by compiling and building for each program (or for each minimum unit of the program).
  • program is a ladder program (hereinafter simply referred to as “program”), and the execution file is created in section units.
  • execution file may be created in accordance with an instruction to create an execution file from the user, or may be created automatically.
  • the execution file may be automatically created at the timing when the program is registered in the task or when the simulation is performed.
  • execution file may be created in units of programs (units of ladder programs).
  • the setting file creation unit 703 creates a setting file indicating the execution order of the execution files created by the execution file creation unit 702 for each task.
  • the setting file may be created in accordance with a setting file creation instruction from the user, or may be created automatically.
  • the setting file may be automatically created at the timing when the program is registered in the task or when simulation is performed.
  • the execution order of the execution files may be the order in which the program is registered in the task, or may be the order specified by the user separately from the registration order.
  • the program selection unit 704 causes the user to select execution / non-execution of each program included in the task registered in the program registration unit 701. Specifically, the program selection unit 704 causes the user to select execution / non-execution of each execution file created by the execution file creation unit 702. Then, the program execution unit 705 is instructed to execute / non-execute the execution file.
  • execution / non-execution of the execution file may be selected for each program, or may be selected for each section (that is, for each execution file).
  • execution / non-execution of all execution files corresponding to the program is selected at a time.
  • the program execution unit 705 switches execution / non-execution of an execution file in accordance with an instruction from the program selection unit 704 when executing a task. Thereby, only a part of the programs included in the task (the program or section selected to be executed by the program selection unit 704) is executed. Specifically, among the execution files created by the execution file creation unit 702, only the execution files selected for execution by the program selection unit 704 are executed in the order indicated by the setting file. That is, the program execution unit 705 simulates only the operation of a part of programs (or sections) included in the task.
  • FIG. 4 is a diagram illustrating an example of a GUI displayed on the display 2.
  • the user can perform operations such as task creation, program registration to the task, program execution order setting, task priority setting, and task execution cycle setting. For example, the user can perform the above operation from a menu screen displayed by a predetermined operation (such as a right mouse click). Further, the above operation can be performed using a button 803 in the registration screen 801.
  • the created task, the registered program, and the name of the section are displayed in a tree shape.
  • the display mode is not limited to a tree shape. As long as the task and the program included in the task can be confirmed, the task may be displayed in any manner.
  • the selection screen 802 displays a list of programs and a check box associated with each program in the list. Specifically, on the selection screen 802, the names of tasks, programs, and sections are displayed in a tree shape as in the registration screen 801, and a check box 804 is provided for each name (item). Are displayed in association with each other.
  • a user can select execution / non-execution of a task, execution / non-execution of a program, and execution / non-execution of a section using a check box 804.
  • the selection screen 802 may display the names of all programs including those not registered in the task. However, if the names of all the programs are displayed, the number of displays (the number of programs and the number of sections) may become enormous, so it is preferable to display only the names of the programs registered in the task. Accordingly, the user can easily select a program or section to be executed, and the convenience for the user is improved.
  • execution / non-execution of the execution file is selected using the check box 804
  • the execution file non-execution selection method is not limited to this.
  • execution / non-execution of an execution file may be selected using a text box 805 as shown in FIG.
  • the configuration may be such that only the execution file corresponding to the program having the name input in the text box 805 is executed (or not executed).
  • the check box is used, the user can easily select execution / non-execution of the execution file.
  • the registration screen 801 and the selection screen 802 are different windows, but the screen of each function is not limited thereto.
  • the created task, the registered program, and the section name may be displayed in a tree shape on the registration screen 801, and a check box may be displayed in association with each name.
  • the content of the task is information that is not changed immediately after being confirmed once, and is rarely confirmed during the execution of the simulation. Therefore, there is no particular problem even if it is not displayed after confirmation.
  • the registration screen 801 and the selection screen 802 are different windows, only the registration screen 801 can be closed (or minimized) after the task is determined.
  • the empty area can be used as an area for displaying other information necessary for the user (for example, an editor display area). As a result, the user can grasp more necessary information (for example, a moving program and its contents) during the simulation execution, and the convenience of the user is improved.
  • FIG. 6 is a flowchart showing an example of the flow of processing of the simulation program according to the present embodiment.
  • the program registration unit 701 causes the user to create a task (step S101).
  • task A composed of programs P1, P2, and P3 is created.
  • the program P1 is composed of sections S11 to S14
  • the program P2 is composed of sections S21 to S22
  • the program P3 is composed of sections S31 to S35.
  • the task B is also created. However, the following description will be given focusing on the task A.
  • the execution file creation unit 702 creates an execution file of the created task in section units (step S102).
  • the setting file creation unit 703 creates a setting file (step S103).
  • the registration screen 801 shows programs and sections in the order of execution. That is, in the example of FIG. 4, a setting file indicating the order of program P1 (section S11 ⁇ S12 ⁇ S13 ⁇ S14) ⁇ program P2 (section S21 ⁇ S22) ⁇ program P3 (section S31 ⁇ S32 ⁇ S33 ⁇ S34 ⁇ S35). Is created.
  • the program execution unit 705 determines whether to execute the execution file to be executed (simulation target). (Step S104). Specifically, the program execution unit 705 determines whether execution is instructed for the execution target execution file. If execution is instructed (step S104: YES), the process proceeds to step S107. If execution is not instructed (step S104: NO), the process proceeds to step S105.
  • the execution file of section S11 is first set as the execution target.
  • the program selection unit 704 instructs execution of the execution file of the section S11.
  • step S105 the program execution unit 705 executes (simulates) the execution file to be executed.
  • step S105 it is determined whether or not to end the simulation (step S106). If the simulation is to be ended (step S106: YES), this flow is ended. If not (step S106: NO), the process proceeds to step S107.
  • the program execution unit 705 may perform or a determination unit (not illustrated) may perform. Whether or not to end may be determined according to the presence or absence of a simulation end instruction from the user, for example. The determination may be made according to whether the task has been executed a predetermined number of cycles.
  • step S107 the program execution unit 705 switches the execution target execution file to the next execution file in accordance with the setting file created in step S103. Then, the process returns to step S104.
  • the execution file of section S12 is the execution target.
  • step S107 If there is no next executable file (when the execution of one cycle is completed), the execution file is switched to the first execution file in the task in step S107. Then, the processing from step S104 is resumed at the set execution cycle.
  • execution / non-execution of the program registered in the task is selected by the user, and only the selected program is executed.
  • only a part of the programs included in the task can be executed in a small number of work steps and in a short time.
  • an executable file is created for each program and only the executable file selected by the user is executed, the above work becomes unnecessary, and some programs included in the task with a small number of work steps and a short time Can only run.
  • execution file is created in the minimum unit of the program
  • execution / non-execution of the program can be switched in the minimum unit.
  • the user can select execution / non-execution of the execution file regardless of whether the simulation is being executed. If the execution / non-execution selection state of the executable file is changed during the simulation, the changed selection is performed during the current cycle of the task that is executed periodically (for example, immediately after the selection state is changed). The simulation may be continued while reflecting the state, or the changed selected state may be reflected at the timing of starting the next cycle.
  • the simulation apparatus of the present invention is a simulation apparatus that simulates the operation of the apparatus, and includes a registration unit that causes a user to register a program group executed by the device as a task, and each task included in the task registered by the registration unit. Selection means for allowing a user to select execution / non-execution of a program; and execution means for executing only a program selected to be executed by the selection means among the programs included in the task registered by the registration means. It is characterized by that.
  • execution / non-execution of each program included in the task is selected by the user, and only the selected program is executed. This eliminates the need for tasks such as creating and rewriting tasks for simulation and creating an execution file for each simulation. As a result, only a part of the programs included in the task can be executed in a small number of work steps and in a short time.
  • the simulation apparatus of the present invention further includes an execution file creation unit that creates an execution file for each program included in the task registered by the registration unit.
  • the selection unit causes the user to select execution / non-execution of each execution file created by the execution file creation unit, and the execution unit includes the execution file created by the execution file creation unit. It is preferable to execute only the execution file whose execution is selected by the selection means. With such a configuration, an executable file is created for each program, and only the executable file selected by the user is executed. Therefore, creation and rewriting of tasks for simulation and execution files for each simulation are executed. A work such as creation becomes unnecessary, and only an execution file corresponding to a part of programs included in the task can be executed in a short work man-hour and in a short time.
  • the execution file creation means creates an execution file in a minimum unit of a program.
  • execution / non-execution of a program can be switched in a minimum unit.
  • the screen for allowing the user to select execution / non-execution of the program preferably includes a list of programs and a check box associated with each program in the list.
  • the screen for allowing the user to register the task and the screen for allowing the user to select execution / non-execution of the program are different windows.
  • the content of the task is information that is not changed immediately after being confirmed once, and is rarely confirmed during the execution of the simulation. Therefore, there is no particular problem even if it is not displayed after confirmation.
  • the screen that allows the user to register the task (registration screen) and the screen that allows the user to select whether to execute or not execute the program (selection screen) are different windows, only the registration screen is closed (or minimized) after the task is confirmed.
  • the vacant area can be used as an area for displaying other information necessary for the user. As a result, the user can grasp more necessary information during the simulation execution, and the convenience of the user is improved.
  • the present invention may be regarded as a simulation apparatus having at least a part of the above means, or a simulation method including at least a part of the above process, or a simulation program for realizing such a method and a program thereof are recorded. It can also be regarded as a recording medium.
  • a simulation apparatus having at least a part of the above means, or a simulation method including at least a part of the above process, or a simulation program for realizing such a method and a program thereof are recorded. It can also be regarded as a recording medium.

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Computer Hardware Design (AREA)
  • Quality & Reliability (AREA)
  • Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Debugging And Monitoring (AREA)
  • Stored Programmes (AREA)

Abstract

La présente invention concerne une technique qui ne permet que l'exécution de certains programmes inclus dans une tâche rapidement avec une faible quantité d'heures-personnes. Ce simulateur est un simulateur pour simuler des opérations d'un dispositif. Le simulateur est caractérisé en ce qu'il comporte un moyen d'enregistrement pour inviter un utilisateur à enregistrer, sous la forme d'une tâche, un groupe de programmes à exécuter par le dispositif ; un moyen de sélection pour inviter l'utilisateur à sélectionner l'exécution/la non-exécution des programmes respectifs contenus dans la tâche qui a été enregistrée à l'aide du moyen d'enregistrement ; et un moyen d'exécution, pour exécuter, parmi les programmes contenus dans la tâche qui a été enregistrée à l'aide du moyen d'enregistrement, uniquement les programmes qui ont été sélectionnés pour être exécutés à l'aide du moyen de sélection.
PCT/JP2011/056925 2011-03-15 2011-03-23 Simulateur Ceased WO2012124153A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
JP2011056382 2011-03-15
JP2011-056382 2011-03-15

Publications (1)

Publication Number Publication Date
WO2012124153A1 true WO2012124153A1 (fr) 2012-09-20

Family

ID=46830261

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/JP2011/056925 Ceased WO2012124153A1 (fr) 2011-03-15 2011-03-23 Simulateur

Country Status (1)

Country Link
WO (1) WO2012124153A1 (fr)

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JPH08286901A (ja) * 1995-04-14 1996-11-01 Yamatake Honeywell Co Ltd ソフトウエア部品の再利用システム
JP2006107378A (ja) * 2004-10-08 2006-04-20 Advanced Telecommunication Research Institute International 設計支援装置
JP2010157108A (ja) * 2008-12-26 2010-07-15 Canon Inc ソフトウエア評価方法及びそれを実現する情報処理装置

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JPH08286901A (ja) * 1995-04-14 1996-11-01 Yamatake Honeywell Co Ltd ソフトウエア部品の再利用システム
JP2006107378A (ja) * 2004-10-08 2006-04-20 Advanced Telecommunication Research Institute International 設計支援装置
JP2010157108A (ja) * 2008-12-26 2010-07-15 Canon Inc ソフトウエア評価方法及びそれを実現する情報処理装置

Similar Documents

Publication Publication Date Title
CN112559315B (zh) 用于自动化对象的测试框架
JP5120473B2 (ja) ネットワークシステムの設計支援装置
JP5506822B2 (ja) プログラム作成支援装置
US20170032058A1 (en) Graphical Design Verification Environment Generator
US9176490B2 (en) Control program generation device, control program generation program, and control program generation method
US20140280528A1 (en) State machine configurator
CN115840421A (zh) 开发工业控制编程的系统、对工业系统编程的方法和介质
US8793668B2 (en) Protocol independent programming environment
JP5498446B2 (ja) ラダープログラム作成装置およびラダープログラム作成方法
KR20150066377A (ko) Ｄｅｖｓ 기반의 시뮬레이션 프레임워크 시스템 및 이를 이용한 시뮬레이션 방법
EP3848866A1 (fr) Procédé et système de gestion de flux de travail d'ingénierie dans un environnement informatique en nuage
WO2012104959A1 (fr) Dispositif de création de composants d'un programme sfc de mouvement
JP7238678B2 (ja) 情報処理装置、サポートプログラムおよびサポートシステム
US20100063606A1 (en) Automated derivation of a logic-controller-behavior-model from a mechanical-machine-operation-model
CN118938791A (zh) 基于仓储物流产线的plc虚拟调试方法和系统
JP5212508B2 (ja) デバッグ装置
WO2012124153A1 (fr) Simulateur
EP4209893A1 (fr) Procédé et système permettant de générer un projet d'ingénierie d'automatisation dans une installation technique à l'aide d'une approche multidisciplinaire
CN112204480B (zh) 信息处理装置以及计算机可读记录介质
CN112272820B (zh) 支持装置以及支持程序的记录介质
Scott Learning RSLogix 5000 Programming: Build Robust PLC Solutions with ControlLogix, CompactLogix, and Studio 5000/RSLogix 5000
US12420408B1 (en) Human machine interface recipe building system for a robotic manufacturing system
EP4636515A1 (fr) Dispositif d'aide au développement, procédé d'aide au développement et programme d'aide au développement
JP7631921B2 (ja) 開発支援装置、開発支援方法および開発支援プログラム
CN117882050B (zh) 用于生成与特定工程环境兼容的工程程序的方法和系统

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 11860752

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 11860752

Country of ref document: EP

Kind code of ref document: A1