Development support device

Abstract

Provided is a development support device capable of obtaining a total number of steps of a load, a required time when a program is executed is predicted. The development support device of the embodiment is a development support device that supports development of a program including a function block. The development support device of the embodiment includes a step counter that counts a number of execution steps of the function block indicating a number of processes executed in the function block, a frequency counter that counts a number of times of use of the function block used in the program, and an arithmetic unit that calculates a product of the number of times of use of the function block and the number of execution steps of the function block, and outputs the number of execution steps of the function block in the program.

Description

Technical Field

[0001] Embodiments of the present invention relate to a program development support device. Background Technology

[0002] In the development of programs for embedded systems, it is sometimes necessary to predict the load and time required for program execution. When developing programs for functional units (POUs) using engineering tools and other development support devices, information called POU entries is obtained, which includes the POU number, program name, category, whether the generation is complete (progress), generation date and time, number of steps, etc.

[0003] However, the number of steps included in the POU entry is output for the purpose of confirming the controller's memory usage, and therefore does not represent the number of execution steps as a representation of the amount of processing during program execution. Previously, the total number of steps used to predict the load and required time during program execution was calculated manually.

[0004] Furthermore, when the program contains function blocks (FBKs), it is difficult to count the total number of steps because the purpose of using function blocks is to access other function blocks, etc.

[0005] Existing technical documents Patent documents Patent Document 1: Japanese Patent Application Publication No. 2012-59078 Summary of the Invention

[0006] The technical problem that the invention aims to solve Therefore, conventional development support devices cannot obtain the total number of steps required to predict the load and time during program execution. The purpose of this invention is to provide a development support device capable of obtaining the total number of steps required to predict the load and time during program execution.

[0007] Means for solving technical problems The development support apparatus of the embodiment is a development support apparatus that supports the development of programs containing function blocks. The development support apparatus of the embodiment includes: a step counter that counts the number of execution steps of the function block, which represents the number of processes executed in the function block; a count counter that counts the number of times the function block is used in the program; and an arithmetic unit that calculates the product of the number of times the function block is used and the number of execution steps of the function block, and outputs the number of execution steps of the function block in the program. Attached Figure Description

[0008] Figure 1 This is a diagram illustrating an example of the program structure of the processing object of the development support device used as an implementation method.

[0009] Figure 2 This is a diagram illustrating an example of the execution content, binary representation, and steps of program MS000.

[0010] Figure 3 This is a diagram illustrating an example of the execution content, binary representation, and steps of the program USR_FBK2.

[0011] Figure 4 This is a block diagram illustrating the functional structure of the development support device for implementing the method.

[0012] Figure 5 This is a flowchart illustrating the operation of the development support device for implementing the method.

[0013] Figure 6 This is a diagram showing an example of a POU entry displayed in a development support device for an implementation method.

[0014] Figure 7 This is a flowchart illustrating the actions of function block processing in the development support device for implementing the method.

[0015] Figure 8 This is a diagram of an example of a table that represents the count of the number of times a function block in the development support device for an implementation method is used.

[0016] Figure 9 This is a diagram of an example of a table showing the count of the number of times a function block of each task category is used in the development support device of the implementation method.

[0017] Figure 10 This is a diagram of an example of a table showing the product of the number of times a recording function block is used and the number of execution steps in a development support device for an implementation method.

[0018] Figure 11 This is a diagram illustrating an example of a table in a development support device for an implementation that records the number of times a function block for each task category is used and the total number of steps.

[0019] Figure 12 This is a diagram illustrating an example of the output information of a development support device for an implementation method. Detailed Implementation

[0020] (Method for calculating the total number of steps) The development support apparatus of the embodiment will now be described in detail with reference to the accompanying drawings. In the development support apparatus of this embodiment, the number of times each function block is used and the number of execution steps are calculated according to each task category. Specifically, the usage destination information of all function blocks is listed, and the number of times each function block is used is calculated. Based on this calculation result, the total number of steps can be calculated.

[0021] Figure 1This is an example of a program structure for a development support device to be used as a processing object in an implementation. In the examples described below, the task categories are three types: Main (MS), High-Speed ​​(HS), and SS (Ultra-High-Speed).

