JP2023005227A - Machine tool controller and machine tool control method - Google Patents

Abstract

To efficiently generate an MDI program.SOLUTION: A machine tool controller includes: an industrial tool management unit that generates an industrial tool management screen image showing a list of industrial tools prepared for a machine tool, and displays the screen image; and an MDI program generation unit that calls a routine program, adds, to the routine program, industrial tool information on an industrial tool selected in the industrial tool management screen image, and generates a manual data input (MDI) program.SELECTED DRAWING: Figure 1

Description

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

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

JP-A-2002-166335

However, the technique described in the above document cannot efficiently generate an MDI program.

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

In order to achieve the above object, a machine tool control device according to the present invention includes:
a tool management unit that generates and displays a tool management screen that displays a list of tools prepared for the machine tool;
an MDI program generation unit that calls a fixed form program, adds tool information of the tool selected on the tool management screen to the fixed form program, and generates an MDI (Manual Data Input) program;
provided.

In order to achieve the above object, a machine tool control method according to the present invention comprises:
a tool management step of generating and displaying a tool management screen displaying a list of tools prepared for the machine tool;
an MDI program generation step of calling a fixed form program and adding tool information of the tool selected on the tool management screen to the fixed form program to generate an MDI (Manual Data Input) program;
including.

In order to achieve the above object, a machine tool control device according to the present invention includes:
a tool management unit that generates and displays a tool offset screen that displays the offset values of the tools prepared for the machine tool;
an MDI program generator that calls a fixed form program, adds the offset value of the tool selected on the tool offset screen to the fixed form program, and generates an MDI (Manual Data Input) program;
provided.

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

1 is a block diagram showing the configuration of a machine tool control device according to a first embodiment; FIG. It is a figure which shows the display operation part of the machine tool control apparatus which concerns on 2nd Embodiment. It is a figure which shows the transition of the display operation part of the machine tool control apparatus which concerns on 2nd Embodiment. It is a figure which shows the structure of the machine tool containing the machine tool control apparatus which concerns on 2nd Embodiment. It is a figure explaining the functional composition of the machine tool containing the machine tool control device concerning a 2nd embodiment. It is a figure which shows the operation|movement outline|summary of the machine tool control apparatus which concerns on 2nd Embodiment. FIG. 11 is a block diagram showing the configuration of a tool management module of the machine tool control device according to the second embodiment; FIG. 10 is a diagram showing configurations of a tool information table and a generation definition table according to the second embodiment; FIG. 8 is a block diagram showing the configuration of an MDI transfer module of the machine tool control device according to the second embodiment; FIG. FIG. 11 is a diagram showing the configuration of a program generation definition storage unit and a snippet storage unit according to the second embodiment; 9 is a flow chart showing a processing procedure of an MDI transfer module of the machine tool control device according to the second embodiment; 9 is a flowchart showing the procedure of program generation processing according to the second embodiment; FIG. 10 is a flowchart showing the procedure of parameter partial search processing according to the second embodiment; FIG. 9 is a flow chart showing the procedure of manual input processing according to the second embodiment; FIG. 12 is a diagram showing an example of a format of a parameter portion according to the second embodiment; FIG. FIG. 11 is a diagram showing a table of an example of an MDI program using the parameter part format according to the second embodiment; FIG. 9 is a diagram showing an example 921 of an MDI program in the machining center according to the second embodiment; FIG. FIG. 10 is a diagram showing an example 922 of an MDI program in the machining center according to the second embodiment; FIG. FIG. 10 is a diagram showing an example 923 of an MDI program in the machining center according to the second embodiment; FIG. FIG. 11 is a diagram showing an example 924 of an MDI program in the machining center according to the second embodiment; FIG. FIG. 11 is a diagram showing an example 925 of an MDI program in the machining center according to the second embodiment; FIG. FIG. 11 is a diagram showing an example 926 of an MDI program in the machining center according to the second embodiment; FIG. FIG. 11 is a diagram showing an example 927 of an MDI program in the machining center according to the second embodiment; FIG. FIG. 11 is a diagram showing an example 928 of an MDI program in the machining center according to the second embodiment; FIG. FIG. 11 is a diagram showing display of an example 931 of an MDI program in a turning center according to the second embodiment; FIG. 11 is a diagram showing an example 932 of an MDI program in the turning center according to the second embodiment; FIG. FIG. 11 is a diagram showing an example of a tool management screen in the turning center according to the second embodiment; FIG. FIG. 11 is a diagram showing a display of an example 941 of an MDI program in tool offset according to the second embodiment; FIG. 11 is a diagram showing an example 942 of an MDI program in tool offset according to the second embodiment; FIG. It is a figure which shows the display operation part of the machine tool control apparatus which concerns on 3rd Embodiment. It is a figure which shows the example of the tool management screen of the machine tool control apparatus which concerns on 3rd Embodiment. FIG. 12 is a diagram showing a snippet generation screen of the machine tool control device according to the third embodiment; FIG. 12 is a diagram showing a snippet editing screen of the machine tool control device according to the third embodiment; FIG. 11 is a block diagram showing the configuration of an MDI transfer module of the machine tool control device according to the third embodiment; It is a figure which shows the structure of the data storage part for snippet editing which concerns on 3rd Embodiment. FIG. 12 is a flowchart showing the procedure of snippet generation and editing processing of the machine tool control device according to the third embodiment; FIG. FIG. 14 is a flow chart showing a procedure of a parameter part description insertion process according to the third embodiment; FIG. It is a figure which shows the production|generation editing procedure of the program definition of the machine tool control apparatus which concerns on 4th Embodiment. FIG. 11 is a block diagram showing the configuration of an MDI transfer module of a machine tool control device according to a fourth embodiment; FIG. 14 is a flow chart showing a procedure of program definition generation and editing processing of the machine tool control device according to the fourth embodiment; FIG. FIG. 14 is a flowchart showing the procedure of snippet change processing according to the fourth embodiment; FIG.

BEST MODE FOR CARRYING OUT THE INVENTION Exemplary embodiments of the present invention will be described in detail below with reference to the drawings. However, the components described in the following embodiments are merely examples, and are not intended to limit the technical scope of the present invention only to them. Note that the term “snippet” used in this embodiment is a reusable short program that is used to create and edit programs. For example, in an NC program, it refers to a short program. A "snippet" corresponds to a "fixed form program" in the claims.

