Diagnostic devices and methods for an irrigation system

Abstract

The present invention discloses a method for testing an irrigation system, involving transmitting a test communication at a frequency different from the nominal communication frequency between a diagnostic irrigation device and a first irrigation device via a conductive wire path. The method further includes receiving the test communication between the diagnostic irrigation device and the first irrigation device, and generating and storing test result data based on the test communication. This innovative method allows for efficient and accurate testing of irrigation systems, enabling quick identification and resolution of potential issues to ensure optimal system performance.

Description

DIAGNOSTIC DEVICES AND METHODS FOR AN IRRIGATION SYSTEMRELATED APPLICATIONS

[0001] This application claims benefit of and priority to U.S. Provisional Application Serial No. 63 / 660,776 filed June 17, 2024 entitled Diagnostic Devices and Methods for an Irrigation System, which is hereby incorporated herein by reference in its entirety.BACKGROUND

[0002] Certain irrigation devices that are part of an irrigation system often rely on sending communications over a wire path. Typically, if the communication devices are able to operate at their intended / specified nominal communication frequency (e.g., their intended baud rate), the system is considered to have been installed correctly and undamaged.

[0003] However, in some circumstances, a wire path may be incorrectly installed, damaged, and / or degraded. Communications may operate at their intended / specified nominal communication frequency, but over time, the wire path may further degrade or introduce communication issues. Until communications at the intended / specified nominal communication frequency begin to occur noticeably to users, such initial low level damage or degradation is not typically easily detectable.SUMMARY

[0004] In some aspects, the techniques described herein relate to a method of testing an irrigation system, including: sending a test communication between a diagnostic irrigation device and a first irrigation device over a conductive wire path at a frequency higher or lower than a nominal frequency of communication; receiving the test communication between the diagnostic irrigation device and the first irrigation device; and, creating and storing test result data from the test communication.

[0005] In some aspects, the techniques described herein relate to a method 1 , wherein sending the test communication further includes: sending the test communication from the diagnostic irrigation device over the conductive wire path to the first irrigation device; and, sending a test result communication from the first irrigation device to the diagnostic irrigation device.

[0006] In some aspects, the techniques described herein relate to a method 2, wherein sending the test communication further includes: sending the test communication from the diagnostic irrigation device over the conductive wire path to the first irrigation device; and, sending a test result communication from the first irrigation device to the diagnostic irrigation device.

[0007] In some aspects, the techniques described herein relate to a method 1 , wherein sending the test communication further includes: sending a test initiation communication by the diagnostic irrigation device over the conductive wire path; receiving the test initiation communication with the first irrigation device; and, sending a test communication from the diagnostic irrigation device to the first irrigation device over the conductive wire path.

[0008] In some aspects, the techniques described herein relate to a method 1 , wherein sending the test communication further includes: sending the test communication from the first irrigation device over the conductive wire path to the first irrigation device.

[0009] In some aspects, the techniques described herein relate to a method 1 , wherein sending the test communication and receiving the test communication are performed a plurality of times as part of a test cycle.

[0010] In some aspects, the techniques described herein relate to a method 6, wherein each test cycle includes sending a plurality of test communications at different incremental frequencies relative to the nominal frequency of communication.

[0011] In some aspects, the techniques described herein relate to a method 6, wherein each test cycle includes sending a plurality of test communications at frequencies higher or lower than a plurality of different nominal frequencies of communication.

[0012] In some aspects, the techniques described herein relate to a method 6, further including performing the test cycle at time intervals of days, weeks, or years.

[0013] In some aspects, the techniques described herein relate to a method 1 , further including analyzing the test result data and characterizing a damage state of the conductive wire path.

[0014] In some aspects, the techniques described herein relate to a method 1 , further including analyzing the test result data and determining a location of damage along the conductive wire path.

[0015] In some aspects, the techniques described herein relate to a diagnostic irrigation device, including: a device body including a processor, a storage device, and software on the storage device and executable by the processor, the software being configured to: send a plurality of test communications between a diagnostic irrigation device and at least a first irrigation device over a conductive wire path at frequencies higher and / or lower than a specified nominal frequency of communication; and, create and store test result data from the plurality of test communications.

[0016] In some aspects, the techniques described herein relate to a diagnostic irrigation device, wherein the software is further configured to receive a plurality of test result communications from the first irrigation device to the diagnostic irrigation device.

[0017] In some aspects, the techniques described herein relate to a diagnostic irrigation device, wherein the software is further configured to send the plurality of test communications at frequencies higher or lower than a plurality of different nominal frequencies of communication.

[0018] In some aspects, the techniques described herein relate to a diagnostic irrigation device, wherein the software is further configured to send the plurality of test communications at a plurality of different incremental frequencies relative to the nominal frequency of communication.

[0019] In some aspects, the techniques described herein relate to a diagnostic irrigation device, wherein the software is further configured to analyze the test result data and determine a location of damage along the conductive wire path.

[0020] In some aspects, the techniques described herein relate to a diagnostic irrigation device, wherein the software is further configured to compare a success rate of the test result communications at the higher frequencies with a success rate of the test result communications at the lower frequencies.

[0021] In some aspects, the techniques described herein relate to a diagnostic irrigation device, wherein the software is further configured to compare a success rate of the test result communications with a predetermined threshold.

[0022] In some aspects, the techniques described herein relate to a diagnostic irrigation device, wherein the software is further configured to display the test result communications grouped by the frequencies higher and / or lower than a specified nominal frequency of communication.

[0023] In some aspects, the techniques described herein relate to a component for a satellite irrigation controller, including: a satellite irrigation controller communication board including a processor, a storage device, and software on the storage device and executable by the processor, the software being configured to: participate in a plurality of test communications between a diagnostic irrigation device and the satellite irrigation device over a conductive wire path at frequencies higher and lower than a specified nominal frequency of communication; wherein test result data from the plurality of test communications are stored by the diagnostic irrigation device.BRIEF DESCRIPTION OF THE DRAWINGS

[0024] The following figures are included to illustrate certain example aspects of the present disclosure and should not be viewed as exclusive or limiting. The subject matter disclosed is capable of considerable modifications, alterations, combinations, and equivalents in form and function, as will occur to one having ordinary skill in the art and having the benefit of this disclosure. The present disclosure references the drawings as follows:

[0025] Fig. 1 illustrates a simplified schematic view of irrigation system 100 according to one example.

[0026] Fig. 2 illustrates a simplified schematic view of connections to a satellite irrigation controller 116 according to one example.

[0027] Fig. 3 illustrates a flow chart of one software method for performing a wire path test according to one example.

[0028] Fig. 4 illustrates a flow chart of a software method for initiating part or an entire test cycle according to one example.

[0029] Fig. 5 illustrates a flow chart of a software method for performing a test cycle according to one example.

[0030] Fig. 6 illustrates an example software interface 170 for displaying and characterizing results communications according to one example.

[0031] Fig. 7 illustrates an example software interface 170 for displaying and characterizing results communications according to one example.

[0032] Fig. 8 illustrates an example software interface 170 for displaying and characterizing results communications according to one example.

[0033] Fig. 9 illustrates an example software interface 170 for displaying and characterizing results communications according to one example.

[0034] Fig. 10 illustrates an example software interface 170 for displaying and characterizing results communications according to one example.

[0035] Fig. 11 illustrates a flow chart of a software method of diagnosis results data from an irrigation device according to one example.

[0036] Fig. 12 illustrates a flow chart in which software of a first irrigation device sends a test communication to a diagnostic irrigation device according to one example.

