WO2020161689A1

WO2020161689A1 - Platform for monitoring and controlling sprayers

Info

Publication number: WO2020161689A1
Application number: PCT/IB2020/051728
Authority: WO
Inventors: Sergio DECARO JUNIOR
Original assignee: Upl Do Brasil Industria E Comercio De Insumos Agropecuarios S.A.
Priority date: 2019-02-08
Filing date: 2020-02-28
Publication date: 2020-08-13
Also published as: BR102019002700A2; BR102019002700B1

Abstract

An aspect includes a platform for monitoring and controlling sprayers. A system includes a memory having computer readable instructions and one or more processors for executing the computer readable instructions. The computer readable instructions control the one or more processors to perform operations. The operations include identifying a type of spray device. The operations also include receiving, via a user interface of the one or more processors, an identifier of a product to be sprayed by the spray device and a desired spray parameter. A recommended setting for the spray device is determined based at least in part on the type of spray device, a property of the product to be sprayed by the spray device and the desired spray parameter. The recommended setting is output via the user interface.

Description

PLATFORM FOR MONITORING AND CONTROLLING SPRAYERS

BACKGROUND

[0001] The present invention relates generally to industrial sprayers and, more specifically, to a platform for monitoring and controlling sprayers.

[0002] Sprayers are often used to apply pesticides and fertilizers to crop fields. A new wave of disease control was initiated by the launch of Unizeb Gold, a mancozeb-based fungicide which is currently being used by a large number of farmers throughout Brazil and Latin America. The increasing use of fungicides such as Unizeb Gold, Unizeb Glory and, now, more recently, Triziman and Tridium has led to increasing numbers of sprayer problems in the field. Problems include nozzle clogging and damage to pumps inside the sprayers when recommended practices are not followed. In many cases, farmers are not knowledgeable about how often to clean the sprayer and recommended sprayer settings such as droplet size when fungicide products are used. When introducing a new product, such as a fungicide, to the market, information can be disseminated to users by providing training meetings, technical meetings, and lectures detailing best practices. This approach can be very costly and not always the most efficient way to disseminate the information and some users may not attend the training sessions.

[0003] Various mobile applications to provide guidance and assistance in the use of an industrial sprayer have generally not been entirely satisfactory for various reasons. Examples of mobile applications include Mix Tank from Precision Laboratories, SpraySelect from TeeJet Technologies, Spray Guide from Plant Health Technologies, Spray It from Pentair, SprayLogger from AgTerra Technologies, Inc., Nozzle Select Mobile Application from John Deere, and ApplyPlus from John Deere. These applications offer services such as tank mixing sequence, nozzle selection, drop size selection, application details, sprayer maintenance, set-up and optimization, and spray log maintenance. These mobile applications suffer from drawbacks that include that they do not consider multiple variables simultaneously in order to machine operational problems such as nozzle clogging and pump seal damages.

[0004] Another prior art technique for providing guidance and assistance to a user of a sprayer is described in US8170849B2, which describes a spray injection analysis and nozzle configuration system having a user input unit that collects spray system input parameters and relays the collected parameters to a fluid performance matching unit and/or problem geometry unit for subsequent processing. The user inputs basic system parameters, including the desired spray fluid characteristics, to obtain suggested system configuration, including spray nozzle types and quantities. Accuracy of suggested spray nozzle type and configuration is increased via approximating the viscosity and/or surface tension parameters of the desired spray fluid with that of collected performance data. When a user already knows the desired spray nozzle type and associated system parameters, the user input unit routes this information to the problem geometry unit for creation of a problem geometry file, including calculation of the drop size distribution and spray velocity, and performance modeling via the fluid modeling unit. This technique suffers from drawbacks including that it addresses only a limited range of pressure and nozzle outflow recommendations and not those commonly required by fungicides.

[0005] Another prior art technique for providing guidance and assistance to a user of a sprayer is described in US4614300A, which describes an improved paint spray machine having a spray gun with an adjustable spray nozzle, apparatus for controlling the speed and acceleration of the horizontal and vertical movement of the gun, apparatus for controlling the number of passes by the gun, apparatus for controlling the dwell period at the end of each pass and apparatus for controlling flash time between coats of paint. This reference also describes a computer system capable of storing programs for multiple paint spray procedures with their specific operating parameters and capable of actuating, monitoring and correcting parameters of a spray procedure so as to insure accurate spray application of the paint. The computer system also optionally includes an apparatus for connecting the spray machine to a remote computer system and apparatus for controlling the flow of paint to the spray gun. This reference is focused on sprayers used in the paint industry and does not address items such as calibration issues in filters, equipment and standards that are common in sprayers used in agriculture or issues that arise when spraying fungicides.

[0006] An additional prior art technique for providing guidance and assistance to a user of a sprayer is described in US20130231780A1, which describes storing a mixing sequence in one or more computer readable memories, the mixing sequence identifying a mixing sequence by formulation type for a plurality of chemicals that are applied via water or liquid fertilizer solutions; storing a product table identifying a plurality of brand name or generic chemicals by respective formulation type in the one or more computer readable memories; receiving, via a user interface of the computing device, a request for a mixing sequence of chemicals; displaying at least a portion of the product table at a user interface of the computing device; receiving, via the user interface of the computing device, a selection of two or more chemicals from the product table; matching the two or more chemicals to its respective formulation type; ordering the two or more chemicals into a tank mixing order determined by its respective formulation type in the mixing sequence; and displaying the tank mixing order of the one or more chemicals to the user interface of the computing device. The techniques described in this reference suffer from the drawbacks that they do not establish or communicate an order of addition of chemicals which can be important when generating particular formulations. Other drawbacks include having to access a database to access a mixture.

[0007] A further prior art technique for providing guidance and assistance to a user of a sprayer is described in US9717178B1 which describes systems and method for monitoring and controlling field operations including planting and harvesting operations. In one embodiment, a data processing system of a machine includes a data transfer and processing module that communicates bi-directionally with different types of controllers and sensors mounted on the machine or an implement attached to the machine. The data transfer and processing module is configured to execute instructions to receive signals from these controllers and sensors, process these signals, and generate data for monitoring and controlling field operations of the machine. At least one display device is coupled to the data transfer and processing module. The at least one display device displays the data for monitoring and controlling field operations of the machine or implement to a user or operator. The techniques described in this reference suffer from drawbacks that include that they do not establish or communicate an order of mixing, and they do not provide recommendations for fungicides and filtering systems.

[0008] There accordingly remains a need in the art for methods and systems for providing guidance and assistance to a user of a sprayer.

BRIEF DESCRIPTION

[0009] According to one or more embodiments of the present invention, methods, systems and computer program products are provided for monitoring and controlling sprayers. A non-limiting example system includes a memory having computer readable instructions and one or more processors for executing the computer readable instructions. The computer readable instructions control the one or more processors to perform operations. The operations include identifying a type of spray device. The operations also include receiving, via a user interface of the one or more processors, an identifier of a product to be sprayed by the spray device and a desired spray parameter. A recommended setting for the spray device is determined based at least in part on the type of spray device, a property of the product to be sprayed by the spray device and the desired spray parameter. The recommended setting is output via the user interface.

