Dispensers, dispenser systems, and refill units configured for autonomous firmware / software updates

Abstract

Disclosed herein are exemplary embodiments of a dispensing system, a dispenser, a refill unit, and a method for autonomously updating firmware and / or software of a dispenser. The exemplary dispenser includes a processor, a dispenser memory, firmware for controlling one or more operations of the dispenser, and a receptacle for receiving a refill unit. A reader for reading information from a near field communication tag is also included. The refill unit includes a near field communication tag affixed to the refill unit. A memory is located on the near field communication tag. Data is stored in the memory. The data includes firmware update instructions. When the refill unit is placed in the receptacle, the reader reads the data. The processor updates the dispenser firmware according to the firmware update instructions read from the near field communication tag on the refill unit.

Description

[Technical field]

[0001] Related Applications This application claims priority to and the benefit of U.S. Provisional Patent Application No. 63 / 043180, entitled DISPENSERS, DISPENSER SYSTEMS AND REFILL UNITS CONFIGURED FOR AUTONOMOUS FIRMWARE / SOFTWARE UPDATES, filed June 24, 2020, which is incorporated by reference in its entirety.

[0002] The present invention relates generally to non-contact dispensers and dispenser systems, and more particularly to non-contact dispensers and dispenser systems configured to receive autonomous firmware / software updates, and refill units having autonomous firmware / software update instructions. [Background technology]

[0003] Some touchless dispensers for soap, sanitizer, and lotion utilize firmware and / or software to control various functions related to operating the dispenser, collecting data, and sharing data. Over time, thousands, if not millions, of touchless dispensers may be distributed and installed in offices, hospitals, restaurants, retail stores, restrooms, etc. around the world. Occasionally, dispensers have firmware / software bugs or other issues that are discovered and ideally would be repaired or updated. Typically, dispensers are unable or never updated due to the sheer number of touchless dispensers installed around the world and the thousands of different locations in which they are installed making such issues extremely difficult and / or prohibitively costly to correct. Summary of the Invention [Means for solving the problem]

[0004] Exemplary embodiments of a dispensing system, a dispenser, a refill unit, and a method for autonomously updating firmware and / or software of a dispenser are disclosed herein. The exemplary dispenser includes a processor, a dispenser memory, firmware for controlling one or more operations of the dispenser, and a receptacle for receiving a refill unit. A reader for reading information from a near field communication tag is also included. The refill unit includes a near field communication tag secured to the refill unit. A memory is on the near field communication tag. Data is stored in the memory. The data includes firmware update instructions. When the refill unit is placed in the receptacle, the reader reads the data. The processor updates the dispenser firmware according to the firmware update instructions read from the near field communication tag on the refill unit.

[0005] Another exemplary dispenser includes a processor, a dispenser memory, software for controlling one or more operations of the dispenser, and a receptacle for receiving a refill unit. A reader for reading information from a near field communication tag is also included. The refill unit includes a near field communication tag secured to the refill unit. A memory is on the near field communication tag. Data is stored in the memory. The data includes software update instructions. When the refill unit is placed in the receptacle, the reader reads the data. The processor updates the dispenser software according to the firmware update instructions read from the near field communication tag on the refill unit.

[0006] Another exemplary dispenser includes a processor, a dispenser memory, logic on the dispenser memory for controlling one or more operations of the dispenser, a receptacle for receiving a refill unit, and wireless communication circuitry for reading information from the refill memory. A refill unit having near field communication circuitry is also provided. The refill unit includes a memory on the near field communication circuitry, and data stored in the memory. The data includes logic update instructions. When the refill unit is placed in the receptacle, the wireless communication circuitry reads the data and the processor updates the dispenser logic according to the logic update instructions.

[0007] An exemplary soap, sanitizer, or lotion refill unit includes a container for holding one of soap, sanitizer, and lotion. A near field communication tag is associated with the container. A refill unit memory is on the near field communication tag. Data is stored in the refill unit memory. The refill unit further includes logic update instructions stored in the refill unit memory. The logic update instructions are configured to perform a logic update on the one or more dispensers when the one or more dispensers interrogate the refill unit memory.