[0037] Fig. 13 illustrates a flow chart of a method of causing two irrigation devices to perform a test by a diagnostic irrigation device according to one example.

[0038] Fig. 14 illustrates a satellite controller according to one example.

[0039] Fig. 15 illustrates a flow chart for a software method of determining if damage is located along several irrigation devices that are serially connected or daisy chained to a conductive wire path according to one example.

[0040] Fig. 16 illustrates a flow chart for a software method of performing a plurality of communication tests over time, according to one example.

[0041] Fig. 17 illustrates a flow chart of a software method of confirming proper installation or repair of a wire path of an irrigation system according to one example.

[0042] Fig. 18 illustrates a flow chart of a software method of automatically testing and adjusting a nominal frequency of irrigation devices connected to a conductive wire path according to one example.DETAILED DESCRIPTION

[0043] It will be appreciated by persons skilled in the art that the present disclosure is not limited to what has been particularly shown and described herein. A variety ofmodifications and variations are possible in view of the teachings herein without departing their scope, spirit, or intent.

[0044] While different examples may be described in this specification, it is specifically contemplated that any of the features from the different examples can be used and brought together in any combination. In other words, the features of different examples can be mixed and matched with each other. Hence, while every permutation of features from different examples may not be explicitly shown or described, it is the intention of this disclosure to cover any such combinations, especially as may be appreciated by one of skill in the art.

[0045] The terminology used in this disclosure should be interpreted in a permissive manner and is not intended to be limiting. In the drawings, like numbers refer to like elements. Unless otherwise noted, all of the accompanying drawings are not to scale. Unless otherwise noted, the term “about” is defined to mean plus-or-minus 5% of a stated value.

[0046] The terms “communication” and “message” may be used interchangeably in this specification and are intended to mean data that is created by a first device, converted to a transmissible format on a wire path, and received and / or stored by a second device. While a communication or message may momentarily exist as an electrical signal on a wire path, it should be understood to also exist in non-transitive form in a first device and / or a second device. A communication or message may comprise one or more files and be transmitted as one or more data packets.

[0047] Numerical ranges discussed in this specification should be interpreted as both inclusive numerical ranges and as covering / disclosing a plurality of numbers within the ranges. Specifically, a range should be considered to recite numbers that increment by two decimal places (hundredths) for the purposes of support in the claims (e.g., 0.01 , 0.02, 0.03, etc.). Any of these incremented numbers from a range should be understood to have significance and importance in the context of the present specification.

[0048] The terms frequency, data frequency, data rate, baud rate, baud frequency, and similar variations are all used interchangeably in this specification to mean the rate or frequency that data is being sent, communicated, or transmitted on a wire path. Different communications formats and techniques may have different types or manifestations of these terms.

[0049] The present specification is generally directed to devices and methods for characterizing damage to communication wire paths of an irrigation system. More specifically, the described devices and methods may help determine if damage to a communication wire path has occurred, what type of damage to a communication wire path has occurred, and / or a general location of the damage to a communication wire path. This information may also be used in various ways, such as to remotely confirm if irrigation equipment has been properly installed or to monitor the degradation of wire paths over time.

[0050] Background information on irrigation systems will be discussed first, followed by a discussion of the method and protocol for characterizing damage to a communication wire path of an irrigation system, and finally different methods of using data obtained through the method and protocol.

[0051] Irrigation systems for large irrigation sites (e.g., golf courses, parks, or sports arenas) may take a variety of different forms, utilizing different types of equipment and layouts. Typically, such irrigation systems may include a central controller that manages the irrigation schedules of the entire system and communicates or controls other irrigation equipment in the system.

[0052] Fig. 1 illustrates a simplified schematic view of irrigation system 100. A central irrigation controller 102 may be connected to an irrigation interface 104 that communicates with a plurality of irrigation equipment 110.

[0053] In some examples, the central controller 102 comprises a computer (e.g., a P.C.) having a processor, memory (e.g., RAM), a storage device (e.g., a hard drive), oneor more inputs (e.g., a keyboard and mouse), and a display (e.g., a monitor). The computer may be configured to execute software or code stored on the storage device in a non-transitory form, such as an operating system and central control software.

[0054] The central controller 102 may create and execute an irrigation schedule, store and display data (e.g., equipment data, weather sensor data, etc.), and may communicate and control at least some of the plurality of irrigation equipment 110 either directly or indirectly via the irrigation interface 104 and the other plurality of irrigation equipment 110 (e.g., one or more satellite controllers).

[0055] The irrigation interface 104 may be in communication with the central controller 102 either directly via one or more wires or wirelessly. The irrigation interface 104 may act as a communication interface between the plurality of irrigation equipment 110, which may often be numerous, and the central controller 102. In that regard, the communication between the central controller 102 and the irrigation interface 104 may be a different protocol than the irrigation interface 104 and the plurality of irrigation equipment 110. Further, the irrigation interface 104 may communicate with one or more protocols where different types of equipment may be included in the irrigation system 100. For example, the irrigation interface 104 may communicate with a satellite irrigation controller via a satellite irrigation controller protocol (e.g., a variation of a DF1 protocol) or with a two-wire decoder (often attached to a sprinkler or a water valve) via a two-wire communication protocol. Additionally, while these protocols are often wired protocols (i.e., for transmission over at least one conductive path), the irrigation interface 104 may also communicate via wireless protocols.

[0056] The irrigation interface 104 may comprise a processor, memory (e.g., RAM), a storage device (e.g., a hard drive), and a communication interface (e.g., wired or wireless network interface), among other features, that allow for the execution of software stored in the storage device and / or memory. This may allow the irrigation interface 104 to perform additional functions that the central controller 102 may or may not be capable of, such as creating and sending the messages necessary for a diagnostic test and / orallowing a user to remotely control the irrigation interface 104 via the internet and a remote computer.

[0057] Alternatively, the irrigation interface 104 may not need a processor, memory, and storage, and instead may only include an interface chip (e.g., a serial to TTL interface chip) that changes voltages or similar electrical characteristics to facilitate communicating with a different network protocol used by the plurality of irrigation equipment 110 (e.g., USB from the central controller 102 to a Bell 202 protocol). In such an example, the central controller 102 may include the necessary software to perform and analyze the diagnostic tests described in this specification.

[0058] Specific examples of an irrigation interface 104 may include a Toro Field Interface Unit, a Toro gateway, a Hunter Field Server, or similar types of devices that interface between different protocols.

[0059] In the present example of Fig. 1 , the irrigation interface 104 is connected to a first conductive wire path 106 that then connects irrigation equipment 112A, 112B, through 112N in series (e.g., daisy chained together). Similarly, the irrigation interface 104 is connected to a second conductive wire path 108 that then connects irrigation equipment 114A, 114B, through 114N in series (e.g., daisy chained together).

[0060] In some examples, the plurality of irrigation equipment 110 (e.g., irrigation equipment 112A-112N, 114A-114N) may be satellite irrigation controllers, two-wire decoders, additional communication interfaces, valves, sensors (e.g., soils sensors or weather stations), outdoor lighting systems (outdoor lighting controllers), or similar irrigation related equipment that may communicate via a conductive wire path.

[0061] Fig. 2 illustrates a simplified schematic view of connections to a satellite irrigation controller 116 according to one example. Here the satellite irrigation controller 116 is considered a type of the plurality of irrigation equipment 110. Typically, the central controller 102 communicates irrigation control commands and / or an irrigation schedule tothe satellite irrigation controller 116 such that the satellite irrigation controller 116 may then directly control irrigation equipment connected directly to it.

