JPH0643921A - Control data structure for packaging machine - Google Patents

Abstract

PURPOSE:To decrease man-hours for the generation of packaging data by improving the handling performance of the packaging data among facilities. CONSTITUTION:The packaging data are classified in purposes and functions classifications and unit expression is employed to classify data varying with the facilities and data that the facilities can share; and the handling performance of the data is improved and the data that the facilities can share are effectively utilized to decrease the man-hours of the data generation.

Description

Detailed Description of the Invention

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a control data structure of a mounting machine.

[0002]

2. Description of the Related Art The structure of control data of a conventional mounting machine will be described. As shown in FIG. 8, the control data of the conventional mounting machine is composed of NC data and parts data. N
The structure of the C data is, as shown in (a), following each operation sequential No, an actual data section consisting of a composite code relating to equipment operation and mounting method, mounting position data, and component placement data (called Z number). It is provided. As shown in (b), the structure of the part data is such that, following the part placement data (Z number) to be accessed based on the NC data, the part name, shape dimension data, detailed data of equipment operation, and mounting. An actual data section including detailed data of a construction method, supply data regarding a supply method, and recognition data regarding component recognition is provided.

Further, in order to manage a floppy disk or the like storing these control data and operate it in a host system or a mounting machine, a mechanism such as memo writing and a data management ledger (file) is required.

[0004]

However, when the above data structure is used, there are the following problems.

(1) In NC data, since the actual data portion of each operation sequential record contains information that changes depending on the equipment model such as equipment operation information and mounting method information, the equipment operation created for each board type The compatibility of the NC data, which is the core data of the above, among the facilities cannot be guaranteed.

(2) In parts data, information that can be shared between equipment models, such as shape and dimension data in the actual data part, and equipment-dependent information that changes depending on equipment mechanism and performance, such as equipment operation data, mounting method data, and supply data. Since it is described as a complete unit, the data cannot be shared between the facilities, and it is necessary to recreate the data for each target facility.

(3) When operating the current mounting machine control data in the host system or equipment, a data management file and the like are required in addition to the data, which complicates the system configuration and processing. In addition, when the person in charge manages and operates it, it must be managed by using a memo on a list or a data management ledger. Moreover, the reliability of the management contents cannot be guaranteed due to manual errors such as memos and transcription errors on the ledger.

In view of the above-mentioned conventional problems, it is an object of the present invention to provide a control data structure of a mounting machine that can reduce the number of data creation steps and improve the data handling property.

[0009]

According to the control data structure of a mounting machine of the present invention, in the control data structure for operating the mounting machine, the control data is classified into item units according to purpose and function, and an identification unit is provided for each classification. It is characterized by being described independently as a data unit.

Further, preferably, management information required for data management and system management is incorporated in the control data as a data unit.

[0011]

According to the above-mentioned structure of the present invention, the control data is classified into items according to the purpose and function of each item, thereby making it possible to provide data that can be shared between facilities and facility-dependent data for each item. Since it is possible to separate the data, it is not necessary to create data from scratch for each equipment, and it is possible to reduce the number of data creation steps and improve data handling. Further, by directly writing the management information in the data head part, for example, it becomes easy to manage in data management and system management.

[0012]

DESCRIPTION OF THE PREFERRED EMBODIMENTS A control data structure of a mounting machine according to an embodiment of the present invention will be described below with reference to FIGS.

FIG. 1 shows a data structure in which the control data of the mounting machine is grouped by purpose and function and its data items. That is, each data item is broadly classified into five types according to purpose and function. That is, (a) an NC program that indicates design conditions such as which component is mounted at which position on the board and at which angle, and (b) an array program that indicates which component is installed at which component supply position of the mounting machine. When,
(C) A parts library that aggregates component information such as the dimensions and shape of each mounted component, mounting conditions, (d) a supply library that indicates the information of the component supply means itself, and (e) information of the board recognition mark It has been grouped with Mark Library. Of these data items (a),
(B) is data input for each board type, and (c)
After inputting all the parts set in each mounting machine, it is almost fixed data in that mounting machine,
(D) and (e) are almost fixed data across facilities. Further, at the head of each data, there is provided a header part describing management information of the data.

Furthermore, the internal representation in each of the above-mentioned data is also described as a data unit for each function to distinguish between equipment dependence and equipment dependence, thus realizing a general-purpose data structure.