[0008] An exemplary method for updating a dispenser includes providing a refill unit. The refill unit includes a near field communication tag. Data is stored in the near field communication tag. Logic update instructions are stored in the near field communication tag. The method further includes providing a dispenser. The dispenser has a processor, a memory, logic stored in the memory for controlling one or more dispenser functions, and a receptacle for receiving the refill unit. The dispenser further includes wireless communication circuitry for reading data from the near field communication tag. The data read from the near field communication tag includes the logic update, and the processor updates the logic stored in the memory of the dispenser.

[0009] An exemplary method of updating a soap or sanitizer dispenser includes providing a refill unit, securing a near field communication tag, and storing update logic on the near field communication tag, such that when the refill unit is placed in a dispenser having a processor, memory, and dispenser logic stored in the memory for controlling one or more dispenser functions, the update logic stored on the near field communication tag causes the update logic to update the dispenser logic.

[0010] An exemplary method of manufacturing a soap or sanitizer dispenser includes providing a dispenser container, an object sensor, a near field communication reader, a power source, a processor, and a memory. The method further includes storing first logic in the memory for controlling the dispenser, the first logic not enabling the object sensor. The method further includes providing a refill unit having a container, a near field communication tag, and a software or firmware update stored in the near field communication tag. The software or firmware update includes second logic for updating the first logic stored in the memory for controlling the dispenser, the second logic enabling the object sensor.

[0011] These and other features and advantages of the present invention will become better understood with regard to the following description and accompanying drawings. [Brief description of the drawings]

[0012] [Figure 1] FIG. 1 is a schematic diagram of an exemplary embodiment of a dispenser configured to receive autonomous firmware and / or software updates.

[0013] [Diagram 2] FIG. 13 is a schematic diagram of an exemplary embodiment of a replenishment unit having a near field communication tag with firmware and / or software updates.

[0014] [Diagram 3] FIG. 13 is a schematic diagram of an exemplary embodiment of a replenishment unit having a near field communication tag with firmware and / or software updates.

[0015] [Figure 4] 1 illustrates an example embodiment or logic diagram of a method for autonomously updating dispenser firmware and / or software using a refill unit.

[0016] [Diagram 5] FIG. 1 is an exemplary embodiment or logic diagram of a method for preparing a refill unit having a near field communication tag with firmware and / or software updates for autonomously updating dispenser firmware and / or software.

[0017] [Figure 6]FIG. 1 is an exemplary embodiment or logic diagram of a method for manufacturing a dispenser having a sleep or disabled mode and receiving firmware and / or software updates via a refill unit having a near field communication tag with the firmware and / or software updates. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0018] The following include definitions of exemplary terms used throughout this disclosure. Both the singular and plural forms of all terms fall within their respective meanings. Unless otherwise noted, both capitalized and non-capitalized forms of all terms fall within their respective meanings.

[0019] "Circuit communication" as used herein refers to a communication relationship between devices. Direct electrical, electromagnetic, and optical connections, as well as indirect electrical, electromagnetic, and optical connections, are examples of circuit communication. Two devices are in circuit communication if a signal from one device is received by the other device, regardless of whether the signal has been modified by some other device. For example, two devices separated by one or more of the following - amplifiers, filters, converters, opto-isolators, digital or analog buffers, analog integrators, other electronic circuit components, fiber optic transceivers, or possibly satellites - are in circuit communication if a signal from one is conveyed to the other, even if the signal has been modified by an intermediate device. As another example, an electromagnetic sensor is in circuit communication with a signal if it receives electromagnetic radiation from the signal. As a final example, two devices that are not directly connected to each other, but have the ability to interface with a third device, such as a CPU, are in circuit communication.