[0010] Additional technical features and benefits are realized through the techniques of the present invention. Embodiments and aspects of the invention are described in detail herein and are considered a part of the claimed subject matter. For a better understanding, refer to the detailed description and to the drawings. BRIEF DESCRIPTION OF THE DRAWINGS

[0011] The subject matter, which is regarded as the invention, is particularly pointed out and distinctly claimed in the claims at the conclusion of the specification. The foregoing and other features, and advantages of the invention are apparent from the following detailed description taken in conjunction with the accompanying drawings in which:

[0012] FIG. 1 is a block diagram of components of a platform for monitoring and controlling sprayers in accordance with one or more embodiments of the present invention;

[0013] FIG. 2 is a flow diagram of a process for selecting different functionalities for a sprayer in accordance with one or more embodiments of the present invention;

[0014] FIG. 3 is a flow diagram of a process for cleaning a sprayer in accordance with one or more embodiments of the present invention;

[0015] FIG. 4 is a flow diagram of a process for performing spray preparation in accordance with one or more embodiments of the present invention;

[0016] FIG. 5 is a flow diagram of a process for adding product names, formulations, and dosages to be used in a sprayer in accordance with one or more embodiments of the present invention;

[0017] FIG. 6 is a flow diagram of a process for selecting droplet size in accordance with one or more embodiments of the present invention;

[0018] FIG. 7 is a flow diagram of a process for displaying instructions about regulation and calibration of a sprayer in accordance with one or more embodiments of the present invention;

[0019] FIG. 8 is a flow diagram of a process for displaying nozzle recommendations in accordance with one or more embodiments of the present invention; [0020] FIG. 9 is a flow diagram of a filtering system process in accordance with one or more embodiments of the present invention;

[0021] FIG. 10 is a flow diagram of a process for selecting options and parameters for a spray tank in accordance with one or more embodiments of the present invention;

[0022] FIG. 11 is a flow diagram of a process for selecting tank agitation in accordance with one or more embodiments of the present invention;

[0023] FIG. 12 is a flow diagram of a process for calculating operation field capacity in accordance with one or more embodiments of the present invention;

[0024] FIG. 13 is a flow diagram of a process for selecting parameters for orchard spray functionality in accordance with one or more embodiments of the present invention;

[0025] FIG. 14 is a flow diagram of a process for calibrating pressure in accordance with one or more embodiments of the present invention;

[0026] FIG. 15 is a schematic illustration of a cloud computing environment in accordance with one or more embodiments of the present invention;

[0027] FIG. 16 is a schematic illustration of an abstraction model layers in accordance with one or more embodiments of the present invention; and

[0028] FIG. 17 is a schematic illustration of a computer system in accordance with one or more embodiments of the present invention.

[0029] The detailed description explains embodiments of the invention, together with advantages and features, by way of example with reference to the drawings.

DETAILED DESCRIPTION

[0030] One or more embodiments of the present invention provide a platform for easily monitoring and controlling industrial sprayers, such as sprayers used by farmers in crop fields to apply fungicides. In accordance with one or more embodiments of the present invention, the platform includes a mobile application executing on a mobile device that is configured to display main procedures and pathways to correctly work with specified pesticides and/or fertilizers. Fungicides are used in several of the examples described herein as an example of a pesticide and/or fertilizer. One skilled in the art will recognize that embodiments of the present invention are not limited to fungicides as embodiments may be utilized by any product(s) capable of being applied using a sprayer device. The procedures and pathways provided by one or more embodiments of the present invention can include instructions for both the handling of the fungicides, as well as suggested settings for the sprayer device that will be used to apply the fungicides. The instructions can be directed, for example, to teaching the order of mixture, recommending particular fungicides, and recommending a filtering system for the sprayer device. The use of embodiments of the mobile application described herein to provide guidance and assistance to end users can result in avoiding and/or to solving most of the common sprayer problems without requiring an on-site visit by an employee of the fungicide or sprayer company.

[0031] As known in the art, fungicides are characterized by products and formulations with very low solubility in water which may accumulate in the bottom of the sprayer tanks if agitation is not enough or if the sequence of adding products to the mixture is incorrect. In accordance with one or more embodiments of the present invention, procedures are provided to instruct a user in the correct way to adjust the agitation; how to prepare the sprayer to receive the mixture; and the correct order of addition of the intended products, from the less soluble to the more soluble ones. If the guidance is followed, the agitation and homogeneity of the products is correct and no sediments will be formed to provide nozzle clogging or pump damage.

[0032] One or more embodiments of the present invention provide technological improvements over current methods for providing guidance and assistance in the use of an industrial sprayer. [0033] Current approaches, such as the mobile applications described above, do not provide criteria for order of addition of formulations and filter sizes, or optimal work pressure, speed and spray volume recommendations. Example embodiments of the present invention provide technical solutions to the above noted deficiency of existing solutions by ordering the formulation more precisely, describing the correct size of the possible filters and if they are necessary or not, warning if the pressure is higher or lower than the optimal range and if the spray volume and ground speed are suitable for fungicide sprays. This allows the sprayer to be correctly assembled with the right filters in order to avoid nozzle clogging as well as to keep the added products more evenly suspended inside the tank mixture.

[0034] Current approaches, such as those described in the patent publications noted above, do not provide information about the filters to be used, a nozzle identifier (e.g., color) according to the best range of pressure, the calculus of necessary agitation on the sprayer, or information on how to prepare the mixture outside and inside the sprayer. Example embodiments of the present invention provide technical solutions to the above noted deficiency of existing solutions by indicating recommended filters and their numbers and identifiers, if the nozzle is appropriate or not to the spray, if the sprayer is capable or not to provide a good agitation inside the tank, and by indicating a precise order or addition and procedures.

[0035] The use of one or more embodiments of the present invention can considerably decrease the number of problems occurring in the field due to lack of correct information. In addition, one or more embodiments of the present invention can provide an increase in customer satisfaction by allowing the sprayers to be used in the most efficient manner with less down time due, for example, to required repairs and/or unclogging of the nozzles. In addition, the spraying may be of higher quality (e.g., more efficient spraying) when guidance is provided (and followed) about how to mix the product being sprayed and settings for the sprayer. In addition, customer satisfaction can be improved by fostering a relationship of trust between sales employees and the costumers by delivering orientation and quality in sprays. Further one or more embodiments of the present invention can aid farmers by offering superior crop protection products and safety during sprays.

