LomaLink User s Guide

LomaLink User s Guide The Serial Communications System for Loma Inspection Equipment Loma Part Number: 811153 Spectrum Inspection Systems Issue: K Southwood Date: July 2007 Farnborough Hampshire GU14 0NY Tel: (01252) 893300 Fax: (01252) 893410 1999-2007 Spectrum Inspection Systems. All rights reserved. Information included in this document is subject to change without notice. No part of this document may be reproduced or transmitted in any form or by any means, electronic or mechanical, for any purpose, without the express written permission of Spectrum Inspection Systems. Page 1 of 32

CONTENTS 1. INTRODUCTION...3 2. LOMA SERIAL INTERFACE...3 3. PHYSICAL LAYER...4 3.1 DEFINITION...4 3.2 REQUIREMENT...4 4. DATA LINK LAYER...5 4.1 DEFINITION...5 4.2 REQUIREMENT...5 5. APPLICATION LAYER...9 5.1 DEFINITION...9 5.2 REQUIREMENT...9 6. LOMALINK DETAILS...13 6.1 COMMANDS, type no 0...13 6.2 REQUESTS, type no 1...16 6.3 CHANGES, type no 2...19 7. MESSAGE CONTENTS...21 7.1 DEFINITION OF TERMS...21 7.2 Production Data Message (READ ONLY)...22 7.3 Product Details Message...24 7.4 Product Setup Status Message...26 7.5 Metal Contaminants log (READ ONLY)...27 7.6 Extra Product Details Message...28 7.7 PV Test Details (READ ONLY)...30 APPENDIX A...32 RETURN CODES...32 Page 2 of 32

1. INTRODUCTION This document is intended to specify the requirements of the standard LomaLink. This is a feature that enables : data to be requested from Loma equipment. data to be sent to Loma equipment. remote control of Loma equipment. (Although not all of these are available on all Loma equipment) All of which can be done using a remote PC, PLC, Terminal or Factory Computer. The document provides sufficient information for a programmer to successfully interface computer equipment to Loma devices. 2. LOMA SERIAL INTERFACE The serial interface will be based on a three-layer master-slave system, where the Loma equipment will always be the slave. The three layer structure comprises:- Physical Layer. Data Link Layer. Application Layer. Each of these areas will be considered in turn - starting with the Physical layer. Page 3 of 32

3. PHYSICAL LAYER 3.1 DEFINITION The physical layer is the hardware and software connection between the two devices which wish to communicate. 3.2 REQUIREMENT In this case it will be implemented using a three wire RS232 serial connection, comprising Tx, Rx and Signal Gnd. (Please note that RS 422 and 20 Ma loop are also available). One implication of this is that there will be no hardware handshaking provided by Loma equipment. The following options are available and can be set up via the serial link menu as for any other serial option (refer to the manual supplied with your equipment for full details of the set up procedure) BAUD RATE - 9600. DATA BITS - 8. STOP BITS - 1. PARITY XON/XOFF - NONE. - OFF. Note: with RS232 one start bit is implied. Page 4 of 32

4. DATA LINK LAYER 4.1 DEFINITION The data link layer establishes an error free point to point communications path between two systems connected on the physical layer and adds the data link layer protocol to the data packages for transmission. The data link layer checks the integrity of received messages and the health of the physical layer indicating all problems to the application layer. 4.2 REQUIREMENT To implement the data link layer a Loma protocol will be used which will be a simple send-andwait ARQ (automatic repeat request) type. The layout of the Loma data packet is shown below, and explained in the flow diagram at the end of this section. All fields except the <info...> field are one byte in length. where: <STX><info...><ETX><CHECKSUM> <STX> - ASCII start of text character (02 hex). <info...> - the message. Note: the message fields are separated with the control character <US> <ETX> - ASCII end of text character (03 hex). <CHECKSUM> - Twos complement of the 8 bit sum of the message (NOTE: the sum does not include the start of text or end of text characters). Note that a checksum of 00 hex is not permissible. If the checksum of the data equals 00 hex, then 1 should be added to make it 01 hex. e.g. If the message characters were <STX><3>< ><0><0><T><E><S><T><US><ETX><CHKSUM>, the ASCII values in HEX would be: 02,33,20,30,30,54,45,53,54,1F,03,<CHKSUM>. The sum of all the characters excluding the STX and ETX i.e. 33+20+30+30+54+45+53+54+1F = 212H. As only the least 8 bits of the sum are used, the checksum is the two s complement of 12H or binary 00010010 i.e. 11101101 + 1 = 11101110 or 0EEH. As with all serial protocols there are two distinct modes of operation - receiving and transmitting. These will be specified separately. 4.2.1 RECEIVING 1. Wait for a period specified by the application layer (forever in the case of slave Loma equipment) for an STX character dumping all other characters that are received. 2. Once STX has been received put all subsequent characters into a buffer until ETX is received. 3. When ETX is received wait for the checksum byte. 4. Calculate the twos complement checksum (in 8 bits) of the data received and compare this with the checksum received. (Note that if the calculated checksum of the data is 00 hex, a 1 should be added before comparison). Page 5 of 32

5. If the checksums match, transmit the ASCII ACK character. Reception is complete. 6. If the checksums did not match, transmit the ASCII NAK character. Reception is complete. 4.2.2 TRANSMITTING 1. Format the data into a Loma message packet and transmit it. 2. Wait for a time out of 2 seconds to receive an ACK character. 3. If an ACK is received in time then transmission is complete. 4. If a NAK character is received the time out will be reset and the message will be re-transmitted until three NAK characters have been received. At this point the data link layer will signal the application layer with the message LINK CORRUPTION. 5. If any other character is received it will be dumped but the time out will be reset. 6. If no characters are received in the 2 seconds allowed, then the message will be re-transmitted until three time-outs have occurred at which point the data link layer will signal the application layer with the message LINK FAILED. Page 6 of 32

'WAIT FOREVER FOR AN ERROR FREE MESSAGE' FLOW DIAGRAM Start Wait forever for a byte Is byte STX? NO TIMEOUT YES Wait with timeout for a byte BYTE Is byte ETX? NO Store byte in Buffer YES NO Have there been too many timeouts? TIMEOUT Wait with timeout for Checksum byte BYTE YES Log problem in Fault Log Calculate Buffer Checksum Do Checksums match? YES Transmit ACK byte Pass Buffer to Application Layer NO END Transmit NAK byte Page 7 of 32