[0020] Also, as used herein, voltages and values ​​representing digitized voltages are considered equivalent for the purposes of this application, and thus the term "voltage" as used herein refers to a signal, or a value in a processor that represents a signal, or a value in a processor determined from a value that represents a signal.

[0021] A "signal" as used herein includes, but is not limited to, one or more electrical signals, analog or digital signals, one or more computer instructions, bits or bit streams, or the like.

[0022] "Logic" is synonymous with "circuitry" as used herein and includes, but is not limited to, hardware, firmware, software, and / or combinations of each to perform a function or act. For example, based on a desired application or need, logic may include a software-controlled microprocessor or microcontroller, or other programmed logic device. Logic may also be embodied entirely in software. The circuitry identified and described herein may have many different configurations to perform a desired function.

[0023] The values ​​identified in the detailed description are exemplary and are determined as necessary for a particular dispenser and / or replenishment design, and therefore the inventive concepts disclosed and claimed herein are not limited to the specific values ​​or ranges of values ​​used to describe the embodiments disclosed herein.

[0024] FIG. 1 illustrates an exemplary embodiment of a contactless dispenser 100 configured for autonomous firmware and / or software updates. In this exemplary embodiment, the dispenser 100 includes a housing 102. System circuitry 130 is located within the housing 102. The system circuitry 130 may be on a single circuit board or on multiple circuit boards. Additionally, some of the circuitry may not be on a circuit board, but rather may be individually mounted and electrically connected to other components, as desired. In this embodiment, the system circuitry 130 includes a processor 132, a memory 133, an optional header 134, a permanent power source 136, an optional voltage regulator 138, an optional door switch circuitry 140, an object sensor 142, an actuator drive circuitry 148, an optional capacitor bank 145, an optional capacitor control circuitry 146, an optional replaceable power interface receptacle 144, and a reader 170.

[0025] Processor 132 may be any type of processor, such as, for example, a microprocessor or the like. Processor 132 is in circuit communication with header 134. Header 134 is a connection port through which a user can connect to system circuitry 130 to manually program the circuitry, run diagnostics on the circuitry, and / or retrieve information from the circuitry. Header 134 is a physical connection that requires a user to physically connect a device to system circuitry 130.

[0026] The processor 132 is in circuit communication with the memory 133. The memory 133 may include any type of memory, such as, for example, random access memory (RAM), read-only memory (ROM), programmable read-only memory (PROM), electrically programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), or the like, or combinations thereof. In some embodiments, the memory 133 is separate from the processor 132, and in some embodiments, the memory 133 is on or within the processor 132.

[0027] In the exemplary embodiment, a permanent power source 136, such as, for example, one or more batteries, is also provided. The permanent power source 136 is preferably designed so that the permanent power source 136 does not need to be replaced during the life of the dispenser 100. The permanent power source 136 is in circuit communication with a voltage regulator circuit component 138. In some exemplary embodiments, the voltage regulator circuit component 138 provides regulated power to the processor 132, the object sensor 142, the reader 170, and the door circuit component 140. The permanent power source 136 may be used to provide power to other circuit components that require a small amount of power and that will not prematurely deplete the permanent power source 136.

[0028] In some embodiments, the processor 132 is in circuit communication with optional door circuitry 140 so that the processor 132 knows when a door (not shown) of the dispenser 100 is closed. In some embodiments, the processor 132 does not allow the dispenser 100 to dispense a dose of fluid when the door is opened. The door circuitry 140 can be any type of circuitry such as, for example, a mechanical switch, a magnetic switch, a proximity switch, or the like.

[0029] The processor 132 is also in circuit communication with an object sensor 142 for detecting whether an object is present in the dispensing area. The object sensor 142 may be any type of passive or active object sensor, such as, for example, infrared sensors and detectors, proximity sensors, imaging sensors, thermal sensors, or the like.

