JP7032596B1 - Machine tool control device and machine tool control method - Google Patents

Abstract

PROBLEM TO BE SOLVED: To efficiently generate an MDI program. SOLUTION: A tool management screen for displaying a list of tools prepared in a machine tool is generated, a tool management unit to be displayed, and a standard program are called, and the tool information of the tool selected on the tool management screen is converted into a standard program. In addition, a machine tool control device including an MDI program generator that generates an MDI (Manual Data Input) program. [Selection diagram] Fig. 1

Description

The present invention relates to a machine tool control device and a machine tool control method.

In the above technical field, Patent Document 1 discloses a technique of displaying a tool selection button figure on a display screen of an operation panel and controlling tool attachment to a tool spindle by button operation in MDI mode operation.

Japanese Unexamined Patent Publication No. 2002-166335

However, the techniques described in the above document could not efficiently generate an MDI program.

An object of the present invention is to provide a technique for solving the above-mentioned problems.

In order to achieve the above object, the machine tool control device according to the present invention is
A tool management unit that creates and displays a tool management screen that displays a list of tools prepared for machine tools, and
An MDI program generator that calls a standard program, adds the tool information of the tool selected on the tool management screen to the standard program, and generates an MDI (Manual Data Input) program.
Equipped with
When two or more tools are selected on the tool management screen, the MDI program generator adds the tool information of the selected tool to each of the number of standard programs corresponding to the number of selected tools. The MDI program is generated by continuously arranging the MDI programs .

In order to achieve the above object, the machine tool control device according to the present invention is
A tool management unit that creates and displays a tool management screen that displays a list of tools prepared for machine tools, and
An MDI program generator that calls a standard program, adds the tool information of the tool selected on the tool management screen to the standard program, and generates an MDI (Manual Data Input) program.
Equipped with
The MDI program generation unit generates the MDI program by arranging an optional stop command between the stylized programs arranged continuously .

In order to achieve the above object, the machine tool control device according to the present invention is
The tool management unit that generates and displays the tool offset screen that displays the offset value of the tool prepared in the machine tool,
An MDI program generator that calls a standard program, adds the offset value of the tool selected on the tool offset screen to the standard program, and generates an MDI (Manual Data Input) program.
Equipped with.

According to the present invention, an MDI program can be efficiently generated.

It is a block diagram which shows the structure of the machine tool control device which concerns on 1st Embodiment. It is a figure which shows the display operation part of the machine tool control device which concerns on 2nd Embodiment. It is a figure which shows the transition of the display operation part of the machine tool control device which concerns on 2nd Embodiment. It is a figure which shows the structure of the machine tool including the machine tool control device which concerns on 2nd Embodiment. It is a figure explaining the functional structure of the machine tool including the machine tool control device which concerns on 2nd Embodiment. It is a figure which shows the operation outline of the machine tool control apparatus which concerns on 2nd Embodiment. It is a block diagram which shows the structure of the tool management module of the machine tool control device which concerns on 2nd Embodiment. It is a figure which shows the structure of the tool information table and the generation definition table which concerns on 2nd Embodiment. It is a block diagram which shows the structure of the MDI transfer module of the machine tool control device which concerns on 2nd Embodiment. It is a figure which shows the structure of the program generation definition storage part and the snippet storage part which concerns on 2nd Embodiment. It is a flowchart which shows the processing procedure of the MDI transfer module of the machine tool control device which concerns on 2nd Embodiment. It is a flowchart which shows the procedure of the program generation process which concerns on 2nd Embodiment. It is a flowchart which shows the procedure of the parameter partial search process which concerns on 2nd Embodiment. It is a flowchart which shows the procedure of the manual input processing which concerns on 2nd Embodiment. It is a figure which shows an example of the format of the parameter part which concerns on 2nd Embodiment. It is a figure which shows the table of the example of the MDI program which used the format of the parameter part which concerns on 2nd Embodiment. It is a figure which shows the example 921 of the MDI program in the machining center which concerns on 2nd Embodiment. It is a figure which shows the example 922 of the MDI program in the machining center which concerns on 2nd Embodiment. It is a figure which shows the example 923 of the MDI program in the machining center which concerns on 2nd Embodiment. It is a figure which shows the example 924 of the MDI program in the machining center which concerns on 2nd Embodiment. It is a figure which shows the example 925 of the MDI program in the machining center which concerns on 2nd Embodiment. It is a figure which shows the example 926 of the MDI program in the machining center which concerns on 2nd Embodiment. It is a figure which shows the example 927 of the MDI program in the machining center which concerns on 2nd Embodiment. It is a figure which shows the example 928 of the MDI program in the machining center which concerns on 2nd Embodiment. It is a figure which shows the display of the example 931 of the MDI program in the turning center which concerns on 2nd Embodiment. It is a figure which shows the example 932 of the MDI program in the turning center which concerns on 2nd Embodiment. It is a figure which shows the example of the tool management screen in the turning center which concerns on 2nd Embodiment. It is a figure which shows the display of the example 941 of the MDI program in the tool offset which concerns on 2nd Embodiment. It is a figure which shows the example 942 of the MDI program in the tool offset which concerns on 2nd Embodiment. It is a figure which shows the display operation part of the machine tool control device which concerns on 3rd Embodiment. It is a figure which shows the example of the tool management screen of the machine tool control device which concerns on 3rd Embodiment. It is a figure which shows the snippet generation screen of the machine tool control device which concerns on 3rd Embodiment. It is a figure which shows the snippet edit screen of the machine tool control device which concerns on 3rd Embodiment. It is a block diagram which shows the structure of the MDI transfer module of the machine tool control device which concerns on 3rd Embodiment. It is a figure which shows the structure of the data storage part for snippet editing which concerns on 3rd Embodiment. It is a flowchart which shows the procedure of the generation editing process of the snippet of the machine tool control device which concerns on 3rd Embodiment. It is a flowchart which shows the procedure of the description insertion process of the parameter part which concerns on 3rd Embodiment. It is a figure which shows the generation edit procedure of the program definition of the machine tool control device which concerns on 4th Embodiment. It is a block diagram which shows the structure of the MDI transfer module of the machine tool control device which concerns on 4th Embodiment. It is a flowchart which shows the procedure of the program definition generation edit processing of the machine tool control apparatus which concerns on 4th Embodiment. It is a flowchart which shows the procedure of the snippet change processing which concerns on 4th Embodiment.

Hereinafter, embodiments of the present invention will be described in detail exemplary with reference to the drawings. However, the components described in the following embodiments are merely examples, and the technical scope of the present invention is not intended to be limited thereto. The wording "snippet" used in this embodiment is a short reusable program and is used for creating and editing a program. For example, in the NC program, it refers to a short program. The "snippet" corresponds to the "standard program" in the claims.

[First Embodiment]
The machine tool control device 100 as the first embodiment of the present invention will be described with reference to FIG. The machine tool control device 100 is a device that controls a machine tool.

As shown in FIG. 1, the machine tool control device 100 includes a tool management unit 101 and an MDI (Manual Data Input) program generation unit 102. The tool management unit 101 generates and displays a tool management screen 111 that displays a list of tools prepared for the machine tool. The MDI program generation unit 102 calls the standard program 121, adds the tool information 112 of the tool selected on the tool management screen 111 to the standard program 121, and generates the MDI program 122.

According to this embodiment, an MDI program can be efficiently generated.

[Second Embodiment]
Next, the machine tool control device 200 according to the second embodiment of the present invention will be described. The machine tool control device 200 gives the tool information of a single tool / pot / ST (station) specified by the operator to the snippet as a parameter and transfers it to the MDI function.

The machine tool controller 200 generates an MDI program containing at least one snippet according to the program generation definition. Here, the program generation definition is a logic that generates a program by using a part that does not depend on the snippet and a part that is based on the snippet.

The snippet may include a parameter part for inputting tool information as a parameter, and by describing a variable in a specific format in the parameter part, what information is received is specified. The parameter part can be classified into an automatic input parameter part in which parameters are automatically input and a manual input parameter part in which a user is manually input. If a snippet containing the manual input parameter part is specified in the program generation definition, the parameter manual input screen is displayed when the MDI transfer button is touched, and the value is reflected by the operator inputting the parameter. An MDI program is generated. When multiple tool / pot / ST information is specified on the tool management screen, multiple snippets are combined based on each information. At that time, an arbitrary command such as an optional stop can be inserted between the snippets according to the program generation definition.

Here, three simple snippet examples will be described.
The first snippet example is
T? TOOL: Q1 ?;
G30X0.Y0.Z0 .;
M6;
This is an example of automatic input described in.
Here, the first line represents the tool of Q1 to the ATC position, the second line represents the origin return, and the third line represents ATC, and as a whole, an example of replacement at the replacement position of the selected tool. Is. Here, TOOL is a description that is replaced with the tool number indicated by the following parameter identifier Q1.

The second snippet example is
G324H # 149B300.M0X? TOOL: Q1102 ?;
This is an example of automatic input of diameter correction shape correction value in automatic tool length measurement (G324) described in.
Here, Q1102 is a parameter identifier indicating the diameter correction shape correction value.

The third snippet example is
G324H # 149B300.M0X? MANUAL INPUT: G324X = TOOL: Q1102 ?;
This is an example of manual input of the diameter correction shape correction value in the automatic tool length measurement (G324) described in.

<Operation procedure of machine tool control device>
Hereinafter, the display operation unit of the machine tool control device 200 incorporated in the machine tool 250 will be described with reference to FIGS. 2A to 2D.