'TRANSMIT RESPONSE' FLOW DIAGRAM Start Transmit STX byte. Transmit byte from Buffer Is Buffer empty? NO YES Transmit ETX byte Calculate Checksum and Transmit NO NO Have there been too many timeouts? TIMEOUT What was Response? NAK Have there been too many NAKs? YES Log problem in Fault Log ACK YES Log problem in Fault Log END Page 8 of 32

5. APPLICATION LAYER 5.1 DEFINITION The application layer is the interface between the system software and the data link layer. It is responsible for creating the messages to transmit, for interpreting the messages received and handling any error conditions indicated by the data link layer. 5.2 REQUIREMENT The Loma application layer is implemented as a slave. This means that the Loma application layer will only create and transmit a message in response to an error free message being received from the data link layer, and that it will instruct the data link layer to wait forever for a message. This should not be allowed to happen on the master. The Loma application layer will recognise three types of message and transmit one of two types in response. The format of these messages is as follows: 5.2.1 Messages RECEIVED by the Loma device: <msg type> <command no> <product no> COMMANDS 0 00-FF 000-FFF <msg type> <data set no> <product no> REQUESTS 1 00-FF 000-FFF <msg type> <data set no> <product no> <data set info...> CHANGES 2 00-FF 000-FFF 5.2.2 Messages TRANSMITTED by the Loma device: <msg type> <data set no> DATA 3 00-FF 0-F <msg type> <data set no> <result> <data set info...> <result> or <command no> CONFIRM 4 00-FF 0-F Note that all message types, data set/command numbers and product numbers that are transmitted to and from the Loma device are in "ASCII HEX". For example, product number ten is denoted as 00A Hex. However, all information transferred is in straight ASCII for ease of understanding. Refer to the Appendices for more information. The Loma application layer is designed to be robust in plant conditions, whilst being kept as simple as possible. However, it may be helpful to read the following description in association with the flow diagram at the end of this section. 1. Wait forever for a message from the link layer. 2. On receipt of a message from the link layer the first two fields will be checked to make sure they are valid. 3. If the msg type field is not valid, INVALID MSG TYPE will be logged in the service log and the application layer will return to step 1 without sending a response. Page 9 of 32

5.2.1 COMMANDS 4. If message type is a command and the command no. is valid it will be executed and the response checked to see if it has been successful. 5. If the command was not valid, UNKNOWN COMMAND No. will be logged in the service log and a confirm message for this command will be transmitted, with the result field set to 7 (indicating UNKNOWN COMMAND No.). 6. If the actioning of the command failed, a confirm message for this command will be transmitted with the result field set to 9 (indicating COMMAND FAILED - application specific). 7. If the command succeeded a confirm message for this command will be transmitted with the result field set to zero indicating success. 5.2.2 REQUESTS 8. If message type is a request and the requested data set no. is valid then the data will be collected into a buffer, formatted, and the system response checked to see if it has been successful. 9. If the requested data set no. is not valid, UNKNOWN DATA SET will be logged in the service log. A data message for this request will be transmitted with the result field set to 8 (indicating UNKNOWN DATA SET). 10. If the actioning of the request failed, a data message for this request will be transmitted with the result field set to 0xA (indicating REQUEST FAILED - application specific) and no data present. 11. If the requested data set is valid a data message will be transmitted for this data set with the result field set to zero indicating success. 5.2.3 CHANGES 12. If the message type is a change, and the data set no. to be changed is valid, the data will be copied to memory and the system response checked to see if it has been successful. 13. If the Data Set change is not valid, UNKNOWN DATA SET will be logged in the service log, and a confirm message for this change will be transmitted with the result field set to 8 (indicating UNKNOWN DATA SET). 14. If the change failed, a confirm message for this change will be transmitted with the result field set to 11 (indicating CHANGE FAILED - application specific). 15. If the change succeeded a confirm message for this change will be transmitted with the result field set to zero indicating success. 16. In all cases where a response message is required it will be passed to the data link layer for transmission. 17. If the data link layer returns LINK CORRUPTED, then the system fault LINK CORRUPTED is logged and the application layer returns to step 1. Page 10 of 32

5.2.3 CHANGES 18. If the data link layer returns LINK FAILED, then the system fault LINK FAILED will be logged and the application layer returns to step 1. 19. If the data link layer returns HEALTHY, transmission is complete and the application layer returns to step 1. Page 11 of 32

APPLICATION LAYER FLOW DIAGRAM Start Wait forever for a error free Message? YES Is Message Type OK? NO Put entry into Service Log YES COMMAND What is Message Type? CHANGE REQUEST Is Command valid? NO Is Request valid? NO Is Change valid? NO YES YES YES Did Command succeed? NO Did Request succeed? NO Did Change succeed? NO YES YES YES Load Result with 0 = OK Load Result with Prob No. Log Problem Transmit Response YES Was Response OK? NO Log Response Problem in Fault Log. 'WAIT FOREVER FOR AN ERROR FREE MESSAGE' & 'TRANSMIT RESPONSE' are explained in detail within the Data Link Layer Section earlier in this manual. Page 12 of 32

6. LOMALINK DETAILS LomaLink consists of a number of commands, requests and changes. As described earlier in this document, the Loma equipment is a slave to a remote device, which is considered the master. Once enabled therefore the Loma system will not send anything asynchronously (i.e. without waiting for a stimulus). Remote control cannot be used with the ISC, Tracker, PVS and Reject Confirmation features. 6.1 COMMANDS, type no 0 The following table details the COMMANDS that are available. No Name Action resulting from COMMAND 00 ASK FOR REMOTE CONTROL (Only available on the ISC, IQ, IQ2, IQ3, Two Line 6000, Two Line 7000 Integrated Combo & AS Series Checkweighers) If the machine is not under REMOTE CONTROL then put the machine into REMOTE CONTROL mode and display an "Under Remote Control" message on the User Interface. If machine is already under REMOTE CONTROL no action is taken. Time delay of at least 100 msec before sending further messages. NOTE: Once REMOTE CONTROL is taken, the Loma Device expects to see a message (command, request or change) every 15 seconds to indicate the hosts wish to retain REMOTE CONTROL. It is recommended that the host sends a message every 10 seconds. If the host does not need to send a particular message at the required time then it is recommended that the ASK FOR REMOTE CONTROL command be sent. 01 RELINQUISH REMOTE CONTROL (Only available on the ISC, IQ, IQ2, IQ3, Two Line 6000, Two Line 7000 Integrated Combo & AS Series Checkweighers) 02 ENTER RUN (Only available on the ISC, IQ, IQ2, IQ3, Two Line 6000, Two Line 7000 Integrated Combo & AS Series Checkweighers) 03 EXIT RUN (Only available on the ISC, IQ, IQ2, IQ3, Two Line 6000, Two Line 7000 Integrated Combo & AS Series Checkweighers) If the machine does not receive a message after 15 seconds since the last message it will return to LOCAL CONTROL. If the machine is under REMOTE CONTROL, it will return to LOCAL CONTROL and the display will be restored to its previous state. If the machine is already under LOCAL CONTROL no action is taken. If the machine is not in run mode, enter run, print necessary reports and set the display to the run menu. If the system is unable to go into run load the result field with a flag indicating why (see Appendix A). If the machine is in run mode, exit run, print necessary reports and set display to 'main' menu. If the system is not in run, no action is taken but the CONFIRM message result field is loaded with the COMMAND FAILED return code. The product number field in this COMMAND has no effect and should be set to ZERO. Page 13 of 32