[0030] Additionally, the processor 132 is in circuit communication with actuator drive circuitry 148. In this exemplary embodiment, the actuator drive circuitry 148 operates a motor and associated gearing 150 to operate the foam pump 114 on the refill unit 110. In some embodiments, the actuator drive circuitry 148 causes a permanent pump (not shown) in the dispenser 100 to pump fluid from the refill unit. In some embodiments, the permanent pump is a sequentially activated multi-diaphragm foam pump, such as that shown and described in U.S. Pat. No. 10,143,339, which is incorporated herein by reference in its entirety. An exemplary embodiment of a non-contact dispenser can be found in U.S. Pat. No. 9,172,266, which is incorporated herein by reference in its entirety.

[0031] In this exemplary embodiment, refill unit 110 is shown in dashed lines inserted into dispenser 100 in Figure 1, and refill unit 110 is also shown in solid lines in Figure 2. Refill unit 110 is easily inserted into dispenser 100 and removed from dispenser 100 as a unit. In this exemplary embodiment, refill unit 110 includes container 112 and optional foam pump 114 including air compressor 116 and outlet nozzle 118. Refill unit 110 also includes a foamable liquid 113, such as, for example, a foaming soap, disinfectant, lotion, moisturizer, or other liquid used for personal hygiene.

[0032] In some embodiments, the refill unit 110 is for use in a liquid dispenser rather than a foam dispenser and is filled with unfoamed liquid, and therefore the air compressor 116 is not required.

[0033] In some embodiments, the pump 114 and the outlet nozzle 118 are part of the dispenser 100, and the refill unit 110 includes a sealing member (not shown) for sealing a bottom opening (not shown) of the container 112 that is used to place the interior of the container 112 in fluid communication with the dispenser pump and outlet nozzle. In such embodiments, the pump 114 may be a foam pump or a liquid pump.

[0034] In the exemplary embodiment, the refill unit 110 includes a replaceable power source 120. The replaceable power source 120 may be any power source, such as, for example, a single "AA" battery. In some embodiments, the replaceable power source 120 does not include enough power and / or a high enough voltage to directly power a motor and associated gearing 150 for dispensing the contents of the refill unit 110, or to power a pump (not shown) that does not require the associated gearing 150. In the exemplary embodiment, the replaceable power source 120 is inserted into the dispenser 100 along with the refill unit 110 and removed from the dispenser 100 along with the refill unit 110. While the refill unit 110 preferably has the replaceable power source 120 affixed thereto, in some embodiments the replaceable power source 120 is provided separately along with the refill unit 110. Nevertheless, in either case, the replaceable power source 120 is installed and removed along with the refill unit 110.

[0035] Refill unit 110 includes a near field communication tag 160. Near field communication tag 160 ("NFC tag 160") is an electronically readable device. In some exemplary embodiments, the term NFC can include, for example, radio frequency identification device ("RFID"). NFC tag 160 is a passive device that contains information. In some embodiments, NFC tag 160 is an active device. Dispenser 100 includes a reader 170 that can be used to read NFC tag 160 when NFC tag 160 is installed in the dispenser.

[0036] In some embodiments, NFC tag 160 utilizes ISO / IEC 18000-3, an international standard for devices that communicate wirelessly at a frequency of 13.56 MHz using Type A or Type B cards. In some embodiments, NFC tag 160 and reader 170 must be close to each other, for example, within 4 centimeters of each other, before information can be transmitted.

[0037] During normal operation, when the refill unit 110 is placed in the dispenser 100, the NFC tag 160 is placed near the reader 170. The reader 170 broadcasts a signal to the NFC tag 160. The NFC tag 160 becomes powered by the signal transmitted from the reader 170. The signal powers the NFC tag 160, and the resulting high frequency magnetic field couples one or more coils on the NFC tag 160 at a distance with one or more coils on the reader 170. Once this field is established and a connection is made, information can be passed between the reader 170 and the NFC tag 160. In some embodiments, the reader 170 sends a first message to the NFC tag 160 to learn what type of communication the NFC tag 160 uses, such as Type A or Type B. When the NFC tag 160 responds, the reader 170 sends its first command in the appropriate specification. In some embodiments, NFC tag 160 receives the command and checks if the command is valid. If the signal is not valid, nothing happens. If the signal is a valid request, NFC tag 160 responds with the requested information.