[First embodiment]
A machine tool control device 100 as a first embodiment of the present invention will be described with reference to FIG. A 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 section 101 and an MDI (Manual Data Input) program generation section 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 fixed form program 121 and adds the tool information 112 of the tool selected on the tool management screen 111 to the fixed form program 121 to generate the MDI program 122 .

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

[Second embodiment]
Next, a machine tool control device 200 according to a second embodiment of the invention will be described. The machine tool control device 200 provides a snippet with tool information of a single or a plurality of tools/pots/STs (stations) designated by the operator as parameters and transfers the snippet to the MDI function.

Machine tool controller 200 generates an MDI program including at least one snippet according to the program generation definition. Here, the program generation definition is logic for generating a program using a part not based on a snippet and a part based on a snippet.

A snippet may include a parameter part for inputting tool information as a parameter, and specifying what information is to be received by describing variables in a specific format in the parameter part. The parameter portion can be classified into an automatic input parameter portion for automatically inputting parameters and a manual input parameter portion for manually inputting parameters by the user. If a snippet including a 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 worker inputting the parameter. An MDI program is generated. When multiple pieces of tool/pot/ST information are specified on the tool management screen, multiple snippets are synthesized based on each piece of information. At that time, an arbitrary command such as an optional stop can be inserted between snippets according to the program generation definition.

Here are three simple example snippets.
The first example snippet is
T?TOOL:Q1?;
G30X0.Y0.Z0.;
M6;
This is an example of automatic input described in .
Here, the first line indicates the indexing of the Q1 tool to the ATC position, the second line indicates return to origin, and the third line indicates ATC. is. Here, TOOL is a description to be replaced with the tool number indicated by the subsequent parameter identifier Q1.

The second example snippet 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 a diameter correction shape correction value.

A third example snippet is
G324H#149B300.M0X?MANUALINPUT:G324X=TOOL:Q1102?;
is an example of manual input of radius correction shape correction values in automatic tool length measurement (G324).

<Operation procedure of the machine tool controller>
The display operation unit of the machine tool control device 200 incorporated in the machine tool 250 will be described below 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 of the machine tool 250. FIG. When an MDI mode for generating and executing an MDI program is set using a switch (not shown), a tool management screen 210 and an 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 one of the buttons 216 and 217, the generation definition of the MDI program corresponding to each button is read. Then, the snippet specified in the read generation definition is read. The read snippet includes a parameter portion 225 described in a specific format, and the tool information of the tool 211 (here, as an example, tool number 10002) is added to the parameter portion 225 to execute the MDI program. generated. The generated MDI program is displayed on the MDI screen 220. FIG. Here, the tool information includes tool identification information (tool number), tool length shape, tool length wear, tool radius shape, tool radius wear, parameters such as correction values, and other information related to tools. It is a concept that can include various information.

MDI transfer buttons 216 and 217 are displayed on the tool management screen 210 . 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 linked to the button 216, and displays the MDI program generated by combining 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, parameters, etc.) of the tool 213 selected on the tool management screen 210 . Also, an optional stop (M function=M01) 228 is automatically inserted between multiple 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 . A snippet "G324H#149B300.M0X?MANUALINPUT...?" Since this snippet 229 requires manual input of variables, a manual input screen 230 is displayed at the same time as the MDI transfer (measurement) button 217 is touched. The user refers to the preview 231 of the MDI program, inputs numerical values in the manual input field 232, and then touches the MDI transfer button 233, thereby realizing manual input of the parameters of the snippet 229. FIG.

<Configuration and operation of machine tool>
As shown in FIG. 3A, machine tool 250 includes machine tool controller 200 and machining center 302 controlled by machine tool controller 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 vertical form, the X, Y, and Z axes are defined as in FIG. 3A.

The machine tool control device 200 has a display operation section 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 tools to be used. The machine tool control device 200 also has an MDI (Manual Data Input) mode and has an MDI function module that operates with an MDI program. Mode selection keys of the control key group 304 include an MDI mode key 305 .

In the MDI mode, function instructions as shown in FIG. 3B are defined, and the MDI program is described by these function instructions. Classification of function instructions and basic function instructions are shared, but some optional dedicated function instructions are also used.

