Abstract: A programmed irrigation controller automatically computes durations for, schedules, and controls split irrigation cycles at up to eight watering stations. The controller is manually entered with high-level information regarding soil type, terrain, and irrigation system watering head type, and also with a total irrigation time, for each station. The maximum "on" time duration for each individual split irrigation cycle, and a minimum "off" time duration, are determined from the high-level information input by table lookup. The controller computes the number of irrigation cycles at each station as its total irrigation time divided by its maximum "on" time duration. The controller schedules composite irrigation cycles for all stations so that no station overwaters within a single irrigation cycle or upon successive irrigation cycles that are too closely time proximate. Exclusionary time-of-day intervals that specify when no watering will occur can be inserted within the schedules.

Abstract: A user interface, typically to an irrigation controller, prompts user responses by asking questions. The questions are hierarchally organized, preferably in a hierarchal tree having approximately three to six questions on each hierarchal level between root and leaves. All command and data input may be done with only an "OK" pushbutton switch, and with an additional ".uparw.", or ".dwnarw." pushbuttom switches. Each "OK" user response affirms the premise of a currently-displayed question, and advances the questioning to a related branch upon a next hierarchal level. The ".uparw." pushbutton is used to advance the questioning in a first direction. An optimal ".dwnarw.", or down arrow,pushbutton switch advances the presentation of successive questions in a second direction. An optional "HELP" switch invokes context-sensitive help messages.

Abstract: A user interface, typically to an irrigation controller, prompts user responses by continuously autoscrolling questions. The questions are hierarchally organized, preferably in a hierarchal tree having approximately three to six questions on each hierarchal level between root and leaves. All command and data input may be done with only an OK/YES pushbutton switch, switches. Each OK/YES user response affirms the premise fo a currently-displayed question, and advances the autoscrolled questioning to a related branch upon a next hierarchal level. The NO pushbutton is never required to advance the questioning which is always autoscrolled, but instead serves, while depressed, to accelerate the autoscrolling of successive questions. A HELP response invokes context-sensitive help messages. A STOP response causes reversion in the hierarchy of questioning toward the root level, but does not stop the autoscrolling of questions.