[0038] In some embodiments, the NFC tag 160 functions in half-duplex while the reader functions in full-duplex. Half-duplex refers to a device that can only transmit or receive, not both simultaneously. Full-duplex is capable of simultaneously transmitting and receiving signals. Thus, in this exemplary embodiment, the NFC tag 160 can only receive or transmit signals, while the reader 170 can simultaneously receive a signal and send a command or signal. In some embodiments, commands are transmitted from the reader using PJM (phase jitter modulation) to modify the surrounding field to send the signal. The NFC tag 160 replies by sending a charge through the coil of the NFC tag 160 using inductive coupling.

[0039] In the exemplary embodiment, the system circuitry 130 also includes a capacitor bank 145 and a capacitor control circuitry 146 in circuit communication with the processor 132. The capacitor bank 145 and the capacitor control circuitry 146 are in circuit communication with a replaceable power interface receptacle 144 and an actuator drive 148. The replaceable power interface receptacle 144 is configured to receive and / or otherwise electrically couple with the replaceable power source 120 when the refill unit 110 is inserted into the dispenser 100.

[0040] During operation, when the refill unit 110 is inserted into the dispenser 100, the processor 132 and the capacitor control circuitry 146 simultaneously charge the capacitor bank. In one exemplary embodiment, there are three capacitors. The capacitors are preferably large to accommodate the power required to power the motor and associated gearing 150 to dispense one dose of foam. The large capacitors are preferably charged to a point less than their maximum charge value. Because the capacitor bank 145 is charged to less than its maximum capacity, there is less discharge of the capacitors when they have not been in operation for a while. In some embodiments, the capacitors are charged to less than about 50% of their maximum capacity. In some embodiments, the capacitors are charged to less than about 75% of their maximum capacity. In some embodiments, the capacitors are charged to less than about 90% of their maximum capacity.

[0041] When processor 132 determines, through object sensor 142, that an object is within the dispensing zone, processor 132 causes capacitor control circuitry 146 to place a capacitor in series to provide power to actuator drive circuitry to power motor and associated gearing 150 and operate foam pump 118. Once a dose is dispensed, processor 132 checks the charge on capacitor 145. If the charge is below a threshold, processor 132 causes capacitor control circuitry 146 to charge capacitor 145. Capacitors 145 are charged simultaneously.

[0042] FIG. 3 is a schematic diagram of an exemplary refill unit 300. The exemplary refill unit 300 may be the same or similar to the refill unit 110 and may include an optional pump. Yet, in this exemplary embodiment, the refill unit 300 does not include the optional pump. In this exemplary embodiment, the refill unit 300 includes a container 312 for holding a fluid (not shown), such as, for example, a disinfectant, soap, or lotion. The refill unit 300 also includes an optional power supply 300. The power supply 300 may be used to transfer power to a dispenser (not shown), such as those shown and described above and those incorporated herein. The refill unit 300 includes an NFC tag 360, which may be affixed to the container 312 or any other portion of the refill unit 300. In this exemplary embodiment, the NFC tag 360 is a passive near field communication tag, but in some embodiments, the NFC tag 360 may be an active tag and, in some embodiments, may be powered by the power supply 320.

[0043] The NFC tag 360 includes a memory 364. In some embodiments, refill specific data or information 366 is located in the memory 364. The refill specific data 366 includes information specific to or describing the refill unit 300. The refill specific data 366 may be, for example, a serial number, a manufacturing date, a manufacturing location, one or more distributor authorization codes, an expiration date, a volume, a type of fluid, a fluid dose size, or the like.

