# Patent

## Title
Electronic postage meter having separate funds charge registers and

## Abstract

The present patent application is a continuation-in-part of patent application U.S. Ser. No. 255,156 filed Oct. 4, 1988 for QUERY-RESPONSE USER PROGRAMMING OF COMPLEX SEQUENCES, now U.S. Pat. No. 5,124,942, which is a continuation-in-part of patent application U.S. Ser. No. 250,841 filed Sept. 28, 1988 for a FLEXIBLY PROGRAMMABLE IRRIGATION SYSTEM CONTROLLER now abandoned.

## Background
1.0 Field of the Invention

The present invention concerns electronic devices having a man-machine interface for the display of information and/or status and for the receipt of information and/or control. The present invention more particularly concerns man-machine interfaces where cost and/or physical size constraints limit the display size to a few words or lines, and where, for the same constraints, a full user keyboard is impractical.

2.0

The advent and widespread low-cost availability of microprocessors and other powerful digital logic building blocks has given rise to an astonishing array of products exhibiting machine "intelligence". This machine "intelligence" often takes the form of increased flexibility and responsiveness to particular user dictates. The user must make his/her dictates known to the machine through a man-machine interface. The man-machine interface desirably permits detailed user control of the machine.

If a complex machine is to be flexibly controlled by its user at its user interface then an extensive sequence of commands and/or data must typically be entered by the user into the machine. This information entry must typically be in accordance with rigorous procedures. The required exactitude is difficult to achieve, especially to the extent that the required entries are extensive, complex, or infrequently performed.

The goal of man-machine interface design is to permit effective and efficient communication between man and machine, considering the costs to both.

At one end of the spectrum of common interfaces between men and "intelligent" (meaning variably flexibly controllable) machines is the typical interface to a complex, multi-function, digital watch. This interface is characterized by having a very narrow information transfer bandwidth. The user must make large amounts of data and control information known to the watch through typically but a few pushbutton switches. A problem exists with this interface in that large numbers of people desiring to exercise the full functionality of a complex, multi-function, digital watch cannot effectively do so, or are deterred from doing so.

At the other end of the spectrum of common manmachine interfaces is the personal computer. Information is typically entered into the computer by a keyboard or tablet (mouse). The computer typically displays information, questions, and help messages upon a video monitor. The informational bandwidth of this interface is much wider than the informational bandwidth of the user interface to a digital watch. This wider informational bandwidth is required in order to support the relatively more complex tasks that are commanded and parameterized across the interface.

A notable characteristic of the man-machine interfaces exhibiting a relatively wider informational bandwidth, such as those of personal computers, is that the man can usually elicit prompts, questions, and/or help messages from the machine. This capability of the machine to guide the human in performing necessary procedures to enter information is designed to reduce the burden on the human, and to facilitate necessary communication.

