Patent Description:
The claimed subject matter is not limited to implementations that solve any or all disadvantages noted in the background.

<CIT> shows a skin treatment sprayer system, comprising: at least one container receptacle configured to receive a container of skin treatment solution, an interrogator coupled to the at least one container receptacle, the interrogator operable to communicate with a machine readable tag associated with the container, a controller comprising a processor in communication with the interrogator; at least one spray nozzle in fluid communication with the container and being operable to emit a spray comprising the skin treatment solution; and wherein the controller is operable to control a spray parameter associated with the emission of the skin treatment solution based on data received from the machine read- able tag.

<CIT> shows a system, comprising: a spray tool comprising a trigger and a sensor, a fluid regulation system, comprising: a container configured to store a coating material, a pump configured to control a flow of the coating material, a pump control system, comprising: a controller configured to change an operating parameter of the pump distributing the coating material in response to an input from the sensor, and wherein the pump control system is coupled to the fluid regulation system.

<CIT> shows a high-pressure cleaning system with a high-pressure cleaning appliance which comprises a pump and a motor driving the pump as well as a pump inlet for supplying cleaning liquid to be pressurized and a pump outlet for delivering pressurized cleaning liquid and a control device for controlling the high-pressure cleaning appliance, and with at least one discharge unit adapted to be brought into fluid connection with the pump outlet for discharging the pressurized cleaning liquid, wherein the high-pressure cleaning system comprises a detection unit by means of which the type of discharge unit presently in fluid connection with the pump outlet is detectable and which is connected in a signal-transmitting manner to the control device, at least one conveying parameter of the high-pressure cleaning appliance being automatically adaptable by the control device to the detected type of discharge unit.

<CIT> shows a component for an application system, the component being an application member of the application system, the component comprising: a transponder configured for storing component data, the component data being configured to be readable, and a wear detection device configured to identify wear of the component, the wear detection device including at least one wear mark at a wear portion of the component and an optical detector.

A fluid spraying system includes a fluid applicator having a tip that atomizes a fluid. The fluid spraying system also includes a pump configure to pump the fluid from a fluid source to the tip and a control system. The control system identifies at least one characteristic of the tip and communicatively couples to the pump. The control system also controls an operating characteristic of the fluid spraying system based on a characteristic of the tip.

These and various other features and advantages will be apparent from a reading of the following Detailed Description. This Summary and Abstract are not intended to identify key features or essential features of the claimed subject matter, nor are they intended to be used as an aid in determining the scope of the claimed subject matter. The claimed subject matter is not limited to implementations that solve any or all disadvantages noted in the background.

While the above-identified figures set forth one or more examples of the disclosed subject matter, other examples are also contemplated, as noted in the disclosure. In all cases, this disclosure presents the disclosed subject matter by way of representation and not limitation. It should be understood that numerous other modifications and examples can be devised by those skilled in the art which fall within the scope of the appended claims.

Different fluids have different physical properties that affect atomization rates, and atomization patterns. Additionally, different spray tips have different properties that affect atomization rates, and atomization patterns. For the average consumer using a spraying system, determining which conditions are necessary for achieving an even spray pattern (e.g., a spray pattern free of tailing effects) can be difficult. Accordingly, one example spraying system includes features that detect (automatically or with some user input) the current tip and/or the current fluid being sprayed. For instance, the fluid can be identified fully automatically by using a sensor in the fluid and the tip can be identified by automatically reading an RFID tag (or other type of tag) in the tip when the tip is inserted into the applicator or by placing the tip near a sensor associated with the pump. Alternatively or in addition, the tip can be identified semi-automatically by having the user scan a machine readable (MR) code (such as a barcode, Quick Response (QR) code, image recognition, etc.) on the tip, tip package, etc. and the fluid can be identified semi-automatically by scanning a bar code on a fluid source (e.g., the fluid bucket, etc.). In some examples, the user can use a separate device, such as a mobile device to scan these codes.

Using tip and fluid identification information, the spraying system can be improved to produce desired spraying characteristics. For instance, changing pump settings based on tip size/geometry and fluid characteristics to get desired atomization rates/ spray patterns. In some examples, the improvement occurs automatically through automatic adjustment of pump settings. In other examples, the improvement is recommended to the operator, such that they can manually accept or reject the recommended changes.

As a tip wears, or otherwise ages, the characteristics of the tip (e.g., the spray pattern shape/size, flowrate, internal turbulation, etc.) can change. For example, a new tip may dispense <NUM>,<NUM>/h (<NUM> oz/min), while that same tip, after some usage, may dispense <NUM>,<NUM>/h (<NUM> oz/min). For consistent or otherwise improved spray coverage, examples of the present system accounts for wear affects, for example by adjusting a characteristic of the pump operation. According to the invention, the diameter of the tip orifice is calculated based on the sensed pressure and pump RPM. Additionally, a "life" of the tip is determined by comparing a current tip's orifice size to the tip's initial orifice size (e.g., <NUM>% tip life) and an unacceptably worn tip orifice size (e.g., <NUM>% tip life).

<FIG> is a perspective view showing one example spraying system <NUM>. Spraying system <NUM> includes a pump <NUM> that is mounted on a cart <NUM> and couples to an applicator <NUM> through a delivery line <NUM>. Pump <NUM> includes a fluid intake <NUM> that is exposed to a fluid source (e.g., a <NUM>,<NUM> (<NUM> gal) bucket of paint). Pump <NUM> pumps the fluid from the fluid source through fluid intake <NUM> and pumps the fluid at a given pressure to applicator <NUM> through delivery line <NUM>. A fluid sensor <NUM> can be mounted on fluid intake <NUM> to sense a type of fluid (e.g., a type of paint). Examples of fluid sensors <NUM> will be described in greater detail below. Alternatively, or in addition, a fluid level sensor <NUM> can sense the amount of remaining fluid in the fluid source (via ultrasound, pressure, etc.). When the fluid reaches a threshold level a user can be notified. For example, an alert on a remote/mobile device may notify the user. As another example, a haptic, visual or audible alert on the applicator may notify the user. The fluid level sensor <NUM> may also track usage over time and notify a user at given intervals. For example, a user may want to be notified when they have three-quarters remaining, one half remaining, one-quarter remaining, etc. This may be useful in helping a user maintain an even coat of fluid coverage over a large spraying job.

