NETWORK FOR COMMUNICATING INFORMATION RELATED TO A CONSUMABLE TO AN APPLIANCE
An appliance network comprising a networked appliance and capable of communicating with a consumable such that information related to the consumable is communicated to the networked appliance.
This application is a continuation of U.S. patent application Ser. No. 11/930,299, filed Oct. 31, 2007, which is a continuation-in-part of International Application No. PCT/US2006/022503, filed Jun. 9, 2006, which claims the benefit of U.S. Provisional Patent Application No. 60/595,148, filed Jun. 9, 2005, all of which are incorporated by reference.BACKGROUND OF THE INVENTION
1. Field of the Invention
The invention relates to components and accessories for a communicating appliance.
2. Description of the Related Art
Household appliances typically comprise one or more components responsible for the electromechanical operations of the appliance. For example, an oven can include an appliance management component having a printed circuit board (PCB) with memory, as well as a user-interface component, such as a control panel or keypad, for a user to issue commands to the oven. As another example, a washing machine can include an appliance management component, a user-interface component, and a motor control component that controls a motor of the washing machine.
Typically, discrete circuits couple the internal components of an appliance, with each discrete circuit responsible for individual communication between related components. The circuits communicate with each other over an internal network that traditionally is implemented by hard-wired ribbon cables or other connectors or harnesses between the components. The hard-wired connectors form a closed system or network that is difficult or not possible to modify. For example, because the closed network relies on hard-coded or hard-wired network solutions, it is not practical to couple additional external components or additional internal components to the appliance to expand the capability or function of the appliance. The closed network cannot easily be adapted for communication with the additional external/internal components and therefore limits the potential of the appliance.SUMMARY OF THE INVENTION
An appliance network comprising a networked appliance and capable of communicating with a consumable such that information related to the consumable is communicated to the networked appliance.
In the drawings:
By employing a software architecture that enables facile communication between internal components of an appliance and between an external component and one or more of the internal components of the appliance, various components and accessories can communicate with the appliance to expand the capability, functionality, and usability of the appliance. The appliance can be any suitable appliance, such as a household appliance. Examples of household appliances include, but are not limited to, clothes washing machines, clothes dryers, ovens, dishwashers, refrigerators, freezers, microwave ovens, trash compactors, and countertop appliances, such as waffle makers, toasters, blenders, mixers, food processors, coffee makers, and the like.
The appliance can be configured to perform a cycle of operation to complete a physical domestic operation on an article. Examples of the physical domestic operations include a food preparation operation, a food preservation operation, a fluid treatment operation, a cleaning operation, a personal care operation, a fabric treatment operation, an air treatment operation, and a hard surface treatment operation. The air treatment operation can comprise, for example, air purification, air humidification, air dehumidification, air heating, and air cooling. The food preparation operation can comprise, for example, food cleaning, food chopping, food mixing, food heating, food peeling, and food cooling. The food preservation operation can comprise, for example, food cooling, food freezing, and food storage in a specialized atmosphere. The fluid treatment operation can comprise, for example, fluid heating, fluid boiling, fluid cooling, fluid freezing, fluid mixing, fluid whipping, fluid dispensing, fluid filtering, and fluid separation. The cleaning operation can comprise, for example, dishwashing, fabric washing, fabric treatment, fabric drying, hard surface cleaning, hard surface treatment, hard surface drying, carpet cleaning, carpet treatment, and carpet drying. The personal care operation can comprise, for example, hair treatment, nail treatment, body massaging, teeth cleaning, body cleaning, and shaving.
The internal components of the appliances can include any component that participates in the operation of the appliance. Some of the internal components have a corresponding controller (main controller, motor controller, user interface, etc.), which can be a simple microprocessor mounted on a printed circuit board, and other components that have no controller. The components can comprise one or more devices that are controlled by the controller. Typically, the controller components in cooperation, either directly or indirectly, through other components, control the operation of all of the components and the associated devices to implement an operation or cycle for the appliance.
The software architecture can be implemented on and communicated over an internal communications network on the appliance. The internal communications network connects the various internal components of the appliance and can be considered a closed network. One example of the internal communications network used within the appliance is the WIDE network protocol, created by Whirlpool, Inc., the assignee of the present patent application.
The software architecture expands the communication ability of the appliance by effectively creating an open network, hereinafter referred to as “network.” Within the appliance, the software architecture can, but does not have to, reside on each of the components that have a controller. Those components with the software architecture form a network node that can communicate with the other nodes.
The software architecture can perform multiple functions. For example, one function can relate to identifying each of the components corresponding to a node on the network, while another function can relate to identifying capabilities or functions of the identified components on the network. Yet another exemplary function is to identify the status of the components on the network. In this way, the software architecture can function to inform all of the nodes on the network of the presence, capabilities, and status of the other nodes.
The software architecture can comprise multiple modules, each of which has different functionality. Various combinations of the modules or all of the modules can reside on each of the components. One module having a basic or core functionality resides on all of the components. In one anticipated configuration, all of the modules reside at least on the main controller, which establishes the main controller to function as a primary or main software architecture, with the other nodes functioning in a client relationship to the main software architecture. In such a configuration, all of the nodes can communicate through the main software architecture. The software architecture can be sufficiently robust that it can permit configurations without a main software architecture or with multiple main software architectures. For example, the controllers of the various components can work together to control the operation of the appliance without any one of the appliances functioning as a main controller. Regardless of the configuration, any component with the software architecture can function as a client with respect to the other components.
Because of the software architecture, the internal components of the appliance are not only connected with one another, but the internal components can also be connected to one or more external components or a new internal component through the network. The external component and/or the new internal component has one, some, or all of the software architecture modules in resident. As a result, the external component and/or the new internal component can communicate with the internal components of the appliance and can also communicate with other external components having the software architecture.
The software architecture can be any suitable software architecture that enables communication between the internal components of the appliance and the external component and/or the new internal component or between components external to the appliance. An example of the software architecture is disclosed in Patent Cooperation Treaty Patent Application No. PCT/US2006/022420, titled “SOFTWARE ARCHITECTURE SYSTEM AND METHOD FOR COMMUNICATION WITH, AND MANAGEMENT OF, AT LEAST ONE COMPONENT WITHIN A HOUSEHOLD APPLIANCE,” filed Jun. 8, 2006, and incorporated herein by reference in its entirety. A related example is shown in priority document U.S. Patent Application No. 60/595,148, filed Jun. 9, 2005. All of the communications between components and accessories and/or any combination of components and accessories described in this application can be implemented by the software and network structures disclosed in either of these applications.
The software architecture disclosed in the aforementioned references can be implemented by providing one or more of the software elements of the software architecture at least on each of the components to be controlled and on the accessory. The software architecture is configured to generate a plurality of messages, with at least one of the software elements residing in each of the components and in the accessory and configured to enable transmission of at least one of the plurality of messages between the components and between the accessory and the components. The messages can be transmitted for bi-directional communication between components and/or components and accessory. The messages can include command messages that are used to implement a physical domestic operation cycle of the appliance.
The messages can be generated by a message generator, which can take the form of the software architecture, the accessory, or a component. One possible message generator is a user interface.
Descriptions of several examples of components and accessories, herein after referred to as “accessory” with it being understood that the accessory can be considered a component on the network, for use in conjunction with the appliance having the software architecture follow. The accessories can be external to the appliance or internal to the appliance. Each of the accessories is enabled with the software architecture whereby the accessory establishes a node on the network or is part of an existing node on the network.
One example of the accessory is a clock. In one embodiment, the clock is external to the appliance and is an atomic clock. For example, the atomic clock can be a wireless atomic clock that can communicate with one or more of the appliances. An illustration of this embodiment is shown in
The clock can acquire an official time via any suitable method, such as from a cellular network, a radio network, or the Internet. The clock can then transmit the official time to the appliance(s). For example, the clock can automatically transmit the official time, transmit the official time based on registered time events (i.e., transmit the official time at predetermined intervals to appliances that have registered for the time events), or transmit the official time upon request from one or more of the appliances.
An example of transmitting the time is shown in
The clock can also function as an amplifier to boost a signal provided by the appliance to a destination appliance or as a wireless access point that can transmit a signal provided by the appliance to a destination appliance. For example, the appliance can have a radio that is not sufficiently strong to provide visibility to the destination appliance but is strong enough to provide visibility to the clock. The clock can receive the signal from the appliance and re-broadcast the signal to a destination appliance or to another appliance that can transmit the signal to the destination appliance, and so on. The clock can amplify the signal prior to or while re-broadcasting the signal, or the clock can simply re-broadcast the signal. An example of utilizing the clock in this manner is illustrated in
The clock can optionally serve as a protocol bridge. A protocol is a standard procedure for regulating data transmission between devices; however, not all devices necessarily communicate in the same protocol. A bridge effectively translates one protocol into another so that devices with different protocols can communicate with one another. The clock, therefore, can function not only as a time-keeping apparatus but also as a bridge between appliances or between the appliance and another device. Thus, the bridge functionality can be incorporated into the clock and the user does not need to purchase a separate bridge. The amplifier and bridging functions can also be included in any of the other accessories described below.
Referring now to
The clock 10 can further have the capability of communicating to the user, such as via the display 18, an alert status of the appliance(s) 12, 14, 16 with which the clock 10 communicates, and, optionally, the user can acknowledge receipt of the alert status, such as via the display 18. According to one embodiment, the acknowledgement by the user can clear the alert status from the clock 10 and the appliance(s) 12, 14, 16. In this manner, the display 18 can function as a user interface that effects communication not only to the user from the appliance but also from the user to the appliance.
With continued reference to
If the clock on the network does not have electronics for functioning as an atomic clock, the clock can be a satellite clock that can receive time from an atomic clock enabled to speak “TimeCast” protocol. Thus, the clock can display the time given by the atomic clock through TimeCast.
The clock can be internal to the appliance, as described above, or can be external to the appliance. When the clock is internal to the appliance, electronics for the clock can be packaged into the appliance during manufacture of the appliance or can be installed into the appliance as an after-market accessory. The clock as an internal accessory can have any of the functionalities described above for the external clock. The clock can also be “plugged” into an appropriate connector on the appliance. The connector can provide both power and data communication.
The clock conventionally associated with the appliance can also function as an accessory. For example, the clock of the appliance can communicate with clocks of other appliances, such as for synchronization of the clocks to establish and/or maintain consistent time among all of the appliances. An example of clock synchronization is illustrated in
Another example of clock synchronization is shown schematically in
The clocks of the appliances can also synchronize by one of the appliances broadcasting the time at periodic intervals. When the clocks are synchronized in this manner, each minute rollover of the time can be synchronized so that there is no discrepancy between the times on the clocks, even while the displayed time is changing.
Another example of an accessory is a cooking aid. The cooking aid can be an active accessory, a sensing accessory, or a combination thereof. The active accessory can be programmed by the user or can receive commands from the appliance for performing an action. The sensing accessory can include one or more sensors that detects a state of the accessory and/or appliance and communicates the state to the appliance or other component on the network.
Exemplary active cooking aids include a controlled stirrer 20 and an ingredient dispenser 22, which can both be associated with the first appliance 12 in the form of the oven. As shown in
Referring now to
The ingredient dispenser 24 can be provided to the user with the ingredients in the compartments 40 (i.e., pre-filled compartments) or with the compartments 40 in an empty condition whereby the user must supply the ingredients to the compartments 40. When the compartments 40 are pre-filled, the type and amount of ingredients can correspond to a predetermined recipe. In one embodiment, the ingredient dispenser 24 can include replaceable compartments so that the user can insert compartments 40 that correspond to a desired recipe.
Employing the ingredient dispenser 24 provides several advantages. For example, the ingredient dispenser can accurately measure and dispense the ingredients at the proper time during the preparation of the material in the cooking vessel 44, thereby improving the quality of the resulting food. Additionally, the ingredient dispenser 24 eliminates or reduces the need for the user to be present at the first appliance 12 for dispensing the ingredients.
Exemplary sensing cooking aids include a sensing cooking vessel 50 and a removable cooking vessel sensor 52, which can both be associated with the first appliance 12 in the form of the oven. As shown in
In the case of a vision sensor, the sensor could transmit video to anther device for the consumer. The consumer could then make control function decisions including control adjustments or stirring activation, as the case may be.
The functionality of the sensing cooking vessel 50 can alternatively be accomplished with the removable cooking vessel sensor 52. Referring now to
The exemplary cooking aids described above, the controlled stirrer 20, the ingredient dispenser 22, the sensing cooking vessel 50, and the removable cooking vessel sensor 52, can be employed individually or in combination with one another. Each of the cooking aids 20, 22, 50, 52 provides a degree of automation to the cooking process, and using more than one of the cooking aids increases the degree of automation. When the user employs more than one of the cooking aids 20, 22, 50, 52, the cooking aids 20, 22, 50, 52 can optionally communicate with each other in addition to communicating with the first appliance 12 or other component on the network.
Another example of an accessory is an operation cycle component configured to store and transfer operation cycles for the appliance. An operation cycle is a set of commands that the appliance executes for operation of the appliance. For example, a washing machine can have several wash cycles that depend on the type of fabric being washed or a size of a fabric load. Similarly, an oven can have several cooking cycles that depend on the type of food being cooked and the cooking process (e.g., defrosting, baking, self-cleaning) Typically, the appliance when purchased by the user has a set of operation cycles that can permanently reside in the appliance as firmware. Referring now to
With continued reference to
The operation cycle component 60 can couple with the appliance 12 in any suitable manner, such as through a direct hardwire connection or a wireless connection. Furthermore, the appliance 12 can implement the additional operation cycles directly from the operation cycle component 60, or the additional operation cycles can be transferred from the operation cycle component 60 to the appliance 12.
Referring now to
In one embodiment, the second portion is compiled software which, in an initial step, reads the data portion and builds a cycle structure in memory which can execute instructions comprising an operational cycle corresponding to the description suggested by the data portion. In a subsequent step, the second portion commences execution of the cycle structure where each step performs some useful action and then transitions to a different step based on transitional logic separating the steps from one another.
In another embodiment, the second portion comprises a compile process step which reads the data portion and builds the cycle structure in memory, and further compiled software which can commence execution of the cycle structure in memory where each step performs some useful action and then transitions to a different step based on transitional logic separating the steps from one another.
The cycle engine itself can be communicated, as well as be configured to communicate with a client to receive and send messages, preferably in accordance with software architecture as shown in FIG. 14 of the incorporated PCT/US2006/022420, having an enabling identifier and a collection of commands and events which are supported via a collection of Op (“Operation”) Codes. Preferably, the cycle engine 69 of either embodiment, will receive messages from a client allowing for changes to the cycle structure. Changes to a cycle structure may be, for example, the insertion or deletion of steps, additions or deletions to the actions of each step, or changes to the transitional logic between any two given steps. To accomplish such changes, identifiers must be associated with the components of the cycle structure such that the client messages can fully specify the exact desired modifications to the cycle structure.
Typical actions in the data portion include, for example, changing the state of electro-mechanical actuators like relays, valves, and fans, and changing the state of user interface indicators like LEDs, buzzers, light rings, segmented displays, or graphics on a graphical LCD. The devices to which the actions will apply may be represented as identifiable functions with a known controllable interface. In other words, physical devices may be modeled or virtually revealed in the SA by an API (Application Programming Interface”} Id where their control interfaces are represented by a collection of Op Codes, each having associated parameters. This allows controllable devices or software components which control the controllable devices to expose themselves to the actions of a step as a message, preferably exposing themselves using the messaging mechanism of the incorporated PCT/US2006/022420 such that location of the control software which can operate on a device or the control software providing controllable access to the device does not need to be known by the cycle engine. With respect to FIG. 14 of the incorporated PCT/US2006/022420, the cycle engine 69 would typically reside in the App Logic 59. “Control software” here means any software, algorithm, or logic directly or indirectly associated with the operational cycle of an appliance. Generally, all logic provides indirect access to the control of a device, but the meaning can extend to include any non-device oriented software participating in the operational cycle of an appliance.
Using the aforementioned cycle engine architecture, an operational cycle accessory can be added to the network of an appliance, discover the cycle engine 69, and send it configuration messages to affect its structure and ultimately its execution. In this case, the operational cycle accessory would typically include a combination of software and data to accomplish the configuration of the cycle engine. Alternately, the aforementioned cycle engine architecture might send a discovery message seeking identification of all sources of the data portion (see the summary of discovery messages below). Sources of the data portion may be in ROM, Flash, EE Prom, an operational cycle component, and/or an external source connected via a network different from the control network (See
In one embodiment, the data portion will be stored in flash memory using the process described in the aforementioned second embodiment, and upon receiving new data from an operational cycle accessory, either physically or virtually by message from a remote client, the cycle engine will compare the received data with the stored dated to create a difference table in a separate memory area. In this way, alterations to the cycle structure can be made to the initial cycle structure while preserving the initial cycle structure for corruption.
When the operation cycle accessory is disconnected from the cycle engine, the data in the difference table associated with that operation cycle accessory may be optionally removed by the cycle engine. This is a form of anti-piracy protection in that the operation cycle accessory must be present for the additional functionality represented by the accessory to be available to the appliance.
Optionally, the connection between the appliance and the operation cycle accessory can include a transfer of data into the difference table or an intermediate table from which the difference table is created or increased. In this case, additional operation cycles may optionally be retained without the permanent presence of the operational cycle accessory. It should also be noted that an operation cycle accessory can be virtual in that the software and data and ability to communicate with the cycle engine may reside on an external device connected to the cycle engine via at least one network and not physically attached to the containing appliance.
It is to be noted that an operational cycle component can have other elements that are not the aforementioned operation cycles or constituent data and complied portions. For example, the operational cycle component can include software code to configure a cycle engine for communication and other functions or code to put software architecture into an alternate mode for the purpose of diagnostics or changing memory.
Other examples of an accessory include a consumable and a consumable reader. A consumable is an object external to the appliance that can be consumed or otherwise used during operation of the appliance or following operation of the appliance. The consumable can be consumed by the appliance or by the user. Examples of consumables include, but are not limited to, detergents and other wash aids for a laundry appliance and/or dishwasher, fabric items (e.g., clothing), heat and serve meals, frozen side dishes, frozen meals, microwave popcorn, frozen pizza, and frozen breakfast sandwiches. Characteristics or information, such as an operating cycle, usage directions, cooking instructions, dosage information, and washing/drying instructions, associated with the consumable can persist, for example, within the consumable itself, in the packaging for the consumable, or in auxiliary materials, such as user manuals and tags, provided with the consumable.
The consumable reader is a component that can accept the information associated with the consumable and transmit it to the controller of the appliance. The consumable reader can be a device integrated with the appliance or a separate device that can be coupled, either by a hardwire connection or wireless connection, to the appliance for communication with the appliance. Examples of consumable readers include, but are not limited to, bar code scanners, radio frequency identification (RFID) tag readers, and magnetic strip readers.
The consumable reader communicates the information associated with the consumable to the appliance so that the appliance can optimize its performance for the consumable. An example of employing the consumable and consumable reader is provided in the schematic illustration of
It is contemplated that the consumable will contain information corresponding to a preferred operating cycle for the consumable. In the case of a food item, the information would correspond to a cooking cycle for the consumable. The consumable can also have the ability to identify the appliance and provide an appliance-specific operating cycle. One manner of implementing this is for the consumable to have operating cycles corresponding to a particular appliance or class of appliance. The appliance in which the consumable is used identifies and implements the relevant operating cycle. Another manner of implementation is for the consumable to have an identifier and the appliance has stored or access to a database or table of operating cycles for different consumables. The appliance takes the consumable identifier and looks up the corresponding operating cycle for the consumable.
The information associated with the consumable can be in any suitable form. In one embodiment, the information can be a communication packet that can be directly transmitted to the software architecture, thereby eliminating a need for a central storage of consumables data. In another embodiment, the information can be a key that can be used to direct the appliance to stored consumables data.
It is within the scope of the invention to utilize the consumables without the consumable reader. For example, the consumable can be configured to directly communicate with the appliance or other component on the network without employing an intermediate consumable reader.
The consumables can be supplied by a third-party provider, as in the case of store-bought frozen meals and wash aids for laundry appliances and/or dishwashers, or provided by the user. Leftovers and cooked and uncooked prepared foods are examples of consumables that can be provided by the user. The leftovers and the prepared foods can be placed in a storage container encoded with information related to the leftovers and prepared foods. For example, the information can include re-heat or cooking instructions and an expiration date (i.e., throw away date). When the information includes the expiration date, the appliance, such as the oven or microwave oven, can refuse to re-heat or cook the food if the current date is past the expiration date. Optionally, the appliance can be configured to receive an override command from the user when the user desires to re-heat or cook the food despite the expiration date.
Any suitable material can be used to encode the information, and examples include, but are not limited to, plastic wrap, aluminum foil, pots, pans, microwave-safe containers, container lids, and an adhesive or magnetic strip that can be placed on the storage container. The information can be configured by the person who originally prepared the leftovers and the prepared foods and encoded using any suitable means, such as a personal computer, a magnetic strip writer, and a handheld encoding device. With this configuration, the user can configure the information on the consumable as desired.
Along the lines of the consumables and the consumable readers, another example of an accessory is a recipe book and a recipe book scanning wand. The recipe book can contain various recipes having associated cooking instructions, and the cooking instructions can be extracted by the recipe book scanning wand. For example, the cooking instructions can be extracted from text of the recipe book or hidden or visible encoding. The recipe book scanning wand can then communicate, via hardwire or wireless connection, the cooking instructions to the appliance for execution. In an alternative embodiment, the recipe book can directly communicate with the appliance without employing the recipe book scanning wand.
Another example of an accessory is a commercial laundry credit accessory. The commercial laundry credit accessory can be any suitable device, such as a card with memory and/or a microprocessor (commonly known as a “smart card”) and a dongle. The commercial laundry credit accessory can store laundry operation cycle credits and communicate with the appliance in the form of a commercial laundry appliance, such as at a public laundry facility, via a direct or wireless connection. When the commercial laundry credit accessory has sufficient credits, the appliance will operate and deduct credits from the commercial laundry credit accessory based on the operation of the appliance. Optionally, individual users can purchase the laundry operation cycle credits, or others can purchase the laundry operation cycle credits for gifting purposes. In one embodiment, the laundry operation cycle credits can be purchased at the public laundry facility or remotely, such as via the Internet.
The credit accessory can also be used in combination with the software architecture to track usage and transferring the usage information to a local or remote central system. Price changes and other operating parameters for the laundry can be changed by the credit accessory. The price change can be linked to other information accessible through the software architecture, such as energy costs, for example. The credit accessory can also collect diagnostic information and call for service or alert the owner if there are any pending issues via wired or wireless. The smart card can also be used to supply alternate content to the user interface of the appliance, such as advertisement, for example.
Another example of an accessory is a customized connector that can be used to couple the appliance with another accessory or with another component on the network. The customized connector can be associated with any item, such as a cable or a dongle, that can couple with the appliance, and can be configured to prevent unauthorized, third-party devices, including generic brand replacement parts, from undesirably coupling with the appliance and other components on the network. Thus, the connecting item must have the customized connector to couple with the appliance or other component on the network.
Another group of exemplary accessories relate to energy usage. For example, the accessory can be an energy controller and/or energy monitor, hereinafter referred to collectively as the energy controller. The energy controller can be a separate component on the network that communicates with several appliances and other networked components in the home and also with an energy source, such as an electricity source. The energy controller can monitor the amount of energy used by each of the appliances and can distribute energy among the appliances. The distribution of energy can result in an efficient usage of energy and can also manage energy usage, for example, when the energy source curtails the amount of supplied energy. The energy controller can also control the operation of the appliances so that the operation occurs during non-peak energy usage times, which typically correspond to lower energy costs.
The energy controller can be internally configured for communication with the appliances, or a separate connection accessory, such as a dongle, can be coupled to the energy controller to provide connectivity to the appliances. Similarly, the appliance can be internally configured for communication with the energy controller, or a separate connection accessory 78, such as a dongle, as illustrated in
The energy controller 78 can be connected to an energy supplier by any suitable means, such as, wireless, Internet, power lines, etc. With such a connection, the energy supplier can provide information relevant to the control of the appliance. The energy supplier can also remotely control the appliance in addition to or in lieu of providing information.
Other energy related accessories include a smart breaker, a smart dimmer, and a smart adapter. The smart breaker is described in detail in U.S. Pat. No. 6,988,375, issued Jun. 24, 2006 which is incorporated herein by reference in its entirety.
The smart dimmer is effectively a replacement for a load switch, such as a light switch, having discrete on/off control and can be used in any component on the network, including lights and ceiling fans. The smart dimmer provides the ability to not only switch power on and off but also to vary voltage, such as via triac control or converter/inverter control. The smart dimmer communicates with the energy controller, such as to respond to requests from the energy controller and to notify the energy controller of energy consumption status. By giving the energy controller additional control over the component associated with the smart dimmer, the energy controller has more capability to achieve target energy consumption without disruption to the user. Furthermore, in the event of an emergency energy curtailment, the energy controller can communicate with the smart dimmer to dim or shut off the lights or other component associated with the smart dimmer. The smart dimmer can also have associated sensing capabilities to feedback to the energy controller measurements of watts and power-factor.
The smart adapter is functionally similar to the smart dimmer but serves as a replacement for a common wall outlet. By replacing the common wall outlet with the smart adapter, which can communicate with the energy controller in a manner similar to the communication between the smart dimmer and the energy controller, “dumb” components, such as water heaters, that typically function in off/on modes can be plugged into the smart adapter and converted for use on the network and for operation at varying voltages. As a result, the components with the smart adapters can participate in energy curtailment programs and can communicate energy usage information to the energy controller.
Other examples of accessories relate to servicing the appliance. In one embodiment, a remote service center can communicate wirelessly with the appliance in the home. As a result, the remote service center can monitor the appliance, including low level components of the appliance, either passively or actively, and diagnose failures of the appliance. An example of passive monitoring of the appliance is illustrated in
If information not available on the internal network of the appliance is needed for diagnosis, the remote service center 80 can use the DAQ, which is described in more detail in the aforementioned and incorporated PCT patent application to retrieve information available in memory of the associated appliance componentry for analysis of a problem or for searching for a problem.
If in addition to passive monitoring, the remote service center 80 determines the need to control and test the low level components of the appliance 12, the remote service center 80 can actively monitor the appliance 12. To actively monitor the appliance 12, the remote service center 80 can put the appliance 12 in a development state, which is described in more detail in the aforementioned and incorporated PCT patent application and priority application. In the development state, the remote service center 80 can communicate with the appliance 12 and actuate the individual components of the appliance, such as heaters, valves, and motors, to facilitate making a diagnosis. According to one embodiment, for the appliance 12 to enter the development state, the appliance 12 must be in an attended mode. In the attended mode, a responsible person must be present at the appliance to ensure that the actuation of the individual components of the appliance 12 does not harm anyone in the vicinity of the appliance 12. The responsible person can be the user of the appliance 12 or any other person deemed responsible. The presence of the responsible person can be confirmed in any suitable manner, such as by communication between an identification card of the responsible person and the appliance 12 or by the responsible person actuating a key press on the appliance 12.
As an alternative, the appliance can be monitored and diagnosed by an individual, such as the user, in the home with the aid of a service accessory rather than employing the remote service center. In this scenario, an automated service system replaces the remote service center. The service accessory can be any suitable device, such as a dongle, configured to communicate, either via a wired connection or wirelessly, with the appliance and with the automated service system.
An example of self-servicing the application using the automated service system and the service accessory is illustrated in
Other examples of accessories relate to home automation. Home automation systems are systems with a control center configured to control multiple objects, such as lights, drapes, blinds, thermostats, audio/video components, and security systems, within a home. Typical control centers are in the form of a monitor, such as a touchpanel monitor, or a remote control with a customized keypad. With the software architecture, the appliance can be integrated with the home automation system. In one embodiment, the appliance can be added to an existing home automation system whereby the appliance can be controlled, monitored, etc. from the control center. The appliance can optionally communicate with the control center via a wireless device coupled to the appliance. Alternatively, the appliance can be used as the control center. For example, a kitchen is generally a centralized location in the home, and one of the appliances, such as a refrigerator, in the kitchen can include the control center. In this example, the control center can be a monitor integrated into a door of the refrigerator.
By combining the appliance and the home automation system, several synergistic features become feasible. For example, when a fire alarm or smoke detector of the home automation system detects a fire or smoke, the combined appliance/home automation system can take appropriate actions, such as turning off an oven and cooktop, turning off HVAC systems, turning on lights, and shutting off gas supply. In another example, the user can set the combined appliance/home automation system in a vacation mode. Upon departure and during the vacation, the combined appliance/home automation system can take appropriate actions, such as shutting off water supply, turning off water heaters, increase refrigerator temperature, enable alarms, and setup an automatic telephone call to police if the refrigerator door opens. On return, the combined appliance/home automation system can take appropriate actions, such as turning on water supply, turning on water heaters, decrease refrigerator temperature, and disable alarms.
As another example, the combined appliance/home automation system can provide notifications to the user for time management benefits and peace of mind. Notifications for time management benefits can include, but are not limited, to fabric/dish washing complete, fabric/dish drying complete, microwave defrost complete, turn food for microwave defrost, oven pre-heat complete, and food cooking complete. Upon receiving the notification, the user can immediately attend to the corresponding appliance to remove the fabric load, dish load, food, etc. rather than spending the time to periodically having to check whether the operation cycle is complete and possibly delaying initiation of another operation cycle. Notifications for peace of mind can include, but are not limited to, refrigerator door ajar, freezer door ajar, water filter operational, oven left on, cooktop left on, basement humidity level satisfactory, air filtration system functioning, air quality index, boil over on cooktop, and grill flame exceeding limit.
The notifications can be provided to the user on the control system or a remote device that can be used outside the home. Examples of remote devices include, but are not limited to, a cellular phone, a key fob, and a pager/buzzer. The remote device can be configured with the software architecture for communication with the appliance or other component on the network.
Another example of an accessory is a network binder. The network binder is a device that binds nodes on a wireless network to the network by assigning an identical unique network ID to each node. Binding allows nodes that are within communication range of each other to be bound together to create private networks and separate the nodes from other nodes that are also within communication range but not part of the network. The network binder can be useful when there are multiple networks within range of one another, as in a neighborhood or an apartment building. The private network prevents communications from being inadvertently transmitted between networks, which would prevent unexpected interactions. The network binder of the present application can be a wireless device that is solely used for binding appliances or other components in a relatively short range of the network binder. For example, the network binder can have a limited transmission range of about three to four feet to ensure that the target appliance or other component becomes bound to the network when the network binder is operated. An exemplary network binder 100 is illustrated in
Another example of an accessory is a remote user interface. The remote user interface is a user interface that can communicate with one or more appliances and can be positioned remotely from the appliances with which the remote user interface communicates. For example, the remote user interface can be positioned in a central location in the home or can be portable within the home. The remote user interface can provide many, if not all, of the functions associated with a traditional user interface of the appliance and can include additional functionalities. The remote user interface can have any suitable form, such as a monitor, including a touchpanel monitor 110, as illustrated in
Another example of an accessory is an appliance monitor. The appliance monitor, which can be a device integrated with or separate from the appliance, monitors and records operational data associated with the appliance. The appliance monitor can monitor one appliance or a plurality of appliances. Optionally, the appliance monitor can include a display for displaying an operational status of the appliance and can be integrated with the remote user interface described above to also provide the ability to issue commands to the appliance. Furthermore, the appliance monitor can optionally be configured to transmit the operational data associated with the appliance to another device, such as a personal computing device or an intermediate storage device, such as a dongle.
In an example illustrated in
Other examples of accessories relate to servicing the appliances. If the appliance experiences a failure that requires a service person to visit the appliance in the home, the service person can couple a personal computer or other portable computing device to the appliance using a smart cable 120 or a smart wireless connector 122. As shown schematically in
Additional service-related accessories include a central collector 130 and a local collector 132, which can implement the same service-related functions previously described. Referring to
The central collector 130 can also be used for aggregation of customer usage data. The customer usage data can be sold to third parties and can be used in customer studies to gain insight to customer usage patterns and preferences. As another option, the central collector 130 can be used for benchmarking. The operational data associated with the appliance can be aggregated and compared to benchmarks or used to generate benchmarks related to appliance performance. When the operational data is compared to a benchmark, and the comparison indicates a degradation of appliance performance, the user can be alerted to the decrease in performance.
A derivative of the central collector 130 is a black box recorder. The black box recorder can function similarly to the central collector 130 but is constructed such that it cannot be destroyed or at least retains the operational data associated with the appliance in case of a fire or other event potentially destructive event to the appliance or the home. The operational data can possibly be used by insurance companies and investigators to assess the cause and effects of the destructive event.
Referring now to
The local collector 132 can be implemented using the service accessory 90. Either of the local collector 132 or the service accessory 90 can be interfaced with the electrical system of the appliance and with either the appliance or with a service tool (accessory) to perform enhanced diagnostics and performance analysis of the appliance. Exemplary uses would be to validate that each output device (when acutated) consumes the expected electrical consumption, and to realize certain performance or failure conditions by evaluating information contained in the electrical bus (example frequency analysis).
Another example of an accessory is an appliance coupler. The appliance coupler can be any device, such as a cable connector or a device capable of wireless communication, that enables direct communication between appliances. As a result, the coupled appliances can communicate with each other, which can be especially beneficial when the operation of one appliance affects the operation of another appliance. For example, a washing machine and a dryer can be coupled together by the appliance coupler, and the operational cycle of the dryer can be selected based on the operational cycle employed by the washer.
Another example of an accessory is a sales demo accessory. As shown by example in
The sales demos can be downloaded to the sales demo accessory 140 from a web site associated with the manufacturer of the appliance 12 and updated periodically to reflect current marketing strategies of the manufacturer of the appliance 12. By differentiating the appliance 12 from other appliances on display in the retail store, the sales demos can help improve sales of the appliance 12. The sales demos can be customized according to the retail store and trade partners of the manufacturer of the appliance 12. Furthermore, by locating the sales demos on the sales demo accessory 140, code for sales demos that would traditionally reside on the appliance 12 can be removed from the appliance 12, thereby reducing development time and cost of the appliance 12.
Another example of an accessory is a cellular phone, which can be used for communication with the appliance 12. In general, today's cellular phones have several integrated technologies, including networking capabilities (Including Bluetooth), Internet connection capabilities, color user interfaces, premium sound, voice recognition capabilities for automatic dialing, and tactile feedback (e.g., vibration), and these integrated technologies can be utilized in conjunction with the appliance 12. Referring to
Examples of using the cellular phone include, but are not limited to, remote diagnostics and service, interactive audio, voice control, and enhanced user interface. For remote diagnostics and service, the cellular phone discovers the appliance and downloads diagnostic tests from the Internet. The cellular phone can locally execute the diagnostic tests through the software architecture and Bluetooth (or other communication means). After the diagnostic tests are complete, the cellular phone can upload testing results to the Internet for diagnosis. For interactive audio, the cellular phone discovers the appliance and downloads custom audio files from the Internet. The cellular phone can register with the appliance for key status events through the software architecture and Bluetooth (or other communication means). When the key events occur on the appliance, the cellular phone can automatically play the appropriate audio file to provide enhanced feedback. For voice control, the user can input voice commands into the cellular phone, and the cellular phone can convert the voice command to a command for the software architecture and transmit the command over Bluetooth (or other communication means). Finally, for the enhanced user interface, a user interface application, which can be downloaded from the Internet, can be executed on the cellular phone. The user interface application can take advantage of the color user interface, the premium sound, and the tactile feedback on the cellular phone. The control of the appliance 12 via the enhanced user interface and feedback from the appliance 12 to the enhanced user interface can occur locally through the software architecture and Bluetooth (or other communication means).
Another example of an accessory is an audio communication accessory. The audio communication accessory is a device that communicates with the appliance or other component on the network having a traditionally visual user interface and adds audio capabilities to the user interface. The audio communication accessory can also be used with any appliances or other component on the network that does not have a user interface. By incorporating the audio communication accessory, the appliance or other component on the network can audibly communicate information related to the appliance or other component to the user, and, optionally, the user can audibly communicate commands and the like to the appliance or other component through the audio communication accessory. Audible communication can be especially beneficial to users having a physical disability, such as blindness or mobility issues where it is difficult for the user to move within visual range of the appliance or other component. The audible communication can be voice (i.e., speaking) or a variety of sounds, such as beeping, alarms, Morse code, songs, etc.
Examples of the information communicated by the audio communication accessory to the user can include, but are not limited to, notifications concerning an operational status of the appliance or other component, such as fireplace on, security system activated, carbon monoxide alarm activated, appliance door open, temperature limits exceeded, leakage, filter requires changing, end of operation cycle, cooktop burner on, oven pre-heat complete, fabric/dish washing complete, water temperature, circuit breaker blown, energy usage status, and energy usage exceeds preprogrammed limit. Examples of the information communicated from the user to the audio communication accessory can include, but are not limited to, commands concerning an operational status of the appliance or other component, such as call or otherwise contact emergency personnel, turn on outdoor spa, turn on outdoor sprinkler system, extend dryer operation cycle, and initiate operation cycle.
Other examples of utilizing the audio communication accessory follow. In one embodiment, the audio communication accessory can be used as an event calendar where the user can record an event, such as a reminder to take medicine, and the audio communication accessory can play the reminder at the appropriate time. As another example, the audio communication accessory can communicate with a source of weather information, such as via the Internet, and notify the user of weather conditions on demand or at preprogrammed times. It is also contemplated that the audio communication accessory can be used in conjunction with tracking devices to locate items in the home. For example, a set of keys can be equipped with the tracking device, and the audio communication accessory can communicate to the user the location of keys when the user cannot find the keys. The audio communication accessory can also be employed as an intercom system where multiple users can communicate with one another through the audio communication accessory. In this scenario, the users can each have the audio communication accessory, or the single audio communication accessory can interface with another device to enable two-way communication. In another embodiment, the audio communication accessory can be used to place the appliances or other components on the network in a “sleep mode,” which can include, for example, shutting off lights, lower heating temperature, and activating the security system, when the user provides a sleep mode command as the user is going to bed. As another example, the audio communication accessory can be used in conjunction with the sales demo accessory described above to audibly enhance the sales demos for the appliance. The customer could effectively talk to the appliance and vice-versa, thereby improving the customer interaction with the appliance at the retail store. It is also contemplated that the audio communication accessory can be used in conjunction with an outdoor audio system and/or outdoor camera whereby the user can audibly communicate with a person who has activated a doorbell and/or view, such as via a display on a cellular phone, images of the person who has activated the doorbell. As another example, the audio communication accessory can communicate with a computing device or telephone system and notify the user when the user has received new electronic mail messages and voice mail messages.
The audio communication accessory can also be used to implement an audible use and care guide associated with the appliance. The audible use and care guide can be considered a replacement or addition to a conventional user manual that a user must read. Listening to the audible user and care guide can be more convenient, more efficient, and more easily understood than reading the conventional user manual. The audible use and care guide can include content traditionally included in the conventional user manual, such as explanations of the operational cycles and/or features of the appliance, troubleshooting information, and recommendations for care of different types of items used in the appliance (e.g., laundry, dishes, foods). As an improvement, the audible use and care guide can be configured to communicate information related to operation cycles selected in real-time by the user. Thus, as the operation cycle is being selected by the user, the audible use and care guide can inform the user, for example, how to use the operation cycle, what the operation cycle is meant for, what options are available for the operation cycle, and steps for programming the operation cycle.
The audible use and care guide can be activated prior to using the appliance for the first time or at any time the user requires assistance. In one embodiment, the audible use and care guide can be always accessible and activated by the user actuating a button on the appliance or voice activation via the audio communication accessory. The user can optionally interact with the audible use and care guide, such as by asking questions or instructing the audible use and care guide to skip information not needed by the user. According to one embodiment, the audible use and care guide can implement multiple, selectable modes for various use scenarios, such as whether the appliance is on the floor of a retail store as a sales demo, for a new appliance in the home, for a new user, or for an experienced user. The amount of information and level of detail in the information provided to the user can depend on the experience of the user. The audible use and care guide can be disabled if it becomes annoying or can be reconfigured.
The audio communication accessory can optionally include tactile feedback, such as vibration, which can be especially useful for users having a hearing disability. The tactile feedback can be used in conjunction with or as an alternative to the audio communication. The user can wear or carry a portable device that provides the tactile feedback.
Regardless of the type of accessory, the software architecture can be configured such that the accessory must present electronic credentials (i.e., authentication) before communicating with the appliance. Requiring the electronic credentials prevents unauthorized communication between the accessory and the appliance, thereby avoiding undesirable control of the appliance by the accessory. The security techniques of the incorporated International Patent Application No. PCT/US2006/022420 work well for the software architecture, including a firewall. Other possible authentication mechanisms can be used to gain access to the firewall. These can include a hardware signal, a sequence of messages, a handshaking algorithm, or a standard encryption algorithm for example. Any standard authentication method can be used to gain access to the firewall, as long as it is possible to verify that a client or accessory is authorized to gain access.
In addition, the disclosed three basic levels of access to the firewall (access, deny, and temporary access) can be expanded as necessary to allow different levels of access to different clients. These access levels each have a unique authentication (such as a unique password) and can be associated with different user roles such as a service technician, factory tester, developer, or consumer. Different levels of access allow different sets of commands to be executed by the client. These levels can be temporary and time bound or permanent once authentication is successfully completed.
The implementation of the firewall can vary as needed. The disclosed implementation uses a table of protected commands to validate against clients. Any number of data structures can be used to validate a user with the allowed commands for an access level of the firewall. In the end, a firewall must only allow access to commands to the appropriate clients that have successfully been authenticated.
Each client node 1002, 1004, 1010, 1012 comprises a software architecture driver (SA driver) 1016 for exchanging messages with any node having a software architecture (SA) 1018 thereon. The nodes on any given network are in operable communication with the other nodes in that network and are optionally in communication with the nodes present on other networks.
The appliance 1000 further comprises at least one node 1020 having the SA thereon. The second appliance 1006 will also likely have a node with the SA on it, and may have one or more clients as well. The first network 1030 also comprises the node 1020.
Couplers 1040, 1042 are special devices that connect to the appliance and/or to a network and/or to two or more networks and communicate therebetween. Each coupler can comprise all the functionality of a node, and each node can comprise all of the functionality of a coupler. In this embodiment, the coupler 1040 couples the second network 1050 to the third network 1052, and can function as a node on each network. The coupler 1042 couples the second network 1050 to the first network 1030. It could also be considered as coupled to the appliance 1000.
Either of the couplers 1040, 1042 can propagate discovery messages issued by the SA or an SA driver across the networks in order to enable the SA and SA drivers or their coupled arbitrary software components to develop references to identifiers of functionality for the different nodes. Each coupler 1040, 1042 can have a routing table stored in a memory for enabling communication between nodes on different networks. The memory can also store identifiers identifying the functionality of each node. The identifiers can be linked to the routing information held within the routing tables so that when a message comprising an identifier is sent to either of the couplers 1040, 1042, the coupler receiving the message can send the message to the appropriate next node.
Each node can comprise a unique combination of software elements. The software elements on any given node include at least one of the SA and an SA driver. The SA driver enables a node to communicate with the SA. The SA inherently includes an SA driver or a variant of the SA Driver. Each node comprising the SA can communicate with other nodes comprising the SA. However, a node can have both the SA and separate SA driver thereon. Each node must also include a suitable communication protocol or communication protocol driver for the respective network type to which it is coupled. An exemplary protocol is the WIDE network protocol 1062, a proprietary appliance network protocol utilized by Whirlpool Corporation. For a client not having WIDE network protocol that needs to communicate WIDE messages (e.g., external client 1004), a WIDE driver 1064 can be used. A port driver 1072 couples the external client 1004 to the network 1050.
Each node can also comprise an arbitrary software component 1060. The couplers 1040, 1042, for example, may not. The SA driver 1016 is a software element configured to allow an arbitrary software component to communicate with the SA 1018 over at least one network. An arbitrary software component is any software component or subcomponent that performs a useful function. Examples include, but are not limited to, a communication driver, an application, a user interface, a control algorithm, message routing, a control for an operational cycle, message handling, data storage, data transformation, data referencing, and software that instructs other software. The SA driver 1016 can receive and at least partially interpret messages from the SA and/or from another SA driver, which are specified as feedback events. In some instances, the SA driver 1016 can also send command messages to the SA 1018. In this respect, the external clients 1002, 1004 can have full capability act as an accessory to communicate with and to enhance or alter the operation of the appliance.
It will be understood that any or all of the external clients 1002, 1004, the couplers 1040, 1042, and the internal clients 1010, 1012 can be physical devices that have a processor, a memory, software, circuitry, and some source of power. In the general sense, they are coupled to transmission media and are preferably configured to take information from the memory and with the processor and the circuitry, produce a signal representing that information in the transmission media. When the information includes an identifier in memory, the node or client is discoverable by other nodes connected via the transmission media.
Discovery is a process by which a first node in communication with at least one coupled network sends discovery messages to the network or networks. Discovery messages generally comprise at least some query information specifying what the sender of the discovery message seeks. The information sought can be information such as another node, an appliance, a client, an arbitrary software component, a device comprising a node, a coupler, or one or more of a plurality of software elements on any node.
A discovery confirmation message is a reply message sent to the sender of a discovery message. Discovery reply messages typically comprise confirmation information and identification information. The confirmation information is an acknowledgment in the form of a positive or a negative response. The identification information is information enabling the sender to send subsequent messages to that which has been discovered.
Where more than one network is connected by a coupler, such as couplers 1040, 1042, a message received by the coupler from one network can be propagated and sent to the second network. The coupler may create a second separate message with the same information compatible for a second network, but together, the first and the second messages are considered a single propagated message, even though they may be literally two messages. A propagated discovery message, then, is a discovery message that is propagated to a receiver. A coupler may be configured to inspect propagated messages to prevent propagation of a circular message, i.e, a sent message that is also unknowingly received by the sender on a second network to which the sender is coupled. At least the coupler 1040 may have a routing table including proxy identifiers of the functionalities of the second node. As well, the coupler 1042 may have a routing table including proxy identifiers. A discovery message sent by the node 1020 is received by the coupler 1042, which evaluates the message in accord with the routing table and propagates the message to the next node, coupler 1040. Similarly, the coupler 1040, evaluates the propagated message in light of the routing table, and propagates the message to the next node in line, which may be the second node.
See, for example,
In this scenario, the source 2010 sends a discovery message over the network 2012 seeking any consumer of resources to which the source wants to send information. The coupler 2006 receives the discovery message, translates the message, if necessary, and propagates the discovery message to the next nodes over the network 2008, including coupler 2000. Coupler 2000 receives the discovery message, translates the message, if necessary, and propagates the discovery message to the next nodes over the network, including the appliance 2002. The relevant nodes in the appliance 2002 evaluate the message and determine a discovery reply message, and send respective replies. Here, we assume at least one reply is positive.
The discovery reply message is received by the coupler 2000, which populates its routing table and sends it to the coupler 2006, which populates its routing table and sends it to the source 2010 in accord with the foregoing process. Each node retains the relevant identifiers so that subsequent message can be communicated without repeating the discovery sequence. As well, those nodes with memory, such as the couplers, can be configured to save messages.
With this structure, a source of information about a resource such as electricity, hot water, gray water, gas, water, replaceable parts, or other consumables, can request a change in the operation of the appliance based on the information. For example, if an electric utility is facing a brownout, a source of information about the electricity can request that an electric dryer not commence an operation for a period of time. Similarly, a source of consumables, such as filters or spare parts, can ascertain from an appliance the status of the consumable and send information about the timing and availability of replacement.
Likewise, when an arbitrary software component configures the cycle engine through communications, the arbitrary software component can first interrogate, through useful communications, the appliance to ascertain its identification whereby that identification is used with the data portion table to retrieve the appropriate data about the cycle structure to be built. The arbitrary software component can then send messages to the API of the cycle engine to build the appropriate cycle data structure for the appliance.
Alternatively, any client having an arbitrary software component can find or discover data about the cycle structure at (4). Then, the arbitrary software component can build a cycle structure in conjunction with the cycle engine, configured to receive configuration messages as at (5). As before, all messages can be optionally routed through an embedded virtual router at (6).
Further explanation of the consumable reader accessory is found in
Information 304 associated or related to a consumable can include data about the consumable itself, the data portion of a cycle structure, data about a response to a query message from the appliance or other accessory, commands associated with an operating cycle, parameters of an operating cycle such as personal preferences of a user (e.g., doneness or crispiness preferences) or environmental parameters (e.g., altitude), and data about the appliance, accessories or components thereof. The information 304 can also include the quantity of consumable pieces, quantity by volume or by weight, date of manufacture, manufacturer, data about its transit from manufacture, distributor, market, and consumer, data about the temperature during transit, nutritional information like calories, fat grams, % daily allowance of essential vitamins and minerals, a list of medical conditions under which a consumable should not be consumed, data about the relationship between the consumable and known diets, known medical conditions, and known reactions to known medications, and the like. The information 304 can further include appliance or component identifier data in accord with the messaging protocol of the software architecture.
The information 304 can be stored in a memory within a node internal to the appliance or within the consumable reader itself, or to removably coupled memory within the consumable reader or to a surface on consumable holder 314. A consumable holder can be an item such as a bag, a box, a carton, a bottle, a can, a bowl, a dish, a plate, or any other rigid or semi-rigid body suitable to contain a substance. The information 304 can also be stored in a removably coupled article comprising memory attached to a surface of the consumable holder or to the consumable 316 itself. The latter would be a consumable enabled to store retrievable information, e.g., food with information directly etched into the food using edible ink. The information 304 can also be stored in a consumable data pod 318 which is article comprising memory enabled to store retrievable information about a consumable. Preferably, the consumable data pod 318 is consumed by the process also operating on the consumable without degradation to the consumable or to the overall objective of the relevant cycle of operation.
In one embodiment, the appliance 310 or accessory 312 detects the coupling of the consumable reader 300, queries the consumable reader for the information 304, and creates an appropriate cycle data structure according to
In a second embodiment, the consumables reader 300 is given or infers a start command by which it selectively retrieves data about an operating cycle, changes the mode of a software operating layer of the appliance, and commands the alternate software layer of the appliance according to the information to retrieve data about an operating cycle. Alternatively, the consumables reader 300 retrieves data about an operating cycle and establishes communication with the appliance 310 or accessory 312 and creates a cycle data structure. Regarding the alternative, the cycle data structure can be created in the memory of the consumables reader 300; or, the consumables reader 300 comprises an arbitrary software component 322 of an accessory which creates the cycle data structure by communication with the API of the cycle engine, using, for example a virtual router and also using discovery messages to establish a reference to the cycle engine's API through the virtual router.
In a third embodiment, the appliance 310 or accessory 312 selectively detects the coupling of the consumable reader 300, which is given or infers a start command. Upon the selected event, the cycle of operation of the appliance will be in communication with the information 304. This direct communication with the information is facilitated by the consumable reader acting as a smart coupler, or by memory within a node in communication with an executing operation cycle previously populated by the consumable reader acting as a smart coupler.
Further explanation of message binding may be helpful with respect to the incorporated disclosure of International Patent Application No. PCT/US2006/022420. The software architecture preferably can support and promote both asynchronous and synchronous data collection. Asynchronous memory polling, for example, is available in the Core API (API ID=1). There are at least two available embodiments of synchronous data collection.
Understanding the invention related to synchronous data collection is helped by an understanding of the concept of bounded updates. Bounded updates are events that are grouped together as a snapshot of the appliance state taken during the same scan of the host microprocessor's Main( ) loop execution. The appliance control main loop will allow for an iterative update of feedback variables that are registered with the DAQ API (e.g., every 25 ms). Each registered variable is monitored and only those that change value according to their memory monitor change operator are broadcast as updates to the client. When updates are in the process of being broadcast, no new updates are allowed in order to preserve the snapshot in time.
In the first embodiment, a snapshot is communicated to the client using the MMP flag in Byte 2 of the software architecture 10 header as shown in the application protocol 28 in FIG. 4 of International Patent Application No. PCT/US2006/022420. While the MMP of 28 is true, more messages are pending for the snapshot. When MMP is false, the current message is the last message in the snapshot. Therefore, if the first message of a snapshot is the only message in that snapshot, MMP will be false.
The example in FIG. 9 of International Patent Application No. PCT/US2006/022420 illustrates a bounded command (Cycle+Temperature+MMP) with acknowledgements, followed by two consecutive bounded updates. Where bounded refers to elements of protocol which indicate to the receiver that more messages are coming from the source and that data processing by the application logic of the receiving component should be delayed until the bounding indicators of the protocol within the packet structure 28 (MMP bit 7) indicate a complete transaction at which time data processing by the application logic is permitted. The bounded command is shown by reference numeral 42 and the two consecutive bounded updates are shown by reference numbers 44 and 46, respectively. Notice that updates do not begin until bounded command execution is complete, providing the client the ability to filter away transient feedback data. Bounded commands are provided by the same mechanism, MMP found in 28, as bounded updates in order to provide applications a greater level of control.
The example of FIG. 9 in International Patent Application No. PCT/US2006/022420 is conceptual. The actual mechanism is MMP found in 28. However for illustrative purpose, the bounded command begins with an initial “begin” command initiator (MMP set) and includes commands to set a washer cycle to wash, a recipe status to ready, a water temperature to medium, again a recipe status to ready, and finally a cycle start indicator, followed by a command terminator (MMP unset). It can be noted that, in FIG. 9, updates (such as by eventing) are disabled to prevent updates from happening before the bounded command is complete. In addition, a “process command” indicator is shown periodically throughout the bounded command processing in the appliance 12 to illustrate the portions of the command issued from the client 16 through the internal communications network 14 are processed.
In the bounded updates 44, the updates are once again enabled (since they were disabled at the beginning of the bounded command 42) to allow the appliance 12 to report its status to the client 16. In the example shown in bounded updates 44, the acknowledgment state is shown to ready, the cycle is reported as wash, the state is reported as running, the basket is reported as fill, the pump is reported as on, and the temperature is reported as medium. Again, beginning and terminating indicators enclose the bounded update 44. These beginning and terminating indicators can be reported by use of the flag, MMP, in the application packet structure 28 as discussed in FIG. 4 of International Patent Application No. PCT/US2006/022420 or another method which would be apparent to one skilled in the art of network protocol.
In the bounded update 46, the basket is reported as agitate, the pump is reported as off and the motor is reported as on. Again, beginning and terminating indicators (MMP) enclose the bounded update 46. Without the beginning and terminating indicators (MMP), the client cannot deduce a relationship between the updates from the appliance. However, with beginning and terminating indicators (MMP), the client can deduce a relationship between the events.
The second embodiment of synchronous data collection is shown in
This technique can also be used to batch commands, as shown in
While the invention has been specifically described in connection with certain specific embodiments thereof, it is to be understood that this is by way of illustration and not of limitation, and the scope of the appended claims should be construed as broadly as the prior art will permit.
1. A network comprising:
- an appliance configured to perform a cycle of operation to complete a physical domestic operation on a consumable, the appliance having: a communication network comprising a plurality of interconnected nodes configured to communicate across the communication network; a plurality of components, each component associated with at least one of the plurality of nodes; and a consumable reader configured to obtain information from the consumable and having at least one node in communication with the communication network; and a software architecture comprising a plurality of software elements and configured to generate a plurality of messages, with at least one of the software elements residing in each of the components and in the consumable reader and configured to enable transmission of at least one of the plurality of messages among the components and between the consumable reader and the components to communicate data related to the consumable from the consumable reader to the appliance.
2. The network of claim 1 wherein the information comprises operating cycle data directly usable by the appliance.
3. The network of claim 2 wherein the information is a communication packet that is communicated to the software architecture.
4. The network of claim 1 wherein the information is a communication packet that is communicated to the software architecture.
5. The network of claim 1 wherein the software architecture includes memory and the information is a key to direct the appliance to any data about the consumable stored in the memory.
6. A network comprising:
- an appliance able to perform a operation cycle related to a consumable;
- a consumable; and
- information associated with the consumable;
- wherein the appliance is configured to receive the information for use in the operation cycle.
7. The network of claim 6 wherein the information comprises operating cycle data directly usable by the appliance.
8. The network of claim 7 wherein the information is a communication packet that is communicated to the appliance.
9. The network of claim 8 wherein the information is on the consumable.
10. The network of claim 6 wherein the information is a communication packet that is communicated to the appliance.
11. The network of claim 10 wherein the information is on the consumable.
12. The network of claim 6 where the consumable has packaging and the information is on the packaging.
13. The network of claim 6 further comprising a consumable reader configured to obtain the information and communicate the information to the appliance.
14. The network of claim 13 wherein the information is a communication packet that is communicated to the appliance.
15. An assembly comprising:
- a consumable for use in an appliance configured to perform an operation cycle related to the consumable and to receive messages;
- information associated with the consumable and configured for communication to the appliance in at least one message; and
- an encoder to encode the information on one of the consumable and packaging for the consumable whereby the appliance can perform an operation cycle based on the information upon receipt of the at least one message.
16. The assembly according to claim 15 wherein the encoder is one of a personal computer, a magnetic strip writer, and a handheld encoding device.
17. The assembly according to claim 15 wherein the information is encoded on material removable from the consumable.
18. The assembly according to claim 17 wherein the material is one of plastic wrap, aluminum foil, pots, pans, microwave-safe containers, container lids, an adhesive strip, and a magnetic strip.
19. A method of providing an operation cycle for an appliance comprising:
- preparing a set of commands to form an operation cycle; and
- encoding the operation cycle to an operation cycle component wherein the operation cycle component is information associated with a consumable having means to transmit the information to an appliance capable of receiving information;
- whereby to configure the appliance to perform the operation cycle.
20. The method according to claim 19 further comprising the step of providing a consumable reader configured to obtain the information and communicate the information to the appliance.
21. A consumable for use in an appliance configured to perform an operation cycle related to the consumable and to receive messages, the consumable comprising encoded information associated therewith and configured for direct communication to the appliance by message for use by the appliance to perform an operation cycle on the consumable.
22. The consumable according to claim 21 wherein the information is a communication packet.
23. The consumable according to claim 21 wherein the information comprises operating cycle data directly usable by the appliance.
24. The consumable according to claim 21 wherein where the consumable has packaging and the information is on the packaging.
Filed: Oct 5, 2015
Publication Date: Jan 28, 2016
Inventors: MATTHEW P. EBROM (HOLLAND, MI), WALLACE J. ELSTON, III (PAW PAW, MI), MARK E. GLOTZBACH (GRANGER, IN), LAYNE E. HEILMAN (OSCEOLA, IN), ANTHONY E. JENKINS (STEVENSVILLE, MI), STEPHEN D. KREFMAN (PAW PAW, MI), RICHARD A. MCCOY (STEVENSVILLE, MI), JAMES P. O'SHAUGHNESSY (MEQUON, WI), RANDY A. VOSS (ST. JOSEPH, MI)
Application Number: 14/874,682