04 PRINT SETPOINTS 05 PRINT BATCH 06 PRINT SHIFT 07 PRINT TOTALS 08 PRINT CONFIGURATION Print SETPOINTS report if printer fitted. The product number field in this COMMAND has no effect and should be set to ZERO. Print BATCH report if printer fitted. The product number field in this COMMAND has no effect and should be set to ZERO. Print SHIFT report if printer fitted. The product number field in this COMMAND has no effect and should be set to ZERO. Print TOTALS report if printer fitted. The product number field in this COMMAND has no effect and should be set to ZERO. Print CONFIGURATION report if printer fitted. The product number field in this COMMAND has no effect and should be set to ZERO. Note: It is necessary to ASK FOR REMOTE CONTROL in order to action Commands. 6.1.1. Command Sequence Example: Assuming that the Loma Device is not already under Remote Control, an example of a command sequence to ENTER RUN FOR PRODUCT no 7 would be as follows: Step 1, Ask For Remote Control : Transmit to Loma device: <STX> <0> <00> <000> <ETX> <CHKSUM> Message Type Product Number (0 = Command) (n/a) (00 = Ask for Remote Control) If all is well receive from Loma device an ACK and the following message: <STX> <4> < 0> <0> <ETX> <CHKSUM> Message Type Result (4 = Confirm) (0=OK) Command No (00 = Ask for Remote Control) denotes space character (20 Hex) Page 14 of 32

Step 2, Enter Run for product 7 : Transmit to Loma device: <STX> <0> <02> <007> <ETX> <CHKSUM> Message Type Product Number (0 = Command) (no 7) Command No (02 = Enter Run) If all is well receive from Loma device an ACK and the following message: <STX> <4> < 2> <0> <ETX> <CHKSUM> Message Type Result (4 = Confirm) (0 = OK) Command No (02 = Enter Run) Step 3, Relinquish Remote Control : Transmit to Loma device: <STX> <0> <01> <000> <ETX> <CHKSUM> Message Type Product Number (0 = Command) (n/a) Command No (01 = Relinquish Remote Control) If all is well receive from Loma device an ACK and the following message: <STX> <4> < 1> <0> <ETX> <CHKSUM> Message Type Result (4 = Confirm) (0 = OK) Command No (01 = Relinquish Remote Control) denotes space character (20 Hex) Page 15 of 32

6.2 REQUESTS, type no 1 The following table details the REQUESTS that can be made. No Name Action resulting from REQUEST 00 PRODUCTION DATA (Available on ISC, IQ, IQ2, IQ3, 6000, 7000, As Series) Snap shot the production data and transmit it with the following format: <(f1) US (f2) US...(f50) US> where US is the ASCII unit separator (1F hex) and fields f1 to f50 are defined in Section 7. Note that the data that is transmitted as a result of this request, will only include data for production since the previous request. The data must be accumulated at the computer. Data is only transmitted for the product that is currently being run. The product number field in this request has no effect, and should be set to 0. 01 PRODUCT DETAILS (Available on ISC, IQ, IQ2, IQ3, 6000, 7000, AS Series) 02 PRODUCT SETUP STATUS (Available on ISC, IQ, IQ2, IQ3, 6000, 7000, AS Series) 03 ERROR LOG (Available on IQ2 and IQ3) This message should not be requested more rapidly than once every 600 ms. Snap shot the product details for the specified product and transmit it with the following format:- <(f1) US (f2) US...(f31) US> where US is the ASCII unit separator (1F hex) and fields f1 to f31 are defined in section 7. On 6000 or 7000 OPUS systems weights are sent in g only and lengths in mm only. Snap shot the product setup status for the product specified and transmit it with the following format:- <(f1) US (f2) US...(f20) US> where US is the ASCII unit separator (1F hex) and fields f1 to f20 are defined in section 7. Snap shot the error log and transmit it with the following format:-<(f1) US (f2) US...(fn) US> where US is the ASCII unit separator (1F hex) and fields f1 to fn are defined in section 7. (fn - the number of fields will vary dependant upon the number of entries in the log) The product number field in this request has no effect, and should be set to 0. 04 FAULT LOG (Available on IQ2 and IQ3) Snap shot the fault log and transmit it with the following format:-<(f1) US (f2) US...(fn) US> where US is the ASCII unit separator (1F hex) and fields f1 to fn are defined in section 7. (fn - the number of fields will vary dependant upon the number of entries in the log) The product number field in this request has no effect, and should be set to 0. Page 16 of 32

05 CONTAM LOG (Available on IQ2 and IQ3) Snap shot the contaminant log and transmit it with the following format:-<(f1) US (f2) US...(fn) US> where US is the ASCII unit separator (1F hex) and fields f1 to fn are defined in section 7. (fn - the number of fields will vary dependant upon the number of entries in the log) The product number field in this request has no effect, and should be set to 0. 06 FAILSAFE LOG Snap shot the failsafe log and transmit it with the following format:-<(f1) US (f2) US...(fn) US> where US is the ASCII unit separator (1F hex) and fields f1 to fn are defined in section 7. (fn - the number of fields will vary dependant upon the number of entries in the log) The product number field in this request has no effect, and should be set to 0. 07 EXTRA PRODUCT DETAILS (Available on ISC, IQ, IQ2,IQ3, 6000, 7000, AS Series) 08 GENERAL SYSTEM DETAILS 09 SYSTEM SENSOR DETAILS (not currently available) 10 SYSTEM SETUP STATUS (not currently available) 11 PV TEST DETAILS (Available on IQ2 and IQ3) Snap shot the extra product details for the specified product and transmit them with the following format:-<(f1) US (f2) US...(f34) US> where US is the ASCII unit separator (1F hex) and the fields f1 to f35 are defined in section 7. The system checks whether any PV Tests have been performed. If they have then the system checks whether there are any PV Test data sets that have previously not been transmitted. If so then the system transmits the oldest data set with the following format: - <(f1) US (f2) US...(f20) US> where US is the ASCI unit separator (1F hex) and fields f1 to f20 are defined in section 7.4. If there have not been any PV Tests performed then an error message is transmitted. If there have been PV Tests performed but the associated test data has been previously transmitted then an error message is transmitted. The product number field in this request has no effect and it should be set to 0. Page 17 of 32