[0036] Turning now to FIG. 1, a block diagram 100 of components of a platform for monitoring and controlling sprayers is generally shown in accordance with one or more embodiments of the present invention. The block diagram 100 of FIG. 1 includes an industrial sprayer 102, a mobile device 106, and a database 112. In accordance with one more embodiments of the present invention, the database 112 includes sprayer information 110 that can include configuration information about the sprayer 102 such as its number of nozzles 104 and a date that it was last serviced. At least a subset of the sprayer information can be obtained based on a serial number of the sprayer 102 which may be entered manually or obtained automatically via the mobile device. The database 112 also includes product information 116 which can include recommended sprayer settings and recommended sprayers for particular products (e.g., pesticides and fertilizers). In one or more embodiments of the present invention, the product information 116 is obtained from a website of a vendor who is selling the product. The database 112 can be implemented using any database or data storage methods known in the art, and can be split across multiple physical storage locations.

[0037] Also shown in the block diagram 100 of FIG. 1 is a mobile device 106 that includes a user interface 114 and a sprayer module 108 for carrying out at least a subset of the processing described herein. The user interface 114 can be used to communicate with a user (e.g., a farmer) of the sprayer in any manner known in the art such as, but not limited to via display, via voice instruction, and via haptic instructions. In accordance with one or more embodiments of the present invention, at least a subset of the sprayer module 108 executes on a processor located on the mobile device. The mobile device 106 can be implemented by any mobile device known in the art such as, but not limited to a mobile telephone and a laptop computer. [0038] The block diagram 100 of FIG. 1 also depicts a sprayer 102 which has nozzles 104. The sprayer 102 may be implemented by any sprayer known in the art.

[0039] The database 112, mobile device 106, and sprayer 102 may be in communication via any short or long range communication method known in the art. They may be implemented as three separate physical components or merged into one or two components. For example, the database 112 may be located on a storage device on the mobile device 106 and/or the sprayer 102. In another example, where the sprayer module 108 automatically updates settings on the sprayer 102, a portion of the sprayer module 108 may be located on the sprayer 102 and executed by a processor located on the sprayer 102. Those skilled in the art will recognize that a variety of different configurations are possible and the embodiment shown in FIG. 1 is not intended to limit embodiments of the present invention.

[0040] Turning now to FIG. 2, a flow diagram 200 of a process for selecting different functionalities for a sprayer, such as sprayer 102 of FIG. 1, is generally shown in accordance with one or more embodiments of the present invention. The processing shown in FIG. 2 can be performed, for example, by sprayer module 108 executing on a processor located on mobile device 106 and/or sprayer 102 of FIG. 1. As illustrated in FIG. 2, at block 202, a user starts the sprayer module via a user interface such as user interface 114 of FIG. 1 or via a user interface (not shown) on sprayer 102 of FIG. 1. As shown in the embodiment of FIG. 2, the user can select bar spray 204, orchard spray 206, or unit conversion 208. In accordance with one or more embodiments of the present invention, when the user selects orchard spray 206, processing continues as shown in FIG. 13 below.

[0041] Referring to FIG. 2, if the user selects unit conversion 208, then the user may select a variable such as, but not limited to pressure, volume, mass, area and production and enter a value in a desired unit in a list and a plurality (e.g., five, seven, ten) of different conversions will appear. For example, the user may choose the variable“mass” and enter the value 1 with a unit of kg. In accordance with one or more embodiments of the present invention, the application will display seven unit conversions: 1,000 g, 1,000,000 mg, 0.00 Ton, 2.2 lb, 35.27 oz, 0.07 Arroba BR and 0.16 st (pedras). If the user selects bar spray 204 of FIG. 2, then processing continues as shown in FIG. 3 below.

[0042] Turning now to FIG. 3 a flow diagram 300 of a process for cleaning a sprayer is generally shown in accordance with one or more embodiments of the present invention. The processing shown in FIG. 3 can be performed, for example, by sprayer module 108 executing on a processor located on mobile device 106 and/or sprayer 102 of FIG. 1. As illustrated in FIG. 3, at block 302, the user is prompted with instructions on how to clean the sprayer (e.g., the sprayer that the mobile device 106 is currently in communication with). The description is via a user interface such as user interface 114 of FIG. 1 or via a user interface (not shown) on sprayer 102 of FIG. 1. In accordance with one or more embodiments of the present invention, the user interface includes a display, and at block 402 a plurality of steps for cleaning the sprayer are shown on the display.

[0043] As shown in FIG. 3, the user can select (e.g., via a user interface) to skip or go back to one or more of the blocks in FIG. 3. The user can either skip (or go back) a group of blocks at a time or they can skip each block separately. At block 304, a screen is displayed for choosing a correct droplet size based on the product to be used during the spraying, as well as the mode of action of the given product and its spray category (e.g., soil or foliar spray, or weed management). As shown in FIG. 3, the user can select a product category via a user interface at block 306, a mode of action at block 308, and a spray category at block 310. Product categories can include, but are not limited to insecticides, herbicides, and fungicides. Mode of action can include, but is not limited to systemic and contact. Spray category can include, but is not limited to foliar, pre- emergent, post-emergent, pre/post-emergent, and soil. Once the user makes the selections, processing continues at block 312 with spray preparation as described below with reference to FIG. 4.

[0044] Turning now to FIG. 4, a flow diagram 400 of a process for performing spray preparation is generally shown in accordance with one or more embodiments of the present invention. The processing shown in FIG. 4 can be performed, for example, by sprayer module 108 executing on a processor located on mobile device 106 and/or sprayer 102 of FIG. 1. As illustrated in FIG. 4, at block 404, the user is prompted, via a user interface, to enter a desired spray volume including specifying a unit as shown in block 402. At block 406, the user indicates the tank sprayer volume. In addition, all of the products to be used can be inserted, based on their formulation, dosage and unit. In accordance with one or more embodiments of the present invention, the sprayer module determines the correct order of addition and the quantity to be put inside the sprayer and inside a bottle to test the compatibility of the solution. Spray volume refers to the quantity of liquid to be sprayed in an area and sprayer tank refers to the quantity of liquid to be used inside the sprayer.

[0045] At block 408, the user indicates whether a bottle test is desired or not. If yes, then block 412 is performed and the user inserts the desired value which is the quantity of liquid to be replied in a small recipient, or bottle. This allows the same behaviour that would occur inside the sprayer tank to be represented in the small recipient. This can avoid having to use a larger volume or quantity of volume to check if the mixture is compatible or not. The user can be assisted in determining the desired value as shown in block 410 by displaying a figure that shows a correct pattern. If the user indicates that a bottle test in not desired, then processing continues at block 414 with adding product names as described below with reference to FIG. 5.

[0046] As shown in FIG. 4, the user can skip the processing shown in FIG. 4 and go directly to block 416 to determine droplet size as described in reference to FIG. 6. Additionally, the user can enter the processing shown in FIG. 4 from the droplet size processing of FIG. 6. The ability to move around the user interface in a user driven order provides flexibility for the user when using the sprayer module functionality.