[0062] In the example of Fig. 2, the satellite irrigation controller 116 may include a two- wire communication board or module that allows it to communicate via a two-wire communication protocol via a first conductive wire path 118 with sprinklers 124A, 124B, through 124N that each include a two-wire decoder module and that are connected in series along the first conductive wire path 118 (e.g., daisy chained together).

[0063] The satellite irrigation controller 116 may also or alternatively include a power board or module that allows it to selectively energize one or more conductive wire paths connected to it, such as a second conductive wire path 120 and / or a third conductive wire path 122. In the present example, the second conductive wire path 120 may be connected to a water valve 126A in fluid communication (e.g., via water pipes) to sprinkler 128A and sprinkler 128B, such that actuation of the water valve 126A causes the sprinkler 128A and sprinkler 128B to irrigate. Similarly, the third conductive wire path 122 may be connected to a water valve 126B in fluid communication (e.g., via water pipes) to sprinkler 128C and sprinkler 128D, such that actuation of the water valve 126B causes the sprinkler 128C and sprinkler 128D to irrigate. Different numbers of this equipment and configurations are also possible.

[0064] Generally, the term conductive wire path or wire path means an electrical path creating a circuit or intending to create a circuit in the case of damage or degradation. A conductive wire path may comprise a single wire with two separate, insulated electrical conductors within it (e.g., having two leads at each end) that is connected to equipment on each end. For example, a wire connected between an irrigation interface 104 and a satellite irrigation controller 116 will create a completed circuit that allows for variations of electrical power of a communication protocol. Depending on the construction of the wire, it may have one or a plurality of conductive wire paths within it. While a conductive wire path between two equipment devices may comprise a single wire with dual conductors, a conductive wire path may also comprise a plurality of equipment devices connected inseries via a plurality of discrete, dual conductor wire segments. The term conductive wire path should not necessarily be limited exclusively to wires. Devices connected to a wire path, themselves, may make up part of a wire path. Hence, while the present specification may focus on damage or deterioration of wires or wire segments, damage or deterioration to devices themselves may also be detected.

[0065] Certain equipment in the irrigation system 100 may include software (e.g., software code or algorithm) that may perform one or more of the following, among other functionality: 1 ) determine if one or more conductive wire paths are correctly installed and communicating as intended, 2) provide a quantified measure of signal fidelity that may indicated stability or damage / degradation, 3) monitor and indicate damage and degradation over time, 4) indicate a need for proactive repair of a conductive wire path, and 5) determine one or more segments of a conductive wire path that may have damage or degradation.

[0066] Generally, these functionalities and others may be achieved, in part, by performing tests that intentionally introduce timing mismatches at different frequencies. Depending on the results of these intentional mismatched frequencies, different aspects of damage or degradation to one or more conductive wire paths may be determined. This may particularly be the case when communications along a conductive wire path otherwise appear to be operating normally during the course of normal operations of the irrigation system.

[0067] During typical operation, digital communication relies on either a carrier waveform or a bit waveform timing itself, to be matched between transmitter and receiver. Modern serial communications typically have a timing mismatch tolerance (e.g., a few percent) within which communication is properly sent and received according to the protocol. For example, if a transmitter on a conductive wire path is nominally transmitting at 115,200 bits per second and the receiver on the conductive wire path receives data at 115,201 bits per second, the difference may not be large enough to interfere with data being communicated.

[0068] However, as a signal on a conductive wire path degrades, the timing mismatch tolerance may be directly affected. For example, physical degradation of the conductive wire path may cause attenuation, line reflection, loss of one of the conductive pairs of the wire path, etc. By intentionally mismatching the timing frequency over a conductive wire path and determining the level or percent above or below the nominal frequency where communication fails, aspects of any communication degradation and therefore physical degradation / damage may be determined and characterized.

[0069] At a high level, software of the present specification may send one or more test data communications between two irrigation devices and at a data frequency or data rate that is higher or lower than a nominal data frequency. This may be performed at several different higher or lower frequencies relative to the nominal data frequency. Based on whether the one or more test data communications are received (or the percentage of message receipt failures), the damage or degradation of a wire path may be characterized or determined. Further, this characterization may include determining what type of damage or degradation may have occurred since different types of damage may cause only certain frequencies to fail such tests. Additionally, the characterization may include determining a general or specific location along a wire path where damage may be present.

[0070] While at least one test communication at a certain frequency may be performed, it may be desirable to perform a plurality of test communications on a specific frequency. This may allow the software to determine which communications were lost or not received and which communications were received. The statistic of this lost / received communications may be represented as a percentage which may help further indicate and characterize damage and / or degradation.

[0071] It should be appreciated that there are several different methods of which one or more test data communications may be sent between a diagnostic irrigation device (e.g., the irrigation interface 104) and a first irrigation device (e.g., a satellite irrigation controller 116). For example, the diagnostic irrigation device may transmit the test datacommunication and the first irrigation device may send a results communication back to the diagnostic irrigation device. In an alternative example, the first irrigation device may transmit the test data communication to the diagnostic irrigation device. Note, test communication and test data communication may be used interchangeably in this specification.

[0072] A diagnostic irrigation device is generally referred to as any irrigation device connected to a conductive wire path that initiates or coordinates a test, as well as optionally stores test result data. A first or second irrigation device (or more irrigation devices) is generally referred to as an irrigation device that participates in a test conducted or coordinated by the diagnostic irrigation devices. The diagnostic irrigation device, as well as the first and second irrigation device may comprise any device that is part of an irrigation system and that communicates via a conductive wire path.

[0073] Fig. 3 illustrates a flow chart of one software method for performing a wire path test according to one example. Starting with step 150, the software may cause a test communication from a diagnostic irrigation device (e.g., the irrigation interface 104) over a conductive wire path at a frequency higher than or lower than a nominal frequency of the hardware and communication protocol of the first irrigation device.

[0074] The nominal frequency is generally defined as the communication frequency or baud rate that normal, non-test, communications are intended to operate on. The nominal frequency may be specified in the firmware / software for any of the irrigation devices and may also be adjusted to different nominal frequencies. Example nominal frequencies may include 9600 baud, 14400 baud, 19200 baud, 28800 baud, or any other frequencies above, below, or in between these frequencies.

[0075] In step 152, the test communication is received (or possibly not received in the case of conductive wire path damage) by a first irrigation device (e.g., a satellite irrigation controller 116) connected to the conductive wire path. In step 154, the first irrigation device sends a results communication to the diagnostic irrigation device indicating whether the test communication was received. In step 156, a damage or deteriorationstate of the conductive wire path may be determined based on receiving (or possibly not receiving) the results communication. This determination may occur after a single test communication or after a plurality of test communications are sent, and may further include displaying the results of the one or more test communications and either allowing the user to analyze the data and / or allowing the software to analyze the data, as discussed in further detail below.

[0076] The diagnostic irrigation device may be almost any device that communicates on a conductive wire path that is part of the irrigation system 100. In one example, the central controller 102 and / or the irrigation interface 104 may be the diagnostic irrigation device. In another example, the diagnostic irrigation device may comprise a cloud server that communicates with a local device, such as the irrigation interface 104 or central controller 102. In another example, the diagnostic irrigation device may include a portable device that may be temporarily connected along a conductive path. Such a portable device may be further attached to a laptop, tablet, or phone. The device that is being tested (e.g., a first irrigation device) may be any device connected directly to a conductive path to communicate with one or more other devices on the conductive path and / or the irrigation system 100 (e.g., a satellite irrigation controller, two-wire decoders, valves, an irrigation interface, a central controller, a moisture or weather sensor, or similar devices). It should be understood that, in order to communicate over a conductive path, the diagnostic irrigation device and the first irrigation device may have a processor, a data storage device, memory, software / firmware for generating, receiving, and processing communications on a conductive path, and a physical electrical interface or terminal that creates an electrical connection to the conductive wire path.