FIG. 2A is a diagram for explaining an operation procedure in the display operation unit 201 of the machine tool control device 200 included in the machine tool 250. When the MDI mode for generating and executing an MDI program is set using a switch (not shown), the tool management screen 210 and the MDI screen 220 are displayed on the display operation unit 201 as shown in FIG. 2A. .. When the user selects the tool 211 on the tool management screen 210 and then touches any of the buttons 216 and 217, the generation definition of the MDI program corresponding to each button is read out. Then, the snippet specified in the read generation definition is read. The read snippet contains a parameter portion 225 described in a particular format, to which the tool information of the tool 211 (here, tool number 10002 as an example) is added to the parameter portion 225 to create an MDI program. Generated. The generated MDI program is displayed on the MDI screen 220. Here, what is the tool information as long as it is information related to the tool such as tool identification information (tool number), tool length shape, tool length wear, tool diameter shape, tool diameter wear, or parameters such as correction value. It is a concept that can include various information.

The MDI transfer buttons 216 and 217 are displayed on the tool management screen 210. The processing when each button is touched will be described with reference to FIG. 2B.

When the MDI transfer (call) button 216 is touched, the display operation unit 201 calls the program generation definition associated with the button 216 and displays the MDI program generated by combining the snippets specified by the program generation definition on the MDI screen. 226 is displayed. At this time, the parameter portion of the snippet is replaced with specific tool information (tool number, parameter, etc.) of the tool 213 selected on the tool management screen 210. Further, an optional stop (M function = M01) 228 is automatically inserted between the plurality of snippets.

On the other hand, when the MDI transfer (measurement) button 217 is touched, the display operation unit 201 calls the program generation definition associated with the MDI transfer (measurement) button 217. In the program generation definition associated with the MDI transfer (measurement) button 217, a snippet "G324H # 149B300.M0X? MANUALINPUT ...?" 229 including a G code (here, G324) accompanied by measurement is specified. Since this snippet 229 requires manual input of variables, the manual input screen 230 is displayed at the same time as the touch of the MDI transfer (measurement) button 217. The user can manually input the parameters of the snippet 229 by touching the MDI transfer button 233 after inputting a numerical value in the manual input field 232 with reference to the preview 231 of the MDI program.

<Machine tool configuration and operation>
As shown in FIG. 3A, the machine tool 250 includes a machine tool control device 200 and a machining center 302 controlled by the machine tool control device 200. The machining center 302 in FIG. 3A is an example of a vertical machining center, but there are other types such as a horizontal type and a portal type. In the vertical form, the X-axis, the Y-axis, and the Z-axis are defined as shown in FIG. 3A.

The machine tool control device 200 has a display operation unit 201, an input key group 303, and a control key group 304. The machine tool control device 200 has a tool management module that manages the tools used. Further, the machine tool control device 200 has an MDI (Manual Data Input) mode and has an MDI function module that operates by an MDI program. The mode selection key of the control key group 304 includes the MDI mode key 305.

In the MDI mode, a functional instruction as shown in FIG. 3B is defined, and the MDI program is described by the functional instruction. The classification of functional instructions and basic functional instructions are shared, but some optional dedicated functional instructions are also used.

(Overview of functional configuration)
As shown in FIG. 3C, the machine tool control device 200 includes a tool management module 310, an MDI transfer module 320, and an MDI function module 330. The tool management module 310 has a tool management unit 311 and a tool information storage unit 312. Further, the tool management module 310 manages the tool management screen 210. The MDI transfer module 320 has an MDI program generation unit 321, a program generation definition storage unit 322, a snippet storage unit 323, and a parameter manual input unit 324. Further, the MDI transfer module 320 manages the parameter manual input screen 230 in the case of parameter manual input. The MDI function module 330 has an NC MDI function unit 331. Further, the MDI function module 330 manages the MDI screen 220.