[0044] Further, in the exemplary embodiment, memory 364 includes a firmware and / or software update 370. Firmware and / or software update 370 may include an optional update version 372, an optional dispenser type / usage 374, one or more update constants 376, and the like. Update version 372 is read by a dispenser (e.g., dispenser 100) and compared to the firmware / software version currently running on the dispenser. If the firmware / software version running on the dispenser is the same or newer, update 370 may be ignored. If the firmware / software version running on the dispenser is older, update 370 may be installed. In some embodiments, the version is not included in memory 364. Thus, any compatible dispenser that receives update 370 will execute the firmware / software update.

[0045] In some embodiments, the firmware / software update includes a dispenser type / usage 372. In such a case, the firmware / software update 370 can run on selected dispensers that match the dispenser type / usage 372, but not others. Thus, a "generic" refill unit, i.e., a refill unit that will work with multiple types of dispensers, can include a firmware / software update, but the update will only run on a selected subset of the dispensers.

[0046] Further, in some embodiments, the firmware / software update 370 is designed to work only with dispensers having a selected tier, such as dispensers of a selected age, or that have had a selected volumetric throughput run through the dispenser for a selected period of time. For example, it may be determined that dispensers that are three years old and / or that have dispensed five or more refill units should be reconfigured to dispense at a different volume than they are currently configured, and the firmware / software update may be used to change the output volume for only those dispensers of a selected age or above volumetric throughput.

[0047] In some embodiments, the firmware / software update 370 includes a constant update 374. The constant update 374 can be particularly useful for firmware updates or updates where the NFC tag deserves to have a smaller amount of memory. Exemplary constants that can be updated autonomously include, for example, the liquid to air ratio of the foam output, the cutoff voltage, i.e., the voltage level of the power supply at which the dispenser ceases to function, dripping or sagging of the dispensed output, and the like. Tailingchanges in hand sensing parameters, such as how often the sensor looks for hands, one or more status indicators or light on / off rates, system clock speed, such as 20 MHz or 5 MHz, low power mode settings, whether to check for authentication tags, NFC tag excitation time, sensor settings, such as light difference between targets and non-targets, start speed, length of time to wait for a target to leave the sensing area, number of targets, and the like.

[0048] 4 is an example method 400 or logic diagram for autonomously updating software and / or firmware in a dispenser. The example methods shown and disclosed herein are example embodiments. In some embodiments, more or fewer steps or blocks may be used. Furthermore, unless otherwise noted, blocks or steps may be performed in different orders. Furthermore, steps or blocks in one example embodiment may be added or removed in other example embodiments.

[0049] The exemplary method begins at block 402. At block 404, a determination is made as to whether a refill unit having an NFC tag has been installed in the dispenser. If a refill unit having an NFC tag has not been installed in the dispenser or if the refill unit does not have an NFC tag, the method loops back to the beginning. If a refill unit having an NFC tag has been installed, the dispenser reads information from the NFC tag at block 406. The information from the NFC tag may include information such as, for example, a serial number of the refill unit, an expiration date of the refill unit, a fluid volume of the refill unit, a distributor identification of the refill unit, software updates, firmware updates, and the like. If a determination is made at block 408 that a firmware or software update has not been identified, the method proceeds to block 412 and ends. If a determination is made at block 408 that a firmware or software update has been identified, the method moves to block 410.

[0050] In some embodiments, at block 408, the dispenser compares the firmware / software update to the firmware / software version currently running on the dispenser. If the firmware / software version currently running on the dispenser is the same as the update, the method moves to block 412 and ends. If the versions are different, the method moves to block 410. At block 410, the dispenser executes the software and / or firmware update on the dispenser. The dispenser stores the updated software and / or firmware in the dispenser memory. If necessary, the dispenser reboots and boots up. Once the dispenser reboots or restarts, the dispenser operates using the updated software and / or firmware. The firmware / software may be a full firmware / software update or may be a partial update. In some embodiments, the update is one or more constant updates. In some embodiments, the dispenser executes the update at a set time, such as 2:00 a.m. to prevent dispenser downtime. In some embodiments, the dispenser requests user input as to whether the update should be performed immediately or at a later time.