[0077] The test communication may be an electronic data communication of almost any size and almost any content / payload. In some examples, the test communication may include random data (e.g., a number or text), certain data related to the testing procedure, such as an identification of the first irrigation device, an intended speed of the communication, a time at which the test communication was initiated, and similar items. In other examples, the test communication may be regular or typical communications fromthe first device that are sent at a higher or lower data frequency than a nominal data frequency for a temporary period of time. In other words, the first irrigation device may simply transmit normal data faster or slower over a period of time while specifying such a temporary frequency change (e.g., in the data of the messages / packets sent).

[0078] In some examples, certain test data may be included to provide enhanced damage detection. For example, certain test data may help further test for D.C. drift problems. The detection of such D.C. drift problems may further indicate damage to a wire path. Typically, D.C. Drift problems occur when a signal on the wire path drifts too high or too low relative to its intended range. In one example, the content / payload of the test communication may be data packets or bits of the same or mostly the same data / bits, such as 00 00 00 00 or FF FF FF FF. When the data bits are encoded with voltage changes, multiple 1 bits or multiple 0 bits may cause “drifting” towards a specific voltage, on average. If the voltage is already drifting due to damage, causing additional drifting in this manner may cause communication issues along certain portions of the wire path and at certain frequencies which may indicate damage to the wire path. Hence, the method of sending a test communication may include sending one or more test communication with packets / content having the same or mostly the same bits / content to cause some D.C. drift. The method may further include sending at least one first test communication with several first bits (e.g., a plurality of “1” bits) and at least one second test communication with several second bits (e.g., a plurality of “0” bits).

[0079] Regarding step 150, the test communication may be initiated and sent in several different ways. Fig. 4 illustrates a flow chart of a software method for initiating part or an entire test cycle according to one example. In step 160, a diagnostic irrigation device transmits a test initiation communication over a conductive wire path.

[0080] A test initiation communication may include data relevant to beginning a test with the first device. For example, the test initiation communication may include a test nominal baud value (e.g., a byte in the communication) that indicates the nominal baud rate to change communications to either for a determined temporary time or indefinitely.Often, communication equipment may be able to switch to different nominal communication data rates (e.g., 1 ,200 baud, 9,600 baud, 19,200 baud, 38,400 baud, 57,600 baud, or 115,200 baud). Again, once set to a specific test nominal baud value, a communication component of a device typically will only process data within a set percentage above or below that nominal data baud rate (e.g., commonly 3.5% above or below).

[0081] In another example, the test initiation communication may include a test timeout value (e.g., a byte in the communication) that indicates how long the test nominal baud value should be maintained (e.g., a specified period of time or indefinitely until otherwise changed again).

[0082] In another example, the test initiation communication may include a test incremental baud value (e.g., a byte in the communication) that indicates an incremental baud value (also referred to as an incremental frequency value) that is increased or decreased relative to the specified nominal baud value. The test incremental baud value may be a data value that indicates the specific number of bauds that should be increased or decreased relative to the specified test nominal baud value (e.g., 10 bauds), a percentage increase or decrease relative to the specified nominal baud rate (e.g., 2%), or a similar data value indicating such a change.

[0083] In step 162, the test initiation communication is received by a first irrigation device through the conductive wire path. In some examples, the first irrigation device may send a confirmation communication that the test initiation communication was received (e.g., on whatever baud rate or frequency the first device and the diagnostic irrigation device were originally communicating on). The first irrigation device may then set its nominal baud rate (i.e., the baud rate or frequency at which it is listening for communications) to the nominal baud rate in the test initiation communication (but not with the specified incremental baud value of the test initiation communication).

[0084] In step 164, the diagnostic irrigation device sends one or more test communications at a higher or lower frequency than the nominal frequency (e.g., nominalbaud rate) over the conductive wire path to the first irrigation device. Specifically, the diagnostic irrigation device may transmit a test irrigation communication at the test incremental baud value of the test initiation communication.

[0085] The first irrigation device may either receive the test irrigation message in its full unchanged form, may receive a corrupted message, or may not receive any message at all. Upon receipt of the test irrigation communication in either an unchanged form or a corrupted form, the first irrigation device may send a test acknowledgement communication to the diagnostic irrigation device. In some examples, the test acknowledgement communication may contain data indicating that the message was received in an unchanged form or a corrupted form. In one example, this may be achieved with a checksum or cyclic redundancy check (CRC). A checksum value may be stored in the test irrigation communication and the checksum test performed on the contents of the message by the first irrigation device. Hence, the test acknowledgement may contain the results of such a checksum test (e.g., success or failure). In some examples, the test acknowledgement communication may contain data indicating that a timeout period has expired. The diagnostic irrigation device may receive the test acknowledgement communication and then store the data in its memory, to be used in one or more ways discussed later in this application.

[0086] While sending the test communication in step 164 may be performed once, with only a single test incremental baud value, a plurality of test communications may also be transmitted. Fig. 5 illustrates a flow chart of a software method comprising, in step 166, performing a test cycle by sending a plurality of test communications from a diagnostic irrigation device over a conductive wire path at a frequency higher or lower than a nominal frequency (e.g., nominal baud rate), and in step 168, storing a plurality of results communications that result from each of the plurality of test communications.

[0087] In some examples, the test communication (and the response of the test acknowledgement communication) may be performed within an inclusive range of 1 to 30 times, including a plurality of times for each test incremental baud value. As noted above,each occurrence will produce a results communication from the first irrigation device. By sending a plurality of test communications, the diagnostic irrigation device may store all the results communications. In some examples, statistical values for each test incremental baud value may be created, such as a percentage of successfully transmitted test communications sent.

[0088] Additionally, steps 160, 162, and 164 may also be performed multiple times as a plurality of test cycles performed on different test nominal baud values and test incremental baud values. For example, test cycles may be performed on one or more of the following test nominal baud rates: 300, 600, 1200, 2400, 9600, 14,400, 19,200, 28,900, 38,800, 57,600, 115,200, 128,00, 230,400, 256,000, 460,800, 512,00, and 912,600.

[0089] For each test of a nominal frequency (e.g., nominal baud rate), one or a plurality of test cycles may be performed on one or a plurality of test incremental baud values. Most modern electronic communication interfaces are designed to operate within a predetermined range of a nominal baud rate (typically 3.5% above and 3.5% below the nominal baud rate for UART speed tolerance limits). For that reason, it may be desirable in some examples to only use test incremental baud values within such a predetermined range of a nominal baud rate of a device or slightly higher. In some examples, the test incremental baud values represent values increments within a predetermined range. For example, 0.5% increments, such as 0.5%, 1.0%, 1.5%, 2.0%, 2.5%, 3.0%, 3.5%, -0.5%, -1.0%, -1.5%, -2.0%, -2.5%, -3.0%, and -3.5%. In another example, 1 % increments, such as 1 %, 2%, 3%, 4%, 5%, -1 %, -2%, -3%, -4%, and -5%. In that respect, the diagnostic irrigation device may end up with many test results data for different test incremental baud values for different test nominal baud values.

[0090] The step 168 of storing the plurality of results communications may be performed by the diagnostic irrigation device. The results communications may be stored in a storage device that is part of the diagnostic irrigation device (e.g., a hard drive orsimilar memory), or may be stored on a remote device (e.g., a hard drive of a central irrigation controller or cloud server).

