Digital Radio Transceiver Programmer With Advanced User Interface

This invention relates to digital radio frequency (RF) transceivers, and more particularly to programmer devices for programming the "personality" of a digital RF portable or mobile RF transceiver. Still more particularly, the present invention relates to a computer user interface for customizing the "personality PROM" (programmable read only memory) programming of a digitally controlled RF trasceiver.

The subject application is tangentially related to following commonly assigned copending applications: Ser. No. 085,490 of Dissoway et al. entitled "Mobile Radio Interface" (Attorney Docket No. 46-80; Client Reference No. 45-MR-549(filed Aug. 14, 1987.

Long ago, virtually all of the features, options and operating characteristics of mobile and portable radio transceivers were determined by hard-wired components. Even operating frequencies were typically controlled by plug-in quartz crystals (in part because that was at one time the only practical way to provide the frequency stability required).

While older radio transceivers required additional or modified circuitry or components to perform certain functions (e.g., channel scanning, tone activated squelch, DTMF dialing, and the like), modern digital microprocessor-controlled transceivers are capable of performing such functions under software control with little or no additional circuitry. In fact, in many cases the only customizing required to adapt a radio transceiver to the specific requirements of a particular radio user is to load "personality" defining digital data into an electrically programmable non-volatile memory internal to the radio transceiver.

Digital microprocessor controlled radio communications devices are generally known, of course. The following (by no means exhaustive) listing of prior issued patents may be generally relevant to the state of the art of so-called "digital radios":

U.S. Pat. No. 4,378,551--Drapac

U.S. Pat. No. 4,392,135--Ohyagi

U.S. Pat. No. 4,525,865--Mears

U.S. Pat. No. 4,247,951--Hattori et al.

U.S. Pat. No. 4,254,504--Lewis et al.

U.S. Pat. No. 4,510,623--Bonneau et al.

U.S. Pat. No. 4,688,261--Killoway et al.

U.S. Pat. No. 4,618,997--Imazeki et al.

Such reference teach controlling transceiver functions and other transceiver operating parameters (e.g., operating frequencies) in response to digital signals stored in a "personality PROM" memory device internal to the radio. For example, specific frequency data can be stored in a memory device to specify corresponding transceiver operating channels. Tone decoding, DTMF encoding, scanning and other parameters can similarly be stored in the same memory device and these parameters can, in conjunction with control algorithms performed by the microprocessor under program control software, provide advance squelch control functions, tone signalling functions, and other advanced functions.

In the past, digital mobile and portable transceivers were preprogrammed at time of memory device (PROM) preprogrammed with the specific set of RF frequencies and other "personality" information. Thus, replacement of the integrated circuit PROM was at one time required to change the operating characteristics of the transceiver. However, to provide increased flexibility and permit transceivers to be reprogrammed more easily in the field (e.g., as user or system requirements change or a particular transceiver is issued to a different user), most modern digital transceivers have been provided with a connector via which programming data produced by an external source (e.g., a dedicated programmer device (an be applied to the transceiver. Programming may be accomplished by connecting a cable between the transceiver and the dedicated programming device and loading frequency allocation tables (and other information) from the programmer into the internal non-volatile "personality PROM" memory device within the transceiver. The transceiver microprocessor (or other component associated with the internal personality PROM) automatically loads the programming data appearing on the connector into appropriate locations in the personality PROM. This newly loaded information is used by the transceiver microprocessor in conjunction with stored program control instructions to control the transceiver. See, for example, commonly assigned U.S. Pat. No. 4,525,865 to Mears (1985) and commonly assigned application Ser. No. 06/910,353 of Flynn et al. filed Sept. 22, 1986 which issued as U.S. Pat. No. 4,843,588 on June 27, 1989 as two examples of methods for programming radio transceiver personality PROMs.

In the past, dedicated special purpose hardware programming devices were typically required to generate programming information and load the programming information into the radios. With the proliferation of personal computers (an in particular, the IBM PC and compatibles), however, some leading manufacturers of mobile and portable digital radios have provided software and associated interface kits which permit a user to program his radio via the ubiquitous RS-232C serial output port of a personal computer. Thus, users for whom the purchase of a specialized dedicated programming system was not cost effective in the past may now program their radios using the same personal computer they use for accounting and word processing functions.

General Electric Company for example provides a conventional Serial Programming Interface Module Model TQ-3310 which connects to the RS-232C serial output port of a personal computer via a serial output cable and connects to a radio transceiver programming connector via a Mobile Programming Cable (e.g., model no. TQ-3314). Using these components, data stored in the transceiver personality PROM can be read into a personal computer disk file and displayed on the personal computer display; and data stored in a personal compputer disk file can be downloaded into the transceiver personality PROM. Motorola, Inc. of Schaumburg, Ill., for example, sells a "level shifter" interface unit and associated cables which permits a personal computer to program Motorola digital radio transceivers. See, for example, the following publications relating to programming digital radios using a personal computer:

Programming Manual for M-PD 16.sup.Plus Personal Radio (General Electric Col);

GE Mobile Communications PC Programming MCS Programming Guide, Model TQ3317 V.10 (General Electric Company, April 1988);

"SABER Series Handle--talkie Portable Radios Field Programmer User's Guide, No. 68P81044C65-0 (Motorola Corp. 1987); and

SMARTNET Standalone Field Programmer Model T5124A Programming Information Guide, Manual No. 68P81117E11 (Motorola Corp. 1985).

While the actual process of downloading a file from a personal computer or other computing device into the personality PROM of a digital radio transceiver is relatively easy and straightforward, a much more challenging problem is to provide a user interface which is sufficiently flexible to allow the user to easily specify the information to be downloaded and to easily perform other tasks related to the programming process. Not all persons involved in programming or reprogramming radio transceivers are skilled computer programmers. Many such people may be radio hardware specialists with little or no computer background, and others may not have much technical skill in any area. Besides, a programmer user interface which is so complex and unwieldy that it cannot be operated by anyone other than a skilled computer programmer would be extremely difficult and inefficient to use.

It would be highly desirable to provide a menu driven digital radio transceiver programmer user interface which is highly "user friendly" and easy to use; provides sufficient flexibility to allow the user to perform radio programming tasks as well as other tasks related to radio programming; and actually assists the user in performing radio programming and other tasks related to radio programming; and actually assists the user in performing radio programming tasks while helping to prevent errors. Such an advanced radio programmer user interface would allow radios to be programmed even by those who are not technically skilled, and would help to make the task of programming radios far more efficient and less time consuming.

The present invention provides method and apparatus for programming digital radio transceivers which defines an advance user interface with the following non-limiting advantageous features (and additional features as well):

A non-intimidating set of display formats that are easily understood by the user;

A user environment that frees the user from ever having to read a manual;

An interface that is comfortable for both the novice and the experienced computer user;

Easy maneuverability between display formats and easy access to task selections;

An interface which places the user in control and reassures the user that he is in fact in control;

Uniformity in operative key function assignments so that the same keys are used to perform similar tasks throughout the interface;

Informative and aesthetically balanced screen formats including a title section, a data/text section, and a navigational key assignment legend section;

Use of partial screen "pop-up" display formats overlying already displayed full screen display formats to display messages and additional selections related to a displayed full screen display format;

Screen and field type help text provided throughout the interface whenever the user depresses a certain key;

Individual Help text files stored in ASCII format for each help text call;

A hierarchial arrangement of display formats wherein each format includes a tree level indicator to help the user easily determine "where he is" in the hierarchy;

Helpful user text prompts which change as different tasks become available to assist the user in making task selections;

For radio bandsplit and other function selections that provide user selection from a limited predefined set of valid values, display of a list of different options so the user merely selects from the displayed options (rather than requiring the user to key in his selection);

Display of error messages in pop-up window overlay format at the same location on the display throughout the interface while preserving the information "beneath" the error message window; and

A main display format providing a listing of all "personality" files previously created and allowing the user to select one of the personalities for modification, downloading into a radio, or other tasks by depressing cursor or other navigational keys.

These and other features and advantages of the present invention will be better and more completely understood by referring to the following detailed description in connection with the appended sheets of drawings, in which:

FIG. 1 is a schematic block diagram of the presently preferred exemplary embodiment of a digital radio transceiver programming system in accordance with the present invention;

FIG. 1A is a simplified schematic diagram of some of the structures within the personal computer and the radio transceiver shown in FIG. 1 which are involved in transceiver programming;

FIGS. 2 and 3 are schematic illustrations of the hierarchial menu structure provided by the FIG. 1 preferred embodiment;

FIGS. 4-15 are schematic high-level flowcharts of exemplary program control steps performed by the FIG. 1 embodiment;

FIGS. 16-18 are schematic diagrams of exemplary data structures used in the preferred embodiment to define display formats; and

FIGS. 19-31 are flowcharts of exemplary program control steps performed by the preferred embodiment to manipulate the FIG. 16 data structures.

FIGS. 32 through 68 illustrate exemplary screen displays shown in the preferred embodiment.

FIG. 1 is a schematic illustration of a presently preferred exemplary embodiment of a radio transceiver programming system 50 in accordance with the present invention.

System 50 includes a personal computer 52 with associated keyboard 54 and mass storage device 56, a display 58, and a digital radio frequency communications device 60 (hereinafter "radio") to be programmed. In the preferred embodiment, radio 60 might comprise a conventional handheld portable radio 60A and/or a conventional handheld portable radio 60B (either of which may be temporarily connected to programming system 50). Personal computer 52 in the preferred embodiment comprises a conventional IBM personal computer or compatible, and display 58 in the preferred embodiment comprises a standard conventional CRT video display.

FIG. 1A is a more detailed schematic diagram of portions of system 50. Conventional radio 60 includes a serial data connector 62 which is capable of being connected to the standard RS-232C personal computer serial port connector 64 via a cable 66 (a standard serial programming interface module such as GE part no. 19D438367G1 or the like may be connected between connectors 62, 64 as required to shift signal levels, convert between protocols, or the like). Conventional radio 60 may include a bidirectional data buffer/trasceiver 68 (e.g., a UART or the like) which communicates a serial data stream between the connector 62 and radio microprocessor 70. Microprocessor 70 in turn is connected to a non-volatile memory 72 (e.g., an EEPROM) storing "personality defining" information.

The personality information stored in EEPROM 72 controls the manner in which radio 60 operates in response to user inputs. For example, memory 72 in the preferred embodiment stores among many other conventional parameters a frequency/channel allocation table; radio scan options (e.g., whether scanning is enabled, hang time, and a parameter controlling whether the transceiver resumes scanning after transmitting on a priority channel); miscellaneous radio options (e.g., serial number, whether data is to be inverted before being transmitted, whether the operator can select power output levels from the keyboard, predetermined minimum power output, whether transmit mode is inhibited when transmit on a busy channel is attempted, etc.); T-99 data and/or digital voice guard mode data selection; and the like. Radio microprocessor 70 reads this personality defining information from EEPROM 72 and controls radio transmitter section 74 and radio receiver section 76 in a conventional manner in accordance with this personality defining information. For example, radio microprocessor 70 controls the synthesized RF operating frequencies for transmitter section 74 and receiver section 76 in accordance with stored frequency information (as indexed by operator inputted channel selections), controls transmitter output power in accordance with stored parameters, etc.--all in a conventional manner.

Personal computer 52 in the preferred embodiment also includes a microprocessor 78 communicating with serial output port 64 via a conventional UART 80 or the like. As is well known, personal computer microprocessor 78 is capable of transmitting serial data (using standard protocols) for loading into radio EEPROM 72 via UART 80, serial port 64, cable (and associated interface module) 66, connector 62, UART 68 and radio microprocessor 70; and is also capable of reading information stored in radio EEPROM 72 via the same path. While radio 60 in the preferred embodiment provides cooperative program control steps performed by radio microprocessor 70 to read from and write to radio EEPROM 72, in some applications it might be desirable to provide direct read/write access to the radio EEPROM via programming connector 62. Both such arrangements are known to those skilled in this art.

The conventional architecture for personal computer 52 shown in FIG. 1A is considerably simplified for clarity. Briefly, in the preferred embodiment personal computer microprocessor 78 executes program control instructions from RAM 82 (these instructions being initially stored in a program control instruction digital data module 84 on mass storage device 56 and loaded into the RAM as needed). Mass storage device 56 may also store one or more "personality files" 86 corresponding to preprogrammed parameters for particular radios. Briefly, such "personality files" 86 in the preferred embodiment contain both information for downloading into the EEPROM 72 of a radio 60 as well as additional information (e.g., comments) used by personal computer microprocessor 78 to facilitate processing and selection of radio personalities by a user (but not necessarily downloaded into a radio EEPROM).

These personality flies 86 can be created "from scratch" using the program control module instructions 84, or can be obtained by uploading the contents of radio EEPROM 72. Thus, two basic modes of operation are possible in system 50: a radio 60 can be programmed or reprogrammed by creating a new personality file 86 on personal computer 52 and downloading the new file into the radio EEPROM 72; or the programming of an already programmed radio can be modified by uploading the radio EEPROM contents to the personal computer (e.g., to create a personality file on mass storage device 56), modifying the uploaded data, and downloading the modified data back into the radio EEPROM to replace the initial EEPROM data. As will be understood, it is also possible to program a new radio 60 to have behavior which is identical to that of an already programmed radio by simply uploading personality data from the already programmed radio and downloading the same data without change into the new radio.

The processes used in the preferred embodiment for uploading data from the radio 60 to the personal computer 52 and downloading data from the personal computer to the radio are conventional. However, the steps performed by the personal computer 52 to permit a user to easily create and/or modify a personality file and to perform other associated tasks are new. Briefly, system 50 presents the user of personal computer 52 with a flexible and advanced user interface (defined by a hierarchial tree structure of menus, windows and other display formats shown in FIGS. 2-3 and controlled by the exemplary program control steps shown in FIGS. 4-15). This user interface presents the user with opportunities to select tasks to be performed, these tasks resulting in the proper programming of radios 60.

In the preferred embodiment, system 50 minimizes user mistakes and guides the user in making task selections by displaying, on display 58, display formats which prompt the user for selections. The user interacts with system 50 in the preferred embodiment by depressing so-called "operational keys" on keyboard 54 as will be explained.

The following is a description of some of the general concepts ("design philosophy") used in accordance with the presently referred exemplary embodiment of the present invention for the format of the screen display formats and the assignment of user operable command and navigation keys.

This interface divides the screen into three distinct sections: the title, the work area and the active function keys; refer to FIG. 32.

The screen title is used to present four items to the user: the program name, the software version number, the current function and the tree level indicator. The program name, located in the center of the title area, is used to provide the correlation between the PC programmer and the radio in which it programs. To the immediate right of the program name is the software version number. This version number is used to identify a particular release of the software i.e.: 1.0, 1.2 etc. The current function is displayed to the left of the program name. This is implemented to assist the user in maintaining a reference point while using the software. In addition, a tree level indicator is displayed to the right of the version number. This indicator provides an additional reference point as a cross-reference to a tree diagram in the user's documentation.

Located between the screen title and the function key labels is the work area of the screen. It is in this area that all windows are displayed and manipulated. No window will ever extend itself over the screen title or the function key labels.

Displayed in the lower portion of the screen are the function key labels. These labels indicate the current functionality of the function keys. There are active keys and inactive keys. Active keys are identified by labels and will carry out the displayed function whenever pressed. Inactive keys are identified by the lack of a label and will not affect the functionality of the program in any way. They are displayed along with the active keys to provide balance to the screen and maintain proportion between the labels.

A window is a section of the screen that has been dedicated to either the displaying or the entering of data. Windows are identified by an outline or box surrounding the window. As shown in FIG. 33, there are no limit to the number of windows that can be displayed on the screen at any one time, however, there can only be one active window. Active windows are identified by their highlighted outlines and gives the user a sense of position, on the screen and within the program. Often, windows will overlap one another with the active window always on top.

Similar to the screen, windows are divided into three distinct regions or parts: the title, the work area and the prompt line as shown in FIG. 34.

As shown in FIG. 34, the title is used to identify the window and give the user an idea of the action taking place or the information being displayed. If the window was a print window, then the title might read `Print Personality`. If the window is used to display system information, `System Information` would be displayed on the top line. Unlike the screen title, the window title occupies only the top line of the window and the length is determined by the width of the window.

The work area of the window is comprised of one or more fields. Fields are the primary tool with which the user and the program interact. Fields provide for the entering of data or the displaying of data. As such, there are two types of fields: display only fields and input fields. Display only fields are used to label the input fields or provide additional information. Input fields accept data from the user.

When a window is painted, all display only fields will appear in normal video. Default values (if any) for input fields will appear in a highlighted attribute. The cursor will be located in the top left input field being edited. The will appear in reverse video to readily identify the field being edited. The user can edit or modify the data as they please. Once completed, the user signifies completion by pressing one of the movement/acceptance keys (see Key Definitions). Before the cursor advances to the next field a validity check of the data is made. If the data is acceptable, advancement to the next field occurs. However, if the data is unacceptable, a message will appear indicating the problem and the cursor remains in the field until acceptable data is entered. Movement through the screen is from top to bottom, left to right. Advancement passed the last field of the window will cause a wrap around the top. Wrap to the bottom occurs on advancement through the top.

FIG. 35 contains two sample windows: sample A and sample B. Refer to sample A. When this window appears, the cursor will be located in the name input field and a `prompt line` appears at the bottom of the screen. The prompt line is used to help explain either the type, format or range of data that is expected in the field. When advancing to the next field (see sample B), the prompt line changes to reflect the next field.

There are two types of function keys: active and inactive. Inactive function keys will not have a function label associated with the key. Pressing the key will have no affect what so ever on the operation of the screen. On the other hand, active keys are identified by a corresponding label and depressing an active key will cause a `jump` to the function specified.

The definition of the function keys are determined by each window. One window may define the function keys in a manner substantially different than another. However, since only one window can be active at any time, only one set of function key definitions can be active at a time. In other words, the active window controls the function keys.

Although the function keys may take on different definitions i.e.: Using F3 for New and Add, similar definitions will always be defined using the same key. For example: two windows require a New Key. To maintain consistency, F3 will always be used to define the New key. We will never define F4 to be a new key or use any other function key other than F3. The following convention has been selected for the function keys.

FIG. 36 lists the currently defined key positions for some of the more commonly used functions. A brief explanation of each function follows:

When pressed, the set up window will be invoked. The set up window is used to maintain infrequently modified definitions. Included might be such items as radio type and band split setup and frequency sets or group sets definition. The specific windows under the guise of set up will depend on the radio if not the system. Therefore, `infrequently modified` ought to be used as a guide in determining window placement under set up.

Change is used to indicate that the desired operation is to change the personality, data or definition currently highlighted by reverse video. A typical example would be a window that lists the currently defined personalities. To change a personality, the user would use the cursor keys to highlight the personality to be changed and press the change key. This will cause activation of the change personality window. The currently selected personality will become the default and the user will be given the opportunity to enter a new name.

The utility key is used to activate the utility functions screen. Because of the limitation of ten function keys, another screen was created to handle the overflow of the functions. The utility window was implemented to satisfy this requirement. Currently, the utility window provides access to the following functions: Port, Maintenance, Directory, Delete, Print, and Extension.

The new function provides the user with the ability to create a new personality, frequency set or group set depending upon which screen their under when the key is pressed. This key may or may not bring up an intermediary window before providing access to the definition screen.

This key is selected in order to download the selected personality into the radio. Once invoked, it will activate the program personality window and give the user the ability to override the selected personality.

Similar to the program radio key, this key is selected in order to read the radio into a file. Once selected, the read radio window will appear to let the user specify the name of the file to receive the radio personality.

F8 has been set aside as the more key. The more key is used to switch the function keys to alternate sets of function keys. Specifically, the more key is used to handle the over flow of functions.

Help is selected whenever the user has a question about what they are looking at or what they are expected to do. There are two levels of help: field help and window help (accessed by pressing shift F9.) The field level help, when selected, will pop up the normal help window centered in the screen. This help should try to answer at least these three questions: 1. What is the field for? 2. What values are acceptable? 3. What affect will this have on the radio? In the case of toggle fields, it should also indicate that the TAB key is used to toggle the field.

Similarly, the window level help should try to answer these questions: 1. What is this window for? 2. What am I expected to do? 3. Where should I go from here or what are my options.

A couple of thoughts:

1. One of the goal of PC programming is to be self explanatory.

2. Assume the user is unfamiliar with the radio and the terminology.

3. Use support material (documentation, worksheets, samples) whenever practical.

Exit is only found under the current personalities window and is used to return the user to DOS. Once selected, an exit confirmation prompt is displayed that will require the user to confirm the exit.

The port key is found under the utility window. When pressed, it will activate the Communications port window. This window gives the user the ability to specify which communications port the radio interface box is attached to.

This key is selected when the user wishes to change some of the operational parameters of the radio such as power, modulation and squelch levels. Once selected, the maintenance window will appear giving the user the ability to perform the maintenance functions.

The DIRECTORY function is used to change the working directory from within the program. Once selected, the Change directory window will appear and the user can specify a new directory. This new directory will appear in the current personality window.

The delete key is selected in order to delete a personality, frequency or group set. Prior to activation, the user will use the cursor keys to position a video bar over a selected personality. This personality will become the default when the delete window appears.

Print is selected when the user wants to produce a formatted output of the personality. This output can be directed to the line printer, the screen or to an ascii file.

Back is used to return to the previous window. As you recall, it is possible to have multiple windows on a screen. When a new window is created (usually by selecting a function key) the current window becomes inactive and the new window becomes the active window. Returning to the old window is possible by selecting Back.

This key is used to switch between active windows. As mentioned earlier, each screen may contain more than one window. However, only one window can be active at any one time. Movement between the windows can be accomplished through the use of the switch key. When this key is pressed, the current window deactivates and the destination window activates. It should also be noted that this is active only under tightly controlled circumstances.

Typically, the insert key is used to insert an element into a list or group of elements. This can be a list of modes, channels, groups, etc. To insert, the user would position the cursor on the line, row or field in which the insert is to made and press the insert key. Once selected, all the elements from the cursor to the end of the list will be shifted down one position with the current field becoming closer.

Remove is selected to delete an element from a list and move everything else in the list up one position. To remove an element, the user would place the cursor in the element position to be removed and select this key.

There are a few windows that have been designated as confirmation windows. Typically, confirmation windows require a Yes/No entry before continuing. The Yes key is selected to confirm the desired operation.

The No key is found on confirmation windows to give the user the opportunity to cancel the desired operation.

Windows are controlled on a first-in, last-out basis. This means that the last window created will be the first to disappear when back is selected and the first window will be the last.

The help windows employed in this interface incorporate some very unique features. First of all, they reside on disk. What this means is that when the help key is pressed, the help window will read a help file from disk for display on the screen. This has a number of advantages. First of all, it reduces program size which has a direct impact on program loading. The smaller the program, the less time required to load it into memory and the less memory required to run in. Also, by maintaining the help files on disk, they can be changed or modified by any text editor. Thus if a help requires more information, we just edit the help file. No additional compilation is required.

Also, the help window provides full scrolling. This provides for reading helps that may contain more information that can appear on the screen at one time. If the file is larger than the window, the user uses the page up and page down keys to scroll through the text.

This interface defines four general categories of keys: function keys, character keys, editing keys and movement/acceptance keys. Function keys have already been discussed so this discussion will limit itself to the remaining three categories.

Character keys are used to enter data into a field. When pressed, they will deposit a character in the field and advance the cursor to the next character position. The character keys will effectively disable when the field fills. Below are the character keys:

Editing keys are used to manipulate the data within a field. The editing keys are:

Left Arrow

Moves the cursor one character to the left until the left most position of the field is reached. Once reached, an additional left arrow key will cause advancement to the previous field.

Right Arrow

Moves the cursor one character to the right until the right most character is reached. Once reached, an additional right arrow key will cause advancement to the next arrow.

Backspace

Deletes the character to the left of the cursor moving the cursor one space to the left.

Delete

Deletes the character under the cursor and shifts all characters on the right, left on space to fill in the gap.

Insert

Toggles insert mode on and off. Insert mode is identified by a block cursor. When in insert mode, characters may be placed anywhere within a string of characters without over writing characters. When a character key is pressed, all characters on the right are shifted one character to the right and the character is placed in the gap.

Cap Lock

Toggles Capital mode on and off. (General usage)

Control/left arrow

Moves the cursor to the left most character in the field.

Control/right arrow

Moves the cursor to the right most character in the field.

Control/Backspace

Deletes all characters in the field. Cursor will be located in the left most character position.

Movement keys are used to provide movement or cursor positioning on the screen. However, they are also used to indicate an end of input in the current field. When a movement key is pressed, before any movement can occur, the current field is checked for acceptable data. If the data in the field is unacceptable, a message indicating the problem with the data is displayed in the prompt line and the user is required to modify the field.

Enter

Accept data in field and advance to the next field.

Up arrow

Accept data in field and move to previous field. In list windows, the Up arrow key causes the cursor to advance to the field immediately above. Causes the cursor to wrap if in top most field when executed.

Accept data in field and advance to next field. In list windows, causes the cursor to advance to the field below current field. If in bottom most field when executed, causes wrap to the top most field.

Home

Move to the first input field on the window.

End

Move to the last input field on the window.

Tab

Toggle the field between selections.

The following keys are considered to have special usage. The reason for this is that depending on their implementation, the may or may not be a movement/acceptance key.

Page Up

Primary purpose is to page up through the screen data. This data might be channels, modes or various options. The secondary purpose is to scroll the help screen up. Help screen will page up until beginning of file is reached.

Page Down

The primary purpose of the page down key is to page down through the screen data or the help window. This key will be used in conjunction with the page up key.

Note: Some screens such as the Current Personality screen requires a redefinition of the cursor keys. On these screens, no editing of the fields are performed, just selection from a list of fields. In these cases, the cursor keys will provide logical movement within the list. Cursor up moves to the field above the current. Cursor down advances to the field below. Left and right arrow moves to the respective fields.

The user interface specification is the single most important contribution to the success of a PC Programmer. It not only gives the programmer specific direction but it also uncovers serious design flaws in the programmer logic and the radio personality.

By definition, the user interface specification has a two fold purpose. First, it is to guide the development of the PC programmer illustrating each screen and field, the acceptable values of each field, the layout of the windows and the help window text. It should attempt to alleviate any questions a programmer will ask in order to code the program. Secondly, it becomes the basis from which the user's manual can be written. The specification should:

1. Illustrate each window to be displayed in the program. Along with the window illustration, it should give a brief discussion on how the window functions, what fields are conditional on other fields, cursor progression and what the program is doing after data is entered in certain fields.

2. Discuss the window level help. More specifically, the specification should spell out exactly the information that the help window is to display to the user. The programmer should be able to transfer this information directory to the window help file.

3. Explain the operation of each field in the window. Specifically, this discussion should tell the programmer specifically what is to happen when information is entered. For example: When the name is entered, a search is made of the data base to locate the entry. If found, the information is pulled up and displayed on the screen and the cursor advances to the next field. If the entry is not found, a message will appear indicating that the field requires a valid entry before cursor progression.

3. Indicate what each field prompt should say.

4. Discuss each field level help. Similar to the window level help, the field help should spell out exactly what the user will see in the help window.

5. Indicate the default value for each field.

6. Explain the validity check for the field and how it should operate.

7. Indicate the storage for the field. The goal is here is to direct the programmer to where the information is being stored in the personality.

Although there is no set way in which to go about producing a user interface specification; here are a couple of suggestions.

1. Start with an existing specification and perform the necessary cuts and pastes to create a new specification.

2. Based upon the prom specification, itemize the information that the user is required to enter. Try to get an accurate idea of every question or input that needs to be asked in the program.

3. Group together related fields/items. For example, put together all information that's required for each channel and use this information to create a channel definition. The channel definition can then be used to determine which window the information is to be solicited.

4. Create the windows based on the groups of data. The attempt here is to create windows comprised of related fields. For example, options relating to scan should be in a scan window. Options relating to Type 99 should be in a separate Type 99 window, etc. This is going to require a lot of creativity to select the right size window, position the fields within the window, and coordinate window calling.

5. Before writing any text, discuss the screens with every one involved to get a feel for acceptance. No sense in writing a lot of text for a window that no one is going to accept.

6. Once the screens and the philosophy of the program has been accepted, start putting the text with the window. Be very verbose and explain how the window operates, how the fields operate, what the helps should say etc.

The S825 Control Head user interface specification provides a good example of what is required for a specification and should be used as an example.

The hierarchial display format tree structure of the preferred embodiment is schematically shown in FIGS. 2-3. When the user first starts programming system 50, a signon display 100 appears and then display 58 displays a main ("root") screen 102 listing all of the personality files 86 (in the default directory and having the default file extension) stored on mass storage device 56. The user may choose a task to perform by depressing any one of a set of active "function keys" of keyboard 54 (in the preferred embodiment the standard PC function keys F1-F10 are assigned to function selection tasks). Depressing a function key causes a task to be performed, causes a further display format listing additional user selections to be displayed on display 58, or both.

As described above, in the preferred embodiment the task selection assigned to a given function key typically changes with the display format currently being displayed. However, the F9 (and shift-F9) function key always causes user help text to be displayed when it is depressed; and the F10 key always executes a "go back" function (causing the display format next closest to "root" screen 102 in the hierarchial "tree" of display formats to be displayed--or terminating the programming function altogether and returning control to the personal computer DOS operating system in response to a further ny" prompt response from the user if the currently displayed screen is the "root" screen).

In the preferred embodiment, the help text displayed when the F9 or shift-F9 key is depressed reflects the display format currently being displayed, and is obtained from a help file stored on mass storage device 56 in a directory called "HELP". In the preferred embodiment, there is a one-to-one correspondence between different help messages and help files, and only a single help message is stored in each help file. That is, the display format call generated when the F9 (shift-F9) key is depressed depends upon what display format is currently being displayed (and for F9 as opposed to shift-F9, also which input field the cursor is currently within, and references a specific stored help file. In the preferred embodiment, all help files use the common file extension ".HLP", each file contains only help text in ASCII format, and the help file names are descriptive of the function or task the help text corresponds to (e.g., a file "LIGHT.HLP" contains help regarding the selection of an option to backlight the radio display for particular channels, and "MIN.sub.-- VOL.HLP" contains the text assisting the user in selecting a minimum radio volume level, etc.). Since the help text file names are descriptive and the help text files contain only ASCII text, it is actually possible for the user to customize the help text of his system 50 using a simple ASCII text editor.

When the "root" screen 102 is displayed on display 58, the following assignments are made to the set of formation keys F1-F10 in the preferred embodiment:

F1--Invoke a "set up" task and cause display of an associated "set up" display format 104 to permit the user to establish system "default" parameters and radio options;

F2--Invoke a "Change"task and display an associated "Change" display format 104 permitting the user to revise an already existing personality file 86;

F3--Invoke a "Utility" task and display an associated "Utility" display format 106 permitting the user to select from various utility tasks associated with radio programming;

F4--Invoke a "New" task to allow the user to create a new personality file 86;

F5--Invoke a "Program Radio" task which downloads a personality file 86 into a radio EEPROM 72;

F6--Invoke a "Read" task which uploads the contents of a radio EEPROM 72 to personal computer RAM 82 and/or mass storage device 56;

F7--Inactive;

F8--Inactive;

F9/Shift F9-Display user help text; and

F10-Exit programming functions and return to DOS.

Upon depressing the F2 key, the user is prompted for the name of the personality file 86 he wishes to modify, and then a "Channel Data Screen" 116 is displayed. Similarly, the "Channel Data Screen" 116 is displayed when the F4 key is depressed to create a new personality file 86. From the screen 116A or 116B, the user may invoke additional tasks which permit him to select specific radio operating parameters specified by the current personality file 86. Referring to FIG. 3, system 50 assigns the function key set to the following functions in one exemplary embodiment when the "Change Data" screen 116 is displayed;

F1--Modify screen format 116 in response to user selection between voice guard and T99 format for data transmission;

F2--Inactive;

F3--Display a "pop-up window" screen format 144 permitting the user to enable "GE STAR" radio options;

F4--Display a "pop-up window" display format 146 allowing the user to input or change a textual comment associated with the personality file being created/modified;

F5--Display a "pop-up window" display format 110B allowing the user to download the current personality file 86 into a radio 60;

F6--Display a "pop-up" window display format 150 permitting the user to select T-99 data options;

F7--Display a "Radio Options" pop-up window display format 152 permitting the user to select radio operating parameters (e.g., power output level selection, radio serial no., home channel, etc.);

F8--Display a "pop-up window" display format 154 permitting the user to specify radio scan operations;

F9/Shift F9-Display help text; and

F10-Return to "root" screen format 102.

As will be explained in greater detail shortly, the "pop-up window" display formats are somewhat different from other display formats in that they typically do not occupy the entire screen of display 58 and are overlaid on top of the display format displayed before the pop-up window display was invoked.

Referring again to FIG. 2, the user may select any of various utility tasks from the utility display format 106, including:

F1--Display a display format 118 permitting the user to change the personal computer serial communications port used as port 64;

F2--Display a display format 120 presenting the user with radio maintenance functions;

F3--Display a format 128 permitting the user to select a "directory" on mass storage device 56 from which personality files 86 can be selected;

F4--Inactive;

F5--Display a display format 130 permitting the user to delete a personality file 86;

F6--Display a format 132 presenting the user with the option to print the contents of the current personality file 86 to a printer, a file, or display 58;

F7--Display a format 140 prompting the user to choose a default DOS file extension for designating personality files 86;

F8--Inactive;

F9/Shift F9-Display Help Text; and

F10-Return to display of root screen 102.

The "maintenance" display format 120 (F2) invokes further display formats and associated tasks in the preferred embodiment. The further "maintenance" formats/tasks in the preferred embodiment involve special maintenance and testing functions and are typically used only by service technicians. These special functions actually control the radio 60 to operate in various ways under interactive control by personal computer 52, and are used to test and diagnose problems relating to the internal operation of the radio 60. When the "maintenance" display format 120 is displayed, the user may make the following selections:

F1--Dynamically reconfigure the radio 60 (display format 122);

F2--Calibrate the radio (display format 124);

F3--Track radio frequency operation (display format 126);

F4 through F8--Inactive;

F9/Shift F9-Display help text; and

F10--return to displaying "utility" display format 106.

The reconfigure, calibrate and tracking tasks are conventional and have been in use for quite some time by GE service technicians and customers.

Now that the overall hierarchial tree arrangement of the display formats in the preferred embodiment has been described, each of the various display screens 100-156 will be discussed in greater detail in connection with Tables showing their actual textual contents and more detailed written descriptions of the task selection options they each present to the user.

The functional hierarchy of the S-825 control head PC programmer is as follows:

This program is invoked by typing S825CNV at the DOS prompt. Once executed, a brief copyright message will appear and the screen illustrated in the FIG. 37 will appear. This is the current personality screen or the main screen for the radio programmer. The purpose for this screen is to show/highlight the currently defined personalities in the current directory. These personalities are identified by a common extension which is displayed to the right of the screen title (Current Personalities). The current directory defaults to the directory the user was in when the program was run and is identified under the screen title.

The current personality screen will identify up to 63 personalities on a screen. A highlighted cursor (reverse video bar) identifies the selected personality in preparation for a change or program. Movement of the video bar is controlled through the cursor keys. If more than 63 personalities reside in the current directory, they can be accessed by pressing the page down key. The page up and page down keys are only active if more than 63 personalities reside in the directory.

Current Personalities

Note: Through out this program and the associated documentation, the term personality is used. Personality is used generically to refer to the information that is stored in the radio that makes a particular radio different from all similar radios. Using this program, that information can be created/deleted/modified and stored on disk for later reference.

This is the main window for the S825 Control Head programmer. At the top of the window is the title "Current Personalities". To the direct right of the title is the default extension. Below the title, the current directory is displayed. Whenever the program is initiated, the currently defined personalities residing in the current directory with the extension selected, will be displayed on the screen. A reverse video bar indicates the default personality for some of the available options. This bar can be positioned by using the cursor keys to move it around.

From this window, your available options are:

F1--Setup. Select this option if you want to:

Set your personality defaults.

F2--Change. Select this option if you want to:

Change/edit an existing personality.

F3--Utility. Select this option if you want to:

Change comm port entry, change directory, delete a personality, print a personality or change extensions.

F4--New. Select this option if you want to:

Create a new personality.

F5--Progrm. Select this operation if you want to:

Program a radio with the personality selected.

F6--Read. Select this option if you want to:

Read the personality out of the radio.

Note to programmer: The field level help should call up the window help.

Selecting F1 (setup) from the current personality window will bring the user into the setup portion of the program. Setup consists of three distinct windows: the deluxe keypad definition (FIG. 38), the basic keypad definition (FIG. 41) and the frequency range window (FIG. 39). The keypad definition windows give the user the ability to define the keypad defaults to use whenever a new personality is created and the frequency range window provides for setting the band split default. Once the user then selects `Back` from any of the windows, the current state of the windows are saved to disk so that program `remembers` the settings. The next time the user enters setup, the last state will be the default. (This includes the last keypad definition window used i.e.: Basic or Deluxe.

Upon entry, the cursor will be located in the first input field of the screen. Each of these input fields is a toggle field and represents the appropriate key on the control head. To define the key, the user toggles the field until the correct selection is displayed. Once the selection has been made, the user advances to the next item.

There are 4 display only fields on the window: Pwr, Fnc, Vol, and Chn. These fields are used only to help provide reference to the screen and to give an indication that they cannot be redefined.

Normal cursor progression is left to right, top to bottom. Once the window has been completed, the user can either switch to the frequency range window or pull up the basic window.

Deluxe Keypad Definition

This is the deluxe keypad definition setup window. The layout of the screen was selected to represent the physical layout of the keys on the deluxe model of the S825 control head. Using this window, you may select the defaults to be used when creating a new personality. To do this, advance the cursor to the key you wish to define and press the TAB key to toggle/select you desired selection.

From this window, your available options are:

F1--Switch. Select this option if you want to:

Change/select the default frequency range.

F2--Basic. Select this option if you want to:

Define the key pad defaults for the basic unit.

Each of the `XXX` displayed above is a toggle field that represents a key on the control head. Using the TAB key, the user toggles between the following list of items:

WAI--Wail, YLP--Yelp, RST--Reset, SL1 to SL8, GE*--GEstar,

VG--Voice Guard, PA--Speaker PA, DSB--Disabled, VLU--Volume up

VLD--Volume down, CHU--Channel up, CHD--Channel down, MOD--Mode

HOM--Home, SCN--Scan, SPR--Speaker, SQL--Squelch level,

CG--Channel guard, DEL--Delete, ADD--Add, VRS--Vehicular RPT,

EG*--Emergency GEstar

Press TAB to toggle, F9 for help.

Key Definition: This field is used to define the respective key on the control head. Using the TAB key, this field toggles between the available options for this field. They are:

WAI--Wail (Initiate the Wail siren)

YLP--Yelp (Initiate the Yelp siren)

RST--Reset (Disable the key)

SL1 to SL8--Siren/Light combination (Initiate the appropriate combination)

GE*--GEstar (Generate GEstar ID)/T90/T99

VG--Voice Guard (Enter encrypted speech mode)

VRS--Vehicular RPT On/Off

EG*--Emergency GE*

PA--Speaker PA

SPR--External speaker

DSB--Key Disabled

VLU--Volume up

VLD--Volume down

CHU--Channel up

CHD--Channel down

MOD--Mode

HOM--Home

SCN--Scan

ADD--Add

DEL--Delete

SQL--Squelch level

CG--Channel guard

The defaults for each field will be the last state of the fields. The program remembers.

Note: When first invoked, the pattern will default to the standard configuration.

There are no validity checks for this field.

Refer to section 11.0 (Prom spec)--Keypad Definition

The window illustrated above is the Basic keypad definition window and is pulled up by selecting the F2 (Keypad) key from the Deluxe window. All data entry for the window operates in a similar fashion to the deluxe.

Upon entry, the cursor will be located in the first input field of the screen. Each of these input fields is a toggle field and represents the appropriate key on the control head. To define the key, the user toggles the field until the correct selection is displayed. Once the selection has been made, the user advances to the next item.

There are 4 display only fields on the window: Pwr, Fnc, Vol, and Chn. These fields are used only to help provide reference to the screen and to give an indication that they cannot be redefined.

Normal cursor progression is left to right, top to bottom. Once the window has been completed, the user can either switch to the frequency range window or pull up the basic window.

Basic Keypad Definition

This is the basic keypad definition setup window. The layout of the screen was selected to represent the physical layout of the keys on the basic model of the S825 control head. Using this window, you may select the defaults to be used when creating a new personality. To do this, advance the cursor to the key you wish to define and press the TAB key toggle/select you desired selection.

From this window, your available options are:

F1--Switch. Select this operation if you want to:

Change/select the default frequency range.

F2--Deluxe Select this option if you want to:

Define the key pad defaults for the deluxe unit.

Each of the `XXX` displayed above is a toggle field that represents a key on the control head. Using the TAB key, the user toggles between the following list of items:

WAI--Wail, YLP--Yelp, RST--Reset, SL1 to SL8, GE*--GEstar,

VG--Voice Guard, PA--Speaker PA, DSB--Disabled, VLU--Volume up

VLD--Volume down, CHU--Channel up, CHD--Channel down, MOD--Mode

HOM--Home, SCN--Scan, SPR--Speaker, SQL--Squelch level,

CG--Channel guard, DEL--Delete, ADD--Add, VRS--Vehicular RPT,

EG*--Emergency GEstar

Press TAB to toggle, F9 for help.

Key Definition: This field is used to define the respective key on the control head. Using the TAB key, this field toggles between the available options for this field. They are:

WAI--Wail (Initiate the Wail siren)

YLP--Yelp (Initiate the Yelp siren)

RST--Reset (Disable the key)

SL1 to SL8--Siren/Light combination (Initiate the appropriate combination)

GE*--GEstar (Generate GEstar ID)/T90/T99

VG--Voice Guard (Enter encrypted speech mode)

VRS--Vehicular RPT On/Off

EG*--Emergency GE*

PA--Speaker PA

SPR--External speaker

DSB--Key Disabled

VLU--Volume up

VLD--Volume down

CHU--Channel up

CHD--Channel down

MOD--Mode

HOM--Home

SCN--Scan

ADD--Add

DEL--Delete

SQL--Squelch level

CG--Channel guard

The defaults for each field will be the last state of the fields. The program remembers.

Note: When first invoked, the pattern will default to the standard configuration.

There are no validity checks for this field.

Refer to section 11.0 (Prom spec)--Keypad Definition

FIG. 39 is one of three frequency range windows and is accessed by selecting the F1 (Switch) key from one of the keypad definition windows. This window consists of 14 selectable fields used to indicate the current/desired band split default. A selection is made by moving a highlighted video bar over the selection and leaving the window (either through the back key or F1). The F1 key returns the user to the keypad definition window.

Access to the other frequency range windows is granted by pressing the F3 (Range) key. Once depressed, the next range window will appear in place of the current window. Three windows provide for Rangr, Narrow band delta and Wide band delta. Note: The other windows are displayed on the following pages.

Frequency Range

FIG. 40 shows the frequency range window. It is used for selecting the band split to default whenever `New` is selected from the current personality screen. To select a band split, position the reverse video bar over your selection and exit the window by pressing F1 or F10. The selected split will be saved to disk so that the program will remember it the next time it is initiated.

FIG. 42 shows the change personality window and is accessed by selecting the F2 (Change) key from the Current Personality Screen. This window is selected in order to change a personality reading in the current directory.

The reason this window is called is to give the user some flexibility in editing personalities. We do not want to restrict the user by making them cursor to the personality they want to edit. Instead, we bring up an intermediary window and give them the opportunity to change the file name.

Change/Edit Personality

This is the change personality window. The purpose of this window is to solicit the name of the personality to change. Once the name is entered press F1 to continue.

From this window your options are:

F1--Select this option if you want to:

Change the personality selected.

F2--Select this option if you want to:

Discontinue this procedure.

File to be edited:

This is an alphanumeric field that is used to solicit the file name of the personality to be edited. Under normal operations, the user will not edit this field but to leave the default.

None

File to edit: This field is used to enter the name of the personality to be changed/edited. This is an eight character alphanumeric field and will accept any valid DOS file name provided the personality exists in the current directory. Once a name is entered, select F1 to change the personality and F2 to abort the operation.

The default for this field is the name that was highlighted in the current personality screen.

A valid entry for this field will pass the following tests:

1. Must be an acceptable DOS file name.

2. File must exist in the current directory.

3. File must be a "personality" file.

There is no storage for this field.

FIG. 43 shows the utility screen and is accessed by selecting the F3 (Utility) key from the current personality screen. The utility screen is used to give the user access to some of the secondary functions of the PC programmer.

This screen operates in a similar manner to the current personality screen. The only difference between the two are the function keys.

Utility

This is the utility window. As you can see, every aspect of this window is the same as the current personality screen except for the function keys.

From this window your options are:

F1--Select this option if you want to:

Change the port to use for programming radios.

F3--Select this option if you want to:

Change your current directory.

F5--Select this option if you want to:

Delete/Erase a personality from the disk.

F6--Select this option if you want to:

Printout the personality to the printer, screen or file.

F7--Select this option if you want to:

Change the current extension.

This is the port setup window. The purpose of this window is to give the user the option of selecting the communications port to use for the programming of the control head. Here the user would enter the port for programming and then select the F1 key. Once the F1 key is selected, the setup file is updated to reflect the new selection.

Communications Port Selection

This is the comm port window. The purpose of this window is to define/select the communications port you wish to use for radio programming purposes. After entering the correct port:

From this window your options are:

F1--Select this option if you want to:

Save the selection.

F2--Select this option if you want to:

Abort this procedure.

This is a numeric field used to identify the communications port to use for programming the control head.

Note: The validity test is only performed if F1 is selected.

Enter the Comm Port ID.

Comm Port ID: The purpose of this field is to identify the communications port to use for programming the control head. There are only two ports available for this purpose: COM1 and COM2. Enter a 1 here to select COM1 and a 2 to select COM2. This field will not accept a comm port ID of a port that does not exist.

First time--1, afterwards the program remembers.

A valid entry will pass the following tests:

1. Must be either a 1 or a 2.

2. The comm port must exist or it will not be accepted.

The entry here is stored in the setup file.

FIG. 45 shows the change directory screen and is selected by pressing the F3 (Dir) key from the Utility screen. The purpose of this window is to provide the means by which the user can change directories without having to leave the program.

Once the user enters a path, they have the option of changing directories to the path entered by pressing F1 or aborting the operation by selecting F2 or F10.

Change Directory

This is the change directory window. The purpose of this window is to solicit the name of the directory to which the change is to be made.

From this window your options are:

F1--Select this option if you want to:

Proceed with the change.

F2--Select this option if you want to:

Abort this procedure.

This is a alphanumeric field that is used to specify the new path. Once the user enters the port, they select F1 to perform the actual change. Selecting F2 will have the affect of cancelling the command.

Note: The validity test is only performed if F1 is selected.

Enter desired directory.

Change Directory: This field is used to specify the desired or target path for a change directory. This field will accept any valid DOS path identifier restricted only to 32 characters. This field will not accept the name of the path that does not exist.

Current path

A valid entry for this field must pass the following conditions:

1. Must be a valid DOS path identifier

2. Path must actually exist.

If path does not exist, give message and the user the opportunity to create one.

None

FIG. 46 shows the delete personality window and is accessed by pressing the F5 (Delete) key from the Utility window. The purpose of this window is to give the user the ability to delete a personality without leaving the program. When this window is opened, the default file name is displayed in the file name field. the user selects F1 to delete or F2 to abort. Once the deletion is made, the current personality screen is updated to reflect the deletion.

Delete Personality

This is the delete personality window. The purpose of this window is to solicit the name of the personality to delete from disk.

WARNING: This operation will permanently remove the file.

From this window your options are:

F1--Select this option if you want to:

Proceed with this operation.

F2--Select this option if you want to:

Abort this operation

This is an alphanumeric field used to indicate the name of the personality to delete. It will accept a file name up to eight characters in length.

Note: The validity test is only performed if F1 is selected.

None

Delete Personality: This field is used to identify the personality to delete. Enter the name of the personality to delete and press F1. Once F1 is selected, the personality is permanently deleted from the directory. If you do not wish to delete the personality, select F2.

The highlighted file name.

A valid field entry will pass the following conditions:

1. The name is a valid DOS file name.

2. The file actually exists.

There is no storage for this field.

This is the print personality screen and represents a new print screen format for PC programming. The reason for the new format is to provide flexibility in print devices, more reliable error/device checking and a considerably easier user interface.

Upon entry, the cursor is located in the personality field. Once the name is selected, the cursor advances to the output field. This is a toggle field that lets the user toggle his/her print options. Whenever the field toggles, a portion of the window appears and/or disappears to display additional options appropriate only for the selected device. All possible configurations are discussed below.

If the user selects F1 to generate the printout, a final edit check should be performed to ensure that the following conditions are met:

1. If the print device is a printer, the printer is on-line.

2. If the print device is a file, that the file is not overwritten unless directed.

Print Personality

This is the print personality window. The purpose of this window is to solicit the information required before performing the print operation. In this window, you should specify the personality to print and where the printout should go.

From this window your options are:

F1--Select this option if you want to:

Continue with this operation.

F2--Select this option if you want to:

Abort this operation.

This field is used to enter the name of the personality to print. This is an alpha numeric field that will accept up to eight characters.

Enter the personality to print.

Personality: This field is used to identify the personality to print. Please enter the personality name.

The highlighted file name.

A valid field entry will pass the following conditions:

1. The name is a valid DOS file name.

2. The file actually exists.

There is no storage for this field.

This is a toggle field that is used to identify the device to receive the printout. There are three available selections: Printer, Screen and File. When printer is selected, the screen above is displayed and the user will have the option of choosing the print device. Once this data is entered, the hard copy printout can be generated. If the user selects Screen, the printout will be generated on the screen and the user can page/cursor through the data. Selecting file from the output to field will cause printout to be generated to a file for printout at a later time.

Press TAB to toggle, F9 for help.

Output To: This is a toggle field that is used to identify where the printed output should go. There are three available options: Printer, Screen and File. Using the TAB key, toggle this field until your selection is displayed and press F1 to generate the print. Choose Printer if you want the printed output to go to the printer. Select Screen if you want the output to go to the screen and File if you want the output generated in an ASCII file format.

Printer

There are no validity checks for this field.

There is no storage for this field.

FIG. 37 illustrates the print window when the output to field has been toggled to Screen.

FIG. 48 illustrates the layout of the window when file is selected as the output device. Here the user is required to enter a file name for the printed output.

This field is used to enter the path/file name to which the output should be generated. Once the user has entered the destination file name and pressed F1, a message will indicate that the printout is being generated and return the user to this screen.

Enter destination file name.

Destination: This field is used to enter the destination file name for the printed output. Enter the complete path name and select F1 to generate the file.

Blank/Empty field

A valid entry will pass the following conditional tests.

1. Name is a valid DOS name.

2. If the file exists, an overwrite prompt will ask for direction.

There is no storage for this field.

FIG. 49 illustrates the change extension window and is used to select the default extension. The extension selected here is displayed on the current personality screen and becomes the default whenever creating a new personality.

When the window is opened, the cursor will be located in the file name extension field. Here they would enter the new extension and press F1 to save the selection. The disk will be updated to reflect the new extension. The extension will be remembered by the program the next time it is initiated.

Change Extension:

The purpose of this window is to solicit the characters for the new extension.

From this window your options are:

F1--Select this option if you want to:

Continue with this operation.

F2--Select this option if you want to:

Abort this operation

This field is used to enter the new file extension to use as the default. This field will accept three alphanumeric characters as valid file extensions.

None

Extension: This field is used to enter the default file name extension. This extension will be displayed at the top of the current personality screen and is used as a "selector" in which personalities should be displayed on the screen. Once the extension has been entered, select F1 to perform the change or F2 to abort.

Currently defined extension. First time - 825.

A valid entry will consist only of alphanumeric characters.

There is no storage for this field.

FIG. 50 illustrate above is the control head personality screen and is the main screen at the personality level. This screen gives a brief overview of the control head personality by identifying the frequency band split, programmed modes and various mode options. Up to eight modes can be displayed on the screen at a time out of a total of 64 modes. Access to modes 9 and above is gained through the use of the page down key. The user can continue "paging" through modes until mode 64 is reached or they reach the end of the defined modes. In other words, the user cannot page down past the last defined mode. Likewise, access to previous modes is accomplished through the page up key. The only limitation here is that the user cannot page up past mode 1.

The screen above is actually one half of a two part screen. All of the information required to be displayed for each mode would not fit on one screen, therefore the screen was split in two. The F4 key is used to toggle between the two halves of the screen. (Please refer to section 2.4.4 for the second half of the screen.) This screen illustrates the scan section of the modes. When F4 is depressed, the signalling portion of the mode data is displayed and the F4 key label changes to "Scan" to indicate that this screen is again accessed by the F4 key.

In the lower right hand corner of the screen is the Bytes Free field. This is a display field only and give the user an indication of the amount of available spaced left in the personality. As the personality fills, the number displayed here will decrease until the available space left dips below the minimum necessary. Although the control head will support up to 64 modes, it may not be possible for the user to define 64 nodes if the personality "runs out of space". This will be based on the combination of modes and channels.

Logical progression of the cursor is left to right, top to bottom. It is intended that the user enter the mode name, frequency set, signal etc. In the order in which it is displayed. However, the program will not restrict the user to enter the data in that fashion. The user has full control over the screen and a final edit check will be made when the user tries to "leave" the personality. This final edit check will ensure that the following conditions are met:

1. There must be at least one valid mode defined.

2. There are no blank or empty imbedded nodes.

(To be considered valid, a mode must contain a frequency set if GEstar is selected, it must have a valid GEstar ID.)

The user has the ability to insert and remove nodes through the use of the F2 (Insert) and F3(Remove) keys. The operation of these two keys are explained further in this text.

Control Head Personality

This is the primary data entry screen when defining a personality. A personality consists of one or more MODES. A mode is a collection of channels in which the radio will operate and a set of options for the mode. These options consist of a signalling scheme, non-priority scan definition and a priority scan definition.

The screen you're in consists of one half of the mode definition. Once the information for this screen has been entered, the additional mode information can be accessed by selecting the F4 key. This key will toggle between the mode scan defaults and the modes signalling defaults.

The steps involved with defining a mode consists of the following:

1. Frequency set definition. You are required to create a frequency set to be used in the personality. This can be done by selecting the `More` key and then the `Freq` key.

2. A mode name is then entered in the name field. The name entered here will be displayed on the control head during operation.

3. Once the name has been entered, a frequency set needs to be `assigned`. You can assign a frequency set to a mode by entering the name of the frequency set in the field to the right of the mode name.

4. The final step to mode creation is to set the various scan and signalling defaults.

To save the currently saved mode to disk, press the F10 key to go back to the currently personality screen. You will be prompted to save the file.

You're other options available from this screen are:

F1--Select this option if you want to:

Get a detail summary of the frequency set.

Move the cursor to the frequency set field you wish to detail.

When this key is pressed, the frequency set definition screen will appear identifying the set data.

F2--Select this option if you want to:

Insert a new mode. This key will cause all modes from the cursor to the end of the personality to shift down one.

F3--Select this option if you want to:

Remove a node.

Use this key to delete a mode by cursoring to the line of the mode you wish to delete and press this key. All modes following will be shifted up one place to fill in the space.

F4--Select this option if you want to:

Reveal the additional mode options.

F5--Select this option if you want to:

Program a control head with the currently displayed personality.

F7--Select this option if you want to:

Define the control head options.

F8--Select this option if you want to:

Create/edit frequency sets and define the personality text.

Working from left to right, the first field displayed is the mode field. The mode field identifies the numerical order of each mode in the control head. It is a display only field meaning the user cannot cursor to it. The value in the mode field is controlled through the use of the page up/down keys as discussed earlier.

This field is used to mnemonically identify the mode for display in the control head. The mode name field will accept up to 8 characters of ASCII data and will automatically capitalize the letters as they are typed.

Prompt

Enter mode name for display on the control head.

Help

Mode Name: This field is used for entering the mode name for a displayable reference on the control head during radio operation. This field will accept all alphanumeric characters (excluding lower case), spaces and the following special symbols: @[] /.-+<>*'&$%#"!?=;:

Default

Blank/Empty field. Empty names are stored as "MODE XX" where XX is the numerical mode identifier during the write operation.

Validity

This field will accept all alphanumeric characters (excluding lower case), spaces and the following special symbols: @[] /.-+<>*'&$%#"!?=;:

Storage

MASCII--One name per mode.

Note:

1. All characters must be used. (Unused filled with periods)

2. Special conversion routine as per PROM spec.

3. MASCII is an array of names.

The frequency set field is used to associate a predefined frequency set to a mode. When the user enters a frequency set name, a search is made of the personality to fine a "matching frequency set name". If a match is found then a logical association is made between the mode and the frequency set. If the set is not found, then a search is made of the pooled directory for a matching set.

If the user wants to replace the existing frequency set with a new frequency set, they simply replace the name with the name of a new set. If the replaced set is not used with any other mode then it is deleted from the personality.

Prompt

Enter the name of a predefined frequency set.

Help

Frequency Set: This field is used for entering the frequency set definition to be used with this mode. When the name is entered, a search is made through the personality and the frequency set pool for a match. Once a match is made, then an association has been created. To change frequency sets, just change names. This field will only accept valid DOS file names as acceptable entries.

Default

Blank/empty field.

Validity:

1. The name must be able to pass a DOS filename validity test.

2. It must match a predefined frequency set.

Storage

The frequency set name is not stored in the personality. Therefore, the read process must create set names. An example of a created set name is "SET.sub.-- XX" where XX is the numerical reference of the set within the personality.

1. Channel count stored in modes.

2. Rx/Tx synthesizer data stored in channels

The signal field is used to identify the type of signalling associated with this mode. Because there are only three possible selections, this field will toggle between the following choices:

Disabl--Indicates signalling disabled

T90T99--Type 90/99 signalling

GEstar--Gestar signalling

Prompt

Press TAB to toggle, F9 for help.

Help

Signal: This field is used to indicate the type of signalling to be used with this mode. Through the use of the TAB key, the value within this field will toggle between the following: "Disabl", "T90T99", and "Gestar". "Disabl" indicates that all signalling should be disabled for this mode. "T90T99" indicates that a T90 or T99 signalling scheme is desired. Leaving "Gestar" in this field will indicate that a GEstar type signalling is desired.

Default

Disabled

Validity

If T90/T99 is selected, then a quick check of the frequency set should be made to ensure that the home channel has a T90 tone. If the home channel does not have a T90 tone, T90/T99 cannot selected.

Storage:

GEstar

This is a toggle field that is used to indicate the type of priority one scan programming. The choices are:

Fixed--P1 channel is entered, not changeable from control head.

User--P1 channel is entered, changeable from control head.

Selchn--P1 channel is not entered.

Help

Priority 1 Programming: This is a toggle field used to select the type of priority 1 programming for this mode. Using the TAB key, the value in this field will toggle between "Fixed", "User", and "Selchn". "Fixed" indicates that the P1 channel will be entered during programming and cannot be modified through the ADD/DEL keys on the control head. "User" indicates that the P1 channel will be selected through the use of the ADD/DEL keys on the control head. Leaving "Selchn" in this field indicates that the P1 channel will always be the current channel.

Default

User

Validity

There is no validity check on the selection. However, if the user selects Selchn, the P1 field is skipped.

Storage

Scan table

The P1 field is used to identify the priority one channel for a selected mode. It corresponds to a channel within the selected frequency set. Only numeric data is accepted.

Prompt

Enter the desired priority 1 channel.

Help

Priority 1 Channel: This field is used to enter the default/fixed P1 channel. If "Fixed" is selected as the type of P1 programming desired, the value entered here becomes the fixed P1 channel. If "User" is selected, then the channel entered here becomes the default P1 channel.

This field will not accept channels outside of the frequency set and the channel selected must have the Scn flag "On".

Default

Bland/Empty channel

Validity

1. It must be a channel from the selected frequency set.

2. The channel chosen must have Scan enabled.

Storage

Scan

This is a toggle field that is used to indicate the type of priority two scan programming. The choices are:

Fixed--P2 channel is entered, not changeable from control head.

User--P2 channel is entered, changeable from control head.

Selchn--P2 channel is not entered.

Prompt

Press TAB to toggle, F9 for help.

Help:

Priority 2 Programming: This is a toggle field used to select the type of priority 2 programming for this mode. Using the TAB key, the value in this field will toggle between "Fixed", "User", and "Selchn". "Fixed" indicates that the P2 channel will be entered during programming and cannot be modified through the ADD/DEL keys on the control head. "User" indicates that the P2 channel will be selected through the use of the ADD/DEL keys on the control head. Leaving "Selchn" in this field indicates that the P2 channel will always be the current channel.

Default

User

Validity

There is no validity check on the selection. However, if the user selects Selchn, the P2 field is skipped.

Storage

Scan

The P2 field is used to identify the priority two channel for a selected mode. It corresponds to a channel within the selected frequency set. Only numeric data is accepted.

Prompt

Enter the desired priority 2 channel.

Help

Priority 2 Channel: This field is used to enter the default/fixed P2 channel. If "Fixed" is selected as the type of P2 programming desired, the value entered here becomes the fixed P2 channel. If "User" is selected, then the channel entered here becomes the default P2 channel.

This field will not accept channels outside of the frequency set and the channel selected must have the Scn flag "On".

Default

Blank/Empty field

Validity

1. It must be a channel from the selected frequency set.

2. The channel chosen must have Scan enabled.

Storage

Scan

Removed in version 1.0

This is a toggle field used to indicate whether or not to scan channels with channel guard. There are only two possible selections for this field, Yes/No. Yes indicates that channels with channel guard can be included into the scan list.

Prompt

Press TAB to toggle, F9 for help.

Help

Scan With Channel Guard: This is a toggle field used to indicate whether or not to scan channels with channel guard. Using the TAB key, this field will toggle between "Yes" and "No". Selecting "No" will have the affect of removing channels with channel guard from the scan list.

Default

Yes

Validity

There are not validity checks for this field.

Storage

Scan table

The detail key is used to provide a detail description of the frequency set selected as shown in FIG. 5. It also provides the means by which the user can modify the frequency set associated with the mode. To access the details of a frequency set, the detail key should be pressed while the cursor is sitting in the freq set field. Once depressed, the screen illustrated above will appear.

The screen displays up to eight channel definitions at a time. Each channel definition includes a channel name, Rx and Tx frequency, Rx and Tx channel guard, Scan flag, CCT, STE Channel guard block and a set of tone signalling frequencies.

Operation of this screen is similar to the control head personality screen. Normal cursor progression is left to right, top to bottom. However, the user is not restricted to entering data in that manner. He/she may cursor freely about the screen, entering data in a fashion comfortable to them. A final screen edit check will perform the consistency checks when the user tries to save the data. The final edit check will ensure that the following conditions are met:

1. There is at least one channel definition in the set.

2. There is no embedded blank/empty channel definition.

(A valid channel definition requires at least an Rx frequency.)

As with the control head personality screen, the user can insert/remove channel definitions through the use of the F2 (Insert) and F3 (Remove) function keys. To insert a channel definition, the user would place the cursor on the line above which the insertion should go. They then press the F2 key. Everything from the current line to the end of the frequency set will be shifted one channel definition down; the current line becoming empty. The user can then proceed to enter the new channel definition.

Removing a channel definition is very similar to the insertion. They would cursor to the line of the channel definition they wish to delete and press the F3 key. The current channel definition would be deleted and all greater channels will be shifted up one definition to fill in the gap.

Channels nine and above can be accessed through the use of the page down key. Each time the page down key is depressed, the next eight channels will be displayed. The user can page down, providing the current page is filled, until channel 32 which is the limit of channels per mode. In a similar manner, the user can page up through the channel using the Page Up key until channel 1 is reached.

Frequency Set Definition

This is the frequency set definition screen and is used to create/edit frequency sets. Basically, a frequency set is an association of channels all within the same band split that will be `assigned` to a mode.

From this window your options are:

F2--Select this option if you want to:

Insert a channel definition.

Position the cursor to the respective line and press this key. The current channel and all following will be shifted down one position.

F3--Select this option if you want to:

Remove a channel definition.

Position the cursor to the line of the channel you wish to delete.

F5--Select this option if you want to:

Store the frequency set to disk.

This field is a display only field that is used to give the user an indication of which channel is being displayed. The value contained within this field is changeable only through the use of the Page Up and Page Down keys.

The name field is used to enter an mnemonic channel identifier that will be displayed on the control head. The channel name can consist of any combination of alphanumeric characters up to eight characters in length. This is an upper case only field in which the character data typed is always converted to upper case automatically.

Prompt

Enter the displayable name for this channel.

Help

Channel Name: The channel is used to indicate the current channel setting of the control head. It can consist of any combination of alphanumeric characters up to 8 characters in length. Alphabetic characters are automatically converted to upper case upon entry.

Default

Blank field. On the writes, channel names are created for blank name fields.: The created name will look similar to this: CHN..XX where XX is the numeric presentation of the channel.

Validity

The validity check for this field is to ensure that the field only contains acceptable characters as identified in the specification.

Storage

CASCII

1. All characters must be used

2. Special conversion routine.

This is a numeric field where the user identifies the transmit frequency of the channel. The frequency entered here is copied over to the Rx freq as a default for the VHF and UHF splits. When working with the 800 split, 45 Mhz is added to this value before copying to the Rx side.

Prompt

Enter the transmit frequency for this channel.

Help

Transmit Frequency: The transmit frequency entered here is used to indicate the frequency of which the radio should transmit while tuned to this channel. Frequencies only within the currently defined band split are acceptable as valid frequencies. VHF frequencies must be evenly divisible by either 5 Khz or 6.25 Khz. UHF frequencies must be evenly divisible by 5 Khz. 800 band frequencies must be evenly divisible by 12.5 Khz.

Default

Empty/Blank Field.

Validity

1. Must be within the current band split.

2. If the Cntrl E key is pressed, must be within 10 Mhz outside split.

3. If VHF--Must be evenly divisible by 5 or 6.25.

4. If UHF--Must be evenly divisible by 5.

5. If 800--Must be evenly divisible by 12.5. Must be between 805-824 or 851-870.

Storage

Channels

This is a numeric field where the user identifies the receive frequency of the channel. This field must be entered in order to have a valid channel definition.

Prompt

Enter the receive frequency for this channel.

Help

Receive Frequency: The receive frequency entered here is used to indicate the frequency of which the radio should receive while tuned to this channel. Frequencies only within the currently defined band split are acceptable as valid frequencies. VHF frequencies must be evenly divisible by either 5 Khz or 6.25 Khz. UHF frequencies must be evenly divisible by 5 Khz. 800 band frequencies must be evenly divisible by 12.5 Khz.

Default

In the VHF and UHF band splits, the default for this field is the value contained in the corresponding Tx frequency. For 800 band split, the default for this field is the corresponding Tx frequency+45 Mhz.

Validity

1. Must be within the current band split.

2. If the Cntrl E key is pressed, must be within 10 Mhz outside split.

3. If VHF--Must be evenly divisible by 5 or 6.25.

4. If UHF--Must be evenly divisible by 5.

5. If 800--Must be evenly divisible by 12.5 Must be between 815-870.

Storage:

Channels

This is a alphanumeric field used to enter the transmit channel guard for this channel. This field accepts digital and tone channel guard codes. Tone channel guards are identified by the placement of a decimal point within the field.

023--Digital Channel Guard

67.0--Tone Channel Guard

When the transmit channel guard is entered, it is automatically copied to the receive channel guard providing it has not yet been defined. This means that once the channel has been defined, the transmit channel guard will not be copied to the receive side regardless of whether or not the field is empty.

There are no known split inversions for channel guards in this control head so none will be performed.

Prompt

Enter the desired tx channel guard mode for this channel.

Help

Transmit Channel Guard: There are two types of channel guard decoding available for this control head: digital and tone. Tone channel guard decoding is identified by the placement of decimal point within the field. For example: 67.0 identifies a tone channel guard of 67 Hz. Valid tone channel guards lay in the range of 67.0 to 210.7 Hz. Digital channel guard decoding is identified by the lack of a decimal point. An example of digital channel guard codes are 023, 047,315 etc. Valid digital channel guard codes can be found in Appendix 1 of the S825 Control Head programming user guild.

Default

There are no defaults for this field.

Validity

The validity check for this field are as follows:

1. If tone channel guard--range is 67.0 to 210.7

2. If digital channel guard--must be included in chngrd.h table.

Storage

TDIV and channel data (always)

This is a alphanumeric field used to enter the receive channel guard for this channel. This field accepts digital and tone channel guard codes. Tone channel guards are identified by the placement of a decimal point within the field. Digital channel guard are identified by the lack of a decimal point. For example:

023--Digital Channel Guard

67.0--Tone Channel Guard

When the transmit channel guard is entered, it is automatically copied to the receive channel guard providing it has not yet been defined. This means that once the channel has been defined, the transmit channel guard will not be copied to the receive side regardless of whether or not the field is empty.

There are no known split inversion for channel guards in this control head so none will be performed.

Prompt

Enter the desired rx channel guard code for this channel.

Help

Receive Channel Guard: There are two types of channel guard decoding available for this control head: digital and tone. Tone channel guard decoding is identified by the placement of decimal point within the field. For example: 67.0 identifies a tone channel guard of 67 Hz. Valid tone channel guards lay in the range of 67.0 to 210.7 Hz. Digital channel guard decoding is identified by the lack of the decimal point. An example of digital channel guard codes are 023, 047, 315 etc. Valid digital guard codes can be found in Appendix 1 of the S825 Control Head programming user guild.

Default

The default for this field is the tx channel guard code--only on the first time the channel is defined.

Validity

The validity check for this field are as follows:

1. If tone channel guard--range is 67.0 to 210.7

2. If digital channel guard--must be included in chngrd.h table.

Storage

If Rx CG decode is enabled:

Digitals always stored in channels and RDIV is set to zero.

Tones always stored in RDIV using * 10 storage and channel Rx cg data is blanked.

Digitals always stored in channels RDIV is set to zero.

Tones always stored in both using PHOENIX III format.

This is a toggle field that is used to indicate whether or not the channels is to be included into the default/fixed scan list. If Non-priority scan is fixed for this mode, than selecting "Yes" for this field will place the channel in the fixed scan list. Otherwise, the channel is defaulted to inclusion into the scan list. A channel cannot be selected for priority scan without having Scn set to "Yes".

Prompt

Press TAB to toggle, F9 for help.

Help

Scan: This field is used to indicate whether or not this field is to be included into the default/fixed scan list. This field can be changed by toggling the TAB key. A "Yes" value indicates that this channel is included in the default/fixed scan list. Note: In order to define a channel for priority scan, it must be enabled for scan; a "Yes" value.

Defaut

No

Validity

There is no validity check for this field.

Storage

Scan

This is a toggle field that is used to indicate whether or not the carrier control timer is enabled for this channel. There are two available options: "On" and "Off". Off indicates that there will be no carrier control timer.

Prompt

Press TAB to toggle, F9 for help.

Help

Carrier Control Timer: This field is used to indicated whether or not the carrier control timer should be enabled for this channel. Using the TAB key, the value in this field will toggle between "On" and "Off". Selecting "On" will have the affect of enabling the carrier control time for this channel. The timeout period can be defined in the control head options screen.

Default

On

Validity

There is not validity test for this field.

Storage

If "On" then use the CCT value from the control head options screen for programming the channel data.

This is a toggle field that is used to indicate whether or not squelch tail elimination is to be enabled for this channel. It toggles between "On" and "Off" with the "On" value indicating that Ste is enabled. Normally, access to this field is denied unless a digital or inverted rx channel guard is entered.

Prompt

Press TAB to toggle, F9 for help.

Help

Squelch Tail Elimination: This field is used to indicate whether or not squelch tail elimination is to be enabled on this channel. By pressing the TAB key, the value within the field will toggle between "On" and "Off". An "On" value indicates that squelch tail elimination has been enabled. STE is set to On for digital channel guard channels.

Default

The default for this channel depends on the Rx channel guard decode. If the Rx CG is a tone channel guard, then this field is defaulted to "On" and the user is given access to this channel. If the Rx CG is digital, this field will default to "On" and the user is denied access to this field. If the Rx CG field is empty, this field defaults to "Off" and the user is denied access.

Validity

There are not validity checks for this field.

Storage

Channel

This is a toggle field that is used to indicate whether or not the channel guard override function is available for this channel. There are two available options: "Yes"0 and "No". Yes indicates that the operator may override the channel guards for this channel using the channel guards in the channel guard table.

Prompt

Press TAB to toggle, F9 for help.

Help

Channel Guard Division: This is a toggle field that is used to indicate whether or not the operator can override the channel guards for this channel using the channel guards stored in the channel guard table. Using the TAB key, the value in this field toggles between "Yes" and "No". Yes indicates that the operator can override the channel guards on this channel.

Default

On

Validity

There is not validity test for this field.

Storage

DIVCHG

This is a numeric field that is used to enter the T90 tone (single tone signalling) or the first tone of the T99 (dual tone signalling).

Prompt

Enter T90/T99 tone. Range 250 Hz to 3000 Hz.

Help

T90/T99 Tone1: This field is used to enter the T90 (single tone signalling) tone or the first tone of the T99 (dual tone signalling). Valid tone values lay in the range of 250 Hz to 3000 Hz.

Default

Blank/Empty field.

Validity

Valid data for this field is an entry between 250 and 3000.

Storage

T90/T99

This is a numeric field that is used for entering the second tone for a T99 tone signalling.

Prompt

Enter the second tone of the T99 signalling sequence.

Help

T99 Tone2: This field is used for entering the second tone of the T99 tone signalling sequence. This field will only accept a value of 250 Hz to 3000 Hz.

Default

Blank/empty field. Write a zero to the personality.

Validity

A valid entry is between 250 and 3000. This field will not accept data if the first tone field is empty.

Storage

T90/T99

The F2 key on the control head personality screen is used for inserting modes within the list. To insert a mode, the user will position the cursor on the line where the new mode should be inserted and press the F2 key. At that time, every mode from the current line and below will be shifted down one slot. The current line will clear allowing the user to enter a new mode definition.

Note: in order to insert, the current mode must contain a valid frequency set.

The F3 key has been selected as the remove key. The purpose of this key is to remove a mode. To use the remove function, the user would position the cursor on the line/mode they wish to remove and press F3. The current mode will disappear with all following modes shifting up one mode position to fill in the space.

The signal key is used to display the second half of the mode definition screen. The reason the key is labeled "Signal" is because this portion of the screen deals primarily with the mode signalling as is shown in FIG. 52. Once this screen has been selected, the F4 key changes labels to "Scan" to indicate pressing F4 will return the user to the screen they just came from. In other words, the F4 key is used to toggle between the two portions of the mode definition screen. When this key is toggled, the name, frequency set and signal fields do not change. They still contain the previous values. All other function keys on the screen operate the same as with the "Scan" portion of the mode definition.

Note: Whenever the F4 (signal/scan) key is pressed, the cursor may leave its current field and land in the signal field.

Control Head Personality

This is the primary data entry screen when defining a personality. A personality consists of one or more MODES. A mode is a collection of channels in which the radio will operate and a set of options for the mode. These options consist of a signalling scheme, non-priority scan definition and a priority scan definition.

The screen you're in consists of one half of the mode definition. Once the information for this screen has been entered, the additional mode information can be accessed by selecting the F4 key. This key will toggle between the mode scan defaults and the modes signalling defaults.

The steps involved with defining a mode consists of the following:

1. Frequency set definition. You are required to create a frequency set to be used in the personality. This can be done by selecting the `More` key and then the `Freq` key.

2. A mode name is then entered in the name field. The name entered here will be displayed on the control head during operation.

3. Once the name has been entered, a frequency set needs to be `assigned`. You can assign a frequency set to a mode by entering the name of the frequency set in the field to the right of the mode name.

4. The final step to mode creation is to set the various scan and signalling defaults.

To save the currently save mode to disk, press the F10 key to go back to the current personality screen. You will be prompted to save the file.

You're other options available from this screen are:

F1--Select this option if you want to:

Get a detail summary of the frequency set.

Move the cursor to the frequency set field your wish to detail.

When this key is pressed, the frequency set definition screen will appear identifying the set data.

F2--Select this option if you want to:

Insert a new mode. This key will cause all modes from the cursor to the end of the personality to shift down one.

F3--Select this option if you want to:

Remove a mode.

Use this key to delete a mode by cursoring to the line of the mode you wish to delete and press this key. All modes following will be shifted up on place to fill in the space.

F4--Select this option if you want to:

Reveal the additional mode options.

F5--Select this option if you want to:

Store the currently displayed personality in the radio.

F7--Select this option if you want to:

Define the control head options.

F8--Select this option if you want to:

Create/edit frequency sets and define the personality text.

This is a numeric field that is used to identify the channel to use as the home channel for this mode. The requirement for this field is that the channel specified here is actually defined in the mode definition and that the channel contains a Rx frequency.

Prompt

Enter the channel to use as the home channel.

Help

Home Channel: This field is used to identify the channel within the frequency set to use as a home channel. The control head will go to the home channel immediately upon depression of the home key. When a channel is entered in this field, a search will be made of the frequency set to ensure that it is a valid channel and has a TX frequency.

Default

Blank/Empty

Validity

It must be a valid channel in the frequency set.

It must have a TX frequency.

Storage

GEstar

Removed in version 1.0

This is a toggle field that is used to indicate how the emergency/id mode operation of the control head is entered. Three selections are possible:

HKSW--(Hookswitch--Emergency/id declared when mike mates with hook)

PTT--(Push to talk--Emergency/id declared when PTT is depressed)

SWITCH--(Switch--Emergency/id declared by switch on control head)

Note: This field does not appear if signalling is disabled for this mode.

Prompt

Press TAB to toggle, F9 for help.

Help

Initiate Emergency/Id: This is a toggle field the is used to indicate the way the emergency/id mode of the radio is entered. By using the TAB key, the value of this field will toggle between "HKSW", "PTT" and "Switch". "HKSW" indicates that initiating emergency/id will occur when the mike mates with the hook. "PTT" indicates initiating emergency/id upon Press-To.sub.-- Talk. "Switch" initiates emergency/id when the emergency button on the control head is depressed.

Default

Switch

Validity

There is no validity check on this field.

Storage

Gestar

This is a toggle field that is used to indicate the PTT options of the indicate emergency operation. This field toggles between "ALL" and "HKSW". "All" indicates that emergency mode is activated every time the mike is keyed. "HKSW" indicates that emergency operation is activated only when the mike is keyed while it is mated with the mike-hook.

Note: This field does not appear if signalling is disabled for this mode and is only active if the value of the Initiate field is "PTT".

Prompt

Press TAB to toggle, F9 for help.

Help

Push-To-Talk Options: This is a toggle field that is used to indicate the desired mode of initiating emergency operation from the PTT. Using the TAB key, the value in this field will toggle between "All" and "Hksw". Selecting "All" will have the affect of initiating emergency operation every time PTT is keyed. Leaving "Hksw" in this field will indicate that emergency operation is only invoked when the PTT is keyed while the mike is mated with the hook-switch.

Default

Hksw

Validity

There are no validity tests for this field.

Storage

Gestar

This is a toggle field that is used to indicate whether or not the user can put the control head in the emergency mode of operation. There are two possible selections for this field: "Yes" and "No". "Yes" indicates that emergency operation is available to the user.

Note: This field does not appear if signalling is disabled for this mode.

Prompt

Press TAB to toggle, F9 for help.

Help

Emergency Operation: This is a toggle field that is used to indicate whether or not the user can put the control head in the emergency mode of operation. There are two possible selections for this field: "Yes" and "No". "Yes" indicates that emergency operation is available to the user.

Default

Yes

Validity

There are no validity checks for this field.

Storage

Gestar

This is a numeric field is used for entering the GE star ID.

Note: This field will only appear if GEstar is selected in the Signal field.

Prompt

Enter the GEstar ID. Valid ID(s) range from 1 to 16383.

Help

GEstar ID: This field is used for entering the GEstar ID. The number entered here will be transmitted if "Gestar" was selected in the Signal field. This field will only accept values in the range of 1 to 16383.

Default

Blank/Empty field.

Validity

The validity check for this field is to ensure that the ID entered here falls in the range of 1 to 16383.

Storage

Gestar

The program radio window is shown in FIG. 53. The purpose of this window is to confirm that the user does in fact want to perform this operation. The user is prompted to press the F1 key to download the personality to the radio or F2 to abort this operation.

Program Radio

From this window your options are:

F1--Select this option if you want to:

Program the radio

F2--Select this option if you want to:

Abort this operation.

FIG. 54 shows the control head options window. It is accessed by pressing the F7 (Options) key from the Control Head Personality screen. From this screen, all radio options can be defined.

Operation of this screen is similar in nature to all other windows. Normal cursor movement is from left to right, top to bottom. The only field that appears and disappears is the Keypad Sel. This field appears when the Unit Type field is "Deluxe" and disappears if the Unit Type is "Basic".

Control Head Options

This window is used to define some of the operational parameters of the control head.

From this window your options are:

F1--Select this option if you want to:

Define the siren/light combinations.

F2--Select this option if you want to:

Define the channel guard table.

F3--Select this option if you want to:

Define the function key control.

F4--Select this option if you want to:

Define the emergency signalling parameters.

F5--Select this option if you want to:

Define some operational characteristic of the radio.

F6--Select this option if you want to:

Define the keyboard definitions.

This is a toggle field that is used to indicate the control unit type. There are two possible selections for this field: "Deluxe" and "Basic". A Deluxe control head has additional features over the Basic including keypad support.

Prompt

Press TAB to toggle, F9 for help.

Help

Unit Type: This field is used to indicate the type of control head that will be the target for this personality. Using the TAB key, this field will toggle between "Deluxe" and "Basic". The deluxe control head will provide further keypad support.

Default

Whatever is selected from the setup window.

Validity

There are no validity checks for this field.

Storage

General options B

This is a toggle field that is used to indicate whether or not the keypad is enabled on the deluxe control head. There are two possible selections: "Ena" and "Dis". "Ena" is selected to enable the keypad.

Note: This field will only appear if the Unit Type is "Deluxe".

Prompt

Press TAB to toggle, F9 for help.

Help

Keypad Select: This is a toggle field used to enable or disable the keypad on the deluxe model of the control head. Disabling the keypad will have the affect of preventing the user from selecting some of the keypad functions. Using the TAB key, this field will toggle between "Ena" (Enabled) and "Dis" (Disabled).

Default

Ena

Validity

There are not validity checks for this field.

Storage

General Options B

This is a toggle field that is used to indicate whether or not alert tones should be enabled on the control head. There are three possible selections for this field: "None", "Ramp", and "All". "None" is used to indicate alert tones are disabled on the control head. "Ramp" is used to indicate alert tones will be generated whenever the ramp keys are depressed. "All" is selected to indicate alert tones will be generated whenever any of the keys on the control head are depressed.

Prompt

Press TAB to toggle, F9 for help.

Help

This is a toggle field that is used to indicate whether or not the control head should generate an audible feedback on key depression. Using the TAB key, this field will toggle between three possible selections: "None", "Ramp", and "All". "None" is used to indicate alert tones are disabled on the control head. "Ramp" is used to indicate alert tones will be generated whenever the ramp keys are depressed. "All" is selected to indicate alert tones will be generated whenever any of the keys on the control head are depressed.

Default

All

Validity

There are no validity checks for this field.

Storage

General

This is a toggle field that is used to indicate whether or not the control head scans with the mike off hook. There are two possible selections for this field: "Scan" and "NoScn". "Scan" is selected to indicate that the control head should perform the scanning functions with the mike off-hook. "NoScn" will have the affect of disabling scan when the mike is lifted.

Prompt

Press TAB to toggle, F9 for help.

Help

Off Hook Scan: This is a toggle field that is used to indicate whether or not the control head scans with the mike off hook. There are two possible selections for this field: "Scan" and "NoScn". "Scan" is selected to indicate that the control head should perform the scanning functions with the mike off-hook. "NoScn" will have the affect of disabling scan when the mike is lifted.

Default

No Scan

Validity

There are no validity checks for this field.

Storage

General options B

This is a toggle field that is used to indicate whether or not to enable the backlighting of the LCD display. This field toggles between "On" and "Off".

Note: Toggling this field will also have the affect of toggling the B-Lite Sav field On and Off.

Prompt

Press TAB to toggle, F9 for help.

Help

Backlight Display: This is a toggle field that is used to indicate whether or not back-lighting of the LCD display is desired. Using the TAB key, the values in this field will toggle between "On" and "Off". Selecting "Off" will have the affect of disabling the backlight on the control head's LCD display and LED indicators.

Default

On

Validity

There are no validity tests for this field.

Storage

General options A

This is a toggle field that is used to indicate whether or not the control head should have the backlight level when power is removed. There are two possible selections for this field "Yes" and "No".

Note: This field will only appear if the Backlight option is enabled.

Prompt

Press TAB to toggle, F9 for help.

Help

Backlight Save: This is a toggle field that is used to indicate whether or not the control head should remember the state/level of backlighting when power is removed. Selecting "No" here will cause the control head to display the default backlighting level whenever power is removed and reapplied.

Default

Yes

Validity

There are no validity test for this field.

Storage

General options A

This is a toggle field that is used to indicate whether or not the control head should decode the receive channel guard or the radio. The two possible selections are "S825" and "Radio". Selecting S825 will cause the write routine to convert the Rx channel guards into the S825 format and stored them in the RDIV section of the prom. Selecting "Radio" will indicate that the writes should use the Rangr/Delta Rx channel guard calculation and store the values in with the channel data area of the prom.

Prompt

Press TAB to toggle, F9 for help.

Help

Rx Channel Guard Decode: This is a toggle field that is used to indicate whether or not the control head should decode the received channel guards. Using the TAB key, the value in this field will toggle between "S825" and "Radio". Selecting "S825" will have the affect of causing the control head to decode received channel guards.

Default

Radio

Validity

There are no validity test for this field.

Storage

General

This is a toggle field that is used to set the minimum volume level for the control head. The two possible selections are: "Set" and "Off". "Set" is used to indicate that volume cannot be ramped so low that it is off. "Off" on the other hand, will have the affect of allowing the user to ramp the volume to its off position.

Prompt

Press TAB to toggle, F9 for help.

Help

Minimum Volume: This is a toggle field that is used to set the minimum volume level for the control head. The two possible selections are: "Set" and "Off". "Set" is used to indicate that volume cannot be ramped below 1. "Off" on the other hand, will have the affect of allowing the user to ramp the volume to its off position.

Default

Off

Validity

There are no validity tests for this field.

Storage

General options A

This is a numeric field that is used to set the number of sections before the display(s) times out in one second intervals.

Prompt

Enter the display timeout. Range is 1 to 5 secs.

Help

Display Timeout: This field is used to set the mode/volume display timeout value. This field will only accept values within the range of 1 to 5 seconds. Entering a value here will cause the non default displays to remain active for the time period specified.

Default

Validity

To ensure that the value entered is between 1 and 5.

Storage

General Options A

This is a toggle field that is used to indicate how the control head should handle channel deletions from the scan list. The two possible selections are: "Temp" and "Store". "Temp" is used to instruct the control head that channel delections from the scan list should only be of a temporary nature. "Store" indicates that the channel deletion is of a permanent nature. On a temporary deletion, the channel is restored when power is recycled or the mode is changed.

Prompt

Press TAB to toggle, F9 for help.

Help

Delete Key: This is a toggle field that is used to indicate how the control head should handle channel deletions from the scan list. The two possible selections are: "Temp" and "Store". "Temp" is used to instruct the control head that channel deletions from the scan list should only be of a temporary nature. "Store" indicates that the channel deletion is of a permanent nature. On a temporary deletion, the channel is restored when power is recycled or the mode is changed.

Default

Store

Validity

There are no validity tests for this field.

Storage

General Options B

This is a toggle field that is used to indicate whether or not the ramp keys on the control head should stop when the end is reached, or wrap around to the beginning. There are two possible selections: "Yes" and "No". "Yes" will cause the control head to wrap around on the ramping function.

Prompt

Press TAB to toggle, F9 for help.

Help

Wrap Ramps: This is a toggle field that instructs the control head to wrap around on the ramping functions. Using the TAB key, the value in this field will toggle between "Yes" and "No". "Yes" will enable the wrap function on the ramp keys.

Default

Yes

Validity

There are no validity test for this field.

Storage

General Options B

This is a toggle field that is used to indicate whether or not the control head should permit the user to perform a display/keypad test operation. The two possible selections are "Ena" and "Dis". "Ena" will have the affect of allowing the user to perform a test of the LEDs, LCD and keypad.

Prompt

Press TAB to toggle, F9 for help.

Help

Display Test Mode: This is a toggle field that is used to indicate whether or not the control head should permit the user to perform a display/keypad test operation. The two possible selections are "Ena" and "Dis". "Ena" will have the affect of allowing the user to perform a test of the LEDs, LCD and keypad.

Default

Dis

Validity

There are no validity tests for this field.

Storage

General Options B

This is a toggle field that is used to indicate whether or not the user has to hold the power off button for one second in order to remove power from the control head. This purpose for this is to prevent accidental power removal. The two possible selections are: "1 Sec" and "None". "1 Sec" is used to indicate that the user will have to hold the power off key for one second in order to remove from the control head.

Prompt

Press TAB to toggle, F9 for help.

Help

Power Off Delay: This is a toggle field that is used to indicate whether or not the user has to hold the power off button for one second in order to remove power from the control head. This purpose for this is to prevent accidental power removal. The two possible selections are: "1 Sec" and "None". "1 Sec" is used to indicate that the user will have to hold the power off key for one second in order to remove power from the control head.

Default

None

Validity

There are no validity tests for this field.

Storage

General

This is a toggle field that is used to indicate whether or not a hang time before scan resume applies to this channel. The two options are: "On" and "Off". On indicates that a hang time will be applied before resuming scan after a transmission.

Prompt

Press TAB to toggle, F9 for help.

Help

Hang Time: This is a toggle field that is used to indicate whether or not a hang time should be applied before resuming scan after a transmit. Using the TAB key, the value in this field will toggle between "On" and "Off". Off indicates that scan will resume immediately after release of the PTT.

Default

On

Validity

There are no validity checks for this field.

Storage

Scan

This is a numeric field that is used to specify the carrier control timer delay. This field will only accept a 1 or 2.

Prompt

Enter in minutes. Range 1 or 2.

Help

CCT: This field is used to indicate the amount of time before the carrier control timer (if activated) drops the transmission. A valid entry will be in the range of 1 to 2.

Default

1

Validity

VHF and UHF will be in the range of 1 and 3

Storage

Channel--(On per channel basis if channel's CCT is On.)

FIG. 55 shows the Siren/Lights windows. It is invoked by selecting the F1 (Siren) key from the control head options screen. The purpose of this window is to give the user the ability to define siren and light combinations associated with the Wail, Yelp and SL keys.

Siren/Lights

The purpose of this window for definition of specific siren and light combinations. Once these combinations have been defined, they can then be assigned to the various programmable keys on the control head.

Each row in the window is setup for defining a key. For example: The first row is labeled `Wail`. This means the everything on that row applies to the `Wail` definition. In a like manner, the same applies for `Yelp` and all of the `S/L`

There are twelve possible entries for a Siren/Light combination. Starting from the left is the `S` (Siren) column. Here you should enter the Siren number (1-5) you wish generated for the `Wail` definition.

There are nine light columns that are used to indicate which light(s) are to be activated with this siren. Chose the corresponding light by enabling the field.

The Can (Cancel) field is used to indicate whether or not selection of this siren/light combination will cancel or sum the currently active combination.

The Mom (Momentary) field is used to indicate whether or not this combination is active only while the key is depressed.

This is a numeric field that is used to identify which siren to use with this key. There are six possible choices for this field. They are:

0. No siren--Light only

1. Wail

2. Yelp

3. Manual

4. Hilo

5. Air Horn

To select one of the six choices, the user would enter a number between 0 and 5 corresponding to the siren desired.

Prompt

Enter desired siren. Range 0 to 5.

Help

Siren: This field is used to identify the siren that is to be produced when this key is depressed. The possible choices are: 0--No siren, 1--Wail, 2--Yelp, 3--Manual, 4--Hilo, and 5--Air Horn.

Default

Wail--1

Yelp--2

All others--0

Validity

A valid entry would be within the range of 0 and 5.

Storage

Keypad

Removed in version 1.0

These are toggle fields that are used to indicate which light(s) are to be activated upon activation of this key. There are two possible selections: `*` and ` `. The `*` is selected to indicate that the light is to be enabled upon activation of the key.

Prompt

Press TAB to toggle, F9 for help.

Help

Lights 1-9: This is a toggle field that is used to indicate whether or not this light is to be enabled upon activation of this key. Using the TAB key, this field will toggle between a `*` and a ` `. Selecting the `*` has the affect of activating or enabling this light.

Default

Blank

Validity

There are no validity test for this field.

Storage

This is a toggle field that is used to indicate whether or not this siren/light combination cancels the previously activated siren/light combination. The two possible options are: "Yes" and "No". Yes indicates that this siren light combination when activated will cancel (suppress) the existing combination.

Prompt

Press TAB to toggle, F9 for help.

Help

Cancel: This is a toggle field that is used to indicate whether or not activation of this siren/light combination will cancel (suppress) any currently active combination. Using the TAB key, the value in this field will toggle between a "Yes" and "No". A Yes indicates that this combination will suppress any currently active siren. A No indicates it will sum (include) any active S/L combination.

Default

No

Validity

There are no validity tests for this field.

Storage

Keypad definitions

This is a toggle field that is used to indicate whether or not activation of this siren/light combination is momentary or not. The two possible selections are: "Yes" and "No". Yes indicates that this S/L is active only while the key is depressed.

Prompt

Press TAB to toggle, F9 for help.

Help

Momentary: This is a toggle field that is used to specify the nature of this siren/light combination. Using the TAB key, the value in this field will toggle between "Yes" and "No". A Yes selection indicates that this combination is only active while the key is depressed and will cancel once the key is released.

Default

No

Validity

There are no validity test for this field.

Storage

Keypad definitions

The Channel Guard Table window, as illustrated in FIG. 56, is implemented to give the user the ability to define up to 14 channel guard. These channel guards can then override the existing channel guard during operation of the control head. This is effect will give each channel the ability to select a channel guard out of a possible 16.

Normal cursor progression is left to right, top to bottom. When the screen is refreshed, the cursor will be placed in the ID field. Here the user enters a 3 character mnemonic for the channel guard and advances to the next field. Here they enter the Tx channel guard. During the creation of a channel guard table, once the tx channel guard is entered it will automatically be copied over to the rx side.

The Ste field will operate in a manner similar to the channel definition. If the Rx channel guard is a tone channel guard, the Ste will default to `Y` and the user will not be allowed to change it. If a digital channel guard is entered, the Ste field is defaulted to `Y` and the user will be permitted to modify the field. If no Rs channel guard is entered, the field will not be accessible.

This window is used to define the 14 channel guard for the control head. Once defined, these channel guards can be used to override the existing channel guard for a specific channel.

The screen operates left to right, top to bottom, beginning with division 1. There are three components for each channel guard definition: an ID, a Tx channel guard and an Rx channel guard. The ID is a three character alphanumeric that will be displayed on the control head to reference this channel guard. The Tx and Rx channel guards may be digital or tone channel guards.

This is a display only field used to indicate which of the fourteen divisions the user is modifying.

This is an alphanumeric field used to enter the 3 character mnemonic for the channel guard. It will accept any alphanumeric character (lower case excluded) and the following special symbols: @[] /.-+<>*'&$%#"!?=;:

Note: This field will convert to upper case all lower case characters.

Prompt

Enter the name of this channel guard.

Help

ID: This field is used to enter the name of this channel guard. The name entered here is used to reference this channel guard during operation of the control head. This field will accept any alphanumeric character (excluding lower case), spaces and the following special symbols: @[] /.-+<>*'&$%#"!?=;:

Default

Blank/Empty field

Validity

A valid entry will only contain the characters described above.

Storage

RDIVASCII

This is a alphanumeric field used to enter the transmit channel guard for this channel. This field accepts digital and tone channel guard codes. Tone channel guards are identified by the placement of a decimal point within the field. Digital channel guard are identified by the lack of a decimal point. For example:

023--Digital Channel Guard

67.0--Tone Channel Guard

When the transmit channel guard is entered, it is automatically copied to the receive channel guard providing it has not yet been defined. This means that once the channel has been defined, the transmit channel guard will not be copied to the receive side regardless of whether or not the field is empty.

Prompt

Enter the desired tx channel guard code.

Help

Transmit Channel Guard: There are two types of channel guard encoding available for this control head: digital and tone. Tone channel guard encoding is identified by the placement of decimal point within the field. For example: 67.0 identifies a tone channel guard of 67 Hz. Valid tone channel guards lay in the range of 67.0 to 210.7 Hz. Digital channel guards decoding is identified by the lack of a decimal point. An example of digital channel guard codes are 023, 047, 315 etc. Valid digital channel guard codes can be found in Appendix 1 of the S825 Control Head programming user guild.

Default

There are no defaults for this field.

Validity

A valid check for this field are as follows:

1. If tone channel guard--range is 67.0 to 210.7

2. If digital channel guard--must be included in chngrd.h table.

Storage

This is a alphanumeric field used to enter the receive channel guard for this channel. This field accepts digital and tone channel guard codes. Tone channel guards are identified by the placement of a decimal point within the field. Digital channel guard are identified by the lack of a decimal point. For example:

023--Digital Channel Guard

67.0--Tone Channel Guard

When the transmit channel guard is entered, it is automatically copied to the receive channel guard providing it has not yet been defined. This means that once the channel has been defined, the transmit channel guard will not be copied to the receive side regardless of whether or not the field is empty.

Prompt

Enter the desired rx channel guard code.

Help

Receive Channel Guard: There are two types of channel guard encoding available for this control head: digital and tone. Tone channel guard encoding is identified by the placement of decimal point within the field. For example: 67.0 identifies a tone channel guard of 67 Hz. Valid tone channel guards lay in the range of 67.0 to 210.7 Hz. Digital channel guards decoding is identified by the lack of a decimal point. An example of digital channel guard codes are 023, 047, 315 etc. Valid digital channel guard codes can be found in Appendix 1 of the S825 Control Head programming user guild.

Default

The default for this field is the tx channel guard code.

Validity

A valid check for this field are as follows:

1. If tone channel guard--range is 67.0 to 210.7

2. If digital channel guard--must be included in chngrd.h table.

This is a toggle field that is used to indicate whether or not squelch tail elimination is to be enabled. It toggles between `Y` and `N` with the `Y` value indicating that Ste is enabled. Normally, access to this field is denied unless a digital or inverted rx channel guard is entered.

Prompt

Press TAB to toggle, F9 for help.

Help

Squelch Tail Elimination: This field is used to indicate whether or not squelch tail elimination is to be enabled on this division. By pressing the TAB key, the value within the field will toggle between `Y` and `N`. A `Y` value indicates that squelch tail elimination has been enabled.

NOTE: Squelch tail elimination must be enabled for digital channel guards.

Default

The default for this field depends on the Rx channel guard decode. If the Rx CG is a tone channel guard, then this field is defaulted to `Y` and the user is granted access to this field. If the Rx CG is either digital or inverted, this field will default to `Y` and the user is denied access to this field. If the Rx CG field is empty, this field defaults to `N` and the user is denied access.

Validity

There are no validity checks for this field.

Storage

RDIV

The FNC Button window (Function key definitions) is accessed by depressing the F3 (FNC) key from the control head options window. The screen shown in FIG. 57 is used to define the primary, secondary and tertiary functions of the function keys.

This window has three input fields. When the window is opened, the cursor is placed in the primary field. Once the user makes a selection, the cursor progresses to the secondary field. Once that selection is made, the cursor then advances to the tertiary field.

There are no final edit checks for this window.

Note: The tertiary field is not to be displayed for version 1.0

Function Control Button

This window is used for defining the primary, secondary and tertiary function of the FNC key on the S825 control unit. The primary function of the function keys is activated whenever the function keys are depressed. The secondary function is activated when the function key is depressed in combination with the FNC key and the tertiary functions are activated when the (Key) is pressed. The primary function is the normal state of the keypad. The secondary function is activated when the FNC key is pressed once. The tertiary function is activated when the FNC key is pressed twice in a row.

This is a toggle field used to indicate the primary function of the function keys. There are four possible choices: "Siren", "DTMF", "Status" and "Disable". "Siren" is selected to indicate that the primary function of the function keys are enable the siren. "DTMF" is used to indicate that the control head is to generate DTMF when the function keys are depressed. By selecting "Status", the control head will generate one of the various status messages and "Disable" will disable the function key.

Default

Siren

Validity

There are no validity checks for this field.

Storage

General options A

This is a toggle field used to indicate the primary function of the function keys. There are four possible choices: "Siren", "DTMF", "Status" and "Disable". "Siren" is selected to indicate that the primary function of the function keys are enable the siren. "DTMF" is used to indicate that the control head is to generate DTMF when the function keys are depressed. By selecting "Status", the control head will generate one of the various status messages and "Disable" will disable the function key.

Note: Status is not to be displayed for version 1.0

Prompt

Press TAB to toggle, F9 for help.

Help

Secondary: This is a toggle field used to indicate the secondary function of the function keys. There are four possible choices: "Siren", "DTMF", "Status" and "Disable". "Siren" is selected to indicate that the secondary function of the function keys are enable the siren. "DTMF" is used to indicate that the control head is to generate DTMF when the function keys are depressed. By selecting "Status", the control head will generate one of the various status messages and "Disable" will disable the function key.

Default

DTMF

Validity

There are no validity checks for this field.

Storage

General options A

This is a toggle field used to indicate the primary function of the function keys. There are four possible choices: "Siren", "DTMF", "Status" and "Disable". "Siren" is selected to indicate that the tertiary function of the function keys are enable the siren. "DTMF" is used to indicate that the control head is to generate DTMF when the function keys are depressed. By selecting "Status", the control head will generate one of the various status messages and "Disable" will disable the function key.

Prompt

Press TAB to toggle, F9 for help.

Help

Secondary: This is a toggle field used to indicate the tertiary function of the function keys. There are four possible choices: "Siren", "DTMF", "Status" and "Disable". "Siren" is selected to indicate that the tertiary function of the function keys are enable the siren. "DTMF" is used to indicate that the control head is to generate DTMF when the function keys are depressed. By selecting "Status", the control head will generate one of the various status messages and "Disable" will disable the function key.

Default

Status

Validity

There are no validity checks for this field.

Storage

General Options

FIG. 58 illustrates the Emergency signalling window and is accessed by pressing the F4 (Signal) key from the Control head personality screen. The purpose of this screen is to define the variables associated with emergency signalling.

When this window is opened, the cursor will be located in the Emerg Tone 1 field. Because all the fields start in the same column, normal cursor progression will be top to bottom. Because of the nature of this window, no final edit check of the window is needed.

Emergency Signalling

The purpose of this window is to define the parameters of the emergency signalling schemes. These parameters consist of the tone lengths and delays for T90 and T99 and the GE star delays.

This is a numeric entry field that is used to define the T90 emergency tone or the first tone of the emergency T99 tone set. This tone will be generated when the user keys an emergency on the control head in a mode that has T90/T99 selected as the signalling desired.

Prompt

Valid tones range 250-3000 Hz or no tone.

Help

Emergency Tone 1: This field is used to define the T90 emergency tone or the first tone of the emergency T99 signalling. This tone will be generated when an emergency is keyed on a mode that has T90/T99 signalling selected. A valid tone entry is in the range of 250 to 3000 Hz.

Default

Blank/Empty field.

Validity

A valid entry will be in the range of 250 and 3000.

Storage

General options

This is a numeric field used to declare the length of the T90/T99 Emergency Tone

1. The value entered here determines the length of time the control head will generate the above tone.

Prompt

Valid lengths range from X to XXXX.

Help

Emergency Tone 1 Length: This field is used to declare the length of time the control head should generate Emergency Tone 1. Valid tone lengths range from 0 to 3000 Msecs in 20 Msecs increments.

Default

1000

Validity

A valid tone length is in the range of 00 to 3000.

Storage

General options

This is a numeric entry field that is used to define second tone of the emergency T99 tone set. This tone will be generated when the user keys an emergency on the control head in a mode that has T90/T99 selected as the signalling desired.

Prompt

Valid tones range 250-3000 Hz.

Help

Emergency Tone 2: This field is used to define the second tone of the emergency T99 signalling. This tone will be generated when an emergency is keyed on a mode that has T90/T99 signalling selected. A valid tone entry is in the range of 250 to 3000 Hz.

Default

Blank/Empty field.

Validity

A valid entry will be in the range of 250 and 3000 or no tone.

Storage

General options

This is a numeric field used to declare the length of the T90/T99 Emergency Tone 2. The value entered here determines the length of time the control head will generate the above tone.

Prompt

Valid lengths range from 0 to 3000.

Help

Emergency Tone 2 Length: This field is used to declare the length of time the control head should generate Emergency Tone 1. Valid tone lengths range from 0 to 3000 Msecs in 20 Msecs increments.

Default

3000

Validity

A valid tone length is in the range of 0 to 3000.

Storage

General options

This is a numeric field that is used to indicate the amount of time the control head should delay between generation of the T99 tones.

Prompt

Valid delays range from 0 to 3000 Msecs.

Help

Tone Delay: This is a numeric field that is used to indicate the amount of time the control head should delay between generation of the T99 tones. This field will only accept values in the range of 0 to 3000 Msecs in 20 Msec increments.

Default

1000

Validity

A valid entry will fall between 0 and 3000 in 20 Msec increments.

Storage

General Options

This is a numeric field used to indicate the number of times the control head is to generate a GEstar ID once the emergency mode of operation has been activated.

Prompt

Valid range is 1 to 255

Help

Repeat Count: This is a numeric field used to indicate the number of times the control head is to generate a GEstar ID once the emergency mode of operation has been activated. Acceptable values are in the range of 1 and 255.

Default

1

Validity

A valid entry is in the range of 1 and 255.

Storage

Gestar

This field is used to indicate the delay between transmissions of the GEstar ID when the emergency mode of operation has been activated.

Prompt

Acceptable values range 1-60.

Help

Delay Time: This field is used to indicate the delay between transmissions of the GEstar ID when the emergency mode of operation has been activated. A valid entry is in the range of 1 to 60 secs in one second increments.

Default

1

Validity

A valid entry will fall in the range of 1 and 60.

Storage

Gestar

This is a numeric field that is used to specify the transmit attack delay prior to sending the GEstar ID.

Prompt

Acceptable values range from 50 to 1275.

Help

Attack Delay: This is a numeric field that is used to specify the transmit attack delay prior to sending the GEstar ID. Acceptable values are in the range of 50 to 1275.

Default

50

Validity

A valid entry is in the range of 50 and 1275.

Storage

Gestar

This is a toggle field that is used to indicate whether or not GEstar or T90/T99 transmissions occur on the home channel or current channel. The two possible selections are "Yes" and "No". Yes indicates the GEstar and T90/T99 transmissions occur on the home channel.

Prompt

Press TAB to toggle, F9 for help.

Help

Revert to home: This is a toggle field that is used to indicate whether or not the control unit should revert to the home channel when performing a GEstar or T90/T99 transmission. Using the TAB key, the value in this field will toggle between a "Yes" and "No". Selecting a Yes will have the affect of causing the control unit the transmit all GEstar and T90/T99 transmissions on the home channel.

Default

Blank/Empty field.

Validity

A valid entry will be in the range of 250 and 3000.

Storage

General options

The radio options screen is entered by pressing the F5 (Radio) key from the Control head options screen shown in FIG. 59. This screen provides for defining some of the options and characteristics of the radio attached to the control head. These options will affect control head/ratio interfacing.

Radio Options

The purpose of this window is to define the radio specific options. Basically, these consist of parameters specific to the type of radio connected to the control head.

This is a toggle field that is used to indicate whether or not the radio supports channel downloading. The two possible selections are: "Ena" and "Dis". Selecting "Ena" will indicate that the control head can download channel data to the radio.

Prompt

Press TAB to toggle, F9 for help.

Help

Radio Download: This is a toggle field that is used to indicate whether or not the radio supports channel downloading. The two possible selections are: "Ena" and "Dis". Selecting "Ena" will indicate that the control head can download channel data to the radio.

Default

Ena

Validity

There are no validity tests for this field.

Storage

General

This is a toggle field that is used to indicate the number of channels/mode that the control head will need to support. The two possible selections are: 16 and 32.

Prompt

Press TAB to toggle, F9 for help.

Help

Max Channels/Mode: This is a toggle field that is used to indicate the number of channels/mode that the control head will need to support. The two possible selections are: 16 and 32. "16" is selected to indicate that the radio attached is either a Rangr or a 16 channel Delta. "32" is selected to indicate a 32 channel Delta.

Default

16

Validity

There are no validity tests for this field

Storage

This is a numeric field that is used to indicate the number of seconds the control head should delay between VRS beeps. The control head will beep at a periodic rate to audibly inform the user that the VRS is "On". The value entered here determines that rate.

Prompt

Acceptable value 1 to 30.

Help

VRS Beep Interval: This is a numeric field that is used to indicate the number of seconds the control head should delay between VRS beeps. The control head will beep at a periodic rate to audibly inform the user that the VRS is "On". The value entered here determines that rate. Acceptable values range from 1 to 30 Secs.

Default

1

Validity

A valid entry is in the range of 1 and 30.

Storage

This is a toggle field that is used to indicate whether or not the VRS is forced to scan. There are two possible selections: "Yes" and "No". A "Yes" indicates that the VRS is forced to Scan.

Prompt

Press TAB to toggle, F9 for help.

Help

VRS Forced Scan: This is a toggle field that is used to indicate whether or not the S825 control unit is forced to scan when the VRS is enabled. There are two possible selections: "Yes" and "No". A "Yes" indicates that the S825 control unit will enable channel scan when the VRS is active.

Default

No

Validity

There are no validity test for this field.

Storage

This is a toggle field that is used to indicate whether or not this control head is equipped for dual control. The two possible selections are: "Yes" and "No". A "Yes" selection indicates that the radio system is equipped for dual control.

Prompt

Press TAB to toggle, F9 for help.

Help

Dual Control: This is a toggle field that is used to indicate whether or not this control head is equipped for dual control. The two possible selections are: "Yes" and "No". A "Yes" selection indicates that the radio system is equipped for dual control.

Default

No

Validity

There are no validity tests for this field.

Storage

FIG. 60 shows the deluxe keypad definition window and is accessed by selecting the F6 (Key) from the control head options window. The F6 (Key) will bring up either the basic or the deluxe window based upon the unit type field. If the unit type field is "Deluxe" this window will be pulled up. If the unit type field is "Basic" the following screen will appear.

Note: Refer to section 2.1.0 for a discussion of this screen.

FIG. 61 shows the basic keypad definition screen and is accessed by selecting the F6 (Key) from the control head options screen. This window is conditional on the state of the unit type field under the control head options window.

Note: Refer to section 2.1.1 for a discussion of this window.

FIG. 62 illustrates what happens when the F8 `More` key is depressed.

Control Head Personality

This is the primary data entry screen when defining a personality. Basically, a personality consists of one or more MODES. A mode is a collection of channels in which the radio will operate and a set of options for the mode. These options consist of a signalling scheme, non-priority scan definition and a priority scan definition.

You're other options available from this screen are:

F2--Select this option if you want to:

Create/Edit/Delete a frequency set in the pool.

F4--Select this option if you want to:

Edit the text associated with this personality.

FIG. 63 shows the currently defined frequency set screen and is accessed by pressing the F2 key from the Control Head personality screen. This screen operates in a similar fashion as the current personality screen.

Current Defined Frequency Sets

This screen shows the currently defined frequency sets residing in the data base. Immediately below the title is the directory in which the currently defined frequency sets reside. This directory is the same directory from which the program was run.

From this window your available options are:

F2--Select this option if you want to:

Change/Edit a frequency set.

F4--Select this option if you want to:

Create a new frequency set.

F5--Select this option if you want to:

Delete a currently defined frequency set.

FIG. 64 shows the text window and is accessed by pressing the F4 (Text) key from the Control Head Personality screen. The purpose of this window is to let the user define a few lines of text that will be stored with this personality on disk. It also displays the software version number of the control head last programmed with this personality. Also, the last data this personality was downloaded to a radio is captured and saved.

Text Window

The purpose of this window is to define/create a few lines of text to be saved with this personality on disk. This text can be any text you desire. Also, you will notice a field for software version and last programmed date. These fields will be filled in once this personality is downloaded into a control head. By referring back to this window, you will have a record of when the control head was programmed and the current software version of the control head.

This is a display only field that is used to indicate the version number of the software residing in the control head. This field gets filled in when this personality is written to the control head.

This is a display only field that identifies the data that this personality was written to the control head. It gets filled in when the personality is written.

There are 8 character fields that are used to enter user defined text to be stored on disk with the personality. This text is not written to the control head, just the file.

Prompt

These fields are user defined.

Help

Text Field: This field is used for entering user defined text. This text is saved on disk with the personality for later review. Enter addresses, comments or any other special notes on this personality.

Default

Blank/Empty

Validity

There are no validity tests with this field.

Storage

None

FIG. 65 illustrates the save personality window and is used to enter the name by which this personality is to be saved. Whenever the user tries to exit the personality, this window appears.

Save Personality

This is the save personality window and is used to confirm exiting of the control head personality screen. The displayed fields are the source file name, the destination file name. The source file name is the name that this personality was originally stored under. The destination field is for entering the name of the file that this personality should be stored to.

From this window you have the following options available:

F1--Select this option if you want to:

Have the personality saved and then exit.

F2--Select this option if you want to:

Exit without saving the personality.

F10--Select this option if you want to:

Continue editing the personality.

This is a display only field that is used to indicate the file from which this personality was originally opened.

This is an alphanumeric field that is used to specify the destination file name on the personality just created. Here the user enters a file name.

Prompt

Enter the destination file name.

Help

Destination File Name

This field is used to enter the destination file name for the personality just created. When this personality is saved to disk, it will be saved under the name specified here.

Default

The source personality name. A new personality will default to NEW.[Extension]

Validity

A valid entry will pass the following conditions:

1. That the name is a valid DOS file name.

2. If the name is different than the source and a personality with the same destination name exists, the user must be given the option to overwrite.

Storage

None

FIG. 66 shows the program radio window and is accessed by selecting the F5 (Program) key from the current personality screen. This window provides for entering the name of the personality to be used for programming the personality.

Window Help

Program Radio

This window is used to confirm the program radio operations. Selecting F1 will cause the program to download the file identified into the radio.

From this window your available options are:

F1--Select this option if you want to:

Program the radio with the personality specified.

F2--Select this option if you want to

Abort this operation.

Filename

This file is used to enter the name of the personality to be used for the program operation.

Prompt

None

Help

File Name: Enter the file name of the personality to be used for programming the radio. This field will accept 8 characters for a valid file name.

Default

The highlighted name.

Validity

A valid entry will pass the following conditions:

1. The entry is valid DOS file name.

2. The personality actually exists.

Storage

FIG. 67 shows the read radio window and is accessed by selecting the F6 (Read) key from the current personality window. The purpose of this window is to confirm the read operation selection.

Window Help

Read Radio

The screen shown in FIG. 68 is used to confirm the read radio operation. Selecting F1 will cause the control head to send its personality up to be stored in the file name specified.

From this window your available options are:

F1--Select this option if you want to:

Read the radio in to the personality specified.

F2--Select this option if you want to:

Abort this operation.

Filename

This file is used to enter the name of the personality to be used for the read operation.

Prompt

None

Help

File Name: This is a character field that is used to enter the name under which the personality is to be stored once read from the control head.

Default

Blank/empty

Validity

A valid entry will pass the following conditions:

1. The entry is valid DOS file name.

2. If the personality exists, the user must be given the overwrite option.

Storage

None

Several overall design considerations for the user interface provided by the preferred embodiment of the present invention should now be evident.

Firstly, a "top-down" approach is followed as much as possible so that tasks are defined in terms of subtasks, subtasks are defined in terms of sub-subtasks, etc. In this way, every component is broken down as far as possible to simplify each of the tasks actually selected by the user--and also to create additional flexibility by permitting each task to be performed more or less independently. In terms of actually selecting radio programming personality file 86 parameters, the "top-down" approach means that each programming task is defined at its lowest level as an input field--and the user interface provided by the present invention is truly field oriented (e.g., by providing field level help windows, field specific prompts, and the like).

Each input field in the preferred embodiment is preferably specified in terms of the type of data (logical, numeric or characters), number of characters which are to fill the field, the numeric range of the field if the field is numeric, and many other parameters (as will become apparent shortly). Range checking is performed automatically on all fields having limited ranges to prevent system 50 from accepting invalid data. Also, many or most input fields in the preferred embodiment preferably have default values which are used to "fill in" the field when it is first displayed. This permits the user to either accept the default value (e.g., by a single keystroke) or change the field contents by overwriting (editing) the default value to obtain a new desired value.

The preferred embodiment uses several basic types of screen display formats:

full list screen;

full format screen;

dual/split screen;

text screen; and

pop up window.

A full list screen in the preferred embodiment does not support field editing, and is used to list a number of fields from which the user may select one field. Preferably, a reverse video bar is used to highlight the current selection (the cursor and/or tab keys are used to move the video bar to other fields). Only when a function key is depressed does the selection actually take place. In a full list screen, the page up key may be used to page upward through the list. The page down key advances through the list until the bottom of the list is encountered. In the preferred embodiment, the root screen 102 is an example of a full list screen.

In the preferred embodiment, the channel data screen 116 is an example of a full format type screen. Unlike the full list screen, the full format screen provides for editing individual fields displayed within the screen. The information contained within the screen can thus be deleted or changed. In the format screen, the left and right cursor keys are used as editing keys (to move the cursor left and right within a field) rather than as field selection keys. The up and down cursor keys are used to select fields, and the Tab key may be used to select field values (e.g., by toggling logical values). It is preferable for improving readability that a screen title be displayed at the very top of each format screen with a blank line directly beneath it; and that a one-line user prompt message be displayed at the bottom line of the format screen with a blank line directly above it. In addition, the one-line user prompt message displayed at the bottom of each display format actually changes as the cursor is moved from one input field to another--thereby prompting the user with a one line description of the type of information the "current" field contains. Thus, the user only needs to depress the F9 help key if he wants a more detailed explanation of the field contents (in the preferred embodiment, display format-level help text is also available by depressing Shift-F9).

In the preferred embodiment, the number of input fields per screen is generally limited to five to ten in order to reduce clutter and the resulting user confusion and intimidation it can cause. The screen formats are also laid out to provide good balance. Good balance helps prevent user anxiety (by facilitating quick visual scanning), directs the user's attention to important areas of the screen and adds to the overall pleasing appearance of the display.

Split screens provide additional flexibility by displaying two half-screens containing related information. There are at least three possibilities for split screen displays: each half screen is a listing screen (permitting the user to select but not edit the fields in the half screens); each half screen is a format screen (so the user can edit the fields displayed in each); or one half screen is a listing screen which allows the user to select the data to be edited in the other (format) screen.

In this latter (one listing half screen, one format half screen) configuration, the listing screen is preferably the left-most window (half screen), and the right-most window (half screen) is a half format screen. On initial entry into the screen, the cursor is placed in the listing half screen with a list of entries on display. A reverse video bar is placed over the first entry in the list. The format half window is used to break out detailed fields associated with the item highlighted in the left-hand list half screen. As the user cursors through the list, the format half screen instantaneously displays changing information corresponding to the current list selection. Once the user has selected an item from the list he wishes to modify the information corresponding to, he may issue a "switch" command (e.g., by depressing the F1 key) to move the cursor is in the format half screen. Once the cursor is in the format half screen, the user may edit the fields displayed there and save any changes made. Another switch command is used to return to the list half screen. This split screen configuration is especially useful when working with sets of sets.

In the preferred embodiment, the setup display format 104 is an example of a split screen display format. The left-hand half screen of this display format 104 is a listing screen displaying two fields from which the user selects; and the right-hand half screen is another listing screen displaying a set of frequency ranges from which the user selects one field.

Full text display formats are used in the preferred embodiment to display files of formatted text. For example, when the user selects printing a personality field 86 to his display 58 in the preferred embodiment, a full text screen format 138 is displayed showing the entire contents of the personality file. Editing within the text window is not supported in the preferred embodiment and no fields are defined. Page up and down keys can be used to scroll through displayed text.

Pop up windows are used in the preferred embodiment for a variety of purposes, including help text display and data entry. Pop up windows are used when the task they implement is subsidiary (or a subset of) an already displayed screen format. For example, many of the screen formats accessed from full format screens in the preferred embodiment are pop-up windows--since these accessed screen formats effect data/field selection functions that are subsets of the general function implemented by the format screen.

For example, the channel data screen 116 is a full format screen in one preferred embodiment that permits the user to specify radio operating frequency, channel guard frequency, and a variety of channel options associated with each channel (see Table 18). Depressing the F3 key from this channel data screen 116 causes the GE Star options window 144 (see Table 20) to "pop up" in an overlaid fashion over the channel data screen 116 to enable the user to enable or disable the GE Star option and to select other parameters associated with GE Star. When the user is finished programming the GE Star options, he depresses the F10 key to take the "pop up" GE Star window 144 off the screen. Meanwhile, the channel data screen 116 remains displayed "beneath" the GE Star window 144 during the entire time the window is displayed, and continues to be displayed when the window is removed from the display.

Another important use of the pop-up window in the preferred embodiment is for displaying help text. In fact, in the preferred embodiment, a help pop-up window can be overlaid onto an already displayed pop-up window (which in turn is overlaid on top of another screen). However, in order to minimize user confusion in the preferred embodiment, once a pop-up window is displayed no other pop-up windows (other than help windows) can be called.

In the preferred embodiment, error messages are displayed in a small pop-up window centered on the screen (an example of an error message display in the preferred embodiment is found at the end of the detailed discussion above). Once displayed, an error message remains displayed until the user presses a key to signify that the message has been read. Once any key is depressed in the preferred embodiment, the message window disappears.

Now that the hierarchical screen display format arrangement of the preferred embodiment has been discussed in detail, a discussion of exemplary program control steps performed by the preferred embodiment of system 50 to provide such screen displays and to effect radio programming and related tasks will be presented.

In the preferred embodiment, two sets of program control instructions cooperate with one another to provide radio programming functions. The first program control instruction set is stored in radio 60 (e.g., in a ROM not shown) and cooperates with personal computer program control instruction module 84 to provide upload and download of personality files 86 and to also provide the test and diagnostic functions provided by utility function screen formats 122-126. The program control instructions executed by the radio microprocessor 70 are conventional and therefore need not be discussed here. FIGS. 4-15 are schematic flowcharts of the exemplary program control steps embodied in personal computer program control instruction module 84.

Referring to FIG. 4, upon starting system 50 an initialization routine is performed (block 200). FIG. 5 shows the initialization routine 200 in detail. If the user previously specified set up defaults (i.e., at setup screen 104), these user specified file extension, communications ports and other defaults stored in a set up file is not accessed and read (blocks 202, 204). If no setup file exists to be opened, on the other hand, system default values are used (block 206). A routine is then called at block 208 to prepare for displaying the "displaying current personalities" display format 102 by initializing a display format handling routine (as will be explained in greater detail shortly). Control then returns to main routine block 210 (to determine first whether the display format window handling routine was successfully initialized at block 210) and to then effect display of the main "display current personalities" display format 102.

Briefly, in the preferred embodiment the contents of each display format is stored in a data structure containing (or referencing) textual contents, positional information for each input and output field along with field level color and other display parameters, a designation of the help text files associated with each field on a field-by-field basis, and information specifying the active function keys corresponding to the display format. Briefly, to display a display format, system 50 "opens" the display format data structure (similar to the manner in which a file is opened) (block 212), "fills" the display format with variable information that must be specified at run time (e.g., a listing of all personality files 86 with the specified file extension currently residing one mass storage device 56, block 214), and then "shows" the display format by displaying the "filled" display format on display 58 (block 216). System 50 then "gets" additional information to the display 58 and also "gets" user input corresponding to the display format (block 218)--being responsive only to those function keys defined as active for the specific display format being displayed. System 50 processes defined user inputs and takes appropriate actions in response (e.g., by calling for display of another display format, performing a programming task, or both). Upon depressing the F10 ("exit") key in the preferred embodiment, system 50 "closes" the display format (block 220) and returns to the next highest level display format in the FIG. 2 tree structure (or, in case of the main routine shown in FIG. 4, resets the image displayed by display 58, terminates radio programming functions and returns control to the disk operating system at block 224).

System 50 performs error checking functions each time it attempts to "open" a display format data structure and terminates program execution if it cannot for some reason successfully "open" a required display format (e.g., "No" exit of decision block 212).

FIG. 6 is a flowchart of the exemplary program control instructions performed when the "set up" option is selected at FIG. 5 block 218. The FIG. 6 routine "opens" the "set up" display format 104 by opening the "Radio Type" half-screen format (block 226) and then opening the frequency range (bandsplit) half screen format (block 228). An exit occurs if either of these half-screen formats cannot successfully be "opened" (blocks 230, 232). If both formats are successfully opened, they are filled with the corresponding field information (block 232) and displayed on display 58 (block 234). System 50 then "gets" user inputs and takes appropriate action in response (block 236). Upon depression of the F10 key, both display formats are "closed" (block 238) and system 50 returns to displaying display format 102 (block 232).

FIGS. 7-15 show exemplary program control steps performed in the preferred embodiment to respectively display the following: the channel personality display format 104, the Utility display format 106, the change communications port display format 118, the maintenance display format 120, the print display format 134, the print display format 138, the channel data screen 116, the program radio display format 110, and the read personality display format 112. Each of these sequences of steps involves "opening", "filling" and "showing" the appropriate display format; "getting" additional display information and user input; and finally, "closing" the display format.

In the preferred embodiment, each display format is defined by a corresponding window definition data structure 400 a high-level block diagram of which is shown in FIG. 16. Each window definition data structure 400 in the preferred embodiment includes all of the information required to fully define the corresponding window (display format). Thus, in the preferred embodiment, there is a one-to-one correspondence between display formats shown in FIGS. 2-3 and corresponding window definition data structure 400.

In the preferred embodiment, each window definition data structure 400 includes the following portions:

window name 402 (which may or may not be explicitly stored as part of the data structure);

field control blocks (404)l-404(n)--one for each "field" of the display format;

a field pointer array 406;

a function key label array 408;

a function key function call array 410; and

a window control block 412.

In the preferred embodiment, the window control block 412 actually includes references to arrays 406-410 which in turn may reference field control blocks 404 and other data structures (e.g., help text files) and/or executable code (e.g., function calls corresponding to active function keys). Thus, the data structure 400 shown in FIG. 16 comprises logically related elements which need not be contiguously stored in memory or defined as part of a single unified stored data block.

In the preferred embodiment, field control blocks 404(l)-404(n) correspond to individual input and/or output fields defined as part of the associated display format. That is, in the preferred embodiment each input field and each output field in the display format is defined individually by a corresponding field control block 404 (the structure of the field control block will be described in greater detail in connection with FIG. 18). Field pointer array 406 provides an array of pointers to the various field control blocks 404 for a particular display format. Thus, the preferred embodiment field control blocks 404 need not actually be stored as part of window definition data structure 400 but can instead be stored anywhere in memory (and in fact, the same field control blocks 404 can be used to define fields of several display formats if convenient and desirable). The field pointer array 406 provides a "linkage" between a collection of field control blocks 404 and a particular window control block 412.

The function key label array 408 in the preferred embodiment is a text listing of legends to be displayed beneath the function key symbols when the display format is displayed. As described previously, in the preferred embodiment a symbol corresponding to each of the function keys is displayed whether or not the function key is active for a particular display format--with the active function keys having additional descriptive legends also displayed for them. In the preferred embodiment, function key label array 408 provides "NULL" entries for inactive function keys and descriptive legends for active function keys. Similarly, the function key function call array 410 provides a listing of actual program control function calls associated with the active function keys. Typically, the function key function call array 410 includes "NULL" function calls for all inactive function keys and will provide calls to executable function modules corresponding to all active function keys.

Referring now more particularly to FIG. 17, window control block 412 specifies the addresses field pointer array 406, function key label array 408 and function key function call array 410 corresponding to a particular display format (e.g., in entries 432, 428, 430, respectively). Even though arrays 406-410 are shown as being stored together with window control block 412 in FIG. 412, in the preferred embodiment this contiguous storage is not required because the window control block contains pointers (addresses) to the locations in which the arrays 406-410 are stored.

As can be seen from FIG. 17, window control block 412 also includes an additional pointer 434 points to an ASCII help file stored on disk and associated with the window; and another pointer 436 pointing to a window page function defining whether or not window "paging" is permitted for the particular window (i.e., for windows in which the displayed text, fields, or other information is too extensive to be displayed on the display screen all at the same time). In the preferred embodiment, window control block 412 also includes a W.sub.-- count field 426 specifying the number of fields contained within the window (and thus, the number of corresponding field control block 404 entries within field pointer array 406). Window control block 412 also includes positional fields 418, 420, 422, 424 specifying respectively the beginning row, beginning column, ending row, and ending column on display 58 at which the display format is to be displayed (all display formats in the preferred embodiment are rectangular unless their size and position can be fully specified with these four fields). Finally, window control block 412 in the preferred embodiment includes a pointer 414 to a "Curses" window and a further pointer 416 to a "Curses" window box.

In the preferred embodiment, the conventional software package called "Curses Library" sold by Lattice, Inc. of Glen Ellyn, Ill. 60138 and its associated screen manager library functions are used to define and control various lower level window functions. The preferred embodiment window library routines make function calls to functions stored within the off-the-shelf Lattice Curses Library. The Curses Library contains very low level functions that help to standardize CRT/terminal interaction. The preferred embodiment makes use of this Lattice Curses Library to ensure that the preferred embodiment program control code is transportable to other machines and operating systems (and thus, the Curses Library provides a degree of standardization since it is available for most C based operating systems). Far more detail regarding the Lattice Curses Library is available from a variety of sources and publications including, for example, the manual "Lattice Curses Screen Manager Library Curses Reference Guide Revision 1.0", Lattice, Inc. (1985) (the entire contents of which are incorporated by reference herein).

Briefly, the Lattice Curses Library is a library of C functions used for updating the screen of an IBM personal computer. The Curses Library is capable of keeping and updating any number of full or partial virtual screen images in memory, and also paints the actual screen as needed with any or many of the images. Functions are provided to write text to virtual screens, move the cursor, scroll the screen, overlay screens, outline, insert, delete, clear and highlight. Nearly 100 functions and macros are provided in the library relating to display format, display and manipulation. These functions and macros are used extensively in the preferred embodiment the present invention to perform the low-level display format manipulations required.

Thus, for example, window control block pointer 414 points to a window buffer (data structure) defined in accordance with the Curses Library "initscr" function (which is invoked in the preferred embodiment via a routine called "new window" described in Appendix A). In this way, a "box" may be displayed on display screen 58 via a Curses "refresh" function call referencing pointer 416--and similarly, a window buffer in memory defined under Curses Library routines may be displayed and otherwise manipulated via Curses function calls referencing pointer 414. See Appendix A for additional details relating to how calls to the Curses Library functions are used in the preferred embodiment.

FIG. 18 is a block diagram of exemplary contents of field control block 404 in the preferred embodiment. In the preferred embodiment, each field within a display format is defined individually in terms of its attributes and characteristics. Field control block entries 438-452 define various different attributes/characteristics of the particular field, including whether it is a display only field (entry 442), whether the cursor automatically advances to the next field when the current field is filled (entry 444), whether the field contents toggles between different values (entry 446), whether only uppercase characters can be displayed within the field (entry 448), and the like. Positional entries 454,456 define the row and column locations, respectively, where the field is to be displayed on display screen 58, while entries 458,460 respectively define minimum or maximum numbers of characters that must be used to fill the field. Field attribute entry 468 describes whether the field contents are to be displayed in normal video, bold video or the like.

Following the attribute characteristic definition entries 438-468 appear various pointers which relate to the function of the field defined by field control block 404. Entry 470 defines the actual data in the personality file data structure to be used for filling in an output field or received from an input field. Entry 472 refers to an ASCII text file containing help text to be displayed when the help F-key is depressed while the cursor is in the field. Prompt field 474 contains an ASCII key string prompt line which is displayed (e.g., at the bottom of the display format) whenever the cursor is moved into the field. Field 476 points to characters data (e.g., if a conversion between displayable character data and a different actual data representation is required), while field 478 points to an edit function which is called whenever an input field is filled in (e.g., for range checking and the like).

FIGS. 19-31 are flow charts of the exemplary program control steps performed by processor 52 and display 58 in the preferred embodiment to display the display formats shown in FIGS. 2-3 in accordance with the information stored in window definition data structures 400 shown in FIG. 16. Referring to FIG. 4 (and as explained previously), a display format is displayed in the preferred embodiment by first initializing it (blocks 200,210 shown in FIG. 4); then "opening" the window (block 212), and finally "filling" and "showing" the window (blocks 214,216). User input is received by "getting" from the window (block 218). Finally, a window and its associated data structure are deactivated by "closing" the window (block 220). The manner in which these various steps are performed using the data structures shown in FIGS. 16-18 will now be explained in conjunction with the flow charts of FIGS. 19-31.

FIG. 19 is a schematic flow diagram of exemplary program control steps performed in the preferred embodiment to initialize the Curses Library runtime module. In the preferred embodiment, the runtime module is initialized by calling a further routine "init screen" (block 500, see Appendix A) which sets aside buffers in personal computer processor random access memory 82 in which to store the various portions of the display format, creates a display format image in memory, initializes various pointers, initializes the attributes of the display 58, etc. System 50 tests whether the screen was properly initialized (decision block 502) by testing a return code provided by the initialization routine. Assuming the screen was properly initialized, a title window is created (e.g., by drawing the outside and inside box delimiters using "draw box" commands, printing appropriate title text, and overwriting the current screen with the new information, block 504) and then a test is performed to determine whether the title window was actually created successfully (decision block 506). If the title window was created properly, then a function key window is created (block 508) and a test is then performed to determine whether the function key window was correctly created (block 510). In the preferred embodiment, decision blocks 502,506,510 are performed by merely testing return codes returned by Curses Library (and/or other) routines which actually perform the blocks 500,504,508. If each of blocks 500,504,508 was correctly performed, then the "INIT window" routine returns a true value (and otherwise returns a false value).

FIG. 20 is a flow chart of exemplary program control steps performed in the preferred embodiment as part of the "open window" routine 212 shown in FIG. 4. The open window routine 212 is called by the FIG. 4 main routine (and also whenever any new window must be displayed as is shown in FIGS. 5-15). It is first determined whether the requested window was already "open" (decision block 514). If the window is not already opened, then the window is created (i.e., appropriate Curses library routines are called to "open" a new EDW window using the window control block 412 a pointer to which is passed to the open window routine 212, decision block 516). An error checking decision block 518 insures that the window was correctly created by the Curses library routines. Once the window is created, then a box is "drawn" around the window in accordance with positional and other information stored in window control block 412 (block 520). In the preferred embodiment, this box is drawn by first referencing window control block 412 to determine whether a thick or a thin box needs to be drawn, and then drawing the box of the appropriate thickness, and finally setting the appropriate attribute. It should be noted that blocks 516,520 do not actually display anything on CRT display 58. Rather, they create images within personal computer processor RAM 82 (i.e., within the memory images created and maintained by the Curses library routines). Specifically, the window create block 516 requests a buffer from the personal computer operating system and allocates this buffer for storage of displaying format image in RAM 82 (referencing field 414 of window control block 412 shown in FIG. 17).

If the open window routine is unsuccessful in creating the window, then an error message is displayed via the "show message" routine 524 a more detailed description of which is shown in FIG. 21. The show message routine 524 displays a message across the middle of the screen in response to parameters specifying text attributes, the text to be displayed, and whether the message is to be displayed until the user presses a key. Show message routine 524 first saves the currently displayed screen so that it can be recalled later for display (block 526). In the preferred embodiment, the save current block 526 is performed by saving the cursor position, style and color in a stack structure of the like and then by actually reading the current screen image from the frame buffer and saving it in a memory buffer within RAM 82. A box is then drawn around the new window (block 528) and the screen attributes for the type text being displayed are set (block 530).

The set attribute and type text block 530 is performed in the preferred embodiment by setting up appropriate attributes for display 58 (e.g., depending upon whether it is monochrome or color display), moving the cursor to the appropriate position on the display for writing the desired help or message text, actually adding the desired text stream to the screen, and then resetting the screen attributes). The save screen may later be restored (block 540) by moving the contents of the saved screen buffer generated by block 526 to the current screen buffer, refreshing the screen to display contents of the screen buffer, and restoring the cursor color and style to the information corresponding to that which was stored by block 526.

After block 530 is performed, the screen is refreshed (block 532) to actually display the new message window, and the preferred embodiment then waits for user input if a character is expected (decision block 534). In response to user input (block 536) the new window is deleted (i.e., erased from the screen and removed from RAM 82, block 538) and the screen that was displayed by display 58 before the new window was displayed is restored to the screen (block 540). If no user input is expected (i.e., if a "no wait" parameter passed to routine 524 is true), then control is immediately returned to calling routine 212 shown in FIG. 20 to remove the show message window just displayed.

FIG. 22 is a flow chart of exemplary program control steps performed in the preferred embodiment to "fill" a window with a data. In the preferred embodiment the fill window routine 214 does not actually write information onto display 58, but rather fills the newly formed buffer in RAM 82 corresponding to the window being created with the appropriate data for display (i.e., to provide output fields and fully or partially "filled in" input fields). Referring now to FIG. 22, the fill window routine 214 references field control blocks 404 shown in FIG. 16 in sequence in order to write all of the input fields and all of the output fields of the display format into the current buffer stored in RAM 82. Decision block 542 first determines whether all of the fields have been written (e.g., by referencing entry 426 shown in FIG. 17 and comparing that value with the number of times the FIG. 22 loop has been executed). If there are still fields left to be written, fill window routine 214 references the field pointer array 406 of the window definition data structure 400 shown in FIG. 16, indexes down the field pointer array 406 to the next field left to be written, and reads the contents of the associated field control block 404 (block 544). Fill window routine 214 then determines whether the current field is an input field (e.g., by testing the logical value of entry 442 of FIG. 18) (decision block 546). If the field is an input field, then it may be necessary to fill in the field with an appropriate previously entered default value (e.g., to save the user the time and effort required to independently enter the new value). Specifically, if the new field is an input field, it may be necessary to reference data pointed to by FIG. 18 pointer 470, convert that data to character data at block 548 (e.g., by referencing the FIG. 18 field control block "f type" entry 464 to determine whether the field contains numerical or character data, and then performing an appropriate conventional conversion routine to provide displayable characters), and move the resulting character data into the window buffer at an appropriate position corresponding to the field position (as specified by FIG. 18 entries 454-460) (block 550).

FIG. 24 is a flow chart of exemplary program control steps performed in the preferred embodiment to "show" a window. (See block 216, FIG. 4). In the preferred embodiment, the show window routine 216 displays all of the input and output fields of the window (that is, the "input field impure area information of the EDW window). In the preferred embodiment, the display of the rest of the window, including the box, title area, function key legend, and the like, is handled by the "get window" routine to be described shortly. The show window routine 216 is passed the pointer to window control block 412, displays the input field "impure" area information in the EDW window data structure and otherwise prepares the screen buffer area for a call to the get window routine. When the show routine 216 is executed, it first determines whether all input and output fields are displayed yet (decision block 566). If all input and output fields are not yet displayed, and the field data for the next field is retrieved (block 568) and tested to determine whether the field is an input field (decision block 570). If the field is an input field, then the contents of the text buffer corresponding to the input field (as established by FIG. 12 block 550) is displayed (block 572). If the field is an output field, on the other hand, then the prompt information corresponding to the field is displayed (block 574). The show window routing 216 then terminates (almost always leading to execution of the get window routine shown in FIG. 25).

The FIG. 25 "get window" routine 218 is passed pointer to the window control block 412 and an additional value specifying the field of the window in which the cursor is to initially to reside (i.e., to save the user the trouble of manually moving the cursor to an initial field to be filled in). The get window routine 218 causes the remainder of the window to be displayed and also handles user input. Referring to FIG. 25, the get window routine 218 first activates the window (block 574) in order to symbolically deactivate EDW window and activate another by changing the attributes of their borders. In the preferred embodiment, the activate window routine 574 actually changes the old EDW window to single width and the new EDW window to double width, and also changes the function keys assigned to the new EDW window both graphically and functionally.

The activate window routine 574 expects two pointers in the preferred embodiment: "from" and "to". The "from" pointer points to the EDW window that is to be deactivated and the "to" pointer points to the EDW window to be activated. If an EDW window is to be activated without deactivating another EDW window, then a NULL point is passed as the "from" pointer. Conversely, if an EDW window is to be deactivated without activating another, a NULL pointer is passed as the "to" pointer.

FIG. 26 is a schematic flow chart of activate window routine 574 in the preferred embodiment. Routine 574 first determines whether the previous window is to deactivated (decision block 576)--since in some instances the new window should now supersede the previous window. If the previous window is to be deactivated (decision block 576), then a box is drawn around the new window (block 578) and the current screen is overwritten with the new window information (block 580). As mentioned previously, some screens in the preferred embodiment (e.g., split format display formats) include two windows only one of which is active and the other which is deactivated. Decision block 582 determines whether the new window is to be activated or merely displayed. If the new window is to be activated, then a highlighted box is drawn around the new window (block 584) and a new function key legend display corresponding to the new window is written over the prior function key legends (block 586).

Referring once again to FIG. 25, after the window is activated, decision block 588 determines whether the cursor is within an input field or within an output field. If the cursor is within an input field, then user input is expected and a routine called "get window field" is executed at block 590. A detailed flow chart of this get window field routine is shown in FIG. 27. In the preferred embodiment, it is first determined whether the field is a toggle field (e.g., an input field which contains a logical value or some other small set of possible values) (decision block 592). If the field is not a toggle field, then the field prompt specified by the field control block prompt line pointer 474 (see FIG. 18) is displayed on display 58 (block 594). If the field is a toggle field, on the other hand, the TAB prompt is displayed instead (to notify the user that all he has to do to toggle the field value to another valid value is to depress the TAB key, block 596). The field itself is then displayed on the screen (block 598) and the cursor is positioned and has its attributes set appropriately (block 600).

The screen is then refreshed and a routine called "get window character" is performed at block 602. The get window character routine processes user inputs. A detailed flow chart of the get window character routine 602 is shown in FIG. 28. The get window character routine 602 first gets a character from the keyboard (block 604) and then determines whether the character is ASCII (decision block 606). If the received character is ASCII, then routine 602 determines whether the field requires numeric information or alphanumeric information (e.g., by referencing the corresponding field control block 404, decision block 608). If numeric information is required, routine 602 determines whether the character supplied by the user is in fact numeric (decision block 610) and generates a beep or other indication requiring reentry of the character if the character is not numeric (block 612). Otherwise, the character is returned to routine 590 (block 614).

FIG. 23 is a schematic flow chart of exemplary program control steps performed in the preferred embodiment to get a character from the keyboard (i.e., FIG. 28, block 604). Referring now to FIG. 23, the preferred embodiment obtains a character from the keyboard buffer (block 552). This character may be passed to on to FIG. 28 block 606 unchanged, or it may be mapped into other data. In the preferred embodiment, it is possible to dynamically alter the significance of different (e.g., special function) keyboard keys to provide additional flexibility. For example, as has been explained, the preferred embodiment provides various functions to open, display and close display formats. These functions are initiated by providing a function call specifying the name of the function (as is well known to those skilled in this art). However, it is generally desirable to be able to dynamically alter the significance of different keyboard keys so that depressing different keys at different times can cause the same function call to be initiated. In the preferred embodiment, the FIG. 23 routine "filters" all user inputted keystrokes and maps certain keystrokes into function calls--with the specific function calls the keystrokes are mapped into being dependent upon a mapping table which can be specified on a window or field level basis (as will now be explained).

The user inputted character is first tested to determine whether it is an ASCII character (i.e., whether it falls within the range of valid ASCII characters which need not be mapped out but may instead be displayed or otherwise processed directly) (decision block 554). If the retrieved character is a valid ASCII character, it is simply returned (block 556). If, on the other hand, decision block 554 determines that the retrieved character is not a valid ASCII character, it may be mapped into a function call by blocks 558-562. The character is then tested to determine whether it is a null character (decision block 558). If the character is a NULL character (i.e., a character having no correspondence in the current mapping table), then the next character is retrieved (block 560) and steps 552-554 are performed for this next character. If the character is not a NULL character, then the character is mapped (block 560) (e.g., by using a prestored memory lookup table which simply converts input characters to function calls). In the preferred embodiment, a default table lookup called "screen map" is used, for example, to map the INS key into a function call "toggle insert"; the "DEL" key into a function call "delete in place"; etc. The preferred embodiment permits different mapping tables to be used at different times (e.g., based on a pointer stored in field control block 404 or the like). The mapped function call is then returned at block 564.

Referring once again to FIG. 27, if the returned character is in fact a character (decision block 616) then it is determined whether there are any character spaces left within the field to be filled in (decision block 618). If no character spaces remain, then blocks 602-618 are performed once again to get another character. Otherwise, the character is processed at block 620 (e.g., by placing it into a buffer, performing an appropriate function call in response to it, or the like). It is then determined whether routine 590 should be exited (decision block 622). An exit at blocks 622 may occur when the entire field has been filled in. Before exiting the routine 590, however, the preferred embodiment performs a validity check in the preferred embodiment with the user-inputted field value at block 624 by calling an "edit" routine if the field is to be edited (as specified by entry 450 of the field control block 404) (see FIG. 18).

If the window field is to be edited, then the field control block entry 478 is used to point to an edit function used for editing this specific field. This field edit function in the preferred embodiment may perform range checking operations to ensure that the field has been filled in with the value of an appropriate range (e.g., if frequency information is required, the edit function may ensure that only frequency information that is within a valid FCC frequency allocation range and which falls on appropriate channel spacings has been filled in). If the edit block 624 does not return the true value (indicating an invalid value has been filled in, decision block 626), then blocks 602-626 are performed again (thereby requiring the user to reenter the field information). Otherwise, the prompt line is cleared and the attributes are reset and a return to "get window" routine 218 occurs at blocks 628-630.

Referring once again to FIG. 25, upon returning to the get window routine 218, the character return block 590 is processed in an appropriate manner depending upon the particular window being displayed and a particular character returned. For example, if the user depresses the "go back" function key, the get window routine 218 is exited (block 618) and the current window is deactivated (block 620). Similarly, some windows having only one input field (e.g., a window prompting the user for a Y, N) may be exited upon the user response to a single field. Otherwise, blocks 588-618 are performed again for any other fields within the window to allow the user to fill in those input fields.

FIG. 29 is a flow chart of exemplary program control steps performed in the preferred embodiment as part of the "closed" window routine 220. The "close window" routine 220 in the preferred embodiment simply closes an EDW window, and returns a true value if it is successful and a false value if it is unsuccessful. If the window to be closed is not even open (as tested for by decision block 650), then an error message is displayed (block 652). Otherwise, the open window is cleared at block 654. To "clear" a window, each one of the individual fields of the window is cleared individually in the preferred embodiment and then the remainder of the window is cleared from the screen.

FIG. 30 is a schematic flow chart of exemplary program control steps performed in the preferred embodiment to set and display currently active function keys associated with a particular window. This "set function keys" routine 670 is typically performed as part of the "get window" routine 218 shown in FIG. 25. Decision block first determines whether the legends for all of the function keys have yet been displayed (decision block 672), and if not, proceeds to display a descriptive legend (obtained by referencing the function key label array of the window pointed to by the window control block 412) beneath a legend for each function key. NULL entries in the function key label array 408 indicate that no legend is to be displayed below the indication of that particular function key. At block 676, a descriptive help message indicating that function key F9 is available for field-level help (and Shift-F9 is available for window-level help) as displayed at the bottom of the screen is overwritten to include all new function key labels (block 678).

FIG. 31 is a flow chart of exemplary program control steps performed in the preferred embodiment as part of a "show help" routine 750 whenever the user depresses the F9 help key. Upon depressing the help key, a help file is opened (block 752) as a buffer in RAM 82 for storing the help text to be displayed. If this buffer cannot be opened (decision block 754), an error message is displayed whereupon (block 756) and a routine return (block 758). Otherwise, the size of the help text to be displayed is retrieved (block 760)--typically by referencing the window control block 412, window help file pointer 434 to determine which help file is to be used and then determining the size of the help file. Next, the current screen is saved (block 762) so that the after the help text is displayed the user can return immediately where he left off. Decision block 764 then test whether the user has requested a "big" (i.e., window-level) help rather than a field-level help. In the preferred embodiment; a large help window is displayed for window-level help (regardless of the amount of text contained within the window-level help) and a smaller window is displayed for field-level help to enable the user to instantly distinguish between window-level help and field-level help. Thus, if a window-level help has been requested, the parameters are set for a big window (block 766), whereas small window parameters are set for field-level help (block 768). The window is next created (block 770) and its successful creation is tested for by decision block 772. A created window is activated (block 774) and the appropriate help file text is displayed within the created window (block 776).

In the preferred embodiment, the user must depress a kay in order to make the help window cease being displayed (and in this way the user can view the help text as long as he wishes). The user input is waited for at block 778, and once the user does depress a key, the help window is closed (block 780), the old screen is restored (block 782) and the help file buffer is closed (block 784).

While the invention has been described in connection with what is presently considered to be the most practical and preferred embodiment, it is to be understood that the invention is not to be limited to the disclosed embodiment, but on the contrary, is intended to cover various modifications and equivalent arrangements included within the spirit and scope of the appended claims. ##SPC1##