Institute of Production Engineering 1 ©Niko Siltala, Global Workflow 2006 26.1.2006 Loppukokoonpano...

Institute of Production Engineering 1©Niko Siltala, Global Workflow 2006 26.1.2006

Loppukokoonpano ja pakkaus (IPC-CAMX standardit)

Niko Siltala, Reijo Tuokko, Jose L. Martínez Lastra

Tampere University of Technology / Institute of Production Engineering /Robotics and Automation Laboratory

2©Niko Siltala, Global Workflow 2006 26.1.2006Institute of Production Engineering

Agenda

• Motivation IPC/CAMX• e2Manufacturing project

• Pilot Line Implementation & Process Description

• IPC/CAMX• General• Glance at IPC-254X Standards• IPC-2546 Am2 / Final Assembly & Packaging

• Software Implementation• Conclusions


IPC/CAMX objectives

MessageBroker

MES

QAS

ERP

Monitoring /operator panels


Motivation: IPC / CAMX (Computer Aided Manufacturing using XML) - Standards

IPC-2556

http://webstds.ipc.orghttp://webstds.ipc.org


e2Manufacturing projectPilot Line Implementation & Process Description


e2Manufacturing Project

e2M #1 e2M #2

Time span: 2/2001 – 10/2003 11/2003 – 12/2004

ÄLY

(Former PMJ automec)

Industrial Partners:

http://www.pe.tut.fi/e2manufacturing/


IPC-CAMX FA&P: Working Group

• Development of IPC-2546 / 9 – Final Assembly & Packaging sectional

• IPC Published IPC-2546 am2 on 10.2.200510.2.2005• 33 WG meetings, 54 CAMX conference calls• Distinguished Committee Service Award

to WG/Niko Siltala (Feb 2004, APEX)• Chair: Niko Siltala, TUT/IPE• The Working Group:

+ others:CAMX conference calls

http://www.pe.tut.fi/projects/ipc2546fa/


e2Manufacturing Project: Pilot Environment (model)


e2Manufacturing Project: Pilot Environment

3a

3b

2

1

Process Point

PC

B


IPC & CAMX General


IPC/CAMX General

Institute of Printed Circuits – Association Connecting Electronics Industries. http://www.ipc.org

• United States-based trade association dedicated to furthering the competitive excellence and financial success of its members worldwide, who are participants in the electronic interconnect industry.

• In pursuit of these objectives, IPC will:• devote resources to management improvement and technology enhancement programs, • the creation of relevant standards, • protection of the environment, and • pertinent government relations.

• IPC encourages the active participation of all its members in these activities and commits to full cooperation with all related national and international organizations.

• Membership and Active Participation• International Electronics Manufacturing Initiative (iNEMI)• American National Standards Institute (ANSI)• Underwriters Laboratories (UL)

• Joint Standards Activity• Japan Printed Circuit Association (JPCA)• Wiring and Harness Manufacturers Association (WHMA)• Electronic Industries Alliance (EIA)• Joint Electron Device Engineering Council (JEDEC)


IPC/CAMX Standards

IPC-2556

e2M project focus areas

http://webstds.ipc.org

http://webstds.ipc.org

IPC-2582FD IPC-2583FD IPC-2584FD IPC-2588FD


CAMX Standard Tree

IPC-2518

IPC-2541

IPC-2501

IPC-2551 IPC-2571IPC-2511

IPC-2546 IPC-2547

IPC-2546 Sectional9. Final Assembly &

Packaging

IPC-2546 Sectional1. Screen printing

IPC-2546 Sectional5. Pick&Place

IPC-2554 IPC-2556

IPC-2531 IPC-2581

IPC-2512 … IPC-2518IPC-2512 … IPC-2518IPC-2512 … IPC-2518IPC-2512 … IPC-2578IPC-2576 …

IPC-2554IPC-2554IPC-2554IPC-2554

IPC-2546 Sectional4. Reflow ovens

IPC-2556 Sectional9. Final Assembly &

Packaging


Glance at IPC-254X Standards


IPC-2541 Standard Defines…

Common state model for manufacturing equipment


IPC -2546 Amendment 2


Developed by

Dispensing:

Reflow:

Final Assembly and Packaging:

Other involved:

Published on 10 Feb 2005