[0091] Once the one or plurality of results communications are stored, they may also be viewed and analyzed / characterized (e.g., step 156 in Fig. 3). This review and characterization may be performed in a variety of different ways. In one example, Figs. 6 and 7 illustrate an example software interface 170 for displaying and characterizing results communications. The software interface 170 may include a plurality of nominal baud rate tabs 172 that allow a user to view different sets of data based on what nominal baud rate was tested. Selecting one of these plurality of nominal baud rate tabs 172 displays a set of results data in data area 174 for one or more irrigation devices. This results data may be in the form of a percentage statistic (e.g., percentage of successful test communications sent), a text indication (e.g., “pass” or “fail”) or similar displays. Results data may also be displayed for each incremental baud communication / value that was tested. In the present example, the incremental baud value may represent a percentage above or below the nominal baud rate that was tested.

[0092] In some examples, a user may make a determination themselves by simply looking at the results data and determining where and at what baud rate / frequency failures in communication occurred.

[0093] In other examples, the software (e.g., executed by the diagnostic irrigation device) may make a characterization or diagnosis of a possible problem with a wire path (or lack of a problem). In that respect, diagnosis area 176 may display any possible diagnosis of a wire path between the diagnostic irrigation device and each test irrigation device (e.g., irrigation device 1 , 2, 3, in data area 174).

[0094] The software interface 170 of Fig. 6 illustrates the “9600” tab of the plurality of nominal baud rate tabs 172 as being selected and showing data for that nominal baud rate. Fig. 7 illustrates the “28800” tab of the plurality of nominal baud rate tabs 172 as being selected and showing data for that nominal baud rate. The data area 174 in Fig. 6 illustrates test data that indicate all test communications were received for a nominal baudrate test at 9600 baud. The 174 in Fig. 7 illustrates test data that indicates most test communications were received for a nominal baud rate test at 28800 baud. However, some higher incremental baud values for “irrigation device 2” and “irrigation device 3) show some communication failures at increased incremental baud values. Such failures, such as at relatively high nominal baud rates and at higher incremental baud values may still be considered normal or acceptable, and may be the result of a relatively long wire connection between two irrigation devices. In some examples, the software interface 170 may include an input or a reference file with data on the distance of the wire used to connected irrigation devices and the diagnostic irrigation device. In examples where the software analyzes the data and provides a diagnosis in the diagnosis area 176, it may factor such a distance via a formula or predetermined adjustment, under which some unsuccessful test results data are ignored.

[0095] In some examples, the software, or alternatively a user, may make a characterization or possible diagnosis by reviewing a plurality of the results data for an irrigation device. Fig. 11 illustrates a flow chart of a software method of diagnosis results data from an irrigation device.

[0096] In step 180, the results data from test of a plurality of incremental baud communications (e.g., steps 166 and 168 of Fig. 5) is reviewed by the software and, in step 182, compared to one or a plurality of thresholds. Depending on whether the results meet one or a plurality of the thresholds, a possible diagnosis is displayed on a software interface (e.g., software interface 170).

[0097] The one or the plurality of thresholds may be a threshold used to compare results data for individual results data, such as a single results data for a single incremental baud value. In other words, each of the results data may be compared against a threshold that may trigger a possible diagnosis that the software displays or that triggers comparison with another, different threshold. The one or the plurality of thresholds may be a threshold used to compare a group or plurality of individual results data. For example, whether any increased incremental baud value data results meet acertain threshold, whether any decreased incremental baud value data results meet a certain threshold, whether any data result for a nominal baud rate meets a certain threshold, whether any groups of data results for high nominal baud rates meets a certain threshold, or whether any groups of data results for high nominal baud rates meets a certain threshold.

[0098] In some examples, a threshold may be predetermined, such as hard coded in the software or determ ined / adjusted by a user. In other examples, a threshold may be dynamic based on other factors, such as a high level of communication traffic from normal operations on the wire path being tested.

[0099] One such threshold may indicate if no communication issues with the wire path between a diagnostic irrigation device and a first irrigation device (or other irrigation devices) is detected. In one example, if all of results data for a first irrigation device are successful (e.g. , 100%) for all incremental baud values, the software may display a results message indicating that no communication issues were detected. In another example, if some of the results data from a first irrigation device have a relatively high successful communication result above an upper success threshold, the software may display a results message indicating that no communication issues were detected. For example, a threshold for any of the incremental baud values may be 95%, 96%, 97%, 98%, or 99%, above which will result in the software displaying a results message indicating that no communication issues were detected. Again, these thresholds may be applied to data results for a first irrigation device across all nominal baud rates.

[0100] Other thresholds may help determine a break in a wire path (e.g., one of two conductive paths in a wire are broken). In some circumstances, if tests of relatively high frequencies or baud rates provide successful results (e.g., a relatively high percentage or 100%) but some or all of relatively low frequencies or baud rates provide some or all unsuccessful results, this may indicate a break in the wire path. It is believed that in some circumstances, the broken or severed conductor may have a tiny “air gap” or may have “dirty water” between its two broken ends, acting as a capacitive element and therebypassing mostly relatively higher frequencies that are transmitted or sent on the wire path. The amount that the soil or gap for the broken conductive path conducts may depend on several factors, such as soil type (e.g., what type of minerals or other materials are in the soil), moisture level (wet soil may conduct better than dryer soil), and soil temperature.

[0101] In other circumstances, if test communications to a first irrigation device are successful but test communications to subsequent irrigation devices (e.g., devices 2 and 3) are partially or fully unsuccessful, such a threshold may indicate that a break in a conductive path may have occurred. For example, Fig. 8 illustrates the software interface 170 in which the data area 174 illustrates fully successful test data for irrigation device 1 , but relatively unsuccessful test data from irrigation device 2 and irrigation device 3. Since some of the test communications are passing through at the “0” incremental baud value (i.e. , the nominal baud rate), a user may not necessarily be aware of the communication issue. This example may indicate a conductive path break between irrigation device 1 and irrigation device 2. However, depending on the type of break (e.g., partial, complete, etc.) the actual physical break may occur either prior to or after irrigation device 2 due to effects of the soil or line reflection. Hence, the software may comprise a method of comparing test data between a first irrigation device and a second irrigation device, and alerting a user if a predetermined threshold between results of the two devices is exceeded. In some examples, such a threshold may be a difference in test results over a certain percentage, such as a percentage within a range of about 50-100%.

[0102] In some examples, a threshold may be any incremental baud values that are lower (e.g., negative) than the test nominal baud value or nominal baud rate and that have unsuccessful results data (e.g., less than 100%). In other examples, a threshold may be certain incremental baud values (e.g., -2%, -3%, -4%, -5%) that are lower (e.g., negative) than the test nominal baud value or nominal baud rate and that have unsuccessful results data (e.g., less than 100%).

[0103] In some circumstances, if tests of relatively low frequencies or baud rates provide successful results (e.g., relatively high percentage or 100%) but some or all ofrelatively high frequencies or baud rates provide some or all unsuccessful results, this may indicate some shorting of the conductors of a wire or conductive path together, causing an attenuating effect.

[0104] It should be understood that, at some point, even a normally wired conductive path will have a “too high” and “too low” value for different frequencies since the wires may not be able to handle data frequencies above a certain threshold or that the UART chip involved in the communications between devices will eventually “bottom out”. Hence, any analysis or comparison of relatively high frequencies and / or relatively low frequencies may occur within a known range of operations.