12 OPC GENERAL DETAILS (Available on IQ2 and IQ3) Snap shot the production data and transmit it with the following format: <(f1) US (f2) US...(f50) US> where US is the ASCII unit separator (1F hex) and fields f1 to f26 are defined in Section 7 Data is only transmitted for the product that is currently being run. The product number field in this request has no effect, and should be set to 0. This message should not be requested more rapidly than once every 600 ms. Note: It is not necessary to ASK FOR REMOTE CONTROL in order to carry out Requests. 6.2.1. Request Sequence Example: An example of a request sequence for PRODUCTION DATA follows:- Transmit to Loma device: <STX> <1> <00> <000> <ETX> <CHKSUM> Message Type Product Number (1 = Request) (n/a for Production Data) Data Set No (00 = Production Data) If all is well receive from Loma device an ACK and the following message: <STX> <3> < 0> <0> <INFO> <ETX><CHKSUM> Message Type Result (3 = Data) (0=OK) Data Set No Production Data (00 = Production Data) (as Section 7) denotes space character (20 Hex) Page 18 of 32

6.3 CHANGES, type no 2 The following table details the CHANGES that can be made. No Name Action resulting from CHANGE 00 UPDATE PRODUCT DETAILS (Only currently available on Two Line 6000 & 7000 Integrated Combo, AS Series) 01 UPDATE PRODUCT SETUP STATUS Extract the data contained in the message in the following format:- <(f1) US (f2) US...(f31) US> where US is the ASCII unit separator (1F hex) and fields f1 to f31 are defined in section 7. Overwrite the product details for the selected product with extracted data, and update any checksums accordingly. This message cannot be used to overwrite the currently running product (Command Failed will occur is this attempted) Extract the data contained in the message in the following format:- <(f1) US (f2) US...(f20) US> where US is the ASCII unit separator (1F hex) and fields f1 to f20 are defined in section 7. Overwrite the product setup status for the selected product with extracted data, and update any checksums accordingly. 02 UPDATE EXTRA PRODUCT DETAILS Extract the data contained in the message in the Following format:- <(f1) US (f2) US...(f34) US> where US is the ASCII unit separator (1F hex) and fields f1 to f34 are defined in section 7. Overwrite the extra product details for the Selected product with extracted data, and update any checksums accordingly. 03 GENERAL SYSTEM DETAILS 04 SYSTEM SENSOR DETAILS 05 SYSTEM SETUP STATUS Note: It is necessary to ASK FOR REMOTE CONTROL in order to carry out Changes. Page 19 of 32

6.3.1. Change Sequence Example: Assuming that the Loma Device is not already under Remote Control, an example of a command sequence to change the product details data set of product number three would be as follows: Step 1, Ask For Remote Control : Transmit to Loma device: <STX> <0> <00> <000> <ETX> <CHKSUM> Message Type Product Number (0 = Command) (n/a) (00 = Ask for Remote Control) If all is well receive from Loma device an ACK and the following message: <STX> <4> < 0> <0> <ETX> <CHKSUM> Message Type Result (4 = Confirm) (0=OK) Command No (00 = Ask for Remote Control) Step 2, Change Product Data Set : Transmit to Loma device: <STX> <2> <01> <003> <INFO> <ETX> <CHKSUM> Message Type Product Number (2 = Change) (no 3) Data Set No Updated Product Details (01 = Product Details) (as Section 7) If all is well receive from Loma device an ACK and the following message: <STX> <4> < 1> <0> <ETX> <CHKSUM> Message Type Result (4 = Confirm) (0=OK) Data Set Number (01 = Product Details) Step 3, Relinquish Remote Control : Transmit to Loma device: <STX> <0> <01> <000> <ETX> <CHKSUM> Message Type Product Number (0 = Command) (n/a) Command No (01 = Relinquish Remote Control) If all is well receive from Loma device an ACK and the following message: <STX> <4> < 1> <0> <ETX> <CHKSUM> Message Type Result (4 = Confirm) (0 = OK) Command No (01 = Relinquish Remote Control) denotes space character (20 Hex) Page 20 of 32

7. MESSAGE CONTENTS 7.1 DEFINITION OF TERMS 31 - ASCII Signed 32 bit Integer number i.e. -2 to + (2 31-1). - ASCII Floating point number with 2 decimal places i.e. ±0. 01to 34. x 10 38. ASCII char - ASCII character (i.e. in 7 bits). spare - A field which is not currently allocated, but may be allocated at a later date. A spare field is set to an ASCII zero. NULL - A field which is not used on this type of machine, however is used on others. A NULL field is set to an ASCII zero. Weights are transmitted in the prevailing machine configured units (except for certain messages on OPUS systems - see sections 6.2.& 6.3), to two decimal places. Machine Weight Units can be configured for one of the following - g, kg, oz, lbs. Lengths are transmitted in the prevailing machine configured units (except for certain messages on OPUS systems - see sections 6.2.& 6.3). Machine Length Units can be configured for one of the following - mm, inches. Page 21 of 32

