TM2832.Badmark Transport.pdf - 第7页
MDOC-SOFT501 16 7/7 4.3. File Format (for information) Bad mark re sult files are s ent in the fol lowing format. File name Ln … “n” is a lane number XXXXXX … Bar code reading result Data for mat -Board name Board name o…
MDOC-SOFT50116 5/7
4. Others
4.1.
Error messages
These are the error messages displayed only when Rcovery is not activated.
Error No. Messages
Ea12852
Board Name under the selection are different because of the check on the forwarding data of
transport badmark result.
[Cause]
The program name under the selection is different from the program name of the forwarding
data.
[Countermeasure]
･Please correct the data that became a disagreement, and turn it on from the upstream
equipment again.
･ Please invalidate "Program name check" when the check on the program name is
unnecessary. Check the upload path by [Software Setting] - [Basic] - [TakeOver Setting].
Program Name
Board Data
Trans Data
Ea12853
The forwarded number of data and the number of data under selections are different because of the
check on the forwarding data of transport badmark result.
[Cause]
The number of data is different in the substrate data and the forwarding data.
[Countermeasure]
Please correct the data that became a disagreement, and turn it on from the upstream
equipment again.
Board Block Local
Board Data
Trans Data
Ea12854
Data other than having recognized it by checking the forwarding data of transport badmark result
were detected.
[Cause]
The number of data is different in the substrate data and the forwarding data.
[Countermeasure]
Please correct the data that became a disagreement, and turn it on from the upstream
equipment again.
Ea12855
It failed in reading transport badmark result file.
[Cause]
It failed in reading transport badmark result file.
[Countermeasure]
Please confirm the folder set to input information can be read.
Check the upload path by [Software Setting] - [Basic] - [TakeOver Setting].
Ea12856
It failed in writing transport badmark result file.
[Cause]
It failed in writing transport badmark result file.
[Countermeasure]
･Please confirm the folder set to output information can be written.
Check the download path by [Software Setting] - [Basic] - [TakeOver Setting].
･Please do the output control when the output is unnecessary.
Please nullify the check on "XXX" by [Software Setting] - [Basic] - [TakeOver Setting].
File name
MDOC-SOFT50116 6/7
4.2. Initial Setup Items
These are items to be initially specified.
Table 4.1 Initial setting items
Menu Items
[Upper Handling]
Select ”SMEMA” or ”ADVANCED GATE” to receive a
badmark recognition result from the upstream machine.
[Lower Handling]
Select ”SMEMA” or ”ADVANCED GATE” to send a
badmark recognition result to the downstream machine.
Fig 4.4 Instllation Setting
Set [Take Over] to “Enable” or “Enable()”.
Fig 4.5 Machine Data
It is not necessary to set [Data Transfer] in a single stage
machine.
MDOC-SOFT50116 7/7
4.3. File Format (for information)
Bad mark result files are sent in the following format.
File name
Ln … “n” is a lane number
XXXXXX … Bar code reading result
Data format
-Board name
Board name of a selected board
-Bad mark result
Value Status
0 No use
3 Detect bad mark
4 Not detect bad mark
5 Not detect bad mark because board bad mark isn’t found.
Sample data
----------------------------------------------------------------------------
NAME=PCB001 //Board name
3, //Board bad result
3,4, //Block bad result
5,5,5,5,3,4,3,4, //Local bad result
----------------------------------------------------------------------------
Board ID
Lane File name Example
NON Single BadMark_Inf.csv BadMark_Inf.csv
Dual BadMark_Inf_Ln.csv BadMark_Inf_L1.csv
BadMark_Inf_L2.csv
Single BadMark_Inf_XXXXXX.csv BadMark_Inf_SAMPLE.csv SIGNBO
ARD
Dual BadMark_Inf_XXXXXX_Ln.csv BadMark_Inf_SAMPLE_L1.csv
BadMark_Inf_SAMPLE_L2.csv
Single BadMark_Inf_XXXXXX.csv BadMark_Inf_SAMPLE.csv TAKE
OVER
Dual BadMark_Inf_XXXXXX_Ln.csv BadMark_Inf_SAMPLE_L1.csv
BadMark_Inf_SAMPLE_L2.csv