[0022] like Figure 1 As shown, the programs that are processed include program MS000 of task category MS, program HS000 of task category HS, and program SS000 of task category SS. Furthermore, the programs that are processed include function blocks USR_FBK1, USR_FBK2, and USR_FBK3. A function block is a program element that outputs more than one result if a certain input value is obtained; it is componentized as a reusable circuit block. These programs or function blocks can be managed as a POU.

[0023] like Figure 1 As shown, program MS000 contains two function blocks USR_FBK2. Similarly, program HS000 contains two function blocks USR_FBK2 and one function block USR_FBK3, and program SS000 contains one function block USR_FBK1.

[0024] Function blocks sometimes contain other function blocks. Figure 1 In the example shown, function block USR_FBK2 contains a function block USR_FBK1. That is, function block USR_FBK2 is in a relationship of using function block USR_FBK1.

[0025] Reference Figure 2 and Figure 3 This section explains the relationship between the program, function blocks, and steps. Figure 2 This is a diagram illustrating an example of the execution content, binary representation, and steps of program MS000. Figure 3 This is a diagram showing an example of the execution content, binary representation, and steps of function block USR_FBK2.

[0026] Figure 2 This represents the graphical display 11, the executed content 12, and the binary display 13 of program MS000. For example... Figure 2 As shown in Figure 11, program MS000 has two function blocks USR_FBK2 (15a, 15b). The execution content of program MS000 shown in Figure 11 is represented by execution content 12. Binary display 13 shows the program MS000 shown in Figure 11 and execution content 12 converted into binary form (downloadable form). In binary display 13, in addition to the binary form of program MS000, step 14 of program MS000 is also shown. The number of steps shown in step 14 corresponds to the number of lines (processing lines) in the binary form of program MS000.

[0027] The execution content of function blocks USR_FBK2 (15a, 15b) shown in Figure 11 corresponds to processes 16a and 16b, respectively. Figure 2 In the code, steps 16a and 16b represent the processing of the call to function block USR_FBK2. Therefore, step 14 of program MS000 does not include steps related to the execution of function block USR_FBK2.

[0028] As shown in binary display 13, program MS000 uses two function blocks USR_FBK2, totaling 22 steps. As shown in processes 16a and 16b, the execution steps of function block USR_FBK2 are four each. However, this only represents the call to function block USR_FBK2, and therefore does not include the total number of execution steps performed by function block USR_FBK2. Therefore, based solely on the number of execution steps in the binary representation of program MS000, the total number of execution steps of program MS000 cannot be determined.

[0029] Figure 3 This represents the graphical display 21, execution content 22, and binary display 23 of function block USR_FBK2. For example... Figure 3 As shown in Figure 21, function block USR_FBK2 has a function block USR_FBK1 (25). The execution content of function block USR_FBK2 shown in Figure 21 is represented by execution content 22. Binary display 23 represents the display of function block USR_FBK2 shown in Figure 21 or execution content 22 in binary form. In binary display 23, in addition to the binary form of function block USR_FBK2, step 24 of function block USR_FBK2 is also shown. The number of steps shown in step 24 corresponds to the number of rows (processing rows) in the binary representation of function block USR_FBK2.

[0030] The function block USR_FBK1 (25) shown in Figure 21 corresponds to process 26. Figure 3 In the code, step 26 indicates the processing of the call to function block USR_FBK1. Therefore, step 24 of function block USR_FBK2 does not include the number of steps involved in the execution of function block USR_FBK1.

[0031] As shown in binary display 23, function block USR_FBK2 is a program that uses a total of 16 steps from function block USR_FBK1. The execution steps of function block USR_FBK1, as shown in process 26, are four steps. However, this only represents a call to function block USR_FBK1, and therefore does not include the total number of execution steps of function block USR_FBK1. Therefore, the total number of execution steps of function block USR_FBK2 cannot be determined from the binary step count of function block USR_FBK2.

[0032] Here, if the number of execution steps of function block USR_FBK1 is set to 12, the number of execution steps when executing program MS000 is calculated in the following way.