In some examples, an electronic device (e.g., smart phone, tablet, PC, etc.) can interface with the pump through a wired or wireless connection. The electronic device can also provide a user interface for a user to control and/or monitor operations of the spraying system <NUM>. For example, setting fluid pressure, entering cleaning mode, tracking fluid throughput, etc. In some examples, water being pumped through spraying system <NUM> to clean the system is detected and not counted as fluid throughput.

An internet or other network connection of the electronic device can be used to update the software/firmware of the spraying system <NUM>. In other examples, spraying system <NUM> can directly connect to the internet or another network.

<FIG> is a perspective view showing one example fluid applicator <NUM>. Fluid applicator <NUM> can be similar to the fluid applicator of <FIG> or can be a different type of fluid applicator as well. Applicator <NUM> receives fluid through an inlet <NUM> (for example from delivery line <NUM> and then into and through inlet <NUM>). Trigger <NUM> actuates to allow fluid flow from inlet <NUM> to an outlet <NUM> of tip <NUM> where the fluid is expelled. Often, tip <NUM> can be replaced with a different type of tip for a different spray pattern or to accommodate a different fluid.

In some cases, tip <NUM> can include an identifier <NUM> that is read by a tip sensor <NUM> coupled to applicator <NUM>. Of course, a different tip sensor <NUM> could also read identifier <NUM> as well. Identifier <NUM> can be a form of RFID tag or similar electronic devices. Tip sensor <NUM> can be an RFID or other electronic reader that reads the identifier <NUM> of tip <NUM> when the objects are within close proximity to each other (e.g., when tip <NUM> is inserted into applicator <NUM>).

Identifier <NUM> could be a different type of device, such as a mechanical device. For example, identifier <NUM> could be a specific profile of tip <NUM> that contacts a different part of tip sensor <NUM> based on the type of tip <NUM> (e.g., each tip would have a unique profile that could be detected by tip sensor <NUM>). Identifier <NUM> could be a different device as well, such as electronic leads that contact leads (tip sensor <NUM>) on applicator <NUM>. Identifier <NUM> could include other items as well to transmit identifying information of the tip to tip sensor <NUM> as well.

As shown, tip sensor <NUM> wirelessly transmits the tip data to a pump controller. In another example, tip sensor <NUM> is coupled to a pump controller via a wired connection (e.g., a wire that runs along the length of delivery line <NUM>).

In some examples, an optical sensor can be disposed on fluid applicator <NUM> (or elsewhere that can sense the fluid being expelled from fluid applicator <NUM>) to sense changes in the spray pattern. For instance, as a tip wears, the pattern it generates can narrow or being to spit. The narrowing or spitting in the pattern can be detected by the optical sensor.

<FIG> is a side view showing one example tip <NUM>. Tip <NUM>, as shown, includes an identifier <NUM> that is an RFID tag. In this case, identifier <NUM> interacts with tip sensor <NUM> that is an RFID reader. Tip <NUM> also has an outlet <NUM> where paint is expelled from. Each different kind of tip <NUM> can have a different outlet <NUM> (and/or internal geometry) that has characteristics that affect the fluid spray expelled from outlet <NUM>. Because each tip <NUM> may have different spray characteristics, it is important to know which tip <NUM> is being used to better control the fluid spray from applicator <NUM>. In some examples, tip <NUM> has keying features to prevent the tip from being inserted into a pump system that is not configured to electronically interact with, or detect tip <NUM> (referred to as a "non-smart" pump system). However, in other examples, tip <NUM> can be inserted into a non-smart pump system and when re-inserted into a smart pump system, the wear from the non-smart pump usage can be estimated, for instance, by calculating the diameter of outlet <NUM>.

<FIG> is a perspective view showing one example fluid source <NUM>. Fluid source <NUM> has a fluid reservoir <NUM> and one or more identifiers <NUM>. Identifier <NUM>-<NUM> includes a machine readable code (e.g., a bar code) that is commonly placed on buckets of fluid. In one example, a device can scan identifier <NUM>-<NUM> and identify the fluid within fluid source <NUM> fluid reservoir <NUM>. Identifier <NUM>-<NUM> includes an RFID tag that is read by an RFID reader (such as fluid sensor <NUM> located on fluid intake <NUM> in <FIG>). Of course, identifiers <NUM>-<NUM> and <NUM>-<NUM> are examples only and other identifiers <NUM> could be used to identify the fluid as well. For instance, a device can take a picture of fluid source <NUM> and identify the fluid based on the image (e.g., by identifying brand markings, optical character recognition of the words on the source, etc.).

<FIG> is a diagram showing an example interface <NUM>. As shown, interface <NUM> is displayed on a smart phone, however in other examples interface <NUM> can be displayed on a different device as well. For example, interface <NUM> could be located on applicator <NUM>, pump <NUM> a handheld device, a watch, an eye wear, or somewhere else.

Interface <NUM>, as shown, includes pressure indicator <NUM> that displays a current pressure of the fluid being pumped by the given pump. Fluid indicator <NUM> is a display mechanism that shows the current fluid being pumped by given pump. Tip indicator <NUM> is a display mechanism that displays the current tip installed in applicator <NUM>. Pressure increase mechanism <NUM> is actuatable to increase the current pressure generated by pump <NUM>. Pressure decreased mechanism <NUM> can be actuated to decrease the current pressure generated by pump <NUM>. In other examples, there may be other actuatable mechanisms that change other settings of pump <NUM>.

Manual tip selection mechanism <NUM> is actuatable to select a given tip. For example, manual tip selection mechanism <NUM> is actuated to generate an interface that allows a user to manually select the tip currently installed in applicator <NUM>. Manual fluid selection mechanism <NUM> is actuatable to select a fluid that is to be applied by applicator <NUM>. For example, manual fluid selection mechanism <NUM> can be actuated to generate an interface that allows a user to select the current fluid being pumped by pump <NUM>. When the user selects the tip manually, the algorithm (tip life indicator) in the app can also figure out the life of the tip (like wear, flow rate, etc.) based on the pre-defined data set hard coded for each tip. Tip can also mean a nozzle.

