Freeze identities before mapping signals
Name the exact mold revision and every core, slide, unscrewing axis, drive and sensor. A generic 'core pull' line cannot control multiple mechanisms.
G19
MOLD / CORE-PULL INTERFACE
Release every core pull and unscrewing axis as its own controlled interface.
Record the mechanism, motion and position map, drive and working demand, power and connectors, machine/ejector/robot sequence, safety boundary, abnormal recovery and FAT/SAT evidence for each mold axis.
ANSWER FIRST
A “core pull included” line is not an interface release.
The quote must pair each identified mold mechanism with one configured machine or external-drive circuit and one complete cell sequence. Keep unknown load, power, position or recovery states open; do not convert an interface name into a compatibility claim.
Carry the released axis into the cell interface registerCore-interface release gate
- Named mold revision and mechanism/axis
- Motion, position, working demand and action window
- Power circuit, connector, pinout and normal/fault states
- Mold, ejector, robot and part-release sequence
- Safety ownership, recovery and FAT/SAT evidence
MECHANISM FIRST
Do not map every mold movement to one linear core-in/core-out row.
Motion and load define the interface fields. An unscrewing or thread-release axis can require rotation, axial travel and reference behavior that a two-position slide does not describe.
| Mechanism | Motion to define | Demand to confirm | Interface consequence |
|---|---|---|---|
| Linear core pull or slide | Translation between named in-mold and retracted positions, including direction, working stroke, datums and any intermediate state | Required force or load basis through the motion, speed or time window, hold condition and permitted overlap with other movements | Drive type, power circuit, end-position evidence, command/acknowledgement semantics and collision-clear sequence |
| Unscrewing or thread-release axis | Rotation or coupled helical motion with direction, turns or angle, pitch/lead relationship, axial travel and defined thread-release state | Torque and axial-load basis, speed/profile, position or reference method, brake/hold behavior and part or insert constraint | Motor/drive or hydraulic mechanism, reference and position feedback, rotation completion and recovery without treating it as a simple two-position slide |
| Compound or interlocked mold movement | Two or more slides, cams, rotary axes or mold sections with individual identities, collision regions and dependency order | Demand and limits for each axis plus the states that permit or block another core, mold, ejector or robot movement | Per-axis commands and feedback, interlock owner, timeout/fault state and one controlled sequence drawing |
| Passive or mold-actuated core | Mechanical motion created by mold opening/closing, a cam, spring or other mold mechanism rather than a commanded machine axis | Required mold travel, load path, wear/return condition and evidence that the mechanism reaches its defined state | Record it explicitly even when no powered interface exists so the machine, mold-protection and robot sequence do not assume an unavailable signal |
RFQ / INTERFACE REGISTER
Fourteen fields keep each mold axis traceable from drawing to recovery.
Duplicate the register for every mechanism. Do not merge two cores, a slide and a thread-release axis because they share one mold.
| Interface field | Record for each mold mechanism | Evidence to request |
|---|---|---|
| Mold and mechanism identity | Mold number/revision, cavity or station, core/slide/unscrewing-axis ID, component released and drawing owner | Controlled mold assembly, section and mechanism list with matching names on every interface document |
| Motion and position map | Direction, datums, in-mold/retracted/reference/intermediate states, collision envelope and a position diagram | Dimensioned motion drawing or approved kinematic record tied to the current mold revision |
| Mechanism and power type | Linear, rotary, helical, compound or passive mechanism; hydraulic, electric, pneumatic, mold-actuated or other drive | Toolmaker design record plus the proposed machine, drive, valve or external-controller scope |
| Working demand | Required stroke, angle/turns or coupled travel and the traceable force, torque, axial/radial load or hold-demand basis | Toolmaker or responsible engineer calculation, simulation, measurement or representative-trial record with assumptions |
| Action window | Permitted speed/profile or time window, dwell/hold condition, simultaneous movements and the process state that starts and completes the action | Approved sequence chart with conditions and owner; no transfer from another mold or mechanism |
| Hydraulic interface | Required pressure and flow basis, fluid, supply/return/drain arrangement, ports/couplings, hose route, return constraint and heat/leak responsibility | Mold hydraulic schematic and supplier-confirmed configured-machine or external-power-unit circuit and limits |
| Electric, pneumatic or other power | Motor/drive/controller, supply and power basis, brake/reference needs; or pneumatic supply, exhaust and state behavior; plus every external device | Current device data, circuit diagram, option list, protection/isolation scope and approved mating-interface detail |
| Sensors and state semantics | Limit/proximity/encoder or other device, location, target, normal/fault state and exact meaning of in, retracted, referenced, standstill or released | Sensor schedule, mounting drawing and controlled signal/state definition verified on the installed mechanism |
| Connector and pinout | Connector/mating side, cable, pin assignment, signal direction, voltage/current basis, reference potential, shielding, labels and spare contacts | As-built electrical drawing and continuity/pinout check for both endpoints; a named interface alone is insufficient |
| Machine sequence | Core commands and confirmations beside mold close/open, injection/holding/cooling and mold-protection states | Configured cycle sequence with denied-motion, timeout and state-transition checks |
| Ejector and part-release handoff | Which core or thread-release state permits ejection, part release and return, and which evidence confirms each separate state | Linked ejector-interface record; completed core motion alone does not prove acceptable part removal |
| Robot and takeout handoff | Robot position/enable dependencies, entry and exit clearance, insert/part state, reject path and ownership of incomplete handoffs | Exact robot-interface edition/implementation, mapping and cell sequence test with safety signals controlled separately |
| Safety and responsibility boundary | Hazards, guarding/interlocking and energy-control owners across mold, machine, external drive, robot/integrator and destination site | Responsible-party risk assessment and validation records; this worksheet does not design or validate a safety function |
| Abnormal recovery and change control | Loss of power/pressure/signal, blocked or out-of-position mechanism, timeout, trapped part, manual recovery authority, restart state and recheck triggers | Manufacturer-approved recovery instructions, FAT/SAT observations, deviations, closure evidence and as-built revision set |
EVIDENCE SEQUENCE
Move from one mechanism drawing to one as-tested cell record.
This is a procurement evidence sequence, not a mold setup, troubleshooting, maintenance or functional-safety procedure.
Draw motion and collision states
Show in-mold, retracted, reference and intermediate positions, the direction of motion and the regions shared with the mold, ejector, part and robot.
Separate demand from available power
Keep mold-required stroke/rotation and load beside supplier-confirmed hydraulic, electric, pneumatic or external-drive capability for the proposed configuration.
Map commands, confirmations and safety separately
Record the exact connector, pinout and normal/fault semantics. Keep ordinary control or OPC UA data distinct from the responsible safety design and signals.
Build the complete cell sequence
Place each axis beside mold movement, injection, ejector, robot entry/takeout and part release, including denied states, timeouts and abnormal recovery.
Retain FAT, SAT and as-built evidence
Tie the test result to the delivered machine, mold, options, external devices, robot, software and drawings. Reopen affected checks after any change.
FAT / SAT / HANDOVER
An interface is released only inside its tested configuration.
The result stays tied to the identified mold mechanism, machine circuit, external devices, robot, software and test conditions.
| Gate | Evidence to retain | Boundary |
|---|---|---|
| Document match | Mold/mechanism IDs, drawings, machine option list, external drives, connector maps and software/configuration revisions agree. | Document agreement establishes identity, not working compatibility or safe operation. |
| Endpoint and state check | Each command, normal confirmation, fault state, reference state and connector/pin is checked against the installed endpoints. | An electrical state does not prove hydraulic load capacity, mechanical clearance or part release. |
| Sequence FAT | Available normal, denied, timeout, loss-of-signal and restart cases are recorded on the identified machine/mold or approved representative setup. | FAT covers only the test arrangement and does not replace final cell or site acceptance. |
| Installed-cell SAT | The final mold, power circuits, machine, robot, guarding, takeout path and destination conditions are checked under an approved plan. | SAT evidence remains conditional on the stated configuration, conditions and responsible approvals. |
| Recovery and handover | Approved abnormal-state recovery, energy-control boundary, training, as-built files, deviations and revalidation triggers are handed over. | This buyer checklist is not an operating, maintenance, troubleshooting or functional-safety procedure. |
PRIMARY SOURCES / BOUNDARY
Use interface documents and named-OEM examples without transferring capability.
Reviewed 31 July 2026. EUROMAP 13 supplies an electrical connection and position-feedback structure, EUROMAP 74 addresses external electric core drives, and EUROMAP 79 supplies non-safety machine/robot data semantics. ARBURG documents are product-specific catalogue examples only. None proves a NEW ORIENTAL IMM interface, hydraulic or electric capability, safety function, compatibility, option or delivered application.
EUROMAP 13 Version 1.5 — IMM and Core Pullers, Electrical Interface
The official recommendation defines a plug interface for two core pullers, including supply/reference contacts and separate core-in/core-retracted limit or proximity signals; an additional plug is needed for further core pullers under this interface.
Boundary: EUROMAP 13 is an electrical connection and feedback interface. It does not establish hydraulic pressure/flow or force capability, complete safety functions, motion clearance, sequence acceptance or compatibility of any proposed machine and mold.
EUROMAP 74 Version 1.3 — IMM and Electrically Driven Cores
The official recommendation covers the connection to an external servo drive or frequency converter for electrically driven cores and defines movement, ready, reference and optional standstill/shutdown signal concepts.
Boundary: EUROMAP 74 does not turn a rotary or helical thread-release axis into an ordinary linear core pull. The corresponding motion, drive, feedback, collision regions and safety responsibilities still require project definitions and validation.
EUROMAP 79 RC 1.00.06 — IMM-to-Robot Data Exchange
The official page lists position signals for multiple cores and robot enabling signals inside the March 2024 release-candidate data model.
Boundary: EUROMAP 79 data exchange does not replace safety signals; the official page directs safety signals to EUROMAP 81. It also does not prove a physical connector, core drive, mechanical fit or complete cell sequence.
EUROMAP Technical Recommendations Catalogue
The current official catalogue identifies EUROMAP 13 as the electrical interface for injection molding machines and core pullers and lists adjacent mold, robot and electrically driven-core recommendations separately.
Boundary: The catalogue is used to verify recommendation identity and scope. Listing a recommendation is not evidence that any endpoint implements it or that two implementations are compatible.
Multi-Axis Robots — Yaskawa, Powered by ARBURG Technical Data
The official 2026 technical catalogue is a named-OEM example showing that core-pull communication can depend on the selected machine/robot control architecture and option scope.
Boundary: Its equipment, interface and option statements apply only to the identified ARBURG system and document revision. No ARBURG interface, count, robot function or capability is transferred to NEW ORIENTAL IMM.
Rotary Units — Technical Data
The official accessory data is a product-specific example separating hydraulic and electric rotary drives, rotation fields, sequence integration and optional core-pull oil circuits.
Boundary: A platen rotary unit is not automatically a mold unscrewing axis. Its architecture, dimensions and values are not copied into a universal rule or attributed to NEW ORIENTAL IMM.
BUYER QUESTIONS
Core-pull and unscrewing interface FAQ
These answers keep electrical interfaces, working capability, mechanism type, robot data and safety evidence in separate records.
01Is EUROMAP 13 enough to prove that a hydraulic core pull will work?+
No. EUROMAP 13 Version 1.5 defines an electrical plug and position-feedback interface for core pullers. Record hydraulic pressure/flow and return requirements, ports, configured supply capability, working stroke/load, sequence, safety responsibility and acceptance evidence separately.
02Can an unscrewing axis be listed as a normal core-in/core-out circuit?+
Not by default. A thread-release mechanism may need rotational direction, turns or angle, pitch-related axial travel, torque and axial load, a reference method, braking/holding and a defined release state. Preserve the actual mechanism rather than forcing it into a two-position linear-core record.
03Does EUROMAP 79 replace the robot or cell safety interface?+
No. The current EUROMAP 79 page says its OPC UA interface does not exchange safety signals and points to EUROMAP 81. Data nodes and ordinary enabling semantics remain separate from the responsible cell safety design, hardware/signals and validation.
04What should be recorded for each position sensor?+
Record the device and target, physical location, connector/pin, voltage and signal direction, the exact meaning of normal and fault states, and how the installed sequence proves in-mold, retracted, referenced, standstill or another required condition.
05Can the core move while the mold, ejector or robot is moving?+
Only when the identified mechanism, configured cell and responsible engineering review explicitly permit the combined motion and define its collision, load, control and safety conditions. Do not infer simultaneous motion from a catalogue label or another installation.
06What belongs in FAT and SAT for the core-pull interface?+
Use an approved plan covering document identity, endpoints, normal and fault states, permitted and denied sequences, timeouts, loss of power or signal, recovery, part release and robot handoff. Retain the exact test configuration, observations, deviations, approvals and as-built files.
CORE-PULL INTERFACE / NEXT STEP
Send one controlled register for every mold axis.
Attach the mold and mechanism drawings, motion/load basis, power circuits, sensors, connectors and pinouts, complete machine/ejector/robot sequence, safety ownership, abnormal recovery plan, FAT/SAT matrix and open evidence list.
Build the machine brief