In the middle of the spectrum of common manmachine interfaces exist a variety of relatively rudimentary interfaces which, although elementary, must support the human control and parameterization of machines of considerable functional complexity. Interfaces, and machines, in this middle range include common household appliances like microwave ovens and Video Cassette Recorders (VCR's).

A common strategy for implementing man-machine interfaces in this middle range is to use a large number of switches each of which is assigned to a particular datum, or function. Typically, a small display is controlled by the machine. A proliferation of dedicated switches costs money, and occupies considerable room. Nonetheless, when an appropriate multi-function display area shows at various times either prompts or status, and when additional display area is devoted to printed instructions and catalogs, most users manage to use this type of man-machine interface to good effect.

Sometimes, however, the control panels become crowded with switches. The functions enabled become increasingly arcane. The cross-compatibility between the user interfaces of different products becomes nonexistent, making a user unable to transfer his knowledge and experience from one product to another.

Another problem occurs with man-machine interfaces if the number of switches and/or the size of the display is limited (i.e., the information bandwidth is constricted), or if the complexity of the required control is high. This problem is exemplified by the common interface to a VCR. A small display presents the VCR status and parameterization. Because the VCR can be set to initiate and to conclude actions, such as recording of television, at many different times, a great number of similarly-appearing time datums are variously multiplexed into the small display. The user tends to lose track of what times he/she has and has not specified, and also of his/her progress in the intricate stepwise procedures for selecting and setting a number of different timed occurrences. The programming is consequently often erroneous. The user's failure to have programmed the VCR as he/she desired or expected typically goes unrecognized until improper results are obtained. At this time recovery is often difficult or impossible.

The present invention contemplates the user programming of complex machine control and/or data sequences by manually causing the machine sequence through a hierarchy of questions to collect from the user one response only: "OK", meaning the affirmative.

The man-machine interface in accordance with the present invention typically exhibits a very narrow informational bandwidth relative to the informational bandwidths of traditional man-machine interfaces that attempt to communicate anywheres near the extent, and sophistication, of the control and/or data that typically transpires on the interface of the invention. For example, the informational output from the machine to the user is typically in two lines of sixteen alphanumeric characters each. For example, the informational input from the user to the machine is typically by four simple switches, only one of which is operated at any one time.

Despite the simplicity of the man-machine interface, and despite its narrow informational bandwidth, it is user friendly in permitting man-machine interfacing for the control and parameterization of complex tasks typically including tens or hundreds of control options and hundreds or thousands of datums. For example, the man-machine interface in accordance with the invention permits all necessary control and parameterization of a modern and highly sophisticated programmable irrigation controller. Because of the simplicity of the interface, it is substantially intuitive to a human user. Indeed, those few skills that are needed to operate the interface are actually preferably taught by the interface itself to the user.

In order to realize its high communications effectiveness and its user friendliness while operating at a narrow informational bandwidth, the man-machine interface in accordance with the present invention employs a number of interrelated strategies. Only four user responses--"HELP", ".uparw.", ".dwnarw." and "OK" (typically in that left-to-right order of presentation)--are recognized by the machine. Each user response is typically registered at a particular associated switch, normally of the pushbutton type. The up arrow ".uparw." and the down arrow ".dwnarw." switches direct the step-wise sequencing of questions, one question per switch actuation. Holding the ".uparw." or ".dwnarw." depressed will cause the displayed questions to commence to scroll, typically presenting a new question each 2-5 seconds. The "HELP" switch causes the display of a contextsensitive help message. The "OK" switch indicates to the machine that the user adopts, or affirms, the control or data object of the presently-displayed question.

The questions, or messages, presented by the machine at its user interface include absolutely all the control, and absolutely all the datums, which are, at various times, capable of being received by the machine from its human user. The questions--which represent all the control and data entry alternatives of which the machine is capable and are thus typically quite voluminous--are organized in a hierarchy. The hierarchy presents a plurality of questions, which may be directed to control or to data entry, upon each of a plurality of levels.

The step-wise sequential presentation of alternatives ensures that the user is exposed, in the form of hierarchical questions, to all acceptable directives and/or datums, one hierarchical level at a time, which may suitably be entered into the machine. This process is most clearly visible, and is substantially intuitive in nature, when the machine is asking questions about control. The user simply adopts one alternative on each successive hierarchical level dealing with control by responding "OK" to one question on that level. The machine then steps, in a completely logical manner, to another series of questions upon the next control level in the hierarchy.

Responsive to several control inputs (in the form of questions adopted by the "OK" response), the machine typically next presents questions directed to that data that is pertinent to the particular control that has been input to the machine. When the data inputs are finished the machine will typically revert, in accordance with the user response to a question posed by the machine on its user interface, back to a control level in the hierarchy. At the conclusion of the collective user responses the machine may routinely have been programmed with control and/or data that is, in the aggregate, complex.

In accordance with the invention the hierarchy of questions asked by the machine is typically a hierarchical tree exhibiting several hierarchical levels between a root level and a leaf level. An "OK" response to a question on one hierarchical level causes a branching to a related series of questions upon the next hierarchical level. Progress within the hierarchical tree from root level to leaf level thus requires asking only such questions at each hierarchical level as are appropriate to previous branchings within the hierarchical tree. This is obviously efficient because only precisely pertinent questions are asked at each level of the hierarchical tree.

In accordance with the invention the hierarchical tree of machine-posed questions is typically not a binary tree. Instead, several questions of equal stature are preferably asked at each level, or rank, of the hierarchical tree that normally exhibits several hierarchical levels between a root level and a leaf level. The number of related questions at each level is normally not so many that the user is likely to forget the first-asked questions before the last questions are asked, and is typically approximately three to six. When the user responds "OK" to any question, meaning that the question's premise is adopted by the user, then all questioning on that hierarchical level ends and the machine progresses to a new series of questions upon a next hierarchical level. The questioning so proceeds in a hierarchy from root to branches to twig to leaf levels, with one "OK" response being accepted to one of the typically several questions at each level of the hierarchy.

When a question on the leaf hierarchical level is, ultimately, affirmatively answered then the machine will resume questioning at a higher hierarchical level, including commonly at the root level.

Despite the fact that all questions and their ordered hierarchical presentations are always as clear and logically ordered as is possible, it is always possible that a user cannot understand what a particular question is asking. Therefore the present invention contemplates an optional "HELP" switch. User actuation of the "HELP" switch in response to the presentation of any question causes the display of an expanded explanation of that question. After viewing one or more help messages by actuation of the ".uparw." switch the user may return to the main line of questioning by actuating the ".uparw." switch.

Actuation of the "HELP" switch at some or all root mode questions may typically result in help messages explaining the operation of the interface of the present invention. Mainly, the messages will explain that the user should attempt to answer the questions with the "OK" switch.

Because of the simplicity of the preferred embodiment of the man-machine interface in accordance with the present invention that uses only four different user inputs one at a time, such limited inputs are readily implemented in voice recognition technology.

Further because of the simplicity of the preferred embodiment interface in accordance with the present invention, use of the interface can be instructed by a "game" that runs upon the interface. The user is offered the option of entering the "game" upon entry into the machine through its interface. The intent of the game is to develop user skills in exercising, and communicating across, the interface. To do so a number, typically ten, questions are asked. Each question requires a user response of a type that is typical on the interface. A total novice must generally use the "HELP" switch in order to progress. The user's correct responses are required to progress, and the user/player's total responses are timed. A score is displayed that indicates the user's command of the interface. The combination of the user's intuitive response to the question-asking interface, and those insights that the user gains from playing the game into the interface operation for tasks such a entering data, reliably (i) educate and (ii) certify a user that is exceedingly unlikely to thereafter experience confusion with any aspect of the interface's operation.

The major attributes of a man-machine interface in accordance with the invention are susceptible of various different combinations. The man-machine interface in accordance with the present invention exhibits at least a display within which a multiplicity of control and datum options, preferably in the form of questions, may be successively individually displayed. The interface also has an "OK" switch or equivalent by which a man may make his affirmation or adoption of a currently-displayed datum known to the machine. The interface also has at least one switch, either an ".uparw." (up arrow) or ".dwnarw." (down arrow) switch, by which the machine is directed to step-wise sequence the display of questions.

In one of its aspects the man-machine interface in accordance with the invention displays a heirarchy of messages, one message at a time step-wise sequentially among a plurality of messages at each of a plurality of levels of the hierarchy. The interface further includes a first-direction sequencer, or ".uparw." switch, that is manually repetitively actuatable for causing the display means to step-wise sequence through the plurality of messages at one level of the hierarchy in a first direction in response to each actuation. Finally, the interface includes an "OK" switch that is manually actuatable, at a time after a desired one of the plurality of messages at the one level of the hierarchy has been displayed for causing (i) an adoption and use of the currently displayed message by the machine and (ii) the display to display messages from another hierarchical level having a selected relationship to said currently displayed message, thereby branching within the hierarchical tree of messages without ever leaving the hierarchical tree. Notably, all man-machine communication for purposes of manual control and data input to the machine has been accomplished solely by manual responses to various selected ones of the multiplicity of messages, and these responses have been made by the selective actuations of two only switches: a ".uparw." switch and an "OK" switch.

The interface may further include a manually actuatable second-direction sequencer, or ".dwnarw." switch, for causing the display to step-wise display each of the plurality of messages at one level of the hierarchy in a second direction in response to each actuation. Finally, the interface may further include a manually actuatable "HELP" switch for causing the display to display a new message associated with a currently displayed message.

In still another of its aspects the interface in accordance with the present invention can be used in a machine that interfaces to a man for (i) control and, at a separate time or times, (ii) data entry. The machine has a control state having a hierarchy of control levels, where at each control level the machine is capable of accepting selected commands associated with the control level in order to effect control of the machine. The machine also has a data entry state having a hierarchy of data entry levels. At each data entry level the machine is capable of accepting selected ones of a plurality of datums associated with the data entry level in order to effect entry of data into the machine. The multi-leveled hierarchies of the control and data entry states are permitted to be intermixed and related. However, the machine can be, at any one time, in only one state and at only one level of such state.

The improved man/machine interface to such a multi-stated multi-level hierarchical machine is, in accordance with the present invention, directed to (i) controlling and (ii) entering data into the machine. It includes a display for displaying (i) in the control state of the machine, and at some one control level of this control state, some one of the commands associated with the control level, and (ii) in the data entry state of the machine, and at some one data entry level of this data entry state, some one of the datums associated with the data entry level, one command or one datum at a time. The improved interface also includes a manually actuable ".uparw." switch for causing the display means to advance (i) in the control state of the machine and at some one control level of this control state, the currently displayed command stepwise in a first direction in an endless loop of the commands associated with this one control level and, (ii) in the data entry state of the machine and at some one data entry level of this data entry state, the currently displayed datum stepwise in a first direction in an endless loop of the datums associated with this one data entry level. Finally, the improved interface includes a manual "OK" switch for causing the machine to (i) accept and adopt, in the control state of the machine and at some one control level of this control state, the currently displayed command and, in the data entry state of the machine and at some one data entry level of this data entry state, the currently displayed datum, and also to (ii) cause the display to advance to a next state and/or a next level that is in a predetermined relationship to the currently displayed command or datum. Accordingly, the machine accepts both (i) commands for purposes of control and also (ii) datums for purposes of data entry resultantly from manual actuations, at separate times, of the "OK" switch.

The man-machine interfaces and man-machine interfacing methods in accordance with the invention are perceived to be especially efficacious for control and parameterization of machines that require a lengthy and logical, complex, control sequences. A machine requiring this type of sequential control has previously typically required an instruction manual, and is opposite from machines requiring pure data entry such as, typically, telephones.

These and other aspects and attributes of the present invention will become increasingly clear upon reference to the following drawings and accompanying specification wherein:

FIG. 1 is the block diagram showing an irrigation controller that employs a preferred embodiment of the man-machine interface in accordance with the present invention;

FIG. 2 is a block diagram of an irrigation system employing the irrigation controller, previously seen in FIG. 1, that employs the man-machine interface in accordance with the present invention;

FIGS. 3a, 3b, 3c, 3d, 3e, 3f, 3g, and 3h, are an electrical schematic diagram of a preferred embodiment of the irrigation controller that employs the preferred embodiment of a man-machine interface in accordance with the present invention;

FIG. 4 is a block diagram of a first, U1, Application Specific Integrated Circuit (ASIC) used in the preferred embodiment of an irrigation controller that employs the preferred embodiment of a man-machine interface in accordance with the present invention;

FIG. 5a is a simplified electrical schematic diagram of the sampling capacitor array and switches used in the ASIC U1 previously diagrammed in FIG. 4;

FIG. 5b is a simplified electrical schematic diagram of a sampling comparator used in the ASIC U1 previously diagrammed in FIG. 4;

FIG. 5c is a simplified electrical schematic diagram of a step-up DC-to-DC converter used in the switching regulator of the ASIC U1 previously diagrammed in FIG. 4;

FIGS. 6a, 6b, 6c, and 6d are a block diagram of a second, U2, Application Specific Integrated Circuit (ASIC) used in the preferred embodiment of an irrigation controller that employs the preferred embodiment of a man-machine interface in accordance with the present invention.

FIG. 7 is a chart showing the mode dependent functions of the keys, or switches, of the preferred embodiment of a man-machine interface in accordance with the invention.

FIG. 8, consisting of FIGS. 8a, 8b, 8c, 8d, 8e, 8f, 8g, 8h, and FIG. 8i, is a diagram of the control and data entry activity transpiring on the preferred embodiment of a man-machine interface in accordance with the present invention as employed in an irrigation controller for purposes of irrigation control.

1.0 The Basic Operation of an Interface in Accordance with the Present Invention

The preferred embodiment of a man-machine interface in accordance with the present invention is used in an irrigation controller. The complex function of this irrigation controller, as hereinafter explained, serves to demonstrate the power of the interface in accordance with the present invention for user programming of sequences that are complex. However, it is not necessary to consider the complexities of irrigation control and irrigation controllers in order to understand the basic operation and principles of the present invention.

The man-machine interface in accordance with the present invention greatly simplifies operational control of an intelligent machine because (i) the user is constantly prompted by questions, and (ii) all command and data input may be done with just two, and preferably with no more than four keys. Because of the simplicity of this interface, it has many potential applications. Any device which needs to be programmed with information, and which has a small display (no keyboard is required) can potentially use the interface of the present invention. (Equivalently, a device with a large display only a small portion of which is desired to be used for user interfacing can also use the present invention.) The device is typically controlled by a microprocessor. Examples of possible applications include home appliances such as microwave ovens, and entertainment electronics such as Video Cassette Recorders (VCR's).

The key features of the new user interface and how it might be applied to a machine are as follows. All control and data entry and review for the machine is accomplished by actuating two switches only, namely an affirmation/selection or "OK" switch, and a switch or switches for causing the presentation of successive questions, either or both an ".uparw." (up arrow) or a ".dwnarw." (down arrow) switch.

A machine may also beneficially use an additional switch, namely a "HELP" switch. The "HELP" switch elicits context sensitive help messages.

The machine's display cycles under control of the ".uparw." or ".dwnarw." switch continuously between questions on a first, root, hierarchical level. For example, if the machine is an irrigation controller then these first-level questions might typically be: "ENTER SCHEDULE?", "RUN SCHEDULE?", "MANUAL RUN?", "NO WATERING?", "SETUP SYSTEM?", or "VIEW INFO?". If the ".uparw." or ".dwnarw." switch is held depressed at the first or any other hierarchical level, the display will proceed to cycle at a predetermined rate, typically 2.5 second per question. If the ".uparw." or ".dwnarw." switch is released then the cycling of the displayed questions stops.

The display steps under control of the ".uparw." or ".dwnarw." switch until one question is answered by depressing the "OK" switch. The display then commences to step-wise through questions in the appropriate next branch of the hierarchal tree of questions.

The step-wise sequencing through the displayed datums, or questions, is controlled by manual actuation of the ".uparw." or ".dwnarw." switches. Such actuations indicate that the "currently displayed datum is not adopted, advance to next datum".

The machine user will always know all choices possible because he/she may sequence through all questions upon any one hierarchical level in an endless loop. Control and data options will cycle under control of the ".uparw." or ".dwnarw." switch in a continuous loop until the user selects one of the options by activating the "OK" switch. Under certain conditions, such as during the conduct of calculations by the machine, the control options may temporarily be limited so that, for example, only a "CALCULATING" or like message is displayed.

To focus the user's attention on the most important part of any option field, the machine typically blinks the important control or data options on the display along with a question mark for each option as the options are displayed one at a time.

A hierarchal tree for control and parameterization of an irrigation controller might be constructed, at least at initial levels of the hierarchy, substantially as shown on Table 1. The options of the hierarchy are not expressed as questions in order to make the structure of the hierarchal tree more visible. However, it should be understood that all options can be, and are, preferably expressed as questions complete with a question mark (or other identifying indicia).

In accordance with the invention the asked questions may be global or specific. A global question asks whether a user desires to adopt a particular course of machine control. For example, "Do you want to start?", "Do you want to set me?", "Do you want to ask me?", and "Do you want to stop?" would be suitable global questions for the control of a microwave oven. Specific questions ask whether a user adopts a particular datum for input to the machine. For example a display that advances under user control through times of 12:00 midnight?, 1:00 a.m.?, 2:00 a.m.?, 3:00 a.m.?, etc. is asking the user to select an hour which he/she desires to enter into the machine. The field that is currently being changed is blinking. All questions both global and specific are always explicit, and never implicit, because they have an appended question mark or similar distinctive indicia.

Sometimes a question will sequence to another question that is only subtly different in wording, although possibly very different in meaning. For example "USE Run Options?" can sequence to "SKIP Run Options". In this case the "USE" or the "SKIP" may be blinked not to indicate that it is to be entered, but to highlight the crux of the question. Pressing "OK" in response to "SKIP" or to "USE" changes to the other. Thus the item to be changed is the item blinked--whether it be control or data. Furthermore, note that the field to be changed is always capitalized in the alphanumeric contents thereof--again whether or not such field is control or data.

Efficient recovery from inadvertent erroneous responses can always be made. Although an erroneous response to a global question may not be immediately subject to retraction, intermediary levels in the hierarchy of questions occasionally contain escape questions, as appropriate, which, when responded to affirmatively, result in a reversion of the hierarchal questioning to previous levels, and typically to the root level.

In any case, the present invention further contemplates user confirmation of his/her responses. Affirmative responses to specific questions at the leaf level are particularly subject to confirmation. This confirmation is itself in the form of an affirmation question. (If desired, these affirmation questions can be considered to exist at the leaf level, and prior specific questions can be considered to exist at the twig, or branch level.) An affirmation question seeks ratification of the prior responses.

If the prior affirmative responses are disavowed, in whole or in part, then the machine will revert to questioning on a previous hierarchal level. When the hierarchy is deep, and the levels many, the machine will typically revert to questioning at an intermediary branch, twig, or leaf level. From these levels it is always possible to retrench still further, and ultimately back to the root level questions. When the hierarchy is shallow, and the levels few, the disavowal of prior responses that results from an affirmative response to the disaffirmation question typically results in reversion to the root level questioning.

Certain attributes of the hierarchy shown in Table 1 are immediately observable. First, the number of levels in the hierarchy that are entered during any one programming episode varies with the response to certain questions. For example, an affirmative response to the "NO WATERING" question is an end in of itself, and does not normally cause progression further into the hierarchy (forebearing the conduct of confirmation). For other responses, such as the entering of an irrigation schedule more extensive levels of the hierarchy are entered.

Second, confirmation questioning (which is only implicit in Table 1) is performed or not performed as appropriate. An affirmative response to the "START ME?" or "PROGRAM SETUP OK?" questions will typically not result in the conduct of confirmation, and the irrigation controller will respond by simply progressing to another level in the hierarchy.

Next, it may be noted that some final, or leaf level, questions have to do with control, e.g. "SYSTEM SETUP OK?". Meanwhile other leaf level questions have to do with data, e.g. "iRRIGATE for 0 hours 0 minutes?, ##SPC1## Irrigate for 1 hours 0 minutes?", etc. Control and data are both forms of information. The questioning method of the present invention permits the machine acceptance of both control and data by the user's affirmative responses.

Next, it may be noted that the nature, and conduct, of confirmation is not rigorous. Confirmation varies. Sometimes the user is not offered the opportunity to confirm his directives. Instead, the machine simply starts, or simply stops, or simply commences to display help messages, all as the user's affirmative response has directed. Sometimes, however, the user will be offered the opportunity to confirm his directives. For example, the user will be posited a confirmation question such as "STA 1 DURATION=1h+11 m?" A blinking "?" at the end of the message means "do you confirm".

When confirmation is offered then disavowal is usually by an affirmative response to a disaffirmation question. This subtle point deserves consideration. All control and data that is entered into a machine by a man using the man-machine interface in accordance with the present invention can be achieved solely by selective affirmative responses to questions, each by actuation of the "OK" switch. Confirmation is also by use only of the "OK" switch. For example, "STA 1 DURATION=1h+11m?" is a confirmation question. Actuation of the "OK" switch would confirm the display information. If the previously entered information is desired to be disavowed then the ".uparw." or ".dwnarw." switches would be used to cause the machine to automatically revert to data entry mode. After the user enters new information, the machine would again present a confirmation screen. This process continues until the user uses the "OK" switch in response to the confirmation question.

The man-machine interface in accordance with the present invention cannot be misdirected sufficiently so as reach a communications impasse between man and machine. A machine operating in accordance with the present invention that is programmed to ask a hierarchy of questions on its user interface considers, for each question, what a user probably wants if he/she activates any of the "OK", ".uparw.", or "HELP" switches while that question is displayed. A program jump table is constructed accordingly.

The ability of the man-machine interface in accordance with the present invention to adroitly step up and down the staircase levels of a hierarchal tree no matter what switch is pushed is one reason why people who have never seen or exercised the interface, and who commonly make some "mistakes" (at least initially) in their attempts to use the interface, can nonetheless accomplish satisfactory machine control and parameterization by use of the interface.

The presentation of the hierarchally organized questions and the optional help messages constitute a sufficiently powerful form of man-machine interfacing so as to be, in many cases, self-teaching. A person who has never seen a VCR, a microwave oven, an irrigation controller, or any other machine employing a man-machine interface in accordance with the present invention generally responds to the interface intuitively, and is generally able to attain some success at communicating with the machine totally without instruction. Hitherto challenging machine control and parameterization exercises like setting the time-of-day clock on a VCR are anticipated to be extremely straightforward.

Although users interact with the non-machine interface of the present invention intuitively, and may gain proficiency with the interface by making real control and data entries on it, it is not always desirable that an unskilled user should be controlling and parameterizing a real machine while he/she learns the interface. Additionally, structured learning is generally superior in efficiency and effectiveness to ad hoc learning. Accordingly, the man-machine interface in accordance with the present invention teaches a user how to use the interface by conducting a game as discussed in the next section 1.1. the Present Invention

The interface in accordance with the present invention teaches a user all necessary skills to use the interface by conducting a game. The purpose of the game is to enable the user to make "friends" with the interface, to teach the user how to interact with the interface (primary skills), to teach the user how to accomplish basic tasks with the interface (secondary skills), and to teach the user how one teaches oneself the application specific control options offered across the interface and how one uses them (tertiary skills).

The user is taught how to invoke the use "HELP", how to recognize the types of irrigation controller requests appearing on the interface (option select, number entry, word entry), how to service irrigation controller requests (selecting an option, entering a number, entering a word), and the function of the keys for each type of controller request.

The progression of primary skills acquisition proceeds as follows. The interface attracts a potential user to the vicinity of the irrigation controller and entices the potential user to initiate interaction. To do so the interface alternates an attention-getting display with "Press Any Key to Play Game". The user will press any key. The interface next wants to teach the user how to move through multiple screen text messages. The interface presents the message: "Hello! Please press .dwnarw.". The user must press the ".dwnarw." switch.

The interface will provide the user positive feedback for his action, and will next explain the purpose of the down arrow key for moving through text display. The interface states: "Great! The .dwnarw. key moves you to the next screen of information. Whenever you see a blinking .dwnarw. like this [** .dwnarw. **], there are more screens to read". The user again presses the ".dwnarw." switch.

The interfaces next goal is to teach the user how to invoke help. The interface states: "Very Good Please press the HELP Key". The user must press the "HELP" key.

The interface then explains the function of the "HELP" key. It states in a succession of autoscrolled messages: the .uparw. to proceed through the help explanation. After the help message, you return to where you were when you pressed help. Remember, press the HELP key whenever you need more information to make a decision. This is the end of the help explanation."

The user to this point has invoked the help explanation above. The user presses the ".dwnarw." switch after the last screen to move the machine to the next instructional state.

The interface next desires to introduce the user to the "OK" key. The interface states: "Very Good! Now please press the OK key". If the user presses the "HELP" key then he invokes the help explanation followed with a return to the same interface message. Pressing "OK" moves the user toward the next goal.

The interface's next goal is to explain the purpose and function of the "OK" key. It states: "Thank you. Press the OK key when you are finished selections". The user must press "OK" to continue. If the user depresses the "HELP" key then he/she invokes the help explanation. Depressing "OK" moves the user to the next controller goal.

The interface's next goal is to explain to the user how to enter numbers. The interface states: Up and down arrows also allow you to enter numbers. The .uparw. increases a number, and the .dwnarw. decreases a number. Holding down the .uparw. and .dwnarw. keys makes the keys repeat. The blinking underline [** .sub.-- **] shows you where you are. Use the .uparw. and .dwnarw. keys to enter a 36. Press the OK key when you are done."

The interface then states: "Enter 36 [** .sub.-- **] Press OK when done". If the user presses "HELP" the interface displays "Use the .uparw. and .dwnarw. keys to enter 36. Press OK when you are done". If the user enters an incorrect number then the interface will let the user know he has made a mistake. It will explain the use of the keys again to the user by stating: "Sorry, that wasn't 36. Try again." followed by the help message above, followed by the "Enter 36 . . . " message. If the user enters the correct number then the interface lets the user know he is doing well. It states: "That's right! You're learning fast."

The next goal of the interface is to instruct the user how to select options. It states: keys to change the option. Press the OK key to select the displayed option. Here is an example."

It then states: "What is your favorite color?" The interface then states [** .uparw. **], [** .dwnarw. **], i.e., a blinking up and down arrow. The user must press "OK" to enter. The actual options are: Red, Green, Blue, Yellow, Black, White, Pink, Brown, Purple, Orange, Grey.

If the user presses "HELP" then the controller will display "Use the .uparw. and .dwnarw. keys to move to your choice. Then press OK to select it". The interface then returns to the message above. When the user presses "OK" then he/she has completed selecting an option.

The interface's final goal is to instruct the user how to enter words. The interface states: before we play the game is how to enter a word. Use the .uparw. and .dwnarw. keys to change a letter, then press OK to move on to the next letter.

It then states: "Try entering the word `red`". If the user presses "HELP" then the interface displays: "To enter a word, use the .uparw. and .dwnarw. keys to change each letter. Then press the OK key to continue." The interface then returns to the "Try . . . " message. If the user presses "OK" to enter an incorrect word then the interface will let the user know he has made a mistake. It will again explain the use of the keys to the user. It states: "Sorry, that wasn't the right answer. Try again." It provides the help message. It returns to the "Try . . . " message. If the user enters the correct word then the interface lets the user know he is doing well. It states: "That's right! Now you know how to enter information, and to answer questions."

Obviously all required responses need to ultimately be made to conclude the game. The interface finally displays the user's elapsed time in the game as an indication of the user's proficiency. Man-Machine Interface in Accordance with the Present Invention

The preferred embodiment of a man-machine interface in accordance with the present invention is incorporated in an irrigation controller. This irrigation controller in accordance with the present invention is light-energized with a built-in incident light collector. It exhibits sufficient energy storage to drive a custom CMOS ultra-low-power microcomputer with 32K RAM memory and to cycle up to eight (8) ultra-low-power irrigation valves up to sixteen (16) times each per twenty-four (24) hour period. This provides complete independence from any need for AC power, saving on energy and installation costs and permitting the controller to be located closer to the valves.

An easy to read two-line LCD display with automatic prompting (questioning) in accordance with the present invention is implemented. Each line typically displays sixteen (16) alphanumeric characters. The user is guided through the programming process with easy to understand two-line "prompts," thus substantially eliminating confusion, mistakes, and requirements to repeatedly reference printed or human authority.

Three-button programming with "best guess" defaults is used for all settings. All programming is done by answering simple questions with "OK" or ".uparw." or ".dwnarw." answers in accordance with the present invention. The controller display automatically shows the user "best guess" defaults where applicable.

An on-line help feature in accordance with the present invention gives directions and information for each operational mode and parameter insertion. These on-line help messages are available at any time by pressing a "HELP" key.

The irrigation controller's design is modular in that multiple 8-valve-station controller units can be integrated together. The individual 8-valve-station controller units can be networked together into optionally radio-linked centrally controlled systems, or, alternatively, multiple unrelated controllers on various sites can be centrally managed by optional multi-programming equipment.

Each of the 8 stations for a single controller unit can be independently programmed. This gives the irrigation controller great programming flexibility. Options for (i) simplified watering setups, (ii) "Autosplit" setups with automatically programmed split cycles and sequential non-overlapping operation, (iii) "Ration" setups for odd/even (day of month) water rationing, (iv) "ISC" setups with complete independence between stations, (v) "Special" setups for lights and fountains, (vi) periodic or one-time "Add-on Soak Cycle" setups, and (vii) for multiple "Add-on Syringe Cycle" setups are implemented.

Timing control of the irrigation valves is from 1 minute to 8 hours in one minute increments. Thus one minute precision in starting or stopping irrigation is combined with the ability to set watering durations of up to 8 hours for each start time. One-time or periodic "soak cycles" can have a duration of up to 16 hours.

A calendar is maintained based on "perpetual calendar" data in permanent memory. Schedules may be established for specific days or every "so many" days. This permits flexible day cycles for irrigation, and allows different stations to operate on different day cycles.

Up to 128 automatic starts per day are enabled, thereby meeting the most demanding applications.

The controller's split cycle capability permits watering times to be split into up to 16 substantially equal increments. This minimizes runoff and puddling by splitting the programmed watering duration into shorter cycles each of which is separated by a programmable minimum "off" time.

A System Budgeting Factor of 10 to 200% acts to determine the numbers of split cycles. The System (water) Budgeting Factor increases or decreases the number of split cycles instead of acting as a total duration multiplier which can lead to runoff and puddling. Monthly budgeting with pre-set default values for each month is also available. This allows an entire year's scheduling to be set up.

Automatic sequential program generation permits "Excluded Time Intervals". The controller automatically generates a sequential matrix of start times for all active valves and split irrigation cycles based on user input for determined total watering durations by valve, either site information selection or operator entered number of split cycles, and on any user-defined "Excluded Time Intervals" when no watering is desired.

For very simple applications the advanced features of the controller can be skipped merely by an affirmative answer to the question "SKIP Extra Options?". This makes it extremely easy to enter simple programs for applications where some of the more sophisticated features of the controller are not needed.

All valve stations can be programmed with totally independent watering day cycles. Another option, "Special Starts", can be used for control of non-valve devices such as fountains, or lighting equipment.

One-time or periodic "Soak" cycles can be overlaid on any regular watering program. This feature can be used for watering in fertilizer, for periodically deep watering trees and shrubs in turf areas, and for periodically leaching salts in drip applications.

Multiple daily cooling or frost-wipe "Syringe" cycles can be overlaid on any regular watering program for any pre-programmed month(s) when needed. These cycles help prevent wilting and scorching of plant materials during hot summer months or damage from freezing or morning dew in cold weather months.

Even and odd days can be automatically excluded as watering days with the choice of "ONLY ODD" or "ONLY EVEN" Water Day Cycles. This allows for odd/even water rationing schedules to be easily programmed where this is mandated by law.

A programmable "Delay Start" permits watering to be suspended for up to 90 days during the rainy season, and at the end of the programmed "Rain Delay" the regular watering schedule will automatically resume.

A special "View Info" mode allows the user to review all settings or to view an event report which displays the controller history and daily schedule. This permits the user to easily review the daily schedules of valve on/off cycles, or to view a list of the last 128 events (watering cycles, program changes, etc.) in chronological order starting from the earliest event.

Built-in wire continuity and short testing, system self-test and report functions are implemented. The user is alerted if shorted or open valve wires exist, and the unit performs a self-diagnostic test when requested.

A "Test Sequence" allows each valve to be operated in sequence for one to thirty minutes. This allows the irrigation system to be easily periodically tested.

Valve stations can be operated automatically, semi-automatically, or manually. In semi-automatic mode, all or selected valves can be run with either a "normal", "soak", or "test" duration. This allows the user to do a one-time soak for watering in fertilizer or new plantings. The controller then automatically reverts to the automatic "Run" mode

Three level access codes provide security and render the controller useless if stolen. Separate codes for gardeners, supervisors, and factory personnel insure that only authorized individuals can change the controller settings, and that codes can be easily changed as operating personnel change. Controller Using a Man-Machine Interface In Accordance with the Present Invention

The preferred embodiment of an irrigation controller using a man-machine interface in accordance with the present invention (i) receives specified information; (ii) makes decisions and performs calculations based on the specified information; (iii) typically displays the decisions and results derived in order that such may be, if desired, manually changed or modified; (iv) generates irrigation schedules for one or more irrigation stations in accordance with calculated results and (v) conducts irrigation in accordance with the generated schedules.

Information may be specified to the controller by manual data entry or by the download of information (and/or firmware operating programs) through communication ports of the controller.

The calculations are performed by a microprocessor, embedded within one of the Application Specific Integrated Circuits of the controller, that operates under control of firmware instructions resident within any of ROM, RAM, and EE memories of the controller.

The preferred embodiment of an irrigation controller in accordance with the present invention accepts high level information regarding the irrigation site and equipment. This high level information typically concerns (i) soil type, (ii) type of sprinkler or irrigation head, and (iii) terrain.

From these informational inputs a table lookup is performed to determine (i) the maximum "on" time of an individual irrigation watering time and (ii) the minimum "off" time between successive irrigation cycles. A typical table with times in minutes is as follows: __________________________________________________________________________ Lookup Table for "On" and "Off" Times of Irrigation Split Cycles MAX ON HEAD     LEVEL HILLY LEVEL HILLY LEVEL HILLY MIN OFF TYPE     SAND SAND LOAM LOAM CLAY CLAY SAND LOAM CLAY __________________________________________________________________________ FLAT SPRAY 3    3     6   3    3    2    30  30  30 LAWN SPRAY 5    5     9   5    5    3    30  30  30 ROTOR    8    8    16   8    8    5    30  30  30 IMPACT   8    8    16   8    8    5    30  30  30 STREAM SPR 8    8    16   8    8    5    30  30  30 MICROSPRAY 10   10   20   10   10   7    30  30  30 DRIP     30   30   60   30   30   30   30  30  30 __________________________________________________________________________ (The maximum ON values in this lookup table were calculated by dividing the maximum precipitation rate for each type of sprinkler into the minimu percolation rate typical for each type of soil, and multiplying by 60 to convert to minutes. Since sandy soils require more frequent irrigation than loam soils because of their low moisture holding capacity, the same maximum ON values were used for sand as for clay even though sand has a much higher percolation rate than clay. Loam has the proper balance of percolation rate and moisture holding capacity, and thus the maximum ON times for loam are longer than for either sand or clay. The minimum OFF times are based on field observation.)

The preferred embodiment of the irrigation controller further receives, e.g., by manual data input, a specification of the desired total irrigation time duration for each station. The controller calculates the number of irrigation cycles within the irrigation schedule for that station as: ##EQU1## For example, for a station irrigating hilly terrain, loam, soil, with a microspray irrigation head the number of cycles for a total irrigation watering time of 30 minutes is: ##EQU2## The irrigation controller may optionally display the irrigation cycle time and number of cycles. The number of cycles may be fractional. In such cases the duration of the last cycle is truncated, so that the total of all the split cycles always exactly equals the duration entered by the user.

The preferred embodiment of the irrigation controller then proceeds by use of (i) the minimum irrigation "off" time, and (ii) the maximum irrigation "on" time that now becomes the duration of an optimal, normal, non-partial irrigation cycle (both quantities derived by table lookup) and (iii) the calculated number of irrigation cycles, to generate the irrigation schedules. The manner of this schedule generation is to (i) allocate irrigation cycles for any one station as "on" times followed by "off" times until the calculated number of irrigation cycles ensue, insofar as (ii) the necessary and prioritized scheduling of irrigation cycles for other stations permits. These rules are best illustrated by example. If, for example, station 1 is a sole station that should, in accordance with the previous example of hilly terrain loam soil with a microspray irrigation head, irrigate for 3 cycles of 10 minutes each cycle separated by 30 minutes between cycles, an irrigation schedule would be generated as follows: Station Station          Station Time       #1      #2          . . . #8 ______________________________________ 12:00 mid. on      off              off 12:05      --      --               -- 12:10      off     --               -- 12:15      --      --               -- 12:20      --      --               -- 12:25      --      --               -- 12:30      --      --               -- 12:35      --      --               -- 12:40      --      --               -- 12:45      --      --               -- 12:50      --      --               -- 12:55      on      --               -- 1:00 am   --      --               -- 1:05      off     --               -- 1:10      --      --               -- 1:15      --      --               -- 1:20      --      --               -- 1:25      --      --               -- 1:30      --      --               -- 1:35      --      --               -- 1:40      --      --               -- 1:45      --      --               -- 1:50      on      --               -- 1:55      --      --               -- 2:00      off     --               -- 2:05      --      --               -- etc. ______________________________________

The last irrigation by station #1 was during the period 1:50 to 2:00 a.m. The cycle recommences the following day.

If station #2 is also enabled under the same circumstances the combined irrigation schedules will be as follows: Station Station          Station Time       #1      #2          . . . #8 ______________________________________ 12:00 mid. on      off              off 12:05      --      --               -- 12:10      off     on               -- 12:15      --      --               -- 12:20      --      off              -- 12:25      --      --               -- 12:30      --      --               -- 12:35      --      --               -- 12:40      --      --               -- 12:45      --      --               -- 12:50      --      --               -- 12:55      on      --               -- 1:00 am   --      --               -- 1:05      off     on               -- 1:10      --      --               -- 1:15      --      off              -- 1:20      --      --               -- 1:25      --      --               -- 1:30      --      --               -- 1:35      --      --               -- 1:40      --      --               -- 1:45      --      --               -- 1:50      on      --               -- 1:55      --      --               -- 2:00      off     on               -- 2:05      --      --               -- etc. ______________________________________

The last irrigation was by station #2 was during the period 2:00 to 2:10 a.m. The cycles recommence the following day.

If the full eight stations are all enabled under the same circumstances then the combined irrigation schedules will be as follows: Station Station          Station Time       #1      #2          . . . #8 ______________________________________ 12:00 mid. on      off              off 12:05      --      --               -- 12:10      off     on               -- 12:15      --      --               -- 12:20      --      off              -- 12:25      --      --               -- 12:30      --      --               -- 12:35      --      --               -- 12:40      --      --               -- 12:45      --      --               -- 12:50      --      --               -- 12:55      --      --               -- 1:00 am   --      --               -- 1:05      --      --               -- 1:10      --      --               on 1:15      --      --               -- 1:20      on      --               off 1:25      --      --               -- 1:30      off     on               -- 1:35      --      --               -- 1:40      --      off              -- 1:45      --      --               -- 1:50      --      --               -- 1:55      --      --               -- 2:00      --      --               -- 2:05      --      --               -- etc. ______________________________________

The last irrigation by station #1 was during the period form 2:40 to 2:50 a.m. The last irrigation overall was by station #8 during the period from 3:50 to 4:00 a.m. In total, eight stations have irrigated for a total of 30 minutes each during 4 chronological hours.

The goal of the staggered starts is to (i) operate one irrigation station at a time with (ii) a minimum amount of dead time on all stations consonant with (iii) operating each station in accordance with its maximum "on" and minimum "off" times while (iv) prioritizing between stations in accordance with their numbers. Each successive station is looked at in turn to see if an irrigation cycle for that station will properly fit within a window within the combined schedules, and if so the cycle is scheduled and the station will water. Which station's cycle to insert in any given window is determined by (i) which station has had the longest wait for a turn to have an irrigation cycle, and if two stations have equal waits then by (ii) the lowest numbered station first.

The preferred embodiment of an irrigation controller in accordance with the present invention accepts the specification, normally by user input, of one or more exclusion time intervals during which irrigation is not to transpire from any station. The specification is normally in the form of interval start and stop times, which are the corresponding times that irrigation is stopped and permissively restarted. The scheduling of irrigation cycles simply works around these one or more exclusion time intervals. An irrigation cycle may start before an exclusion interval, be suspended (off) during the exclusion interval, and resume to completion after the exclusion interval. This in essence adds an extra split watering cycle.

The preferred embodiment of an irrigation controller in accordance with the present invention accepts specification of a budget factor. The controller uses this budget factor to calculate a new, budgeted, total irrigation time duration as ##EQU3## For example, if the budget factor is 200% and a station's total irrigation time is 1 hour, then budgeted total irrigation time duration=200%.times.1 hour ##EQU4## The controller then proceeds to calculate a budgeted number of irrigation cycles in consideration of the maximum "on" time derived from the table lookup as ##EQU5## For example, for the hilly terrain loam soil irrigated with a microspray irrigation head: ##EQU6## This should be compared to the 6 cycles during which irrigation would normally transpire. The creation of irrigation schedules for the adjusted (budgeted) number of irrigation cycles transpires normally. There is also a Monthly Budget feature that allows a different budget to be set for each month of the year. Defaults are provided for each month.

The preferred embodiment of an irrigation controller in accordance with the present invention accepts programming of a deep soak cycle for a selected station that overrides, supplants, and substitutes for all normal irrigation that might otherwise normally be scheduled for the station upon a particular day.

The (i) time duration, (ii) first occurrence, and (iii) periodicity days of the soak cycle are specified to the irrigation controller. The soak duration can be automatically calculated from site information, or user entered. For example, a particular, station might be programmed to conduct a 1 hour soak cycle every 30 days from a set day. Upon the set day, and each 30 days thereafter, the composite irrigation schedules will be routinely computed in a normal manner as if the particular station had only one irrigation period of duration 1 hour. All other irrigation cycles at other stations may be shifted in time-of-day but will otherwise proceed normally. Any base irrigation cycles that fall on a soak day for any particular station are skipped. Syringe cycles, if programmed, can fall on a soak day (see below).

Syringe cycles are implemented in the preferred embodiment of an irrigation controller in accordance with the present invention as a separate schedule, automatically generated, that is (i) prioritized above the normal irrigation schedules. Syringe cycles are programmed in common for all stations based on one (only) set of input information for all parameters, except the syringe cycle duration. (They are not, however, conducted simultaneously.)

The controller accepts specification of the (i) syringe cycle duration by station, (ii) start time of the first station's (i.e., station #1) initial syringe cycle occurrence, (iii) start time of the first station's final syringe cycle occurrence, (iv) periodicity of the syringe cycles in the defined time interval, and, (v) active months during which syringe cycles are to be performed. The controller schedules syringe cycles of the indicated duration starting at the initial start time for station #1 followed by station #2 continuing up to station #8. After the proscribed time interval the syringe cycles repeat, and so continue until the last sequence of eight cycles upon the eight stations. This schedule is enabled only for the designated months.

For example, 1 minute duration syringe cycles might be specified to occur every two hours during a syringe period starting at 10:00 a.m. and ending with a 6:00 p.m. start time. Eight minutes of syringes would transpire, one minute per station, from 10:00 to 10:09 a.m. Another series would transpire from 12:00 noon to 12:09 p.m. The final series would be from 6:00 to 6:09 p.m. Each of these series would suspend any other irrigation cycle otherwise in progress. Each suspended cycle will conclude to its full scheduled duration at the end of the current series of syringe cycles.

The preferred embodiment of an irrigation controller using a man-machine interface in accordance with the present invention uses Light Energized Irrigation Technology (LEIT.TM.) (trademark of Solatrol, Inc., San Diego, Calif.). It can operate with the amount of incident light available in northern latitudes on a worst-case cloudy winter's day without needing any of the batteries, external solar panels, or the A.C. power connections required for traditional controllers. It is also extremely flexible and versatile in its operation.

A diagrammatic view of the preferred embodiment of the controller, with its cover plate removed and operator's panel area exposed, is shown in FIG. 1. Controller 1 is typically attached to post 2. An array of photovoltaic devices 10 (not shown) is located under transparent lens 11 on top of case 12.

Various electrical connectors are presented. A valve connector block 13 permits electrical connection by wires (not shown) to up to eight (8) electrically actuated valves. A control key socket 14 accepts a pluggable power source (not shown), being a 9 vdc battery suitably packaged so as to plug into socket 14. A digital accessory connector 15 permits communication connection to a multiprogramming unit (not shown) that may upload and download programs into the controller 1 (among other alternative ways of programming controller 1). The connector 15 is a standard type, and may, under firmware control within controller 1, interface to further devices. A sensor connector block 16 permits connection of up to eight (8) optional soil moisture sensors or other sensing devices. These soil moisture sensors, and the control proceeding therefrom, are not taught within this specification for being unimportant to the present invention.

A control panel 20 contains a liquid crystal display (LCD) 21 for showing information, questions, and directives. The control panel 20 also contains pushbutton switches 22-25. A "HELP" switch 22 causes the controller 1 to display more information and/or instructions, keyed to the current operation or displayed questions, in LCD 21. The ".dwnarw." switch 23 and the ".uparw." switch 24 are used to change the displayed options and data which are needed to specify the parameters of irrigation (e.g., the watering schedule) and to enable selectable readout of controller stored data. The "OK" switch 25 is used to select options and confirm data entries.

The controller 1 is controlled in its operation by firmware running on a special Application Specific Integrated Circuit (ASIC) that includes a microprocessor. The explanation of the controller 1 hardware is contained in major sections 3-5 of this specification. The firmware executed by controller 1 is attached as Appendix A to this specification. This major section 2 deals with the user interface to controller 1, and serves to show its many unique aspects that are controlled and parameterized by an interface in accordance with the present invention.

The term "programming" used throughout this specification includes actions performed at the operator interface to the controller 1--actions normally but not necessarily performed in the field--by which the controller 1 is parameterized and directed in its programmed operation. The firmware itself is, of course, also "programmed". In some cases the act of "programming" at the operator's panel will alter the flow, as well as the parameters used, within the firmware; thus constituting a form of "programming" at the process control level. The word "programming" is used to refer to the total compendium of operator/programmer interface to, and control of, irrigation controller 1. The word includes actions more exactingly thought of as parameterization (typically done in the field), as well as actions more exactingly thought of as coding (typically done in the factory or depot).

The key features of the user interface to the irrigation controller in accordance with the present invention are as follows:

The irrigation controller always shows the user two or more blinking choices or options. To see next available option, the user must press ".uparw.". To see the previous option, the user must press ".dwnarw.". When best option is displayed, the user must press "OK".

When entering numbers or other information, items to accept or change will blink. To increase numbers the user presses ".uparw.". To decrease them he/she presses ".dwnarw.". Holding down either arrow key makes items change faster. When the desired item is displayed, the user must press "OK".

When the user sees a BLINKING QUESTION MARK (?), the irrigation controller is asking if the settings shown are correct. To keep the settings shown, the user must press OK", or to change settings, the user must press ".uparw." or ".dwnarw." to advance to a new setting.

The irrigation controller lets the user copy the settings made for one valve for use with the next valve. The user has two options when he/she is asked:

To use SAME setting, the user must press "OK". To enter a new setting, he/she must press ".uparw." or ".dwnarw.".

To get help at any point the user should press "HELP". The user may then read the displayed information. To read further, the user should press ".uparw.". A blinking UP ARROW ".dwnarw." in the lower right hand corner of the display screen reminds the user how to advance to the next screen.

To back up to the previous text, the user should press ".uparw.". When the user is finished with help messages then he/she should press ".dwnarw.". The machine will continue where it was before the user pressed "HELP".

When the user first inserts a pluggable power source to activate the man-machine interface, the display will come on immediately if the irrigation controller is fully charged. Otherwise, the message: "Charging! Please Wait . . . " flashes periodically. The 9-volt battery in the pluggable power source charges the irrigation controller, and provides power to run the display. New and previously unpowered, or profoundly discharged, irrigation controllers may take up to 10 minutes to charge fully. The user should use a fresh 9-volt alkaline battery, or Nickel-Cadmium rechargeable battery in the pluggable power source. When it becomes fully charged, the irrigation controller displays the following message: "Press OK when most readable 1". This message is sequentially displayed at three different contrast levels (numbered 1 to 3). The user should press "OK" when the display is most readable. The display contrast will cycle continuously (autoscroll) until the user selects a contrast level.

The irrigation controller next conducts the practice game previously discussed in Section 1.1 to teach the user the basic operating skills that he/she needs to use the irrigation controller. The game shows the user how to use the keys and how to select options. The user's score on the game will depend on how fast he/she can correctly answer ten questions. Some of the questions require the user to press "HELP" for a hint about the correct answer.

To play the game, the user should press "OK" when the irrigation controller asks "Press OK to PLAY GAME". The game is self-teaching. When the user is done, the user will have all the skills he/she needs to use the irrigation controller.

Once the user is familiar with the few simple skills that he/she needs to know to operate the irrigation controller, he or she can thereafter skip the game by merely pressing ".uparw." or ".dwnarw.".

After setting the display contrast and conducting the optional practice game, the irrigation controller asks "SKIP Self Test?" To do a system self test, the user must press ".uparw." and then press "OK" to the question "DO Self Test?" The system self test automatically tests the wiring and displays the time, date, & current operating mode.

If the user has entered and activated passwords in setup system he/she will need to enter a correct password to continue.

The user must next enter either a 3-digit supervisor or gardener code, pressing "OK" after each digit (letter or number). Without a correct password the user cannot see or change watering schedules or other irrigation controller settings, but can do a system self test.

To see or change irrigation controller settings, the user must temporarily stop the current run cycle (if running) by pressing "OK" when the display reads "Press OK to STOP RUNNING". The Computer automatically resumes running when the user removes the "LEIT Key.TM." or starts a new automatic or semi-auto run.

When the display reads "HELLO! PRESS OK TO PICK OPTIONS" the user must press "OK" to see the first blinking option. There are six main options used in running the irrigation controller. To see all of the main options, the user keeps pressing the ".uparw." key.

When the user decides which option he/she wants to use, he/she must then press "OK". The six blinking options are:

ENTER SCHEDULE. ENTER SCHEDULE lets the user enter or change watering schedules. Depending on the ACTIVE watering program chosen in SETUP SYSTEM, the user can enter either: MAIN PGM, ALTERNATE PGM, or DAILY PGM.

RUN SCHEDULE. RUN SCHEDULE lets the user run watering schedules. There are three run options: AUTOMATIC RUN, SEMI-AUTOMATIC RUN, RESUME LAST RUN.

MANUAL RUN. MANUAL RUN lets the user RUN STATIONS one at a time, in groups, or in a defined TEST SEQUENCE.

NO WATERING. For times when the user wants NO WATERING to occur, he/she should select this option. The irrigation controller will keep its schedules, but will not conduct irrigation.

SETUP SYSTEM. SETUP SYSTEM lets the user set up the system to fit his/her site & specific needs.

SEE INFO. SEE INFO lets the user see an EVENT HISTORY by date and time, or see today's DAILY SCHEDULE of all watering starts by station.

The first time the user programs the irrigation controller, he/she normally uses Setup System to enter his/her specific requirements. System settings are optional, since the irrigation controller comes with pre-programmed station numbers and monthly water budgets.

After making any desired changes in the SYSTEM SETUP, the user should choose ENTER SCHEDULE to enter a watering schedule. The user should choose RUN SCHEDULE to start AUTOMATIC or SEMI-AUTOMATIC watering, and to see or change the time, watering budgets, or optional rain delays.

SET PASSWORDS. This sequence allows the user to establish passwords. Passwords prevent unauthorized individuals from changing settings. The user can enter two separate codes, a gardener and a supervisor code. A third factor code is preset.

SET COMPUTER ID. SET COMPUTER ID assigns a name or number for each individual controller in multi-controller applications.

SET ACTIVE PGM. SET ACTIVE PGM lets the user switch between different watering schedules. The user should select MAIN PGM, ALTERNATE PGM, or DAILY PGM.

WIRING SETUP. WIRING SETUP lets the user do a wire self-test, change the number of active stations, change the station numbers assigned to each valve without switching the valve wires, or use a pump relay. Pump relays are automatically activated whenever any other station is on.

MONTHLY BUDGETS. MONTHLY BUDGETS customize the watering budgets for each month of the year, based on the hottest month and the historical weather patterns (rainfall and evapotranspirative demand) for the user's particular area.

SYSTEM SETUP OK. The user should select this option when he/she is finished configuring the irrigation control system.

PASSWORDS limit access to the controller. Tne user can enter two different PASSWORDS: SUPERVISOR CODE and GARDENER CODE. Both codes allow access to the irrigation controller, but only the SUPERVISOR CODE lets the user change passwords. When the Computer asks "Supervisor Password : --- ?" the user should depress either of the arrow keys ".uparw." or ".dwnarw." to change the three dashes (-) to the desired letters or numbers, pressing "OK" after each letter or number. The user enters the GARDENER code in the same way.

After the user has entered both passwords, the controller asks: "ACTIVATE All Passwords?" The user will now need a password each time he/she uses the irrigation controller. If the user forgets his/her passwords, he or she may use a pre-set FACTORY code stamped on his/her irrigation controller Warranty Card.

SETUP SYSTEM allows the user to assign a name or number to each irrigation controller. This allows each irrigation controller to be uniquely identified by communication devices, such as the MULTI-PROGRAMMER unit taught in co-pending U.S. patent application Ser. No. 255,150 filed Oct. 4, 1988, a device that allows programs for multiple irrigation controllers to be stored and downloaded simply by plugging into the communication port on each irrigation controller. Similarly, RADIO-LINK CENTRAL STATION is a unit that allows individual field irrigation controllers to communicate with a central office irrigation controller via radio. Entering an ID name or number works exactly like entering a PASSWORD code, except that the irrigation controller ID is 9 digits long. To use a name less than 9 digits long, the user must press "OK" for each unused dash (-) on the entry screen. The irrigation controller ID can be composed of all letters, all numbers, or a combination of letters and numbers.

The irrigation controller lets the user set up three entirely different watering programs. MAIN PGM is used to control a regular watering schedule. Each station can have a totally independent watering day cycle. The user can either use or skip all of the irrigation controller's advanced features, such as Auto Splits, Syringes, Soaks, Special Starts, and Excluded Periods, with this program. ALTERNATE PGM lets the user enter a separate and independent schedule for special needs, such as watering newly planted or seeded areas. The user can also use this program to experiment with a new watering schedule without losing his/her MAIN PGM. DAILY PGM is entered to modify the factory-entered backup watering schedule that is automatically invoked if the light-gathering photocells of the irrigation controller are covered for prolonged periods, causing a power loss. This program is stored in special non-erasable memory within the irrigation controller. Only ONE of these programs can be active at one time.

The option selected in SET ACTIVE PGM becomes the active program for both ENTERING and RUNNING schedules.

Wiring setup lets the user do a wire check to self-test the wiring for opens and shorts. The user may either see or change the current number of active stations. Initially all 8 stations are active. To use fewer stations, the user must tell the irrigation controller how many stations he/she wants to use. This manner of data entry simplifies entering a watering schedule, since the user will not have to enter settings for any unused stations. The user views the current valve-wire identification numbers. The irrigation controller initially has Station #s 1 to 8 respectively assigned to the top through the bottom positions of the physical valve-wire terminal strip. The user first tells the irrigation controller whether or not he/she is using a PUMP RELAY. The user may then proceed to change the station #s assigned to the physical valve-wire positions without actually changing the valve-wire positions.

First the user must do a WIRE CHECK to check for shorted or broken (open) valve-wires. The LEFT symbol on the display shows the status of the TOP wire position with `o'=OPEN, `V'=VALVE, `x'=SHORT. An "open" indicates that either no wire is connected or the wire is broken or not inserted properly into the connector. The user should try re-inserting the wire to correct the "open" condition. In case "shorts" are detected it is wise to install a new wire, instead of trying to find the shorted wire.

The user must never attach batteries or continuity testers to the wires while they are still attached to the irrigation controller because this can cause permanent damage to the irrigation controller.

The irrigation controller asks: "Use 8 Stations?" To change the display number, the user must press ".uparw." in order to enter the number that he/she would like to use. This number can be changed later.

The irrigation controller asks: "View Current Station IDs?" The current ID shows how the wires are connected to the valve terminal strip (on left side of irrigation controller). The leftmost number shows the number assigned to the top light grey connector pair on the left terminal strip.

When the irrigation controller asks: "Enter New Station IDs?" the user should press OK" to change valve numbers without switching wires.

USE PUMP RELAY lets the user employ the last active station number to control a pump relay. The pump relay will come on when any other valve is on. To activate a pump relay, the user must press "OK" when the irrigation controller asks "USE Pump Relay?".

To identify the valves to the irrigation controller, the user must go to the valve station that he/she wants to be Stn #1. The user inserts a pen or a paper clip into the small hole on the wire connector between the valve pigtail and the wire run to the irrigation controller. This action depresses a switch which tells the irrigation controller to assign identification #1 to this station. The user then goes to the valve station that he/she wants to be Stn # 2, and repeats this process. The user ultimately conducts this process for all wired stations. If the system displays a pump relay, the user must identify the pump relay as the last station number. After conclusion of the identifications, the user must press "OK" to SAVE new valve number assignments, and to ERASE old ones.

A system setup lets the user customize the monthly watering budgets of the irrigation controller to the weather pattern in the user's geographical area. The irrigation controller is pre-programmed with monthly watering budgets that reflect typical seasonal weather changes. It automatically changes these estimated monthly watering budgets based on a user input for the hottest month in the user's geographical area. The hottest month is always budgeted at 100%. The user can change each individual monthly watering budget to match the particular weather for the user's area. The appropriate budget for each month is the historical Net ET.sub.o (Evapotranspirative demand in inches) for the month divided by the demand for the hottest month. ##EQU7## where Net ET.sub.o =Total ET.sub.o for month - Total Rainfall for month. The user can fine tune the monthly watering budgets when he/she starts a new AUTOMATIC RUN. Run Budgets can be changed in 10% increments above or below the normal monthly budgets (from 10% to 200% of normal). This does not change the normal monthly budgets.

The user must press OK" after he/she has made all desired changes in the other SETUP SYSTEM options.

In order to go back and change one or more of the SETUP SYSTEM options, the user should press ".uparw." or ".dwnarw." and then select the SETUP SYSTEM option that he/she wants to change.

SET NEW SCHEDULE lets the user enter a new watering schedule. A watering schedule includes HOW LONG to water with each station. This is the Total Duration or Run Time that will be used with a Water Budget of 100%. The watering schedule also includes WHEN to start watering. This is the Start Time. The user need only to enter one Start Time, since the irrigation controller automatically calculates all repeat starts. The watering schedule also includes HOW OFTEN to water with each station. This is the Watering Day Cycle. Finally, the watering schedule optionally includes EXTRA OPTIONS. For very simple applications the user can choose to SKIP some or all of the many available EXTRA OPTIONS. The user presses "OK" to SKIP all of the extra features, or presses ".uparw." or ".dwnarw." to see all the options available: Auto-splits, Excluded Periods, Soaks, Syringes, and Special Starts.

The user selects this option to see or change a previously entered schedule. The user may see or change some or all of the following previously entered settings: Durations, Start Time, Day Cycles, Extra Options, Nothing. The user must press "OK" for each type of setting that he/she wants to see or change. The previously entered settings will then be displayed, one by one, with a blinking question mark (?).

The user should press "OK" to keep the setting shown and advance to the next setting, or should press ".uparw." or ".dwnarw." to change the setting shown. This process must be repeated for each setting that the user wants to see or change. For EXTRA OPTIONS the user will get additional choices. These choices differ depending on whether or not the Extra Option listed on the top line of the display was used previously. If the feature was used previously, the choices are: SEE/CHANGE (which lets the user review or modify current settings), KEEP SAME (which lets the user keep the same settings without reviewing them), and CANCEL (which lets the user stop using the current Extra Option).

If the feature was not previously used, the choices are: ADD (which lets the user start using a previously unused Extra Option), NONE (which lets the user continue NOT using the current Extra Option).

When the user is finished reviewing or changing extra options, he/she then picks: "Extra Options: ALL OPTIONS OK". When the user is are finished reviewing or modifying the previous settings, he/she selects: "See or change NOTHING". The irrigation controller then tell the user that it is SAVING the user's program. Any changes the user has made will not be saved until the user advances to this point.

The user may enter the TOTAL desired watering time per day for each valve. The irrigation controller automatically splits this duration into shorter repeat cycles (if needed), based on the site information for each station. Watering Durations can be from 1 minute to 8 hours. The user must enter numbers for both hours and minutes. The ARROW KEYS are used to select an appropriate hour (h), followed by pressing "OK". To enter a total duration of less than 1 hour, the user should press "OK" for zero hours (Oh). The desired number of minutes (m) is entered by using the ARROW KEYS, and again pressing "OK". Entering a 100% Duration=0h+Om lets the user SKIP watering with the indicated valve number. The user continues each duration just entered by pressing "OK" when the irrigation controller displays the entered duration (in hours+minutes) followed by a blinking question mark. The user is then asked if he/she wants to Use SAME SETTING for next valve? This lets the user copy settings from one valve station to the next. The user will press one of the ARROW KEYS to enter a different duration.

The user may enter when to START WATERING commencing with the first active valve station. The ARROW KEYS are used to select the desired hour, followed by pressing "OK". The user next sets the desired minutes after the hour when he/she wants to begin watering, and again presses "OK". To confirm the start time the user just entered, he/she still again presses "OK". The user need only to enter one Start Time because the irrigation controller automatically calculates all the repeat start times.

The user should be sure to use AM for morning start times, and PM for afternoon start times. Noon and Midnight are indicated 12:Noon and 12:Midn. The user must select a Start Time early enough to finish before midnight if he/she is using long watering times or an Excluded Period. If there are times during the day when the user wants NO WATERING to occur, he/she may set an Excluded Period. This tells the irrigation controller to automatically SKIP over this period of time when it automatically calculates the repeat starts.

The hierarchical structure of the man-machine interface, specifically to an irrigation controller, in accordance with the present invention is outlined in Table I of previous Section 2.1. An abbreviated description of the programmed management of the interface in accordance with the hierarchical structure is contained in this section 3.0 A chart showing the mode dependent functions of the ".uparw.", ".dwnarw.", "OK" and "HELP" is shown in FIG. 7. Finally, a diagram showing the possible entry of control and data on the preferred embodiment of a man-machine interface in accordance with the present invention is shown in FIG. 8, consisting of FIG. 8a through FIG. 8i. The Table I, section 3.0, FIG. 7 chart and FIG. 8 diagram considered collectively accord understanding of how the preferred embodiment of the man-machine interface functions in detail in its preferred application in an irrigation controller.

At its first level the irrigation controller presents through its interface the following six questions: "ENTER SCHEDULE?", "RUN SCHEDULE?", "MANUAL RUN?", NO WATERING?", SETUP SYSTEM?", and "VIEW INFO?"

An OK response to the first-level question "ENTER SCHEDULE?" causes the second level to be entered. At this second level the irrigation controller presents the following two questions: "ENTER NEW PROGRAM?", "SEE/CHANGE PROGRAM?"

An OK response to the second-level question "ENTER NEW PROGRAM" causes the third level to be entered (at this point in the hierarchy). At this third level point the controller will (i) accept data entry and (ii) ask further, third-level, questions.

At the onset, the controller will display "STA 1 DURATION=Oh+Om" The hours field is initially blinking. After running the hours to the desired number 0-8, and pressing OK active entry shifts to the minutes field, which then blinks. Entry continues for the number of stations set-up in the system, a maximum of eight.

Next at this level three, and at this point in the hierarchy, a principle start time from which all other start times will be automatically calculated is entered. The controller displays "Start Time=12:mid" and progresses through the hours, and then the minutes.

Also at this level three at this point in the hierarchal tree, the irrigation controller will sequence to the following two questions:

"SKIP Day Cycle Options", or "USE Day Cycle Options"

"SKIP EXTRA OPTIONS" or "USE EXTRA OPTIONS"The blinking "SKIP" messages are always displayed first, and with use of either arrow key (".uparw.", ".dwnarw."), the message cycles to "USE". One alternative--"SKIP" or "USE"--must be adapted with the "OK" key.

An "OK" response to the third-level question "SKIP Day Cycle Options" causes branching to the fifth level questions within the second following paragraph.

An "OK" response to the third-level question "USE Day Cycle Options" causes the fourth level to be entered at this point in the hierarchy. At this fourth-level point the controller will ask

"DIFFERENT For All Stns?" or "SAME For All Stns?" The blinking "DIFFERENT" message is always displayed first, followed by the "SAME" message upon use of either arrow (".uparw.", ".dwnarw.") key.

Adaptation of either fourth-level message with the "OK" key causes the following four fifth-level questions to be displayed:

An "OK" response to the "SPECIFIC" question gives a display of:

The user depresses "OK" for each day to water (causing a letter mnemonic to appear at the appropriate top-line display position) and to sequence to the next day, or depresses an arrow key to sequence to the next day.

Responses to the "SO MANY", "ONLY ODD", and "ONLY EVEN" fifth-level questions are straightforward. For example, "SO MANY" can be answered (by appropriate key actuations) to be every 90 days in a range from 1 to 90; "ONLY ODD" can be answered to be ODD @ XX days in a range XX from 2 to 90 by twos; and "ONLY EVEN" can be answered EVEN @ YY days in a range YY from 2 to 90 by twos.

At any conclusion in the hierarchy below the third-level question "SKIP Day Cycles" the controller will advance to the related third level question(s): "SKIP EXTRA OPTIONS" or "USE EXTRA OPTIONS".

Reverting to a higher level in the hierarchy, an "OK" response to the third level question "USE EXTRA OPTIONS" will cause the controller to cycle through the following six fourth-level questions:

The fourth-level question "AUTO-SPLITS?" may be adapted, causing display of fifth-level questions:

The default to the first fifth-level question, and to the fourth level question "AUTO-SPLITS" itself, is based on site information by station. The default to the site information itself (entered elsewhere) is level sand, flat sprays. After default, or entered, information is accepted the controller will display calculated maximum ON and minimum OFF times by station.

Adaptation of the fourth-level question "EXCLUDED PERIOD" requires entry of a start and a stop time to the excluded period, all in the conventional manner of entering time first by (blinking) hour and then by (blinking) minute.

Adaptation by pressing the "OK" key of the fourth-level question "SYRINGE CYCLES" causes an irrevocable sequence to gather the following information (not hereinafter next expressed in the form of questions):

The detailed information entry varies but is substantially respectively similar to data entry transpiring in response to (i) the fifth-level question "SPECIFIC . . . , (ii) the third-level question "STA 1 DURATION=Oh+Om", (iii) the fourth level question "EXCLUDED PERIOD?", (iv) a generalized time interval entry in hours and minutes, and (v) a generalized confirmation of a displayed number--each as discussed above.

Adoption by pressing the "OK" key of the fourth-level question SOAKS CYCLES? causes a totally automated calculation to transpire. The calculated results are displayed as:

Disavowal is by use of the arrow keys, and is followed by user insertion of desired data. The user is in any case asked for the soak day by question "SOAK DAY?" Day of the week entry response to this question is conventional.

Adoption by pressing the "OK" key of the fourth-level question "SPECIAL STARTS?" is directed to entering data for lights, fountains, and other fixedtime events up to sixteen in number (of starts). Data that is enterable includes, for each start, includes the following:

At the end of each entry the questions "NO MORE/MORE" are positioned in the alternative to let the user choose to enter more information, or to exit to the next fourth-level question.

An affirmative, "OK" key, response to the final fourth-level question "OPTION SETUP OK?" causes an information-only screen (no keys are active) saying "WAIT . . . saving program" while the entered option data is saved. Thereafter continuation is made at the next first-level menu item, or "RUN SCHEDULE?".

Returning to the second level, an "OK" response to the second-level question "SEE/CHANGE PROGRAM?" causes the sequential display of the following five questions in the form of a menu:

At each of the "DURATIONS?", "START TIME?", "DAY CYCLES?" the displayed quantity is respectively the duration, start time, and cycles previously entered for a particular station. Repudiation of any or all of these quantities by use of the arrow keys permits the immediate entry of new data in the conventional manner.

An "OK" response to the third-level question "EXTRA OPTIONS?" causes the fourth level to be entered at this point in the hierarchy. At this fourth-level point the controller cycles through fourth-level questions:

Data entry in accordance with each question may be entered by pressing the "OK" key, or a next question may be sequenced by pressing the arrow keys. Exit from this fourth level is accomplished by pressing the "OK" key to the question "OPTION SETUP OK?".

Adaptation of any of the fourth-level questions "AUTO-SPLITS?", "EXCLUDED PERIOD?", "SYRINGE CYCLES?", and/or "SPECIAL STARTS?", results in the further sequencing through the following fifth-level questions: to see. Any existent data within the computer for the corresponding quantity will then be displayed. An arrow response to the "SEE/CHANGE?" question will allow entry of data changing the display quantity in a conventional data entry manner. The "SEE/CHANGE?" sequence steps through all stations, including those for which no data has been previously entered.

The "KEEP SAME?" fifth-level question applies to all stations in aggregate. If this question is responded to by an "OK" response then all data for all stations remains as previously set. Depression of an arrow key cycles to one of the remaining two questions upon the same fifth level.

An "OK" response to the "CANCEL?" question indicates that the corresponding splits, period, cycles, or starts, as the case may be, should be cancelled. Alternatively, an "OK" response to the "ADD?" question causes a branch back to the appropriate third-level data entry section as respectively regards auto-splits, excluded period, syringe cycles, soak cycles, or special starts. An "OK" response to the "ADD?" is thus a means, accomplished during the program review cycle ("SEE/CHANGE PROGRAM?"), permit expeditious return to an appropriate data entry area if program changes are desired to be made.

At the conclusion of all adoptions and/or changes that are desired to be made due to program review under the second-level question "SEE/CHANGE PROGRAM?", an "OK" response is made to the third-level question "NOTHING?". At this time the controller will display the information-only message (no keys are active) "WAIT . . . saving program". At this time any revised information is saved. The controller thereafter continues at the next first-level menu item, or RUN SCHEDULE?".

Continuing at the highest, first, level, the second of the controller's six positive questions is "RUN SCHEDULE?". If this question is adopted by an "OK" response then the controller will (i) display a particular piece of data, and accept changes thereto, and (ii) ask further second-level questions.

At the onset, the controller will display the current time in hours, minutes, day of week, month, date, and year--accompanied by a blinking question mark. An "OK" response to this display will cause sequencing on this second level to one of the two additional activities thereat, both in the form of options. An arrow key response to the display time and blinking question mark will cause a first one of the seven fields thereof to blink. If it is desired to change this field then data entry to do so may be accomplished by conventional use of the arrow keys.

If, however, the content of this particular field is satisfactory then the next field may be sequenced for change by depressing the "OK" key. At such time as all fields have been sequenced through the entire seven-field current date will again be displayed with the blinking question mark.

Continuing at the second level, an "OK" response to the question "AUTOMATIC RUN?" permits entry into options for initiating automated activity, or running, of the irrigation controller. At this point in the second hierarichal level, the irrigation controller will sequence through the following two questions:

As with the "SKIP"/"USE" options available under first-level question "ENTER NEW PROGRAM?", the blinking "SKIP" message is always displayed first. Use of either arrow key causes the message to cycle to "USE". One alternative, either "SKIP" or "USE" must be adopted by depressing the "OK" key.

An "OK" response to the second-level question "USE Run Options?" causes the controller to sequence through the following three fourth-level questions:

An "OK" response to "RESUME LAST run?" will cause resumption of running at the same day number as when the previous running stopped. It will additionally cause that further questions upon this fourth-level are skipped, and the controller will proceed to the next second-level "READY to run now?/NOT READY to run now?" questions.

An arrow response to the question "RESUME LAST run?" will cause the question "START NEW run?" to be displayed. An "OK" response to this question starts the run at day number one, and causes the controller to sequence to a next, fifth-level, menu. The questions on this fifth-level menu are as follows:

Data in response to each of these questions may be entered by depressing the "OK" key. In the case of an "OK" response to the "WATER BUDGETS?" question, the further questions "MONTHLY?" followed by "YEARLY" will be asked. The "MONTHLY?" question may be responded to by conventionally entering a number which represents the percent of a normal months budget which is to be used. The question "YEARLY?" may likewise be responded to by entering a number which represents the percentage of the overall watering budget that is to be used.

The next fifth-level question "SET RAIN DELAY?" may be responded to by a conventional data entry of a period from 0 to 90 days. The final fifth-level question at this point in the hierarchy, "TURN STNS OFF/ON?" may be responded to so as to set (by the "OK" key) or not set (by the arrow keys) each individual station either to respectively run or not to run.

At such time as fourth-level questions "RESUME LAST run?" and "START NEW run?" have been responded to, a final fourth-level question at this point in the hierarchy asks "ALL OPTIONS OK?". An "OK" response to this question indicates that the user is done with setting the run resumption and start options, and that reversion to the second level of the hierarchy is desired. Conversely, an arrow key response to this question will continue cycling within the fourth level of the hierarchy.

If a reversion is made to the third level of the hierarchy, and if the "READY to run now?" question is adopted by use of the "OK" key, the controller will display the information-only message "Now Watering: Remove LEIT Key!" as the terminal message of operator communication. The acronym "LEIT" stands for Light Energized Irrigation Technology, and refers to the irrigation controller in accordance with the present invention.

The function of the man-machine interface has been explained, to this point, sufficiently so as to permit recognition of the control and data entry that transpires across the interface, and of the manner of context switching that the interface undergoes in response to user entries. The equivalent use of the interface to realize still other function so irrigation control may be understood by further reference to Table 1, FIG. 7, and particularly to FIG. 8.

The block diagram of FIG. 4 shows the overall architecture of the first, U1, Application Specific Integrated Circuit (ASIC) used within the preferred embodiment of the irrigation controller using a manmachine interface in accordance with the present invention. The detail function of ASIC U1 is essentially unimportant for the purposes of the present invention, and is included within this specification only for purposes of completeness. The photovoltaic module (PVM, shown in FIG. 3a), SUPERCAPS C1 and C2 (shown in FIG. 3a) and ASIC U1 (shown in FIG. 3a) may be considered to simply be the implementation of a special form of a light-energized power supply. The general implementation of an a.c. or battery source power supply is, of course, routine in the electrical arts.

The U1 ASIC device is used to generate a 5 volt power supply using power from a photovoltaic modult or battery. Power is stored by charging very large supercapacitors ("SUPERCAPS") to 10.8 volts. The stored energy is then used for operation during dark periods. Because the energy stored in the SUPERCAPS=1/2 CV.sub.cap.sup.2, the run time duration of the controller during conditions of darkness is greatly affected by how closely the maximum charge voltage can be brought to the maximum tolerable voltage for the SUPERCAP components. Therefore, to increase the dark run time, the "SUPERCAPS" are very carefully monitored, so that they may be charged to a maximum value without being over-charged.

The U1 ASIC device is designed to use minimal power while providing five (5) functions:

First, it monitors SUPERCAP voltages and shunts the charging current if they are over-charged. The monitoring holds this voltage to within +/- 1.75%.

Second, it provides a 5 volt +/-2.5%, 0-65 mA output voltage to power other electronics.

Third, it provides status signals indicating the condition of the power supply.

Fourth, it provides a 2 kHz, 30 us pulse for use as a time base.

Fifth, it steps up a 9 volt battery to 17 volts to charge the SUPERCAPS and provide current during programming of other electronics. (Power consumption is less of a concern in this mode.)

Sampling capacitors are used to monitor the various capacitor and power supply voltages, allowing the use of only one comparator to conserve current. CrSi 100 k.OMEGA./resistors are used to minimize analog currents.

The voltage reference is trimmed using on-chip metal fuses.

There are 3 potential `most positive` voltages and two potential `most negative` voltages, making substrate connections difficult. This is handled by using bipolar junction isolation that employs the isolated n- regions as separate CMOS substrates. This allows the CMOS circuitry to operate from several supplies, any one of which could be at the highest potential at different times.

The logic generally runs from VSSI (OV) to VDD2 (0-5 V), level shifting where required. Analog references run from VSS1 to VDD1 (0-11 V). Switching regulator components run from VSS2 (-0.7 to +5.5 V) to VBAT (0 to 15 V). The upper shunt transistor is connected to a voltage which can range from 0 to VDD1 +0.7 V.

The VREF1 circuit X4 is a voltage reference for monitoring supercaps, system low, and system very low. The circuit requires no opamps, reducing offset error. NMOS transistors at collectors of non bandgap transistors are used to eliminate early voltage effects. The circuit has a buffered output which multiplies the bandgap voltage and is trimmed to 1.50 volts. This trimming is with on-chip metal fuses. The trim range is approximately 1.5 +/-0.1 volts with minimum steps of 3 mV. An extra +/-1 LSB is provided in case original trim is incorrect. The circuit temperature coefficient is 60 ppm/.degree. C. typical, 150 ppm/.degree. C. worst case.

The IBIAS & XTAL BIAS circuit Xl generates 20 nA bias currents for other cells, and 100nA bias (voltage) for xtal oscillator. It generates buffered 2 Vth voltage "VLOW" used to run the xtal oscillator and high-order dividers at low current. CrSi and p-resistors are combined to match TC of Vbe. The bias varies approximately +/- 28% over all parameters.

The XTAL & 2 kHz DIVIDERS circuit X2 generates a clock for capacitor switch sequencing. It uses a low current oscillator (CASC1 from TCJ) running from the second Vth supply voltage called VLOW. Internal trim capacitors are added to the crystal pins and are metal mask trimmable. Dividers to 2 kHz run from VLOW, then are level shifted to VSS1, VDD2 (0 to 5 V). This avoids level shifting at 32 kHz, conserving current.

Circuit input PULSE receives a 2 kHz 30 microsecond pulse used for on and off chip timing. Circuit input NSTROBE receives a 2 kHz, 15 us negative pulse occurring 60 us after PULSE and is used for on chip timing. The level shifters use approx. 30 nA each at 2 kHz.

The SS DECODE circuit X3 is clocked by input PULSE. One-shot is used to effectively generate a non-overlapped clock for the switch output signals. All switch signals are disabled (by inputs E and NE) for 0.6 to 4 us after each clock.

Switch sequencing samples the upper supercap, lower supercap, system low, and system very low in that order. Inputs NSC1, NSC2, NSSL, NSSVL define which voltage is being sampled. Each voltage is sampled once every 7.8 ms.

Input NCMP.sub.-- CLK is the comparator clock. Input NCMP.sub.-- ON powers down the comparator during unused periods.

The CAP ARRAY & SWITCHES circuit X5 contains sampling capacitors that are basically unit sizes. Due to the variety of voltages sampled, fractions of units are required. Poly etch tolerance can cause approximately 0.2% ratio error.

Inputs S1, S2, S3, S8 and S9 require signals level shifted above VSS2 (the normal logic level is VSS1, VDD2). Inputs S1, S2, S3, S8, S9 must save bodies tied to VSS1 & VDD1. All other switches may be tied to VSS1, VDD2. Note that this includes p-channel bodies, since they are isolated from the substrate in this process.

Sampling occurs such that the node OUT should remain at the reference voltage level if the sampled voltage is at its exact trip point. This avoids parasitic capacitance effects at this high-impedance node.

100 mV of hysteresis is added to the SL and SVL tests by switching between two slightly different capacitor values.

A simplified electrical schematic of the CAP ARRAY & SWITCHES circuit X5 illustrating its function is shown in FIG. 5a. In operation, V.sub.OUT =V.sub.REF if V.sub.SAMPLE .multidot.C1=V.sub.REF .multidot.C2.

The SCOMP circuit X7 compares output from the capacitor array to the reference voltage. It is inherently offset compensated. It's response time is less than 25 us.

A simplified electrical schematic of the SCOMP circuit X7 illustrating its function is shown in FIG. 5b. Phase 1 shorts the n-channel so that its gate voltage moves to the voltage where it carries exactly the current source current. The input capacitor is shorted to VREF and stores the difference between this gate voltage and VREF. Phase 2 opens the n-channel and connects the capacitor to the input voltage. If the input voltage is different from the reference, the gate is forced higher or lower, pulling the output of the current source down or allowing the current source to pull up.

The COMP DL circuit X11 stores the output of the comparator in the latch corresponding to the voltage being tested. It is clocked by input NSTROBE.

The WT TIMER circuit X12 is used as a "timed hysteresis" when the SUPERCAP voltages are sampled.

When near the trip voltage, the capacitors will tend to be above the trip voltage when charging, and immediately fall below the trip voltage when the charging current is shunted away. This is due to approximately 7.OMEGA. internal resistance in the SUPERCAPS.

The SUPERCAPS are sampled every 7.8 ms, and under the above conditions would alternate charging/discharging at a 50% cycle. A typical charge current of 20 mA would average 10 mA, while a typical load current is 12 mA continuous, resulting in a net energy loss. This would result in the capacitor charging to less than its maximum value by the internal I-R drop.

To avoid this situation, the comparator data latch is disabled for 3.times.7.8 ms after it comes out of a shunt mode. This results in a 3:1 charge to shunt ratio, ensuring that the net charge current is positive.

The SHUNT TRANSISTORS X10 shunt up to 70 mA away from the SUPERCAP when the maixmum voltage is exceeded. The SHUNT TRANSISTORS X10 have a resistance of approximately 3.5 .OMEGA..

The SWITCHING REGULATOR circuit X9 provides 17 volts from a 9 volt battery. The inductor shorting transistor of the circuit is off-chip (the IC is not required to handle the 17 volts).

Output NBP signals the VDD2, VSS1 logic when a battery is attached to the BAT, VSS2 terminals.

A simplified electrical schematic of a step-up DC-to-DC Converter circuit used in SWITCHING REGULATOR circuit X9 and illustrating its function is shown in FIG. 5c. When switch S is closed the battery voltage is applied across the inductor L. Charging current flows through the inductor, building up a magnetic field, increasing as the switch is held closed. While the switch is closed, the diode D is reverse biased (open circuit) and current is supplied to the load by the capacitor C. Until the switch is opened the inductor current will increase linearly to a maximum value determined by the battery voltage, inductor value, and the amount of time the switch is held closed (I.sub.PEAK =V.sub.BAT /L.times.T.sub.ON). When the switch is opened, the magnetic field collapses, and the energy stored in the magnetic field is converted into a discharge current which flows through the inductor in the same direction as the charging current. Because there is no path for current to flow through the switch, the current must flow through the diode to supply the load and charge the output capacitor.

If the switch is opened and closed repeatedly, at a rate much greater than the time constant of the output RC, then a constant DC voltage will be produced at the output.

The internal bias of SWITCHING REGULATOR circuit X9 is used only for biasing switching regulator components. The bias is provided by a Standard 5 uA bias cell type A54020. Its absolute value is not critical.

The SWITCHING REGULATOR circuit X9 has an internal reference for monitoring switching regulator output voltage. The reference is provided by a standard cell reference type A53000 that is modified to use CrSi.

The reference circuit is chosen to keep non collectors at positive voltage. (Switching regulator can have voltages below the substrate voltage VSS1.)

The value and temperature coefficient of the circuit are not critical, and trim is not required.

The SWITCHING REGULATOR circuit X9 has an internal clock for switching the regulator at approx. 25 kHz. The clock is divided from 50 kHz to give a 50% duty cycle. It employs a standard cell reference type A55010 that is modified for CrSi. An approximate 150 k.OMEGA. external resistor is required.

The SWITCHING REGULATOR circuit X9 has a comparator that uses positive feedback for an improved response time of 3.5 us maximum.

The 5 V REGULATOR circuit X6 provides a 5 volt +/-2.5% regulated output for external electronics as well as VDD2 for internal logic. An external NPN is used to avoid thermal effects on the IC.

The LOW RESET circuit X8 resets the entire UI ASIC. The power supply can (under various light conditions) take minutes to hours for power up, which eliminates normal power-on-reset circuits. This circuit must ensure that all outputs are valid until the analog circuits are operational.

The output holds all latches in reset until the bias, reference, and regulator circuits are all running at levels acceptable for operation.

The U1 ASIC is suitably implemented in BIPOLAR-CMOS technology available from several semiconductor foundaries. It is typically implemented in the BI-CMOS process of Micro-Rel Division of Medtronic, Inc., 2343 W. 10th Place, Tempe, Ariz. 85281.

The block diagram of FIG. 6, consisting of FIG. 6a through FIG. 6f, shows the overall architecture of the second, U2, Application Specific Integrated Circuit (ASIC) used within the preferred embodiment of the irrigation controller using a manmachine interface in accordance with the present invention.

The U2 ASIC device is concerned with calculation, command, and control. It is primarily digital in operation, and may be considered to be a specialized microprocessor with substantial analog as well as digital I/0 capabilities. The diagram of the U2 ASIC device shows the detailed interconnection of the various functional blocks.

The central microprocessor Y31 of the U2 ASIC device is a NCR 65CX02 macrocell. It employs an 8-bit datapath structure controlled by an internal programmable logic array (PLA) using 8-bit instructions and having a 16-bit addressing capability. Importantly, all circuitry internal to the microprocessor is completely static and complementary so that the clock signal may be frozen and only leakage current will be consumed. It has a clock speed of 455 KHz and a 2.2 microsecond cycle time.

The microprocessor Y31 executes the instruction repertoire of commercially available micorprocessor type 6502. The mnemonic codes for the instructions of this repertoire, such mnemonic codes as appear with the firmware program listing attached as Appendix A to this specification, are commonly recognized mnemonics, and a complete description of the microprocessor type 6502 instruction repertoire, are contained, among numerous other places, in the book "6502 Assembly Language Programming" by Lance A. Leventhal, published in 1979 by Osborne/McGraw Hill, 630 Bancroft Way, Berkeley, Calif. 94710. It will be recognized that, consonant with the modest computational requirements of an irrigation controller, the relatively simple 6502 microprocessor macrocell is not the sole type that could be employed, and that many microprocessors including types commonly incorporated in ASICs are suitable for use within the irrigation controller in accordance with the present invention.

The firmware instructions executed by micorprocessor Y31 occupy memory addresses in accordance with the following memory map table: 00-3F       I/O Parts 40-7FFF     RAM Memory U5 (shown in FIG. 3h) 8000-FFFF   ROM Memory U4 (shown in FIG. 3f) ______________________________________

The operand fields of the firmware instructions are interpretable in accordance with the following memory map table: 00         O      Microprocessor power off 01         O      RTC counter clear 02         O      A/D power, 1=on, 0=off 03         O      A/D interface, 1=enable, 0=disable 04         O      LCD power, 1=on, 0=off 05         O      LCD interface, 1=enable, 0=disable 06         O      Valve select byte bits 0-2 - valve #, + side bits 3-5 - valve #, - side bit 6 - polarity, 0=normal, 1=reversed 07 O      Valve enable, 1=on, 0=off 08         O      TIMER hi byte latch 09         O      TIMER lo byte latch 0A         O      TIMER control, 1=on, 0=off 0B         O      RTC, 1=10 seconds, 0=1 minute 0C         O      Serial clock 0D         O      TIMER load 0E         O      Write serial data out 0F         O      Serial output ready 10         I      RTC counter hi byte 11         I      RTC counter lo byte 12         I      Status register 1 bit 0 - 0=external battery present bit 1 - 1=watchdog timeout bit 2 - 0=system power low bit 3 - 0=system power very low bit 4 - 0=RTC pulse bit 5 - 1=battery low or caps charging bit 6 - 1=serial data link present bit 7 - 0=serial data link ready 13         I      Status register 2 bit 0 - Switch 1, 1=pressed STOP bit 1 - Switch 2 bit 2 - Switch 3 bit 3 - Switch 4 HELP bit 4 - Switch 5 NO bit 5 - Switch 6 OK bit 6 - bit 7 - 0=A/D end of conversion 14         I      Read serial data in 15         I      Read A/D converter 16         I      Load serial shift register 17         I      Clear input ready latch 18         I      LCD busy flag & address counter (RS=0) bit 7 - 1=busy O      LCD instruction register (RS=0) 19         I      LCD read data (RS=1) O      LCD write data (RS=1) 1A         O      LCD contrast select (0-7) 1B         O      Clear watchdog timer 1C         O      Clock RTC counter 1D         I/O    EEPROM 1E         O      Coil test drivers 1F         O      Sensor test drivers 20         O      Start A/D channel 0, sensor 1 21         O      Start A/D channel 1, sensor 2 22         O      Start A/D channel 2, sensor 3 23         O      Start A/D channel 3, sensor 4 24         O      Start A/D channel 4, sensor 5 25         O      Start A/D channel 5, sensor 6 26         O      Start A/D channel 6, sensor 7 27         O      Start A/D channel 7, sensor 8 28         O      Start A/D channel 8, valve 1 29         O      Start A/D channel 9, valve 2 2A         O      Start A/D channel 10, valve 3 2B         O      Start A/D channel 11, valve 4 2C         O      Start A/D channel 12, valve 5 2D         O      Start A/D channel 13, valve 6 2E         O      Start A/D channel 14, valve 7 2F         O      Start A/D channel 15, valve 8 30-3F 40-FF      Zero page variables, pointers, and tables 100-1FF    Stack 200-3FF    Program variables 8000       ROM start FFFA-FFFB  NMI vector FFFC-FFFD  RESET vector FFFE-FFFF  IRQ vector ______________________________________

The coil drivers Y20 work in pairs to supply relatively large bidirectional current pulses to operate electromagnetically actuated valves. Only one pair of coil drivers is active at a time, as specified by the contents of the data bus. Additionally, the output (coil) drivers have the capability to sink a regulated current for testing and programming purposes.

The timer Y26 consists of two 8-bit latches on the data bus and a 16-bit down counter which is clocked at 2 kHz. Loading of the counter and latches is under the control of the processor. When the counter reaches zero, a processor interrupt is generated.

The Analog-to-digital converter Y43 receives signals from external sensors and from the valves, a total of 16 channels in all, which are converted to digital information and placed on the data bus. The selection of the channel to be digitized is made on the basis of the contents of the address bus. The converted data is expressed as an eight-bit fraction. For the eight channels originating at the sensors and for the eight channels originating at the coils, this fraction is the ratio of the input voltage to the full power supply. All 16 ADC inputs may be pulled to ground through a poly resistor and an n-channel switch which together constitute a nominal 330 ohm resistance. The resistors associated with the eight channels originating at the sensors are enabled individually (as determined by the contents of the data bus) upon command of the processor. The performance specifications of the Analog-to-digital (A/D) Converter are as follows: a.     Resolution/Accuracy 8 bits .+-. one-half LSB for VIN = 1 (Vd) 8 bits .+-. one LSB for VIN = 1/2 (Vd) b.     Conversion Time ##STR1## depending upon whether the conversion is full scale or half scale. c.     Operating Current 3 mA maximum d.     Analog Reference Digital Supply Voltage (Vd) e.     Analog Inputs (Vin) Each input voltage is ratiometric with the digital supply voltage (Vd) where: Vin for full scale = 1/2 (Vd) for A/D channels 1 through 8 Vin for full scale = 1 (Vd) for A/D channels 9 through 16 ______________________________________

This clock/calendar Y22 provides several timing functions. It generates a 2 second timing tick at 10 second or 1 minute intervals.

It keeps watch on the status of the programmer battery by generating a "Battery Low" status bit if either of two "Supercap Shunt" signals are absent for more than 64 second during programming activity.

It counts up to 65535 ticks while the processor is in a low voltage shutdown mode so as to provide calendar memory. The calendar contents may be placed on the data bus.

It maintains a 128 second dead-man timer which can generate a hardware reset if the processor fails.

The switch register Y2 acts as an interface between six external configuration switches and the data bus. An additional input is the end-of-conversion signal from the analog-to-digital converter.

The status register Y3 makes the following internal flags available to the processor as data on the data bus: Battery Present, Dead-man timeout, System Low, System Very Low, Real Time Clock Tick, Battery Low, Serial Data Link Present, and External Ready.

The serial data link Y1 provides high speed two-way communication between the device and a remote data transceiver. Data is loaded or retrieved via the data bus under control of the processor. Transmission of serial data is also directly controlled by the processor.

These circuits Y23 provide handshaking between the processor and an external device (such as a serial data link) through the status register and data bus.

The wakeup circuit Y27, upon stimulation by either the Serial Data Link Present or the clock/calendar time-tic or the Battery Present signals, starts the main system oscillator and then after a 500 microsecond delay, removes the system reset. Upon stimulation by the System Very Low signal or by the processor, the wakeup circuit immediately causes the system to be reset. The dead-man timeout signal will cause a 30 microsecond reset pulse to occur at two second intervals until the processor resets it.

The main oscillator Y25 uses an external capacitor and a charge-discharge scheme to produce a high-speed clock for the processor. This oscillator can be shut down to conserve power. It will restart immediately upon command. The frequency of oscillations is determined by the size of the external capacitor. The relationship between capacitor size and frequency, as well as the frequency stability over changes in operating environment, may be tailored in consideration of the operational environment within which the irrigation controller is used.

The LCD interface Y29 consists of a latch on the data bus and the control circuitry needed to operate an external liquid crystal display and the DAC. The LCD interface can be configured to function as the 6502 Data I/O port. The interface is configured in this way only during a special test mode. Under processor control, a flip flop is set which alters the internal logic paths so that the LCD bus will be configured as a 6502 Data I/O port. This special test feature allows the 6502 to be tested independently of the peripheral logic.

The four bit digital-to-analog converter Y32 provides a voltage, as specified by the contents of the data bus, through the LCD interface for contrast control of the external liquid crystal display.

The performance specification of the DAC are as follows: a.    Resolution: 4 bits b.    Accuracy:  .+-. 1/2 LSB for all voltage steps c.    Vout =     n(0.147) where 0 .ltoreq. n .ltoreq. 15 d.    Io (min) = 500 uA sink for Vout = OV .+-. 50 mV e.    Vo (max) = .+-. 50 mV for Io = 500 uA for the DAC setting D3 = D2 = D1 = D0 = 0 ______________________________________

The address decoder circuit Y38 uniquely maps all internal functions into page zero of the processor's memory space. The decoder produces timing and control signals for these internal circuits as well as for reading and writing of external memory.

The power switch circuit Y28 controls the power for the external ROM and display as well as the internal analog functions in order to conserve power and to permit the irrigation controller to enter a "sleep" mode.

The resistor control circuit U42 permits reconfiguration of the sensor and coil interfaces to enable communication upon each of the A/D channel lines so that integrity of both valve coils and moisture elements may be self-tested. This is accomplished by selectively switching a low value resistor between the channel signal line and ground.

These pins operate in pairs, one pair at a time, when driving the coils of the electromagnetically actuated valves. One pin of the pair goes high while the other goes low in order to provide bidirectional current. Inactive coil driver pairs assume a high impedance state. When the coil is deenergized the driver circuitry must absorb the energy of the collapsing field. CD8-CD15 also function as analog inputs to the ADC. These pins have the additional capability of sinking a regulated current for testing and programming purposes.

These pins provide information from the coils and sensors whose integrity the processor must evaluate. ADC8-ADC15 are shared with the 8 valve lines CD8-CD15. ADC0-ADC7 are shared with the 8 sensor lines. All these 166 lines have the capability of sinking a regulated current for testing purposes.

An active low input indicates that the condition of the power supply is such that further operation will soon be impossible. The processor, upon receiving this signal, will immediately turn off all valves in anticipation of approaching shutdown.

An active low signal indicates that the condition of the power supply is such that further operation is impossible. Upon receiving this signal the processor will immediately go into hibernation. After approximately 100 milliseconds, a hardware system reset will occur independently of the processor.

If either of these signals persists in the high state for longer than 64 seconds, a Battery Low status will be generated.

An active low signal indicates that a battery is connected to the power supply so that the processor may run continuously.

Active high inputs with internal pulldowns go directly to the switch register.

The external RAM and ROM are addressed by these pins. A0 - A7 in conjunction with ALE also functions as D0 - D7.

The external RAM and ROM use these lines for transferring data to and from the device. The lower address bits are multiplexed with the data on these lines in conjunction with the ALE signal.

When this signal is high, data transfers may take on the D0-D7 pins. When this signal is low, these same pins are used as A0-A7 outputs.

This signal appears as one of the bits of the status register. RDYIN provides handshaking protocol from a distant serial data link. A low-to-high transition of this signal sets the Serial Data Link Present status bit low. The signal is provided with an internal pulldown.

This signal passes the contents of data bus bit zero out of the device under control of the processor to provide handshaking protocol to a distant serial data link.

This signal is used to enable the outputs of the external ROM onto the D0-D7 pins.

These bidirectional signals transfer data to and from the external liquid crystal display. They are provided with internal pulldowns.

This output signal enables the external liquid crystal display. This output signal can be made to exhibit high impedance with an internal pulldown.

This output signal informs the external LCD module that either data or command appears on the data inputs. This output signal can be made high impedance with an internal pulldown.

This output signal controls the direction of data flow to or from the external liquid crystal display. This output signal can be made to exhibit high impedance with an internal pulldown. Display

This analog output signal is used to control the display contrast.

When this signal is switched on it provides current from the device power input VDD. When it is switched off, it sinks current into the device power return VSS.

When this signal is switched on, it provides current from the device power input VDD. When it is switched off, it sinks current into the device power return VSS.

When this signal is switched on, it provides the device power input VDD. When it is switched off, it sinks current into the device power return VSS.

When driven by the device for outward data transmission, this signal alternatively assumes a low impedance high state and a low impedance low state. If the low state persists for more than 20 to 40 nanoseconds then the signal remains at a high impedance with an internal pulldown. In this last state, the pin may be driven by an external source for inward data transfer (reception). The clocks generated by this pin may have a rate of up to 32,000 Hertz. This pin may be loaded with up to 300 picofarads capacitance.

When driven by the device for outward data transmission, this signal assumes a low impedance state whenever the Serial Clock is high, and then, if the clock low state persists for more than 20 to 40 nanoseconds, a high impedance with an internal pulldown. In this last state, the pin may be driven by an external source for inward data transfer (reception). The data generated by this pin may have a rate of up to 32,000 bits per second. This pin may be loaded with up to 300 picofarads.

Provides a connection for a capacitor whose value determines the frequency of the Main Oscillator.

Indicates whether a memory read or memory write cycle is in progress.

This signal is high during the active portion of the processor's operation. When low, the processor is precharging its internal busses. This signal must logically combine with Read and the appropriate address decode to create the control signals to apply to external memory.

This signal is used in conjunction with READ and PH12 for external EEPROM operations.

This active-low signal indicates that the processor is shut down and may be used to initialize external circuitry to the correct state for processor startup.

This pin goes high when the address bus is in address area 0040H through 7FFFH inclusive.

5.2.30 VDD - Device positive supply.

5.2.31 VSS - Device negative supply.

The frequency is nominally 2 Khz with a 30 u second high-going pulse.

When SPSEL=1, the chip requires a 32 Khz time base on the CK input. When SPSEL=0, the chip requires a 2Khz time base on the CK input. Parameter      Symbol   Min      Max  Units ______________________________________ Power supply   VDD A    4.5      5.5  V All circuitry active ______________________________________ Power Supply  VDD  B  2.00  5.5  V Real time clock, interrupt, and battery low detection circuitry operative. All other circuits are at a static, defined logic level (therefore, not being clocked). Active Supply Current  Ia     6.0 mA VDD = 5.5v, 2Khz Real time clock running, main oscillator running, processor, ADC, LCD interface logic running (only), DAC running, coil drivers in high- impedance state, external interface circuitry to EEPROM, ROM and RAM is active, however, the active current of the EEPROM, ROM and RAM is not included. Quiescent Supply Current  Iq     1.5 uA VDD = 5.5v, Real time clock running, main oscillator stopped, processor stopped, coil drivers in high- impedance state, ADC, LCD, DAC are all powered off. External EEPROM and ROM are powered off. External RAM is at a static, defined logic level (therefore, not being clocked). The quiescent current of the RAM is not included in Iq. ______________________________________

Unless otherwise stated, the following characteristics apply over the applicable operating power supply range as specified above. All pins are protected against electrostatic discharge. Parameter    Symbol   Min       Max     Unit ______________________________________ Capacitance of Ci                 10      pF Inputs Capacitance of Co                 10      pF Outputs Capacitance of Ct                 10      pF Tristate Input Leakage Iil      -1        +1      uA' Current Tristate Leakage Itl      -1        +1      uA Current Passive Pulldown Ipd      -1        -30     uA Current (@ Vih = VDD)z Active Pulldown Irpd     -4        -12     mA Current (@ Vi = 2.5v) VA, VL, VP Output High  Voh      VDD-0.3   VDD+0.3 V Voltage Output Low   Vol      -0.3      +0.4    V Voltage Output High  Ioh      -6.0              mA Current (@ Voh = VDD-0.3V) Output Low   Iol      6.0               mA Current VLCD Output Voltage Volcd    0.0       2.2     V Range Output Current Ioled    +0.5              mA (@ Vol = 0.05V) Coil Driver Pins Input Voltage See ADC8 - ADC15 below Range Output Pair Drop Vdr      0.0       1.0     V (@ I = 45mA, Vdd = 4.5v) ADC0 - ADC15 Input resistance Rin      10Meg             Ohm Input Voltage Vina     -0.0      VDD     V Range C01, C02 Output High  Voh      0.5       VDD+0.3 V Voltage Output Low   Vol      -0.3      0.4     V Voltage Output High  Ioh      -4.0      -12.0   mA Current (@ Voh = 2.5V) Output Low   Iol      4.0               mA Current (@ Vol = 0.4V) All Other Pins Input High   Vih      2.0       VDD+0.3 V Voltage Input Low    Vil      -0.3      0.8     V Voltage Output High  Voh      VDD-0.5   VDD+0.3 V Voltage Output Low   Vol      -0.3      +0.4    V Voltage Output High  Ioh      -2.0              mA Current (@ Voh - VDD-0.5V) Output Low   Iol      4.0               mA Current (@ Vol = 4.0V) ______________________________________

The device is packaged in an 84-pin plastic leaded chip carrier. The package life exceeds 20 years.

The limits below represent the environmental limits to which the device will ordinarily be subjected. Rating          Value        Unit ______________________________________ Storage Temperature -40 to +85   deg C. Operating Temperature -10 to +70   deg C. Lead Temperature 250          deg C. (4 min soldering) Humidity        85/85        deg C./percents ______________________________________

The preferred embodiment of ASIC U2 is preferably implemented in the CMOS technology of NCR Corporation, Dayton, Ohio. This technology, and the design rules and standard cells therein, is discussed in the "NCR ASIC Data Book" for January 1987. The equivalent technologies of other manufacturers will be realized to be equally suitable. It will be understood that the irrigation system of FIG. 2 could also be implemented using standard integrated circuit and microprocessor components in combination with a control program corresponding to that of attachment A. Such a system could be used alternately to implement the present method.

Although the present invention has been taught in the context of electrical circuits that are fairly sophisticated for employing both a predominantly digital ASIC (ASIC U2), it should be understood that the functionality of the preferred embodiment of an interface in accordance with the present invention is readily realizable by diverse alternative designs. In particular, the core microprocessor of the preferred embodiment of the invention is 100% compatible with industry standard type 6502. All firmware appended to this specification will execute on a 6502 microprocessor, and is readily convertible to alternative microinstruction repertoires executing on alternative microprocessors. The circuits by which data is manually input to the microprocessor and displayed are, in the preferred embodiment of the invention, powered and sequenced to states of activity in a highly unique manner. Nonetheless, it will be recognized that alternative implementations of these circuits, particularly as consume higher power and/or operate at higher or continuous duty cycles, are readily realizable by a practitioner of the electrical design arts. Accordingly, the present invention should be considered in terms of the functions that it performs, and not solely in terms of any particular hardware embodiment for realizing these functions.

In accordance with these and other aspects and attributes of the present invention, the invention should be determined by the scope of the following claims, only, and not solely in accordance with those particular embodiments within which the invention has been taught. ##SPC2##

## Claims

1. A manually operable interface to a machine comprising: step-wise sequentially among a plurality of messages at each of a plurality of levels of the hierarchy; causing the display to step-wise sequentially display each of the plurality of messages at one level of the hierarchy in a first direction in response to each actuation; desired one of the plurality of messages at the one level of the hierarchy has been displayed for causing (i) an adoption and use of the currently displayed message by the machine and (ii) the display to display messages from another hierarchical level having a selected relationship to said currently displayed message in order to effect branching within the hierarchal tree of messages without ever leaving the hierarchal tree; and for causing the display to step-wise sequentially display each of the plurality of messages at one level of the hierarchy in a second direction in response to each actuation.

2. The interface according to claim 1 further comprising: to display a new message associated with a currently displayed message.

3. The interface according to claim 2 further comprising: display a plurality of instructional messages that (i) induce manual actuation of each of the first-direction sequencing switch, the adoption switch, the second-direction sequencing switch, and the help switch, and that (ii) require a particular one of these induced manual actuations to be performed in turn before the display will display a next sequential one of the plurality of instructional messages.

4. In a machine that interfaces to a man for alternative control and data entry having capable of accepting selected commands at each control level associated with the control level for effecting control of the machine, and an alternative related capable of accepting selected ones of an plurality of datums at each data entry level associated with the data entry level for effecting entry of data into the machine; an improved man/machine interface for controlling and entering data into the multi-stated multi-level hierarchical machine, the interface comprising: level of the control state, a one of the commands associated with this control level, one command at a time, and entry level of the data entry state, a one of the datums associated with the data entry level, one datum at a time; machine and at a selected control level of this control state, commands associated with this one control level in a first direction in an endless loop and the machine and at a selected data entry level of this data entry state, datums associated with this one data entry level in the first direction in an endless loop; adopt, in the control state of the machine, the currently displayed command, machine, the currently displayed datum, and predetermined relationship to the currently displayed command or datum; and sequentially display, (i) in the control state of the machine at a selected control level of this control state, commands associated with the selected control level stepwise in a second direction in an endless loop and, (ii) in the data entry state of the machine at some one data entry level of this data entry state, the currently displayed datum stepwise in a second direction in an endless loop of the datums associated with this one data entry level.

5. The interface according to claim 4 wherein the display comprises: which help messages is relevant to some selected ones of the commands and the datums, one help message at a time; and wherein the interface further comprises: is associated with, currently displayed command or datum.

6. The interface according to claim 4 in a machine further having of which is relevant to selected ones of the commands and the datums, and wherein the display comprises: help message at a time; and wherein the manually actuable first selection switch comprises: advance, in the help state of the machine, the currently displayed help message stepwise in a first direction.

7. The interface according to claim 4 in a machine further having of which is relevant to some selected or ones of the commands and the datums, the display comprises: help messages, each of which help messages is relevant to selected ones of the commands, the datums and the help messages themselves; wherein the manually actuable first selection switch comprises: advance, in the help state of the machine, the currently displayed help message stepwise in a first direction; and wherein the interface further comprises: message that is associated, in the control state of the machine at some one control level, with the currently displayed command and, in the data entry state of the machine at some one data entry level, with the currently displayed datum and, in the help state of the machine, with the currently displayed help message.

8. An interface to a machine for use by a man comprising: time, and for alternatively displaying each of a multiplicity of explanatory messages associated with the multiplicity of datums one message at a time; use a currently displayed one of the multiplicity of datums; next one of the multiplicity of datums; and the multiplicity of messages associated with a currently-displayed one of the multiplicity of datums; and for thereafter causing the display to automatically redisplay said currently-displayed one of the multiplicity of datums.

9. The interface according to claim 8 questions; questions are in the form of a multiplicity of explanations of the associated questions.

10. A manually operable interface to a machine comprising: organized in a hierarchal tree having a plurality of messages at each of a plurality of hierarchical levels, one message at a time from a plurality of messages at a selected hierarchical level in a continuous loop; in a first direction through the plurality of messages that at the one hierarchal level, one message at a time; actuation of the first stepping switch, for causing adoption and use by the machine of the currently displayed message and the display to advance to displaying further messages, one message at a time, at a next hierarchical level having a selected relationship to the one hierarchical level; and in a second direction, opposite to the first direction, through its currently displayed plurality of messages, one message at a time; actuation of the first stepping switch and the second stepping switch.

11. The interface according to claim 10 further comprising: and the second stepping switch and the adoption switch, for causing the display to display a message that is associated with the currently displayed message.

12. A man-machine interface comprising: and for alternatively displaying each of a multiplicity of messages associated with the previously displayed datum; selection and use of a currently displayed one of said multiplicity of datums; by said display of a next one of said multiplicity of datums; display of one of said multiplicity of messages corresponding to the previously displayed one of said multiplicity of datums, and for subsequently displaying said datum after actuation of said manually actuable selection switch.

13. The interface according to claim 12 and said datums and includes an explanation thereof.

14. An interface to a machine for use by a man comprising: a hierarchal tree having a plurality of datums at each of a plurality of levels between a root level and leaf level, one datum at a time, and (ii) for displaying, at other times to the multiplicity of datums, a multiplicity of messages that are associated with the multiplicity of datums, this displaying of a multiplicity of messages also being one at a time; display the plurality of datums that are upon a one hierarchal level in an endless loop, commencing at root level and proceeding step-wise one datum at a time; is displaying a one of the multiplicity of datums, (i) adoption and use by the machine of a currently displayed one of the multiplicity of datums, and (ii) the display to branch to displaying a plurality of datums that are upon a next hierarchal level to the hierarchal level of a the currently-displayed one of the plurality of datums; of the multiplicity of messages that is associated with a currently-displayed one of the multiplicity of datums, after which display an actuation of the second manually actuable switch will cause the display to return to redisplaying said currently-displayed one of the multiplicity of datums.

15. An interface to a machine for use by a man comprising: sequentially advance in its one-at-a-time displaying of the multiplicity of datums in a first direction; a currently-displayed one of the multiplicity of datums; and sequentially advance in its one-at-a-time displaying of the multiplicity of datums in a second direction.

16. The interface according to claim 15 a hierarchy having a plurality of datums upon a plurality of levels; the display to step-wise advance in a one-at-a-time displaying of a plurality of datums that are upon a single hierarchal level in an endless loop; and display to progress to displaying a plurality of datums that are upon a next hierarchal level to the hierarchal level of the currently-displayed one of the plurality of datums.

17. The interface according to claim 15 multiplicity of datums, a multiplicity of messages that are associated with the multiplicity of datums, this displaying of a multiplicity of messages also being one at a time; and wherein the interface further comprises: of the multiplicity of messages that is associated with a currently-displayed one of the multiplicity of datums, after which display actuations of the first and the third manually actuable switches will cause the display to return to redisplay said currently-displayed one of the multiplicity of datums.

18. An interface to a machine for use by a man comprising: other times a multiplicity of messages that are associated with the multiplicity of datums also one at a time; advance in its one-at-a-time displaying of the multiplicity of datums, or from a displayed one of the multiplicity of messages back to redisplaying of an associated one of the multiplicity of datums, as the case may be; use a currently-displayed one of the multiplicity of datums; and the multiplicity of messages that is associated with a currently displayed one of the multiplicity of datums.

19. The interface according to claim 18 of a multiplicity of questions, and at other times a multiplicity of messages each in the form of an explanation to an associated one of the multiplicity of questions.

20. The interface according to claim 18 organized in a hierarchy having a plurality of datums upon a plurality of levels; display to automatically advance in its one-at-a-time displaying among a plurality of datums that are upon a single hierarchal level in an endless loop; and display to progress to displaying a plurality of datums that are upon a next hierarchal level to the hierarchal level of the currently-displayed one of the plurality of datums.

21. A method of query-response programming of complex sequences comprising: questions, the hierarchy of questions consisting of a first plurality of questions at a first, root, level, with at least some of these first plurality of questions having an associated second plurality of questions, with some ones of these second plurality of questions having an associated third plurality of questions and so on, the complex sequences being entirely broken down into a hierarchal tree of questions ranging from broader questions at the root level to more specific questions of the leaf level; of questions to a human user/programmer, the user/programmer permissively adopting for each single question displayed one of the options of question will advance to the next successive question in the same hierarchal plurality, and so on in an endless loop while the premise or the article of the currently displayed question is not adopted; currently-displayed question is adopted, in which case IF the currently-displayed question is not of a leaf-level plurality of questions THEN progressing to a next associated plurality of questions and proceeding to the cyclically displaying of this plurality of questions ELSE IF the currently-displayed question is of a leaf level plurality of questions THEN returning to the cyclically displaying of the first plurality of questions; and in temporary display of a context sensitive help message explaining to the user/programmer the responses that are being elicited by the currently cyclically displayed plurality of questions and how the user/programmer may evoke these responses.

22. The method according to claim 21 wherein continuously performing a.) selecting an advance response causes not only that the displayed question will immediately cycle to the next successive question but that, the a.) selecting an advance response being continued, the displayed question will cycle to still another successive question at the expiration of a reduced latency time, this faster cycling thereafter being continued until, and unless, the a.) selecting an advanced response is ceased.