Auto tip selection mechanism <NUM> is actuated to automatically sense the current tip within applicator <NUM>. For example, the tip can be automatically selected by reading the RFID tag within the tip or some other electrical connection between the tip and a device. In another example, the tip can be automatically selected by scanning the barcode on the tip or packaging of the tip, etc..

Automatic fluid selection <NUM> can be actuated to automatically select the type of fluid being pumped by pump <NUM>. For example, a sensor located in the fluid can sense a type of fluid. In another example, a barcode on the fluid storage device can be scanned to identify the type of fluid. In another example, an RFID or similar electronic mechanism can be read to identify the fluid. In another example, an application uses camera functionality on a mobile device, and the user takes a picture of the name of fluid storage device, and through image recognition the app can figure out the type of fluid.

Tip life indicator <NUM> displays a current remaining life of the inserted tip. This life can be calculated or estimated by the pump controller. For example, previous data gathered on the wear of certain tips that are spraying certain fluids can be used to estimate wear on the current tip. In some cases, tips can have unique identifiers that identify themselves from other tips (of the same type), this way a tip can be tracked over a given time frame even when being switched with other tips. In one example, a tip used across multiple spraying systems can have its life tracked by saving usage/spray times in combination with the unique tip identifier to a database accessible to multiple spraying systems. In one example, for each tip, the information generated on the wear, shall be saved on to the cloud and is used by the manufacturer to better estimate/ understand the tip wear. The manufacturer, who has access to the tip wear data with different coatings, can use the information to better design future tips.

<FIG> is a block diagram showing an example spraying system environment <NUM>. For sake of illustration, but not by limitation, environment <NUM> will be described in the context of system <NUM> and similar elements are similarly numbered.

Environment <NUM> includes spraying system <NUM>, tip <NUM>, fluid source <NUM> and mobile device <NUM>, but can include other items as well. Spraying system <NUM> includes pump <NUM> that pumps a fluid from fluid source <NUM> to applicator <NUM> and tip <NUM>. System <NUM> includes a controller <NUM>. In one example, controller <NUM> comprises a computing device, such as a microprocessor that communicatively couples to pump <NUM> and sends signals to pump <NUM> to control various aspects of operation of pump <NUM>. For example, controller <NUM> monitors pump operation and controls the pump to maintain a fluid pressure in a fluid as it is pumped to applicator <NUM>. In one example, controller <NUM> includes integrated software or logic components to perform a variety of different functions. For example, integrated software may be used to change the state of a solenoid in a reciprocating piston pump. Controller <NUM> couples to communication component <NUM> that allows communication with interface <NUM>, when interface <NUM> is on another device, such as a smart phone or other mobile device (e.g., interface <NUM>).

As mentioned, controller <NUM> can include computer processors with associated memory and timing circuitry, not separately shown. They are functional parts of the systems or devices to which they belong and are activated by, and facilitate the functionality of the other components or items in those systems.

Spraying system <NUM> also includes a data store <NUM>. Data store <NUM> can store information associated with the pump, tip, spray gun/applicator, users, jobs, etc. For example, as a tip is used, the wear on the tip (e.g., calculated based on throughput of fluid, calculating a tip orifice diameter, etc.) can be stored with the tip identifier in data store <NUM> as tip data <NUM>. As another example, the pump hours can be stored in data store <NUM>. Data store <NUM> can reside on spraying system <NUM> or in another environment, such as a remote server.

Fluid intake <NUM> facilitates fluid flow from fluid source <NUM> to pump <NUM>. Delivery line <NUM> facilitates fluid flow from pump <NUM> to applicator <NUM>/tip <NUM>. Delivery line <NUM> can include other items as well, such as, a communication line that facilitates data transfers from any device located on applicator <NUM> to pump <NUM>. For example, data from applicator <NUM> can be used to set the pressure generated by pump <NUM> (e.g., the type of tip in applicator <NUM>).

Interface <NUM> allows control of pump <NUM> and ultimately control of the spray pattern generated by the spraying operation. Interface <NUM> can be located on a housing of pump <NUM> or can be located remotely as well. For example, interface <NUM> could be on a mobile device (such as a mobile device <NUM>) that sends control signals to pump <NUM> wirelessly, or through wired connection. Interface <NUM> could include different devices and/or mechanisms as well. Spraying system <NUM> can have one or more tip sensors <NUM> that identify the type of tip <NUM> and/or one or more fluid sensors <NUM> the type of fluid in fluid source <NUM>. Sensors <NUM> and <NUM> can include RFID readers, barcode scanners, QR code scanners, fluid sensors, electronic leads/pins and switches, etc. Spraying system <NUM> can include other items as well, as indicated by block <NUM>. Sensors <NUM> and <NUM> can be disposed in a variety of different places, for example, in or on the applicator, a mobile device, a pump, etc..

Spraying system <NUM> includes spray system monitoring and control system <NUM>. Spray system monitoring and control system <NUM> includes various software or hardware logic components <NUM>-<NUM>. In some examples, these components are implemented by controller <NUM>. In other examples, these components are implemented by a different controller or processor (e.g., processor <NUM> or another processor located at a remote server).

Spray system monitoring and control system <NUM> includes tip identifying logic <NUM> which identifies the tip. For example, tip identifying logic <NUM> receives sensor signals that indicate the tip model and serial number. In one instance, tip identifying logic <NUM> receives sensor signals from a camera and identifies the tip based on the image (e.g., by reading a machine-readable code in the image, using optical character recognition to read a serial/model number, etc.). In another instance, tip identifying logic <NUM> receives sensor signals from a wireless communications sensor and identifies tip <NUM> based on the wireless signal (e.g., a RFID signal, a Bluetooth signal, an NFC signal, etc.). In another instance, tip identity logic <NUM> generates interactive components on an interface (e.g., interface <NUM>) that enables a user to manually select a tip. In other examples, tip identifying logic <NUM> can identify tip <NUM> in other ways as well.