[0105] While Figs. 3 and 4 illustrate certain steps of a test method in which the diagnostic irrigation device sends a test communication to a first irrigation device, it should be understood that different steps may also be used to achieve a similar result. For example, the first irrigation device may send the test message communication to the diagnostic irrigation device. In other words, a test message communication should be sent between the diagnostic irrigation device and the first irrigation device, and appropriate test results can be achieved no matter which device sends the test communication.

[0106] In that regard, Fig. 12 illustrates a flow chart in which software of a first irrigation device sends a test communication to a diagnostic irrigation device. These steps are similar to those discussed for Fig. 4 and the terminology and procedures are similar, except as noted below. In step 186, a test initiation communication is sent over the conductive wire path by a diagnostic irrigation device. In step 188, the test initiation communication from the diagnostic irrigation device is received by a first irrigation device connected to the conductive wire path. In step 190, a test communication is sent from the first irrigation device to the diagnostic irrigation device over the conductive wire path.

[0107] In some examples, it may be desirable for a diagnostic irrigation device to cause a test in which one or more test communications are sent between two other irrigation device and then the results of those test are sent back to the diagnostic irrigationdevice. This may be helpful, in some examples, for wire paths in which an initial part of the wire path may be split in a non-serial or daisy chained manner, but further irrigation devices are connected in a serial or daisy chained manner. For example, Fig. 13 illustrates a flow chart of a method of causing two irrigation devices to perform a test by a diagnostic irrigation device. The steps are similar to those previously described except as otherwise noted. In step 192, a test initiation communication is sent over a conductive wire path by a diagnostic irrigation device. In step 194, the test initiation communication is received by a first irrigation device connected to the conductive wire path. In step 196, a test communication is sent to a second irrigation device of the conductive wire path. In step 198, a test result communication is sent back to the diagnostic irrigation device over the conductive wire path. This test result communication may be sent from the first irrigation device or the second irrigation device, depending on which device is designated to receive it (i.e. , similar to the method of Fig. 4 or Fig. 12).

[0108] Additionally or alternatively, the method of Fig. 13 or any of the other methods may, in some circumstances, be used to detect “Y” branching or non-serially linked irrigation devices. Such arrangements may cause line reflection and therefore interfere with communications for some frequencies. This may be particularly helpful if repairs or initial installations are tested to ensure they were installed properly.

[0109] In an alternative example, the diagnostic irrigation device may initiate a test communication by sending a test communication initially, without the need for a test initiation communication, to a first irrigation device over a conductive wire path and then the first irrigation device may send results of the received test communication back to the diagnostic irrigation device. In another alternative example, a diagnostic irrigation device or a first irrigation device may periodically transmit a test communication to another irrigation device or each other, either with or without the need for a test initiation communication, which may be helpful for periodically tracking degradation of wire paths over time.

[0110] The software methods of this specification may be performed by any of the previously described irrigation devices. In that respect, the irrigation devices may include processors that execute software or firmware stored on storage devices (e.g., hard drives, firmware memory chips, or similar storage devices).

[0111] In some examples, some or all of the irrigation devices connected at an irrigation site via wire paths may comprise software that may perform some or all of the software methods described in this specification. However, it may not be necessary for all irrigation devices to have the same software firmware. For example, a diagnostic irrigation device (e.g., an irrigation interface 104 and / or a central irrigation controller 102) may have different software that allows for sending and receiving certain messages and other irrigation devices on the network may have simplified software / firmware necessary to complete some or all of the methods of this specification.

[0112] Some devices, such as the satellite irrigation controller 116 illustrated in Fig. 14 or a two-wire decoder (not shown in Fig. 14), may have wire path communication modules or boards 116A that may be added to the satellite irrigation controller 116 or sprinkler as needed. Hence, this specification specifically contemplates a wire path communication module or board 116A for a satellite irrigation controller (or a two-wire decoder) containing software / firmware capable of performing at least some of the methods described in this specification. Again, such a communication module may have its own processor for executing memory storing its firmware, as well as a wire path interface. It is additionally contemplated that a wire path communication module or board 116A may not initially have such firmware stored in its memory but may be later upgraded via a firmware upgrade. Hence, the present specification also includes the method of updating a wire path communication module or board 116A with firmware that performs some of or all of the test methods described in this specification. Alternatively, any other components of the satellite irrigation controller 116, such as a timing module, may store and / or execute software performing at least some of the methods described in this specification.

[0113] The testing methods of this specification may also be used to determine which sections of a wire path may have damage or degradation, as previously discussed with regard to Fig. 8. This may occur by conducting communication tests on two or more irrigation devices on the same conductive wire path. For example, Fig. 15 illustrates a flow chart for a software method of determining if damage is located along several irrigation devices that are serially connected or daisy chained to a conductive wire path. In step 200, a first communication test is performed between a diagnostic irrigation device and a first irrigation device that are both connected to the same conductive wire path. In step 202, a second communication test is performed between the diagnostic irrigation device and a second irrigation device that is connected to the same conductive wire path as the diagnostic irrigation device and the first irrigation device. Again, these communication tests may be any of the test or variations thereof that are described in this specification.

[0114] In step 204, the software (or alternatively the user) determines if damage is located between or near the diagnostic irrigation device and the first irrigation device or between the first irrigation device and the second irrigation device. If both communication tests include some unsuccessful results, this may indicate that a damaged portion of the conductive wire path is located between the diagnostic irrigation device and the first irrigation device or possibly beyond the first irrigation device since, depending on the type of break (e.g., partial, complete, etc.) the effects of the soil or line reflection may interfere with signals before and after the physical break. If only the second communication test provides unsuccessful test results, but the first communication test provides only (or mostly) successful test results, this may indicate that a damaged portion of the conductive wire path is located at least between the first irrigation device and the second irrigation device, or locations just prior or after those locations. This determination may be made by the software and a diagnosis display may be displayed on a software interface (e.g., software interface 170). While only described for a first and second irrigation device, this method may be performed on many irrigation devices connected serially or daisy chained on the same conductive wire path (e.g., 2, 3, 4, 5, 6, 7, 8, or more devices). Hence, similar techniques may be used to determine which wire path segment may containdamage. These results and analysis may be displayed on the software interface 170, such as shown in Fig. 8.

[0115] The testing methods described in this specification may be performed only once or may be performed multiple times over a period of time (e.g., at regular or different time intervals). This testing data may be stored in a database file (e.g., on the central controller 102) and tracked to see trends over time. For example, increasing unsuccessful test results between an irrigation device (e.g., increasing numbers of incremental baud rate test results or increasing percentages on specific incremental baud rate test results) may indicate that a segment of the wire path is corroding or otherwise degrading over time. In another example, increasing and / or decreasing unsuccessful test results between an irrigation device may be correlated with irrigation cycles to determine if increasing moisture in the soil near a segment of a wire path to the irrigation device may indicate that the insulation to the wire segment is compromised because of degradation or a partial cut / break.

[0116] In that respect, Fig. 16 illustrates a flow chart for a software method of performing a plurality of communication tests over time, according to one example. In step 206, a plurality of communication tests may be performed over a period of time and stored in a storage device (e.g., hard drive). The communication tests may be any or several of those described in this specification. In some examples, the plurality of communication tests may be performed at regular time intervals (e.g., weekly, monthly, etc.) or at irregular intervals (e.g., whenever a user manually schedules a test). In some examples, the time interval between tests is relatively long, such as 1 -7 days, 1 -52 weeks, or 1 -3 years. In some examples, the communication tests at each interval time may comprise communication tests for some or all of the irrigation devices connected to wire paths for communication purposes. In some examples, the data may be stored on a computer (e.g., central controller 102) in a database, log file, or similar file. Fig. 9 illustrates the software interface 170 displaying test data from a first time / date and Fig. 10 illustrates the software interface 170 displaying test data from a second time / date that is later than the first. As can be seen in Fig. 9, “irrigation device 3” demonstrates somedegraded test result data at higher incremental baud values. In Fig. 10, “irrigation device 3) demonstrates increased degradation of test result data at higher incremental baud values.