[0047] Turning now to FIG. 5, a flow diagram 500 of a process for adding product names, formulations, and dosages to be used in a sprayer is generally shown in accordance with one or more embodiments of the present invention. The processing shown in FIG. 5 can be performed, for example, by sprayer module 108 executing on a processor located on mobile device 106 and/or sprayer 102 of FIG. 1. As illustrated in FIG. 5, at block 502, the user enters, via a user interface, a type of product to be used for spraying and the commercial name of the product. At block 504, a formulation is selected by the user which may be chosen according to the label of the product. The formulation can be selected from a list that includes, but is not limited to conditioner, WG (water dispersible granules), WP (water dispersible powder), SC (suspended concentration), OD (oil dispersible concentration), DC (dispersible concentration), CS (suspension of encapsulated), Surfactant Adjuvant, EC (emulsified concentration) - mineral oil, EC (emulsified concentration) -vegetal oil, EC (emulsified concentration) - methyl ether, EC (emulsified concentration), EW (emulsion of oil in water), EO (emulsion of water in oil), ME (micro emulsion), SG (soluble granules), SP (soluble powder), SL (soluble solution), foliar fertilizer and the like.

[0048] The user then inserts the intended dosage at block 506 according to the range in the product label and at block 508 selects a correct unit, according to options that can include but are not limited to: kilograms (kg), grams (g), liters (L), milliliters (mL), kg/lOOL, g/lOOL, L/100L, mL/lOOL, and concentration (%v/v). As shown in block 510, the user can select an additional product(s), when more than one product is to be added to the tank in correct order. When the user selects block 516, the processing continues at block 416 selecting a droplet size as described below with reference to FIG. 6.

[0049] Turning now to FIG. 6, a flow diagram 600 of a process for selecting droplet size is generally shown in accordance with one or more embodiments of the present invention. The processing shown in FIG. 6 can be performed, for example, by sprayer module 108 executing on a processor located on mobile device 106 and/or sprayer 102 of FIG. 1. As shown starting at block 602 of FIG. 6, the user can update the droplet size selected previously in the processing described about with reference to FIG. 3, followed by the spray preparation described in reference to FIG. 4. In accordance with one or more embodiments of the present invention, the user selects droplet size from a user interface screen, where recommendations about the necessary droplet size to be used are provided.

[0050] Once the final droplet size is selected, processing continues at block 606 where a nozzle type is chosen. The user can be presented with nozzle models that will produce the recommended droplet size and user selects the desired nozzle type. The nozzle types can include, but not limited to: hollow cone, hollow cone with air induction, flat twin jet, flat twin jet with air-induction, simple flat fan, and Simple Flat fan with air-induction. The processing continues at block 604 to perform regulation and calibration as described below with reference to FIG. 7.

[0051] Turning now to FIG. 7, a flow diagram 700 of a process for displaying instructions about regulation and calibration of a sprayer is generally shown in accordance with one or more embodiments of the present invention. The processing shown in FIG. 7 can be performed, for example, by sprayer module 108 executing on a processor located on mobile device 106 and/or sprayer 102 of FIG. 1. As shown in FIG. 7, the user inserts, via a user interface, a desired speed to be used during the spray at block 702, an intended spray volume to be used on the area at block 704, and a spacing between each nozzle placed on the bar at block 706. At block 708, the sprayer module calculates a recommended outflow. The processing continues at block 710 with a nozzle recommendation as described below with reference to FIG. 8.

[0052] Turning now to FIG. 8, a flow diagram 800 of a process for displaying nozzle recommendations is generally shown in accordance with one or more embodiments of the present invention. The processing shown in FIG. 8 can be performed, for example, by sprayer module 108 executing on a processor located on mobile device 106 and/or sprayer 102 of FIG. 1. If the nozzle follows a color pattern as determined at block 802, then the user can select block 804 to selects one of the outflow colors to attend to the calculated outflow such as but not limited to orange, green, yellow, purple, blue, red, brown, and gray. Alternatively the user can select block 806 to click on the nozzle color recommended by the sprayer module. The theoretical pressure is calculated by the sprayer module at block 810. Based on the value of the theoretical pressure, the system can also suggest, via the user interface, that the user choose a different nozzle (e.g., based on a color identifying a nozzle type) and repeat the processing starting at block 802. The system suggests that the user work within a specified range of pressure. At block 808, the user selects a theoretical pressure unit for pressure that can include, but is not limited to Bar, PSI, Kgf/cm , Kgf/m , mcs, atm and kPa. At block 812, an outflow per nozzle is collected and at block 814 a unit for the outflow per nozzle is selected. The processing continues at block 816 with recommending filters as described below with reference to FIG. 9.

[0053] Turning now to FIG. 9, a flow diagram 900 of a filtering system process is generally shown in accordance with one or more embodiments of the present invention. The processing shown in FIG. 9 can be performed, for example, by sprayer module 108 executing on a processor located on mobile device 106 and/or sprayer 102 of FIG. 1. The process shown in FIG. 9 offers a recommend scenario of filters to be assembled inside the sprayer. The recommended filters may vary according to the nozzle outflow and model chosen previously. At block 902 the user selects a desired position of each filter that appears on the sprayer. In accordance with one or more embodiments, the recommended filters are displayed to the user while the user is making the selection at block 902. At block 904, the user selects the real filter mesh which appears on the sprayer, according to a list that can include, but is limited to: 15, 25, 30, 50, 60, 80, 100, and 120. The user can also be presented with an image that explains how to find out the mesh value of a given filter. The user can further be presented with a user interface screen that provides an image to help field users to identify the filters already installed in the sprayer. The processing continues at block 906 with recommending spray solutions as described below with reference to FIG. 10.

[0054] Turning now to FIG. 10, a flow diagram 1000 of a process for selecting options and parameters for a spray tank is generally shown in accordance with one or more embodiments of the present invention. The processing shown in FIG. 10 can be performed, for example, by sprayer module 108 executing on a processor located on mobile device 106 and/or sprayer 102 of FIG. 1. At block 1002, the user is asked whether it is necessary to correct the hardness or pH of the water. At block 1006 the user is asked whether particular formulations will be used. Thereafter, procedures to correctly make the spraying liquid and keeping inside the tank are displayed on the screen at one of blocks 1004, 1008, and 1010 based on the user response to the questions. In accordance with one or more embodiments of the present invention, the procedures are stored in database 112 of FIG. 1. Processing continues at block 1012 as described below with reference to FIG. 11.

[0055] Turning now to FIG. 11, a flow diagram 1100 of a process for selecting tank agitation is generally shown in accordance with one or more embodiments of the present invention. In accordance with one or more embodiments of the present invention, when a mechanical or hydraulic type sprayer is chosen, a screen to correctly recommend the user to work with the sprayer agitation process throughout the spray is displayed. At the end, it indicates if the intensity is okay or poor if a hydraulic sprayer is chosen as shown in FIG. 11. For mechanical type sprayers, information appears on a user interface to guide the best usage of the agitator. The processing shown in FIG. 11 can be performed, for example, by sprayer module 108 executing on a processor located on mobile device 106 and/or sprayer 102 of FIG. 1.