7.2 Production Data Message (READ ONLY) Field No. 6000 READ ONLY 7000 READ ONLY AS Series READ ONLY ISC READ ONLY IQ, IQ2 and IQ3 READ ONLY Data Item Name Format Data Item Name Format Data Item Name Format Data Item Name Format Data Item Name Format 1 Machine ID 0-16 ASCII chars Machine ID 0-16 ASCII chars Machine ID 0-16 ASCII chars Machine ID 0-7 ASCII Chars Machine ID 0-7 ASCII chars 2 Machine Mode ASCII Machine Mode Machine Mode Machine Mode Machine Mode Unconfigured = 0 Not Inspecting = 1 In Run = 2 Calibrate = 4 Check In Run = 5 DAC Null = 6 integer Unconfigured = 0 Not Inspecting = 1 In Run = 2 Calibrate = 4 Check In Run = 5 DAC Null = 6 Unconfigured = 0 Not Inspecting = 1 In Run = 2 Calibrate = 4 Check In Run = 5 DAC Null = 6 Not Detecting = 0 Unconfigured = 0 Full Calibrate In Run = 130 Reject Disabled In Run = 129 Update Calibrate In Run = 134 In Run = 132 Not Detecting = 0 Unconfigured = 0 Full Calibrate In Run = 130 Reject Disabled In Run = 129 Update Calibrate In Run = 134 In Run = 132 3 Remote Request Count ASCII integer Remote Request Count Remote Request Count Remote Request Count Remote Request Count 4 Product Number ASCII integer 5 Product Code 0-16 ASCII chars 6 Weights Legislation / ASCII Zones integer European/Canadian = 0 Minimum Weights = 1 American 4 Zone =2 American 3 Zone = 3 Page 22 of 32 Product Number Product Number Product Number I = ISC product F = Ferrite product Product Code Weights legislation /Zones European/Canadian = 0 Minimum Weights = 1 American 4 Zone =2 American 3 Zone = 3 0-16 ASCII chars Product Code Weights legislation /Zones European/Canadian = 0 Minimum Weights = 1 American 4 Zone =2 American 3 Zone = 3 ASCII integer, ASCII char I or F 0-10 ASCII chars Product Number I = ISC product F = Ferrite product ASCII integer, ASCII char I or F 0-10 ASCII chars 0-16 ASCII Product Code Product Code chars RESERVED 0 RESERVED 0 7 RESERVED 0 Sensors Enabled Sensors Enabled RESERVED 0 RESERVED 0 CW&MD = 0, MD=1,CW=2 CW=2 8 Tare Weight Tare Weight Tare Weight RESERVED 0 RESERVED 0 9 TU2 setpoint / under TU2 setpoint / under cutpoint TU2 setpoint / under RESERVED 0 RESERVED 0 cutpoint cutpoint 10 TU1 setpoint TU1 setpoint TU1 setpoint RESERVED 0 RESERVED 0 11 Nominal weight / Label Nominal weight / Label weight Nominal weight / Label RESERVED 0 RESERVED 0 weight weight 12 Target Weight Target Weight Target Weight RESERVED 0 RESERVED 0 13 High setpoint / Over cut High setpoint / Over cut point High setpoint / Over cut RESERVED 0 RESERVED 0 point point 14 RESERVED 0 Detection compensation RESERVED 0 Detection compensation Detection compensation 15 RESERVED 0 Detection threshold RESERVED 0 Detection threshold Detection threshold 16 RESERVED 0 Detection mode RESERVED 0 Detection mode Detection mode Resistive/ Dry tune = 0 Reactive = 1 Resistive = 0 Reactive = 1 Dry tune = 2 Resistive = 0 Reactive = 1 Dry tune = 2 17 RESERVED 0 RESERVED 0 RESERVED 0 RESERVED 0 Detection phase angle x 10 (IQ3 only) 18 Mean weight of accept Mean weight of accept packs Mean weight of accept packs RESERVED 0 RESERVED 0 packs 19 Mean weight of all packs Mean weight of all packs Mean weight of all packs RESERVED 0 RESERVED 0 20 Sum of squares of deviations on accepted packs 21 Sum of squares of deviations all packs 22 Count of all packs accepted 23 Weight of all packs accepted Sum of squares of deviations on accepted packs Sum of squares of deviations on accepted / all packs RESERVED 0 RESERVED 0 Sum of squares of deviations all packs Sum of samples of deviations on accepted / all packs RESERVED 0 RESERVED 0 ASCII Count of all packs accepted Count of accepted / all packs Count of all packs accepted Count of all packs accepted integer Weight of all packs accepted Weight of accepted packs RESERVED 0 RESERVED 0 24 TU2 count / under count ASCII TU2 count / under count TU2 count / under count RESERVED 0 RESERVED 0

integer Field No. 6000 READ ONLY 7000 READ ONLY AS Series READ ONLY ISC READ ONLY IQ, IQ2 and IQ3 READ ONLY 25 TU2 weight / under weight TU2 weight / under weight TU2 weight / under weight RESERVED 0 RESERVED 0 26 TU1 count ASCII TU1 count TU1 count RESERVED 0 RESERVED 0 integer 27 TU1 weight TU1 weight TU1 weight RESERVED 0 RESERVED 0 28 TU12 count ASCII TU12 count TU12 count RESERVED 0 RESERVED 0 integer 29 TU12 weight TU12 weight TU12 weight RESERVED 0 RESERVED 0 30 Pass minus count ASCII Pass minus count Pass minus count RESERVED 0 RESERVED 0 integer 31 Pass minus weight Pass minus weight Pass minus weight RESERVED 0 RESERVED 0 32 Pass plus count / accept ASCII Pass plus count / accept count Pass plus count / accept RESERVED 0 RESERVED 0 count integer count 33 Pass plus weight / accept Pass plus weight / accept weight Pass plus weight / accept RESERVED 0 RESERVED 0 weight weight 34 High count / over count ASCII High count / over count High count / over count RESERVED 0 RESERVED 0 integer 35 High weight / over weight High weight / over weight High weight / over weight RESERVED 0 RESERVED 0 36 Metal count (If 6000 ASCII Metal count RESERVED 0 Metal count Metal count combo) (Not currently available) integer 37 Metal weight(if 6000 Metal weight RESERVED 0 RESERVED 0 RESERVED 0 combo) 38 RESERVED 0 RESERVED 0 RESERVED 0 RESERVED 0 RESERVED 0 39 RESERVED 0 RESERVED 0 RESERVED 0 RESERVED 0 RESERVED 0 40 Last run error ASCII Last run error Last run error Last run error Last run error integer 41 RESERVED 0 RESERVED 0 RESERVED 0 Time of last contaminant Time of last contaminant 42 RESERVED 0 Minimum Resultant RESERVED 0 Minimum resultant Minimum resultant 43 RESERVED 0 Maximum Resultant RESERVED 0 Maximum resultant Maximum resultant 44 RESERVED 0 Average Resultant RESERVED 0 Average resultant Average resultant 45 Date of last Weighing Calibration e.g. 01/03/1998 46 Time of last Weighing Calibration e.g. 19:03:34 10 ASCII chars Date of last Weighing Calibration e.g. 01/03/1998 10 ASCII chars Date of last Weighing Calibration e.g. 01/03/1998 10 ASCII chars RESERVED 0 RESERVED 0 8 ASCII Time of last Weighing 8 ASCII chars Time of last Weighing 8 ASCII chars RESERVED 0 RESERVED 0 chars Calibration e.g. 19:03:34 Calibration e.g. 19:03:34 47 Mis-weigh reject count ASCII Mis-weigh reject count Mis-weigh reject count RESERVED 0 RESERVED 0 integer 48 Spare 0 Spare 0 Spare 0 Spare 0 Frequency - khz (IQ3 only) 49 RESERVED 0 RESERVED 0 AMC count RESERVED 0 RESERVED 0 50 RESERVED 0 RESERVED 0 AMC weight RESERVED 0 RESERVED 0 NOTE. Requesting production data has no effect on the run time data of the Loma device. When production data is requested, only the production data that has occurred since the last request is transferred. For example, if production data is requested every three minutes, then the transferred production data will only be based on three minutes of production. Page 23 of 32