23. The method according to claim 21 wherein adoption of the user programmer of the displayed option b.) selecting an OK response results in the further step comprising: particular question/response adopted by act of the user/programmer's b.) selecting an OK response until the user/programmer adopts a one of the options of displayed confirmation message is adopted, in which case IF further questions/responses of the same plurality of questions/responses remain unanswered and are potentially adoptable THEN returning to the display of successive further ones of the same plurality of questions/responses ELSE IF no further questions/responses of the same plurality of questions/ responses remain unanswered and adoptable THEN returning to the cyclically displaying of the first plurality of questions/responses; and displayed confirmation message is not adopted, in which case the displayed question/response will ultimately return to that question/response for which, when previously displayed, the programmer/user did adopt the option b.) selecting an OK response.

24. A man-machine interface for manually controlling and entering data into a programmable machine, the interface comprising: available control options for the machine in loops, each containing a plurality of control options, and for separate times sequentially displaying a multiplicity of all available datum options one datum option at a time in a loop containing a plurality of datum options associated with a particular control option; the display to step-wise sequence in a first direction (1) its display of the multiplicity of control options, and (2) its display of the multiplicity of datum options, as a function that either (1) the loop of control options or (2) the loop of datum options is currently displayed; causing the display to step-wise sequence in a second direction (1) its display of the multiplicity of control options, and (2) its display of the multiplicity of datum options, as a function that either the (1) loop of control options or (2) the loop of data options is currently displayed; switch shifts back and forth between loops of pluralities of control options and pluralities of datum options; accept are displayed by the display in response to actuation of the sequencing switch and are adopted in response to actuation of the selection switch.

25. The man-machine interface according to claim 24 further comprising: help message that is associated with a currently-displayed one of the multiplicity of control options and the multiplicity of datum options, after which interruption the display returns, under control of the first-direction and the second-direction step sequencing switches to step-wise sequencing its display of the multiplicity of control options and the multiplicity of datum options.

26. The man-machine interface according to claim 24 questions.