[0056] At block 1104, the user selects an agitation type. As shown in FIG. 11, if the user selects mechanical, then processing continues at block 1102 and information to guide the user in using the mechanical agitator are displayed. If the user selects hydraulic at block 1104, then block 1106 is performed and a pump outflow is entered (manually or automatically). Pump outflow information can be found, for example, in sprayer catalogues and refers to the outflow at three bar of pressure. Thereafter, the user is prompted to insert (or alternatively at least a subset of the information is obtained automatically from data stored for example in database 112 of FIG. 1): the maximum capacity of the sprayer tank at block 1114, the size of the bar at block 1112, a number of nozzles in usage on the bar at block 1110, a spacing between the nozzles on the bar at block 1108, a desired spray volume to be used on the area at block 1122, desired speed to be used during the spray at block 1120, a pressure to be used on nozzles at block 1118, and a quantity of agitation expressed in tank return (%) at block 1116 to see if it is okay or poor. The determination of whether the pressure it is okay or poor can be made, for example, by the sprayer module 106 based on data contained in the database 112. Processing continues at block 1124 to calculate operational field capacity as described below with reference to FIG. 12.

[0057] Turning now to FIG. 12, a flow diagram 1200 of a process for calculating operation field capacity is generally shown in accordance with one or more embodiments of the present invention. The processing shown in FIG. 12 can be performed, for example, by sprayer module 108 executing on a processor located on mobile device 106 and/or sprayer 102 of FIG. 1. A user interface to calculate operational field capacity (e.g., the quantity of area treated per hour in Hectares or Alqueires) is output to the user. The user in prompted to insert (or alternatively at least a subset of the information is obtained automatically from data stored for example in database 112 of FIG. 1): the size of the treated area during machine displacement at block 1202, a capacity of the tank at block 1204, a desired spray volume to be used on the area at block 1206, and a desired speed to be used during the spray and preparation time at block 1208. At block 1210 a preparation time that includes individual protection equipment, check nozzles, clean the sprayer and other dedicated time before spraying is started is input by the user (or automatically based on data available to the sprayer module). Thereafter, the user or the sprayer module can insert the time required to refuel a full tank with spraying liquid while the sprayer is stopped at block 1212, an average spraying displacement during the spray on the culture lines at block 1214, an average distance for the sprayer to refuel at block 1216, a speed of the sprayer during the displacement for refuel at block 1218, and an average time required for complete one turn or round with the sprayer at block 1220. The result is then displayed on the screen. The user may then return to a home screen at block 202 where three different options such as, but not limited to, bar spray block 204, orchard spray block 206 and unit conversion block 208 are displayed.

[0058] Turning now to FIG. 13, a flow diagram 1300 of a process for selecting parameters for orchard spray functionality is generally shown in accordance with one or more embodiments of the present invention. The processing shown in FIG. 13 can be performed, for example, by sprayer module 108 executing on a processor located on mobile device 106 and/or sprayer 102 of FIG. 1. The processing shown in FIG. 13 occurs when the orchard spray 206 is selected on the user interface described above in reference to FIG. 2. The user interface (e.g., screen) receives information from the field to regulate the sprays for orchards only. The user may choose a desired variable to calculate at block 1304. If the user wants to calculate nozzle outflow then block 1302 followed by blocks 1308A, 1310A, 1312A, 1314A, 1316, and 1320 are performed. Alternatively, or in addition, if the user wants to calculate spray volume then block 1306 followed by blocks 1308B, 1310B, 1312B, 1314B, 1318 and 1324 are performed. For both nozzle outflow and spray volume, the user inserts desired speed to be used during the spray at block 1308, the number of nozzles in usage at block 1310, sides of sprayer in usage (e.g., one or two) at block 1312, the distance between plant lines at block 1314, and maximum capacity of the tank at blocks 1320 and 1324. Once the outflow of the nozzle and the spray volume are determined, processing can continue at block 1322 with calibrating pressure as described below with reference to FIG. 14.

[0059] Turning now to FIG. 14, a flow diagram of a process for calibrating pressure is generally shown in accordance with one or more embodiments of the present invention. The processing shown in FIG. 14 can be performed, for example, by sprayer module 108 executing on a processor located on mobile device 106 and/or sprayer 102 of FIG. 1. To calibrate the necessary pressure for the sprayer considering the previous outflow, a user interface screen can be presented to the user. The user can be requested to insert the necessary outflow on the nozzle at block 1402, to insert the pressure expected be used on the nozzles at block 1404, and to insert the actual nozzle outflow collected on the sprayer (gives the real pressure needed for the spray) at block 1406. The user can then chose to return to a home screen at block 202.

[0060] In accordance with one or more embodiments of the present invention, a user interface is presented to the user to perform the processing described above with reference to FIGs. 2 through 14. The user interface may be implemented using user interface 114 of FIG. 1 and/or a user interface (not shown) on sprayer 102 of FIG. 1. In accordance with one or more embodiments of the present invention, the user interface is implemented by sprayer module 108 executing on a processor located on mobile device 106 and/or sprayer 102. In accordance with one or more embodiments of the present invention, the user interface is implemented by sprayer module 108 executing on a processor located external to the mobile device 106 and/or sprayer 102. In accordance with one or more embodiments of the present invention, the user interface includes a display.

[0061] In accordance with one or more embodiments of the present invention, data that is available can be presented to the user via a user interface screen and the user can decide whether to use the available data or to over write it with different data. Data can be available (and/or calculated) to the sprayer module from a number of sources such as, but not limited to product specifications, data previously entered by the user, internet sources, and historical usage data. At least a subset of the data may be stored in a database, such as database 112 of FIG. 1 as sprayer information 110 and/or product information 116.

[0062] It is understood in advance that although this disclosure describes the monitoring and controlling of sprayers in reference to cloud computing, implementation of the teachings recited herein are not limited to a cloud computing environment. Rather, embodiments of the present invention are capable of being implemented in conjunction with any other type of computing environment now known or later developed.

[0063] Cloud computing is a model of service delivery for enabling convenient, on- demand network access to a shared pool of configurable computing resources (e.g. networks, network bandwidth, servers, processing, memory, storage, applications, virtual machines, and services) that can be rapidly provisioned and released with minimal management effort or interaction with a provider of the service. This cloud model may include at least five characteristics, at least three service models, and at least four deployment models.

[0064] Characteristics are as follows:

On-demand self-service: a cloud consumer can unilaterally provision computing capabilities, such as server time and network storage, as needed automatically without requiring human interaction with the service’s provider;

Broad network access: capabilities are available over a network and accessed through standard mechanisms that promote use by heterogeneous thin or thick client platforms (e.g., mobile phones, laptops, and PDAs);

Resource pooling: the provider’s computing resources are pooled to serve multiple consumers using a multi-tenant model, with different physical and virtual resources dynamically assigned and reassigned according to demand. There is a sense of location independence in that the consumer generally has no control or knowledge over the exact location of the provided resources but may be able to specify location at a higher level of abstraction (e.g., country, state, or datacenter);

Rapid elasticity: capabilities can be rapidly and elastically provisioned, in some cases automatically, to quickly scale out and rapidly released to quickly scale in. To the consumer, the capabilities available for provisioning often appear to be unlimited and can be purchased in any quantity at any time; and