Fluid identifying logic <NUM> identifies the fluid. For example, fluid identifying logic <NUM> receives sensor signals that indicate the type and/or amount of paint. In one instance, fluid identifying logic <NUM> receives sensor signals from a camera and identifies the fluid by the image (e.g., by reading a machine-readable code in the image such as a barcode, using optical character recognition to read a part number, etc.). In another instance, fluid identifying logic <NUM> receives sensor signals from a wireless communications sensor and identifies fluid source <NUM> based on the wireless signal (e.g., a RFID signal, a Bluetooth signal, an NFC signal, etc.). In other examples, fluid identifying logic <NUM> can identify fluid source <NUM> in other ways as well.

Fluid flow logic <NUM> calculates or monitors fluid flow through pump <NUM>. For instance, fluid flow logic <NUM> can receive sensor signals indicative of displacement of a piston within pump <NUM> and frequency of the piston reciprocation to calculate fluid flow. In another example, fluid flow logic <NUM> receives a signal from a fluid flow meter. Fluid flow logic <NUM> can calculate or monitor fluid flow in other ways as well.

Fluid coverage logic <NUM> calculates an area and thickness of fluid coverage on a surface being covered by a spraying operation. For example, fluid coverage logic <NUM> receives sensor signals from motion/location sensors (e.g., inertial measurement unit, gyroscope, accelerometer, proximity sensor, etc.) on an applicator and, a fluid flow rate and a spray pattern area to calculate fluid coverage. For instance, if an applicator <NUM> moves slower during application the coverage area will be less but the coverage thickness will be greater. Fluid coverage logic <NUM> can calculate an area and thickness of fluid coverage in other ways as well. Fluid coverage logic <NUM>, in one example, can use visual aids to spatially map the covered paint area, including the ability to calculate the area of curved surfaces. Fluid coverage logic <NUM>, in one example, can use edge detection algorithms, smoothing algorithms, and determines where fluid has or has not been applied, through color detection/ light emission schemes.

Job management logic <NUM> generates user interface displays that a user can interact with to manage jobs. For example, a job can track information about a specific fluid operation at a worksite. Some characteristics of the job include the customer, the users completing the job, the location of the job, the fluid used on the job, the equipment (e.g., pump tip, applicator, etc.) used on the job, the time allocated to complete the job, calculating costs of job, environmental considerations etc. In one example, job management logic <NUM>, can use pre-defined data set for over spray with a tip, to calculate the amount of over spray at the end of day. In one example, the over spray calculation, can help the occupants in deciding the safe duration to return to their space.

Tip wear logic <NUM> calculates the wear of tips <NUM> during a spraying operation. For example, tip wear logic <NUM> can receive information from tip identifying logic <NUM> as to the characteristics of the current tip <NUM> (e.g., the tip material, tip diameter tip orifice diameter, tip internal tip geometry, tip pressure ranges, etc.). Tip wear logic <NUM> can compare the standard characteristics of tip <NUM> (e.g., the characteristics the tip should have at manufacture) with the current detected characteristics of the tip to calculate a "tip life". The tip characteristic related to the tip life is the tip orifice size which is calculated based at least on the pump RPM and pump pressure. Comparing the tip at manufacture orifice size to the current tip orifice size and the largest acceptable orifice size indicates a life of the tip, that is, the length of time a tip has to work effectively.

Timing logic <NUM> calculates and stores the time that the various components of spraying system <NUM> have been used. For example, pumps need to be serviced after a given amount of time and timing logic <NUM> keeps track of the time since the pump was last serviced. Similarly, tips need to be replaced often need to be replaced after given amount time and timing logic <NUM> can automatically keep track of this time.

Recommendation logic <NUM> generates recommendations for user <NUM>. For example, recommendation logic <NUM> can receive information from tip identifying logic <NUM> tip wear logic <NUM> and fluid identifying logic <NUM> that indicative of the current tip and fluid being used. With this knowledge, recommendation logic <NUM> can give a recommendation (e.g., shown to the user on a display of a mobile device or pump) on a pressure to set for effective spraying with the current tip and fluid combination. In another example, recommendation logic <NUM> receives data from tip wear logic <NUM> and gives a recommendation to change a setting of pump <NUM> based on the wear of tip <NUM> identified by tip wear logic <NUM>. In another example, recommendation logic <NUM> will give a recommendation to service pump <NUM> after a time of use has been received from timing logic <NUM>. In one example, the service notifications are also stored in the cloud and the technical service personnel can have access to this information for every pump, before servicing the device. The technical service personnel can look for this information through the pump's serial number in the remote server/ cloud and obtain contextual information on the pump which can aide in diagnosing and repairing procedures.

Motor logic <NUM> interfaces with motor <NUM> that controls pump <NUM>. For example, motor logic <NUM> can monitor the motor temperature and send a high temperature alert. As another example, motor logic <NUM> monitors the motor RPM, which normally correlates with the fluid flow and/or pressure of the fluid.

Non-smart pump logic <NUM> includes components to interface with a non-smart pump. For example, non-smart pump logic <NUM> can connect to a dongle or other device that couples to a non-smart pump to provide some smart pump features. For instance, the run-time, temperature, and RPM's of the pump could be monitored by the device and sent to the non-smart pump logic <NUM>. In some cases, non-smart pump logic <NUM> can receive manual user input on pump usage from a user for the pump.

Control logic <NUM> generates control signals to control pump <NUM>, motor <NUM> and other components of spraying system <NUM>. For instance, control logic <NUM> generates a series of electrical impulses to control motor <NUM> to operate at a given RPM.

Datastore <NUM> includes tip data <NUM>, fluid data <NUM>, pump data <NUM>, user data <NUM>, job data <NUM> and can include other items as well, as indicated by block <NUM>. Tip data <NUM> can include data on tips, for example, the tip model number, the tip serial number or other identifier, the tip life, the tip usage time, the fluids used with the tip, the tip initial dimensions, the tip current dimensions, etc. Fluid data <NUM> can include data on fluids, for example, the shear viscosity, extensional viscosity, rheological profile (shear rate graph), density, surface tension, preferred tip for the fluid, etc. Pump data <NUM> can include data on pumps, for example, the pump horsepower, the pump displacement length, the pump chamber volume, maximum and minimum effective pressure, pump operating history, etc. User data <NUM> can include data on users, for example, the username, the user run time, fluids used by the user, tips used by the user, pumps used by the user, etc. Job data <NUM> includes data on jobs, for example, the job location, the job coverage area, the job fluid thickness, the fluid type, the time on the job, the customer associated with the job, etc..

