EUROMAP 63 Data Exchange Interface

1 EUROMAP 63 data Exchange InterfaceVersion , 2000(59 pages)The recommendation under this cover has been prepared by theTechnical Commission of EUROMAP and SPI (The Society of thePlastics Industry, USA-Washington, DC)In this document, the American spelling is the an identical text of EUROMAP 63 is published as an SPIdocument. Copyrigth by EUROMAPEUROMAP SPI data Exchange Interface , Page 2 Table of - SPI COMMITTEE ON communication BASED communication (FBC).. PROTOCOL SEVEN LAYER 1, PHYSICAL File Based Communicaton (FBC) Physical 2, data LINK FBC data Link 3, FBC NETWORK FBC Network 4, FBC TRANSPORT FBC Transport 5, SESSION FBC communication Session Request and Response File (stream)

2 Request File Response File Request File Commands and 6, PRESENTATION FBC Presentation data Presentation Request and Response Command Request and Response File Request File Response File Requests and 7, APPLICATION specific command tokens and Response File Log Response File Alarms Event Protocol File Current Machine Alarms Event Protocol File Overall Change Event Protocol File Response File Response File Information File Log Types and AND SPACES AND SPECIAL SESSION Request Flow Replay Flow PRESENTATION CLASS LAYER ERROR REQUEST COMMANDS AND Connection Verification Execute LAYER ERROR SPI data Exchange Interface , Page REQUEST AND RESPONSE Specification Specification Specification Operator Parameter Parameter Specification Specification REQUEST COMMANDS AND Job Request Generation Request Log Request Request Request request request request request IMM DEVICE TOKEN SUMMARY FOR OTHER of Process of Alarm of Process Log for a Status of Alarm Log for a Status a data Set (Example 1).

3 A data Set (Example 2).. Several of Tables and FiguresFigure , File Based , OSI Seven Layer , FBC Physical data , Presentation Layer White-Space , Type Token , Unit Token , Function Token , Miscellaneous Token , Session Request Flow , Session Replay Flow , Error Class , Session Layer Error , Presentation Layer Error , Machine Status , Barrel Temperature , Mould Temperature , Miscellaneous Temperature , Process Monitoring Parameter , Physical Units Used in Injection Moulding SPI data Exchange Interface , Page - SPI Committee on communication ProtocolThe widespread use of microprocessor controls in industrial equipment allows datato be collected and transmitted to central computer systems.

4 Since the mid-eighties, therehave been efforts, largely driven by the automotive industry, to establish computer integratedproduction plants. The aim of these efforts is to increase the transparency of the productionprocesses and thus to obtain information rapidly concerning throughput, quality benefits of networked systems are also important to the plastics industry; thus in1992 the EUROMAP 15 standard for injection molding machine communication wasestablished. Likewise, in 1994, the SPI organization developed standards to encompasssimilar communication systems in the SPI Phase II communication , it has not been possible to establish either protocol widely.

5 Because ofthe rapid developments in computer technology, certain transfer techniques quickly becameobsolete and unacceptably expensive. In addition, the compatibility between the variousmanufacturer s products was many times uncertain. Thus, the implementation and servicingof the existing protocols has led to much expense on the part of machinery manufactures aswell as end joint EUROMAP - SPI Committee on communication Protocol (CCP) wasassigned the task to standardize a protocol for use by plastic machinery manufacturers. Thecommittee was charged to develop a flexible concept, by use of simple communicationstructures, which establishes an economical host computer Interface using standard dataprocessing hardware and software.

6 The committee adopted the following rules to govern thecreation of this protocol: The protocol will be developed using as many existing standards and protocols rule was designed to help save in development time and add credibility to the finalprotocol. Also, it will aid in developer and end user understanding as there are existingbooks and reference documents which describe the various standards and protocols. The protocol shall use existing and readily available technology and shall notinterfere with the normal operations of the processing many of the manufacturers had already developed various equipment withcommunication capabilities. the protocol had to be able to be retrofitted in existingequipment designs.

7 The addition of the communication hardware and software must notimpose any impact on the main operating functionality of the processing equipment. The purpose of the protocol is to provide centralized setup and monitoring of variousplastics processing equipment from a centralized computer system. The protocol shallnot be used for any function necessary for the safe operation of equipment norperform any direct control of central computer would not actually control the equipment, but would allow thecentral computer to set a machine's operating parameters and then monitor it's processdata. No direct control functions or function necessary for the safe operation ofequipment will be provided by the protocol.

8 At no time will any control or safetyfunction of equipment be dependent on the operation of the communication SPI data Exchange Interface , Page Based communication (FBC)In order to satisfy the general requirements adopted by the committee, a File BasedCommunication (FCB) model has been created. This model can be described using thefollowing structure:Figure , File Based CommunicationAs can be seen from the schematic representation, the file based data Exchange interfaceprovides a standard method for different application programs to access information fromvarious machines regardless of manufacturer or type of control systems Interface itself is accomplished using ASCII files.

9 An underlying network file system,whose type and mechanisms are outside the scope of this document, is responsible forproviding access to shared network file servers. Files termed Job Files are created toidentify the information to be communicated with a particular machine. The machine willprocess this job file to both receive information as well as identify information to be writtenby the machine to a Response File . Within these files, commands and response are writtenusing a simple syntax based on ASCII command tokens. For example, a job file for sendinga complete set of machine setup parameters to a machine might have the followingappearance (keywords in capital letters):JOB test RESPONSE = ;// Specification of the data setUPLOAD \\sv1\vol1\ data \test // Use data from data set test START TIME>= 10:05:00;// Start upload at 10:05 This method allows the utilization of sophisticated and complex software applications toaccess machine information by automatically creating job files and processing returnedresponse files as well as the use of a simple text editor to manually create job files and viewreturned response files.

10 Further, this method allows the creation of a complete processmonitoring system using standard data processing (personal computer) components. Forexample, a word processing program can be used to created job request files and aspreadsheet program can be used to analyze the returned machine information. In addition,existing process monitoring systems can be easily adapted to use this file basedcommunication method in place of costly, slow and unreliable direct serial based data Exchange interfaceIMMM anufacturer1 Applicationprogram 1 Applicationprogram 2 Applicationprogram 3 StandardEDP worldIMM worldIMMM anufacturer2 IMMM anufacturernEUROMAP SPI data Exchange Interface , Page OrganizationThe CCP Version manual was organized based on the Open SystemsInterconnection (OSI) 7 Layer Model.