The detailed structure of each data will be described below with reference to FIGS.

First, the data structure of the header part common to each data will be described with reference to FIG. 2, with "%" prefixed with "%" as an ID part indicating the header part.
“R” is described, followed by information necessary for the administrator to manage and operate, and the main items are the program name, model name indicating the target mounting machine name, machine name, creation Date, modification date, link data name indicating related data, designation of coordinate system, etc. are described.

As shown in FIG. 3, the data structure of the NC program has an "ID" portion indicating that it is NC data.
% "Is added to the beginning of the description, followed by actual data for each sequential NO. As actual data, mounting position data, mounting attitude data, and component placement data (Z No.), part name, and N
A circuit number for visually confirming C data on the board and data such as production conditions are described. All of these data are data that do not change depending on the type of equipment.

As shown in FIG. 4, the data structure of the array program is described as "% SETUP" by prefixing "%" as an ID portion indicating that it is the component array data, and subsequently, the part placement NO. ． Actual data is described for each (Z number). As the actual data, a shape code for identifying a part based on its shape, a part name, and spare position data indicating a disposition position of a spare part are described. These data are data that do not change depending on the type of equipment.

As shown in FIG. 5, the data structure of the parts library is described as "% PARTS" by prefixing "%" for each part as an ID part indicating that it is part data. A shape code for accessing the data of a desired part is described based on the array program, and then each data is described for each item described by adding "&" at the beginning. As data items, "& SIZ
"E", MC's basic data (equipment-independent data) that describes the basic dimensions and catalog information of the parts described after "E"
Machine operation condition data (equipment dependent data) indicating the operating conditions of the mounting machine for the target component described after "MOVE", and mounting condition data section (equipment dependent data) indicating the mounting method for the target component described after "&MNTCND". ), Supply condition data (equipment-independent data) indicating the supply condition determined by the target component described after "&SUPPLY", and component recognition data indicating optical information for recognizing the target component described after "&RECOG" ( Data is composed of a plurality of units separated by "&" from the ID part beginning with "%" in this way, and the equipment-dependent data and the equipment-independent data are classified. It is written so that they are not distinguished and mixed.

The data structure of the supply library is, as shown in FIG. 6, an ID portion indicating supply data.
"% SUPPLY" is described with "%" at the head, the supply form name is described after that, and the supply form data is described following the item display of "&SUPPLY" with "&" at the beginning. .

As shown in FIG. 7, the data structure of the mark library is described as "% MARK" by prefixing "%" with "%" as an ID part indicating that the mark data is for board recognition. The mark type is described, followed by the item display of "&MARK" with "&" at the beginning, followed by the mark shape characteristics, and then "&RECOG".
The recognition data is described subsequent to the item display.

As described above, since the control data is classified by item according to the purpose and function of each, and is divided into data that can be shared between facilities and data that depends on the facility,
Data that can be shared between facilities does not have to be created from scratch, which facilitates data creation and improves data handling.

[0023]

As described above, according to the present invention, by classifying the control data item by item according to the purpose and function of each item, data that can be shared between facilities and facility dependent data for each item The data handling property between the facilities can be improved and the man-hour for data creation can be reduced. Further, by describing data management information necessary for management and operation inside the data, reliability of information and easy management can be achieved.

[Brief description of drawings]

FIG. 1 is an explanatory diagram of an overall structure of mounting data according to an embodiment of the present invention.

FIG. 2 is an explanatory diagram of a data structure of a header section in the embodiment.

FIG. 3 is an explanatory diagram of a data structure of an NC program in the embodiment.

FIG. 4 is an explanatory diagram of a data structure of an array program in the same embodiment.

FIG. 5 is an explanatory diagram of a data structure of a parts library in the embodiment.

FIG. 6 is an explanatory diagram of a data structure of a supply library in the embodiment.

FIG. 7 is an explanatory diagram of a data structure of a mark library in the embodiment.

FIG. 8 is an explanatory diagram of a mounting data structure in a conventional example.

Claims (2)

[Claims] 1. In a control data structure for operating a mounting machine, control data is classified by item and purpose according to function,
A control data structure of a mounting machine, which is described as an independent data unit by providing an identification section for each classification. 2. The control data structure of the mounting machine according to claim 1, wherein management information required for data management and system management is incorporated as a data unit in the control data.