Data Acquisition System Having Selective Communication Capability

The disclosures of the following copending applications assigned to the assignee of the present application and filed concurrently herewith are specifically incorporated by reference:

"Data Acquisition System Having Setup Duplication Capability", U.S. Pat. No. 5,295,063 issued Mar. 15, 1994; and

"Control Board Having Dual Means of Configuration", U.S. Pat. No. 5,299,113 issued Mar. 29, 1994.

1. Field of the Invention

The present invention is directed to the field of data acquisition and, in particular, to a data acquisition system having selective communication capability.

2. Description of the Prior Art

In the commercial laundry field, state-of-the-art commercial laundry appliances today incorporate data accumulation and communication capabilities. For example, switches or electro-optical detectors may be provided to monitor certain aspects of machine operation, such as monies deposited, cycles vended, certain door openings, power failures and other useful information. These data may be retained in electronic memory within the appliance and subsequently communicated to a portable collection unit, such as a hand held probe or computer. Systems of this type are described, for example, in U.S. Pat. Nos. 4,369,442 (Werth et al.); U.S. Pat. No. 4,216,461 (Werth et al., and U.S. Pat. No. 4,306,219 (Main et al.). In such a system, the laundry appliance is provided with an appropriate means for establishing communication with an external device, such as an infrared optical communication link.

The prior art approaches for permitting communication between a data probe and a data acquisition unit as described above have many limitations. In particular, the data acquisition systems of this type are system dedicated The data probe interrogates the data acquisition unit of the appliance and the data acquisition unit responds by sending records of information it has accumulated. The problem, however, is the inability of either the data probe or the data acquisition unit to communicate with other data acquisition systems. For example, a first type of data acquisition system would have a data probe and data units compatible with one another but not with other data acquisition systems. A second type of data acquisition system would suffer from the same disadvantage. Thus once a data acquisition system is selected, neither the data probe nor data unit may be replaced by a probe or data unit from another data acquisition system.

This presents a disadvantage to an owner who initially purchased a data acquisition system comprising several appliances having data acquisition units and a compatible probe and later replaces some or all of the appliances by appliances having data acquisition units from a different data acquisition system. The owner would then have to purchase a second probe that was compatible with the new appliances. Not only does this increase the expense of the system and limit the owner's choice among data acquisition units, but the route operator must now carry two probes in order to communicate with all of the appliances on his route. The incompatibility of prior data acquisition systems thus complicates the data collection process and adds to the expense of such systems.

It is desirable to provide data acquisition system having selective communication capability thereby enabling the data acquisition system to communicate with various data acquisition units and probes. Such flexibility permits the owner or route operator to communicate with the appliances without having to replace the data acquisition units or purchase alternative probes.

A data acquisition system having selective communication capability to enable the data acquisition system to communicate with other data acquisition systems. The probe of the present invention initiates communication with a data acquisition unit located in an appliance. The data acquisition unit maintains a collection record which indicates the current setup and counts of the appliance. When the probe communicates with the data unit, it identifies itself and based upon this identification, the data unit responds with a particular collection record which is compatible with the probe communicating with the data unit, In addition, if the probe is used to setup a data unity the probe decides what type of setup record to send based upon the collection record received from the data unit.

Further objects and advantages of this invention will become more apparent and readily appreciated from the following detailed description of the present invention with reference to the accompanying drawings.

FIG. 1 illustrates a data acquisition system according to one embodiment of the present invention.

FIG. 2 illustrates an appliance equipped with optical communication capability.

FIG. 3 illustrates a portable probe used in conjunction with the present invention.

FIG. 4 is an electrical schematic of a portion of a control board having an optical communication link for the appliance shown in FIG. 2.

FIG. 5 illustrates the byte format used in the communication protocol.

FIG. 6 illustrates the message format for a control message.

FIG. 7 illustrates the message format for a data message.

FIG. 8 illustrates a first collection record.

FIG. 9 illustrates a second collection record.

FIGS. 10a-k illustrates flow charts for the communication protocol according to a preferred embodiment of the present invention.

FIG. 1 illustrates a data acquisition system 10 according to the present invention. The data acquisition system incorporates three major elements: a data acquisition unit 12 which resides in an appliance such as a washer or dryer and is integral with the appliance's controller; a commercially available collection probe 14 which is carried by a route operator to interface with one or more of the appliances having data collection capability; and a personal computer system 16 for use by the route operator to receive collected information from the collection probe 14 and perform desired business analyses on the information. One aspect of the present invention is directed to the series of messages, referred to as protocol, exchanged between a data acquisition unit 12 and a collection probe 14.

FIG. 2 illustrates an appliance such as a washer 18 according to the present invention. The washer 18 is equipped with at least one coin drop slot 20, an optical window 22 behind which is an optical transceiver (not shown) having an optical emitter and an optical detector and a panel (not shown) behind which is a group of switches. The optical window 22 is provided so that the washer 18 can communicate with an external device such as a portable collection unit, for example, a hand held probe (see FIG. 3). Alternatively, the switches located behind the panel are located so as to be easily accessible by an owner or route operator and are provided to setup the appliance as described in copending patent application, incorporated herewith, entitled "Control Means Having Dual Means of Configuration" U.S. Pat. No. 5,299,113 issued Mar. 29, 1994, and assigned to the MAYTAG Corporation. Preferably, the switches are placed behind a limited access panel.

FIG. 3 illustrates an external device in the form of a portable probe 24 which may be used in conjunction with the present invention. The probe 24 has an optical communications window 26 located on the side of the probe 24 behind which lies an optical transceiver (not shown) formed by an optical emitter and an optical detector. In addition, a keypad 28 is provided to allow the owner or route operator to select a mode of operation and enter data. There are generally three modes of operation of concern to the present invention; collection, monitor and setup which will be described in detail hereinafter. A liquid crystal display (LCD) screen 25 displays menus from which the user may select options including the three discussed above. A trigger button 30 is used to initiate sending signals to and receiving signals from the optical communications window 22 of the washer 18 after a selection is made. Preferably the probe 24 employed utilizes infrared communications although other optical wavelengths may be similarly utilized. An infrared probe is available from Mars Electronic Company commercially as the MARS MEQ.TM. 130 Portable Data Terminal.

FIG. 4 is an electrical schematic of a portion of the data acquisition unit located on control board 32 having an optical communication link in accordance with the present invention for the appliance shown in FIG. 2.

The control board 32 includes a microprocessor 34, a group of dual inline package (dip) switches 36 and an optical transceiver 38 formed by an optical emitter 40 and an optical detector 42. Preferably the microprocessor 34 is a HITACHI microcomputer, model number HD 6305VO. Many types of switches may be used and preferably a 12 position dip switch, model number 76SB128 available from GRAYHILL of LaGrange, Ill. is used.

In the present invention, an appliance, such as a washer, has a relay (not shown) mounted on the control board to power or initiate an electro-mechanical timer. The timer sequences and powers various appliances such as water valves and motors. For other appliances, a plurality of relays may be mounted off the control board and electrically connected with components of the board. The relays are selectively energized for controlling the various functions of the appliance. The specific construction of the apparatus required for the mechanical functions of the appliance are well known to those skilled in the art and form no part of the present invention. For that reason, they will not be described in detail, it being understood that the relays open and close the required electrical circuits for proper operation of the appliance.

The optical transceiver 38 preferably provides two-way communication between an appliance, such as a washer 18 (FIG. 2) and the hand held probe 24 (FIG. 3). The appliance can thus transmit information to the probe 24 via its emitter 40 and receive information from the probe 24 via its detector 42. Both the probe and the data unit include memory to store information transmitted during the communication protocol.

If data accumulated by the appliance is to be collected using the probe 24, the user selects the collection mode from a menu displayed on the screen 25 of the probe 24 by the keypad 28 and begins communication with the appliance by pulling the probe's trigger 30. If the user wants to set-up or change the operational parameters of the appliance using the probe 24, the user selects a setup or configuration mode by the keypad 28 and sends a setup record to the appliance by pulling the trigger 30. The setup record is preferably created at a remote computer site and downloaded into the memory of the probe 24. The setup record may be created on-site using the keypad 28 of the probe 24, however, this is generally not as convenient. As an alternative to using the probe 24 to setup the appliance, certain parameters may be configured by the group of switches 36 as previously described.

An output 44 of the microprocessor 34 may be used and controlled by appropriate programming in a manner well known to those of ordinary skill in the art to control the optical emitter 40. The output 44 may be controlled by suitable programming of the microprocessor 34 to generate coded outputs corresponding to, for example, data received by the microprocessor 34 from various machine monitoring inputs 46 and stored in the internal memory registers of the microprocessor 34 for subsequent transmission. To avoid interference by ambient infrared and optical signals which are typically present, it is desirable to encode the transmitted intelligence on a known carrier frequency. In the preferred embodiments communications are provided by synchronous signals at 1200 baud encoded on a 30.+-.1 Kilohertz carrier frequency. This encoding is accomplished by the microprocessor 34 in manners well known by those skilled in the art. Of course other forms of encoding may be employed if desired.

If encoding on a carrier frequency, as preferred, is employed, the receiving circuitry may include a demodulator and buffer amplifier 48. In the preferred embodiment, a MOTOROLA demodulator and preamplifier, Part No. MC3373P, is employed and the discriminated output signal is supplied to an interrupt input 50 of the microprocessor 34. Alternatively, the received signal may be supplied directly to the microprocessor 34 which itself may then decode and further discriminate the intelligence as desired in manners known in the art.

The electro-optical communication between the probe 24 and the data acquisition unit is initiated by aiming the optical communications window 26 (FIG. 3) of the portable probe 24 at the optical communications window 22 (FIG. 2) of the appliance. The probe 24 is activated by pulling the trigger button 30 to send a signal to the optical transceiver 38 of the appliance. The receiving circuitry of the appliance delivers a demodulated signal to the interrupt 50 input of the microprocessor 34 as is well known to those skilled in the art. Preferably the communication between the data acquisition unit and the collection probe is two-way with the collection probe sending control and command signals and the data acquisition unit replying by sending data records which were stored in the data unit during the operation of the appliance. The specific signals transmitted and received by the probe and the data acquisition unit will be described hereinafter.

When the probe 24 is used to interrogate a data acquisition unit, a specific interrogation and verification protocol must be successfully performed before the data collection unit in the appliance will output any data from its registers. This protocol will be described with respect to the flow charts of FIGS. 10a-k.

The present invention employs a data probe and data unit which can selectively communicate with other data acquisition systems. The data unit of the present invention is interrogated by a probe which identifies itself to the data unit and tells the data unit what information it is seeking. Based upon this identification, the data unit will respond by transmitting the requested information in a format dependent upon the identification of the probe. The data unit thus selectively chooses how it will respond to an interrogation by a probe based upon the manner in which it is spoken to. In addition, the probe of the present invention may interrogate various data units. The probe recognizes the data unit by information sent by the data unit. Based upon the identification of the data unit, the probe will respond by transmitting information in a format based upon the identity of the data unit.

Data acquisition system may utilize many different communication formats. These formats may be used to identify data units and probes from different data acquisition systems. Different data acquisition systems may employ communications using various modulation schemes, carrier frequencies and transmission rates, for example. In the preferred embodiment, the distinguishing characteristic identifying probes and data units according to the present invention is determined by specific bytes of information transmitted by the probes and data units. While a particular communication protocol will be described hereinafter, it is not intended that the present invention be limited to such a communication protocol.

The format of the signals sent by the probe and the data acquisition unit will now be described with reference to the preferred embodiment of the present invention. Each message is preferably transmitted serially byte by byte. FIG. 5 illustrates the byte format. Each byte comprises 10 bits having one start bit, 8 data bits and one stop bit. The data bits are not specifically coded and there are no restrictions as to data values therefore any of 256 combinations of 8 data bits may be transmitted as a data byte. Each byte is transmitted least significant bit first, after the start bit and most significant bit last immediately preceding the stop bit at a transmission rate of 1200 Baud as described above. On/off keying of optical signals is used as the modulation scheme with an amplitude modulation depth of approximately 80 to 100%. As described earlier the subcarrier frequency preferably ranges from about 29 to 31 Kilohertz. The duty cycle of the optical emitter at the subcarrier rate shall range from 40 to 60%. A binary low, i.e. "0", is defined as the presence of optical energy at the optical emitter of the probe or the data acquisition unit, i.e. carrier and subcarrier, and a binary high, i.e., "1" is defined as the absence of any transmitted optical energy from the optical emitter of the probe or the data acquisition unit.

The data communication between the data acquisition unit and the collection probe involves both control messages and data messages. The protocol specified is a variation and subset of DDCMP, a byte count protocol for data link control as specified by the Digital Equipment Corporation. (DDCMP, Ver. 4.0; 01 Mar. 1978). Error detection is included for both the control and the data messages. The error detection employs a cyclic redundancy check using the CRC-16 convention as is well known by those skilled in the art. The CRC-16 algorithm is defined by the equation p(x)=x.sup.16 +x.sup.15 +x.sup.2 +x.sup.0. [See, W. Stallings, Data Computer Communications, pages 105-110 (MacMillian Publishing Co. 1985) incorporated herein by reference.]

FIG. 6 illustrates the message format for a control message. The control message has 8 bytes of information. The first byte is a control message identifier and is used to differentiate control messages from data messages. The second byte defines the message type and is used to distinguish one control message from another control message. The third through the fifth bytes are not currently used. The sixth byte defines STATUS which will be described in detail hereinafter. The seventh and eighth bytes represent the low and high bytes respectively of CRC16 for the first six bytes of the control message.

There are preferably four types of control messages used: Start ("START"); Start Acknowledge ("STACK"); Acknowledge ("ACK"); and No Acknowledge ("NACK"). As mentioned above, the second byte is used to distinguish these messages. The sixth byte, STATUS, is used in the ACK message where it may have one of two possible values as will be described in detail hereinafter.

FIG. 7 illustrates the message format for a data and maintenance message. The format includes an 8 byte preamble plus a variable length data field. The first byte of the preamble is a message identifier which is used to differentiate data messages, maintenance messages and control messages. The second byte represents the least significant 8 bits of a 14 bit count defining the total number of data bytes in the message. The least significant 6 bits of the third byte define the most significant 6 bits of the 14 bit count defining total number of data bytes in the message. The fourth and fifth bytes are currently not used. The sixth byte defines STATUS. The seventh and eighth bytes define the CRC16 for the first 6 bytes. Immediately following the preamble bytes are the data bytes. The number of data bytes is variable.

There are preferably three types of data messages used: Security/Control Data ("DATA 1"); Vending Data ("DATA 2") and Bad Security Code ("BADSEC").

A DATA 1 message is always sent by the probe to the data unit. The sixth byte of the preamble, STATUS, has two possible values. The STATUS byte is used to identify the probe communicating with the data unit. The data unit thus recognizes the probe by this byte and sends information in an appropriate format in response thereto. More specifically, the data unit is directed to send a particular record. The data bytes following the preamble are variable but the following information, for example, may be transmitted. Data bytes 1-3 define an old security code in binary coded decimal (BCD) format. While these bytes are referred to as bytes 1-3, they are actually the ninth through the eleventh bytes since they immediately follow the 8 byte preamble. Bytes 4-6 define a new security code in BCD format. Bytes 7-8 define a selected mode of operation. For example, if the value of bytes 7-8 is less than a particular value, the probe is used to monitor information accumulated by the data unit. If the value is greater, the probe is used to collect information accumulated by the data unit. Bytes 7-8 act as a back-up security for an ACK message, the significance of this will become clear with reference to FIGS. 10a-h. Bytes 9-11 define the date in BCD format. Bytes 12-13 define the time in BCD format. Bytes 14-15 define CRC16. More will be said concerning how the DATA 1 information is used hereinafter.

A DATA 2 message is always transmitted by the data acquisition unit to the collection probe. Like the DATA 1 message, a DATA 2 message has an 8 byte preamble plus a variable number data field. All bytes of the preamble have the same definition as those of the DATA 1 preamble except for the sixth byte, STATUS, which is left undefined. Immediately following the preamble are the data bytes. The first through the Nth bytes define an appliance collection record. The first byte of this record distinguishes particular data acquisition units by brand or model, for example. The Nth+1 and the Nth+2 bytes define CRC16 for the N data bytes.

As described above, different types of records may be sent by the data unit. For example, if probe #1 communicates with the data unit depending upon the probe that is communicating with the unit, a collection record as shown in FIG. 8 may be sent. If probe #2, however, communicates with the data unit, a collection record as shown in FIG. 9 may be sent, which provides more information than the record of FIG. 8.

Each field length of the collection records shown in FIGS. 8 and 9 is measured in bytes with each byte having eight bits. Not every field will be described since the field name provides sufficient description as to the contents of the field. Both records contain a one byte field at the first position of the record defined as record type. This byte distinguishes the records of one data unit employing one type of data format from those of another. The record illustrated in FIG. 8 has a different value for the record type byte than the record illustrated in FIG. 9 and thus indicates different data formats.

For the record illustrated in FIG. 8, the first four fields provide information concerning the appliance and its location. The remaining fields contain information concerning the operation of the appliance. For example, the interval revenue slide field is a 2 byte field representing the number of cycles the appliance has sold since the last collection probe reading. The status debounce and status fields are 1 byte fields representing the current status of the appliance.

For the record illustrated in FIG. 9, the first five fields provide information concerning the appliance and its location. The remaining fields provide information concerning the operating parameters of the appliance. The current status 1 and current status 2 fields are 1 byte fields representing the current status of the appliance. The diagnostics field is a 3 byte field representing potential problems detected by the microprocessor.

The third type of data message, BADSEC, is always transmitted by the data unit to the probe and thus has an 8 byte preamble followed by four data bytes. The preamble bytes have the same definition as the preamble bytes of a DATA 2 message described above. A BADSEC message is distinguished from other data messages because it is the only data message that does not have a variable data field. The following data may be transmitted in a BADSEC message. Data byte 1 defines a file type. Bytes 2-4 define the appliance identification associated with the data unit in BCD format. Bytes 5-6 represent CRC16 for the 4 data bytes.

There are preferably two types of maintenance messages used: SETUP DATA 1 and SETUP DATA 2. SETUP DATA 1 is always transmitted by the probe to the appliance and SETUP DATA 2 is always transmitted by the appliance to the probe. Both maintenance messages have an 8 byte preamble plus a variable number of data bytes. All bytes of the preamble are the same as those for a DATA 1 message except the first and sixth bytes. The first byte, maintenance message identifier, has a different value from that of DATA 1, DATA 2 and BADSEC messages and thus distinguishes these maintenance message from the data and control messages. The sixth byte, STATUS, is left undefined. Immediately following the preamble are the data bytes. The first through the Nth bytes define an appliance setup record. The Nth+1 and the Nth+2 bytes define CRC16 for the N data bytes. An example of these maintenance messages will be described with reference to Tables I and II.

As described above, there are predominantly three modes of operation of the data acquisition system. A DATA 1 message is sent if the probe is used to monitor or collect information accumulated by the appliance. A SETUP DATA 1 message is sent if the probe is used to configure the appliance. Generally, the probe initiates communication with the data unit by transmitting a START message. If the data unit receives the START message, it responds by transmitting a STACK message. If the probe does not receive a STACK message or detects an error in the message, the probe will send another START message preferably after 250 ms. Failure to receive a valid STACK message after preferably nineteen tries results in a failed communication.

If the probe receives a valid STACK message, it transmits a DATA 1 message. This message identifies the probe communicating with the data unit and determines what type of record will be transmitted by the data unit in response to the DATA 1 message. The data unit will wait preferably 250 ms to receive this message. If the data unit detects an error in the DATA 1 message, it will transmit a NACK message. After receiving preferably nineteen NACK messages, the probe will end communications.

If the data unit receives a valid DATA 1 message, it compares its security code to both the old and new security codes transmitted in the data bytes of the DATA 1 message. If the security codes do not match, a BADSEC message will be transmitted by the data unit and the data unit will ignore communications for preferably 60 seconds. If the data unit's security code matches either the old or new security code of the DATA 1 message, the data unit will adopt the new security code as its own and respond with a DATA 2 message.

The probe waits preferably 250 ms for the DATA 2 message. If the probe detects an error in the DATA 2 message, it transmits a NACK message. After preferably five NACK messages, communications are ended. If the DATA 2 message is received correctly, the probe transmits an ACK message.

The data unit waits preferably 250 ms for the ACK message. Depending upon the value of the sixth byte, STATUS, of the ACK message, the data unit will clear its interval data and responds by sending an Ack message. Two timers are set, one for 30 minutes for a valid door opening and the other for one minute to allow receipt by the data unit of a SETUP DATA 1 message.

If the probe is in setup mode, the probe sends a START message and the appliance responds with a STACK message as described above. A SETUP DATA 1 message is now sent instead of a DATA 1 message. The probe determines which setup record to send from the file type field of the DATA 2 collection record it received from the data unit.

In order to setup the appliance, the machine id field of the setup record must match the data unit's machine id if it is nonzero. If they do not match, the data unit responds by transmitting a DATA 2 message in the form of a collection record. If they do match, the data unit adopts fields of the setup record depending upon the action code value, as will be described in detail hereinafter, and the data unit transmits its new setup record with the high bit of the action code set to indicate that the record is used. The probe will respond by sending an ACK message and the data unit responds with an ACK message to complete the setup.

The communication protocol between the probe and the data acquisition unit will be described with reference to FIGS. 10a-k. The blocks of the flow charts illustrated with reference to the present invention are representative of both the structure of the present invention and the function of that structure. Although in the preferred embodiments most of the decisional and operational units shown in these flow charts are contained internally in the microprocessor chip, it is equally feasible to construct them of conventional logic integrated circuits, or even with discrete components. Thus, the representation of the boxes in the flow charts of the present invention are both structural and functional and can be interpreted as hardware and/or software. In these figures, rectangles are provided to illustrate operational devices or units which may be flip-flops, solenoids, relays, etc.; and diamonds are provided to represent decision units which may be comparators, coincidence gates, or the like. Since the physical construction of each operation unit, and each decision unit, is obvious to those skilled in the art from a consideration of its function, the specific construction which may be employed for the various operation units and decision units will not be described in detail. The decision units and operation units shown in the flow charts of the present invention operate in a prescribed sequence, and control the manner in which the various functions are carried out. For that reason, the flow charts will be described in terms of one unit passing control to the next unit, implying that the previous operation or decision has been completed.

The microprocessor monitors its interrupt line as is well known to those skilled in the art to determine the presence of a signal at unit 52 (FIG. 10a). When a message is detected control is passed to unit 54 which checks the CRC to determine if an error is present in the message. If an error is present, control is passed to unit 56 which functions to ignore any inputs on the interrupt line of the microprocessor for a particular time period, preferably 175 ms. If an error is not present, control is passed to unit 58 which determines if the message is a control message. As described earlier, the first byte of the received message distinguishes control messages from other messages. If the message is not a control message, control is passed to unit 56 and communications are ignored. If the message is identified as a control message, control is passed to unit 60 where it is determined if the control message is a START message. As described earlier, the second byte of a control message distinguishes control messages from one another. If the control message is not identified as a START message, control is passed to unit 56 and communications are ignored. If the message is identified as a START message, control is passed to unit 62 which sends a STACK message. The STACK message tells the probe that the START message was received and communications can continue. Control is then passed to unit 64 which sends the CRC for the STACK message.

After the probe has received the STACK message, control is passed to unit 66 (FIG. 10b) which prepares the data unit for receiving a message from the probe. Unit 68 clears the CRC register and prepares the data unit for receiving an 8 byte header. Control is then passed to unit 70 which sets a clock for preferably 250 ms. Control is then passed to unit 72 which increments a NACK counter. Since this is the first time the NACK counter has been incremented, it will have a value of one. Control is passed to unit 74 which determines if the NACK counter is greater than a value, preferably 19. NACK messages are sent by the probe and data unit to indicate that a message transmitted by the probe or data unit has not been acknowledged. If too many NACK messages are transmitted, control is passed to unit 76 which terminates communications, otherwise control is passed to unit 78 which instructs the data unit to wait for a message.

Control is then passed to unit 80 (FIG. 10c) which receives an 8 byte header. Control is then passed to unit 82 which determines if the message is a DATA 1 message. As described earlier, the first byte distinguishes a DATA 1 message from other messages. If the message is not identified as a DATA 1 message, control is passed to unit 84 which determines if the message is a SETUP DATA 1 message. If a collection or monitor mode is selected, the probe will send a DATA 1 message. If a setup mode is selected, the probe will send a SETUP DATA 1 message. The SETUP DATA 1 message is distinguished from the DATA 1 message by the first byte of the preamble. If the first byte identifies this as a SETUP DATA 1 message, control is passed to unit 86 which tells the data unit to get all data bytes of the setup record. Control is then passed to unit 88 which receives the CRC for the SETUP message. The setup protocol will be described in detail hereinafter with reference to FIGS. 10i-k. As described earlier, before an actual SETUP DATA 1 message is transmitted the probe monitors the data unit to receive its current setup and counts in the form of a collection record. This is automatically accomplished by selecting the setup mode. The following protocol described with reference to a DATA 1 message is also automatically carried out in the setup protocol before the SETUP DATA 1 message is actually transmitted by the probe.

If the message was identified as a DATA 1 message by unit 82, control is passed to unit 90 (FIG. 10d) which receives the data bytes of the DATA 1 message. Control is then passed to unit 92 which determines if the CRC is correct. If the CRC is not correct, control is passed to unit 94 which sends a NACK message, increments the NACK counter and tells the probe to send the DATA 1 message again by returning control to unit 66 of FIG. 10(b). If the CRC is correct, control is passed to unit 96 which determines if the monitor or collection mode was selected. As described earlier, this is determined by data bytes 7-8 of the DATA 1 message and an appropriate bit is set to indicate that the probe is acting as a monitor or collector. As will become apparent from the following detailed description, bytes 7-8 are used as a backup security to the ACK message. As described above, the sixth bytes STATUS, of the ACK message, can have one of two values which will either clear interval data or not. Interval data refers to data accumulated between data collections. When the probe is acting as a collector, the interval counts will be cleared whereas when the probe is acting as a monitor, the interval counts are not cleared. Thus if the appliance does not receive a final ACK message at the end of communications from the probe, bytes 7 and 8 of the DATA 1 message ensure that the data unit will clear its interval data if the probe is acting as a collector. In the preferred embodiment, bytes 7-8 will only clear interval data if probe #2 from the example communicates with an appliance having a collection record as shown in FIG. 9.

Control is then passed to unit 98 which determines if the preamble of DATA 1 message is valid. If it is not, control is passed to unit 94 which functions to transmit a NACK message as described above. If the preamble is valid, control is passed to unit 100 which increments the number of probe readings in the collection record of the data unit and clears the NACK count. Control is then passed to unit 102 which determines if the service and vault doors are open. If they are open, control is passed to unit 110 (FIG. 10e) which tells the data unit to adopt a new security code contained in data bytes 4-6 of the DATA 1 message. If the doors are not open, control is passed to unit 104 which determines whether the data unit security code matches the old security code contained in data bytes 1-3 of the DATA 1 message. If they match, control is passed to unit 110 where the data unit adopts the new security code. If they do not match, control is passed to unit 106 which determines whether the data unit security code matches the new security code contained in data bytes 4-6 of the DATA 1 message. If they do not match, control is passed to unit 108 which tells the data unit to send a BADSEC message.

If the data unit's security code matched the setup new security code as determined by unit 106 or the data unit's security code was changed to the setup new security code by unit 110, control is passed to unit 112 which gets data bytes 9-13 of DATA 1 for the date and time. Control is then passed to unit 114 which determines the identity of the probe communicating with the data unit. As described earlier, the sixth byte of the DATA 1 preamble, STATUS, identifies the probe. If the probe is identified as probe #2, control is passed to unit 116 which sends a header and then CRC for a DATA 2 message. If the probe is identified as a probe #1, control is passed to unit 118 which sends a header and then CRC for a DATA 2 message.

If the probe was identified as probe #2, control is passed from unit 116 to unit 120 (FIG. 10f) which prepares to send a DATA 2 message. Control is passed to unit 122 which first copies the interval and cumulative counts from the collection record into temporary storage in the appliance. Control is passed to unit 124 which sends a DATA 2 message having data bytes describing the record fields illustrated in FIG. 9 and the CRC for the DATA 2 message.

If it was determined at unit 114 that probe #1 was communicating with the data unit, control is passed to unit 146 (FIG. 10g) which prepares to send a DATA 2 message having a collection record as shown in FIG. 8. Control is then passed to unit 148 which first copies the interval and cumulative counts from the collection record into the temporary storage of the appliance. Control is then passed to unit 149 which sends the DATA 2 message and CRC.

After the appropriate DATA 2 collection record and CRC have been sent, control is then returned to unit 66 which prepares the data unit for receiving a message as described earlier and therefore need not be described again. Control is then passed from unit 78 to unit 126 (FIG. 10h) to receive a message. Control is then passed to unit 128 to determine if the CRC is correct. If the CRC is correct, control is passed to unit 130 which determines if the received message is a control message. If the message is identified as a control message, unit 132 determines if the message is a START message. If either the CRC is not correct as determined by unit 128 or the message is not a control message as determined by unit 130, control is returned to unit 114 (FIG. 10e) which determines which probe is communicating with the data unit. The data unit will resend a DATA 2 message and wait for a message from the probe. If the message at unit 132 is identified as a START message, control is passed to unit 134 which sends a STACK message. Control is then passed to unit 52 (FIG. 10a) which begins the communication protocol over again. If the message is not a START message, control is passed to unit 136 which determines if the message is an ACK message. If it is an ACK message, control is passed to unit 138 which determines if the interval data should be cleared. As described earlier, the sixth byte, STATUS, of the ACK message can have one of two values. One value clears the interval data while the other does not for a preferred data acquisition system.

If the interval data is to be cleared, control is passed to unit 140 which clears the data. If the message is not an ACK message or the interval data is not to be cleared, control is passed to unit 142 which sees a valid door timer preferably to 30 minutes. Control is then passed to unit 144 which sends a final ACK message. If a final ACK message is not sent, bytes 7-8 of the DATA 1 message sent by probe #2 in the preferred embodiment ensure that the interval counts are cleared if the probe was acting as a collector.

If the setup mode of operation is selected, the probe transmits a setup record to the data unit no either setup the data unit for the first time or reconfigure the data unit's setup record. When the setup mode is selected, the probe automatically first receives a collection record in a DATA 2 message from the data unit it is communicating with before a setup record is sent. The data format used by the data unit is identified by the record type located in the first byte of the collection record. The setup record transmitted by the probe will depend upon the record type of the data unit. The setup record for a first data unit may contain the fields of information shown in Table I below.

The setup record for a second data unit may contain the fields of information shown in Table II below.

Both setup records have a one byte "action code"field. Depending upon the value of the action code byte, particular fields of the setup record will be adopted by the data unit.

Table III below illustrates the action code values, the associated bits which need to be set and the adopted fields. A set bit indicates that a bit is either in a high or low state, preferably high compared to the other bits.

If the user selects the setup mode, immediately after the probe monitors the appliance, control is returned to unit 52 (FIG. 10a) and the probe sends a START message and the appliance replies by sending a STACK message. A SETUP DATA 1 message is then transmitted and unit 88 (FIG. 10c) passes control to unit 150 (FIG. 10i).

Unit 152 determines if there is an error in the setup message. If there is an error, control is passed to unit 154 which functions to transmit a NACK message. If the setup message does not have an error, control is passed to unit 156 which determines whether the setup message was received within one minute of the last valid communication took place. As described above, the probe preferably monitors the data unit before actually transmitting a setup record and thus receives information concerning the current setup and status of the appliance before sending the setup message. Security is thus provided in that it is determined whether the probe is authorized to setup the appliance by first checking security codes as described above. If the SETUP DATA 1 communication does not take place within one minute of the last valid communication, communications are terminated.

If the SETUP DATA 1 communication takes place within one minute of a previous valid communication, control is then passed to unit 158 which checks the file type of the record obtained by the probe from monitoring the data unit before transmission of the setup record. If the file type of the collection record does not match the file type of the setup record, a NACK message is transmitted by the appliance and the probe sends a new setup record.

If there is a match, control is then passed to unit 160 which determines whether the machine identification (id) is equal to zero. If the machine id is zeros then control is passed to unit 162 which determines if the action code authorizes the machine id of the setup record to be adopted. According to Table II, the setup machine id will be adopted if bit 0 of the action code is set. If bit 0 of the action code is set, control is passed to unit 164 and the setup machine id becomes the machine id.

If bit 0 of the action code is not set or the machine id does not equal zero, control is passed to unit 166 which determines if the machine id equals the setup machine id. If the ids do not match, then control is passed to unit 114 (FIG. 10e) which functions to send an appropriate DATA 2 message as described previously. If the ids match, control is passed to unit 168 (FIG. 10j) which determines if bit 0 of the action code is set. If bit 0 is set, control is passed to unit 170 which clears the machine id only if the ids match. Control is passed to unit 172 which sets bit 7 of the action code (Table III) to signify that the setup record has been used.

Control is then passed to unit 174 which determines whether the location and position parameters are to be set. These parameters will be set if bit 1 of the action code is set. If bit 1 of the action code is set, control is passed to unit 176 which sets the location and position parameters according to the setup record. Control is passed to unit 178 which determines whether the setup record is for a second data unit having a setup record illustrated in Table II above. If the setup record is not for a second data unit, control is passed to 186 (FIG. 10k). If the setup record is for a second data unit, control is passed to unit 180.

Unit 180 determines whether the price and coin parameters are to be set. These parameters will be set if bit 2 of the action code is set. If bit 2 of the action code is set, control is passed to unit 182 which sets those parameters accordingly. Otherwise control is passed to unit 184 (FIG. 10k) which determines whether the cycle parameters are to be set. These parameters will be set if bit 4 of the action code is set. If bit 4 of the action code is set, control is passed to unit 185 which sets those parameters accordingly. Otherwise control is passed to unit 186 which determines if bit 5 of the action code has been set. Bit 5 is set if the interval counts accumulated by the appliance are to be cleared. If bit 5 of the action code is set, control is passed to unit 188 which clears the interval counts. Control is passed to unit 190 which saves a two minute timer to remember the time of the last setup. Control is then passed to unit 192 and the appliance sends a SETUP DATA 2 message and CRC. The data bytes of the SETUP DATA 2 message describe the appliance's newly created setup record. Control is then passed to unit 194 where it is determined if a received message is an ACK message. If it is, control is passed to unit 196 and the appliance responds by sending an ACK message and setup is complete. If the received message is not an ACK message, control is passed to unit 198 and the appliance sends a NACK message and the appliance sends a SETUP DATA 2 message again, and a CRC is sent by unit 192.

The source code for the communication protocol described is set out at the end of the detailed description before the claims.

While the present invention has been described with reference to an appliance and in particular a washer, those skilled in the art will appreciate that the present invention can be used in conjunction with many other devices which require configuration of the control board to control the operation of the device.

While the invention has been shown and described in connection with particular preferred embodiments, it is apparent that certain changes and modifications, in addition to those mentioned above, may be made by those who are skilled in the art without departing from the basic features of the present invention. Accordingly, it is the intention of the Applicants to protect all variations and modifications within the true spirit and valid scope of the invention. ##SPC1##