7.3 Product Details Message Field No. 6000 7000 AS Series ISC (See note 5) IQ, IQ2 & IQ3 (See note 5) Data Item Name Format Data Item Name Format Data Item Name Format Data Item Name Format Data Item Name Format General Parameters 1 Product Code 16 ASCII chars Product Code 16 ASCII chars Product Code 16 ASCII chars Name 10 ASCII chars Name 10 ASCII chars 2 RESERVED 0 Operation mode Operation mode RESERVED 0 RESERVED 0 0=Combo, 1=Metal detector only 2=Checkweigher only 2=Checkweigher only 3 Batch size 0 Batch size Batch size Batch size Batch size 4 Pack Length *1 Pack Length *1 Pack Length *1 Flow length Flow length 5 Weights legislation /Zones European/Canadian = 0 Minimum Weights = 1 American 4 Zone = 2 American 3 Zone = 3. 6 Tare Weight 7 Nominal Weight *1 8 Target Weight 9 High Setpoint 10 Mid 1 in 40 Setpoint 11 Low Setpoint 12 Display Width Weights legislation /Zones European/Canadian = 0 Minimum Weights = 1 American 4 Zone = 2 American 3 Zone = 3. Tare Weight Nominal Weight *1 Target Weight High Setpoint Mid 1 in 40 Setpoint Low Setpoint Display Width Page 24 of 32 Weighing Parameters Weights legislation /Zones European/Canadian = 0 Minimum Weights = 1 American 4 Zone = 2 American 3 Zone = 3. Tare Weight Nominal Weight *1 Target Weight High Setpoint Mid 1 in 40 Setpoint Low Setpoint Display Width RESERVED 0 RESERVED 0 RESERVED 0 RESERVED 0 RESERVED 0 RESERVED 0 RESERVED 0 RESERVED 0 RESERVED 0 RESERVED 0 RESERVED 0 RESERVED 0 RESERVED 0 RESERVED 0 RESERVED 0 RESERVED 0 Metal Detection Parameters 13 RESERVED Compensation RESERVED 0 Compensation Compensation 14 RESERVED Threshold *3 RESERVED 0 Threshold Threshold 15 RESERVED Minimum Threshold RESERVED 0 Minimum Threshold Minimum Threshold 16 RESERVED 0 Maximum Threshold RESERVED 0 Maximum Threshold Maximum Threshold 17 RESERVED 0 Gain Value Lock *2 RESERVED 0 Head Power Lock Head Power Lock On=1, Off=0 On=1, Off=0 On=1, Off=0 18 RESERVED 0 Control Line Settings *2 *4 RESERVED 0 Head Power Setting Min=0,1,2,3,4,5, Max=6 Head Power Setting (IQ & IQ2) Min=0,1,2,3,4,5,6,7 Max=8 Head Drive Setting (IQ3) 19 RESERVED 0 Detection Mode *2 Resistive=0, Reactive=1, Dry Tune=2 RESERVED 0 Working Mode Resistive=0, Reactive=1, Dry Tune=2 RESERVED 0 Working Mode Lock On=1, Off=0 Working Mode Resistive=0, Reactive=1, Dry Tune=2 20 RESERVED 0 Ferrite Product True=1, False=0 Working Mode Lock On=1, Off=0 21 RESERVED 0 RESERVED 0 RESERVED 0 Calibrate Trigger Calibrate Trigger Threshold Threshold 22 Weight units (Read Only) 0 Weight units (Read Only) Weight units (Read Only) RESERVED 0 RESERVED 0 0=g, 1=oz, 2=Kg, 3=Lbs 0=g, 1=oz, 2=Kg, 3=Lbs 0=g, 1=oz, 2=Kg, 3=Lbs 23 Length units (Read Only) 0 Length units (Read Only) Length units (Read Only) RESERVED 0 RESERVED 0 0=mm, 1=inches. 0=mm, 1=inches. 0=mm, 1=inches.

24 System type = 1 System type = 2 System type = 4 System type = 0 System type = 3 (IQ & IQ2) = 5 (IQ3) Field No. 6000 7000 AS Series ISC (See note 5) IQ, IQ2 & IQ3 (See note 5) 25 RESERVED RESERVED 0 RESERVED 0 RESERVED 0 Detection Normal=0, Reverse=1 26 RESERVED RESERVED 0 RESERVED 0 RESERVED 0 Phase Angle x 10 (IQ3 only) 27 RESERVED RESERVED 0 RESERVED 0 RESERVED 0 Frequency index (IQ3 only) 28 RESERVED 0 RESERVED 0 RESERVED 0 RESERVED 0 Head P Gain (IQ3 only) 29 RESERVED 0 RESERVED 0 RESERVED 0 RESERVED 0 Head Q Gain (IQ3 only) 30 RESERVED 0 RESERVED 0 RESERVED 0 RESERVED 0 RESERVED 0 31 RESERVED 0 RESERVED 0 RESERVED 0 RESERVED 0 RESERVED 0 Note 1. Transmitting a Change Product Details Message that includes new values for fields 4 and 7 will effect the accuracy of the Checkweigher. Re-calibration of the Checkweigher is recommended. Note 2. Transmitting a Change Product Details Message that includes new values for fields 17,18 and 19 will cause the Metal Detector calibrate flag to be cleared. Re-calibration of the Checkweigher will therefore be required. Note 3. Transmitting a Change Product Details Message that includes field 14 only, after one that included fields 17, 18, and 19 will cause the Metal Detector flag to indicate a calibrated status. Note 4. Control Line Settings. 0= Out, Out, Out. 1= In, Out, Out. 2= Out, In, Out. 3= In, In, Out. 4= Out, Out, In. 5= In, Out, In. 6= Out, In, In. 7= In, In, In. Note 5. Transmitting a Change Product Details Message will cause the Metal Detector calibrate flag to be cleared. Re-calibration of the Metal Detector will therefore be required. Page 25 of 32