The tool management unit 311 of the tool management module 310 refers to the tool information stored in the tool information storage unit 312, displays the tool information on the tool management screen 210, and displays the tool information input to the tool management screen 210. It is stored in the tool information storage unit 312. Further, the tool management unit 311 sends the identifier of one or more tools selected on the tool management screen 210 and the identifier of the selected program generation definition to the MDI transfer module 320 ((# 1) in FIG. 3C. )reference).

The tool management unit 311 waits for a request from the MDI program generation unit 321 for tool information that replaces the parameter portion described in the snippet. The tool management unit 311 includes an identifier of a tool indicating tool information for replacing a parameter portion and an identifier of specific tool information (for example, Q0). Upon receiving the information transmission request (see (# 3) in FIG. 3C), the tool management unit 311 receives specific tool information (eg, all tool information) among all tool information (all tool information) for each selected tool. If it is Q0, the tool number) is extracted. The tool management unit 311 passes the extracted specific tool information to the MDI program generation unit 321 (see (# 4) in FIG. 3C), so that the MDI program generation unit 321 extracts a predetermined parameter part of the snippet. Generate an MDI program by replacing it with specific tool information. The exchange of specific tool information between (# 3) and (# 4) in FIG. 3C is repeated as many times as (the number of selected tools × the number of parameter parts of automatic input). Here, it was decided to extract specific tool information in the tool management module 310, but the MDI program generation unit 321 accesses the tool information storage unit 312 and is required to replace the parameter part. Tool information may be extracted.

The MDI program generation unit 321 of the MDI transfer module 320 reads the program generation definition corresponding to the button pressed from the program generation definition storage unit 322 by using the program generation definition identifier received from the tool management unit 311 (FIG. 3C). See (# 2) inside). Next, the MDI program generation unit 321 searches for the snippet identifier described in the read program generation definition. Then, the snippet is read from the snippet storage unit 323 using the snippet identifier (see (# 2) in FIG. 3C). When the MDI program generation unit 321 finds a parameter part of a specific format in the read snippet, it analyzes the specific format and specifies the attribute of the parameter part. If the MDI program generation unit 321 confirms that the specified parameter part is the automatic input of the tool information of the selected tool, the MDI program generation unit 321 requests the tool management unit 311 for the specific tool information that replaces the parameter part described in the snippet. do. That is, a request for sending information including an identifier of the tool and an identifier of specific tool information (for example, Q0) is transmitted to the tool management unit 311 (see (# 3) in FIG. 3C). The MDI program generation unit 321 receives from the tool management unit 311 specific tool information (for example, a tool number in the case of Q0) among all tool information related to each selected tool ((# in FIG. 3C). 4)), this parameter part is replaced with the specific tool information received by the selected tool. The exchange of specific tool information between (# 3) and (# 4) in FIG. 3C is repeated as many times as (the number of selected tools × the number of parameter parts of automatic input). Further, the MDI program generation unit 321 may access the tool information storage unit 312 to extract specific tool information necessary for replacing the parameter portion. On the other hand, if the specified parameter portion is confirmed as the manual input of the tool information of the selected tool, the MDI program generation unit 321 replaces this parameter portion with the tool information input by the user from the parameter manual input screen 230. By executing this MDI program generation procedure according to the program generation definition, an MDI program is generated in which the parameter portion in the program is replaced with specific tool information (parameters are fixed).

The generated MDI program is sent from the MDI program generation unit 321 to the NC MDI function unit 331 of the MDI function module 330, and the MDI program is executed. Further, the generated MDI program and its execution state are displayed on the MDI screen 220. Although the MDI screen 220 is displayed here when the MDI program is generated, the present invention is not limited to this. In order to set the generated program to the MDI function of NC, the MDI screen 220 may be displayed in that state. Further, the MDI function may be used internally without displaying the MDI screen 220.

<Structure of tool management module>
In FIG. 4A, the tool management module 310 includes a module interface 401, an input / output interface 402, a tool information acquisition / storage unit 403, a display control unit 404, and an operation control unit 405. Further, the tool management module 310 includes a tool information acquisition unit 406, a tool identifier transmission unit 407, a generation definition identifier acquisition unit 408, a generation definition identifier transmission unit 409, a parameter automatic input unit 411 for tool information, and a database. It is equipped with 410. In FIG. 4A, (# 1), (# 3), and (# 4) indicate the same processing as that in FIG. 3C.

The module interface 401 is an interface that controls data exchange between the tool management module 310 and the MDI transfer module 320. The input / output interface 402 is an interface that controls data exchange between the tool management module 310 and internal and external peripheral devices. In the present embodiment, the database 410 as a storage unit is connected as an internal peripheral device, and the display operation unit 201 is connected as an external peripheral device, but the present invention is not limited to this.

The tool information acquisition / storage unit 403 acquires the tool information input from the display operation unit 201 and stores it in the tool information storage unit 312 of the database 410. The display control unit 404 controls the display of tool information on the display operation unit 201. The operation control unit 405 controls the input operation of the user from the display operation unit 201. For example, the operation control unit 405 acquires the identifier of the tool selected by the user from the tool displayed on the display operation unit 201, and generates a program corresponding to the case where the user presses the button displayed on the display operation unit 201. Control to get the definition identifier.

The tool identifier transmission unit 407 transmits the tool identifier acquired by the operation control unit 405 to the MDI transfer module 320 (see (# 1) in FIG. 4A). The generation definition identifier acquisition unit 408 has a generation definition identifier table 481, and uses the generation definition identifier table 481 to acquire the identifier of the program generation definition instructed by the user from the display operation unit 201 based on the control of the operation control unit 405. do. The identifier of the program generation definition is input by pressing the software button additionally displayed on the tool management screen 210 according to the present embodiment. The generation definition identifier transmission unit 409 transmits the program generation definition identifier acquired by the generation definition identifier acquisition unit 408 to the MDI transfer module 320. Further, if the snippet can be directly selected from the display operation unit 201, the snippet identifier 491 may be included.

The parameter automatic input unit 411 for tool information has a parameter table 412 for tool information. The parameter automatic input unit 411 for tool information receives a tool identifier and a specific tool information identifier for selecting specific tool information to be added to the snippet parameter part from the MDI transfer module 320 (FIG. 4A). See (# 3). Then, the parameter automatic input unit 411 for tool information passes the tool identifier to the tool information acquisition unit 406, and instructs the tool information storage unit 312 to acquire all the tool information corresponding to the tool identifier. The tool information acquisition unit 406 has a tool information table 461, and using the tool information table 461, all tools of the tool instructed by the user from the display operation unit 201 based on the request from the parameter automatic input unit 411 for tool information. Get information.

The parameter automatic input unit 411 for tool information uses the parameter table 412 of tool information to specify a specific tool information identifier corresponding to a specific tool information identifier from all tool information corresponding to the tool identifier acquired by the tool information acquisition unit 406. The tool information is extracted and returned to the MDI transfer module 320 (see (# 4) in FIG. 4A).

(Tool information table)
The tool information table 461 of FIG. 4B is used to acquire all tool information corresponding to the tool identifier requested from the parameter automatic input unit 411 for tool information from the tool information storage unit 312. The tool information table 461 is stored as all tool information 422 acquired from the tool information storage unit 312 in association with the tool identifier 421 requested by the parameter automatic input unit 411 for tool information. Then, the tool identifier 423 is stored in association with each of the instruction screen positions 432.

(Parameter table of tool information)
The parameter table 412 of the tool information of FIG. 4B is used to extract the specific information (parameter) of the tool to be added to the parameter part of the snippet requested by the parameter automatic input unit 411 for the tool information from the MDI transfer module 320. Will be done. The parameter table 412 of the tool information stores the specific tool information 443 extracted from the corresponding tool information in association with the identifier 441 of the tool requested from the MDI transfer module 320 and the identifier 442 of the specific tool information.

(Generation definition identifier table)
The generation definition identifier table 481 of FIG. 4B is used by the generation definition identifier acquisition unit 408 to acquire the identifier of the program generation periodicity corresponding to the button selected by the user displayed on the tool management screen 210. The generation definition identifier table 481 stores the position where at least one button is displayed as the instruction screen position 432 in association with the display screen identifier 431 of the tool management screen 210 indicating the type of the tool. Then, the button type 433 is stored in association with each of the instruction screen positions 432, and when a plurality of menus are included in one button (for example, a pull-down menu), the menu position 434 and the generation definition identifier 435 are stored.

<MDI transfer module configuration>
In FIG. 5A, the MDI transfer module 320 includes a module interface 501, an input / output interface 502, a tool identifier acquisition unit 503, a program generation definition identifier acquisition unit 505, and a program generation definition acquisition unit 506. Further, the MDI transfer module 320 includes a snippet acquisition unit 507, an MDI program generation unit 321, a parameter manual input unit 324, and a database 510. In FIG. 5A, (# 1), (# 3), and (# 4) indicate the same processing as that in FIGS. 3C and 4A.

The module interface 501 is an interface that controls data exchange between the MDI transfer module 320, the tool management module 310, and the MDI function module 330. The input / output interface 502 is an interface that controls data exchange between the MDI transfer module 320 and internal and external peripheral devices. In the present embodiment, the database 510, which is a storage unit, is connected as an internal peripheral device, and the display operation unit 201 is connected as an external peripheral device, but the present invention is not limited to this.

The tool identifier acquisition unit 503 acquires the identifiers of one or more tools sent from the tool management module 310 (see (# 1) in FIG. 5A) and sends them to the MDI program generation unit 321. The program generation definition identifier acquisition unit 505 acquires the program generation definition identifier sent from the tool management module 310 in response to the button (see (# 1) in FIG. 5A). The program generation definition acquisition unit 506 acquires the program generation definition from the program generation definition storage unit 322 of the database 510 by using the program generation definition identifier.

The snippet acquisition unit 507 acquires snippets from the snippet storage unit 323 of the database 510 using the snippet identifier specified in the program generation definition. Based on the program generation definition, the MDI program generation unit 321 generates an MDI program in which a snippet in which the parameter portion is replaced with a tool identifier or other tool information is arranged, and sends the MDI program to the MDI function module 330. Based on the program generation definition, the MDI program generation unit 321 automatically replaces the parameter part with a tool identifier or other tool information if the format of the parameter part of the acquired snippet indicates automatic input. On the other hand, if the format of the parameter portion of the acquired snippet indicates manual input, the parameter manual input unit 324 displays the manual input field on the display operation unit 201 and acquires the manual input data. Then, the parameter manual input unit 324 replaces the parameter part with the tool information manually input by the user.

The processing when the above parameter part is automatically replaced by the tool identifier or other tool information is as follows. When the format of the parameter part of the snippet indicates automatic input, the MDI program generation unit 321 sends a request for tool information to the tool management module 310 to request specific tool information (see (# 3) in FIG. 5A). ). The tool information request includes a tool identifier that replaces a parameter portion of one or more tool identifiers acquired by the tool identifier acquisition unit 503 from the tool management module 310, and a specific tool information identifier. Then, when the MDI program generation unit 321 receives the specific tool information corresponding to the identifier of the tool requested from the tool management module 310 and the identifier of the specific tool information, the parameter portion is replaced with the received specific tool information.

(Program generation definition storage unit and snippet storage unit)
As shown in FIG. 5B, the program generation definition storage unit 322 of FIG. 3C stores the program generation definition 532 in association with the generation definition identifier 531. At least one snippet identifier and a placement location (snippet position) of the snippet in the MDI program are associated with the program generation definition 532 (533). The program generation definition 532 is also associated with a program other than the snippet and its placement location 534.

As shown in FIG. 5B, the snippet storage unit 323 of FIG. 3C stores the snippet and provides the snippet associated with the snippet identifier included in the program generation definition to the MDI transfer module 320. That is, each line of the snippet storage unit 323 identifies the snippet, and stores the standard portion 542, the automatic input parameter portion 543, and the manual input parameter portion 544 in association with the snippet identifier 541.

<Processing procedure of MDI transfer module>
FIG. 6 is a flowchart showing a processing procedure of the MDI transfer module 320. The processing shown in this flowchart is executed by using a CPU (Central Processing Unit) and a RAM (Random Access Memory) (not shown) included in the machine tool control device 200, and realizes each functional configuration of the MDI transfer module 320. ..

The MDI transfer module 320 determines in step S601 whether or not it is in the MDI mode. If it is not in MDI mode, another process is executed. In the MDI mode, the MDI transfer module 320 waits for the user to select a tool using the tool management screen 210 in step S607. If there is a tool selection, the MDI transfer module 320 waits for the user to touch the MDI transfer buttons 216 and 217 on the tool management screen 210 in step S609. If the MDI transfer buttons 216 and 217 are touched, the process proceeds to step S611, and the MDI program generation unit 321 acquires the program generation definition corresponding to the touched MDI transfer button from the program generation definition storage unit 322. Then, the process proceeds to step S613, and the MDI program generation unit 321 acquires the tool information extracted for the selected tool. Further, the process proceeds to step S615, and the MDI program generation process according to the acquired program generation definition is executed. The MDI transfer module 320 outputs the generated MDI program to the MDI function module 330 in step S617.

(MDI program generation process)
FIG. 7 is a flowchart showing in detail the flow of the process in the MDI program generation process S615 of FIG. In step S701, the MDI program generation unit 321 reads the snippet specified in the program generation definition from the snippet storage unit 323. Next, the MDI program generation unit 321 executes the parameter partial search process in the read snippet in step S703. Then, the MDI program generation unit 321 determines in step S705 whether the format of the found parameter portion is automatic input or manual input. If it is an automatic input parameter portion, the MDI program generation unit 321 inputs specific tool information selected from the tool information acquired in step S613 to the parameter portion in step S707. On the other hand, if it is a manual input, the MDI program generation unit 321 executes the manual input process in step S709. When the parameter input to one parameter part in the snippet is completed, the MDI program generation unit 321 determines in step S711 whether or not the parameter part search in the snippet is completed. If the parameter partial search is not completed, the MDI program generation unit 321 returns to step S703 and repeats the replacement process of the remaining parameter portion in the snippet.

When the parameter partial search for one snippet is completed, the MDI program generation unit 321 arranges the snippet in which all the parameter parts are replaced in the MDI program in step S713 according to the program generation definition. Next, the MDI program generation unit 321 determines in step S715 whether or not there is the next snippet specified in the program generation definition. If a snippet is further specified, the MDI program generation unit 321 returns to step S701, reads the next snippet specified in the program generation definition, and starts searching for the parameter portion.

On the other hand, if there are no other snippets, the MDI program generator 321 determines in step S717 whether the selected tool still remains. If the selected tool still remains, the MDI program generator 321 inserts an optional stop (M function = M01) after the snippet in step S719 and returns to step S701. If there is no other selected tool, the MDI program generation process ends.

(Parameter partial search process)
FIG. 8A is a flowchart illustrating a processing flow in the parameter partial search process S703 of FIG. 7 in detail. In step S801, the MDI program generation unit 321 searches for the parameter portion in the snippet to find its format. In the present embodiment, the parameter portion of the automatic input is a parameter portion starting from "? TOOL" and ending with "?". Further, the parameter part of the manual input is a parameter part starting from "? MANUAL INPUT" and ending with "?". The format is not limited to this format.

The MDI program generation unit 321 determines in step S811 whether or not "? TOOL" is found. If "? TOOL" is found, the MDI program generation unit 321 sets in step S813 that it is a parameter part for automatically inputting specific tool information. If "? TOOL" is not found, the MDI program generation unit 321 determines in step S821 whether or not "? MANUAL INPUT" is found. If "? MANUAL INPUT" is found, the MDI program generation unit 321 sets in step S823 that it is a parameter part for manually inputting specific information. If "? MANUAL INPUT" is not found, the MDI program generation unit 321 finds "??", which is an optional conventional parameter partial marker, or "[[", which is a conventional function selection marker, in step S831. Is determined. If any of them is found, the MDI program generation unit 321 executes the existing manual input or function selection for each character. If neither is the case, the MDI program generation unit 321 returns to step S801 and continues the parameter partial search.

(Manual input processing)
In the manual input process S709 of FIG. 7, the process shown in the flowchart of FIG. 8B is performed. The MDI program generation unit 321 generates a parameter manual input screen in step S843. In step S845, the MDI program generation unit 321 displays the parameter manual input screen on the tool management screen 210 or the MDI screen 220. The MDI transfer module 320 waits for manual input by the user in step S847. If there is a manual input by the user, the MDI program generation unit 321 acquires the input value (parameter) in step S849. Then, the MDI program generation unit 321 adds an input value to the parameter portion of the manual input in step S851. A specific value of tool information may be set as an initial value in the parameter input field.

<Format of parameter part>
FIG. 9A is an example of the format of the parameter portion (format of the parameter portion) 910, and in the present embodiment, the parameter portion in the snippet is a character string sandwiched between “?” And “?”.

Format 1 in the parameter automatic input request is a format for inputting the value of a specific parameter. <Parameter identifier of automatic parameter input section>: <Parameter identifier>? Defined in. Here, <identifier of the parameter automatic input unit> is defined as "TOOL". For example, if there is a description "T? TOOL: Q0?" In the snippet, TOOL is the identifier of the parameter automatic input section for tool information, and Q0 indicates the tool number. It becomes.

Format 2 in the parameter automatic input request is a format for inputting a value obtained by calculating a constant value for a specific parameter value. <Parameter identifier of automatic parameter input section>: <Parameter identifier> <Operator> <Constant value>? Defined in. For example, if there is a description "G324H # 149B? TOOL: Q1101 + 100.? M0X0." In the snippet, Q1101 indicates the tool length shape correction value. For example, the tool length shape correction value of the tool is If it is 100., it will be replaced with G324H # 149B200.M0X0.

In format 1 in the parameter manual input request, the initial value of the manual input field is empty definition, and? <Identifier of manual parameter input section>: <Parameter identifier>? Defined in. Here, <identifier of parameter manual input unit> is defined as "MAMUAL INPUT". For example, if there is a description "G324H # 149B300.M0X? MANUALINPUT: G324X?" In the snippet, the G324X field will be displayed on the parameter manual input screen (initial value is empty), and enter "10.". If so, it will be replaced with G324H # 149B300.M0X10.

In format 2 in the parameter manual input request, the initial value of the manual input field is a constant value, and? <Identifier of manual parameter input section>: <Parameter identifier> = <Constant value>? Defined in. For example, if there is a description "G324H # 149B300.M0X? MANUALINPUT: G324X = 0.?" In the snippet, the initial value 0. is displayed in the G324X column on the parameter manual input screen, and "10." If is entered, it will be replaced with G324H # 149B300.M0X10.

In the format 3 in the parameter manual input request, the initial value of the input field of the manual input is determined in the same manner as the parameter automatic input format 1. <Identifier of manual parameter input unit>: <Parameter identifier> = <Identifier of automatic parameter input unit>: <Parameter identifier>? Defined in. For example, if there is a description "G324H # 149B300.M0X? MANUAL INPUT: G324X = TOOL: Q1102?" In the snippet, the tool diameter shape correction value is displayed as the initial value in the G324X column on the parameter manual input screen. (Q1102 indicates the tool diameter shape correction value), if "10." is input, it will be replaced with G324H # 149B300.M0X10.

In the format 4 in the parameter manual input request, the initial value of the input field of the manual input is determined in the same manner as the parameter automatic input format 2. <Identifier of manual parameter input unit>: <Parameter identifier> = <Identifier of automatic parameter input unit>: <Parameter identifier> <Operator> <Constant value>? Defined in. For example, if there is a description "G324H # 149B? MANUALINPUT: G324B = TOOL: Q1101 + 100.? M0X0.", The tool length shape correction value is set to +100 as the initial value in the G324B column on the parameter manual input screen. Is displayed (Q1101 indicates the tool length shape correction value), and if "150." is entered, it will be replaced with G324H # 149B250.M0X0.

The format of the parameter portion in FIG. 9A is merely an example, and various changes and combinations are possible.

<Specific example of MDI program>
FIG. 9B shows Table 920 summarizing the features of Examples 921-942 of an MDI program using the parameter portion format 910. Specifically, in each of Examples 921 to 928 (for the machining center), 931-932 (for the turning center), and 941-942 (for the tool offset), the format used, the tool information selection target, and the program generation definition. Complexity, snippet complexity, etc. are indicated by circles.

≪Example in machining center≫
(Example 921)
FIG. 10A is a diagram illustrating an example 921 of an MDI program in the machining center shown in FIG. 9B. The case where one tool is selected by the check box 1001 on the tool management screen 210 and the MDI transfer button 216 is pressed is described. The selected tool has a tool number of 10001. One tool selection on the tool management screen 210 replaces the parameter part of one snippet.

When the MDI transfer button 216 is touched, the MDI program generation unit 321 inserts the snippet 1 according to the program generation definition associated with the MDI transfer button 216. Next, the parameter part of the snippet 1 is searched. Then, the tool number 10001 of the selected tool is input to? TOOL: Q0? Of the searched parameter part to be automatically input, and the generated MDI program 1012 is displayed on the MDI screen 220.

The tool number is 10001.
Snippet 1 is
T? TOOL: Q0 ?;
G91G30Z0 .;
G91G30X0.Y0 .;
M6;
Is. "T? TOOL: Q0 ?;" corresponds to the parameter automatic input request format 1 in FIG. 9A, TOOL is an identifier (code string) indicating the parameter automatic input unit for inputting tool information, and Q0 is a specific. It is an identifier indicating the tool number which is the tool information.

The tool number 10001 selected on the tool management screen 210 is inserted at the position of? TOOL: Q0? For the parameter part "T? TOOL: Q0 ?;" of the snippet 1.
As an MDI program 1012
T10001;
G91G30Z0 .;
G91G30X0.Y0 .;
M6;
Is generated.
Here, "T10001;" is a command to index the 10001 tool in the magazine, "G91G30Z0 .;" and "G91G30X0.Y0 .;" are commands to move the spindle to the tool change position, and "M6;" is a tool change command. It is an order.

(Example 922)
FIG. 10B is a diagram illustrating an example 922 of an MDI program in the machining center shown in FIG. 9B. The case where two tools are selected by the check box on the tool management screen 210 and the MDI transfer button 216 is pressed is described. The first tool has a tool number of 10001. The second tool has a tool number of 10002.

When the MDI transfer button 216 is touched, the MDI program generation unit 321 inserts the snippet 1 according to the program generation definition associated with the MDI transfer button 216. Since a plurality of tools are selected, a plurality of snippets 1 are arranged and M1 (optional stop command) is inserted between them.

Specifically, for the first tool, the tool number 10001 is input to the parameter part? TOOL: Q0? Of the automatic input in the snippet 1 (1012). Further, since there is a second tool, the optional stop (M01) 1025 is inserted, and the tool number 10002 is input to the parameter part? TOOL: Q0? Of the automatic input in the same snippet 1 (1022). The MDI program 1021 that combines these is displayed on the MDI screen 220.

Snippet 1 is
T? TOOL: Q0 ?;
G91G30Z0 .;
G91G30X0.Y0 .;
M6;
Is.
As an MDI program
T10001;
G91G30Z0 .;
G91G30X0.Y0 .;
M6;
M1;
T10002;
G91G30Z0 .;
G91G30X0.Y0 .;
M6;
Is generated.
Here, "T10001;" is a command to index the 10001 tool in the magazine, "G91G30Z0 .;" and "G91G30X0.Y0 .;" are commands to move the spindle to the tool change position, and "M6;" is a tool change command. It is an order. With the optional stop (M1;) in between, "T10002;" is a command to index the 10002 tool in the magazine, "G91G30Z0 .;" and "G91G30X0.Y0 .;" are commands to move the spindle to the tool change position, "M6; ”is a tool change order.

(Example 923)
FIG. 10C is a diagram illustrating an example 923 of an MDI program in the machining center shown in FIG. 9B. The case where three tools are selected by the check box on the tool management screen 210 and the MDI transfer button 217 is pressed is described. The first tool is a drill tool, the tool number is 10001. The second tool is an end mill tool with a tool number of 10002. The third tool is an end mill tool, which has a tool number of 1003.

When the MDI transfer button 217 is touched, the MDI program generation unit 321 inserts the snippet 1 according to the program generation definition associated with the MDI transfer button 216, and then inserts the snippet 2 if the tool type is a drill. If it is an end mill, then insert the snippet 3. When multiple tools are selected, an M1 (optional stop command) is inserted between the set of snippets 1 and 2 and the set of snippets 1 and 3.

Specifically, for the first selection tool, the first tool number 10001 is input to the automatic input parameter part? TOOL: Q0? Of the snippet 1 (1012). Then, it is determined whether the first selected tool type is a drill or an end mill. Since the first selection tool type is a drill, snippet 2 (automatic call of the tool length measurement macro) is inserted (1035). After inserting the optional stop (M01) 1025, the second tool number 10002 is input to the automatic input parameter part? TOOL: Q0? Of the snippet 1 (1022). Then, it is determined whether the second selection tool type is a drill or an end mill. Since the second selection tool type is an end mill, the tool diameter shape correction value (“20.” in FIG. 10C) of the selected end mill is automatically set in the automatic input parameter part? TOOL: Q1102? Of snippet 3 (1036). ). Further, after inserting the optional stop (M01) 1025, the third tool number 1003 is input to the automatic input parameter part? TOOL: Q0? Of the snippet 1 (1032). Then, it is determined whether the third selected tool type is a drill or an end mill. Since the third selected tool type is an end mill, the tool diameter shape correction value of the selected end mill (“30.” in FIG. 10C is automatically set in the automatic input parameter part? TOOL: Q1102? Of snippet 3 (1037). The MDI program 1031 that combines these programs is displayed on the MDI screen 220.

Snippet 1 is
T? TOOL: Q0 ?;
G91G30Z0 .;
G91G30X0.Y0 .;
M6;
Is.
Snippet 2 is G324H # 149 ;, which is an instruction to call a macro for measuring tool length.
The snippet 3 is G324H # 149B300.M0X? TOOL: Q1102 ?;, the tool length measurement macro is called, the temporary tool length is set to 300, and the tool diameter shape correction value set for the selected tool is set. This is an instruction to be input as an X-axis shift amount. Here, Q1102 is a parameter identifier indicating a tool diameter shape correction value.
As an MDI program
T10001;
G91G30Z0 .;
G91G30X0.Y0 .;
M6;
G324H # 149;
M1;
T10002;
G91G30Z0 .;
G91G30X0.Y0 .;
M6;
G324H # 149B300.M0X20 .;
M1;
T10003;
G91G30Z0 .;
G91G30X0.Y0 .;
M6;
G324H # 149B300.M0X30 .;
Is generated.
Here, "T10001;" to "M6;" are operation commands of the snippet 1 by the tool of the tool number 10001. "G324H # 149;" is an instruction to call a macro for measuring tool length. With the optional stop (M1;) in between, "T10002;" to "M6;" are operation commands for snippet 1 by the tool with tool number 10002. "G324H # 149B300.M0X20 .;" calls the tool length measurement macro, specifies the temporary tool length to "300." In snippet 3 for the tool with tool number 10002, and corrects the X-axis shift amount to the tool diameter shape. This is an instruction specified in "20." that is automatically entered as a value. With the optional stop (M1;) in between, "T10003;" to "M6;" are operation commands for snippet 1 by the tool with tool number 1003. "G324H # 149B300.M0X30 .;" calls the tool length measurement macro, specifies the temporary tool length to "300." In snippet 3 for the tool with tool number 1003, and corrects the X-axis shift amount to the tool diameter shape. This is an instruction to specify "30." that is automatically entered as a value.

(Example 924)
FIG. 10D is a diagram illustrating an example 924 of an MDI program in the machining center shown in FIG. 9B. Example 924 is an example in which, in Example 923, not the snippet 3 but the snippet 4 including the format 2 shown in FIG. 9A of the parameter automatic input request is read out and an MDI program is generated. In the snippet 4, the macro for measuring the tool length is automatically called, and the temporary tool length is automatically input. Note that, in FIG. 10D, the same as in FIG. 10C except that the snippet 3 is changed to the snippet 4, so the same reference number is assigned to the same component, and the description of the same process is omitted to avoid duplication.

When the MDI transfer button 217 is touched, the MDI program generation unit 321 inserts the snippet 1 according to the program generation definition associated with the MDI transfer button 217, and then inserts the snippet 2 if the tool type is a drill. If it is an end mill, then insert the snippet 4. When multiple tools are selected, an M1 (optional stop command) is inserted between the set of snippets 1 and 2 and the set of snippets 1 and 4.

Specifically, since the selected second and third tools are end mills, the snippet 4 is inserted next to the snippet 1. Then, in the automatic input parameter part? TOOL: Q1101 + 100.? Of the snippet 4, a value obtained by adding 100 to the tool length shape correction value set for the selected tool is input (1046, 1047). That is, in the instruction 1046, 200. (= 100 + 100) is input to the automatic input parameter part? TOOL: Q1101 + 100.?, And in the instruction 1046, 250. (=) is input to the automatic input parameter part? TOOL: Q1101 + 100.? 150 + 100) is entered. The MDI program 1041 generated in this way is displayed on the MDI screen 220.

The snippet 4 is G324H # 149B? TOOL: Q1101 + 100.? M0X0 .; and corresponds to the format 2 of the parameter automatic input request of FIG. 9A. The snippet 4 calls the tool length measurement macro, inputs the value obtained by adding 100 to the tool diameter shape correction value set for the selected tool as the temporary tool length, and inputs 0. as the X-axis shift amount. It is an order to do. Here, Q1101 is a parameter identifier indicating a tool length shape correction value.
As an MDI program
T10001;
G91G30Z0 .;
G91G30X0.Y0 .;
M6;
G324H # 149;
M1;
T10002;
G91G30Z0 .;
G91G30X0.Y0 .;
M6;
G324H # 149B200.M0X0 .;
M1;
T10003;
G91G30Z0 .;
G91G30X0.Y0 .;
M6;
G324H # 149B250.M0X0 .;
Is generated.
Here, "G324H # 149B200.M0X0 .;" calls the tool length measurement macro, and for the tool with tool number 10002, the temporary tool length is used, and the tool length shape correction value "100" of the selected tool is used. It is a command to specify "200. (= 100 + 100)" and specify the X-axis shift amount to "0." of the snippet 4. "G324H # 149B250.M0X0 .;" calls the tool length measurement macro, and for the tool with tool number 1003, the temporary tool length is set to "250." Using the tool length shape correction value "150" of the selected tool. (= 150 + 100) ”, and the X-axis shift amount is specified as“ 0. ”In snippet 4.

(Example 925)
FIG. 10E is a diagram illustrating an example 925 of an MDI program in the machining center shown in FIG. 9B. Explains the case where three tools are selected by the check boxes on the tool management screen 210 and the MDI transfer button 217 is pressed. Example 925 is an example in which, in Example 923, not the snippet 3 but the snippet 5 including the format 3 shown in FIG. 9A of the parameter manual input request is read out and an MDI program is generated. In the snippet 5, the tool length measurement macro is automatically called, the initial value of the X-axis shift amount is set to the tool diameter shape correction value of the selected tool, and then the user can manually input the X-axis shift amount. Note that, in FIG. 10E, the same as in FIG. 10C except that the snippet 3 is changed to the snippet 5, so the same reference number is assigned to the same component, and the description of the same process is omitted in order to avoid duplication.

When the MDI transfer button 217 is touched, the MDI program generation unit 321 inserts the snippet 1 according to the program generation definition associated with the MDI transfer button 217, and if the tool type is a drill, the snippet 2 is inserted. The snippet 5 is then inserted. When multiple tools are selected, an M1 (optional stop command) is inserted between the set of snippets 1 and 2 and the set of snippets 1 and 3.

Specifically, since the selected second and third tools are end mills, the snippet 5 is inserted next to the snippet 1. Then, since the snippet 5 describes? MANUALINPUT: G324X = TOOL: Q1102? To request the manual input of the X-axis shift amount, open the parameter manual input screen 230 and manually input the X-axis shift amount. wait. Since TOOL: Q1102 is specified in the snippet 5, the tool diameter shape correction values (“20.” and “30.”) of the selected tool are set as the initial values in the manual input field 232 of the parameter manual input screen 230. Is displayed. The user may maintain or change the initial value of the manual input field 232 by referring to the preview 231 of the MDI program in the parameter manual input screen 230.

When the user inputs a change in the manual input field 232 and touches the MDI transfer button 233, manual input to the parameter portion of the snippet 5 is realized. In FIG. 10E, since "21." is input in the manual input field 232 of the tool number 10002, "21." is input in the manual input parameter part? MANUALINPUT: G324X = TOOL: Q1102? Of the snippet 5. 1056). Further, since "31." is input in the manual input field 232 of the tool number 1003, "31." is input in the manual input parameter part? MANUALINPUT: G324X = TOOL: Q1102? Of the snippet 5 (1057). The MDI program 1051 that combines these is displayed on the MDI screen 220.

The snippet 5 is G324H # 149B300.M0X? MANUALINPUT: G324X = TOOL: Q1102 ?;, and is an instruction to call the tool length measurement macro and manually input the tool diameter shape correction value as the X-axis shift amount. Here, Q1102 is a parameter identifier indicating a tool diameter shape correction value of the selected tool.
As an MDI program
T10001;
G91G30Z0 .;
G91G30X0.Y0 .;
M6;
G324H # 149;
M1;
T10002;
G91G30Z0 .;
G91G30X0.Y0 .;
M6;
G324H # 149B300.M0X21 .;
M1;
T10003;
G91G30Z0 .;
G91G30X0.Y0 .;
M6;
G324H # 149B300.M0X31 .;
Is generated.
Here, "G324H # 149B300.M0X21 .;" calls the tool length measurement macro, specifies the temporary tool length to "300." In snippet 5 for the tool with tool number 10002, and manually sets the X-axis shift amount. This is an instruction to set to the entered "21.". "G324H # 149B300.M0X31 .;" calls the tool length measurement macro, specifies the temporary tool length as "300." In snippet 5 for the tool with tool number 1003, and manually inputs the X-axis shift amount. 31. ”is an instruction to set.

(Example 926)
FIG. 10F is a diagram illustrating an example 926 of an MDI program in the machining center shown in FIG. 9B. Explains the case where three tools are selected by the check boxes on the tool management screen 210 and the MDI transfer button 217 is pressed. In Example 926, in Example 923, the snippet 6 is used instead of the snippet 3. In the snippet 6, the macro for measuring the tool length is automatically called, the temporary tool length is automatically input according to the parameter automatic input request format 2 of FIG. 9A, and the X-axis shift amount is manually input according to the parameter manual input request format 1. do. Note that, in FIG. 10F, the same as in FIG. 10C except that the snippet 3 is changed to the snippet 6, so the same reference number is assigned to the same component, and the description of the same process is omitted in order to avoid duplication.

When the MDI transfer button 217 is touched, the MDI program generation unit 321 inserts the snippet 1 according to the program generation definition associated with the MDI transfer button 217, and if the tool type is a drill, the snippet 2 is inserted. The snippet 6 is then inserted. When multiple tools are selected, M1 (optional stop command) is inserted between the set of snipetos 1 and 2 and the set of snipests 1 and 6.

Specifically, since the selected second and third tools are end mills, the snippet 6 is inserted next to the snippet 1. In the snippet 6, (tool length shape correction value +100 of the selected tool) is input corresponding to? TOOL: Q1101 + 100.?, Which indicates the automatic input of the temporary tool length. Further, since? MANUALINPUT: G324X? Requesting the manual input of the X-axis shift amount is described, the parameter manual input screen 230 is opened and the manual input of the X-axis shift amount is waited for. The user refers to the preview 231 of the MDI program in the parameter manual input screen 230, manually inputs the tool diameter shape correction value in the manual input field 232, and touches the MDI transfer button 233 to touch the parameter of the snippet 6. Manual input to the part is realized. In FIG. 10F, "200." Is input to the automatic input parameter part? TOOL: Q1101 + 100.? Of the snippet 6 for the tool number 10002. Then, since "21." is input in the manual input field 232 of the tool number 10002, "21." is input in the manual input parameter part? MANUALINPUT: G324X? (1066). Further, for the tool number 1003, "200." Is input to the automatic input parameter part? TOOL: Q1101 + 100.? Of the snippet 6. Then, since "31." is input in the manual input field 232 of the tool number 1003, "31." is input in the manual input parameter part? MANUALINPUT: G324X? (1067). The MDI program 1061 that synthesizes these programs is displayed on the MDI screen 220.

Snippet 6 is G324H # 149B3? TOOL: Q1101 + 100.? M0X? MANUALINPUT: G324X ?;, calls the tool length measurement macro, automatically inputs the temporary tool length, and manually inputs the X-axis shift amount. It is an order. Here, Q1101 is a parameter identifier indicating a tool length shape correction value, and Q1102 is a parameter identifier indicating a tool diameter shape correction value.
As an MDI program
T10001;
G91G30Z0 .;
G91G30X0.Y0 .;
M6;
G324H # 149;
M1;
T10002;
G91G30Z0 .;
G91G30X0.Y0 .;
M6;
G324H # 149B200.M0X21 .;
M1;
T10003;
G91G30Z0 .;
G91G30X0.Y0 .;
M6;
G324H # 149B250.M0X31 .;
Is generated.
Here, "G324H # 149B200.M0X21 .;" calls the tool length measurement macro, and for the tool with tool number 10002, the temporary tool length is set to "200" using the tool length shape correction value of the automatically input tool. It is a command to set ". (= 100 + 100)" and set the X-axis shift amount to "21." manually input. "G324H # 149B200.M0X31 .;" calls the tool length measurement macro, and for the tool with tool number 1003, the temporary tool length is set to "250. (=) Using the tool length shape correction value of the automatically input tool. It is a command to set to "150 + 100)" and set to "31." where the X-axis shift amount is manually input.

(Example 927)
FIG. 10G is a diagram illustrating an example 927 of an MDI program in the machining center shown in FIG. 9B. Explains the case where three tools are selected by the check boxes on the tool management screen 210 and the MDI transfer button 217 is pressed. In Example 927, the snippet 7 is used instead of the snippet 3 in the example 923. In the snippet 7, the measurement macro is automatically called, the temporary tool length is manually input according to the parameter manual input request format 4 of FIG. 9A, and the X-axis shift amount is manually input according to the parameter manual input request format 2. In FIG. 10G, the same as in FIG. 10C except that the snippet 3 is changed to the snippet 7, so the same reference number is assigned to the same component, and the description of the same process is omitted in order to avoid duplication.

When the MDI transfer button 217 is touched, the MDI program generation unit 321 inserts the snippet 1 according to the program generation definition associated with the MDI transfer button 217, and if the tool type is a drill, the snippet 2 is inserted. The snippet 7 is then inserted. When multiple tools are selected, M1 (optional stop command) is inserted between the set of snippets 1 and 2 and the set of snippets 1 and 7.

Specifically, since the selected second and third tools are end mills, the snippet 7 is inserted next to the snippet 1. In the snippet 7,? MANUAL INPUT: G324B = TOOL: Q1101 + 100.?, Which indicates the manual input of the temporary tool length, is described, and? MANUAL INPUT: G324X = 0.?, Which requires the manual input of the X-axis shift amount, is described. Therefore, the parameter manual input screen 230 is opened, and the manual input of the temporary tool length and the X-axis shift amount is awaited. The manual input field 1072 of the parameter manual input screen 230 contains "200. (= 100 + 100)" as the initial value for the tool number 10002, and the manual input field 232 contains "0." as the initial value. ing. Further, "250. (= 150 + 100)" is entered as an initial value for the tool number 1003, and "0." is entered as an initial value in the manual input field 232. The user may maintain or change the initial values of the manual input fields 1072 and 232 by referring to the preview 231 of the MDI program in the parameter manual input screen 230.

The user changes the initial value, manually inputs to the manual input field 1072 of the temporary tool length and the manual input field 232 of the X-axis shift amount, and touches the MDI transfer button 233 to go to the parameter part of the snippet 7. Manual input is realized. In FIG. 10G, since "150." Is input in the manual input field 1072 of the tool number 10002 and "21." is input in the manual input field 232, the manual input parameter part of the snippet 7? MANUALINPUT: G324B = TOOL: "150." is input to Q1101 + 100.?, And "21." is input to the manual input parameter part? MANUALINPUT: G324X = 0.? (1076). Also, since "200." Was entered in the manual input field 1072 of the tool number 1003 and "31." was entered in the manual input field 232, the snippet 7's? MANUAL INPUT: G324B = TOOL: Q1101 + 100.? "200" is input, and "31." is input to the manual input parameter part? MANUALINPUT: G324X = 0.? (1077). The MDI program 1071 that synthesizes these programs is displayed on the MDI screen 220.

Snippet 7 is G324H # 149B3? MANUALINPUT: G324B = TOOL: Q1101 + 100.? M0X? MANUALINPUT: G324X = 0.?; This is an instruction to manually input the shift amount. Here, Q1101 is a parameter identifier indicating a tool length shape correction value.
As an MDI program
T10001;
G91G30Z0 .;
G91G30X0.Y0 .;
M6;
G324H # 149;
M1;
T10002;
G91G30Z0 .;
G91G30X0.Y0 .;
M6;
G324H # 149B150.M0X21 .;
M1;
T10003;
G91G30Z0 .;
G91G30X0.Y0 .;
M6;
G324H # 149B200.M0X31 .;
Is generated.
Here, "G324H # 149B250.M0X21 .;" calls the tool length measurement macro, and for the tool with tool number 10002, the temporary tool length is set to the manually input tool length shape correction value "150.". This is a command to set the X-axis shift amount to "21.", which is manually input. "G324H # 149B300.M0X31 .;" calls the tool length measurement macro, sets the temporary tool length to the manually input tool length shape correction value "200." for the tool with tool number 1003, and shifts to the X-axis. This is an instruction to set the amount to "31.", which is manually entered.

(Example 928)
FIG. 10H is a diagram illustrating an example 928 of an MDI program in the machining center shown in FIG. 9B. Example 928 is an example of reading the snippet 8 and generating an MDI program. In the snippet 8, the tool diameter wear correction value is read out as a macro variable (# 100) and changed, and the changed value is written back from the macro variable (# 100) as the tool diameter wear correction value.

When the MDI transfer button 216 is touched, the MDI program generation unit 321 inserts the tool number of the selected tool into the snippet 8 according to the program generation definition associated with the MDI transfer button 216. Specifically, the tool number of the selected tool is input to the automatic input parameter part? TOOL: Q0? (1082). The generated MDI program 1081 is displayed on the MDI screen 220.

Snippet 8
G388A100.T? TOOL: Q0 ?. Q1104;
# 100 = # 100 + 0.1;
G389A100.T? TOOL: Q0 ?. Q1104;
Is. Here, G388 is a tool data read command, and G389 is a tool data write command. A100 represents the variable number 100. Q1104 is a parameter identifier that indicates the tool diameter wear compensation value.
As an MDI program
G388A100.T10001.Q1104;
# 100 = # 100 + 0.1;
G389A100.T10001.Q1104;
Is generated.
Here, G388A100.T10001.Q1104; is an instruction to read the tool diameter wear compensation value of tool number 10001 from the tool management function to the macro variable # 100. # 100 = # 100 + 0.1; is an instruction to add "0.1" to the read tool diameter wear compensation value. G369A100.T10001.Q1104; is an instruction to write the value of macro variable # 100 (that is, the read macro variable # 100 + 0.1) to the tool diameter wear compensation value of tool number 10001 of the tool management function.

≪Example in a turning center≫
(Example 931)
FIG. 11A is a diagram illustrating an example 931 of an MDI program in the turning center shown in FIG. 9B. The tool 1111 selected on the tool management screen 1110 in the turning center has a station number and a correction number as tool information. When the MDI transfer button 1112 is touched, the MDI program generation unit 321 inserts the snippet 9 corresponding to the selected tool based on the program generation definition of the MDI program associated with the MDI transfer button 1112.

Specifically, the snippet 9 that describes the station indexing and the command of the correction number is read out, and the T code indicated by the parameter identifier Q1118 is input to the snippet 9 from the tool information of the tool 1111 to generate the MDI. The program 1114 is displayed on the MDI screen 220.

Snippet 9
T? TOOL: Q1118 ?;
Is. Here, Q1118 is a parameter identifier indicating a T code.
As an MDI program
T0121;
Is generated.
In the turning center T command, the left two digits represent the station number (01) and the right two digits represent the correction number (21), and the station indexing and the correction number command are performed together.

(Example 932)
11B is a diagram illustrating an example 932 of an MDI program in the turning center shown in FIG. 9B. Example 932 is an MDI program generated when a plurality of tools 1111 and 1121 are selected. When the MDI transfer button 1112 is touched, the MDI program generation unit 321 inserts the snippet 9 corresponding to each of the selected tools based on the program generation definition of the MDI program associated with the MDI transfer button 1112. do. If multiple tools are selected, an optional stop (M1) is inserted between them.

Specifically, the snippet 9 describing the station indexing and the command of the correction number is read out, and the T code indicated by the parameter identifier Q1118 is input to the snippet 9 from the tool information of the tool 1111 (1114). Further, the snippet 9 is read out, and the T code indicated by the parameter identifier Q1118 is input to the snippet 9 from the tool information 1121 (1124). In the displayed MDI program 1123, an optional stop (M1) 1125 is inserted between the MDI programs 1114 and 1124 by the snippets 9 of the two tools 1111 and 1121.

The selected tools are T-code 0121 and T-code 0222.
Snippet 9
T? TOOL: Q1118 ?;
Is. Here, Q1118 is a parameter identifier indicating a T code.
As an MDI program
T0121;
M1;
T0222;
Is generated.
In the turning center T command, the left two digits represent the station number and the right two digits represent the correction number. After the station 01 indexing and the correction number (21) command are collectively performed, the station 02 indexing and correction number ( 22) and the command are put together.

It is possible to attach a tool holder to the turret station and attach multiple tools such as two or four, but tool management when a tool holder is attached to the turret station and two tools are attached. The screen 1130 is as shown in FIG. 11C. An MDI program can be automatically generated by, for example, selecting the second tool 1131 of ST1 and touching the MDI transfer button 1132 on the tool management screen 1130.

<< Example of tool offset >>
(Example 941)
FIG. 12A is a diagram illustrating a specific example 941 of an MDI program at the tool offset shown in FIG. 9B. The tool correction information 1211 of the tool selected on the tool offset screen 1210 used in the tool offset has a correction number, a tool diameter shape correction value, and a tool diameter wear correction value. Then, when the tool offset number is selected on the tool offset screen and the MDI transfer button 1212 is touched, the MDI program generation unit 321 snippets based on the program generation definition of the MDI program associated with the MDI transfer button 1212. Insert 10 Specifically, the snippet 10 is read out, and a program is generated in which a tool offset is input to increase the tool diameter wear compensation value by a certain amount (1214). The generated program 1214 is displayed on the MDI screen 220 as an MDI program 1213.

Snippet 10
? TOOLOFFSET: DWEARVAR? =? TOOLOFFSET: DWEARVAR? +0.1;
Is. Here, TOOLOFFSET is an identifier of the parameter automatic input unit for tool offset information, and DWEARVAR is a parameter identifier indicating a system variable of the tool diameter wear compensation value.
As an MDI program
# 12001 = # 12001 + 0.1;
Is generated.
Here, the selected correction number is No. 1, the tool diameter wear correction value is 10, and the system variable # 12001 is set as the tool diameter wear correction value whose correction number is No. 1 by the MDI program 1241. Do to escape by increasing a certain amount. Generally, machining accuracy is generally required in the radial direction as compared with the long direction. For example, a screw hole. For example, assuming that the tolerance is ± 0.01, when the first machining of the combination of the tool and the workpiece is performed, the workpiece is once missed by 0.1 and the workpiece is measured, and the correction value is adjusted based on the measurement result to produce a defective product. You don't have to.

(Example 942)
FIG. 12B is a diagram illustrating an example 942 of an MDI program at the tool offset shown in FIG. 9B. Similar to FIG. 12A, the tool correction information 1211 of the tool selected on the tool offset screen 1210 used in the tool offset has a correction number, a tool diameter shape correction value, and a tool diameter wear correction value. Then, when the tool offset number is selected on the tool offset screen and the MDI transfer button 1212 is touched, the MDI program generation unit 321 snippets based on the program generation definition of the MDI program associated with the MDI transfer button 1212. 11 is inserted. Specifically, the snippet 11 is read out, and a program is generated in which the tool offset is input and the tool diameter wear compensation value is rewritten by a specified value (1224). The generated program 1224 is displayed on the MDI screen 220 as an MDI program 1223.

Snippet 11 is G10G90L13P? TOOLOFFSET: NUMBER? R? TOOLOFFSET: DWEAR + 0.1 ?;
Is. Here, NUMBER is a correction number, and DWEAR is a parameter identifier indicating a tool diameter wear correction value.
As an MDI program
G10G90L13P1R10.1;
Is generated.
Here, G10L13 is a command for rewriting the tool diameter wear correction value, P is a correction number, and R is a correction value.

As described above, according to the present embodiment, the parameter part described in the standard program is automatically replaced with the specific tool information of the tool selected on the tool management screen, so that the user can use the specific tool information including the tool number. It is possible to generate an MDI program by setting it automatically without key input by. In addition, the parameter part described in the standard program is automatically replaced with the offset value of the tool selected on the tool offset screen, so the offset value of the tool is automatically set without key input by the user, and the MDI program is executed. Can be generated.

That is, since the parameter part described in the snippet is defined by a specific format, it is easy for the user to edit the snippet by changing and modifying it, and the generation and editing of the MDI program can be realized without mistake.

By using the technique of the present embodiment, it is possible to greatly reduce the time and effort required to generate the MDI program and the risk of operation errors. This is particularly effective when a plurality of tools are continuously called to the tool spindle.

[Third Embodiment]
Next, the machine tool control device according to the third embodiment of the present invention will be described. The machine tool control device according to the present embodiment is different from the second embodiment in that the snippet generated and edited by the user can be used. In the present embodiment, the parameter portion having a specific format is automatically inserted into the standard program according to the selection instruction on the screen by the user. Since other configurations and operations are the same as those in the second embodiment, the same configurations and operations are designated by the same reference numerals and detailed description thereof will be omitted.

<Structure including snippet generation and editing>
As shown in FIG. 13A, when a plurality of tools 213 are selected on the tool management screen 210 and the MDI transfer (user-defined A) button 1314 and the MDI transfer (user-defined B) button 1315 are touched, the MDI As shown in screen 1316, a user-generated MDI program is generated based on the snippet associated with each button.

FIG. 13B shows an example in which a plurality of MDI transfer buttons are not displayed on the tool management screen 210 and a pull-down menu 1318 is displayed as in FIG. 13A. For example, when MDI transfer (user-defined) is selected, the lower menu 1319 is displayed.

<Snippet generation and editing procedure>
FIG. 13C is a diagram showing a snippet generation / editing screen 1320 of the machine tool control device. On the snippet generation edit screen 1320, first, the first "T (index to ATC (Automatic Tool Changer) position)" of the first line of the snippet is input to the snippet display screen 1321. When "automatic parameter input" is instructed in the snippet generation edit window 1322, "? TOOL:" is automatically input to the snippet display screen 1323. Next, when the "tool number" is instructed in the snippet generation edit window 1324, "Q0" is automatically input to the snippet display screen 1325. Then, when "confirm" is instructed in the snippet generation edit window 1326, the input of the first line of the snippet of "T? TOOL: Q?" Is completed. Although an example of initial input is shown in FIG. 13C, when reading and editing an existing snippet, input can be easily performed by the same operation.

FIG. 13D is a diagram showing another snippet generation / editing screen 1340 of the machine tool control device. On the snippet generation edit screen 1340, a snippet is generated or edited for each instruction of each line. A snippet display screen 1341 and a numerical value input field 1342 for each function (G28 function in the figure) are shown. By touching the Insert button 1343, the value in the input field 1342 is inserted into the snippet. The snippet generation / editing screen 1340 is used for simple generation / editing of snippets.

<Structure of tool management module>
FIG. 14 is a block diagram showing the configuration of the MDI transfer module 1420. In FIG. 14, the same components as those in FIG. 5A are designated by the same reference numbers, and duplicate description will be omitted.

The MDI transfer module 1420 includes a snippet acquisition unit 1421, a snippet editing data acquisition unit 1422, and a snippet generation editing unit 1423. Further, the MDI transfer module 1420 includes a database 1410 having a snippet editing data storage unit 1424. The snippet acquisition unit 1421 acquires the snippet for editing from the snippet storage unit 323 by the snippet identifier. The snippet editing data acquisition unit 1422 acquires snippet editing data from the snippet editing data storage unit 1424. The snippet generation editing unit 1423 edits the snippet acquired by the snippet acquisition unit 1421 using the snippet editing data. If there is no acquired snippet, a snippet is generated. The generated or edited snippet is stored searchably in the snippet storage unit 323.

(Data storage section for snippet editing)
FIG. 15 is a diagram showing the configuration of the snippet editing data storage unit 1424. The snippet editing data storage unit 1424 has an input mode table 1510, a format table 1520, and an input data table 1530. The input mode table 1510 stores the snippet descriptor 1412 corresponding to the user setting 1511 whether the input mode of the parameter portion is automatic input or manual input. In the present embodiment, "? TOOL" is stored in the case of automatic input, and "? MANUAL INPUT" is stored in the case of manual input. In the format table 1520, the format definition 1522 and the input description example 1523 are stored in association with the format number 1521 as shown in FIG. 9A. Input description example 1523 is displayed for user reference. The input data table 1530 stores the parameter identifier 1532 and the format number 1533 to be used in association with the input data name 1531. For example, if the input data name 1531 is a tool number, "Q0" is stored in the parameter identifier 1532. If the input data name 1531 is a tool length correction shape, "Q1101" is stored in the parameter identifier 1532. If the input data name 1531 is a tool diameter correction shape, "Q1102" is stored in the parameter identifier 1532.

<Procedure for creating and editing snippets>
FIG. 16A is a flowchart showing a procedure for generating and editing a snippet of a machine tool control device according to the present embodiment. The MDI transfer module 1420 determines in step S1601 whether the snippet is generated or edited. If the snippet is generated, the MDI transfer module 1420 sets a new snippet identifier in step S1611. The MDI transfer module 1420 inputs the function description of the snippet in order in step S1613. Then, the MDI transfer module 1420 determines in step S1615 that the input parameter position has been reached. When the input parameter position is reached, the MDI transfer module 1420 executes the description insertion process of the parameter portion in step S1617. Then, in step S1619, the MDI transfer module 1420 determines the end of snippet generation. If the snippet generation is not completed, the MDI transfer module 1420 returns to step S1613 and continues the snippet generation.

On the other hand, in the case of editing the snippet, the MDI transfer module 1420 inputs the snippet identifier in step S1621. In step S1623, the MDI transfer module 1420 reads out the snippet using the snippet identifier and displays it on the MDI screen. Then, the MDI transfer module 1420 sets in step S1625 which position of the existing snippet to edit. In step S1627, the MDI transfer module 1420 determines whether or not the editing position is the parameter partial editing position. If it is the parameter part edit position, the MDI transfer module 1420 executes the description insertion process of the parameter part in step S1629. On the other hand, if it is not the parameter part edit position, the MDI transfer module 1420 corrects the function description of the parameter part in step S1631. Then, in step S1633, the MDI transfer module 1420 determines the end of editing the snippet. If the editing of the snippet is not completed, the MDI transfer module 1420 returns to step S1625 and continues editing the snippet.

Upon determining the end of snippet generation or snippet editing, the MDI transfer module 1420 stores the generated new snippet or the edited existing snippet in step S1620.

(Process to insert description of parameter part)
FIG. 16B is a flowchart showing the procedure of the description insertion processing S1617 and S1629 of the parameter portion. The MDI transfer module 1420 determines in step S1641 whether it is an automatic input or a manual input. If it is an automatic input, the MDI transfer module 1420 inserts "? TOOL" at the input position of the snippet in step S1643. On the other hand, if it is a manual input, the MDI transfer module 1420 inserts "? MANUAL INPUT" into the input position of the snippet in step S1643.

Next, in step S1647, the MDI transfer module 1420 determines whether or not the data to be input next is an input value identifier. If it is an input value identifier, the MDI transfer module 1420 inputs the input value identifier or selects it from a pull-down menu or the like in step S1649. If it is not an input value identifier, the MDI transfer module 1420 determines in step S1651 whether it is a function identifier or not. If it is a function identifier, the MDI transfer module 1420 inputs the function identifier or selects it from a pull-down menu in step S1653. If it is not a function identifier, proceed to the next without doing anything. In step S1655, the MDI transfer module 1420 determines whether or not the input of the parameter portion is completed. If the input of the parameter portion is not completed, the MDI transfer module 1420 returns to step S1647 and repeats the process until the parameter meter is completed.

When the input of the parameter portion is completed, the MDI transfer module 1420 inserts a “?” At the end of the parameter portion in step S1647 to end the process.

According to this embodiment, it is possible to automatically insert a parameter part and generate and edit a snippet without key input by the user. Then, the MDI program can be efficiently generated by using the dunipet generated and edited by the user.

[Fourth Embodiment]
Next, the machine tool control device according to the fourth embodiment of the present invention will be described. The machine tool control device according to the present embodiment is different from the second embodiment and the third embodiment in that the generation and editing of the program generation definition can be realized by a simple operation. In the present embodiment, the snippet in the program generation definition is changed and modified according to the selection instruction on the screen by the user, and the program generation definition is automatically edited. Since other configurations and operations are the same as those in the second embodiment, the same configurations and operations are designated by the same reference numerals and detailed description thereof will be omitted.

<Procedure for generating and editing program definitions>
FIG. 17 shows a procedure for generating and editing a program generation definition of a machine tool control device. In the program definition generation edit screen 1720, first, the old snippet of the program generation definition is displayed on the program definition display screen 1721. When "change" is instructed in the program definition generation / editing window 1722 and then a new snippet is selected in the program definition generation / editing window 1724, the new snippet is displayed on the program definition display screen 1723. When "correction" is instructed in the program definition generation edit window 1722, the contents of the program generation definition are updated by modifying the old snippet according to the description of the third embodiment.

<Structure of tool management module>
FIG. 18 is a block diagram showing a configuration of the MDI transfer module 1820 of the machine tool control device. In FIG. 18, the same reference numbers are assigned to the same components as those in FIGS. 5 and 14, and duplicate description will be omitted.

The MDI transfer module 1820 includes a program generation definition acquisition unit 1821 and a program generation definition generation and editing unit 1822. The program generation definition acquisition unit 1821 acquires the program generation definition from the program generation definition storage unit 322 by using the program generation definition identifier. The program generation definition generation editing unit 1822 edits the acquired program generation definition by, for example, replacing the snippet or changing the snippet. If the program generation definition is not acquired, a new program generation definition is generated.

<Program definition generation and editing process procedure>
FIG. 19A is a flowchart showing the procedure of the program definition generation and editing process. In step S1901, the MDI transfer module 1820 determines whether to generate or edit the program generation definition. If the program generation definition is generated, the MDI transfer module 1820 sets a new program generation definition identifier in step S1911. The MDI transfer module 1820 describes a program generation definition in step S1913. Then, the MDI transfer module 1820 determines in step S1915 that the snippet placement position has been reached. When the snippet placement position is reached, the MDI transfer module 1820 executes the snippet change process in step S1817. Then, in step S1919, the MDI transfer module 1820 determines the end of generation of the program generation definition. If the generation of the program generation definition is not completed, the MDI transfer module 1820 returns to step S1913 and continues the generation of the program generation definition.

On the other hand, in the case of editing the program generation definition, the MDI transfer module 1820 inputs the program generation definition identifier in step S1921. In step S1923, the MDI transfer module 1820 reads out the program generation definition using the program generation definition identifier and displays it on the MDI screen. Then, in step S1925, the MDI transfer module 1820 sets which position of the existing program generation definition is to be edited. In step S1827, the MDI transfer module 1820 determines whether or not the editing position is the snippet editing position. If it is the snippet edit position, the MDI transfer module 1820 executes the snippet change process in step S1929. On the other hand, if it is not the snippet edit position, the MDI transfer module 1820 modifies the description of the program generation definition in step S1931. Then, in step S1933, the MDI transfer module 1820 determines the end of editing the program generation definition. If the editing of the program generation definition is not completed, the MDI transfer module 1820 returns to step S1925 and continues editing the program generation definition.

Upon determining the end of generation of the program generation definition or the end of editing of the program generation definition, the MDI transfer module 1820 stores the generated new program generation definition or the edited existing program generation definition in step S1920.

(Snippet change process)
FIG. 19B is a flowchart showing the procedure of the snippet change processing S1917 and S1929. In step S1941, the MDI transfer module 1820 determines whether or not the snippet has been changed. If the snippet is changed, the MDI transfer module 1820 inputs a new snippet identifier in step S1943. In step S1945, the MDI transfer module 1820 reads out a new snippet and replaces it with the original snippet. The MDI transfer module 1820 determines in step S1947 whether to edit the read and replaced snippet. When editing the snippet, the snippet editing in the third embodiment is executed.

If the snippet is not modified, the MDI transfer module 1820 determines in step S1949 whether to edit the original snippet. When editing the snippet, the snippet editing in the third embodiment is executed. If neither is a snippet edit, the process ends.

According to this embodiment, snippets can be automatically changed and modified to generate and edit program generation definitions without user keystrokes.

[Other embodiments]
Although the invention of the present application has been described above with reference to the embodiments, the invention of the present application is not limited to the above-described embodiment. Various changes that can be understood by those skilled in the art can be made to the structure and details of the present invention within the technical scope of the present invention. Also included in the technical scope of the invention are systems or devices in any combination of the different features contained in each embodiment.

Further, the present invention may be applied to a system composed of a plurality of devices, or may be applied to a single device. Further, the present invention is also applicable when an information processing program that realizes the functions of the embodiment is supplied to a system or an apparatus and executed by a built-in processor. In order to realize the functions of the present invention on a computer, the technical scope of the present invention includes a program installed in the computer, a medium containing the program, a server for downloading the program, and a processor for executing the program. .. In particular, at least a non-transitory computer readable medium containing a program that causes a computer to execute the processing steps included in the above-described embodiment is included in the technical scope of the present invention.

Claims (5)

A tool management unit that creates and displays a tool management screen that displays a list of tools prepared for machine tools, and
An MDI program generator that calls a standard program, adds the tool information of the tool selected on the tool management screen to the standard program, and generates an MDI (Manual Data Input) program.
Equipped with
When two or more tools are selected on the tool management screen, the MDI program generator adds the tool information of the selected tool to each of the number of standard programs corresponding to the number of selected tools. A machine tool control device that generates the MDI program by continuously arranging the MDI program . A tool management unit that creates and displays a tool management screen that displays a list of tools prepared for machine tools, and
An MDI program generator that calls a standard program, adds the tool information of the tool selected on the tool management screen to the standard program, and generates an MDI (Manual Data Input) program.
Equipped with
The MDI program generation unit is a machine tool control device that generates the MDI program by arranging an optional stop command between the routine programs arranged continuously. Further provided with a storage unit for storing the standard program,
The machine tool control device according to claim 1 or 2 , wherein the MDI program generation unit reads the standard program from the storage unit and generates the MDI program. The machine tool control according to any one of claims 1 to 3, wherein the MDI program generation unit acquires tool information of a type corresponding to the description of the standard program from the tool management unit and adds it to the standard program. Device. The tool management unit that generates and displays the tool offset screen that displays the offset value of the tool prepared in the machine tool,
An MDI program generator that calls a standard program, adds the offset value of the tool selected on the tool offset screen to the standard program, and generates an MDI (Manual Data Input) program.
Machine tool control device equipped with.

Images