Any and all applications for which a foreign or domestic priority claim is identified in the Application Data Sheet as filed with the present application are hereby incorporated by reference under 37 CFR 1.57.
1. Field of the Invention
The present invention relates to residential and commercial irrigation systems used with turf and landscaping, and more particularly to irrigation controllers that execute watering schedules and other landscape related functions in accordance with an operational program.
2. Description of the Related Art
Electronic irrigation controllers have long been used on residential and commercial irrigation sites to water turf and landscaping. They typically comprise a plastic housing that encloses circuitry including a processor that executes a watering program. Watering schedules are typically manually entered or selected by a user with pushbutton and/or rotary controls while observing an LCD display. The processor turns a plurality of solenoid actuated valves ON and OFF with solid-state switches in accordance with the watering schedules that are carried out by the watering program. The valves deliver water to sprinklers connected by subterranean pipes.
Irrigation controllers are manufactured with a wide range of sizes and features. Large irrigation controllers are typically used in commercial applications, golf courses, playing fields, and parks. Large irrigation controllers have the capability of watering many zones, e.g. fifty zones or more, and sometimes have sophisticated features not found in smaller irrigation controllers used in residential applications. For example, large irrigation controllers may have built-in capability for turning sprinklers on and off to optimize the flow of water through the irrigation pipes while meeting the irrigation requirements of the property
The features provided by irrigation controllers continue to evolve to accommodate more complex landscapes and continuously developing strategies to manage water and energy more effectively. Irrigation controllers used in the professional market place tend to be relatively expensive and labor intensive to replace as new features are introduced. There is a growing need to provide different features on different sites. From a cost standpoint, homeowners and professionals do not want to pay for features they do not require. There is also a need to develop irrigation controllers that meet multiple needs of a landscaped property besides just irrigating plants.
At the present time homeowners and professionals can only purchase irrigation controllers with the capability of adding station modules to increase the number of zones, but without feature upgrade capability. This forces distributors to stock a wide range of irrigation controllers, which adds the cost of carrying a large inventory of different types of irrigation controllers. Moreover, as the irrigation needs of a particular landscape site change and/or as government imposes more water usage restrictions, homeowners and professionals are sometimes forced to buy entirely new irrigation controllers.
In accordance with the present invention, a landscape controller includes a housing and a control panel on the housing. The control panel includes a display and at least one manual control that enable a user to enter and/or select a watering schedule. A memory is provided for storing an operational program for carrying out the watering schedule. A processor is connected to the memory and is capable of executing the operational program. A connecting device in the control panel operatively connects at least one feature module to the processor. The controller further includes station control circuitry controlled by the processor that enables the processor to selectively energize a plurality of valves to deliver water to sprinklers in accordance with the watering schedule.
A landscape irrigation system includes an irrigation controller, an RFID tag, and an RFID tag reader. The RFID tag comprises information to modify the operation of the irrigation controller. When the RFID tag is near the RFID tag reader, the RFID tag reader reads the information from the RFID tag and communicates the information to the irrigation controller. The information may include features that are not available without the information.
In an embodiment, the RFID tag is placed inside the irrigation controller. In another embodiment, a feature module comprises the RFID tag and a holder configured to support the RFID tag. In an embodiment, the feature module is inserted into a slot in the control panel of the irrigation controller. In another embodiment, the holder is formed in the door of the irrigation controller. In another embodiment, the holder is formed in the controller housing. In another embodiment, the feature module is carried by an operator and allows the operator access to the features which are not available to others.
Certain embodiments relate to an irrigation system comprising a back plane housed by a housing, a control panel mounted to the housing and configured to enable a user to enter and/or select a watering schedule, where the control panel comprises a memory configured to store an operational program that implements the watering schedule and a processor configured to execute the operational program, at least one feature module configured to provide additional functionality not available without the at least one feature module, where the at least one feature module comprises a radio frequency identification (RFID) tag configured to provide tag information, an RFID tag reader configured to read the RFID tag and to communicate the tag information to the processor, where based at least in part on the tag information, the processor implements the additional functionality, and station control circuitry configured to selectively energize a plurality of valves to deliver water to sprinklers according to the watering schedule, where the station control circuitry is further configured to be removably insertable on the back plane.
In an embodiment, the processor controls the RDIF tag reader. In another embodiment, the reader periodically reads the RFID tag to determine whether the feature module has been removed from a reading range of the RFID tag reader. In a further embodiment, the RFID tag comprises memory that stores the tag information. In a yet further embodiment, the tag information comprises executable code configured to be executed by the processor.
In an embodiment, the tag information comprises authentication information to authenticate the feature module. In another embodiment, the RFID tag reader is further configured to query one or more RFID tags associated with the control panel, and based at least in part on the responses returned from the one or more RFID tags, the processor determines types of the feature modules. In a further embodiment, the RFID tag comprises read/write memory and the RFID tag reader is configured to send data to the RFID tag to be stored in the read/write memory. In a yet further embodiment, the data comprises use information about a use of the at least one feature module.
Other embodiments relate to a method to control a plurality of valves on an irrigation site. The method comprises accepting inputs on a control panel from a user that enable the user to enter a watering schedule, storing the watering schedule in memory that is operatively connected to a processor configured to execute the watering schedule, providing a feature module that comprises a radio frequency identification (RFID) tag and a housing configured to house the RFID tag, where the feature module is configured to provide additional functionality not available without the feature module, reading the RFID tag to obtain tag information, determining, based on the tag information, whether to access the additional functionality provided by the feature module, and selectively turning a power signal ON to a plurality of valves that deliver water to a plurality of sprinklers located on an irrigation site according to the watering schedule.
In an embodiment, reading the RFID tag comprises reading the RFID tag with an RFID tag reader when the RFID tag is within a reading range of the RFID tag reader. In another embodiment, the method further comprises communicating the tag information to the processor. In a further embodiment, the processor and the RFID tag reader communicate over a serial peripheral interface (SPI) connection. In a yet further embodiment, the additional functionality comprises one or more of a feature unlocking function, a user privilege, a new feature enablement function, a module authentication function, a module inventory function, and a health/history log.
Certain embodiments relate to a landscape controller comprising a housing, a control panel associated with the housing and including at least one manual control that enables a user to enter and/or select a watering schedule, a memory storing an operational program to implement the watering schedule, a processor configured to execute the operational program, a radio frequency identification (RFID) tag reader configured to read tag information from an RFID tag when the RFID tag is near the RFID tag reader, where the RFID tag is associated with a feature module that provides additional functionality not available without the feature module. The RFID tag reader is further configured to communicate the tag information to the processor, where based at least in part on the tag information, the processor accesses the additional functionality provided by the feature module. The landscape controller further comprises station control circuitry controlled by the processor that enables the processor to selectively energize a plurality of valves to deliver water to sprinklers according to the watering schedule.
In an embodiment, the operational program includes a set of features capable of being executed by the processor and the additional functionality of the feature module enables a sub-set of the set of features. In another embodiment, the feature module further comprises additional memory that enables the processor to execute at least one feature when the additional functionality is accessed that is otherwise not executable by the processor. In a further embodiment, the operational program comprises at least one locked irrigation feature. In a yet further embodiment, the processor is configured to unlock the at least one locked irrigation feature based at least in part on the tag information. In another embodiment, the station control circuitry comprises an encoder that transmits operational instruction to decoders that are installed outside of the landscape controller.
Throughout the drawings, reference numbers are re-used to indicate correspondence between referenced elements. The drawings, associated descriptions, and specific implementation are provided to illustrate embodiments and not to limit the scope of the disclosure.
The entire disclosure of U.S. patent application Ser. No. 12/181,894 filed Jul. 29, 2008 of Peter J. Woytowitz et al. entitled IRRIGATION SYSTEM WITH ET BASED SEASONAL WATERING ADJUSTMENT, which was published on Feb. 4, 2010 as US 2010/0030476 A1, is hereby incorporated by reference. The aforementioned U.S. patent application Ser. No. 12/181,894 is assigned to Hunter Industries, Inc., the assignee of the subject application.
It would be highly desirable in the irrigation controller marketplace to be able to modify and/or add to features within an existing irrigation controller to customize the irrigation controller for a particular site. It would also be desirable to meet the changing watering needs of the particular irrigation site by allowing an irrigation controller to be upgraded. The present invention provides a landscape controller that can be easily and economically configured and/or upgraded by the user to meet the specific needs of the associated irrigation site. This is accomplished by installing at least one feature module that communicates with the processor of the landscape controller and alters the operational program, changes a functionality of an operational program executed by the processor, and/or provides additional memory capacity. The term “landscape controller” as used herein refers to a device, which can function as an irrigation controller, and optionally perform additional functions on a site besides watering, such as the control of landscape lights and water features, or which can function as a controller that controls any combination of or any one of the functions of a lighting controller and a water feature controller.
The present invention allows the homeowner or professional to purchase a base controller with only the features needed for his or her particular irrigation site. Features can easily be added at a later date to the installed landscape controller. Landscape controllers can thus be readily and economically tailored to meet the different needs of different sites. Distributors can carry a smaller inventory of controllers and still meet the needs of a wide range of customer demands.
The feature module of the present invention is installed into the control panel portion of the controller that typically contains the processor, display, and manual controls where the user enters watering schedules. The feature module can have various designs to meet particular needs. One form of the feature module is a simple electronic key that enables and/or disables features already programmed into the existing memory of the landscape controller. Another form of feature module provides additional memory, thereby allowing the processor to handle more complex tasks not otherwise capable of being performed by the base controller, such as a memory intensive data logging feature. The feature module may contain new programs that are downloaded into the landscape controller and change the functionality of the operational program executed by the processor, thereby enhancing, adding to and/or otherwise changing the functional irrigation features available to the user, such as providing the capability of modifying watering schedules based on ET data, or optimizing the flow of water through the irrigation pipes. In addition to just changing programming in the controller, the feature module may facilitate expanded communications, e.g. wireless communications with an external rain sensor, a soil moisture sensor, or a weather station, and other capabilities such as controlling a pump relay, landscape lighting, and aesthetic water features such as an electric water fountain. Therefore, instead of using the term “watering program” to refer to the overall program executed by the processor to carry out watering schedules, that code is referred to herein using the term “operational program.” The stored watering program includes a comprehensive set of functional irrigation features and the feature module can be configured to unlock less than all of the functional irrigation features. The feature module and the operational program can be configured so that the feature module can only unlock predetermined functional irrigation features on a predetermined controller and no other controllers. This prevents customers from undercutting the sales of controllers with enhanced features by loaning this feature module to other customers and unlocking the desired features. The feature module can be configured so that the irrigation controller will only execute specified functions so long as that feature module is plugged into the control panel. The feature module can simultaneously unlock certain functional irrigation features stored in the landscape controller and add additional functional irrigation features not found in the firmware originally present in the program memory of the landscape controller. The landscape controller of the present invention can be partially or entirely re-programmed through the feature module years after installation to incorporate many new utilities not previously available on the controller.
The features of the inventive systems and methods will now be described with reference to the drawings summarized above.
Referring to
Referring to
Referring to
The back panel 12 houses a second printed circuit board 60 that functions as a so-called “back plane.” The printed circuit board 60 mechanically supports and/or electrically interconnects the second communications link 50, power supply 36 and station control circuitry in the form of driver/switch circuits 62, 64 and 66. The processor 44 executes an operation program, including a watering program that is stored in PM 56 in order to carry out the desired watering schedules and any other functions such as turning landscape lighting ON and OFF. By activating the driver/switch circuits 62, 64 and 66 via communications link 50. The driver/switch circuits 62, 64 and 66 are conventional and may include transistor drivers responsive to ON and OFF commands from the processor 44 that turn triacs ON and OFF to switch low voltage AC power from power supply 36. The driver/switch circuits 62, 64 and 66 control six irrigation valves 68 and 70, and three landscape lights 72 that are connectable to dedicated field lines 74, 76 and 78 and a common return line 80 via screw terminals 34 (
Referring still to
The operational program stored in the PM 56 includes a watering program having all of the features and algorithms necessary to satisfy multiple irrigation controller market segments. The watering program includes scheduling code for sports field application, as well as nursery application. Additional code allows the watering program to make adjustments based on evapotranspiration (ET) data supplied to the processor 44 from a service or from environmental sensors. Different feature modules 22 may be manufactured for installation in the face pack 14 that each enable or activate for usage a predetermined sub-set of a comprehensive set of features capable of being executed by the processor 44. The different feature modules can enable, through unique keys stored on an integrated circuit, different feature sets for different irrigation controller market segments. The most expensive feature module may enable the processor 44 to execute every available feature. Thus, the feature module 22 that is inserted into the face pack 14 enables a predetermined specific set of instructions that implement a comprehensive set of features capable of being executed by the processor 44. In this way, the user only pays for the features needed on his or her particular irrigation site.
Our invention allows a user to buy the base landscape controller 10 and the desired feature set that is enabled by a specific one of several interchangeable feature modules 22. The user can only access a predetermined sub-set of the comprehensive set of features capable of being executed by the processor 44 that are included in the extensive operational program stored in the PM 56 of the face pack. The manufacturer's software engineers only need to write one comprehensive watering program, instead of different watering programs for irrigation controllers targeted at different market segments. Field upgrades can be accomplished by simply purchasing and installing a new feature module 22. Since the feature module is plugged into the face pack 14, all of the authorized functionality of the landscape controller is fully available to the user when the face pack is unplugged from the frame 32 so that the user can walk around the irrigation site, change the water schedule, and make other adjustments.
U.S. Pat. No. 7,257,465 of Perez et al. discloses a modular irrigation controller with a removable face pack. The controller has a number of bays or receptacles in its rear panel into which a plurality of station modules may be individually plugged to increase the number of zones that can be watered. These station modules are not plugged into the removable face pack but are instead plugged into the receptacles so as to allow the station modules to electrically connect to the back plane in the rear panel. So-called “smart” modules can be plugged into these receptacles, such as an ET module or a decoder module, in order to provide additional functionality to the base irrigation controller. However, this irrigation controller architecture suffers from a number of drawbacks. First, each time a smart module is plugged into one of the receptacles in the rear panel, the number of zones that can potentially be controlled is correspondingly reduced since that receptacle is no longer available to receive a station module. Secondly, since the smart modules are not plugged into the face pack, the processor in the face pack may not be able to be programmed using all of the additional functionality provided by the smart modules when the face pack is unplugged from the rear housing. Thirdly, the smart modules disclosed in U.S. Pat. No. 7,257,465 of Perez et al. have no capability for unlocking or enabling otherwise non-available features programmed into the main memory of the base controller. The landscape controller of the present invention overcomes each of these shortcomings.
The primary purpose of an alternate feature module 22 can be the provision of additional memory, or data via that memory, to the face pack 14. For instance, once the processor 44 detects that additional memory has been plugged into the face pack 14, it may enable a memory intensive data logging function not previously possible with the DM 58 in the face pack. Alternatively, the processor 44 may allow more complex programming when there is additional memory available to store more start times, run times, etc. Yet another use of the additional memory is to provide the processor 44 with data. For instance, a memory chip in the feature module 22 may be pre-loaded with historic environmental conditions to allow automatic watering schedule changes. This historic data may be historic average daily ET data for a particular zip code, for example. See U.S. patent application Ser. No. 12/176,936 filed Jul. 21, 2008, the entire disclosure of which is hereby incorporated by reference. A new version of application code may later be developed for the face pack 14. Microcontrollers are currently available for use as the processor 44 that have the ability to write to their own memory (re-flashable). Such a microcontroller can read the information out of the memory in the feature module 22, and re-program itself.
The feature module 22 can contain a variety of different types of memory that can be accessed by the processor 44 in a number of different ways. Serial memory can be accessed with only a few lines. In most cases, these consist of only a clock line, and a data line. There may also be two data lines—one for each direction of data flow. Examples of this type of memory are the 93XX and 24XX industry standards. For instance, the 24LC512 manufactured by Microchip Technology, is a serial, 512 Kbit non-volatile memory chip. The 93LC66, also from Microchip Technology, is a serial, 4 Kbit non-volatile memory chip. An example of how a 24LC512 is configured to work with the host processor (the microcontroller in the landscape controller), is illustrated in
Parallel memory has the advantage that it can be accessed much faster than serial memory. This is because once the address has been set up (all at once), and the chip is enabled, all the data bits appear simultaneously, usually within a few tens or hundreds of nanoseconds. There are usually no clocking operations involved. One example of parallel memory is the CY62128 from Cypress Semiconductor, which is a 128K Byte RAM. An example of how this device can be connected to the processor 44 is illustrated in
The feature module can be configured as a plug-in memory module that has its own microcontroller on-board. The purpose of this microcontroller is to adapt a memory chip (either serial or parallel) to an industry standard protocol. One example of this is a USB flash or thumb drive. These devices typically have a parallel flash memory chip, such as the Toshiba TC58DVG02A1 connected to a USB-enabled microcontroller such as the Freescale Semiconductor 9S12UF32. The microcontroller manages the implementation of instructions (read/write) over the USB interface, and communicates with the memory chip via its Smart Media Interface. With slightly different firmware, the microcontroller can be adapted to interface to a number of different memory devices, yet the USB interface is standardized.
As already explained, a feature module can be inserted to enable more or less functions in the face pack 14. The landscape controller 10 may be sold in a version in which all features already exist in the face pack. In this version, the operational program stored in the PM 56 has all the features that the end user could ever utilize already coded in firmware. When the unit is shipped, some, but not all of these features are active, perhaps for logistic reasons (they may confuse less savvy end users), or for marketing reasons (the end user may be willing to pay more for some features). In either case, the purpose of the feature module 22 is to enable some or all of the features already contained in the face pack code, or to de-feature it.
In another version of the landscape controller 10, all of the features are not already programmed into the PM 56 of the face pack 14. In this version of the landscape controller 10, the face pack does not have a particular feature or features that could be added later with a feature module. In order to accomplish this, new operational code must be programmed into the PM 56 of the face pack 14, or otherwise made available to the processor 44. As discussed above, a memory module could hold code that is re-flashed into the face pack 14. However, such a module may be taken to multiple landscape controllers (even if it was only paid for once), and used to re-flash all of them. This limitation can be overcome in several ways. Part of the new application code could be a routine to periodically go out and check for the presence of the memory module, even though its “services” are no longer needed. Another approach is for the microcontroller to actually execute the code out of the module itself.
Another embodiment of the feature module takes the form of a standard secure digital memory card, also known as an SD card that interfaces with the processor in the face pack of the irrigation controller and allows that processor to read and write data files to the SD card. Data files can be stored on the SD card in a number of different forms, providing the irrigation controller with many new features, some of which are briefly described hereafter.
Referring to
Referring to
The standard SD card 118 could be in the form of other solid state memory devices commercially available in other industry standard form factors such as the mini SD card and the micro SD card. The standard SD card 118 could also be in the form of other solid-state memory devices with different file systems and data transfer rates such as the SD High Capacity (SDHC) card, the SD Extended Capacity (SDXC) card, and the Ultra High Speed (UHS-I and UHS-II) cards. As used in the claims set forth hereafter, the term “SD card” includes all forms described in this specification as well as other forms of SD cards not specifically described herein and those developed after the filing date of this application.
Referring to
Referring to
While several embodiments of a landscape controller with a control panel insertable feature module have been described in detail, persons skilled in the art will appreciate that the present invention can be modified in arrangement and detail. For example, the feature module 84 (
RFID is an acronym for Radio Frequency Identification. In general, an RFID system comprises at least two devices, such as a two-way radio frequency transmitter-receiver or interrogator, and a transponder. The interrogator is sometimes referred to as the reader, and the transponder is sometimes referred to as the tag. In an embodiment, the reader sends a signal and then detects a response from a tag in proximity to the reader. In general, the nature of the response is a short digital message identifying the tag. In some embodiments, moderate amounts of data can be exchanged between the reader and the tag. In further embodiments, the exchange of data between the reader and the tag can be be-directional.
Tags may be read-only and have a factory-assigned serial number that is used as a key into a database, or may be read/write, where object-specific data can be written into the tag by the system user. Field programmable tags may be write-once, read-multiple; “blank” tags may be written with an electronic product code by the user.
RFID tags comprise at least an integrated circuit for storing and processing information, modulating and demodulating a radio-frequency (RF) signal, collecting DC power from the incident reader signal in some embodiments, and performing other specialized functions; and an antenna for receiving and transmitting the RF signal. The tag information is stored in a non-volatile memory. The RFID tag includes either fixed or programmable logic for processing the transmission and sensor data, respectively.
An RFID reader transmits an encoded radio signal to interrogate the tag. The RFID tag receives the message and then responds with its identification and in some embodiments, other information. Since RFID tags have individual serial numbers, the RFID system, in an embodiment, can discriminate among several tags that may be within the range of the RFID reader and read them simultaneously.
There are a plurality frequencies that can be used by RFID systems to send and receive signals. For example, some common frequencies are shown in Table 1. In other embodiments, other frequencies can be used by the RFID system to send and receive signals.
The operating distances in the table comprise approximations based on the nature of the tags, such as active or passive, the size of the antenna associated with the tag and/or the reader, and other factors. As indicated in Table 1, the range or operating distance between the tag and the reader generally increases with frequency. This is not typically the case for radio frequency (RF) links. However, the nature RFID tags is that they are relatively small and inexpensive. At lower frequencies, in some embodiments, it may be difficult to make an efficient, inexpensive antenna that is also small.
RFID tags, for example, can be either passive, active or battery-assisted passive. A battery-assisted passive (BAP) has a small battery on board and is activated when in the presence of an RFID reader.
Passive RFID tags contain no power source. Instead, the tag derives power from the RF energy transmitted by the reader. Readers that operate with passive tags typically generate strong RF signals to power the tags. For example, to operate a passive tag in one embodiment, it is illuminated with a power level roughly a thousand times stronger than for signal transmission. Additionally, because the tags can only harvest limited amounts of energy from the reader's RF signal, the range of these systems can be limited. In an embodiment, passive RFID tags only operate while in the presence of the reader.
Some passive RFID tags have no electronics, but comprise patterns of metallic material printed on a base material such as paper. The geometry of this pattern is configured such that it has certain resonance frequencies. When interrogating this type of tag, the reader will generate a signal rich in many of the possible frequencies of resonance in the tag, such as a pulse signal, a chirp signal, or the like. The reader then listens for the minute response which will occur only at the resonance frequencies dictated by the tag's pattern. The encoding of the data in the tag is determined by which set of frequencies are returned.
Another method used to communicate with tags that have no electronics is time domain reflectometry. In time domain reflectometry, the reader transmits a pulse of energy, and based on the pattern in the tag, a series of reflections are returned. The data is encoded by the timing of the reflections.
An active RFID tag has an on-board power source, such as a battery, and has the ability to initiate communications. Active RFID tags may require very low power levels from the reader since they do not need to harvest energy, and can typically operate over a larger range than passive tags.
Active RFID tags can also comprise electronic circuits. The electronic circuits may comprise one or more microcontrollers, memory, RF circuits, logic circuits, and the like. Because active RFID tags have a power source, they use the electronic circuits to perform some operations while not being interrogated. These may include logging sensor data, reporting sensor data, broadcasting telemetry data, and the like.
In an embodiment, the active RFID tag comprises memory which can be written to and read by the reader. In another embodiment, the active RFID tag comprises a microcontroller allowing the tag to write to the memory itself, and interface with other circuitry that can be operatively connected to the tag. In an embodiment, the tag can respond with a signal having a different frequency than the frequency of the signal used to interrogate the tag.
In an embodiment, the module 2520 comprises a feature module. In an embodiment, the controller 2510 further comprises the module 2520. In another embodiment, the module 2520 is removably inserted into the face pack of the controller 2510. In a further embodiment, the module 2520 is separate from the controller 2510, or in other words, is not located within the controller 2510, but provides functionality when it is located in proximity to the RFID reader 2540.
The RFID tag 2530 and the RFID reader 2540 communicate via RF signals which are transmitted from or received by the antenna 2550. In an embodiment, the RF communications between the RFID tag 2530 and the RFID reader 2540 is bi-directional. RFID tags 2530 are commercially available. For example, the RFID tag 2530 could be a RI-I16-114A-01 available from Texas Instruments, or the like.
The controller 2510 further comprises a processor or microcontroller 2544, which is operationally connected to the RFID reader 2540 via a Serial Peripheral Interface (SPI) connection. In other embodiments, other interfaces, such as a parallel interface, a serial interface, and the like can be used to provide communications between the microcontroller 2544 and the RFID reader 2540. The microcontroller 2544 is, for example, a PIC18F86K90 available from Microchip Technology, or the like. In another embodiment, the RFID reader 2540 is located in the face pack of the controller 2510, which is typically where the microcontroller 2544 is also located.
The SPI communication protocol designates that one device is a master and the other device is a slave for communication purposes. The master supplies the clock signal for the SPI connection, and therefore controls the timing. The SPI connection comprises at least three signals. The first is the aforementioned clock signal. The second is the serial data from the slave device to the master device (MISO or Master In Slave Out). The third is the serial data from the master device to the slave device (MOSI or Master Out Slave In).
In an embodiment, the microcontroller 2544 communicates with the RFID reader 2540 to periodically search for an RFID tag 2530 within its range. Depending on the type of RFID tag found and the data returned, features associated with the feature module 2520 can be enabled. Examples of features are Feature Unlocking, User Privileges, New Feature Enablement, Module Authentication, Module Inventory, and the like.
In an embodiment, the code or firmware for the feature already exists in the controller 2510 and is “unlocked” by the RFID Tag 2530 which is installed in the controller 2510. The RFID tag 2530 functions as a key and the controller 2510 periodically checks to see that the key has not been removed. In an embodiment, when the RFID tag 2530 is removed from the controller 2510, the feature no longer operates.
In an embodiment, certain users are issued RFID tags 2530 that act as a key to unlock certain privileges in the controller 2510 when the RFID tag 2530 is in the proximity of the controller 2510. For example, the RFID tag 2530 could be part of a key chain issued to the user. A maintenance contractor, for instance, may not be issued an RFID tag 2530, and therefore he can only start/stop manual irrigation, whereas a supervisor does have the RFID tag 2530 and can make schedule and setup changes to the controller 2510.
In an embodiment, the RFID Tag 2530 comprises onboard memory, which can be read by the controller 2510 via the RFID reader 2540. This memory may comprise code patches or new code, which provides new or additional functionality in the controller 2510.
A challenge associated with modular products, such as feature modules 2520, is that third party suppliers often produce “compatible” replacement modules using substandard designs and parts, and sell them for less. An RFID tag 2530 embedded into the feature module 2520 could be used to authenticate the feature module 2520. In an embodiment, the controller 2510 would not recognize unauthenticated feature modules.
In an embodiment, the controller 2510 via the RFID reader 2540 queries the modules 2520. Based on receiving a response, the controller 2510 determines the quantity of installed modules 2520. Based on the response returned from the modules 2520 via the RFID tag 2530, the controller 2510 determines the types of installed modules 2520.
In another embodiment, the RFID reader 2540 sends data to the RFID tag 2530 to be stored in the RFID tag 2530. For example, the controller 2510 could maintain a Health/History Log of the installed modules 2520.
In an embodiment, the RFID tag 2530 comprising read/write memory could be installed inside the module 2520 where the read/write memory comprises information about the use of the module 2520. Because the RFID tag 2530 is not electrically connected to the controller 2510 or other circuitry in the module 2520, the RFID tag 2530 is relatively immune to the effects of lightning and surge that can damage controllers 2510 and modules 2520. Therefore, the memory in the RFID tag 2530 can be written with information, such as the date of manufacture, whether the module 2520 passed factory acceptance testing, the number of times the module 2520 was actuated, the date and conditions when the controller 2510 could no longer communicate with the module 2520 in the event of a failure, and the like. Even if the primary electronic circuitry in the module 2520 were damaged, the RFID tag 2530 could still be read and provide clues to what caused the failure and how to design better products in the future.
In the illustrated embodiment of
The crystal oscillator Y1 provides a time-base for the RF signals used by the RFID controller system 2500. In an embodiment, the crystal oscillator Y1 has an approximately 13.56 MHz frequency and is used as the time-base for the approximately 13.56 MHz RF signals. Capacitors C1-C6, C14-C15 are decoupling and bypass capacitors, which assure that the TRF7963A, has a clean power supply. Capacitors C7-C13 and inductors L1, L2 are matching components configured as a matching circuit to match the impedance of the antenna ANT1 to the input and output impedances of the RFID reader IC U1. In an embodiment, the antenna ANT1 comprises a 50-ohm antenna. Resistor R2, inductor L3, and capacitor C17 comprise a parallel tuned circuit to decrease spurious outputs in transmit mode and filters spurious inputs in receive mode.
As described herein, there are numerous types of RFID systems. It is possible that newer, higher frequency systems will be developed. The embodiments presented herein comprise examples of how an RFID system could be incorporated with feature modules 22, 88, 92, 96, 102, 106, 112, 2540 and landscape controllers 10, 2510. Further, Feature Unlocking, User Privileges, New Feature Enablement, Module Authentication, Module Inventory, Health/History Log are just some of the benefits that can be achieved by incorporating RFID systems into the feature modules 22, 88, 92, 96, 102, 106, 112, 2540 and landscape controllers 10, 2540. Other embodiments and other benefits can be achieved without departing from the spirit of the disclosure.
Depending on the embodiment, certain acts, events, or functions of any of the algorithms described herein can be performed in a different sequence, can be added, merged, or left out (e.g., not all described acts or events are necessary for the practice of the algorithm). Moreover, in certain embodiments, acts or events can be performed concurrently, e.g., through multi-threaded processing, interrupt processing, or multiple processors or processor cores or on other parallel architectures, rather than sequentially.
The various illustrative logical blocks, modules, and algorithm steps described in connection with the embodiments disclosed herein can be implemented as electronic hardware, computer software, or combinations of both. To clearly illustrate this interchangeability of hardware and software, various illustrative components, blocks, modules, and steps have been described above generally in terms of their functionality. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the overall system. The described functionality can be implemented in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the disclosure.
The various illustrative logical blocks and modules described in connection with the embodiments disclosed herein can be implemented or performed by a machine, such as a general purpose processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general-purpose processor can be a microprocessor, but in the alternative, the processor can be a controller, microcontroller, or state machine, combinations of the same, or the like. A processor can also be implemented as a combination of computing devices, e.g., a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration.
The steps of a method, process, or algorithm described in connection with the embodiments disclosed herein can be embodied directly in hardware, in a software module executed by a processor, or in a combination of the two. A software module can reside in RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, hard disk, a removable disk, a CD-ROM, or any other form of computer-readable storage medium known in the art. An exemplary storage medium can be coupled to the processor such that the processor can read information from, and write information to, the storage medium. In the alternative, the storage medium can be integral to the processor. The processor and the storage medium can reside in an ASIC.
Conditional language used herein, such as, among others, “can,” “might,” “may,” “e.g.,” and the like, unless specifically stated otherwise, or otherwise understood within the context as used, is generally intended to convey that certain embodiments include, while other embodiments do not include, certain features, elements, and/or states. Thus, such conditional language is not generally intended to imply that features, elements, and/or states are in any way required for one or more embodiments or that one or more embodiments necessarily include logic for deciding whether these features, elements, and/or states are included or are to be performed in any particular embodiment. The terms “comprising,” “including,” “having,” and the like are synonymous and are used inclusively, in an open-ended fashion, and do not exclude additional elements, features, acts, operations, and so forth. Also, the term “or” is used in its inclusive sense (and not in its exclusive sense) so that when used, for example, to connect a list of elements, the term “or” means one, some, or all of the elements in the list.
While the above detailed description has shown, described, and pointed out novel features as applied to various embodiments, it will be understood that various omissions, substitutions, and changes in the form and details of the devices or algorithms illustrated can be made without departing from the spirit of the disclosure. As will be recognized, certain embodiments of the inventions described herein can be embodied within a form that does not provide all of the features and benefits set forth herein, as some features can be used or practiced separately from others. The scope of certain inventions disclosed herein is indicated by the appended claims rather than by the foregoing description. All changes which come within the meaning and range of equivalency of the claims are to be embraced within their scope.
Number | Date | Country | |
---|---|---|---|
Parent | 12243897 | Oct 2008 | US |
Child | 13091645 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 13708577 | Dec 2012 | US |
Child | 14702466 | US | |
Parent | 13091645 | Apr 2011 | US |
Child | 13708577 | US |