IPC-2546 Am2: Content

• Terms & definitions• Abstract model of assembly equipment• List of process specific parameters & subsystems• Data Model for product• Process specific messages & data structures:

• Status of equipment (state model from IPC-2541)• Cautions: alarms, errors, warnings (Ext. IPC-2541)• Equipment information• Product information (incl. Transport, tracing)• Operator

• Sequence diagrams• Implementation guide (examples)


Abstract Model of FA&P Equipment

A,1

A,2 A,3 A,4

A,5

A,2 A,3

A,5

A,4A,3A,2

A,1

Equ.3

Equ.4

Equ.5Equ.1

×

Example 1.Example 1.

A,1Equ.2

Equip B-Lane2

Zone1 Zone2 Zone3

Material Supply Area

Tra

ck

Fee

de

r

Fe

ed

er

Div

isio

n

Container

Component

Section A – A :Side view of TrayFeederTower TrayFeeder

TrayFeederLocationE

qu

ipm

en

tB

Eq

uip

me

nt

A

Equip B-Lane1

Zone1 Zone2 Zone3

Equip A-Lane1

TrayId

TraySection

FeederDivision

Component

A A

EndEffectorStorageEndEffectorStorageLocation

EndEffectorToolStorageEndEffectorToolStorageLocation Manipulator


Abstract Model of FA&P End Effector

EEBase3 EEBase1EEBase2EEBase4

2..n

Component

EndEffectorTool

EndEffectorSegment

EndEffectorStorageLocation

EndEffectorToolStorage

EndEffectorStorage

EndEffectorToolStorageLocation

Manipulator/RobotArm

EEBase3EEBase3

En

d E

ffect

or

EndEffectorToolStorage EndEffectorStorageLocation =

EndEffectorToolStorageLocation =

Legend:Legend:

Example:Example:

EndEffectorTool


Abstract Model of FA&P Equipment

MaterialHandler

EndEffectorMaterialHandler

Container(f rom I temModel )

ContainerPosition

designator

(f ro m I te mMo del )

0..*0..10..1

Component

designator

(from ItemModel)

0..10..10..n0..n

One at a time for a instance of EndEffectorTool

One at a time for a instance of Item

XOR for a single instance

TraySection

Tray

1..n1..n

FeederDivision (for Tray)

1..n1..nFeederDivision

(for Feeder)

TrayLocation

0..10..1

Feeder

1..n1..n

Item (from ItemModel)

<<abstract>>

0..1

0..1

0..1

0..1

0..1

0..1

0..1

0..1

TrayFeeder

1..n1..n

Track

0..n0..n

EndEffectorToolStorageLocation

EndEffectorTool

0..1

0..1

0..1

0..1

0..1

0..1

0..1

0..1

MaterialSupplyArea

0..n0..n

0..n0..n

EndEffectorToolStorage

1..n1..n

EndEffectorStorage

EndEffectorSegment0..10..1 0..10..1

EndEffectorStorageLocation

1..n1..n

FA&P_Equipment

0..n0..n 0..n0..n0..n0..n

EndEffectorBase

1..n1..n

0..10..1

Manipulator

0..n0..n

0..n0..n

0..*

Container

ContainerPosition

designator

0..*0..*

0..10..1

Component

designator

0..10..1

0..*0..*

ItemIdentifier

identifier

BoundBox

Item <<abstract>> 1..*1..*

0..10..1

XOR for single instance

Abstract model of assembled product


e2Manufacturing: Software Implementation


Monitoring applet

SW Architecture

CAMXMsg lib

Data Collectorapplication DB

MonitoringServlet

FLA Adapter JOT AdapterFLA Adapter OPC Adapter

CAMX Message Broker

CAMX Message Broker

SerialSerial OPC DDE

VisualizationSubscribe

Publish

Datamining

StateModel

IPC-2501

Ada

pter

IPC-2501

Monitoring applet

Datamining

StateModel

IPC-2501

Ada

pter

Datamining

StateModel

IPC-2501

Ada

pter

Datamining

StateModel

IPC-2501

Ada

pter

SocketSocketSocketSocket


Message Broker

• Middleware application working like central post office

• Generic interface between clients cf. OPC

• One-to-many• Client needs only one connection point• MSB distributes the message to subscribers