[0051] FIG. 5 is an exemplary method of programming a near field communication tag on a refill unit. The exemplary method begins at block 502. At block 504, a refill unit is provided. In some embodiments, the refill unit is a container with a pump attached to the container. In some embodiments, the refill unit is filled prior to applying the NFC tag. In some embodiments, the refill unit is filled after applying the NFC tag to the refill unit. At block 506, an NFC tag is provided. At block 510, a firmware or software update is copied to the NFC tag. Refill specific data is preferably simultaneously stored in the NFC tag. At block 512, a determination is made as to whether the firmware and / or software was successfully saved to the NFC tag. If saved, the method proceeds to block 516. If not saved, the firmware and / or software update is resaved at block 514. At block 516, the NFC tag is secured to the refill unit and the method ends at block 518.

[0052] The refill unit is preferably a standard refill unit that includes a container with a fluid desired to be dispensed, such as, for example, a disinfectant, soap, or lotion. In some embodiments, the refill unit is a dummy refill unit and does not include a fluid. In some embodiments, depending on the location of the NFC tag, the dummy refill unit may not include one or more components of a standard refill, but may in fact not even physically resemble a refill unit.

[0053] A non-contact dispenser has one or more sensors to detect when an object is present in the sensing area. If a battery is placed in the dispenser at manufacture and then placed in a box, the sensor will check to see if an object is present, as it normally would, which causes the battery to begin to run out of power. Some non-contact dispensers have a switch to turn off the power, or a plastic tab between the battery contacts and the dispenser contacts, and the plastic tab must be removed from the dispenser when the dispenser is operated. Problems arise if the installer forgets to flip the switch or remove the plastic during installation. In this exemplary method, the dispenser may be manufactured, the battery placed in the dispenser, and the dispenser packed in a box without the need for a switch or plastic tab.

[0054] 6 is an exemplary method for a dispenser to "sleep" until a refill unit having a firmware and / or software update is installed in the dispenser. The exemplary method begins at block 602. At block 604, the dispenser is manufactured. During manufacturing, the dispenser is completed and a battery is installed. At block 606, the dispenser is programmed. The dispenser is programmed to be in a sleep mode or a mode that disables the sensor for detecting objects in the detection area. In the sleep mode, the sensor goes into a power saving mode and only wakes up periodically to search for objects. In the dispenser disabled mode, the sensor does not wake up to search for objects.

[0055] The dispenser is shipped at block 608 and installed at block 610. Once the dispenser is installed, a refill unit is installed at block 612. The refill includes an NFC tag. In some embodiments, when the NFC tag is placed near a reader in the dispenser circuitry, it reads the update information on the NFC tag and updates the firmware and / or software. The firmware / software is updated at block 614 and the sensor is configured to actively search for objects within the detection zone during normal operation. The exemplary method ends at block 616.

[0056] Although various inventive aspects, concepts, and features of the present invention may be described and shown herein as embodied in combination in exemplary embodiments, these various aspects, concepts, and features may be used in many alternative embodiments, individually or in various combinations and subcombinations thereof. It is not the intention of the applicant to restrict the scope of the appended claims to such particulars or in any manner to limit them. Unless expressly excluded herein, all such combinations and subcombinations are intended to be within the scope of the present invention. Furthermore, although various alternative embodiments of the various aspects, concepts, and features of the present invention--alternative materials, structures, configurations, methods, circuits, devices and components, software, hardware, control logic, alternatives (in form, fit, and function), etc.--may be described herein, such descriptions are not intended to be a complete or exhaustive list of available alternative embodiments, whether currently known or later developed. Those skilled in the art may readily employ one or more of the inventive aspects, concepts, or features in additional embodiments and use within the scope of the present invention even if such embodiments were not expressly disclosed herein. Additionally, although some features, concepts, or aspects of the invention may be described herein as being preferred arrangements or methods, such description is not intended to imply that such features are required or necessary unless expressly so stated. Furthermore, while exemplary or representative values ​​and ranges may be included to aid in understanding the present disclosure, such values ​​and ranges should not be construed in a limiting sense, and are intended to be significant values ​​or ranges only when so expressly stated. Moreover, although various aspects, features, and concepts may be expressly identified herein as being inventive or forming part of the invention, such identification is not intended to be exclusive, and rather, there may be aspects, concepts, and features of the invention fully described herein that are not expressly identified as such a particular invention or part of a particular invention.The description of an example method or process is not limited to including all steps as required in all cases, and the order in which the steps are presented should not be construed as required or necessary unless expressly stated as such.