[0033] • Number of execution steps for MS000: 22 • Number of execution steps × number of uses for USR_FBK2: 16 × 2 • Number of execution steps × number of uses for USR_FBK1: 12 × 2 22 + 16 × 2 + 12 × 2 = 78 (1) That is, the number of steps is different from the number of execution steps (22 steps) of program MS000. In the development support device of the implementation, the number of execution steps for each task category is obtained by calculating the product of the number of times each function block is used and the number of execution steps in this way.

[0034] (Structure of the implementation method) Next, the structure of the development support device for the implementation method will be described in detail. Figure 4 This is a block diagram illustrating the functional structure of the development support device 100 for implementing the method.

[0035] like Figure 4 As shown, the development support device 100 of this embodiment includes a display unit 105, a display control unit 110, an input unit 115, an output unit 120, and a storage unit 125. Furthermore, the development support device 100 of this embodiment includes an editor 130, a compiler 135, a step counter 140, a count counter 140, and an arithmetic unit 150. The development support device 100 can be implemented, for example, using a computer device. A computer device includes a CPU, main memory, and auxiliary memory, and is implemented through the cooperation of software and hardware. Figure 4 The device with the functional structure shown.

[0036] Display unit 105 is a functional element that displays information to the user. Display unit 105 can be implemented, for example, by a display device, a printer device, etc. Display unit 105 displays display information generated by display control unit 110.

[0037] The display control unit 110 is a functional element that generates the information (display information) to be displayed by the display unit 105. For example, the display control unit 110 stores the template to be displayed by the display unit 105 in the storage unit 125 (described later), and generates display information by appending data to the template.

[0038] The input unit 115 is a functional element for users to input information. The input unit 115 can be implemented, for example, by a keyboard, mouse, etc. The input unit 115 can also be combined with the display unit 105 and implemented by a touch panel, etc.

[0039] The output unit 120 is a functional element that outputs user-created programs or data generated by the development support device 100 in the form of files or the like. For example, if it is a program, the output unit 120 can output it in text form, and if it is data, it can output it in CSV (Comma Separated Values) form, etc. The output unit 120 can also save the data to be output to the storage unit 125.

[0040] Storage unit 125 is a support storage device for development support device 100. Storage unit 125 can store software that implements development support device 100, user-created programs, templates of display information stored by display control unit 110, various tables, etc. Storage unit 125 can be implemented, for example, by hard disk drive (HDD), semiconductor drive (SDD), etc.

[0041] Editor 130 is a functional element that provides editing capabilities for users when creating programs. Editor 130 can take various forms depending on the programming language.

[0042] The compiler 135 is a functional element that converts user-created programs into a form that a computer can execute or interpret. The compiler 135 may be a compiler corresponding to the programming language. In the development support device 100 of the implementation, the compiler 135 converts the programs shown in the graphical displays 11 and 21, and the executable content of the programs shown in the executable content 12 and 22, into binary form shown in the binary displays 13 and 23.

[0043] The step counter 140 is a functional element that counts the number of execution steps of a program or binary execution content.

[0044] The count counter 145 is a functional element that counts the number of times a function block is used.

[0045] The arithmetic unit 150 is a functional element that performs numerical calculations and searches for the destination of the function block.

[0046] (The actions of the implementation method) Next, refer to Figure 5 and Figure 6 The operation of the development support device 100, which provides a detailed description of the implementation method, is explained. Figure 5 This is a flowchart illustrating the operation of the development support device for implementing the method. Figure 6 This is a diagram showing an example of a POU entry displayed in a development support device for an implementation method.

[0047] The display control unit 110 generates a POU entry screen (S200). The display control unit 110 reads the template of the POU entry screen from the storage unit 125. The display control unit 110 appends information such as the number, program name, category, and generation date of each program (POU) stored in the storage unit 125 to the read template.

[0048] The step counter 140 counts the number of execution steps for each POU stored in the storage unit 125 and transmits this count to the display control unit 110. The display control unit 110 appends the received count value to the template of the POU entry screen, thus completing the POU entry screen (S210). In the following description, the information such as the POU's number, program name, category, generation date, and number of execution steps will be referred to as a POU entry.

[0049] The display control unit 110 causes the display unit 105 to display the screen of completed POU entries (S220). Figure 6 This is an example of a POU (Proof of Use) entry screen. For example... Figure 6 As shown, the POU entry screen 30 includes a title 31, module name 32, display order 33, display row 34, value selection 35, file save button 36, etc. These can be selected using a mouse or the like, which serves as an input unit 115, and the selection result is sent to the display control unit 110.