(Overview of functional configuration)
The machine tool controller 200 includes a tool management module 310, an MDI transfer module 320, and an MDI function module 330, as shown in FIG. 3C. The tool management module 310 has a tool management section 311 and a tool information storage section 312 . The tool management module 310 also manages the tool management screen 210. FIG. 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 . Also, 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 . Also, 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. Stored in the tool information storage unit 312 . The tool management unit 311 also 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 for replacing the parameter part described in the snippet. The tool management unit 311 includes a tool identifier indicating tool information that replaces the parameter portion and a specific tool information identifier (eg, Q0). Upon receiving a request to send information (see (#3) in FIG. 3C), the tool management unit 311 selects specific tool information (for example, 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), and the MDI program generation unit 321 extracts the predetermined parameter part of the snippet. The MDI program is generated by replacing with the specified tool information. The exchange of specific tool information in (#3) and (#4) in FIG. 3C is repeated the number of times (the number of selected tools×the number of automatic input parameter portions). Here, the specific tool information is extracted in the tool management module 310, but the MDI program generation unit 321 accesses the tool information storage unit 312 and extracts the specific tool information necessary for replacing the parameter part. Tool information may be extracted.

The MDI program generation unit 321 of the MDI transfer module 320 uses the program generation definition identifier received from the tool management unit 311 to read the program generation definition corresponding to the pressed button from the program generation definition storage unit 322 (FIG. 3C). See (#2) inside). Next, the MDI program generation unit 321 searches for a snippet identifier described in the read program generation definition. Then, using the snippet identifier, the snippet is read from the snippet storage unit 323 (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 identifies attributes of the parameter part. When 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 part 321 requests the tool management part 311 for the specific tool information to replace the parameter part described in the snippet. do. That is, a request for information transmission including the identifier of the tool and the identifier of the specific tool information (for example, Q0) is transmitted to the tool management section 311 (see (#3) in FIG. 3C). The MDI program generation unit 321 receives specific tool information (for example, tool number if Q0) among all tool information related to each selected tool from the tool management unit 311 ((# in FIG. 3C). 4)), replace this parameter portion with the received specific tool information for the selected tool. The exchange of specific tool information (#3) and (#4) in FIG. 3C is repeated the number of times (the number of selected tools×the number of automatic input parameter portions). Alternatively, the MDI program generation unit 321 may access the tool information storage unit 312 and extract specific tool information necessary for replacing the parameter portion. On the other hand, the MDI program generation unit 321 replaces the specified parameter portion with the tool information input by the user from the parameter manual input screen 230 when it is confirmed that the tool information of the selected tool is manually input. 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 MDI function unit 331 of the NC of the MDI function module 330, and the MDI program is executed. Also, the generated MDI program and its execution state are displayed on the MDI screen 220 . Although the MDI screen 220 is displayed when the MDI program is generated here, the present invention is not limited to this. In order to set the generated program to the MDI function of the NC, the MDI screen 220 should be displayed in that state. Alternatively, the MDI function may be used internally without displaying the MDI screen 220 .

<Configuration of tool management module>
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. The tool management module 310 also 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, an automatic parameter input unit 411 for tool information, a database 410; In FIG. 4A, (#1), (#3), and (#4) indicate the same processing as the processing in FIG. 3C.

A 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 this 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 tool information input from the display operation unit 201 and stores it in the tool information storage unit 312 of the database 410 . A display control unit 404 controls display of tool information on the display operation unit 201 . The operation control unit 405 controls user input operations 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 tools displayed on the display operation unit 201, and generates a program corresponding to when 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 specified by the user from the display operation unit 201 under the control of the operation control unit 405. do. The program generation definition identifier 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 . Also, if a snippet can be directly selected from the display operation unit 201, the snippet identifier 491 may be included.

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

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

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

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

(Generation definition identifier table)
The generation definition identifier table 481 in FIG. 4B is used by the generation definition identifier acquisition unit 408 to acquire the program generation period identifier corresponding to the button displayed on the tool management screen 210 and selected by the user. The generated 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 tool. A button type 433 is associated with each instruction screen position 432, and a menu position 434 and a generation definition identifier 435 when one button includes a plurality of menus (for example, a pull-down menu) are stored.

<Configuration of MDI transfer module>
5A, the MDI transfer module 320 includes a module interface 501, an input/output interface 502, a tool identifier acquisition section 503, a program generation definition identifier acquisition section 505, and a program generation definition acquisition section 506. The MDI transfer module 320 also 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 processes as those in FIGS. 3C and 4A.

A module interface 501 is an interface that controls data exchange between the MDI transfer module 320 and the tool management module 310 and 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 peripherals. In this 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 one or more tool identifiers 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 corresponding 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 using the program generation definition identifier.

The snippet acquisition unit 507 acquires a snippet 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 part is replaced with a tool identifier or other tool information is arranged, and sends it to the MDI function module 330 . Based on the program generation definition, the MDI program generation unit 321 automatically replaces the parameter portion with a tool identifier or other tool information if the format of the parameter portion 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 a manual input field on the display operation unit 201 to acquire manual input data. Then, the parameter manual input unit 324 replaces the parameter portion with the tool information manually input by the user.

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

(Program generation definition storage and snippet storage)
The program generation definition storage unit 322 in FIG. 3C stores the program generation definition 532 in association with the generation definition identifier 531 as shown in FIG. 5B. At least one snippet identifier and the location of the snippet in the MDI program (snippet position) 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 .

The snippet storage unit 323 of FIG. 3C stores the snippets and provides the MDI transfer module 320 with the snippets linked by the snippet identifier included in the program generation definition, as shown in FIG. 5B. That is, each row of the snippet storage unit 323 specifies a snippet, and stores a fixed form part 542, an automatic input parameter part 543, and a manual input parameter part 544 in association with the snippet identifier 541. FIG.

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

The MDI transfer module 320 determines in step S601 whether it is in the MDI mode. If not in MDI mode, other processing is executed. If in MDI mode, MDI transfer module 320 waits for tool selection by the user using 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, proceeding to step S613, the MDI program generation unit 321 acquires the extracted tool information regarding the selected tool. Further, the flow advances to step S615 to execute MDI program generation processing in accordance with the acquired program generation definition. The MDI transfer module 320 outputs the generated MDI program to the MDI function module 330 in step S617.

(MDI program generation processing)
FIG. 7 is a flowchart showing in detail the flow of processing in the MDI program generation processing S615 of FIG. The MDI program generation unit 321 reads a snippet specified by the program generation definition from the snippet storage unit 323 in step S701. Next, in step S703, the MDI program generation unit 321 executes parameter partial search processing in the read snippet. Then, in step S705, the MDI program generation unit 321 determines 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 generator 321 inputs specific tool information selected from the tool information acquired in step S613 into the parameter portion in step S707. On the other hand, if it is manual input, the MDI program generation unit 321 executes manual input processing in step S709. When the parameter input to one parameter part in the snippet is finished, the MDI program generation unit 321 determines in step S711 whether or not the search for the parameter part in the snippet is completed. If the parameter part search is not completed, the MDI program generation unit 321 returns to step S703 and repeats the replacement process for the remaining parameter parts in the snippet.

When the parameter part search for one snippet is completed, in step S713, the MDI program generator 321 arranges the snippet with all parameter parts replaced in the MDI program according to the program generation definition. Next, in step S715, the MDI program generation unit 321 determines whether or not there is the next snippet designated by the program generation definition. If another snippet is specified, the MDI program generator 321 returns to step S701, reads the next snippet specified in the program generation definition, and starts searching for the parameter part.

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

(Parameter partial search process)
FIG. 8A is a flowchart explaining in detail the flow of processing in the parameter partial search processing S703 of FIG. The MDI program generator 321 searches the parameter part in the snippet to find its format in step S801. In this embodiment, the parameter portion of the automatic input is the parameter portion starting with "?TOOL" and ending with "?". Also, the manual input parameter portion is a parameter portion that starts with "?MANUALINPUT" and ends with "?". Note that the format is not limited to this format.

The MDI program generation unit 321 determines whether or not "?TOOL" is found in step S811. If "?TOOL" is found, the MDI program generator 321 sets in step S813 that it is a parameter portion for automatically inputting specific tool information. If "? TOOL" is not found, the MDI program generator 321 determines in step S821 whether or not "? MANUALINPUT" is found. If "?MANUALINPUT" is found, the MDI program generator 321 sets in step S823 that it is a parameter part for manually inputting specific information. If “?MANUALINPUT” is not found, the MDI program generator 321 optionally determines in step S831 whether the conventional parameter part mark “?” or the conventional function selection mark “[[” was found. judge. If either is found, the MDI program generator 321 executes the existing manual character-by-character input and function selection. If neither, the MDI program generator 321 returns to step S801 to continue 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. The MDI program generation unit 321 displays a parameter manual input screen on the tool management screen 210 or the MDI screen 220 in step S845. 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 generator 321 acquires the input value (parameter) in step S849. Then, in step S851, the MDI program generation unit 321 adds an input value to the parameter portion of the manual input. A specific value of the tool information may be set as the initial value of the parameter input field.

<Format of parameter part>
FIG. 9A shows an example of a parameter part format (parameter part format) 910. In this embodiment, the parameter part in a 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, and ? <Identifier of automatic parameter input part>:<Parameter identifier>? defined by Here, <identifier of parameter automatic input unit> is defined as "TOOL". For example, if there is a description "T?TOOL:Q0?" becomes.

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

Format 1 in the parameter manual input request has an initial value of an empty definition in the input field for manual input, and ? <Identifier of parameter manual input unit>:<Parameter identifier>? defined by Here, <identifier of parameter manual input section> is defined as "MAMUALINPUT". For example, if the snippet contains "G324H#149B300.M0X?MANUALINPUT:G324X?", the G324X field will be displayed on the parameter manual input screen (the initial value is empty) and enter "10." is replaced with G324H#149B300.M0X10.

Format 2 in the parameter manual input request has a constant value as the initial value in the input field for manual input, and ? <Identifier of manual parameter input unit>:<Parameter identifier>=<Constant value>? defined by For example, if the snippet contains the description "G324H#149B300.M0X?MANUALINPUT:G324X=0.?" is replaced with G324H#149B300.M0X10.

In Form 3 in the parameter manual input request, the initial values of the input fields for manual input are determined in the same way as in Form 1 for automatic parameter input, and ? <identifier of manual parameter input unit>:<parameter identifier>=<identifier of automatic parameter input unit>:<parameter identifier>? defined by For example, if the snippet contains the description "G324H#149B300.M0X?MANUALINPUT:G324X=TOOL:Q1102?", the tool diameter shape correction value will be displayed as the initial value in the G324X column on the parameter manual input screen. (Assuming that Q1102 indicates the tool diameter shape compensation value), and if "10." is entered, it will be replaced with G324H#149B300.M0X10.

In Form 4 in the parameter manual input request, the initial values of the input fields for manual input are determined in the same way as in Form 2 for automatic parameter input, and ? <identifier of manual parameter input unit>:<parameter identifier>=<identifier of automatic parameter input unit>:<parameter identifier><operator><constant value>? defined by For example, if there is a description of "G324H#149B?MANUALINPUT:G324B=TOOL:Q1101+100.?M0X0.", the initial value in the G324B field on the parameter manual input screen will be +100. (Q1101 indicates the tool length shape correction value), and if you enter "150.", it will be replaced with G324H#149B250.M0X0.

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

<Specific example of MDI program>
FIG. 9B shows a table 920 summarizing characteristics of example MDI programs 921-942 using the parameter part format 910. FIG. Specifically, in each of examples 921-928 (for machining centers), 931-932 (for turning centers), and 941-942 (for tool offsets), the format used, the selection of tool information, and the program generation definition Complexity, snippet complexity, etc. are indicated by circles.

<<Example in a machining center>>
(Example 921)
FIG. 10A is a diagram explaining an example 921 of the MDI program in the machining center shown in FIG. 9B. A case is explained in which one tool is selected by a check box 1001 on the tool management screen 210 and the MDI transfer button 216 is pressed. The selected tool has a tool number of 10001. A single tool selection on the tool management screen 210 replaces the parameter portion of a single snippet.

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

The tool number is 10001.
Snippet 1 is
T?TOOL:Q0?;
G91G30Z0.;
G91G30X0.Y0.;
M6;
is. "T?TOOL:Q0?;" corresponds to Format 1 of the parameter automatic input request in FIG. This is an identifier that indicates a tool number, which is tool information.

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

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

When the MDI transfer button 216 is touched, the MDI program generation unit 321 inserts snippet 1 according to the program generation definition associated with the MDI transfer button 216 . Since multiple tools are selected, multiple 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 automatic input parameter ?TOOL:Q0? in snippet 1 (1012). Furthermore, since there is a second tool, an optional stop (M01) 1025 is inserted, and the tool number 10002 is input to the automatic input parameter ?TOOL:Q0? in the same snippet 1 (1022). An MDI program 1021 combining 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 10001st tool in the magazine, "G91G30Z0.;" and "G91G30X0.Y0.;" are commands to move the spindle to the tool change position, and "M6;" is an order. With an optional stop (M1;) in between, "T10002;" is a command to index tool number 10002 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.

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

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

Specifically, for the first selected tool, the first tool number 10001 is input to the automatic input parameter section ?TOOL:Q0? of snippet 1 (1012). Then, it is determined whether the first selected tool type is a drill or an end mill. Since the first selected tool type is a drill, snippet 2 (automatic call of tool length measurement macro) is inserted (1035). After inserting the optional stop (M01) 1025, the second tool number 10002 is entered in the automatic input parameter section ?TOOL:Q0? of snippet 1 (1022). Then, it is determined whether the second selected tool type is a drill or an end mill. Since the second selected tool type is an end mill, automatically set the tool diameter shape correction value (“20.” in FIG. 10C) of the selected end mill in the automatic input parameter part ?TOOL:Q1102? of snippet 3 (1036) ). Furthermore, after inserting an optional stop (M01) 1025, the third tool number 10003 is entered in the automatic input parameter section ?TOOL:Q0? of 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 automatic input parameter part ?TOOL:Q1102? of snippet 3 is automatically set to the tool diameter shape correction value of the selected end mill ("30." An MDI program 1031 combining 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 the tool length measurement macro.
Snippet 3 is G324H#149B300.M0X?TOOL:Q1102?;, which calls the tool length measurement macro, sets the temporary tool length to 300, and sets the tool radius shape correction value set for the selected tool to This command is input as the 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 instructions for snippet 1 by the tool with tool number 10001. "G324H#149;" is an instruction to call the tool length measurement macro. From "T10002;" to "M6;" with an optional stop (M1;) interposed therebetween is an operation command of 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." This is an instruction to specify "20." automatically entered as a value. From "T10003;" to "M6;" with an optional stop (M1;) interposed therebetween is an operation command of snippet 1 by the tool with tool number 10003. "G324H#149B300.M0X30.;" calls the tool length measurement macro, specifies the temporary tool length to "300." This is an instruction to specify "30." automatically entered as a value.

(Example 924)
FIG. 10D is a diagram illustrating an example MDI program 924 in the machining center shown in FIG. 9B. Example 924 is an example of generating an MDI program by reading not snippet 3 but snippet 4 including format 2 shown in FIG. 9A of the parameter automatic input request in example 923 . In snippet 4, the tool length measurement macro is automatically called to automatically input the temporary tool length. Note that FIG. 10D is the same as FIG. 10C except that snippet 3 is changed to snippet 4, so the same reference numbers are given to the same components, and the description of the same processing is omitted to avoid duplication.

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

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

Snippet 4 is G324H#149B?TOOL:Q1101+100.?M0X0.; and corresponds to format 2 of the parameter automatic input request in FIG. 9A. 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. is an instruction to Here, Q1101 is a parameter identifier indicating the 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 calculated using the tool length shape correction value "100" of the selected tool. This command specifies “200.(=100+100)” and specifies “0.” in snippet 4 as the X-axis shift amount. "G324H#149B250.M0X0.;" calls the tool length measurement macro, and for the tool with tool number 10003, the temporary tool length is set to "250. (=150+100)” and the X-axis shift amount to “0.” in snippet 4.

(Example 925)
FIG. 10E is a diagram illustrating an example MDI program 925 in the machining center shown in FIG. 9B. A case is described in which three tools are selected by 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, instead of snippet 3, snippet 5 including format 3 of the parameter manual input request shown in FIG. 9A is read to generate an MDI program. In snippet 5, the tool length measurement macro is automatically called to set the initial value of the X-axis shift amount 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 FIG. 10E is the same as FIG. 10C except that snippet 3 is changed to snippet 5, so the same components are given the same reference numerals, and the description of the same processing is omitted to avoid duplication.

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

Specifically, since the second and third tools selected are end mills, snippet 5 is inserted after snippet 1 . Since ?MANUALINPUT:G324X=TOOL:Q1102?, which requires manual input of the X-axis shift amount, is described in snippet 5, open the parameter manual input screen 230 and manually input the X-axis shift amount. wait. Since TOOL:Q1102 is specified in snippet 5, the tool diameter shape correction values ("20." Is displayed. The user may refer to the MDI program preview 231 in the parameter manual entry screen 230 to maintain or change the initial values of the manual entry fields 232 .

When the user inputs changes 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, "21." is input to the manual input field 232 of the tool number 10002, so "21." is input to the manual input parameter ?MANUALINPUT:G324X=TOOL:Q1102? 1056). Also, since "31." is entered in the manual input field 232 of the tool number 10003, "31." is entered in the manual input parameter portion ?MANUALINPUT:G324X=TOOL:Q1102? An MDI program 1051 combining these is displayed on the MDI screen 220 .

Snippet 5 is G324H#149B300.M0X?MANUALINPUT:G324X=TOOL:Q1102?;, which 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 the tool radius 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." This is an instruction to set the input "21.". "G324H#149B300.M0X31.;" calls the tool length measurement macro, specifies the temporary tool length to "300." 31.”.

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

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

Specifically, since the second and third tools selected are end mills, snippet 6 is inserted after snippet 1 . In snippet 6, (tool length shape correction value of the selected tool+100) is input corresponding to ?TOOL:Q1101+100.? indicating automatic input of the temporary tool length. Also, since ?MANUALINPUT:G324X? for requesting manual input of the X-axis shift amount is described, the parameter manual input screen 230 is opened to wait for manual input of the X-axis shift amount. The user refers to the preview 231 of the MDI program in the parameter manual input screen 230, performs manual input in the manual input field 232 of the tool diameter shape correction value, and touches the MDI transfer button 233, so that the parameters of the snippet 6 Manual entry into parts is realized. In FIG. 10F, for tool number 10002, "200." Since "21." is entered in the manual input field 232 of the tool number 10002, "21." is entered in the manual input parameter section ?MANUALINPUT:G324X? (1066). Also, for tool number 10003, "200." is input to the automatic input parameter portion ?TOOL:Q1101+100.? Since "31." is entered in the manual input field 232 of the tool number 10003, "31." is entered in the manual input parameter section ?MANUALINPUT:G324X? (1067). An MDI program 1061 combining these programs is displayed on the MDI screen 220 .

Snippet 6 is G324H#149B3?TOOL:Q1101+100.?M0X?MANUALINPUT:G324X?;, which calls the tool length measurement macro, automatically inputs the temporary tool length, and manually inputs the X-axis shift amount. is an order. Here, Q1101 is a parameter identifier indicating the tool length shape correction value, and Q1102 is a parameter identifier indicating the 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 macro for tool length measurement, and for the tool with tool number 10002, the temporary tool length is set to "200" using the automatically input tool length shape correction value of the tool. (=100+100)” and the X-axis shift amount is set to the manually input “21.”. "G324H#149B200.M0X31.;" calls the tool length measurement macro, and for the tool with tool number 10003, the temporary tool length is set to "250.(= 150+100)”, and the X-axis shift amount is set to manually input “31.”.

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

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

Specifically, since the second and third tools selected are end mills, snippet 7 is inserted after snippet 1 . Snippet 7 describes ?MANUALINPUT:G324B=TOOL:Q1101+100.? indicating manual input of temporary tool length, and ?MANUALINPUT:G324X=0.? requesting manual input of X-axis shift amount. Therefore, the parameter manual input screen 230 is opened to wait for manual input of the temporary tool length and the X-axis shift amount. 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. Also, "250.(=150+100)" is entered as the initial value for the tool number 10003, and "0." The user may refer to the MDI program preview 231 in the parameter manual input screen 230 to maintain or change the initial values of the manual input fields 1072 and 232 .

The user changes the initial values, manually inputs the manual input field 1072 for the temporary tool length and the manual input field 232 for the X-axis shift amount, and touches the MDI transfer button 233 to transfer to the parameter part of the snippet 7. manual input is realized. In FIG. 10G, "150." was entered in the manual input field 1072 of the tool number 10002 and "21." "150." is input to Q1101+100.?, and "21." is input to the manual input parameter portion ?MANUALINPUT:G324X=0.? (1076). Also, since "200." is entered in the manual input field 1072 of the tool number 10003 and "31." is entered in the manual input field 232, " 200" is entered, and "31." is entered in the manual input parameter portion ?MANUALINPUT:G324X=0.? (1077). An MDI program 1071 combining 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 for manually inputting a shift amount. Here, Q1101 is a parameter identifier indicating the 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, sets the temporary tool length for the tool with tool number 10002 to the manually entered tool length shape correction value "150." This is an instruction to set the X-axis shift amount to the manually input "21.""G324H#149B300.M0X31.;" calls the tool length measurement macro, sets the temporary tool length of the tool with tool number 10003 to the manually entered tool length shape correction value "200." This is an instruction to set the amount to manually entered "31."

(Example 928)
FIG. 10H is a diagram illustrating an example MDI program 928 in the machining center shown in FIG. 9B. Example 928 is an example of reading snippet 8 and generating an MDI program. In 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 entered in the automatic input parameter section ?TOOL:Q0? (1082). The generated MDI program 1081 is displayed on the MDI screen 220. FIG.

Snippet 8 is
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 variable number 100. Q1104 is a parameter identifier indicating a 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 a command to read the tool radius wear correction value of tool number 10001 from the tool management function to macro variable #100. #100=#100+0.1; is a command to add "0.1" to the read tool diameter wear correction value. G369A100.T10001.Q1104; is an instruction to write the value of macro variable #100 (that is, read macro variable #100+0.1) to the tool radius wear correction value of tool number 10001 in the tool management function.

≪Example of a turning center≫
(Example 931)
FIG. 11A is a diagram illustrating an example MDI program 931 in the turning center shown in FIG. 9B. A 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 linked to the MDI transfer button 1112 .

Specifically, the snippet 9 describing station indexing and correction number commands is read, the T code indicated by the parameter identifier Q1118 is input to the snippet 9 from the tool information of the tool 1111, and the generated MDI Program 1114 is displayed on MDI screen 220 .

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

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

Specifically, the snippet 9 describing station indexing and correction number commands is read, 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). Also, snippet 9 is read, and the T code indicated by parameter identifier Q1118 is input to snippet 9 from tool information 1121 (1124). In the displayed MDI program 1123, an optional stop (M1) 1125 is inserted between the MDI programs 1114, 1124 by snippet 9 of the two tools 1111, 1121.

The selected tools are T code 0121 and T code 0222.
Snippet 9 is
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 T command of the turning center, the left 2 digits represent the station number and the right 2 digits represent the correction number. 22) are collectively executed.

By attaching a tool holder to the turret station, it is possible to attach a plurality of tools such as 2 or 4 tools. Screen 1130 appears as shown in FIG. 11C. On the tool management screen 1130, for example, by selecting the second tool 1131 of ST1 and touching the MDI transfer button 1132, an MDI program can be automatically generated.

≪Example of tool offset≫
(Example 941)
FIG. 12A is a diagram illustrating a specific example 941 of the MDI program in the tool offset shown in FIG. 9B. The tool correction information 1211 of the tool selected on the tool offset screen 1210 used for tool offset has a correction number, a tool diameter shape correction value, and a tool radius wear correction value. Then, when a tool offset number is selected on the tool offset screen and the MDI transfer button 1212 is touched, the MDI program generation unit 321 generates a snippet based on the program generation definition of the MDI program linked to the MDI transfer button 1212. Insert 10. Specifically, the snippet 10 is read, and a program is generated for inputting the tool offset and increasing the tool radius wear correction value by a certain amount (1214). A generated program 1214 is displayed on the MDI screen 220 as an MDI program 1213 .

Snippet 10 is
?TOOLOFFSET:DWEARVAR?=?TOOLOFFSET:DWEARVAR?+0.1;
is. Here, TOOLOFFSET is an identifier of an automatic parameter input unit for tool offset information, and DWEARVAR is a parameter identifier indicating a system variable for tool radius wear correction value.
As an MDI program,
#12001=#12001+0.1;
is generated.
Here, the selected correction number is 1 and the tool radius wear correction value is 10, and the MDI program 1241 sets the system variable #12001 to the tool radius wear correction value with the correction number of 1, and the tool radius wear correction value By increasing a certain amount, you can escape. In general, machining accuracy is generally required more in the radial direction than in the longitudinal direction. For example, screw holes. For example, if the tolerance is ±0.01, when the combination of the tool and the workpiece is processed for the first time, the workpiece is measured after machining with a relief of 0.1, and the correction value is adjusted based on the measurement results to produce defective products. It will be done without.

(Example 942)
FIG. 12B is a diagram illustrating an example MDI program 942 for the tool offsets shown in FIG. 9B. As in FIG. 12A, the tool correction information 1211 of the tool selected on the tool offset screen 1210 used for tool offset has a correction number, a tool radius shape correction value, and a tool radius wear correction value. Then, when a tool offset number is selected on the tool offset screen and the MDI transfer button 1212 is touched, the MDI program generation unit 321 generates a snippet based on the program generation definition of the MDI program linked to the MDI transfer button 1212. Insert 11. Specifically, the snippet 11 is read, and a program is generated for inputting the tool offset and rewriting the tool diameter wear compensation value by the designated value (1224). A 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 to rewrite the tool diameter wear compensation value, P is the compensation number, and R is the compensation value.

As described above, according to this embodiment, the parameter portion described in the fixed form program is automatically replaced with the specific tool information of the tool selected on the tool management screen. It is possible to automatically set and generate an MDI program without key input by . In addition, since the parameter portion described in the fixed form program is automatically replaced with the offset value of the tool selected on the tool offset screen, the offset value of the tool is automatically set without key input by the user and the MDI program can be executed. can be generated.

That is, since the parameter portion described in the snippet is defined by a specific format, the snippet can be easily edited by the user by changing and correcting, and the generation and editing of the MDI program can be realized without mistakes.

By using the technique of this embodiment, it is possible to greatly reduce the time and effort involved in generating an MDI program and the risk of operational errors. In particular, it is effective when a plurality of tools are continuously called to the tool spindle.

[Third embodiment]
Next, a machine tool control device according to a third embodiment of the invention will be described. The machine tool control device according to this embodiment differs from the second embodiment in that snippets generated and edited by the user can be used. In this embodiment, a parameter portion having a specific format is automatically inserted into the fixed form program according to the user's selection instruction on the screen. Since other configurations and operations are similar to those of the second embodiment, the same configurations and operations are denoted by the same reference numerals, and detailed description thereof will be omitted.

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

FIG. 13B shows an example of displaying a pull-down menu 1318 without displaying a plurality of MDI transfer buttons on the tool management screen 210 as in FIG. 13A. For example, when MDI Transfer (User Defined) is selected, a subordinate menu 1319 is displayed.

<Snippet generation and editing procedure>
FIG. 13C is a diagram showing a snippet generation edit screen 1320 of the machine tool controller. In the snippet generation/edit screen 1320, first, in the snippet display screen 1321, the beginning of the first line of the snippet "T (Index to ATC (Automatic Tool Changer) position)" is input. In the snippet generation/editing window 1322 , when “automatic parameter input” is instructed, “?TOOL:” is automatically input in the snippet display screen 1323 . Next, when the “tool number” is specified in the snippet generation/edit window 1324 , “Q0” is automatically entered in the snippet display screen 1325 . Then, in the snippet generation/edit window 1326, when "confirm" is instructed, the input of the first line of the snippet "T?TOOL:Q?" is completed. Note that FIG. 13C shows an example of initial input, but even when reading and editing an existing snippet, input can be easily performed by the same operation.

FIG. 13D shows another snippet generation edit screen 1340 of the machine tool controller. On the snippet generation/editing screen 1340, a snippet is generated or edited for each command of each line. A snippet display screen 1341 and numerical input fields 1342 for each function (G28 function in the figure) are shown. Touching the Insert button 1343 inserts the numerical value in the input field 1342 into the snippet. The snippet creation/editing screen 1340 is used for simple creation/editing of snippets.

<Configuration of tool management module>
FIG. 14 is a block diagram showing the configuration of the MDI transfer module 1420. As shown in FIG. In addition, in FIG. 14, the same reference numerals are given to the same components as those in FIG. 5A, and overlapping explanations are 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 . The MDI transfer module 1420 also includes a database 1410 having a snippet editing data repository 1424 . The snippet acquisition unit 1421 acquires a snippet for editing from the snippet storage unit 323 using 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 in the snippet storage unit 323 in a searchable manner.

(Data storage for snippet editing)
FIG. 15 is a diagram showing the configuration of the snippet editing data storage unit 1424. As shown in FIG. 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 a snippet descriptor 1412 corresponding to the user setting 1511 of whether the input mode of the parameter part is automatic input or manual input. In this embodiment, "? TOOL" is stored for automatic input, and "? MANUALINPUT" is stored for manual input. The format table 1520 stores a format definition 1522 and an input description example 1523 in association with the format number 1521 shown in FIG. 9A. An example input description 1523 is displayed for the user's reference. Input data table 1530 stores parameter identifier 1532 and format number 1533 to be used in association with input data name 1531 . For example, if the input data name 1531 is the tool number, the parameter identifier 1532 stores "Q0". Also, if the input data name 1531 is a tool length compensation shape, the parameter identifier 1532 stores “Q1101”. If the input data name 1531 is a tool radius compensation shape, the parameter identifier 1532 stores "Q1102".

<Procedure for generating and editing snippets>
FIG. 16A is a flowchart showing the procedure of snippet generation and editing processing of the machine tool control device according to the present embodiment. The MDI transfer module 1420 determines whether to generate or edit a snippet in step S1601. For snippet generation, the MDI transfer module 1420 sets a new snippet identifier in step S1611. The MDI transfer module 1420 sequentially inputs the functional description of the snippets in step S1613. MDI transfer module 1420 then determines in step S1615 that an input parameter position has been reached. When the input parameter position has been reached, the MDI transfer module 1420 executes description insertion processing for the parameter portion in step S1617. Then, in step S1619, the MDI transfer module 1420 determines the end of snippet generation. If snippet generation is not finished, the MDI transfer module 1420 returns to step S1613 to continue snippet generation.

On the other hand, for snippet editing, the MDI transfer module 1420 inputs a snippet identifier in step S1621. The MDI transfer module 1420 reads the snippet using the snippet identifier and displays it on the MDI screen in step S1623. The MDI transfer module 1420 then sets which position of the existing snippet to edit in step S1625. MDI transfer module 1420 determines in step S1627 whether the edit position is the parameter partial edit position. If it is at the parameter part edit position, the MDI transfer module 1420 executes parameter part description insertion processing in step S1629. On the other hand, if it is not at 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 end of snippet editing. If editing of the snippet is not finished, the MDI transfer module 1420 returns to step S1625 to continue editing the snippet.

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

(Description insertion processing of the parameter part)
FIG. 16B is a flow chart showing the procedure of the parameter part description insertion processing S1617 and S1629. MDI transfer module 1420 determines in step S1641 whether the input is automatic or manual. If it is 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 "?MANUALINPUT" at the snippet input position in step S1643.

Next, MDI transfer module 1420 determines in step S1647 whether or not the data to be input next is an input value identifier. If it is an input value identifier, MDI transfer module 1420, in step S1649, inputs the input value identifier or makes a selection from a pull-down menu or the like. If it is not an input value identifier, the MDI transfer module 1420 determines whether it is a function identifier in step S1651. If it is a function identifier, the MDI transfer module 1420, in step S1653, inputs the function identifier or makes a selection from a pull-down menu or the like. If it is not a function identifier, do nothing and proceed to the next step. The MDI transfer module 1420 determines in step S1655 whether or not the input of the parameter portion has ended. If the input of the parameter portion is not completed, MDI transfer module 1420 returns to step S1647 and repeats the process until the parameter is completed.

When the input of the parameter part is completed, the MDI transfer module 1420 inserts "?" at the end of the parameter part in step S1647 and ends the process.

According to this embodiment, a snippet can be generated and edited by automatically inserting a parameter portion without key input by the user. Then, an MDI program can be efficiently generated using the user-generated and edited znippets.

[Fourth Embodiment]
Next, a machine tool control device according to a fourth embodiment of the invention will be described. The machine tool control apparatus according to the present embodiment differs from the above-described second and third embodiments in that the generation and editing of the program generation definition are realized with simple operations. In this embodiment, the program generation definition is automatically edited by changing and correcting snippets in the program generation definition according to the user's selection instructions on the screen. Since other configurations and operations are similar to those of the second embodiment, the same configurations and operations are denoted by the same reference numerals, and detailed description thereof will be omitted.

<Program definition generation and editing procedure>
FIG. 17 shows the generation and editing procedure of the program generation definition of the machine tool control device. In the program definition generation and editing screen 1720, first, the program definition display screen 1721 displays the old snippet of the program generation definition. When "change" is instructed in the program definition generation and editing window 1722 and then a new snippet is selected in the program definition generation and editing window 1724, the new snippet is displayed on the program definition display screen 1723. FIG. When "correction" is instructed in the program definition generation and editing window 1722, the content of the program generation definition is updated by correcting the old snippet according to the description of the third embodiment.

<Configuration of tool management module>
FIG. 18 is a block diagram showing the configuration of the MDI transfer module 1820 of the machine tool controller. In FIG. 18, the same reference numerals are given to the same components as in FIGS. 5 and 14, and overlapping descriptions are 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 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. Also, if the program generation definition has not been acquired, a new program generation definition is generated.

<Procedure for generating and editing program definition>
FIG. 19A is a flow chart showing the procedure of program definition generation and editing processing. The MDI transfer module 1820 determines in step S1901 whether to generate or edit a program generation definition. If it is a program generation definition generation, the MDI transfer module 1820 sets a new program generation definition identifier in step S1911. The MDI transfer module 1820 writes the program generation definition in step S1913. Then, in step S1915, the MDI transfer module 1820 determines that the snippet placement position has been reached. When the snippet placement position is reached, the MDI transfer module 1820 executes snippet change processing in step S1817. Then, in step S1919, the MDI transfer module 1820 determines completion of generation of the program generation definition. If the generation of the program generation definition is not finished, the MDI transfer module 1820 returns to step S1913 to continue 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. The MDI transfer module 1820 reads the program generation definition using the program generation definition identifier and displays it on the MDI screen in step S1923. MDI transfer module 1820 then sets which position of the existing program generation definition to edit in step S1925. The MDI transfer module 1820 determines in step S1827 whether the editing position is the snippet editing position. If it is at the snippet edit position, the MDI transfer module 1820 executes snippet change processing in step S1929. On the other hand, if it is not the snippet edit position, the MDI transfer module 1820 corrects the description of the program generation definition in step S1931. Then, in step S1933, the MDI transfer module 1820 determines the end of editing of the program generation definition. If editing of the program generation definition is not finished, the MDI transfer module 1820 returns to step S1925 to continue 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 processing)
FIG. 19B is a flowchart showing the procedure of snippet change processing S1917 and S1929. The MDI transfer module 1820 determines in step S1941 whether or not the snippet has been changed. If it is a snippet change, MDI transfer module 1820 inputs a new snippet identifier in step S1943. MDI transfer module 1820 reads the new snippet to replace the original snippet in step S1945. The MDI transfer module 1820 determines in step S1947 whether to edit the retrieved and replaced snippet. When editing a snippet, snippet editing in the third embodiment is performed.

If the snippet is not changed, MDI transfer module 1820 determines whether to edit the original snippet in step S1949. When editing a snippet, snippet editing in the third embodiment is performed. If none of them is snippet editing, the process is terminated.

According to this embodiment, snippets can be automatically changed and modified to generate and edit program generated definitions without key input by the user.

[Other embodiments]
Although the present invention has been described with reference to the embodiments, the present invention is not limited to the above embodiments. Various changes that can be understood by those skilled in the art can be made to the configuration and details of the present invention within the technical scope of the present invention. Also, any system or apparatus that combines separate features included in each embodiment is included in the technical scope of the present invention.

Further, the present invention may be applied to a system composed of a plurality of devices, or may be applied to a single device. Furthermore, the present invention can also be applied when an information processing program that implements the functions of the embodiments is supplied to a system or 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 a computer, a medium storing the program, a server for downloading the program, and a processor executing the program. . In particular, non-transitory computer readable media storing programs that cause a computer to perform at least the processing steps included in the above-described embodiments fall within the scope of the present invention.

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

In order to achieve the above object, a machine tool control device according to the present invention includes:
a tool management unit that generates and displays a tool management screen that displays a list of tools prepared for the machine tool;
an MDI program generation unit that calls a fixed form program, adds tool information of the tool selected on the tool management screen to the fixed form program, and generates an MDI (Manual Data Input) program;
with
The MDI program generator generates the MDI program by placing an optional stop command between the continuously arranged fixed form programs .

Claims (7)

a tool management unit that generates and displays a tool management screen that displays a list of tools prepared for the machine tool;
an MDI program generation unit that calls a fixed form program, adds tool information of the tool selected on the tool management screen to the fixed form program, and generates an MDI (Manual Data Input) program;
machine tool controller with further comprising a storage unit that stores the fixed form program,
2. The machine tool control device according to claim 1, wherein the MDI program generation unit reads out the fixed form program from the storage unit and generates the MDI program. 3. The machine tool control device according to claim 1, wherein the MDI program generation unit acquires the type of tool information corresponding to the description of the fixed program from the tool management unit, and adds the information to the fixed program. When two or more tools are selected on the tool management screen, the MDI program generation unit adds tool information of the selected tools to each of the fixed programs corresponding to the number of selected tools. 4. The machine tool control device according to any one of claims 1 to 3, wherein the MDI program is generated by arranging the MDI program continuously. 5. The machine tool according to any one of claims 1 to 4, wherein the MDI program generator generates the MDI program by placing an optional stop command between the continuously arranged fixed form programs. Control device. a tool management step of generating and displaying a tool management screen displaying a list of tools prepared for the machine tool;
an MDI program generation step of calling a fixed form program and adding tool information of the tool selected on the tool management screen to the fixed form program to generate an MDI (Manual Data Input) program;
machine tool control method including; a tool management unit that generates and displays a tool offset screen that displays the offset values of the tools prepared for the machine tool;
an MDI program generator that calls a fixed form program, adds the offset value of the tool selected on the tool offset screen to the fixed form program, and generates an MDI (Manual Data Input) program;
machine tool controller with

Images