Abstract:
In an exemplary embodiment, portable data devices can be coupled with a local area network at any of a multiplicity of points and integrated into the system on a dynamic basis. The preferred system is highly flexible and closely adaptable to changing needs of an individual user. For example, unitary multiple docking devices each receiving a plurality of handheld computerized data terminals may be chained in a series to a single primary controller which may have a further LAN channel including an auxiliary unit which may supply charging power to a further series of multiple docking devices, added to the system as needed. A preferred auxiliary unit is capable of handling two-way communication without the provision of a direction control line in the channel. A preferred LAN system may have unitary printed circuit boards or other rigid network pathways provided with multiple docking receptacles. The control for the LAN system will automatically establish identities for randomly added devices.

Description:
CROSS REFERENCE TO RELATED APPLICATIONS 
     This application is a continuation of application Ser. No. 07/347,849, filed May 3, 1989, now abandoned, which is a continuation-in-part of a copending application in the names of Phillip Miller, Steven E. Koenck, Joseph J. Kubler, Keith K. Cargin, Jr. and George E. Hanson, &#34;VEHICLE DATA SYSTEM&#34;, U.S. Ser. No. 07/305,302 filed Jan. 31, 1989. Reference is made pursuant to 35 USC 120 to said copending application, and the entire disclosure thereof including the drawings and appendices is incorporated herein by reference. 
    
    
     AUTHORIZATION PURSUANT TO 37 CFR 1.71(d) and (e). 
     A portion of the disclosure of this patent document contains material which is subject to copyright protection. The copyright owner has no objection to the facsimile reproduction by anyone of the patent document or the patent disclosure, as it appears in the Patent and Trademark Office patent file or records, but otherwise reserves all copyright rights whatsoever. Reference is made to the following related applications: 
     
         ______________________________________U.S. Ser. No.        U.S. Filing Date                     Named Inventors______________________________________1.  06/915,023   October 3, 1986                         Keith K. Cargin, Jr.    (Now                      George E. Hanson    Abandoned)2.  06/928,916   November 7, 1986                         Keith K. Cargin, Jr.    (Now                      George E. Hanson    Abandoned)3.  07/212,435   June 28, 1988                         Keith K. Cargin, Jr.    (U.S. Pat. No.            George E. Hanson    5,023,823    6/11/91)4.  07/303,557   January 27, 1989                         Darald R. Schultz5.  07/327,660   March 23, 1989                         Patrick H. Davis    (Now    Abandoned)6.  07/339,330   April 14, 1989                         Keith K. Cargin, Jr.    (Now                      Stephen J. Kelly    Abandoned)                Kevin Lewis Fischer                         William T. Gibbs                         Darrell L. Boatwright                         Dennis Alan Durbin7.  07/345,200 filed            April 28, 1989                         George E. Hanson    (Attorney Docket    No. 6649-X)    (now allowed)8.  07/346,771 filed            May 2, 1989  Phillip Miller    (Attorney Docket          Steven E. Koenck    No. 6643-Y)               Jerry L. Walter    (Now                      Joseph J. Kubler    Abandoned)                Keith K. Cargin, Jr.                         George E. Hanson                         Patrick H. Davis                         Steven R. Kunert                         Darald R. Schultz9.  07/347,298 filed            May 2, 1989  Phillip Miller    (Attorney Docket          Robert J. Traeger    No. 36504Y)               Joseph J. Kubler                         Keith K. Cargin, Jr.                         George E. Hanson                         Patrick H. Davis                         Darald R. Schultz______________________________________ 
    
     The entire disclosures including the drawings and Appendices of these related applications are hereby incorporated herein by reference in their entireties. 
     BACKGROUND OF THE INVENTION 
     In the data capture field, there are many applications where hand-held data terminals should be of rugged construction so as to survive rough handling. Many operators are not inclined toward painstaking or precise manipulations. An example is in the use of RF data capture terminals on forklift trucks in factories and warehouses where items to be transported are identified by bar codes. Other examples are found in the field of route delivery and direct store delivery where many items are handled and the terminal means automates the accounting function. Even in applications where bar code data is transmitted on-line to a central station, it may be desirable for hand-held terminals to be inserted into docking apparatus for the interchange of data signals e.g. the loading of scheduling information or the like into the terminal at the beginning of a working shift. Further where terminal means has memory capacity for accumulating data during a delivery operation or the like, it may be desirable for such data to be transferred to a printer so that a hard copy may be produced. In cases where rechargeable batteries are used, the docking apparatus may provide for the recharging of such batteries at the same time as data communication is taking place. 
     It is conceived that it would be highly advantageous to provide a data communication system with docking apparatus adaptable to a wide range of terminal means, and which furthermore could be quickly and simply loaded in a relatively foolproof manner, and without requiring attention and care from operators engaged in physically demanding and arduous work routines. A docking apparatus would be desirable that completely avoids the use of mating pin and socket type electrical connections, and that does not rely on a specialized configuration of the terminal, e.g. the provision of an optical scanner tip which may be used for data communication. 
     SUMMARY OF THE INVENTION 
     Accordingly, it is an important object of the present invention to provide a data communication system wherein components can be readily detached for portable operation A further object resides in the provision of such a data communication system wherein multiple devices may be connected at different locations on a local area network and integrated into a data communication system on a dynamic basis without interrupting system operation. 
     In a presently preferred configuration for communication with portable data capture terminals, a local area network (LAN) has the following characteristics: 
     (1) The LAN is configured so that multiple devices may be connected simultaneously. 
     (2) The LAN provides reliable two-way data communication. 
     (3) The LAN may have a total length up to hundreds of feet. 
     (4) Any connected device may be inactive or off without having an effect on the other devices. 
     Power for operation of the portable data terminal is provided by the internal terminal batteries when used portably and by the docking system when the terminal is placed in a terminal receptacle thereof. Further, the terminal batteries may receive charge while the terminal is operating from the system power so that full battery capacity is available when portable operation is again required. 
     In accordance with a further development of the invention, portable terminals, for example, may be quickly removed from the system, and may be placed in generally random physical network locations by the terminal users. 
     It is a feature of the invention to provide a network capable of assigning suitable identification to a newly added terminal or the like on a dynamic basis (without requiring each device to have its own unique &#34;hard&#34; address, and without interruption of system operation). 
     The present invention relates particularly to data communication systems for portable data terminal means which are to be held in one hand during data capture operation; however the invention is also applicable to portable data terminal means which may be mounted e.g. on a belt or e.g. on a vehicle during data capture operation. The data terminal means preferably will be of size and weight to be held in one hand, even though not so held during data capture operation. Also the data terminal means may be provided with batteries so as to be capable of portable operation, and such batteries may be rechargeable. 
     In a typical case, the portable data terminal means will have user interface means such as a manually operated data input (e.g. a keyboard) and/or a data output (e.g. a liquid crystal display), and will contain data storage means for the storage of programming instructions and/or program data, and/or for the storage of data capture information. 
     In accordance with an important aspect of the present disclosure, a docking apparatus removably receives portable data terminal means for purposes of data communication e.g. with a host computer and/or for the recharging of rechargeable batteries, and is so configured that the terminal means may have electrical contact pad means generally flush with the exterior of the terminal means. Preferably an abutting type engagement between the terminal contact pad means and cooperating electrical contact means of the docking apparatus is used for each electrical connection which is required at the docking apparatus, and the typical pin and socket type docking connections are entirely avoided. 
     In accordance with another aspect of the invention the same basic docking structure may be provided with greater or lesser numbers of contact positions. For example, one type of hand-held terminal intended for on-line RF communication with a host computer may have six contact pads for coupling with a local area network, and may have a nine position electrical connector for compatibility with an earlier type of interface system requiring interfitting of pin and socket connectors; another type of hand-held terminal designed for route accounting applications may have e.g. twelve external contact pads and be intended for interfacing only with systems having provision for open abutment type interconnection. 
     A further object is to provide an expandable docking network which is closely adaptable to changing needs of various customers. 
     A particular feature resides in the provision of auxiliary units for expanding the local area network of a docking system without requiring a direction control line for the signal communication repeater system. 
     A further object is to provide a particularly economical and reliable multidocking subsystem which may be quickly and conveniently configured into a larger network as required. 
     A unique feature resides in a multipoint coupling with a local area network formed directly on a printed circuit board or other rigid electrical pathway of this type. For example, a six unit docking subsystem may be implemented as a single wall-or bench-mounted entity, and one or two printed circuit boards may directly carry the local area network pathways to all six docking points. In a most preferred embodiment both signal and power pathways traverse the subsystem from end to end, and further subsystems may be chained therewith at either end as desired. 
     Other objects, features and advantages will be apparent from the following detailed description, taken in connection with the accompanying drawings, and from the individual features and relationships of the respective appended claims. 
    
    
     BRIEF DESCRIPTION OF THE DRAWING FIGURES 
     FIG. 1 is a perspective view of a preferred docking unit for use in the present invention. 
     FIG. 2 is a partial enlarged perspective view of the contact end of a hand-held device of the type shown in FIG. 1. 
     FIG. 3 is an enlarged view of the multiple contact subassembly forming part of the terminal receptacle means of FIG. 1. 
     FIG. 4 is a front elevation of the embodiment of the docking unit shown in FIG. 1 with portions cut away. 
     FIG. 5 is a view in section along lines 5--5 of FIG. 4. 
     FIG. 6 is a perspective view of a multidocking apparatus for use in an embodiment of the invention, with a hand-held device in one of the terminal receptacles. 
     FIG. 7 is a frontal elevational view of the multidocking apparatus of FIG. 6. 
     FIG. 8 is a rear elevational view of the docking apparatus of FIGS. 6 and 7. 
     FIG. 9 is a left end elevational view of the docking apparatus as seen in FIG. 7. 
     FIG. 10 is a top plan view of the docking apparatus as shown in FIG. 7. 
     FIG. 11 is a bottom plan view of the docking apparatus of FIG. 7. 
     FIG. 12 is a frontal elevational view of a single docking unit such as shown in FIG. 1. 
     FIG. 13 is a left side elevational view of the docking unit of FIG. 12. 
     FIG. 14 is a top plan view of the docking unit of FIG. 12. 
     FIG. 15 is a bottom plan view of the docking unit of FIG. 12. 
     FIG. 16 is a rear elevational view of the docking unit of FIG. 12. 
     FIG. 17 is a front elevational view of a network controller unit for communication with the docking units of FIGS. 1 through 
     FIG. 18 is a left side elevational view of the network controller of FIG. 17. 
     FIG. 19 is a top plan view of the network controller of FIG. 17. 
     FIG. 20 is a right side elevational view of the network controller of FIG. 17. 
     FIG. 21 is a rear elevational view of the network controller of FIG. 17. 
     FIG. 22 is a bottom plan view of the network controller of FlG. 17. 
     FIG. 23 is a somewhat diagrammatic partially exploded frontal elevational view showing multidocking apparatus according to FIGS. 6 and 7, but with certain parts broken away to illustrate significant features of internal construction. 
     FIG. 24 is a somewhat diagrammatic left side elevational view of the structure of FIG. 23 with parts separated from each other to indicate details of internal construction and assembly. 
     FIG. 25 is a somewhat diagrammatic front elevational view of the printed circuit boards and contact assemblies associated with the multidocking apparatus of FIG. 23. 
     FIG. 26 is a top plan view of the solder sides of the printed circuit boards utilized in the multidocking apparatus of FIG. 23. 
     FIG. 27 is a somewhat diagrammatic exploded elevational view for illustrating constructional details associated with the printed circuit board arrangement of FIG. 25. 
     FIG. 28 shows a typical network configuration involving multidock apparatus such as shown in FIGS. 6 through 10 and 23 through 27, and which may utilize a network controller such as illustrated in FIGS. 17 through 22. 
     FIG. 28A illustrates a communications system relating to a single dock unit such as shown in FIGS. 1 through 5 and 12 through 16. 
     FIGS. 29 and 29A show circuitry for an auxiliary power unit which may be utilized as illustrated in FIG. 28. 
     FIGS. 30A and 30B together show a block diagram of a local area network controller such as may be utilized in the network configuration of FIG. 28, FIG. 30B being a continuation of FIG. 30A to the right. 
     FIG. 31 shows an exemplary implementation for the PAL component of FIG. 30A. 
     FIGS. 32A and 32B show a preferred implementation for the auxiliary power unit of FIG. 28. 
     FIG. 33 shows an exemplary implementation for the RS232 interface components of FIG. 30B. 
     FIGS. 34A, 34B and 34C show an exemplary implementation for the port select and RS485 interface components of FIG. 30B. 
     FIGS. 35A and 35B show an exemplary implementation for the plus twelve volt regulator and plus five volt DC/DC converter components of FIG. 30B. 
     FIGS. 36A, 36B and 36C show an exemplary circuit for the RAM controller component of FIG. 30A. 
     FIGS. 37A through 37F show circuit details related to the EPROM component, the microprocessor component, the latch component and the real time clock of FIG. 30A, and related components, FIG. 37B being a continuation of FIG. 37A to the right, FIG. 37C being a continuation of FIG. 37B to the right and sharing a vertical segment of the control bus therewith, FIG. 37D being a continuation of FIG. 37A in the downward direction, FIG. 37E being a continuation of FIG. 37B in the downward direction and a continuation of FIG. 37D to the right, and FIG. 37F sharing a vertical segment of the control bus with FIG. 37E and thus being a continuation of FIGS. 37B and 37C in the downward direction and a continuation of FIG. 37E to the right. 
     FIGS. 38A through 38E show the serial communications controller components of FIG. 30B in a preferred implementation and show additional circuitry such as the keyboard encoder component and the disk drive controller of FIG. 30A, FIG. 38B being a continuation of FIG. 38A to the right, FIG. 38C being a continuation of FIG. 38A in a downward direction, FIG. 38D being a continuation of FIG. 38B in a downward direction and a continuation of FIG. 38C to the right, and FIG. 38E being a continuation of FIG. 38B in a downward direction and a continuation of FIG. 38D to the right. 
    
    
     DETAILED DESCRIPTION 
     Description of FIGS. 1-6 
     Referring now to the drawings, FIG. 1 discloses a preferred embodiment of single docking unit 2 in a perspective view, showing a data entry terminal 4 of a type insertable therein. Data entry terminal 4 is provided with an elongated housing 6 having a front wall 8 generally orthogonally positioned to end walls 16 and 18. A keypad 10 and visual display 12 are provided on front wall 8 of housing 6. It is intended that data entry terminal 4 is a portable, preferably hand-held, data collection device which may be carried with the user such that the user may enter data to be collected either by activation of the keys of keypad 10 or by other means, such as through bar code reading accessories, which are not illustrated in the drawings. Data entry terminal 4 may provide data or instructions to the user by way of display 12, and/or display 12 may display to the user the data which is being entered through the keypad or other input means which may be used. Data entry terminal 4 may also be equipped to electromagnetically communicate by transmitted waves with other devices to gather and transmit data. 
     Devices such as data entry terminal 4 require electrical power to operate, such power generally being provided by rechargeable batteries contained within housing 6. Because such batteries become discharged with use, it is desirable for data entry terminal 4 to be electrically chargeable by external means. 
     As seen in the preferred embodiment of FIG. 1, docking unit 2 comprises a generally upstanding terminal receptacle means 20 into which data entry terminal 4 is insertable. Receptacle 20 comprises opposing sidewalls 22 and 24 which are interconnected by rear wall 26. Front wall 28 of receptacle 20 is substantially shorter than rear wall 26 thereby avoiding interference with the keypad 10 of data entry terminal 4. A bottom wall 30 of receptacle 20 interconnects with sidewalls 22 and 24 and with front wall 28 and rear wall 26. Contact members 32 project through an aperture in bottom wall 30. Rail 34 (see also FIG. 4) extends inwardly from rear wall 26, so as to engage the back of data entry terminal 4 as it is inserted into a loading channel 36, thereby guiding the data entry terminal 4 into proper position relative to contact members 32. Cooperating frontal terminal guide ribs such as 37, FIG. 1, further serve to define the loading channel 36. 
     Receptacle 20 may be carried by a supporting framework 40 which in turn may be wall or table mounted by means of a bracket 42. 
     Bracket 42 is provided with a generally upstanding plate 48 and an integral base 46. Slotted opening 44 is provided in plate 48 to allow hanging of the docking unit upon a vertical surface if desired. Base 46 provides a structure for fastening the docking unit to a horizontal workbench or shelf, if preferred. 
     Plate 48 of support 42 is provided with opening 49 to receive plug means of a typical telephone wall mounting plate. Slotted opening 44 and slot 47 of plate 48 are disposed to receive large-headed mounting studs typical of telephone wall mounting plates. Thus a user may leave docking unit 2 attached to a wall at a telephone wall plate and may attach telephone cabling through opening 49 to modulator-demodulator means which may interconnect with data entry terminal 4. When data intercommunication with a data collection device, or recharging thereof is desired, the device may be placed within the docking unit 2 as it hangs from a wall, mounted to a telephone wall plate if desired. 
     Referring now to FIGS. 4 and 5, the structure of a preferred embodiment of docking unit 2 can better be visualized. Contact elements 32 are arranged in spaced apart insulated fashion and are mounted at bottom wall 30 of receptacle 20. Offset part 25 of the rear wall 26 overhangs rear wall 41 of frame 40. Detents 50 and 52 are carried by tabs 54 which are integral with rear wall 26 at sloped region 27 thereof. This construction allows tabs 54 to deflect relative to rear wall 26. Detents 50 and 52 comprise mating elements for indentations formed in the rear of housing 6 of data entry terminal 4 and are positioned on rear wall 26 such that mating engagements with indentations on data entry terminal 4 are achieved when data entry terminal 4 is fully seated within receptacle 20. Electrical connector 76 provides an interconnection junction between circuit board 48 and external means and in the preferred embodiment comprises a pin-containing shell housing well known as a DB-9 connector. 
     Referring to FIG. 3, a plurality of contact elements 32 are deployed within a contact block 70 of insulating material. In FIG. 3, one contact element 32 is displaced from its position on block 70 for illustration of detail. Each contact element 32 comprises a formed conductive strip having a first leg 60 and a second leg 62. Leg 62 is provided with a generally U-shaped area 64 therealong. First leg 60 and second leg 62 are formed in generally parallel relationship separated by a reverse bend 66. Contact elements 32 are constructed of electrically conductive material with sufficient resilience such that the second leg 62 will return to its generally parallel relationship to first leg 60 when not subjected to deflective force. 
     Each contact element 32 is fitted into contact receiving block 70 such that contact elements 32 are spaced apart in generally parallel insulated relationship with U-shaped sections 64 projecting upwardly. The second legs 62 including U-shaped sections 64 are free to be deflected somewhat downward when contact elements 32 are positioned within contact receiving block 70. First leg 60 of contact element 32 is provided with a protrusion 63 projecting below lower surface 61 thereof, said protrusion 63 establishing electrical contact with a conductive area upon circuit board 48, FIG. 5, to which contact receiving block 70 is mounted. 
     Referring now in particular to FIG. 5, it can be seen that contact receiving block 70 is stationed below bottom wall 30 of receptacle 20, with the U-shaped sections 64 of contact elements 32 normally projecting through opening 72 of bottom wall 30. 
     Frame 40 carries receptacle 20, being secured thereto by screw 74. Bracket 42 is secured to frame 40 at angle pieces 43 and 45 and is shaped to afford a convenient recline to frame 40. It can be seen that bracket 42 may be mounted by appropriate means to a vertical structure, or to a horizontal structure at its base 46. 
     FIG. 2 discloses, from the rear, the lower end 17 of the hand-held data entry terminal 4 of FIG. 1. Indentations 56 and 58 are provided on a wear plate 55 at the back of data entry terminal 4 and are disposed to receive detents 50 and 52 respectively when data entry terminal 4 is inserted in receptacle 20 and seated upon bottom wall 30 thereof A plurality of contact pads 80 are positioned upon end wall 18 of data entry terminal 4. When data entry terminal 4 is properly positioned in receptacle 20, contact pads 80 of data entry terminal 4 engage contact elements 32 at U-shaped sections 64 thereof in abutting pressure engagement. The engagement of contact pads 80 with contact elements 32 provides a substantial deflection of the legs 62 of the contact elements relative to legs 60, and results in substantial contact pressure between each U-shaped section 64 and the associated contact pad 86. The deflection of legs 62 is limited by stop 82, which can be best seen in FIG. 5. 
     The employment of detents 50 and 52 in cooperation with indentations 56 and 58 permits receptacle 20 to be disposed in other than generally vertical orientation while still allowing secure retention of data entry terminal 4 in frame 20 with reliable interengagement of contact pads 80 of data entry terminal 4 with contact elements 32 of the receptacle. 
     FIG. 6 discloses a multidocking unit wherein a plurality of receptacles 20 are mounted within an elongated frame 140. In the embodiment shown there are six receptacles 20. A data entry terminal 4 may be placed in each of the receptacles 20 of the unit of FIG. 6, such that six data entry terminal units may be recharged and/or integrated with a data collection system at one time. Each data entry terminal 4 may be selectively positioned in any of the receptacles 20 independently of any placement of other data entry terminals in any other receptacle 20. Frame 140 is supported at a slight recline by a bracket 142 which comprises base 146 and upstanding wall 148. Mounting means 102 is optionally available to secure bracket 142 to a vertical structure, if desired. 
     OPERATION OF THE EMBODIMENT OF FIGS. 1-5 
     As the need arises to recharge the internal batteries of one or more data entry terminal 4, or to feed data to or collect data from said data entry terminal 4, the data entry terminal 4 may be placed in a receptacle 20 such that the contact pads 80 of data entry terminal 4 engage and depress the resilient legs 62 of contact elements 32 of receptacle 20. Since contact pads 80 and contact elements 32 are electrically conductive, the engagement of a contact pad 80 with a contact element 32 provides a completed electrical pathway such that electrical charging and electrical communication between the docking system 2 and data entry terminal 4 may be accomplished. 
     Detents 50 and 52 of rear wall 26 of receptacle 20 engage mating indentations 56 and 58 on the rear of data entry terminal 4 such that sufficient mechanical rigidity is achieved between data entry terminal 4 and receptacle 20 to maintain firm pressure engagement between contact pads 80 of data entry terminal 4 and contact elements 32 of receptacle 20. 
     Bracket 42 of docket unit 2 may be mounted to a vertical wall over a telephone mounting bracket having vertically spaced apart studs and a telephone jack which remains accessible through opening 49 of plate 48 of bracket 42. 
     Once insertion of data entry terminal 4 is completed within receptacle 20, recharging of batteries and intercommunication of the data entry terminal with outside computing facilities may be achieved. 
     Reference is made to a copending application of Patrick H. Davis, U.S. Ser. No. 07/327,660 filed Mar. 23, 1989,  which contains description and claims relating to FIGS. 1 to 6, and the entire disclosure of this copending application including the drawings is hereby incorporated herein by reference. 
     Description of FIGS. 7-11 
     FIGS. 7 to 11 correspond generally with figures one to five of a pending design patent application U.S. Ser. No. 07/303,557 filed Jan. 27, 1989, and the entire disclosure including the drawings of Ser. No. 07/303,557 is incorporated herein by reference. 
     FIG. 7 shows a multidock system 100 with a series of receptacle modules 101-106 corresponding to the receptacles 20 of FIGS. 1 and 6. Each receptacle may be identical to the receptacle 20 of FIG. 1, and be provided with detents 50, 52 as in FIGS. 4-5 
     FIG. 9 shows a left end cap 111 for the system 100, and right hand end cap 112, FIG. 7 may be a mirror image of left end cap 111. 
     As seen in FIGS. 8 and 9, the system 100 may be provided with a mounting bracket 120, with feet such as 121, 122, FIG. 7, and 123, 124, FIG. 8, for facilitating mounting of an horizontal support surface of a bench or the like. For wall mounting, shoulder rivets 125-128, FIG. 8, are provided. 
     FIG. 10 shows the sets of spring fingers, 141-146, corresponding to contacts 32, FIG. 3, for the respective receptacle modules 101-106. 
     Since each of the receptacle modules is designed to function the same as the receptacle 20 of FIG. 1, a further description of FIGS. 7 to 11 would be superfluous A major advantage of the multidock system is that it may be formed of parts identical to parts of the receptacle 20 shown in FIGS. 1-5. 
     Description of FIGS. 12-16 
     FIGS. 12 to 16 show the general subject matter of figures six to ten of the incorporated design patent application U.S. Ser. No. 07/303,557. 
     FIGS 12 to 16 may illustrate a single dock assembly which is identical to that of FIGS. 1 to 5 and accordingly the same reference numerals have been applied. End caps 111&#39;, 112, may be of the same construction as parts 111, 112, FIGS. 7-9. FIGS. 12 to 16 further show a single dock stand 160, which may have feet 161-164 for accommodating mounting of the single dock on a horizontal surface, e.g. of a desk or table. Slots 171, 172, FIG. 16, accommodate wall mounting of the assembly 
     Description of FIGS. 17-22 
     FIGS. 17 to 22 show a network controller unit 200 which may be associated with the multidock assembly 100, FIGS. 7 to 11, for furnishing charging potential to the terminals in the respective receptacle modules such as 101-106. The controller 200 may also, for example, control communication between the respective terminals and a host computer system. 
     The controller 200 is shown as comprising a base 201 and cover 202 forming a housing for the electrical components. A feet bracket 203 has front feet 206, FIG. 20, and 207, FIG. 18, while the base 201 directly mounts rear feet 208, 209. Wall mounting is accommodated by shouldered rivets 211, 212. The cover has a keyboard 220 and a display 221 at the front thereof. A loading slot 224, FIG. 18, may be at the left side for receiving a floppy disk. A cooling fan outlet 226 is shown in FIG. 20. 
     A power receptacle 230 and a power control switch 231 are indicated in FIG. 18. FIG. 21 shows a bracket 234 for mounting six D-sub type connectors. 
     The internal structure and operation of the controller 200 will be described in detail hereinafter. 
     Description of FIGS. 23-27 
     FIGS. 23 to 27 show a preferred electrical configuration for the multidock arrangement of FIGS. 6 and 7 to 11. 
     As shown in FIG. 23, printed circuit boards 301, 302 may each extend continuously through a set of three receptacle modules, i.e. board 301 extends through modules 101-103 and board 302 is associated with modules 104-106. The two boards 301, 302 may be interconnected by a flex cable 303. The set of six modules of a multidock unit may be coupled with the controller unit 200 by means of one of two end connector receptacles 311, 312, FIG. 25. The other end connector receptacle may connect the system to a further multidocking unit, for example. 
     In the embodiment of FIGS. 23-27, a single continuous receptacle support plate 420 may have the receptacle modules 101-106 secured therewith by means of respective hooks such as 421, FIG. 24, which are formed integrally with the rear walls of the modules by offsetting the metal from slots 431-436, FIG. 23. Each receptacle module is then fixed in place by means of a screw such as 437, FIG. 24, and a thread lock adhesive. While the support plate 420 is common to the six receptacle modules 101-106, the multidock base 120 extends only over the area of the central four receptacle units so that connector means 311, 312, FIG. 25, are accessible from behind modules 101 and 106. 
     Further screws 438 secure the connectors 311, 312 to the receptacle support plate 420. 
     Screws 439, FIG. 25, secure latch blocks 440, FIG. 27, and bracket 441 to form the connectors such as 312. As seen in FIG. 26, latch blocks 440 have notches 440a for securing mating connectors therewith. 
     For example, a cable may have a connector at one end engaged with a D-sub connector at position 450, FIG. 21, and a connector at the opposite end engaged with nine position D-sub connector part 451 or 452 of connector 311 or 312, FIG. 25. 
     FIG. 27 illustrates how docking connectors 461-466 are fastened to printed circuit boards 301, 302 by screws 467 and nuts 468 so as to clamp the spring contacts 470 to respective contact means 471-476, FIG. 26, of the printed circuit boards. The sets of spring fingers 141-146, FIG. 10, formed by contacts 470 project through openings in the bottom of the receptacle modules 101-106 so as to engage external contacts of hand-held data terminals inserted into the respective docking modules the same as explained in reference to FIGS. 1 through 6. 
     EXEMPLARY NETWORK CONFIGURATION, FIG. 28 
     A preferred network configuration would comprise a primary and multiple secondary devices, where a controller module such as 200, FIGS. 21-26, is the primary device, and hand-held data terminals, printers and optional interfaces and bridge products are the secondary devices. Hand-held data terminals also may operate in a network without a controller. In a preferred configuration, communication in the network is via a RS-485 bus. The controller 200 in addition to its data communication function may provide a power system for charging of the terminals in the docking modules such as 101-106, FIG. 23, and in some cases may also supply system power to the secondary devices. Where the capacity of the controller 200 is exceeded, an auxiliary power unit (APU) may connect with one of the receptacles 450, FIG. 21 to receive communication from the controller 200, and may itself contain a power system for associated terminals for other secondary devices. The network is thus preferably a local area network (LAN), with physical connectivity to the network provided by multidock units such as shown in FIGS. 7-11 and single dock units such as indicated in FIGS. 12-16. These devices may be connected together using connection receptacles such as shown at 451, 452, FIG. 25, using simple twisted pair cabling. FIG. 28 shows a block diagram of an exemplary network configuration, and a brief description of each network module is as follows: 
     Single Dock, (FIGS. 1-5, 12-16 and 28A) 
     The single dock is a passive device for electrical connection to a communications network and power system. Charging voltage may be provided through a LAN interface and a separate connector e.g. 76, FIG. 5. The dock establishes proper alignment and retention for a hand-held data terminal so as to enable host communications. A RS-232 port allows communication between a single dock as represented at 400, FIG. 28A, and a modem 401, or alternatively allows a direct connection between the single dock 400 and a host. 
     Multidock, (FIGS. 6-11 and 23-28) 
     A desired number of hand-held data terminals are connected to the local area network with one or more multidocks as represented at 411 and 412, FIG. 28. Six single terminal modules are integrated into one enclosure as illustrated in FIG. 23. Quick release connectors such as 311, 312, FIG. 25, located at each end, allow connectivity to additional terminal interfaces and other devices. Individual optional locking devices are available for providing security (preventing removal of a terminal from its docking receptacle without a key or the like). 
     Auxiliary Power Unit, (FIGS. 28 and 29, 29A) 
     An auxiliary power unit such as represented at 421, FIG. 28, may develop charging voltage and operating power for up to twenty-four hand-held data terminals, e.g. associated with four multidocks such as 422. In a particular system a controller 400 may be capable of charging only twenty-four hand-held data terminals on its primary LAN channel indicated at 425. The auxiliary power unit 421 may be used on a secondary LAN channel 426 or used to extend beyond the original twenty-four terminals on the primary LAN channel 425. A repeater reshapes the RS-485 signal so that it may drive an additional twenty-four logical units. Each functional block of the auxiliary power unit 421 is shown in FIG. 29. 
     In FIG. 29, the secondary LAN channel may comprise conductors 426A and 426B, while output channel 427 from the auxiliary power unit to the multidock 422, FIG. 28, may comprise conductors 427A and 427B. The connection between controller 400 and auxiliary power unit 421 may additionally include a direction control line 431, for controlling repeater components 432 and 433. As represented in FIG. 29, a plus fifteen volt power supply component 435 and a five volt regulator component 436 may also be included in the auxiliary power unit, and may receive a conventional commercial one hundred and twenty volt alternating current via a receptacle essentially corresponding to receptacle 230, FIG. 18. 
     Controller, (400, FIG. 28) 
     The network controller 400 may be a multipurpose communications controller designed to provide a flexible interface for communications between a customer&#39;s host computer and hand-held data terminals and the like. Data ports may comprise a host port leading to a host channel 431, and one to three terminal ports such as associated with a channels 425, 426 and 432 in FIG. 28. An optional LAN port may be selected through software which precludes the use of the third terminal port associated with channel 432 in FIG. 28. The second LAN port and secondary channel 426 is connected in parallel with the primary LAN port associated with channel 425, for added configuration capabilities. 
     Flexibility allows the controller 400 to be used as a communication gateway at a host location or as a LAN interface device in remote depots where a multiplicity of hand-held data terminals are to be downloaded, have their batteries recharged and so on. Port expansion is possible by chaining additional controllers together via the communications ports. 
     The mechanical design allows the controller 400 to connect to multidocks such as 411 with quick-connect cables for easy configuration and serviceability. The exemplary controller 200 of FIG. 21 may have six connectors leading to channels such as indicated at 425, 426, 431, 432 and 433. 
     In the example of RS-485 LAN, all devices which interface to the LAN connect to a single wire pair using a balanced transceiver. This standard is advantageous since it allows for multiple drivers and receivers, high noise immunity over relatively long lines, operation with wide common mode voltages, and the provision by the drivers of self protection against contention. 
     The RS-232 interface does not directly affect the architecture of the controller 400. Under normal system configurations, this interface will be used to communicate with various modems and non-LAN products. 
     The controller 400 may be configured as a communications controller. Four sync/async RS-232 ports are software configured for host and remote communication channels. A RS-232 port will enable host communications using the most common asynchronous and synchronous protocols. These include Bisync, two-way TTY and ADCCP. During system configuration, the target protocol is specific and soft-loaded from a removable disk inserted in the disk receptacle slot 224, FIG. 18, so as to be loaded in executable RAM. 
     The dimensions of the controller 200 are generally as follows: Height--9.5 inches max., width 13.0 inches max., depth --7.5 inches. The weight is five pounds maximum. As previously described, the controller will have the option to be rigidly attached to a surface or wall. The mounting technique allows access to all cables and power connections, and removal of adjacent multidocks without removing the controller from its mounting surface. 
     Connectors 
     The RS-485 LAN may comprise one primary port and one secondary port. The ports may use nine pine D-sub connectors. Signal definition is identified below. 
     
         ______________________________________Pin Number           Signal Name______________________________________Primary Port (J6)1                    V+2                    +RS-4853                    -RS-4854                    V+5                    Direction6                    N.C.7                    GND8                    GND9                    N.C.Secondary Port (J7)1                    N.C.2                    +RS-4853                    -RS-4854                    N.C.5                    Direction6                    N.C.7                    GND8                    GND9                    N.C.______________________________________ 
    
     Each of the RS-232 ports are fifteen pin D-sub male connectors, with pin assignments as follows: 
     
         ______________________________________Pin Number          Signal Name______________________________________1                   N.C.2                   -TXD3                   DTR4                   -RXD5                   DSR6                   RTS7                   CTS8                   GND9                   N.C.10                  N.C.11                  TRXCO12                  TRXCI13                  RTXCO14                  RTXCI15                  N.C.______________________________________ 
    
     The LCD display 221 may be a two line by sixteen character format. The keyboard may be a sixteen position four row by four column matrix. Depression of the keys may result in positive tactile feel. Environmentally the assembly may resist exposure to moisture. 
     The AC line cord my be removable from receptacle 230. 
     The disc drive associated with loading slot 224 may comprise a 3.5 inch half-height unit capable of an unformatted capacity of one megabyte per disk (720KB formatted). An optional two megabyte per disk drive is available. 
     Exemplary Controller Circuit, (FIG. 30) 
     A discussion of the functional blocks of the exemplary controller circuit of FIG. 30 is presented in the following paragraphs. 
     Microcomputer 500, (FIG. 30) 
     The microcomputer 500 may be a type 80C186, some applicable features being as follows: 
     16 bit external bus 
     Clock generator 
     Two independent DMA channels 
     Programmable interrupt controller 
     Three programmable 16-bit timers 
     Programmable memory and peripheral chip select logic 
     Programmable wait-state generator 
     Local bus controller 
     Additional detailed information is available in the Intel 80C186 user&#39;s manual. 
     The microcontroller memory map of TABLE A on the following page gives the general organization of various functions within the memory space by way of example. 
     
                                           TABLE A__________________________________________________________________________Controller Memory Map__________________________________________________________________________ ##STR1## ##STR2##__________________________________________________________________________ 
    
     Since the application software may reside in RAM component 501 and in removable disk storage, board level EPROM component 502 may only provide boot functions and diagnostics. This approach allows a stable well tested EPROM to be released with the system without future updates. A socket is preferably provided for easy access. 
     All application programs execute from RAM (e.g. 501, FIG. 30A). This memory space is a maximum of 768K (see memory map in TABLE A). All application programs are retained on the removable 3.5 inch disks and are booted to RAM on power up. This allows RAM to be volatile, eliminating the need for optional battery back-up in some cases. 
     Two 85C30 SCC&#39;s, SCC1 and SCC2, FIG. 30B, may be used for host and terminal communications. The four channels may be configured as synchronous or asynchronous, RS-232 ports. One of the four communication ports may be software configured for RS-485 LAN communications. 
     Real-time clock component 550 may be a Motorola type MC146818. This device is power backed-up to maintain accurate time during power interruptions of various durations depending on the backup options. When an external battery is not used, a capacitor maintains memory and time for up to two weeks. The battery option may extend clock operation for more than three months. 
     Along with internal registers for time, date and other data, the MC146818 provides fifty bytes of general purpose battery backed-up RAM. 
     SYNC/ASYNC interface component 560, FIG. 30B, may comprise ports A, B, C and D as shown at the right in FIG. 30B. For synchronous protocols, transmit and receive clock lines are available. The controller or connecting device may generate the clocks and is selected by a direction signal from the microprocessor and use of one of two possible cables between the host and controller. 
     Autoanswer modems may be connected to this port, and autodial may be initiated using Hayes commands. 
     The LAN interface component 570, FIG. 30B, may consist of primary and secondary channels. Each channel is driven by an RS-485 transceiver. The primary channel can drive twenty-four logical units or transceivers. Multidocks connect directly to the controller using the primary channel with the use of cables. The secondary RS-485 channel connects to additional multidocks using cables and an APU (FIGS. 29-29A) for charging. 
     The RS-485 or the fourth RS-232 port is selectable through software (485SEL). This allows communication with four RS-232 devices (e.g. host and three modems) and also devices directly connected to the RS-485 LAN. 
     A LCD interface 571 may be a self contained module with data lines, read/write strobe and two control lines for enabling the module (PCS4) and controlling power to the device. 
     Keyboard interface 572 may strobe the four columns of the 4 ×4 matrix and detect corresponding key closures on one of the four rows. Keyboard activity may be interrupt driven using INIT3. Debounce key rollover will be handled in the firmware keyboard driver. Once the interrupt is detected the key code may be read from the keyboard interface. The chip enable signal may be PCS5. 
     The 3.5 inch disk drive controller 573 may be an Intel type 82072 high integration floppy disk controller with built-in analog data separator. This provides the interface requirements to the 3.5 inch disk drive of network controller 200. 
     Five DMA sources may be logically &#34;ORed&#34; to the two available DMA request inputs of the DMA controller of microcomputer 500. The software may keep track of the active device within each group &#34;ORed&#34; to the specific DMA channel A list of the DMA sources and their respective grouping is listed below. 
     SCC Port A (LAN)=DRQ0 
     Disk Controller=DRQ1 
     The interrupt source and type of interrupt to the processor 500 may be as listed below. 
     
         ______________________________________Source               Interrupt Type______________________________________Manual Reset         NMISCC Channels A,B,C,D INIT0Disk Drive Controller                INIT1Keyboard             INIT3______________________________________ 
    
     A DC/DC converter 581, FIG. 30B, may provide logic power. It may be designed to operate over a wide input voltage range of thirteen to twenty volts. The converter is board resident and allows the use of a relatively inexpensive single output power supply used also for charge voltage to the multidocks on the primary channel. 
     A linear regulator 582 may be powered by the plus fifteen volt power supply and provide plus twelve volts to the disk drive. 
     A back-up battery is indicated at 583 and may consist of a 3.6 volt, three-cell nicad battery pack with a 500 amp-hour capacity. 
     A self oscillating buzzer 584 may be enabled under microprocessor control. 
     Charge voltage and input power to the controller board may be provided by a single output power supply. Output voltage may be in the range from not less than fifteen volts to not greater than twenty volts. The supply may be capable of sourcing 7.0 amperes and may current limit before 8.0 amperes. 
     Software Discussion 
     The Network Controller 400, FIG. 28, may provide high-speed LAN communications for directly connected hand-held terminals via a communications protocol known by the initials NPCP (Norand Portable Communication Protocol). 
     The Network Controller may provide both synchronous and asynchronous communications support for devices which are remote to the host site. This support may include auto-dial and auto-answer capabilities. 
     The Network Controller may provide communications support for existing TTY and ADCCP devices of Norand Corporation. 
     The Network Controller may support an existing file transfer protocol for hand-held computers of Norand Corporation which consists of a single upload session followed by a single download session. 
     The Network Controller may provide a migration path to a file transfer protocol which may require multiple uploads and downloads. 
     The file transfer system implemented by the Network Controller my provide a migration path for full-duplex Network Controller to Network Controller communications. 
     A mechanism may be provided to chain Network Controllers, either directly or over switched lines. The chaining mechanism may be used to provide additional RS-232 ports at a host site or to establish a session with a controller at a remote site. 
     The Network Controller may provide the host with a method for initiating a communications session with a specific terminal (not necessarily a hand-held data terminal). 
     The Network Controller may provide a method for &#34;broadcasting&#34; a file or files to multiple terminals. 
     The Network Controller may provide a method for storing user files on the system. 
     The Network Controller may provide a method for downloading files requested by hand-held data terminals, independently of a host computer. 
     The Network Controller may provide a method for downloading files to hand-held data terminals under the direction of a host computer. The origination of the file may be transparent to the hand-held terminal. 
     Communication ports on the Network Controller may be software configurable. 
     The Network Controller may provide the user with an easy-to-use interface for changing configuration parameters. 
     APPENDIX A (not printed here, but is available in the application file) provides the information required to operate the network controller of FIGS. 30A, 30B to carry out each of the functions specified in this Software Discussion. 
     A detailed exemplary NPCP program listing for RAM component 501, FIG. 30A, is found in APPENDIX B (not printed here, but is available in the application file). 
     System Configuration 
     The Network Controller may be configured through a menu driven program using the keyboard and display. 
     The following examples represent some possible system configurations. 
     (A) Host to local Network Controller configurations: ##STR3## 
     Network Controllers at the host site may be configured with four RS232 ports, or with three RS232 ports and one RS485 port. The RS485 port is used if hand-held computers are in a LAN at the host site. One of the RS232 ports is used for communication with the host, and the remaining RS232 ports are used for remote communications. Currently, the host port data-link protocol must be transparent point-to-point bisynchronous or asychronous with (optional) parity checking. The host port may be configured at speeds up to 19,200 bps. 
     Local Network Controller to remote Network Controller configurations: ##STR4## 
     Several options are provided for support of remote sites. Network Controllers at remote sites have one RS232 &#34;host&#34; port, for communications with a &#34;host&#34; Network Controller, and one LAN port. The communications link to the host controller can be manually configured to use either ADCCP or a TTY extension as the data-link protocol. ADCCP ports on a host controller may communicate with either remote controllers configured for ADCCP or with ADCCP terminals in Multi-quad Lockboxes. TTY ports on a host controller may communicate with 4300/4400 terminals, 101/121/141 terminals or other TTY devices of Norand Corporation. The host controller determines if a remote device is a Network Controller or an ADCCP/TTY device, when the connection is made. The host may dynamically configure RS232 ports on a Network Controller as either ADCCP or TTY ports when the port is activated. This facilitates the use of a single port for synchronous communications to remote Network Controllers and asynchronous communications to TTY devices. 
     Information on 4300/4400 terminals which may operate on the network of FIG. 28 using the NPCP software of APPENDICES A and B is found in the following pending applications: 
     (1) Cargin, Jr., Kelly, Fischer, Gibbs, Boatwright and Durbin application for patent entitled &#34;HAND-HELD COMPUTER TERMINAL&#34; U.S. Ser. No. 07/339,330 filed Apr. 14, l989 (now abandoned). 
     (2) Miller, Koenck, Walter, Kubler, Cargin, Hanson, Davis and Schultz application for patent entitled &#34;DATA CAPTURE SYSTEM WITH COMMUNICATING AND RECHARGING DOCKING APPARATUS, AND MODULAR PRINTER AND HAND-HELD DATA TERMINAL MEANS COOPERABLE THEREWITH&#34; U.S. Ser. No. 07/345,771 filed on May 2, 1989 (now abandoned). 
     The entire disclosure of each of these pending applications including the drawings is hereby incorporated herein by reference in its entirety. 
     Software interface 
     The Network Controller maintains sessions between the host computer and hand-held computers of Norand Corporation (or other devices) on logical channels. As used here, &#34;channel&#34; consistently refers to a logical data channel and &#34;port&#34; refers to the physical link, which may contain one or more logical channels. Data from the Network Controller to the host is identified by channel number and record type. With the possible exception of an initialization record, data from the host is sent in response to a &#34;channel request&#34; from the Network Controller and is identified by record type only. (Record types &#34;0&#34; to &#34;5&#34; are, for the most part, compatible with NI315/NI311 record types). 
     Logical Channels - Data transfers to/from the host computer are on logical channels. The logical channel identifier field, which precedes data to the host, consists of a 1-byte &#34;controller channel&#34; followed by a 1-byte &#34;terminal channel&#34;. Controller channels may contain terminal channels ranging from &#34;1&#34; to &#34;9&#34;. Controller channels range from &#34;0&#34; to &#34;9&#34;. New controller channels are opened each time a secondary controller--with multiple &#34;terminal&#34; ports--connects to the &#34;host&#34; controller. An identification record is sent to the host when a new controller channel is opened. The identification record contains a location identifier for the new controller, port information, and a channel number for the controller. 
     Note: Only one controller channel is required, to the host, if no secondary controllers have multiple terminal ports. Data transfers for secondary controllers can occur on the primary controller channel (e.g: &#34;0&#34;). In this case, the host could treat the 2-byte channel identifier as a single field and avoid double indexing, or, optionally, the channel identifier could be reduced to a 1-byte field. 
     Records from the Network Controller to the host computer. 
     Records from the Network Controller are always preceded by a channel identifier, followed by a 1-byte record type. Network Controller record types are: 
     0--UPLOAD DATA--Upload data records contain &#34;upload&#34; data from hand-held terminals. The host is guaranteed that the data from (or to) a terminal is contiguous on a logical channel. 
     2--END-OF-S ESSION--End-of-session records are sent after each hand-held session completes, to indicate the status of the communications session 
     2--DATA REQUEST - Data request records are used to request data from the host computer. The host may respond with a data record, a file directive or an end-of-data record. 
     3--INACTIVE STATUS--Active/Inactive status records are sent by the controller when the host port is inactive. An inactive status record indicates that no terminals are currently active on the channel. 
     4--ACTIVE STATUS--Active/Inactive status records are sent by the controller when the host port is inactive. An active status record indicates that a terminal(s) is currently active on the channel. 
     5--ACTIVATE REQUEST--Activate request records are used to obtain the information from the host which is necessary to activate the specified channel. Activate requests are sent for a physical port whenever the port is disconnected and include the status of the previous activate request for the port. The host may respond with an auto-dial activation record, an auto-answer activation record, or with a deactivate record. Auto-answer activation records may include a &#34;timeout period&#34; specified in minutes. If the timeout period expires, the port will be deactivated and a new activation request will be generated for the port. This feature will allow a port to be toggled between auto-answer and auto-dial. 
     Note: Modem configuration information is only required for modem types not supported by Norand. 
     Note: The activate request record replaces the NI311/NI315 phone request record. 
     6--SPECIAL REQUESTS--Special requests are used to prompt the host with an extended set of Network Controller requests. The host must examine a &#34;subtype&#34; filed to determine the type of special request. Currently, two subtypes of special requests are required: 
     1--FILE REQUEST--File requests are sent to the host computer each time a Network Controller is brought-on-line. The host may respond to a file request with a one of several possible file directives or with an end-of-data record. File requests/directives can be used to load and maintain files stored on the Network Controller diskette and in RAM. The controller will send file requests to the host until the host responds with an end-of-data record. The file request option may be turned on or off with a flag in the initialization record. 
     2--CONNECTION REQUEST--Connection requests are sent to the host to allow the host to establish a communications session with a specific device or terminal. The connection request includes a field to identify the location of the Network Controller which generated the request. The host may respond with a device identifier (terminal ID) to establish a session or may respond with an end-of-data record. The connection request option is enabled with a flag in the initialization or activation record. If the option is turned on, the host will be prompted with a connection request: 1) at the beginning of a session with a Network Controller, 2) after each end-of-session record is sent, and 3) after a fixed time period expires with no activity on a channel. An end-of-session always follows a connect request, either after the request fails or after the terminal session completes. 
     Note: Inactive status records will not be sent to channels with connection requests enabled. 
     7--DIRECTIVE STATUS--Directive status records are sent to the host computer to supply the host with completion status information for an outstanding host directive. The directive type is included in the status record. 
     8--IDENTIFICATION RECORD--A Network Controller may be configured with the keyboard to send a location identifier to the host computer or host Network Controller. If the identification record is enabled it will be the first record sent in a communications session. The identification record is required for remote Network Controllers. The identification record includes a location ID, port information, the number of non-host &#34;terminal&#34; ports on the controller. If this number is greater than one: 1) another &#34;controller channel&#34; will be opened to the host, 2) the identification record will be forwarded to the host on the new channel, 3) an initialization record will be expected, from the host, on the channel. 
     Records from the host to the Network Controller. 
     Records are sent from the host to the Network Controller in response to channel requests from the controller, with the exception of the first initialization record Host record 
     0--DOWNLOAD DATA--Download data records are sent from the host to the controller in response to download requests, and connection requests 
     1--END-OF-DATA--End-of-data records may be sent from the host to the controller in response to data requests and special requests. The end-of-data record indicates that no data exists for the type of request specified. 
     2--INITIALIZATION RECORD--The initialization record is used to configure the host/Network Controller communications session. The initialization record is sent at the beginning of a communications session with a controller. For remote controllers, the initialization record is sent in response to an identification record. 
     3--AUTO-ANSWER ACTIVATION RECORD--Auto-answer activation records are sent in response to an activation request and may include optional modem and port configuration parameters. An auto-answer activation record may also include an optional timeout parameter, which contains the maximum number of minutes that the controller should wait for a connection on the port. After the timeout has expired, the port will be deactivated and another activation request will be sent to the host. 
     Note: The auto-answer activation record replaces the NI311/NI315 &#34;cancel-auto-dial&#34; record. 
     4--AUTO-DIAL ACTIVATION RECORD--Auto-dial activation records are sent in response to an activation request and include a phone number and may include optional modem and port configuration parameters. 
     Note: The host can use activation records to dynamically change port type (e.g. ADCCP to TTY). 
     5--DEACTIVATE (for one minute)--Deactivate records may be sent by the host computer to deactivate a channel requesting activation, for one minute. 
     6--HOST DIRECTIVE--A host directive may be sent by the host in response to a special (file or connect) request or data request from the Network Controller. The host directive contains a &#34;subtype&#34; field. The host will receive a status after the directive has completed, either normally or abnormally. Currently, five subtypes of host directives are required: 
     1--FILE UPLOAD DIRECTIVE--An upload request can be used to upload a user file stored on the disk of the controller which generated the file request. For example, this feature can be used to obtain the directory of user files on the controller disk. After the requested file is uploaded the controller will sent another file request to the host. 
     2--LOAD DIRECTIVE--A load directive may be sent in response to a file request, to download a file to the controller which generated the file request. The load directive must include a directory entry which specifies the file name, date, size, etc. After the load directive has been sent, the controller will send data requests for file data until the host responds with an end-of-data record. The data will be written to a file on disk, with the name specified. Existing files with the same name will be overwritten and excess space will be recovered. After the file has been successfully written, a status field will be set to indicate tat the file is in a defined state and is available for use. 
     3--DELETE DIRECTIVE--A delete directive may be sent in response to a file request to delete a data file on the Network Controller. A delete directive will fail if the file is in use. 
     4--DOWNLOAD DIRECTIVE--A download directive may be sent in response to a data request and is used to download a file which exists on a controller&#39;s disk to a terminal on the attached LAN. The terminal which receives the download data should not be able to distinguish between &#34;download directive data&#34; and data from the host. 
     5--CONNECT DIRECTIVE--A connect directive may be sent in response to a &#34;connect request&#34; from the Network Controller to enable the host to connect to a specific terminal on the LAN. The connect directive must contain a terminal identifier. 
     Remote Network Controller interface 
     &#34;Remote controllers&#34; can be configured for connection to a &#34;host controller&#34;, through any of the four ports, over either a switched or non-switched line. The connection will be synchronous and will use ADCCP for data-link control. The controller will acknowledge an ADCCP poll (SNRM) directed to its destination address. The remote controller will then send an identification record which will include the logical location of the controller (for customer use) and a control byte with a device identifier. 
     Remote Network Controller record types are identical to the record types for a local Network Controller. If the remote controller is configured for multiple terminal ports, the host controller will open a new channel for the remote controller and will simply pass all data through, to the customer&#39;s host computer. If the remote controller is configured for a single LAN port, the host controller can, optionally, intercept identification and activation records, and can pass data through on existing channels to the host. 
     Remote controllers will default to auto-answer mode. 
     Auto-dialing with a remote controller: 
     Controllers in a remote &#34;depot&#34; can be configured to auto-dial a phone number(s) at the host site. A primary and alternate phone number may be entered with the keyboard, along with an associated dial time, number of retries, retry wait time, failure threshold, modem type, and minimum number of terminals. The primary phone number will first be dialed after the dial time is reached and the minimum number of terminals are connected. The minimum number of terminals will default to one, and must be non-zero. If the dial time is zero, the primary number will be dialed as soon as the minimum number of terminals are connected. The controller will retry the primary number after the wait time has expired and at least one terminal is connected. Retries will continue until the retry count is exceeded or the failure threshold is reached. If the failure threshold is reached the alternate phone number will be used for the next call. 
     Remote controllers will default to auto-answer mode. 
     ESTABLISHING COMMUNICATIONS SESSIONS WITH TERMINALS OF NORAND CORPORATION 
     A. NON-LAN TERMINALS. This category of terminals includes existing TTY and ADCCP terminals of Norand Corporation, and 4330/4400 terminals on an RS232 interface. Non-LAN terminals may respond to a poll from the host (or host controller) with one or more upload data blocks, and then receive zero or more download blocks from the host. The host, typically, identifies the terminal by an identifier in the upload data and associates download data with the identifier. 
     Note: Support for booting 3X/4X terminals in a non-LAN environment is currently undefined. 
     B. LAN TERMINALS. LAN terminals are attached to a high-speed RS485 multi-drop link on the Network Controller. The Network Controller determines what logical terminals are attached to the network, and is responsible for maintaining a current terminal table. The terminal table must include a LAN address and an associated terminal name, which does not need to be unique and can be a &#34;wild card&#34; name. The name of a terminal can be fixed or can be set by a customer. For example, the terminal name can be a function of a bakery route ID, or can be hard-coded in the firmware of the device supporting the terminal. 
     1. HOST-TO-TERMINAL SESSIONS. Host-to-terminal sessions can be initiated in one of two ways: 
     a) LISTEN-ANY (MYID, YOURID)--In this mode a controller application identifies itself and will listen to any terminal trying to connect to &#34;myid&#34;. After a successful connection, a terminal name is returned in &#34;yourid&#34;. &#34;Myid&#34; could be hard-coded in the software/firmware of the controller and terminal. 
     b) OPEN-SPECIFIC (MYID, YOURID)--In this mode a controller application will attempt to connect to a terminal specified by &#34;yourid&#34;. Open-specific requests are generated when the host responds to a connect-request with a terminal ID. The host and terminal must agree on the terminal ID (e.g. &#34;yourid&#34;) used to make the connection. 
     After a terminal connects, the controller simply provides a link between the host and the terminal. In a single session, the terminal can send zero or more upload records to the host, and then the host may send zero or more download records to the terminal. Nothing prevents a terminal on the LAN from having additional uploads and downloads or from establishing multiple sessions. 
     2. CONTROLLER-TO-TERMINAL SESSIONS--The Network Controller will provide a continuous application which will attempt to communicate to devices on the LAN, whether or not the host is connected. The application will be provided for the purpose of downloading data files from the system disk to terminals on the LAN. This facility could be used to load HHC&#39;s with operating system files or a kernel program, for example. The application will issue a listen-any (myid, yourid) and will establish sessions with terminals attempting to connect to &#34;myid&#34;. The terminal can optionally send a list of the names of files to download. If the terminal does not send a list of download files, the controller application will scan a data file directory for &#34;boot&#34; files and will download those files to the terminal. The host computer will be provided with facilities to maintain data files kept on the controller. In addition, a facility will be provided through the controller keyboard and display which allows the user to load data files from a 31/2 inch MS-DOS diskette. The host will receive no status information for controller-to-terminal sessions. Using this option while the host is in session may result in contention for a file. 
     STORE-AND-FORWARD FILE TRANSFER SUPPORT 
     The Network Controller will provide the host computer with the facilities to maintain data files on the Network Controller. (Refer to the section describing file requests and host directives.) In addition, a facility will be provided to allow the user to load data files from a 31/2 inch diskette. All data files will be written to the Network Controller system diskette, and will be read into RAM during the controller&#39;s boot cycle. An entry for each data file will exist in a data directory file. The fields in the directory entries are primarily under host control and are intended for version control. The directory entry will include a type field, which may be used to connect the file to a specific application (i.e. a boot application). Data files which do not have an entry in the directory file will be deleted during the boot cycle. 
     Host file maintenance will occur after the host session has been established, and before communications begin on any of the other Network Controller ports. The host is responsible for examining the data file directory, via a &#34;directory file request&#34;, and ensuring that all data files are current. After normal communications begin, the host may direct that any data file be sent to a terminal requesting a download, by sending a download directive which contains directory information for the file. 
     A task will run continuously on the Network Controller and will open two types of NPCP &#34;listen&#34; sessions. The first type will simply send &#34;boot type&#34; files to LAN terminals which connect to it. The second session will read a list of files from terminals which connect to it and then attempt to download those files to the terminal. The user is responsible for ensuring that any necessary files are in a defined state on the Network Controller. 
     EXAMPLE TELECOM SESSION--The following example is a step-by-step representation of a host to Network Controller communications session. It is important to remember that any logical sequence of steps will proceed in a &#34;single-file&#34; order on a logical channel, but that steps from different logical channels can be interspersed on the host port. 
     1. The host opens the communications port to the Network Controller. 
     2. The Network Controller sends an (optional) identification record to the host. 
     3. The host sends an initialization record to the Network Controller. The initialization record configures the controller and enables file requests. 
     4. The controller sends a file request to the host. 
     5. The host responds by sending an upload directive to the controller to upload the directory file. 
     6. The controller sends a directory of the data files on disk to the host, followed by the directive status. 
     7. The controller sends another file request to the host. 
     8. The host responds by sending a file &#34;load&#34; directive to the controller. 
     9. The controller determines that the load directive is acceptable, opens the respective file, and sends a data request to the host. 
     10. The host sends a data record to the controller. 
     11. The controller sends a data request to the host. 
     12. Steps 10 and 11 may be repeated any number of times. 
     13. The host sends and end-of-data record to the controller. 
     14. The controller closes the file, updates the status of the file in the file directory, and sends a directive status to the host. 
     15. The controller sends another file request to the host. 
     16. The host sends an end-of-data record to the controller. 
     17. The controller sends an activation request for the LAN port and each of the remote ports (ports 2 and 3). 
     18. The host responds with an auto-answer activation record for the LAN port and port 2, and an auto-dial activation record for port 3. Port 2 is configured to be asynchronous and port 3 is configured to be synchronous. Connection requests are enabled for the LAN port. 
     19. A connection is established with a remote controller on port 3. 
     21. The remote controller sends an identification record to the host (via the local controller). 
     22. The host sends an initialization record to the remote controller, which enables file request processing. 
     23. The remote controller sends a file request record to the host, and file request processing proceeds as with the local controller. 
     24. The remote controller sends an activation request, for its LAN port, to the host. 
     25. The host responds by sending an auto-answer activation record to the remote controller. 
     26. The remote controller sends an upload data record, from a terminal on its LAN port, to the host. 
     27. Step 26 can be repeated any number of times. 
     28. The remote controller sends a download data request to the host. 
     29. The host responds with an end-of-data record. 
     30. The remote controller sends a session status record from the terminal to the host. 
     31. Activity switches to the local LAN, and the local Network Controller sends a connect request record to the host. 
     32. The host responds with a connect directive to establish a session with a specific terminal. 
     33. The terminal is located and a directive status is sent to host which indicates that a session is established. 
     34. The local controller sends an upload data record, from the terminal to the host. 
     35. Step 34 can be repeated any number of times. 
     36. The local controller sends a data request record to the host. 
     37. The host responds by sending a &#34;download file directive&#34; to the controller. 
     38. The controller opens the specified file, and downloads the entire file from the controller (RAM) disk to the terminal active on the LAN channel. 
     39. The controller sends a &#34;directive status&#34; record to the host to indicate that the file was downloaded successfully. 
     40. The controller sends the next data request record, for the channel, to the host. 
     41. The host responds by sending a download data record. 
     42. Steps 40 and 41 or steps 40, 37, 38 and 39 may be repeated any number of times, until the host sends an end-of-data record. 
     43. The host sends an end-of-data record for the channel. 
     44. The controller sends an end-of-session record, from the terminal active on the channel, to the host. 
     45. The controller sends another connection request to the host. 
     46. The host responds by sending an end-of- data record to the controller. 
     47. The controller randomly establishes a session with another terminal on the LAN. 
     48. A communications session proceeds on the channel as in steps 34 through 44. 
     49. The controller determines that no terminals are available on the remote auto-dial port (port 3), deactivates the port and sends an activation request record, for the port, to the host. The activation request contains a status field which indicates why the port was deactivated. 
     50. The host responds by sending an auto-answer activation record to the controller, which re-configures port 3 as an auto-answer, asynchronous port. The port is now capable of answering calls from single 4300/4400 terminals (not in a LAN) and existing TTY devices. 
     51. The controller receives an upload data record from a 4300/4400 terminal on port 2. 
     52. The controller transfers the data to a host channel and sends the data on to the host. 
     53. Steps 51 and 52 may be repeated any number of times until the 4300/4400 has finished uploading data. 
     54. The controller sends a download data request, for the 4300/4400 terminal, to the host. 
     55. The host responds by sending a data record. 
     56. Steps 55 and 56 may be repeated 0 or more times. 
     57. The host sends an end-of-data record for the 4300/4400 terminal. 
     58. The controller sends the end-of-session record from the terminal to the host. 
     * Once set, activation parameters remain in effect until they are specifically reset. Default activation parameters are contained in a configuration file on the controller&#39;s disk. 
     ** Enabling connection requests will probably be the exception, rather than the norm. If connection requests are not enabled, connection requests will not be generated and terminal sessions will be established in a way similar to that used in Norand&#39;s existing protocol converters (e.g. The controller will accept upload data from any terminal, and pass the data on to the host. The host will use information in the upload data to associate download data with the terminal) 
     Description of FIG. 31 FIG. 31 illustrates exemplary logic for component 600, FIG. 30A. Inputs PCS0 and PCS1 are identified at 601 and 602 in FIG. 31, and corresponding inputs are apparent in FIG. 30A, which emanate from bus 604. Input DCDRQ designated 606 in FIG. 31 will be seen to originate at the disk drive controller 573, FIG. 30A. Inputs 611, 612 and 613 of FIG. 31, designated DRQB, DBQC, DBQD, are apparent at the right of component 600, FIG. 30A. Output signal lines 615 and 616, FIG. 31, are shown to be connected to the microcomputer 500, FIG. 30A. Outputs 621 and 622, FIG. 31, are seen in FIGS. 30A and 30B to be associated with bus 624 and to lead to the respective serial communications controllers SCC1 and SCC2, FIG. 30B. Input 626, FIG. 31, is seen in FIGS. 30B and 30A to originate at serial controller SCC1. 
     Description of FIGS. 32A and 32B 
     FIGS. 32A and 32B show a preferred implementation of the auxiliary power unit (APU) shown at 421 in FIG. 28, and an earlier implementation being shown in FIG. 29. In accordance with the present invention, the auxiliary power unit of FIGS. 32A and 32B enables the expansion of the LAN system beyond the initial twenty-four docking units. The device provides power for an additional twenty-four hand-held computer terminals, so that the batteries may be recharged during the communication process. The APU circuitry of FIGS. 32A and 32B also provides for a bi-directional repeater for the RS-485 communication signals. A commercially available LAN configuration can be expanded to a maximum of seventy-two docking units utilizing one network controller 400, FIG. 28, twelve multi-dock systems such as illustrated in FIGS. 23-27 and two auxiliary power units as represented in FIGS. 32A, 32B. 
     The connector arrangement as shown at 450, FIG. 21, on the back panel of the network controller and corresponding connectors at the back of the APU unit 421, FIG. 28, simplify the configuration of systems and allow flexibility in routing of external interconnecting cables. 
     The APU circuitry of FIGS. 32A and 32B is unique because the repeater circuit is bi-directional and does not require an external signal to determine the direction of data (such as provided by direction control line 431, FIG. 29). An energy detection circuit comprised of components 32-U6A and 32-U6B, FIG. 32B, automatically determines which side of the repeater circuitry of FIG. 32A is receiving the data, and enables the repeater circuit for that direction. The enable control lines are indicated at 633, 634, FIGS. 32A, 32B. At that time, the repeater circuit for the opposite direction is disabled. Once data activity stops, both repeater circuits are disabled. The energy detect circuit of FIG. 32B then monitors both sides of the APU repeater circuit for data activity and reactivates one or the other of the two repeaters as required. 
     By way of example, the respective components of FIGS. 32A and 32B may be of the following types: 
     
         ______________________________________32-U6A, 32-U6B, FIG. 32B                 Multivibrator                 e.g. 74HC12332-U2, FIG. 32A       Bus Repeater                 e.g. Type 75178B32-U3, 32-U4, 32-U5, FIG. 32A                 Bus Repeater                 e.g. Type 75177B32-REG1, FIG. 32B     Regulator                 e.g. LM317T______________________________________ 
    
     Description of FIG. 33 
     FIG. 33 illustrates the circuitry for the RS232 interface components 560 for ports B, C and D of FIG. 30B. FIG. 33 specifically shows the interface for port D wherein the signal CLKSELD shown at input 650 at the left in FIG. 33 originates from a latch 651, FIG. 30A, and is transmitted via bus 652, FIGS. 30A and 30B. Component 654, FIG. 33, may be a driver/receiver, for example MAX 235. 
     Description of FIGS. 34A, 34B and 34C 
     In FIGS. 34B and 34C, the RS232 interface component for port A, FIG. 30B, is indicated at 660 and corresponds with the other interface components such as 654, FIG. 33. Thus, bus 652, FIGS. 30A and 30B, supplies the signal CLKSELA at input 662, FIG. 34A. Port select component 664, FIG. 30B, may be implemented as shown at 666 and 667 in FIG. 34A, these components being quad multiplexors, e.g. type 74HC157. The 485SEL signal for input 670, FIG. 34A, originates at latch 651, FIG. 30A, and is transmitted by bus 652. The RS485 interface component 570, FIG. 30B, may be implemented as indicated at 675, FIG. 34B, and component 675 may be a differential bus transceiver, e.g. type 96176. 
     Description of FIGS. 35A and 35B 
     FIGS. 35A and 35B illustrate an exemplary implementation of the power supply components 581 and 582, FIG. 30B. The input at line 680, FIG. 35A, may be between 13 volts DC and 20 volts DC and the output 681, FIG. 35A, may supply plus twelve volts to the disk drive component, while output 682 may supply plus five volts. 
     By way of example, component 690, FIG. 35B, may be a plus modulator, e.g. type UC494AC. 
     By way of example, the plus twelve volt output at 681 may be supplied by a regulator component 692, e.g. a voltage regulator type UA7812UC. 
     Description of FIGS. 36A, 36B and 36C 
     By way of example RAM controller 700, FIG. 30A, may be implemented as shown at 701, 702, FIG. 36B. Coupling of these components to address bus 710 is indicated in FIG. 36A. 
     FIG. 36C shows a regulator 36-REG1, e.g. type LM317LZ, which is coupled via line 712, FIGS. 36C, 36B, with a plus three volt regulator 36-REG2, e.q. type 581230. The input to components 701, 702 such as VBB1, VBB2 and plus five volts (+5V) have suitable banks of capacitors associated therewith and the same is true of other voltage inputs throughout the preferred embodiment of a network controller. The showing of these capacitor banks has been omitted since this is a matter of routine for those skilled in the art. 
     FIG. 36C also shows a RAM chip select signal at 714 (RAMCS). Other connections between FIGS. 36C and 36B are indicated at 716 and 718. 
     Description of Exemplary Microprocessor And Related Circuits (FIGS. 37A-36F) 
     In FIG. 37A, the address bus 710 on a complete sheet of engineering drawings would be shown as leading to the sixteen bit inputs (A1-A16) of two EPROM chips (each 64KX8, e.g. 27C512). Such circuitry for implementing component 800, FIG. 30A, is a matter of routine for one skilled in the art, and need not be further described. The data from the EPROM 800 (e.g. D0-D7) is supplied to bus 801 (e.g. as signals DB0-DB7 and AD8-AD15). 
     The RAM component 810, FIG. 30A, may be implemented as twenty-four CMOS SRAM chips, 32Kx8, e.g. PD43256C. Address bus 710 would supply inputs (e.g. A1-A15), while components 701, 702, FIG. 36B would provide respective select signals (e.g. RCE0, RCE23). A further description of an implementation of component 810 is unnecessary since such circuitry is well within the routine skill of the art. 
     In FIG. 37A, the control and data bus 820 is shown which is associated with outputs (AD8-AD15) of the EPROM chips implementing component 820. For convenience of compact illustration of the circuitry, this bus 820 is shown offset to the right in FIG. 37D. FIG. 37D also shows a bus part 820A offset to the right from the corresponding bus part 820A of FIG. 37. Otherwise, vertical lines of FIG. 37D are in alignment with the corresponding vertical lines (i.e. 831, 832) in FIG. 37A. 
     Horizontal lines 841-852 in FIGS. 37A and 37B are in horizontal alignment and have been numbered for convenience of correlation of these figures. 
     In an actual engineering drawing, a vertical bus segment 820B is shown by the same vertical lines. Thus segments 820C in FIGS. 37C and 37B are identical segments (rather than being connected between the figures). This same procedure has been followed with respect to bus segments 820D, 820E in FIGS. 37E and 37F. Thus, in an actual engineering drawing the lines of bus segment 820B, FIGS. 37B and 37C, would be in direct alignment with and would connect with the two lines of bus segment 820D, FIGS. 37E and 37F, and bus segment 820E of FIG. 37F would be superimposed on and part of bus segment 820E of FIG. 37E. Horizontal line 861 has been numbered in FIGS. 37B and 37C to assist in correlating these figures. Horizontal line 862 has been numbered in FIGS. 37A and 37E, and the horizontal bus segments 870 have been designated at the bottom of FIG. 37A and near the top of FIG. 37E. Bus segment 880 has been labeled as a vertical segment in FIG. 37B and as a horizontal segment in FIG. 37E, these segments being in alignment in the present patent drawings. Vertical bus segments 820G have been designated in FIGS. 37B and 37E since these segments are in vertical alignment in the patent drawings. Horizontal lines 881 through 886 have been designated in FIGS. 37E and 37F to assist in associating these figures. 
     Exemplary components for the circuitry of FIGS. 37A through 37F is as follows: 
     
         ______________________________________37-U42, FIG. 37A    Buffer,               e.g. 74HC24137-U28, FIG. 37A    D-Type Positive-               Edge-Triggered               Flip-Flop37-U5, FIG. 37B     Microprocessor,               e.g. Type 80C18637-U6, 37-U7, 37-U8, FIG. 37C               Octal Latch,               e.g. 75HC57337-U30              JK Flip-Flip,               e.g. Type 74HC11237-U38, FIG. 37E    CMOS Clock,               e.g. Type MC146818P37-U26              Programmable Logic               &#34;LANPAL&#34;               (Type PALC22V10H)37-U32, 37-U27      Bus Transceiver,               e.g. 74HC245______________________________________ 
    
     Description of FIGS. 38A-38E 
     In order to assist in correlation of FIGS. 30A, 30B with the exemplary implementation of FIGS. 38A-38E, the communications bus has been designated 624 in the detailed implementation. 
     FIG. 38A shows components 901 and 902 for implementing serial communications controller chips SCC1 and SCC2. The address bus has been designated 710 in FIGS. 30A, 30B and FIGS. 38A, 38B and 38E. Data bus 607, FIGS. 38A and 30B, has been designated with the same reference numeral in FIGS. 38A, 38B and 38E. 
     The vertical line between FIGS. 38A and 38C has been designated 905, and the horizontal lines between FIGS. 38C and 38D have been designated 911-920. The horizontal lines between FIGS. 38D and 38E have been designated 921-928. 
     Component 930, FIG. 38B, may represent an implementation of the keyboard interface 572, FIG. 30A. Component 940, FIG. 38E, may represent a detailed circuit for disk drive controller 573. 
     Exemplary type numbers for the major components in FIGS. 38A, 38B and 38E are as follows: 
     
         ______________________________________Components 901, 902, FIG. 38A                Serial Communica-                tions Controller,                e.g. Type 85C3038-U24, FIG. 38B     Octal Latch,                e.g. Type 74HC573930, FIG. 38B        CMOS Keyboard                Encoder,                e.g. Type 74C923940, FIG. 38E        Controller,                e.g. Type 82072______________________________________ 
    
     Summary Re: FIGS. 31-38E 
     With the foregoing description, and the detailed circuitry shown in FIGS. 31 through 38E, a preferred embodiment of the circuitry for implementing FIGS. 28 and 30A, 30B, will readily be understood by those skilled in the art. Of prime importance is the preferred implementation for the auxiliary power unit 421 as described with reference to FIGS. 32A and 32B. 
     It will be apparent that many modifications and variations may be effected without departing from the scope of the novel teachings and concepts of the present invention.