[0050] like Figure 6 As shown, the POU entry screen 30 has an entry list 37. The entry list 37 contains the POU number, program name, category, whether it has been generated, generation date, number of steps, etc., listed for each POU, such as program or function block. Here, the number of steps included in the entry list 37 is the number of execution steps in the program or function block unit.

[0051] When the user selects the file save button 36 on the POU entry screen 30 via a mouse or the like, which serves as the input unit 115 (S230), the count counter 145 counts the number of times each type of function block used in the program is used, according to each task category (S240).

[0052] exist Figure 1 In the program group shown, the function block USR_FBK1 in task category SS is used 1 time, and the function block USR_FBK2 in task category MS is used 2 times. The count counter 145 saves the count result in the storage unit 125.

[0053] The arithmetic unit 150 calculates the product of the number of times a function block is used within the program (counted in S240) and the number of execution steps of that function block (S250). The number of times a function block is used is obtained in S240. The number of execution steps of the function block is obtained in S210. The arithmetic unit 150 calculates their product.

[0054] For example, the function block USR_FBK1 used in program SS000 is used once. Furthermore, the number of execution steps of function block USR_FBK1 is 12. Therefore, the arithmetic unit 150 calculates 1 × 12. The result of the calculation, 12, is the number of execution steps of function block USR_FBK1 used in program SS000.

[0055] The arithmetic unit 150 appends the usage count and execution step count of each task category of the function block to the POU entry (S260). In task category SS, the function block USR_FBK1 is used once, and the execution step count of function block USR_FBK1 is 12. If the execution step count of program SS000 in task category SS is as follows... Figure 6 If the number is 16, then the total number of execution steps of program SS000 is the sum of 16 and 12, which is 28.

[0056] The output unit 120 saves the POU entries with the number of times they are used and the number of execution steps as a CSV file in the storage unit 125 (S270).

[0057] If the file save button 36 is not selected and the output unit 120 has output a file (S230 No, S270), the input unit 115 waits for input from the user (S280). If the input unit 115 does not receive a screen end instruction from the user (S280 No), the input unit 115 waits for the file save button to be selected (S230). When the input unit 115 receives a screen end instruction from the user (S280 Yes), the process ends.

[0058] Furthermore, in the examples described above, the count of the number of times the function block is used or the product of the number of steps is calculated after the POU entry screen is displayed, but this is not a limitation. The count of the number of uses and the calculation of the product can also be performed without displaying the POU entry screen.

[0059] (Counting action of function block) Then, referring to Figures 7-12 The method for counting the number of times a function block is used in the development support device of the implementation method is described in detail. Figure 7 This is a flowchart illustrating the actions of function block processing in the development support device for implementing the method. Figure 8 This is a diagram of an example of a table that represents the count of the number of times a function block in the development support device for an implementation method is used. Figure 9 This is a diagram of an example of a table that represents the count of the number of times a function block of each task category in the development support device for the implementation method is used. Figure 10This is a diagram of an example of a table showing the product of the number of times a recording function block is used and the number of execution steps in a development support device for an implementation method. Figure 11 This is a diagram illustrating an example of a table in a development support device for an implementation that records the number of times a function block for each task category is used and the total number of steps. Figure 12 This is a diagram illustrating an example of the output of a development support device for an implementation method.

[0060] The arithmetic unit 150 first searches for the destination of use of function block USR_FBK1 (S300). The arithmetic unit 150 refers to the program or binary stored in the storage unit 125 to search for the destination of use of function block USR_FBK1 (the program that uses function block USR_FBK1, etc.). For example... Figure 1 As shown, function block USR_FBK1 is used by program SS000 and function block USR_FBK2. Therefore, it can be concluded that function block USR_FBK1 is a function block used in task SS.

[0061] The arithmetic unit 150 determines whether the destination of the function block USR_FBK1 is a function block (S310). Figure 1 In the example shown, function block USR_FBK1 is used in function block USR_FBK2 (S310 is).