[0117] In step 208, some or all of the data from the one or more communication tests may be displayed and / or analyzed for patterns or trends. For example, an irrigation device with decreasing percentages of successful test results over time, such as between Fig. 9 and Fig. 10, may indicate corrosion or similar ongoing degradation. In one example, some or all of the data from the communication tests may be displayed (e.g., on software interface 170) as a graph, a chart, or a similar display to convey any changes in communication test results. For example, a chart may display a percentage of test result data values measured over time for particular irrigation devices or several irrigation devices at the same time. In another example, the software may analyze the data from the communication tests and alert a user if a number of unsuccessful tests increases for specific irrigation devices over time, such as unsuccessful tests increase by a predetermined percentage threshold over a predetermined period of time (e g., 5% over one month time). The software interface may then create a visual and / or audio alert for a user and optionally illustrate the data or a graph / chart that illustrates the triggered condition. In another example, a chart may display a percentage of test results data values measure over time, as well as other data that may affect a damages conductive wire path, such as irrigation cycles near a wire path, temperature, weather, maintenance events (e.g., a date / time of conducting work on or near a wire path), and similar data.

[0118] It should be appreciated that the method of Fig. 16 may be used in a predictive manner to alert a user that one or more segments of a conductive path may fail to convey data in the future at a nominal frequency or baud rate.

[0119] The test methods of the present specification may be used to help determine if the wire paths of an irrigation system that are used for communications between irrigation devices were properly installed or repaired (e.g., either a completely new irrigation system or repairs to an existing irrigation system). This may allow a user to perform such testson site or from a remote location to confirm proper installation at an irrigation site. Example installation problems may include installation of a wire with a nick or cut, improper connection of wire ends to equipment, installation of a non-serial “Y” conductive path, or similar installation problems that may interfere with desirable signal transmission.

[0120] For example, Fig. 17 illustrates a flow chart of a software method of confirming proper installation or repair of a wire path of an irrigation system. In step 210, part or all of an irrigation system including one or more wire paths may be installed or repaired by a worker. This may include connecting and / or replacing new wires between irrigation devices, replacing one or more irrigation devices on a wire path, adding one or more new irrigation devices to an existing wire path, or similar work.

[0121] In step 212, communication test (e.g., any of the tests and methods described in this application) may be performed with the irrigation devices that are part of the new installation or repair (e.g., connected to the wire path on which repairs or new irrigation devices added). For example, if a segment of wire is replaced for a wire path, at least the two irrigation devices between the segments may be tested, and possibly all of the irrigation devices that are on the wire path as a whole. In another example, equipment on other wire paths near any work that was performed may also be tested to ensure that damage was not caused to existing wire paths and irrigation devices.

[0122] In step 214, the results of the test result data may be displayed and / or analyzed by the software (e.g., in a similar manner as the methods described in this specification) to help identify any improper installation or inadvertent damage to existing irrigation devices. In some examples, the initiation of the communication tests and / or the displaying / analysis of the test result data may be performed locally at the irrigation site (e.g., by a central controller 102 or an irrigation interface 104) or may be performed by a computer remote from the irrigation site, such as a cloud server or personal computing device that is in communication with a cloud server that may control an irrigation site.

[0123] The testing methods of this specification may also be used to dynamically or automatically determine an optimal or operational frequency for a conductive wire pathand then adjust some or all of the devices on the conductive wire path to the new optimal or operational frequency. For example, Fig. 18 illustrates a flow chart for a software method of determining and setting an optimal or operation frequency for one or more devices on a conductive wire path.

[0124] In step 216, at least one communication test may be performed between a diagnostic irrigation device and at least a first irrigation device connected to a conductive wire path. This communication test may be any of the tests and variations thereof described in this specification.

[0125] The at least one communication test may be performed between the diagnostic irrigation device and only one other irrigation device or with a plurality of irrigation devices connected to the conductive wire path. As previously discussed, this may provide results data about which nominal frequencies are operational (e.g., get at least some data packets through at frequencies higher or lower than a nominal frequency) and which frequencies are performing optimally (e.g., get most or all of its data packets through at frequencies higher or lower than a nominal frequency).

[0126] The software may include an algorithm that selects which nominal frequency is best to communicate on. This may be determined by several factors, such as which of the fastest / highest nominal frequencies operate with little or no errors higher / lower than the nominal frequency. If multiple irrigation devices are present on the conductive wire path and are each tested, the software may select a new nominal frequency based on data from all those irrigation devices tested.

[0127] As seen in step 218, once the software determines a new nominal frequency, it may automatically change the nominal frequency used by all of the irrigation devices connected to that specific conductive path wire, or optionally just one of the irrigation devices on that wire path (i.e., some irrigation devices may have certain nominal frequencies and other irrigation devices may have other nominal frequencies). In one example, this may be performed by the diagnostic irrigation device sending commands to each device instructing it to communicate on the new nominal frequency. In additionto changing the frequency, other communication changes are also possible, such as packet sizes.

[0128] This process of testing and then automatically adjusting the nominal frequency for communications of one or more irrigation devices may be performed at regular time intervals (e.g., daily, weekly, monthly, yearly, etc.). Hence, proper communications with irrigation devices can be maintained in a variety of scenarios. For example, if a conductive wire path is damaged or degraded, the conductive wire path is improperly installed or repaired, or if a conductive wire path has been expanded to include additional length and irrigation devices.

[0129] While the methods of this specification have been discussed primarily in terms of identifying damage or degradation to conductive paths of an irrigation system, they also may be used for other purposes.

[0130] In a first example, the methods of this specification may be used to determine if changes in speed may be used to compensate for damage or degradation. Since wire conductive paths are typically buried underground, they can be difficult and expensive to dig up and repair. In some circumstances, an owner of an irrigation site may wish to use degraded wires as long as possible. By performing one or more of the methods in this specification to obtain test data, a user can determine which frequencies may still be functioning adequately and then may set one or all of the irrigation devices of an irrigation site to the frequency that still functions adequately to convey data. Hence, the present specification includes a method of 1 ) performing one or more of the previously described tests, 2) analyzing the test data for frequencies that can successfully transmit data (either by a human or by the software itself), and 3) transmitting commands to one or more irrigation devices on an irrigation site to switch to a nominal communication frequency that demonstrates successful communication. In the event that multiple segments of a conductive path may have different frequencies that successfully transmit data, the user or software may determine which “successful” frequencies overlap and switch all irrigation devices to those frequencies.

[0131] In another example, the methods of this specification may be used to determine whether further extending a conductive path (e.g., if a new irrigation device is added) will harm communications at certain frequencies. For example, certain lengths of wire may have known amounts (e.g., percentages) that they tend to degrade certain frequencies. Those known degradation amounts may be added to existing test results and displayed for a user. The software may further make recommendations about which frequencies may or may not be substantially impacted with the addition of certain lengths of wire, or may recommend the maximum length of additional wire that can be added before communication issues result at different frequencies.