Tip <NUM> includes identifier <NUM> that is scanned or otherwise interacts with tip sensor <NUM> to identify the type of tip <NUM>. Some examples of identifies <NUM> include serial/mode numbers, electronic ID tags, physical keying features, etc. Tip <NUM> can include other items as well, as indicated by block <NUM>.

Fluid source <NUM> includes identifier <NUM> that can interact with fluid sensor <NUM> to identify the type of fluid in fluid source <NUM>. Fluid source <NUM> can include other items as well, as indicated by block <NUM>.

<FIG> is a flow diagram showing an example operation of spraying system <NUM>. Operation <NUM> begins at block <NUM>, where the spray tip is identified (e.g., tip <NUM> is identified by tip identifying logic <NUM>). Tip <NUM> can be identified in a variety of different ways, as indicated by blocks <NUM>-<NUM>. The spray tip can be identified by scanning a machine-readable code (e.g., a bar or QR code), as indicated by block <NUM>. The bar or QR code can be located on the tip itself, the tip packaging, a tip storage area, etc. The tip can be identified through an RFID, image recognition or other electronic communication, as indicated by block <NUM>. For example, an RFID tag can be embedded in the flag of the spray tip and, when it comes into close proximity of an RFID reader on the applicator <NUM> or pump <NUM>, the identifying information is read from the RFID tag to identify the tip. The tip can be identified manually, as indicated by block <NUM>. For example, a user selects the tip from a list of tips on an interface (e.g., interface <NUM>). The tip can be identified in other ways as well, as indicated by block <NUM>. For example, an image of the tip can be taken and is analyzed by tip identifying logic <NUM> to identify the tip.

Operation <NUM> proceeds at block <NUM>, where the fluid to be applied is identified (e.g., fluid source <NUM> is identified by fluid identifying logic <NUM>). Fluid can be identified a number of different ways, as indicated by blocks <NUM>-<NUM>. Fluid can be identified by scanning a machine-readable code (e.g., a bar or QR code) as indicated by block <NUM>. The machine-readable code can be located on the fluid storage area, the fluid packaging, etc. The reader can be located on a mobile device, the fluid applicator (e.g., applicator <NUM>) or some other device as well.

The fluid to be applied can be identified by an RFID or other electronic method, as indicated by block <NUM>. For example, an RFID tag can be disposed on a bucket in which the fluid is sold in and an RFID reader is located on a fluid intake of the pump to read the RFID tag. The liquid can be identified manually, as indicated by block <NUM>. For example, a user selects the type of fluid from a list on an interface <NUM>. The liquid can be identified in other ways as well, as indicated by block <NUM>. For examples, an image of the fluid source can be taken and is analyzed by fluid identifying logic <NUM> to identify the fluid source.

Operation <NUM> proceeds at block <NUM>, where the pressure is set or a recommendation is made, based on the identified fluid and tip (e.g., by recommendation logic <NUM>). The pressure can be retrieved from a lookup table or database of fluids and tips, as indicated by block <NUM>. The pressure can be set based on an algorithm, as indicated by block <NUM>. The pressure can be set based on other items as well, as indicated by block <NUM>. In some examples, a different setting other than pressure is modified.

In addition, or in the alternate, a recommendation may be given to the user. In some examples, the user may be informed of an incompatibility between the fluid and the tip. In some examples, a recommendation may be made to the user to use a different tip/fluid combination for a better spray pattern. In one example, the user selects a desired type of atomization rate or pattern and the system recommends a specific tip/fluid/pump setting combination to achieve the desired outcome.

Operation <NUM> proceeds at block <NUM> where the fluid is pumped from the pump <NUM> to the applicator, where it is sprayed at the pressure determined in block <NUM>. In one example, the pressure or setting is changed automatically (e.g., by control logic <NUM>). In another example, the pressure or setting change is recommended to the user (e.g., by recommendation logic <NUM> and displayed on a display of the pump, mobile device, etc.). In another example, the pressure or setting change is made automatically, unless the user vetoes the change.

During operation the system <NUM> can provide other functions as well. For example, the tip life is displayed intermittently during the spray operation to the operator. In another example, as the tip life degrades the pump is adjusted to maintain a consistent spray pattern. Additionally, the flow rate and/or current application thickness are displayed (e.g., in oz/min).

At block <NUM> it is determined if the job is complete. If so, then operation <NUM> ends. If not, then operation <NUM> proceeds to block <NUM>.

<FIG> is a side view showing an example spray tip. The tip of <FIG> includes a machine-readable code <NUM> that can be scanned by a device to identify tip <NUM>. As shown, machine readable code <NUM> is a barcode, however it could be a different type of machine-readable code as well. One example of an identification device that can read barcode <NUM> is shown in <FIG>.

<FIG> is a side view showing an example tip. Tip <NUM> includes a near field communication device <NUM>. Near field communication device <NUM> can be sensed by a mobile device or other near field communication device to identify tip <NUM>. One example of an identification device that can communicate with near field communication device <NUM> is shown in <FIG>.

<FIG> is a side view showing an example tip <NUM>. Tip <NUM> has a RFID identifier <NUM>. RFID identifier <NUM> can be sensed by another device to identify tip <NUM>. One example of an identification device that can communicate with RFID identifier <NUM> is shown in <FIG>.

<FIG> is a side view of an example identification device <NUM> that includes a power switch <NUM>, a charger <NUM>, and communication pins <NUM>. Identification device <NUM> can be any one or more of the devices previously mentioned that identify a tip (e.g., barcode or QR reader, RFID reader, NFC device). Identification device <NUM> can be powered on or off by switch <NUM>. Identification device <NUM> can be charged by charging port <NUM>. Identification device <NUM> can connect to a different device via communication pins <NUM>. In addition, or in the alternate, identification device <NUM> can wirelessly connect with other components.