[0062] The counter 145 counts the number of times function block USR_FBK2 is used. The arithmetic unit 150 saves a table containing the name of the function block and the number of times it is used to the destination function block into the storage unit 125 (S320). Figure 1 As shown, the destination function block for using function block USR_FBK1 is function block USR_FBK2. Furthermore, function block USR_FBK2 is used twice in program MS000 and twice in program HS000. The arithmetic unit 150 records in the storage unit 125 that function block USR_FBK2 was used a total of four times. Figure 8 This represents an example of the contents stored in the storage unit 125 by the arithmetic unit 150.

[0063] Next, the arithmetic unit 150 retrieves the destination of use for function block USR_FBK2 (S330). Figure 1 In the example shown, the function block USR_FBK2 is used by programs MS000 and HS000.

[0064] The arithmetic unit 150 determines whether the destination of the retrieved function block USR_FBK2 is a function block (S340). If the determination result is a function block (yes in S340), the count counter 145 counts the number of times the function block is used, and the arithmetic unit 150 maintains the name and number of times the function block is used (S320) and further searches for its destination (S330). Furthermore, if a function block exists as the destination of the function block, this process is repeated.

[0065] If the result of the determination is that it is not a function block (No in S340), the count counter 145 counts the number of times each function block is used according to each task category (S350). Figure 1 In the example shown, the function block USR_FBK1 is used once for task category SS. Furthermore, the function block USR_FBK2 is used twice for task category MS.

[0066] At this stage, we can determine the destination function block (USR_FBK2) of function block USR_FBK1 and the number of times function block USR_FBK2 is used. That is, we obtain the following information.

[0067] The function block USR_FBK1 is used in task SS (S300). The function block USR_FBK2 is used four times (S320). The function block USR_FBK2 is used twice each in tasks MS and HS (S350). The arithmetic unit 150 records this information in the storage unit 125.

[0068] Figure 9 This represents an example of the contents stored in storage unit 125 by arithmetic unit 150. Specifically, task SS uses function block USR_FBK1 once. Task HS uses function block USR_FBK2 twice. Task MS uses function block USR_FBK2 twice.

[0069] Next, the computation unit 150 calculates the product of the number of times the function block USR_FBK1 is used in the function block USR_FBK2 used in the destination and the number of times FBK2 is used for each task category (S360). Figure 1In the example shown, function block USR_FBK2 is not used in task SS, but function block USR_FBK1 is used only once. In task HS, function block USR_FBK2 is used twice, and function block USR_FBK1 is used once within function block USR_FBK2, so their product is 2. Similarly, in task MS, function block USR_FBK2 is used twice, and function block USR_FBK1 is used once within function block USR_FBK2, so their product is 2. The arithmetic unit 150 stores this result in the storage unit 125.

[0070] Figure 10 This represents an example of the contents stored in storage unit 125 by arithmetic unit 150. Specifically, the product is 1 in task SS, 2 in task HS, and 2 in task MS. These represent the number of times function block USR_FBK1 is used for each task category.

[0071] The arithmetic unit 150 calculates the product of the number of times the function block is used and the number of execution steps of the function block for each task category (S370). The function block USR_FBK1 has 12 execution steps and is used once in task SS, therefore its product is 12. Similarly, the function block is used twice in task HS, therefore its product is 24. The function block is also used twice in task MS, therefore its product is 24. The arithmetic unit 150 saves the calculation result to the storage unit 125. The output unit 120 provides the saved content to the user. Figure 11 This represents an example of the contents stored in the storage unit 125 by the arithmetic unit 150.

[0072] The arithmetic unit 150 performs processing steps S300 to S370 on all function blocks and saves the output information, which has been listed, in the storage unit 125. Figure 12 This represents an example of the contents stored in the storage unit 125 by the arithmetic unit 150.

[0073] Figure 12 The illustrated output information 40 includes a list of entries containing POU number, program name, category, whether generation is complete, generation date, number of steps, etc. 41; the number of uses in task category SS; the number of uses in task category HS; the number of uses in task category MS; the total number of steps in task category SS; the total number of steps in task category HS; and the total number of steps in task category MS. Among these, the total number of steps in task category SS 45, the total number of steps in task category HS 46, and the total number of steps in task category MS 47 represent the total number of execution steps in each task.