• MSB & Protocol defined in IPC-2501• Implementation used MSB from eX-Mission

CAMX MessageBroker

CAMX MessageBroker

Publish

IPC-2501

http://www.ex-mission.net/


Message Broker

Equipment Equipment

Application Application

Equipment Equipment

Message Exchange


Publisher: IPC Adapter

• Boundary conditions:• Equipment control programs left untouched• Vendor specific legacy interfaces to be used

1. Datamining• Creator of messages (IPC-2541, IPC-2546)• Datamining configuration file: variables, logic rules,

mapping (both creation & parsing)• Cyclically receives copy of controller (PLC)

variables (over TCPI/IP socket)• Trigger conditions are searched (hierarchical)• Dynamic message data is collected from variables

FLA Adapter

Serial

Publish

Datamining

StateModel

IPC-2501

Ada

pter

Datamining

StateModel

IPC-2501

Ada

pter

Socket



2. State Model• Implements IPC-2541 State Model• All sent messages are circulated via module• Equipment state & sub-states maintained

• uses layout info• State changes reported Message(s) generated• User may ignore the State Model in Datamining

FLA Adapter

Serial

Publish

Datamining

StateModel

IPC-2501

Ada

pter

Datamining

StateModel

IPC-2501

Ada

pter

Socket

Blocked

Setup

Down

Starved

Active Executing

Ready

Idle

Processing

43

Off



3. IPC-2501• Communication protocol implementation

with Message Broker• Specified in IPC-2501• Module reused in other parts of the system

4. Equipment Adapter• C++ applications• Internal protocol (XML) for connecting Datamining• Part1: Module for Interface to Datamining

• Common• Part2: Equipment specific part

• Connection to ‘legacy’ interface• Only part needed to change if app.

used with new equipment• Comp. DLL, DDE, OPC, …

FLA Adapter

Serial

Publish

Datamining

StateModel

IPC-2501

Ada

pter

Datamining

StateModel

IPC-2501

Ada

pter

Socket



5. Control• Launcher & integrator of the application• Read & process configuration file

• Application setup (incl. Client & MSB info)• Equipment material flow layout

(lanes-zones, in, out, internal exchange points)• Published, Subscribed & Point-to-Point messages

• Logging (events to: Generic, Error, Msg)• Filtering of unnecessary messages• GUI

FLA Adapter

Serial

Publish

Datamining

StateModel

IPC-2501

Ada

pter

Datamining

StateModel

IPC-2501

Ada

pter

Socket


Subscribers

• Data Collector• Subscribing messages• Processing & summarizing• Storing processed data into DB• Reuses IPC-2501 module

• IPC Adapter (as viewer)• Showed messages from publishing clients• Same application –

different parameter files

Data Collectorapplication DB

Subscribe

IPC-2501


Visualization: Monitoring

• 1..1: Servlet application• Collects requested data from DB• Sends the data into requesting applets

• 1..N: Applets shown on the web browsers

Monitoring appletDBMonitoring

Servlet

Visualization

Monitoring applet


Conclusions


Results & Conclusions

• Applicability of IPC-2546/9 ensured because developed by industrial expert group and feedback from pilot implementation

• Proving suitability of IPC/CAMX messages for assembly

• Environment was set up and functioning• Mechanical integration of line and assembly of case product• FIS Framework build and connected to legacy equipment• Data visualised on-line parallel to the system

• More effective and smoother solution achieved if IPC/CAMX concept considered in design phase of control solution

• Not as separate black box

• Pilot and some industrial solutions have proven the applicability & advantages of IPC-2540 series

• Standard two-way communication still required by production systems


Additional information:

• e2Manufacturing project: http://www.pe.tut.fi/e2manufacturing/

• IPC http://www.ipc.org • IPC Web based solutions

http://webstds.ipc.org • Final Assembly & Packaging Working Group

http://www.pe.tut.fi/projects/ipc2546fa/• Nex-Mission (message broker)

http://www.ex-mission.net/

Thank You!Thank You!

Institute of Production Engineering 1 ©Niko Siltala, Global Workflow 2006 26.1.2006 Loppukokoonpano...

Documents

Transcript of Institute of Production Engineering 1 ©Niko Siltala, Global Workflow 2006 26.1.2006 Loppukokoonpano...