Claims

1. 1. A soap or sanitizer dispenser comprising: A processor; A dispenser memory; firmware for controlling one or more operations of the dispenser; A sensor for detecting an object; a receptacle for receiving a refill unit; A reader for reading information from the short-range wireless communication tag; A supplementary unit; Equipped with the replenishment unit includes a short-range wireless communication tag fixed to the replenishment unit; a memory on the near field communication tag; a firmware update code stored in said memory; Equipped with when the refill unit is placed in the receptacle, the reader reads the firmware update code; the processor updates the dispenser firmware according to the firmware update code read from the near field communication tag on the refill unit; the firmware update code includes code for updating one or more constants; Soap or sanitizer dispensers.

2. The dispenser of claim 1 , wherein the one or more constants is a liquid to air ratio of foam output.

3. The dispenser of claim 1 , wherein the one or more constants is a cutoff voltage.

4. The dispenser of claim 1 , wherein the one or more constants is a speed profile configured to limit dripping or tailing of the dispensed output.

5. The dispenser of claim 1 , wherein the one or more constants vary a sensing parameter of the object sensor.

6. The dispenser of claim 1 , wherein the one or more constants are an on / off rate of one or more status indicators or lights.

7. 2. The dispenser of claim 1, wherein the one or more constants is a speed of a system clock.

8. The dispenser of claim 1 , wherein the one or more constants are one or more low power mode settings.

9. The dispenser of claim 1 , wherein the one or more constants is whether to check an authentication tag.

10. The dispenser of claim 1 , wherein the one or more constants is an NFC tag excitation time.

11. The dispenser of claim 1 , wherein the one or more constants are sensor settings.

12. The dispenser of claim 1 , wherein the one or more constants is a start speed.

13. The dispenser of claim 1 , wherein the one or more constants is a length of time to wait for targets to leave a detection area of ​​the object sensor or a number of targets.

14. 1. A soap, disinfectant, or lotion refill unit comprising: a container for holding one of a soap, a disinfectant, and a lotion; a short-range wireless communication tag associated with the container; a refill unit memory on the near field communication tag; update logic stored in the refill unit memory for updating software and / or firmware; Equipped with the update logic is configured to perform a software or firmware update on the dispenser; the update logic includes logic for updating one or more constants; Refill units for soap, sanitizer, or lotion.

15. 15. The dispenser of claim 14, wherein the constant is the liquid to air ratio of the foam output.

16. The dispenser of claim 14, wherein the constant is a cutoff voltage.

17. 15. The dispenser of claim 14, wherein the constant is a speed profile configured to limit dripping or tailing of the dispensed output.

18. The dispenser of claim 14, wherein the constant varies a hand sensing parameter.

19. 15. The dispenser of claim 14, wherein the constant is an on / off rate of one or more status indicators or lights.

20. 15. The dispenser of claim 14, wherein the constant is the speed of a system clock.

21. The dispenser of claim 14, wherein the constant is one or more low power mode settings.

22. 15. The dispenser of claim 14, wherein the constant is whether to check an authentication tag.

23. The dispenser of claim 14, wherein the constant is an NFC tag excitation time.

24. The dispenser of claim 14, wherein the constant is a sensor setting.

25. 15. The dispenser of claim 14, wherein the constant is a start speed.

26. 15. The dispenser of claim 14, wherein the constant is a length of time to wait for targets to leave a sensing area or a number of targets.

Images