7.4 Product Setup Status Message Field No. 6000 7000 AS Series ISC IQ, IQ2 & IQ3 Data Item Name Format Data Item Name Format Data Item Name Format Data Item Name Format Data Item Name Format 1 General Parameters Setup Mask General Parameters Setup Mask 2 Checkweighing Checkweighing Parameters Setup Parameters Setup Mask Mask 3 RESERVED 0 Metal Detection Parameters Setup Mask Parameter Groups Setup General Parameters Setup Mask RESERVED 0 RESERVED 0 Checkweighing RESERVED 0 RESERVED 0 Parameters Setup Mask RESERVED 0 RESERVED 0 RESERVED 0 4 RESERVED 0 RESERVED 0 RESERVED 0 RESERVED 0 RESERVED 0 5 RESERVED 0 RESERVED 0 RESERVED 0 RESERVED 0 RESERVED 0 6 RESERVED 0 RESERVED 0 RESERVED 0 RESERVED 0 RESERVED 0 7 RESERVED 0 RESERVED 0 RESERVED 0 RESERVED 0 RESERVED 0 8 Checkweigher Calibrated (Read Only) True=1, False=0 Checkweigher Calibrated (Read Only) True=1, False=0 9 RESERVED 0 Metal Detector Calibrated (Read Only) True=1, False=0 Calibration Status Checkweigher Calibrated (Read Only) True=1, False=0 RESERVED 0 Metal Detector Calibrated (Read Only) True=1, False=0 RESERVED 0 RESERVED 0 Metal Detector Calibrated (Read Only) True=1, False=0 10 RESERVED 0 RESERVED 0 RESERVED 0 RESERVED 0 RESERVED 0 11 Multispeed Multispeed Multispeed RESERVED 0 RESERVED 0 Calibrated (Read Only) True=1, False=0 Calibrated (Read Only) True=1, False=0 Calibrated (Read Only) True=1, False=0 12 Spare 0 Spare 0 Spare 0 Spare 0 Spare 0 13 Spare 0 Spare 0 Spare 0 Spare 0 Spare 0 14 Spare 0 Spare 0 Spare 0 Spare 0 Spare 0 15 Spare 0 Spare 0 Spare 0 Spare 0 Spare 0 Page 26 of 32

7.5 Metal Contaminants log (READ ONLY) Field No. 6000 NOT APPLICABLE 7000 NOT CURRENTLY AVAILABLE AS Series NOT APPLICABLE ISC NOT CURRENTLY AVAILABLE IQ, IQ2 & IQ3 Data Item Name Format Data Item Name Format Data Item Name Format Data Item Name Format Data Item Name Format 1 Time e.g. 19:03:57, 04:45:12 8 ASCII chars Time e.g. 19:03:57, 04:45:12 8 ASCII chars Time e.g. 19:03:57, 04:45:12 8 ASCII chars 2 Date e.g. 01/07/97, 03/09/98 3 Saturated Channels None=0, Resistive=1, Reactive=2, Both=3. 10 ASCII chars Date e.g. 01/07/97, 03/09/98 Saturated Channels None=0, Resistive=1, Reactive=2, Both=3. 10 ASCII chars Date e.g. 01/07/97, 03/09/98 Saturated Channels None=0, Resistive=1, Reactive=2, Both=3. 10 ASCII chars 4 Signal Value Signal Value Signal Value 5 Threshold at Time of Contaminant Detection Threshold at Time of Contaminant Detection Threshold at Time of Contaminant Detection. Time e.g. 19:03:57, 04:45:12. Date e.g. 01/07/97, 03/09/98. Saturated Channels None=0, Resistive=1, Reactive=2, Both=3. 8 ASCII chars Time e.g. 19:03:57, 04:45:12 10 ASCII chars Date e.g. 01/07/97, 03/09/98 Saturated Channels None=0, Resistive=1, Reactive=2, Both=3. 8 ASCII chars Time e.g. 19:03:57, 04:45:12 10 ASCII chars Date e.g. 01/07/97, 03/09/98 Saturated Channels None=0, Resistive=1, Reactive=2, Both=3. 8 ASCII chars 10 ASCII chars. Signal Value Signal Value Signal Value n Threshold at Time of Contaminant Detection Threshold at Time of Contaminant Detection Threshold at Time of Contaminant Detection Note The log messages may vary in length between 0 and 20 fields. Page 27 of 32

7.6 Extra Product Details Message Field No. 6000 7000 AS Series ISC IQ, IQ2 & IQ3 (see note 3) Data Item Name Format Data Item Name Format Data Item Name Format Data Item Name Format Data Item Name Format 1 Reject output 1 delay 2 Reject output 1 dwell 3 Reject output 2 delay 4 Reject output 2 dwell 5 Reject output 3 delay 6 Reject output 3 dwell 7 Reject output 4 delay 8 Reject output 4 dwell 9 Mode Step=0 Pulse train = 1 10 High Weight Limit 11 Low Weight Limit 12 Weight Resolution Reject output 1 delay Reject output 1 dwell Reject output 2 delay Reject output 2 dwell Reject output 3 delay Reject output 3 dwell Reject output 4 delay Reject output 4 dwell Mode Step=0 Pulse train = 1 High Weight Limit Low Weight Limit Weight Resolution Page 28 of 32 Reject Timing Parameters Reject output 1 delay Reject output 1 delay 50 Ms units Reject output 1 delay 50 Ms units Reject output 1 dwell Reject output 1 dwell Reject output 1 dwell 50 Ms units 50 Ms units Reject output 2 delay RESERVED 0 RESERVED 0 Reject output 2 dwell RESERVED 0 RESERVED 0 Reject output 3 delay RESERVED 0 RESERVED 0 Reject output 3 dwell RESERVED 0 RESERVED 0 RESERVED 0 RESERVED 0 RESERVED 0 RESERVED 0 RESERVED 0 RESERVED 0 Servo Parameters Mode Step=0 Pulse train = 1 High Weight Limit Low Weight Limit Weight Resolution RESERVED 0 RESERVED 0 RESERVED 0 RESERVED 0 RESERVED 0 RESERVED 0 RESERVED 0 RESERVED 0 13 Gain (20 ms units) Gain (20 ms units) Gain (20 ms units) RESERVED 0 RESERVED 0 14 Short Term Count Short Term Count Short Term Count RESERVED 0 RESERVED 0 15 Long Term Multiplier Long Term Multiplier Long Term Multiplier RESERVED 0 RESERVED 0 16 Number of Packs in Transit Number of Packs in Transit Number of Packs in Transit Tracker Parameters 17 Tracker Packs Tracker Packs Tracker Packs Tracker Enabled On=1, Off=0 18 Tracker Multiplier Tracker Multiplier Tracker Multiplier Tracker High Threshold 19 RESERVED 0 RESERVED 0 RESERVED 0 Tracker Low Threshold 20 *1 Pack Rate (packs per minute) 21 *1 Powered weigh table speed M/min 22 Auxiliary conveyor speed M/min 23 *1 Auxiliary conveyor DAC value *1 Pack Rate (packs per minute) Powered weigh table speed M/min *1 Auxiliary conveyor speed M/min *1 Auxiliary conveyor DAC value Multispeed Parameters *1 Pack Rate (packs per minute) Powered weigh table speed M/min *1 Auxiliary conveyor speed M/min *1 Auxiliary conveyor DAC value RESERVED 0 RESERVED 0 Tracker Enabled On=1, Off=0 Tracker High Threshold Tracker Low Threshold RESERVED 0 RESERVED 0 RESERVED 0 RESERVED 0 RESERVED 0 RESERVED 0 RESERVED 0 RESERVED 0