<FIG> is a side view showing the example identification device <NUM> of <FIG>. As shown, identification device <NUM> includes coupling device <NUM> that couples identification device <NUM> to a fluid applicator <NUM>. As shown, applicator <NUM> is similar to applicator <NUM> discussed above. In one example, coupling device <NUM> requires tools for coupling of identification device <NUM> to applicator <NUM>. In other examples, coupling device <NUM> may require no tools to be coupled to applicator <NUM>.

<FIG> illustrate example user interfaces that can be displayed on a device (e.g. such as interface <NUM>). <FIG> is an example home screen user interface that shows a variety of options, such as, but not limited to my sprayers, job history, call for service, pump locator map, tip reader, order spare parts, get new pump, and settings. Actuating the "my sprayer" mechanism generates the user interface of 10B.

The interface of <FIG> shows the sprayers that are currently coupled to the device displaying the interface. For example, as shown, the "model <NUM> sprayer" is connected to the device (that is displaying the interface) and the model <NUM> sprayer is not connected to the device but has been previously connected to or identified by the device. This interface also allows a user to add or remove pumps from the sprayer list for easy connection.

<FIG> is an example interface that is shown when a user selects a pump in the interface of <FIG>. Interface of <FIG> allows a user to perform tasks, such as, start a new job, began auto cleaning of selected pump, order spare pumps for the part, locate the pump (e.g., location of pump can be used based on a strength of a wireless signal), set a lock code for the current pump, called a service, and/or show a pump lifetime history. Of course, these are examples only and more options may be available in the sprayer dashboard interface of <FIG> C.

<FIG> shows an example scanning interface that accesses a camera of the interface device and allows a user to use their camera to locate a UPC, barcode or other MR code.

<FIG> is an interface showing fluid data. In the example shown, the fluid is a paint and has been selected by scanning a UPC or barcode on the paint can. For instance, the UPC is scanned and used to acquire fluid information from an online database, in some examples, that could be provided from the fluid manufacturer.

<FIG> is similar to <FIG>, however, the scanning process is used to identify a tip rather than a fluid. As illustratively shown, the interface of <FIG> can allow a user to either scan an MR code (e.g., barcode, QR code, etc.) or can use a wireless connection such as RFID to identify the tip.

<FIG> is an example interface that allows a user to enter characteristics of the surface that they will be painting on. For example, a surface type can be chosen such as porous, flat, etc. The surface type can be important in a painting operation as different surfaces absorb paint at different rates or require more paint for proper coverage. The surface area may also be entered. The surface area can be used to calculate the percent complete of a job while a user is spraying. For instance, using the surface type, surface area, and/or desired thickness it can be determined how much paint will need to be used to cover this area. Then this required amount of paint is compared against the paint and operators using during a spraying operation. For instance, it may be calculated that, for proper coverage, <NUM>,<NUM> Liter (<NUM> gallons) of paint may be needed and during operation a user can be notified of how much paint they have remaining versus how much paint is required for proper coverage.

<FIG> is example an interface that shows a user a preparation summary. A preparation summary can be gathered via the paint information (e.g. the paint information shown in <FIG>) and the tip installed amongst other things, such as pump characteristics and/or tip characteristics.

<FIG> is an example interface showing a job dashboard. The job dashboard can be displayed while a user is in a spraying operation. Some metrics that can be shown are paint left, area covered, pressure set and pressure acting. Paint left can be calculated via a sensor (e.g., fluid level sensor <NUM>) on the pump. The area covered can be calculated via the previously discussed method of <FIG>. For example, an algorithm is used to determine how much paint is needed to paint an area and this is compared against the amount of paint used.

<FIG> is an example interface where a user can adjust pressure produced by the pump. As shown, the pressure adjusting mechanism is a slider, however in other examples the pressure adjusting mechanism can be other mechanisms as well. For instance, the pressure can be set with a text input.

<FIG> is an example interface showing a job summary. For example, the job summary can tell a user the time that the pump ran, the painting efficiency, the gallons sprayed, the area covered in (e.g. the area covered can be determined based on accelerometers and gyroscopes within the applicator multiplied by the on time of the applicator), estimated thickness, etc. The job summary interface may also allow a user to generate an invoice based on paint usage, on time, etc. Job summary interface may also allow a user to take job pictures of the job that they have completed. Job summary interface can also have a mechanism that allows the user to share their completed job online (such as social media platforms or business websites).

<FIG> is a diagrammatic view showing an example pump selection interface display. As shown, the interface is displayed on a mobile device and shows two pump selection mechanisms that a user can select from. A user can also scroll further down to see additional pumps. Also, there is a menu button used to alter characteristics of a pump and an 'add' interface mechanisms that allows a user to add another pump to the pump selection interface. As shown, each pump has an indicator of connectivity in the top right, a title in the top center and a sample image of the pump in the center. Additionally, each pump selection mechanism has additional information, such as, a serial number, run time, last service date, etc. In other examples, each selection mechanism can include other items as well (e.g., a pump nickname or other identifier, additional images, etc.).

<FIG> is a diagrammatic view showing an example pump information interface display. As shown, the interface is on a mobile device, however the interface may be displayed on other devices as well. The interface shows information such as the title/model of the pump and status of connectivity at the top. Additionally, a photo of the pump is provided. At the bottom are the serial number, running hours, last service date, and an option to show more information about the pump. In other examples, this interface could show additional information such as, running hours using specific types of fluid, users that have used the pump, jobs the pump has been used on, etc..