[0074] For example, the usage count of 42 in task category SS represents the number of times POU is used in task category SS. That is, in task category SS, it means that program SS000 is used once and function block USR_FBK1 is used once. Furthermore, the total number of steps of 45 in task category SS represents the number of execution steps performed in task category SS. That is, program SS000 has 16 execution steps, and function block USR_FBK1 has 12 execution steps. Their sum represents task category SS, in other words, the total number of execution steps when program SS000 is executed.

[0075] Similarly, the usage count of 44 in task category MS represents the number of times POU is used in task category MS. That is, it indicates the following: in task category MS, program MS000 is used once, function block USR_FBK2 is used twice, and function block USR_FBK1 is used twice. Furthermore, the total number of steps of 47 in task category MS represents the number of execution steps performed in task category MS. That is, program MS000 has 22 execution steps, function block USR_FBK2 has 32 (16×2) execution steps, and function block USR_FBK1 has 24 (12×2) execution steps. Their sum represents the total number of execution steps in task category MS, in other words, when program MS000 is executed.

[0076] The arithmetic unit 150 calculates the total number of execution steps when executing each task category, and the output information 40 may also include this total number of execution steps.

[0077] Thus, according to the development support device of the implementation method, for each task category, the number of times the original function block is used is calculated by using the number of times the destination function block is used. Therefore, even when a function block is used, the number of execution steps can be accurately calculated. That is, the number of execution steps of the program that takes into account the number of execution steps of the function block can be obtained.

[0078] Several embodiments of the present invention have been described, but these embodiments are given by way of example and are not intended to limit the scope of the invention. These embodiments can be implemented in various other ways, and various omissions, substitutions, and modifications can be made without departing from the spirit of the invention. These embodiments and their variations are included in the scope and spirit of the invention, as well as in the scope of the invention as set forth in the claims and its equivalents.

[0079] Explanation of reference numerals in the attached figures 11, 21… Graphical display 12, 22… Execution content 13, 23… binary display Steps 14, 24... Function blocks 15a, 15b... USR_FBK2 Processing 16a, 16b, 26… 25… Function block USR_FBK1 30…POU entry screen 31…Title 32…Module Name 33… Display order 34… Display line 35… value selection 36, 41… File save button 37… List of Entries 40… Output Information 42… Number of uses in Quest SS 43… Number of uses in Task HS 44… Number of uses in Mission MS 45… Total number of steps in Task SS 46… Total number of steps in task HS 47… Total number of steps in Task MS 100…Development Support Device 105… Display Department 110… Display Control Department 115… Input Section 120… Output Department 125… Storage Department 130…Editor 135… Compiler 140…Connecting part 145…Step counter 150…Arithmetic unit.

Claims

1. A development support apparatus for supporting the development of programs comprising function blocks, the development support apparatus comprising: A step counter that counts the number of execution steps of the function block, representing the number of processes performed in the function block; A counter that counts the number of times the function block is used in the program; and The arithmetic unit calculates the product of the number of times the function block is used and the number of execution steps of the function block, and outputs the number of execution steps of the function block in the program.

2. The development support device according to claim 1, characterized in that, The step counter also counts the number of execution steps of the program, which represents the number of processes performed in the program. The arithmetic unit calculates the sum of the number of execution steps of the program and the number of execution steps of the functional blocks in the program, and outputs the total number of execution steps when the program is executed.

3. The development support device according to claim 1, characterized in that, The program is categorized according to each task type. The count counter counts the number of times the function block used in the program is used for each task category. The computation unit calculates the product of the number of times the function block is used for each task category and the number of execution steps of the function block, and outputs the number of execution steps of the function block in the program for each task category.

4. The development support device according to claim 1, characterized in that, The functional block has a first functional block and a second functional block that uses the first functional block. The count counter counts the first number of times the first function block is used in the second function block and the second number of times the second function program is used in the program. The arithmetic unit calculates the product of the first usage count and the second usage count, and outputs the number of execution steps of the first functional block used in the program.

5. The development support device according to claim 4, characterized in that, The program is categorized according to each task type. The count counter counts the first number of times the first function block is used in the second function block and the second number of times the second function program is used according to each task category. The arithmetic unit calculates the product of the first usage count and the second usage count, and outputs the number of execution steps of the first functional block used for each task category.

Images