[0132] It should be understood that the methods described in this specification may be used in several primary ways. First, the methods may provide a raw determination of the range of throughput bandwidth that a conductive path may handle (e.g., slowest to fastest bits per second rate).

[0133] Second, for any given throughput bandwidth, a determination may be made of the robustness of the communication via the methods. This may be expressed as a bit error rate for certain incremental baud values, a “range of transmission remaining” for a conductive path distance, or a “margin” or “timing percentage error” before communication failure, among other examples.

[0134] Third, total throughput bandwidth may be determined via the methods at a system level for all irrigation devices of an irrigation system that use conductive paths or only for specific irrigation devices (e.g., to avoid replacing wires).

[0135] Fourth, the methods may be used to qualify installation of a new irrigation site, qualify maintenance on an existing irrigation site, and / or monitoring changes over time in performance.

[0136] Fifth, the methods may be used to determine the location of failures of the conductive path, since each segment of the conductive path may be measured for throughput bandwidth and robustness.

[0137] Sixth, the methods may be used to measure bandwidth problems and correlate those to possible physical causes. For example, an irrigation site may experience bandwidth loss in a certain conductive path segment and by note characteristics of the loss (severity, high or low speeds, intermittency, correlation to external events or conductions) the problem and its location may be detected. Example physical causes may include one or more wires / conductors may be severed, one or more wires / conductors are starting to short to earth, the wires / conductors are starting to short to each other, additional wire has been incorrectly connected to the conductive path, the conductive path is we or corroding over time, there is foreign material in the cable jacket of the wire, there is noise / interference affecting the wire path, or similar causes.

[0138] Seventh, the methods may be used to predict failure of one or more segments of a conductive path before communications on the system fail at a nominal frequency, and may be further used to initiate repair or adjust a nominal frequency to compensate for any degradation.

[0139] Eighth, the methods may be used to adjust nominal frequencies or baud rates to compensate for long lengths of a conductive path, damage / degradation, or improper installation / repair.

[0140] Ninth, the methods may be further used to slightly modify a standard nominal frequency or baud rate when the nominal frequency / rate is near a frequency with difficulty receiving data. In some situations, mismatching communication transmission timing a little bit can improve communication robustness, by 'offsetting' the effects of bandwidth loss. For example, consider a 3% timing mismatch tolerance to the slow side but only 0.01 % timing mismatch tolerance to the fast side, of a given Bits Per Second speed. By intentionally mismatching timing 1.5% to the slow side, this 're centers' and optimizes timing such that communication is not on the edge of failure.

[0141] Tenth, the methods may be further used over a period of time (e.g., weekly) to monitor for trends in degradation. Additionally, test results may be electronically deliveredto specific individuals, such as maintenance technicians, equipment distributors, manufacturers, technical support personnel, or similar individuals.

[0142] While the present specification has provided examples of devices that include a central controller 102, an irrigation interface 104, and a satellite irrigation controller 116, it should be emphasized that any of the processes / methods / software may be used between two-wire encoders and decoders, as are known in the art. In some examples, the satellite irrigation controller 116 may have a two-wire encoder on it and be connected to a conductive wire path that connects to one or more decoders that control a valve or similar device.

[0143] Additionally, by obtaining input voltage / current values at each decoder, and correlating those to their geo-referenced physical location, the software may determine issues with wire and irrigation devices in terms of location, type of fault, and severity. By including additional sensors to an irrigation network such as acoustic sensing (microphone), Magnetometer (magnetic field strength, magnetic direction, dipole), accelerometer (vibration, motion), temperature and temperature change, the software may determine issues with wire and irrigation devices in terms of location, type of fault, severity, as well as system performance and function.

Claims

What is claimed is:1 . A method of testing an irrigation system, comprising: sending a test communication between a diagnostic irrigation device and a first irrigation device over a conductive wire path at a frequency higher or lower than a nominal frequency of communication; receiving the test communication between the diagnostic irrigation device and the first irrigation device; and, creating and storing test result data from the test communication.

2. The method of testing an irrigation system of claim 1 , wherein sending the test communication further comprises: sending the test communication from the diagnostic irrigation device over the conductive wire path to the first irrigation device; and, sending a test result communication from the first irrigation device to the diagnostic irrigation device.

3. The method of testing an irrigation system of claim 2, wherein sending the test communication further comprises: sending the test communication from the diagnostic irrigation device over the conductive wire path to the first irrigation device; and, sending a test result communication from the first irrigation device to the diagnostic irrigation device.

4. The method of testing an irrigation system of claim 1 , wherein sending the test communication further comprises: sending a test initiation communication by the diagnostic irrigation device over the conductive wire path; receiving the test initiation communication with the first irrigation device; and,sending a test communication from the diagnostic irrigation device to the first irrigation device over the conductive wire path.

5. The method of testing an irrigation system of claim 1 , wherein sending the test communication further comprises: sending the test communication from the first irrigation device over the conductive wire path to the first irrigation device.

6. The method of testing an irrigation system of claim 1 , wherein sending the test communication and receiving the test communication are performed a plurality of times as part of a test cycle.

7. The method of testing an irrigation system of claim 6, wherein each test cycle comprises sending a plurality of test communications at different incremental frequencies relative to the nominal frequency of communication.

8. The method of testing an irrigation system of claim 6, wherein each test cycle comprises sending a plurality of test communications at frequencies higher or lower than a plurality of different nominal frequencies of communication.

9. The method of testing an irrigation system of claim 6, further comprising performing the test cycle at time intervals of days, weeks, or years.

10. The method of testing an irrigation system of claim 1 , further comprising analyzing the test result data and characterizing a damage state of the conductive wire path.11 . The method of testing an irrigation system of claim 1 , further comprising analyzing the test result data and determining a location of damage along the conductive wire path.

12. A diagnostic irrigation device, comprising: a device body comprising a processor, a storage device, and software on the storage device and executable by the processor, the software being configured to: send a plurality of test communications between a diagnostic irrigation device and at least a first irrigation device over a conductive wire path at frequencies higher and / or lower than a specified nominal frequency of communication; and, create and store test result data from the plurality of test communications.

13. The diagnostic irrigation device of claim 12, wherein the software is further configured to receive a plurality of test result communications from the first irrigation device to the diagnostic irrigation device.

14. The diagnostic irrigation device of claim 13, wherein the software is further configured to send the plurality of test communications at frequencies higher or lower than a plurality of different nominal frequencies of communication.

15. The diagnostic irrigation device of claim 13, wherein the software is further configured to send the plurality of test communications at a plurality of different incremental frequencies relative to the nominal frequency of communication.

16. The diagnostic irrigation device of claim 13, wherein the software is further configured to analyze the test result data and determine a location of damage along the conductive wire path.

17. The diagnostic irrigation device of claim 13, wherein the software is further configured to compare a success rate of the test result communications at the higher frequencies with a success rate of the test result communications at the lower frequencies.

18. The diagnostic irrigation device of claim 13, wherein the software is further configured to compare a success rate of the test result communications with a predetermined threshold.

19. The diagnostic irrigation device of claim 13, wherein the software is further configured to display the test result communications grouped by the frequencies higher and / or lower than a specified nominal frequency of communication.

20. A component for a satellite irrigation controller, comprising: a satellite irrigation controller communication board comprising a processor, a storage device, and software on the storage device and executable by the processor, the software being configured to: participate in a plurality of test communications between a diagnostic irrigation device and the satellite irrigation device over a conductive wire path at frequencies higher and lower than a specified nominal frequency of communication; wherein test result data from the plurality of test communications are stored by the diagnostic irrigation device.

Images