At the bottom of the pump information window are prepare job and start job mechanisms which can be actuated to fulfill different functions. For example, actuating the prepare job mechanism can inform a user what they need to do to prepare for the next job (e.g., service the pump, change a filter or other component. Actuating the start job mechanism can bring a user to an interface such as the one shown in <FIG>. The interface of <FIG> allows the user to choose the type of tip that they will be using during the spraying operation. As shown, there are three specific tips selection mechanisms and one 'other tip' selection mechanism. Actuating one of these mechanisms will bring up further information on the tip and/or designate the tip as the tip to be used during the spray operation. In one example, this interface is not presented and instead the tip is automatically detected by the spray system. In another example, actuating one of the tip selection interface mechanisms brings a user to the interface of <FIG>.

<FIG> is a diagrammatic view showing an example tip information interface display. As shown, the interface is displayed on a mobile device. As shown, an image of the tip is provided, and a life of the tip is presented at the top. This life can be calculated by the system, as it saves usage history of the tip. In some examples, a calculation is used to determine tip life. According to the invention, a relationship between a pump RPM and pressure estimates the size of the tip orifice and the size of the tip orifice has a relationship to the known manufactured orifice size of the tip. For instance, a model <NUM> tip has a manufactured orifice diameter of <NUM>,<NUM> (. <NUM> inches) and after <NUM>% use the diameter size may be <NUM>,<NUM> (. <NUM> inches). Therefore, if the system detects a <NUM>,<NUM> (. <NUM>-inch) orifice on a model <NUM> tip the life can be adjusted to <NUM>%.

The interface of <FIG> also allows user to change tips or proceed with the currently selected tip, as shown, by the buttons on the bottom of interface of <FIG>. The interface of <FIG> may also include other tip identifying information such as a nickname, the last user to use the tip. the recommended types of fluid that this tip is used for, the job history this tip has been used on, etc..

<FIG> is a diagrammatic view showing an example tip sensing interface display. As shown, the interface instructs a user to hold a smart tip next to the pump which can be read by a sensor on the pump. For instance, the spray tip may have an embedded RFID, NFC or other wireless communication device that the smart pump scanner can sense. In some examples, the smart tip has a barcode or number, QR code or other machine-readable identifier that the smart pump scanner can read. The pump can have an indicator (e.g., one or more lights, a display, audible device, etc.) that alerts the use the tip has been identified and also when the tip data is sent to the mobile device (e.g., the device that interface eleven a is displayed on). In other examples, the tip may be recognized in other ways as well.

<FIG> is a diagrammatic view showing an example surface selection interface display. As shown, there are several different surface types that the user can select from, identified by their industry standard names. In other examples, the user could select the surface type based on its given characteristics (e.g., porosity, absorption, flatness, etc.).

<FIG> is a diagrammatic view showing an example operating interface display. As shown, the current amount of paint used, and the area covered is displayed. The paint use can be calculated based on the fluid throughput sensed through the pump (e.g. by calculating the pressure, orifice size, pump RPM. pump displacement, etc.) The area covered can be calculated based on the paint use and a motion sensor (e.g., IMU inertial measurement unit, gyroscope, accelerometers, camera, etc.) in the applicator. In some examples, the area covered can be calculated with a visual sensor (e.g., on the paint sprayer or elsewhere).

The interface of <FIG> also displays the on-time, that is, the time that the system or pump has been powered on. The interface of <FIG> also shows the runtime, that is, the time that the pump has been running to pump paint. The interface of <FIG> also allows a user to change the pressure of the smart pump. As shown, there are interval mechanisms allow a user to increase the pressure in intervals of <NUM>,<NUM> bar (<NUM> psi). In other examples, this could be changed to a different interval value as well (e.g., <NUM>,<NUM> bar (<NUM> psi), <NUM>,<NUM> bar (<NUM> psi), <NUM> bar, etc.). In one example, a user can actuate the manual set mechanism which can generate an interface similar to that shown in <FIG>. Additionally, the pressure set is displayed, and the actual pressure is also displayed. In some examples, these pressures may be different which can indicate an error with the pump or other component.

<FIG> is a diagrammatic view showing an example pressure setting interface display. As shown, the pressure can be set by actuating an interface mechanism along a scale. The scale can correspond to the limits of the smart pump that the device is attached coupled to connected to. For instance, the max setting is shown to be <NUM>,<NUM> bar (three-thousand-two-hundred psi) and the minimum is <NUM> bar (zero psi) while the user has selected <NUM>,<NUM> bar (one-thousand-six-hundred psi) as the operating pressure. In some examples, the scale corresponds to commonly used pressures (e.g. based on the fluid being applied, type of job, etc.) In other examples, the pressure can be set manually in other ways, such as typing in a value.

At least some examples are described herein in the context of applying a coating material, such as paint, to a surface. As used herein, paint includes substances composed of coloring matter or pigment suspending in a liquid medium as well as substances that are free of coloring matter or pigment. Paint can also include preparatory coatings, such as primers. Paint can be applied to coat a surface as a liquid or a gaseous suspension, for example, and the coating provided can be opaque, transparent, or semi-transparent. Some particular examples include, but are not limited to, latex paint, oil-based paint, stain, lacquers, varnish, inks, and the like. At least some examples can be applied in plural components systems. For example, multiple identification devices identify the plurality of components used in the plural component system.

It should also be noted that the different examples described herein can be combined in different ways as long as the resulting combination falls under the scope of the appended claims. That is, parts of one or more examples can be combined with parts of one or more other examples as long as the resulting combination falls under the scope of the appended claims.

The present discussion has mentioned processors and servers. In one embodiment, the processors and servers include computer processors with associated memory and timing circuitry, not separately shown. They are functional parts of the systems or devices to which they belong and are activated by and facilitate the functionality of the other components or items in those systems.

<FIG> is a block diagram of spraying system environment <NUM>, shown in <FIG>, deployed in a remote server architecture <NUM>. In an example, remote server architecture <NUM> can provide computation, software, data access, and storage services that do not require end-user knowledge of the physical location or configuration of the system that delivers the services. In various examples, remote servers can deliver the services over a wide area network, such as the internet, using appropriate protocols. For instance, remote servers can deliver applications over a wide area network and they can be accessed through a web browser or any other computing component. Software or components shown in <FIG> as well as the corresponding data, can be stored on servers at a remote location. The computing resources in a remote server environment can be consolidated at a remote data center location or they can be dispersed. Remote server infrastructures can deliver services through shared data centers, even though they appear as a single point of access for the user. Thus, the components and functions described herein can be provided from a remote server at a remote location using a remote server architecture. Alternatively, they can be provided from a conventional server, or they can be installed on client devices directly, or in other ways.

In the example shown in <FIG>, some items are similar to those shown in <FIG> and they are similarly numbered. <FIG> specifically shows that spray system monitoring and control system <NUM> can be located at a remote server location <NUM>. Alternatively, or in addition, one or more of remote systems <NUM> and/or data stores <NUM> can be located at the remote server location <NUM>. Therefore, mobile device <NUM>, user <NUM>, spraying system <NUM>, and other components access those systems through remote server location <NUM>.

<FIG> also depicts another example of a remote server architecture. <FIG> shows that it is also contemplated that some elements of <FIG> are disposed at remote server location <NUM> while others are not. By way of example, spray system monitoring and control system <NUM> can be disposed at a location separate from location <NUM> and accessed through the remote server at location <NUM>. Further, one or more of data stores <NUM> can be disposed at a location separate from location <NUM> and accessed through the remote server at location <NUM>. Regardless of where they are located, they can be accessed directly by spraying system <NUM>, through a network (either a wide area network or a local area network), they can be hosted at a remote site by a service, or they can be provided as a service, or accessed by a connection service that resides in a remote location.

It will also be noted that the elements of <FIG>, or portions of them, can be disposed on a wide variety of different devices. Some of those devices include servers, desktop computers, laptop computers, tablet computers, or other mobile devices, such as palm top computers, cell phones, smart phones, multimedia players, personal digital assistants, etc..

<FIG> is a simplified block diagram of one illustrative example of a handheld or mobile computing device that can be used as a user's or client's device <NUM>, in which the present system (or parts of it) can be deployed. <FIG> are examples of handheld or mobile devices.

<FIG> provides a general block diagram of the components of a device <NUM> that can run some components shown in <FIG>, that interacts with them, or both. In the device <NUM>, a communications link <NUM> is provided that allows the handheld device to communicate with other computing devices and under some embodiments provides a channel for receiving information automatically, such as by scanning. Examples of communications link <NUM> include allowing communication though one or more communication protocols, such as wireless services used to provide cellular access to a network, as well as protocols that provide local wireless connections to networks.

In other examples, applications can be received on a removable Secure Digital (SD) card that is connected to an interface <NUM>. Interface <NUM> and communications link <NUM> communicate with a processor <NUM> (which can also embody processors or servers from previous FIGS. ) along a bus <NUM> that is also connected to memory <NUM> and input/output (I/O) components <NUM>, as well as clock <NUM> and location system <NUM>.

I/O components <NUM>, in one example, are provided to facilitate input and output operations. I/O components <NUM> for various embodiments of the device <NUM> can include input components such as buttons, touch sensors, optical sensors, microphones, touch screens, proximity sensors, accelerometers, orientation sensors and output components such as a display device, a speaker, and or a printer port. Other types of I/O components <NUM> can be used as well.

Memory <NUM> stores operating system <NUM>, network settings <NUM>, applications <NUM>, application configuration settings <NUM>, data store <NUM>, communication drivers <NUM>, and communication configuration settings <NUM>. Memory <NUM> can include all types of tangible volatile and non-volatile computer-readable memory devices. It can also include computer storage media (described below). Memory <NUM> stores computer readable instructions that, when executed by processor <NUM>, cause the processor to perform computer-implemented steps or functions according to the instructions. Processor <NUM> can be activated by other components to facilitate their functionality as well.

<FIG> shows one example in which device <NUM> is a tablet computer <NUM>. In <FIG>, computer <NUM> is shown with user interface display screen <NUM>. Screen <NUM> can be a touch screen or a pen-enabled interface that receives inputs from a pen or stylus. It can also use an on-screen virtual keyboard. Of course, it might also be attached to a keyboard or other user input device through a suitable attachment mechanism, such as a wireless link or USB port, for instance. Computer <NUM> can also illustratively receive voice inputs as well.

Note that other forms of device <NUM> are possible.

<FIG> is one example of a computing environment in which elements of <FIG>, or parts of it, (for example) can be deployed. With reference to <FIG>, an example system for implementing some embodiments includes a computing device in the form of a computer <NUM>. Components of computer <NUM> may include, but are not limited to, a processing unit <NUM> (which can comprise processors or servers from previous FIGS. ), a system memory <NUM>, and a system bus <NUM> that couples various system components including the system memory to the processing unit <NUM>. The system bus <NUM> may be any of several types of bus structures including a memory bus or memory controller, a peripheral bus, and a local bus using any of a variety of bus architectures. Memory and programs described with respect to <FIG> can be deployed in corresponding portions of <FIG>.

The system memory <NUM> includes computer storage media in the form of volatile and/or nonvolatile memory such as read only memory (ROM) <NUM> and random-access memory (RAM) <NUM>.

The hard disk drive <NUM> is typically connected to the system bus <NUM> through a non-removable memory interface such as interface <NUM>, and optical disk drive <NUM> is typically connected to the system bus <NUM> by a removable memory interface, such as interface <NUM>.

These and other input devices are often connected to the processing unit <NUM> through a user input interface <NUM> that is coupled to the system bus but may be connected by other interface and bus structures.

The computer <NUM> is operated in a networked environment using logical connections (such as a local area network - LAN, or wide area network - WAN or a controller area network - CAN) to one or more remote computers, such as a remote computer <NUM>.

It should also be noted that the different examples described herein can be combined in different ways, as long as the resulting combination falls under the scope of the appended claims. That is, parts of one or more examples can be combined with parts of one or more other examples, as long as the resulting combination falls under the scope of the appended claims.

Claim 1:
A fluid spraying system (<NUM>) comprising:
a fluid applicator (<NUM>) having a tip (<NUM>) that atomizes a fluid;
a pump (<NUM>) configured to pump the fluid from a fluid source (<NUM>) to the tip (<NUM>);
a control system (<NUM>) that:
identifies at least one characteristic of the tip (<NUM>); is communicatively coupled to the pump (<NUM>); and
controls an operating characteristic of the fluid spraying system (<NUM>) based on the at least one characteristic of the tip (<NUM>),
characterized in that,
the at least one characteristic of the tip (<NUM>) comprises a "life of the tip" parameter, wherein the "life of the tip" parameter is calculated by the control system via a relationship between a pump RPM and pump pressure estimating wear affecting the tip orifice size.