Measured service: cloud systems automatically control and optimize resource use by leveraging a metering capability at some level of abstraction appropriate to the type of service (e.g., storage, processing, bandwidth, and active user accounts). Resource usage can be monitored, controlled, and reported providing transparency for both the provider and consumer of the utilized service.

[0065] Service Models are as follows:

Software as a Service (SaaS): the capability provided to the consumer is to use the provider’s applications running on a cloud infrastructure. The applications are accessible from various client devices through a thin client interface such as a web browser (e.g., web-based e-mail). The consumer does not manage or control the underlying cloud infrastructure including network, servers, operating systems, storage, or even individual application capabilities, with the possible exception of limited user-specific application configuration settings;

Platform as a Service (PaaS): the capability provided to the consumer is to deploy onto the cloud infrastructure consumer-created or acquired applications created using programming languages and tools supported by the provider. The consumer does not manage or control the underlying cloud infrastructure including networks, servers, operating systems, or storage, but has control over the deployed applications and possibly application hosting environment configurations; and

Infrastructure as a Service (IaaS): the capability provided to the consumer is to provision processing, storage, networks, and other fundamental computing resources where the consumer is able to deploy and run arbitrary software, which can include operating systems and applications. The consumer does not manage or control the underlying cloud infrastructure but has control over operating systems, storage, deployed applications, and possibly limited control of select networking components (e.g., host firewalls).

[0066] Deployment Models are as follows: Private cloud: the cloud infrastructure is operated solely for an organization. It may be managed by the organization or a third party and may exist on premises or off-premises;

Community cloud: the cloud infrastructure is shared by several organizations and supports a specific community that has shared concerns (e.g., mission, security requirements, policy, and compliance considerations). It may be managed by the organizations or a third party and may exist on-premises or off-premises;

Public cloud: the cloud infrastructure is made available to the general public or a large industry group and is owned by an organization selling cloud services; and

Hybrid cloud: the cloud infrastructure is a composition of two or more clouds (private, community, or public) that remain unique entities but are bound together by standardized or proprietary technology that enables data and application portability (e.g., cloud bursting for load-balancing between clouds).

[0067] A cloud computing environment is service oriented with a focus on statelessness, low coupling, modularity, and semantic interoperability. In essence, cloud computing is an infrastructure made up of a network of interconnected nodes.

[0068] Referring now to FIG. 15, an illustrative cloud computing environment 1500 is depicted. As shown, cloud computing environment 1500 comprises one or more cloud computing nodes 1502 with which local computing devices used by cloud consumers, such as, computer 1512 connected to sprayer 1510, mobile device 1508, and sprayer 1506 may communicate. In an embodiment database 1504 is also stored in the cloud and accessed as a node 1502. Nodes 1502 may communicate with one another. They may be grouped (not shown) physically or virtually, in one or more networks, such as Private, Community, Public, or Hybrid clouds as described hereinabove, or a combination thereof. This allows cloud computing environment 1500 to offer infrastructure, platforms and/or software as services for which a cloud consumer does not need to maintain resources on a local computing device. It is understood that the types of computing devices 1504-1510 shown in FIG. 15 are intended to be illustrative only and that computing nodes 1502 and cloud computing environment 1500 can communicate with any type of computerized device over any type of network and/or network addressable connection (e.g., using a web browser).

[0069] Referring now to FIG. 16, a set of functional abstraction layers provided by cloud computing environment 1500 (FIG. 15) is shown. It should be understood in advance that the components, layers, and functions shown in FIG. 16 are intended to be illustrative only and embodiments of the invention are not limited thereto. As depicted, the following layers and corresponding functions are provided: hardware and software layer 1612 includes hardware and software components. Examples of hardware components include: mainframes 1614; RISC (Reduced Instruction Set Computer) architecture based servers 1616; servers 1618; blade servers 1620; storage devices 1622; and networks and networking components 1624. In some embodiments, software components include network application server software 1626 and database software 1628; virtualization layer 1630 provides an abstraction layer from which the following examples of virtual entities may be provided: virtual servers 1632; virtual storage 1634; virtual networks 1636, including virtual private networks; virtual applications and operating systems 1638; and virtual clients 1640.

[0070] In one example, management layer 1642 may provide the functions described below. Resource provisioning 1644 provides dynamic procurement of computing resources and other resources that are utilized to perform tasks within the cloud computing environment. Metering and pricing 1646 provide cost tracking as resources are utilized within the cloud computing environment, and billing or invoicing for consumption of these resources. In one example, these resources may comprise application software licenses. Security provides identity verification for cloud consumers and tasks, as well as protection for data and other resources. User portal 1648 provides access to the cloud computing environment for consumers and system administrators. Service level management 1650 provides cloud computing resource allocation and management such that required service levels are met. Service Level Agreement (SLA) planning and fulfillment 1652 provides pre-arrangement for, and procurement of, cloud computing resources for which a future requirement is anticipated in accordance with an SLA.

[0071] Workloads layer 1654 provides examples of functionality for which the cloud computing environment may be utilized. Examples of workloads and functions which may be provided from this layer include: mapping and navigation 1656; software development and lifecycle management 1658; transaction processing 1660; point cloud to virtual reality data processing 1664; user defined content to point cloud processing 1666; and virtual reality data file generation and delivery processing 1668.

[0072] Turning now to FIG. 17, a schematic illustration of a system 1700 is depicted upon which aspects of one or more embodiments of monitoring and controlling of sprayers may be implemented. In an embodiment, all or a portion of the system 1700 may be incorporated into one or more of the sprayers and mobile devices described herein. In one or more exemplary embodiments, in terms of hardware architecture, as shown in FIG. 17, the computer 1701 includes a processing device 1705 and a memory 1710 coupled to a memory controller 1715 and an input/output controller 1735. The input/output controller 1735 can be, for example, but not limited to, one or more buses or other wired or wireless connections, as is known in the art. The input/output controller 1735 may have additional elements, which are omitted for simplicity, such as controllers, buffers (caches), drivers, repeaters, and receivers, to enable communications. Further, the computer 1701 may include address, control, and/or data connections to enable appropriate communications among the aforementioned components.

[0073] In one or more exemplary embodiments, a keyboard 1750 and mouse 1755 or similar devices can be coupled to the input/output controller 1735. Alternatively, input may be received via a touch-sensitive or motion sensitive interface (not depicted). The computer 1701 can further include a display controller 1725 coupled to a display 1730.

[0074] The processing device 1705 is a hardware device for executing software, particularly software stored in secondary storage 1720 or memory 1710. The processing device 1705 can be any custom made or commercially available computer processor, a central processing unit (CPU), an auxiliary processor among several processors associated with the computer 1701, a semiconductor-based microprocessor (in the form of a microchip or chip set), a macro-processor, or generally any device for executing instructions.