Field No. 24 Short Term Mean Sample Size 6000 7000 AS Series ISC (See note 5) IQ, IQ2 & IQ3 (See note 5) Short Term Mean Sample Size Short Term Mean Short Term Mean Sample Size RESERVED 0 RESERVED 0 PV Test Parameters 25 RESERVED 0 RESERVED 0 RESERVED 0 RESERVED 0 False threshold 26 RESERVED 0 RESERVED 0 RESERVED 0 RESERVED 0 Threshold 27 RESERVED 0 RESERVED 0 RESERVED 0 RESERVED 0 Ferrous test sample size (Not currently available) 28 RESERVED 0 RESERVED 0 RESERVED 0 RESERVED 0 Non ferrous test sample size (Not currently available) 29 RESERVED 0 RESERVED 0 RESERVED 0 RESERVED 0 Stainless steel test sample size (Not currently available) Servo Parameters 30 Spare 0 Spare 0 Servo Backlash Spare 0 Spare 0 31 Spare 0 Spare 0 Spare 0 Spare 0 Spare 0 32 Spare 0 Spare 0 Spare 0 Spare 0 Spare 0 33 Spare 0 Spare 0 Spare 0 Spare 0 Spare 0 34 Spare 0 Spare 0 Spare 0 Spare 0 Spare 0 0 0 0 Note 1. Transmitting an Extra Product Details Message that includes new values for fields 20,21 and 23 will cause the Checkweigher calibrate flag to be cleared. Re-calibration of the Checkweigher will therefore be required. Note2. PV Test parameters are available from software version IQV1.01 Page 29 of 32

7.7 PV Test Details (READ ONLY) Field No. 6000 NOT APPLICABLE 7000 NOT APPLICABLE AS Series NOT APPLICABLE ISC NOT CURRENTLY AVAILABLE IQ & IQ2 (FROM S/W IQV1.01) Data Item Name Format Data Item Name Format Data Item Name Format Data Item Name Format Data Item Name Format 1 Machine ID 0-7 ASCII chars 2 Time PV Test initiated 8 ASCII chars e.g. 19:03:57, 04:45:12 3 Date PV Test initiated 10 ASCII chars e.g. 01/07/97, 03/09/98 4 Time PV Test completed 8 ASCII chars e.g. 19:03:57, 04:45:12 5 Date PV Test completed 10 ASCII chars e.g. 01/07/97, 03/09/98 6 Product Number F = Ferrite product, ASCII char 7 Product Code 0-10 ASCII chars 8 Operator ID 0-3 ASCII chars 9 Number of passes 10 PV Status 0=Success, 1=No samples, 2=Not Actioned 11 Ferrous test sample size 12 Non ferrous test sample size 13 Stainless steel test sample size 14 Threshold 15 False Threshold 16 Timing mode 0=Off, 1=Interval, 2=Batch Page 30 of 32

7.7 OPC General Details (READ ONLY) Field No. 6000 NOT APPLICABLE 7000 NOT APPLICABLE AS Series NOT APPLICABLE ISC NOT CURRENTLY AVAILABLE IQ2 & IQ3 (IQ2 FROM S/W IQ2V1.8.0) (IQ3 FROM S/W IQ3V1.2.0) Data Item Name Format Data Item Name Format Data Item Name Format Data Item Name Format Data Item Name Format 1 System Type ASCI integer 2 Machine ID 0-7 ASCII chars 3 Machine Mode 4 MachineTime 8 ASCII chars e.g. 19:03:57, 04:45:12 5 Machine Date 8 ASCII chars e.g. 01/07/07, 03/09/07 6 Machine Day 7 PV Enabled 8 Product Reg. PEC 9 Product Number 10 Product Name 10 ASCII chars 11 Frequency khz (IQ3 only) 12 Threshold 13 Compensation 14 Detection Mode 15 Phase Angle x 10 (IQ3 only) 16 Head Power / Drive 17 Head P Gain (IQ3 only) 18 Head Q Gain (IQ3 only) 19 Reject Delay 20 Reject Dwell 21 Remote Request Count 22 Total Accepts 23 Metal Count 24 Min Resultant 25 Ave Resultant 26 Max Resultant Page 31 of 32

APPENDIX A RETURN CODES Code Status/Error Details 0 DATA LINK HEALTHY (OK) 1 INVALID MESSAGE TYPE 2 SENT COMMAND CHANGE 3 SENT REQUEST 4 NOT A DATA REQUEST 5 NOT A DATA CHANGE COMMAND 6 NOT A COMMAND SENT 7 UNKNOWN COMMAND 8 UNKNOWN DATA SET 9 COMMAND FAILED a REQUEST FAILED b CHANGE FAILED c CRITICAL LOCAL CONTROL d PRINTER NEEDS ATTENTION e MESSAGE OR DATA FORMAT ERROR f NON EXISTENT PRODUCT NUMBER NOTE 1: RETURN CODES in normal type are not relevant to this application. NOTE 2 : when the return code is greater than 9 i.e. a - f the code is in lower case. Page 32 of 32