Is EUROMAP 63 obsolete?

It is superseded by EUROMAP 77 but not out of service: an injection moulding machine lasts decades and the installed base still offers EUROMAP 63 as its only interface. In practice it is integrated as is and normalised in an intermediate layer.

Can EUROMAP 63 be moved to OPC-UA without replacing the machine?

Yes. An intermediate device can act as the EUROMAP 63 host, read the files from the shared directory and publish the result as an OPC-UA server shaped like EUROMAP 77. The machine is untouched and the MES sees one interface across the whole fleet.

Why do two EUROMAP 63 machines not deliver the same data?

Because the recommendation fixes a base parameter set and leaves vendor extensions open. Each control adds its own variables and naming, so equivalence across brands has to be established explicitly in the mapping, machine by machine.

What latency does EUROMAP 63 have?

The machine cycle sets it, not the network: the moulding machine answers once the current cycle ends, so the collector timeout must exceed the cycle time. It suits per-shot data, counters and alarms, not sub-second supervision.

What is EUROMAP 63: definition and uses

EUROMAP 63 is the recommendation defining data exchange between plastic injection moulding machines and production management systems through ASCII files placed in a shared directory. Published in 2000, it covers cycle data, counters, alarms and job data transfer, and remains the interface on a large share of the installed machine base.

Where EUROMAP 63 shows up on the plant floor

EUROMAP is the European association of plastics and rubber machinery manufacturers, and its recommendations are the sector’s common language. EUROMAP 63 turns up in any injection moulding shop running machines from the last two decades: packaging, automotive components, housewares, toys and technical plastics, particularly dense in the Valencian industrial fabric. The mechanism is deliberately simple. Machine and host share a directory; the host writes a session request file with a .REQ extension, the machine detects it, processes it, writes the session response under the same base name with a .RSP extension, and leaves the requested data in .DAT files. A request counts as complete once the .REQ file is gone and the expected response files exist. On top of that mechanism the host requests cyclic reports per shot or per interval, machine state, alarms and job data, and can also preset a job on the machine.

EUROMAP 63 versus EUROMAP 77

The usual confusion is treating them as versions of one protocol, which they are not: they are two different technologies serving the same purpose. EUROMAP 77 is an OPC-UA companion specification: data are typed nodes in an address space, the MES subscribes and gets notified as each cycle closes, and security (certificates, encryption, user authentication) comes from OPC-UA itself. EUROMAP 63 is a file exchange: the host polls a directory, there is no subscription, there is no encryption or authentication beyond the share permissions, and the parameter list is an agreed table rather than an information model with types and relationships. A second, more practical difference matters even more than the technical one: the recommendation defines a base parameter set, but each manufacturer adds its own, so two machines both claiming EUROMAP 63 rarely deliver the same names or the same detail.

Getting EUROMAP 63 data into a data layer

The first constraint is latency, and it comes from the machine rather than the network: the moulding machine answers a request once the current cycle finishes, so the collector timeout has to exceed the cycle time. With cycles of tens of seconds, an aggressive timeout produces failures that look like communication faults and are not. This puts EUROMAP 63 at the natural granularity of injection moulding, the shot, and rules it out as a control or sub-second monitoring channel.

The second is transport. The shared directory is usually published over SMB from the machine control PC, which on older equipment runs Windows and SMB versions that current operating systems no longer enable by default. That detail, prior to any data architecture discussion, is what most often blocks an injection moulding integration. The alternative is mounting the share from an intermediate machine in the plant segment, acting as the single client and republishing northbound. The third is hygiene of the directory itself: every request and every report leaves files behind, and if the collector does not consume and delete them, the folder grows until it degrades the machine’s own performance.

Reading requires no line stop and no change to the process: enabling the interface is a control configuration option, sometimes licensed, and the share is mounted from outside. Permissions do deserve separation, since the same channel that reads reports can preset jobs on the machine. The real work is not reading the files but normalising them: translating each manufacturer’s vocabulary into a single model, stamping the shot against a common clock and publishing once northbound, so the MES never has to know each brand’s quirks. That translation layer across standards and brands is the subject of industrial interoperability.

EUROMAP 63 feeds the MES and the OEE calculation of an injection moulding plant. Its successor is EUROMAP 77, built on OPC-UA, and coexistence of both across a mixed fleet is normally handled with an industrial gateway that unifies the model before handing it to business systems.

What is EUROMAP 63