[0075] The memory 1710 can include any one or combination of volatile memory elements (e.g., random access memory (RAM, such as DRAM, SRAM, SDRAM, etc.)) and nonvolatile memory elements (e.g., ROM, erasable programmable read only memory (EPROM), electronically erasable programmable read only memory (EEPROM), flash memory, programmable read only memory (PROM), tape, compact disc read only memory (CD-ROM), flash drive, disk, hard disk drive, diskette, cartridge, cassette or the like, etc.). Moreover, the memory 1710 may incorporate electronic, magnetic, optical, and/or other types of storage media. Accordingly, the memory 1710 is an example of a tangible computer readable storage medium 1740 upon which instructions executable by the processing device 1705 may be embodied as a computer program product. The memory 1710 can have a distributed architecture, where various components are situated remote from one another, but can be accessed by the processing device 1705.

[0076] The instructions in memory 1710 may include one or more separate programs, each of which comprises an ordered listing of executable instructions for implementing logical functions. In the example of FIG. 17, the instructions in the memory 1710 include a suitable operating system (OS) 1711 and program instructions 1716. The operating system 1711 essentially controls the execution of other computer programs and provides scheduling, input-output control, file and data management, memory management, and communication control and related services. When the computer 1701 is in operation, the processing device 1705 is configured to execute instructions stored within the memory 1710, to communicate data to and from the memory 1710, and to generally control operations of the computer 1701 pursuant to the instructions. Examples of program instructions 1716 can include instructions to implement the processing described herein in reference to FIGs. 1-16.

[0077] The computer 1701 of FIG. 17 also includes a network interface 1760 that can establish communication channels with one or more other computer systems via one or more network links. The network interface 1760 can support wired and/or wireless communication protocols known in the art. For example, when embodied in a user system, the network interface 1760 can establish communication channels with an application server.

[0078] In accordance with one or more embodiments of the invention, a system includes: a memory having computer readable instructions; and one or more processors for executing the computer readable instructions, the computer readable instructions controlling the one or more processors to perform operations. The operations include: identifying a type of spray device; receiving, via a user interface of the one or more processors, an identifier of a product to be sprayed by the spray device; receiving, via the user interface, a desired spray parameter; determining a recommended setting for the spray device based at least in part on the type of spray device, a property of the product to be sprayed by the spray device, and the desired spray parameter; and outputting, via the user interface, the recommended setting.

[0079] The system can also include that the operations further include automatically causing the spray device to be set to the recommended setting prior to the product being sprayed by the spray device.

[0080] The system can also include that the product is a fungicide product.

[0081] The system can also include that the system is a mobile device in communication with the sprayer, the identifying is via a signal received at the mobile device from the spray device, and the outputting is to the sprayer for updating a setting of the sprayer based on the recommended setting.

[0082] The system can also include that the operations further include displaying, via the user interface, a plurality of steps for cleaning the spray device.

[0083] The system can also include that at least one additional product is identified to be combined with the product and sprayed by the spray device, the determining is further based at least in part on the at least one additional product, and the operations further comprise outputting a recommended mixture order of the product and the at least one additional product.

[0084] The system can also include that at least one additional desired spray parameter is identified, the determining is further based at least in part on the at least one additional desired spray parameter, and the outputting includes outputting a recommended setting for the at least one additional desired spray parameter.

[0085] The system can also include receiving a mode of action, wherein the determining a recommended setting is further based at least in part on the mode of action.

[0086] The system can also include receiving a spray category, wherein the determining a recommended action is further based at least in part on the spray category.

[0087] The system can also include that the recommended setting includes one or both of a regulation and a calibration of the spray device.

[0088] The system can also include that the desired spray parameter is selected from the group consisting of droplet size, nozzle models, sprayer agitation, time, spraying speed, and nozzle outflow.

[0089] The system can also include that outputting, via the user interface, a quantity of the product to be put inside the spray device. [0090] The system can also include that the desired spray parameter includes at least one of a speed to be used during spray, an intended spray volume to be used in an area, and a spacing between each nozzle placed on a bar of the spray device.

[0091] Other embodiments of the present invention implement the features of the above- described systems in method and computer program products.

[0092] Throughout the specification and claims, the following terms take the meanings explicitly associated herein, unless the context clearly dictates otherwise. The term "connected" means a direct connection between the items connected, without any intermediate devices. The term "coupled" means either a direct connection between the items connected, or an indirect connection through one or more passive or active intermediary devices. The term "circuit" means either a single component or a multiplicity of components, either active and/or passive, that are coupled together to provide or perform a desired function. The term "signal" means at least one current, voltage, or data signal. The term "module" means a circuit (whether integrated or otherwise), a group of such circuits, a processor(s), a processor(s) implementing software, or a combination of a circuit (whether integrated or otherwise), a group of such circuits, a processor(s) and/or a processor(s) implementing software.

[0093] The term“about” is intended to include the degree of error associated with measurement of the particular quantity based upon the equipment available at the time of filing the application. For example,“about” can include a range of ± 8% or 5%, or 2% of a given value.

[0094] The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the disclosure. As used herein, the singular forms“a”,“an” and“the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will be further understood that the terms “comprises” and/or“comprising,” when used in this specification, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, element components, and/or groups thereof.

[0095] The corresponding structures, materials, acts, and equivalents of all means or step plus function elements in the claims below are intended to include any structure, material, or act for performing the function in combination with other claimed elements as specifically claimed. The description of the present invention has been presented for purposes of illustration and description, but is not intended to be exhaustive or limited to the invention in the form disclosed. Many modifications and variations will be apparent to those of ordinary skill in the art without departing from the scope and spirit of the invention. The embodiments were chosen and described in order to best explain the principles of the invention and the practical application, and to enable others of ordinary skill in the art to understand the invention for various embodiments with various modifications as are suited to the particular use contemplated.

[0096] The present invention may be a system, a method, and/or a computer program product. The computer program product may include a computer readable storage medium (or media) having computer readable program instructions thereon for causing a processor to carry out aspects of the present invention.

[0097] The computer readable storage medium can be a tangible device that can retain and store instructions for use by an instruction execution device. The computer readable storage medium may be, for example, but is not limited to, an electronic storage device, a magnetic storage device, an optical storage device, an electromagnetic storage device, a semiconductor storage device, or any suitable combination of the foregoing. A non- exhaustive list of more specific examples of the computer readable storage medium includes the following: a portable computer diskette, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or Flash memory), a static random access memory (SRAM), a portable compact disc read-only memory (CD-ROM), a digital versatile disk (DVD), a memory stick, a floppy disk, a mechanically encoded device such as punch-cards or raised structures in a groove having instructions recorded thereon, and any suitable combination of the foregoing. A computer readable storage medium, as used herein, is not to be construed as being transitory signals per se, such as radio waves or other freely propagating electromagnetic waves, electromagnetic waves propagating through a waveguide or other transmission media (e.g., light pulses passing through a fiber-optic cable), or electrical signals transmitted through a wire.

[0098] Computer readable program instructions described herein can be downloaded to respective computing/processing devices from a computer readable storage medium or to an external computer or external storage device via a network, for example, the Internet, a local area network, a wide area network and/or a wireless network. The network may comprise copper transmission cables, optical transmission fibers, wireless transmission, routers, firewalls, switches, gateway computers and/or edge servers. A network adapter card or network interface in each computing/processing device receives computer readable program instructions from the network and forwards the computer readable program instructions for storage in a computer readable storage medium within the respective computing/processing device.

[0099] Computer readable program instructions for carrying out operations of the present invention may be assembler instructions, instruction-set-architecture (ISA) instructions, machine instructions, machine dependent instructions, microcode, firmware instructions, state-setting data, or either source code or object code written in any combination of one or more programming languages, including an object oriented programming language such as Python, Java, Smalltalk, C++ or the like, and conventional procedural programming languages, such as the "C" programming language or similar programming languages. The computer readable program instructions may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the latter scenario, the remote computer may be connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or the connection may be made to an external computer (for example, through the Internet using an Internet Service Provider). In some embodiments, electronic circuitry including, for example, programmable logic circuitry, field- programmable gate arrays (FPGA), or programmable logic arrays (PLA) may execute the computer readable program instructions by utilizing state information of the computer readable program instructions to personalize the electronic circuitry, in order to perform aspects of the present invention.

[00100] Aspects of the present invention are described herein with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the invention. It will be understood that each block of the flowchart illustrations and/or block diagrams, and combinations of blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer readable program instructions.

[00101] These computer readable program instructions may be provided to a processor of a general purpose computer, special purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks. These computer readable program instructions may also be stored in a computer readable storage medium that can direct a computer, a programmable data processing apparatus, and/or other devices to function in a particular manner, such that the computer readable storage medium having instructions stored therein comprises an article of manufacture including instructions which implement aspects of the function/act specified in the flowchart and/or block diagram block or blocks.

[00102] The computer readable program instructions may also be loaded onto a computer, other programmable data processing apparatus, or other device to cause a series of operational steps to be performed on the computer, other programmable apparatus or other device to produce a computer implemented process, such that the instructions which execute on the computer, other programmable apparatus, or other device implement the functions/acts specified in the flowchart and/or block diagram block or blocks.

[00103] The flowchart and block diagrams in the Figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer program products according to various embodiments of the present invention. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of instructions, which comprises one or more executable instructions for implementing the specified logical function(s). In some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, can be implemented by special purpose hardware -based systems that perform the specified functions or acts or carry out combinations of special purpose hardware and computer instructions.

[00104] While the disclosure is provided in detail in connection with only a limited number of embodiments, it should be readily understood that the disclosure is not limited to such disclosed embodiments. Rather, the disclosure can be modified to incorporate any number of variations, alterations, substitutions or equivalent arrangements not heretofore described, but which are commensurate with the spirit and scope of the disclosure. Additionally, while various embodiments of the disclosure have been described, it is to be understood that the exemplary embodiment(s) may include only some of the described exemplary aspects. Accordingly, the disclosure is not to be seen as limited by the foregoing description, but is only limited by the scope of the appended claims.

Claims

CLAIMS What is claimed is:

1. A system comprising: a memory having computer readable instructions; and one or more processors for executing the computer readable instructions, the computer readable instructions controlling the one or more processors to perform operations comprising: identifying a type of spray device; receiving, via a user interface of the one or more processors, an identifier of a product to be sprayed by the spray device; receiving, via the user interface, a desired spray parameter; determining a recommended setting for the spray device based at least in part on the type of spray device, a property of the product to be sprayed by the spray device, and the desired spray parameter; and outputting, via the user interface, the recommended setting.

2. The system of claim 1, wherein the operations further comprise automatically causing the spray device to be set to the recommended setting prior to the product being sprayed by the spray device.

3. The system of claim 1, wherein the product is a fungicide product.

4. The system of claim 1, wherein the system is a mobile device in

communication with the sprayer, the identifying is via a signal received at the mobile device from the spray device, and the outputting is to the sprayer for updating a setting of the sprayer based on the recommended setting.

5. The system of claim 1, wherein the operations further comprise displaying, via the user interface, a plurality of steps for cleaning the spray device.

6. The system of claim 1, wherein at least one additional product is identified to be combined with the product and sprayed by the spray device, the determining is further based at least in part on the at least one additional product, and the operations further comprise outputting a recommended mixture order of the product and the at least one additional product.

7. The system of claim 1, wherein at least one additional desired spray parameter is identified, the determining is further based at least in part on the at least one additional desired spray parameter, and the outputting includes outputting a recommended setting for the at least one additional desired spray parameter.

8. The system of claim 1, wherein the operations further comprise receiving a mode of action, wherein the determining a recommended setting is further based at least in part on the mode of action.

9. The system of claim 1, wherein the operations further comprise receiving a spray category, wherein the determining a recommended action is further based at least in part on the spray category.

10. The system of claim 1, wherein the recommended setting includes one or both of a regulation and a calibration of the spray device.

11. The system of claim 1 , wherein the desired spray parameter is selected from the group consisting of droplet size, nozzle models, sprayer agitation, time, spraying speed, and nozzle outflow.

12. The system of claim 1, wherein the operations further comprise outputting, via the user interface, a quantity of the product to be put inside the spray device.

13. The system of claim 1, wherein the desired spray parameter includes at least one of a speed to be used during spray, an intended spray volume to be used in an area, and a spacing between each nozzle placed on a bar of the spray device.

14. A method comprising: identifying, using a processor, a type of spray device; receiving, via a user interface of the processor, an identifier of a product to be sprayed by the spray device; receiving, via the user interface, a desired spray parameter; determining, using the processor, a recommended setting for the spray device based at least in part on the type of spray device, a property of the product to be sprayed by the spray device, and the desired spray parameter; and outputting, via the user interface, the recommended setting.

15. The method of claim 14, further comprising automatically, using the processor, causing the spray device to be set to the recommended setting prior to the product being sprayed by the spray device.

16. The method of claim 14, wherein the product is a fungicide product.

17. The method of claim 14, further comprising displaying, using the processor via the user interface, a plurality of steps for cleaning the spray device.

18. The method of claim 14, wherein at least one additional product is identified to be combined with the product and sprayed by the spray device, the determining is further based at least in part on the at least one additional product, and the method further comprises outputting a recommended mixture order of the product and the at least one additional product.

19. The method of claim 14, wherein at least one additional desired spray parameter is identified, the determining is further based at least in part on the at least one additional desired spray parameter, and the outputting includes outputting a

recommended setting for the at least one additional desired spray parameter.

20. A computer program product comprising a computer readable storage medium having program instructions embodied therewith, the program instructions executable by a processor to cause the processor to perform operations comprising: identifying a type of spray device; receiving, via a user interface of the processor, an identifier of a product to be sprayed by the spray device; receiving, via the user interface, a desired spray parameter; determining a recommended setting for the spray device based at least in part on the type of spray device, a property of the product to be sprayed by the spray device and the desired spray parameter; and outputting, via the user interface, the recommended setting.