Method of accessing configured nodes in a facilities management system with a non-configured device

• US 5,444,851 A
• Filed: 01/21/1994
• Issued: 08/22/1995
• Est. Priority Date: 01/30/1990
• Status: Expired due to Term

• Current Assignee: Johnson Controls Technology Company (Johnson Controls International plc)
• Original Assignee: Johnson Service Company
• Inventors: Woest, Karen L.
• Primary Examiner(s): Harrell, Robert B.
• Application Number:
  US08/185,674
• Time in Patent Office: 578 Days
• Field of Search: 364/DIG. 1 MS File, 364/DIG. 2 MS File, 395/200, 395/250, 395/275, 395/325, 395/375, 395/600, 395/650, 395/700, 395/800, 370/94.1, 370/85.1, 370/85.7, 370/95.1, 370/60, 370/60.1, 379/59, 379/219, 379/220, 379/221, 455/33, 340/825.5, 340/825.1, 340/825.52, 340/825.03, 340/825.04, 340/825.36, 340/825.411
• US Class Current: 709/222
• CPC Class Codes: G06F 11/22 Detection or location of defective computer hardware by testing during standby operation or during idle time, e.g. start-up testing
• CPC Class Codes: G06F 9/465 Distributed object oriented systems remote method invocation [RMI] G06F9/548
• CPC Class Codes: G06F 9/54 Interprogram communication
• CPC Class Codes: Y10S 707/99945 Object-oriented database structure processing
• CPC Class Codes: Y10S 707/99954 Version management

Abstract

A networked system having a wide variety of applications and particularly applicable to facilities management systems has multiple levels of software in processing nodes. The levels include a "features" processing level which communicates requests for data to a software object level containing databases of processes and attributes and database managers. The database managers in the software object level operate to provide data to the high level features in the same format. The software object level communicates with a hardware object level which also contains databases and database managers to mask differences between operational hardware units. By categorizing operational units by type, additional units of a known type can be added with only low level hardware object database changes. Adding units of a new type is facilitated by software changes confined to the lower level hardware and software objects, avoiding software changes at high level features. Individual software objects are tailored for typical types of inputs and output devices encountered by facilities management systems. Universal drive circuitry also provides applicability to a broad range of devices. A non-configured node is connected to a configured network at a location defined by a subnet and a local address. The location information and a drop identifier are used as a network address for the non-configured node to transmit and receive messages. Routing information stored in the configured nodes allows non-configured node to communicate with other network nodes.

Claims

1. A method of accessing network controllers in a facilities management system with a portable computing unit, the network controllers in the facilities management system being arranged to control a process, the network controllers being configured as at least one network and being interconnected by at least one communication link, each of the network controllers including an equipment interface for receiving data related to the process, and a processor including a drop port, the processor being coupled to the equipment interface, the facilities management system being initialized so that the network controllers are configured to each have a network address indicative of a particular location in the facilities management system, the network address including a subset indicative of an associated communication link to which the network controller is connected, a local address indicative of the network controller, and a node drop ID indicating that the network controller is a configured network controller, the portable computing unit being a non-configured device not part of the network, the method comprising:

connecting the portable computing unit to a first port of a first network controller of the network controllers, the first configured network controller configured on the system at a first location defined by the subset indicative of the communication link and a first local address indicative of the first network controller;

assigning a first network address to the portable computing unit, the first network address including the subset, the first local address and a first drop identifier indicative of the first drop port of the first network controller;

transmitting a request for data received at an equipment interface of a second network controller located at a second network address from the portable computing unit to the second network controller, the request including the second network address as a destination indicator and the first network address as a source indicator;

transmitting the data from the second network controller to the portable computing unit in response to the request for data, the data including the second network address as the source indicator and the first network address as the destination indicator;

receiving the data from the second network controller at the processor of the first network controller according to the subset and local address of the first network address;

transmitting the data to the portable computing unit through the first drop port specified by the first drop identifier portion of the first network address.

2. The method of claim 1 wherein each network controller further includes a network layer, and a data link layer, the facilities management system including intermediate network controllers located between the first network controller and the second network controller, the method further comprising:

transmitting the request for data to the intermediate controllers along a path between the first network controller and the second network controller, the intermediate network controllers receiving the request at the data link layer and decoding the destination address in the network layer, the intermediate network controllers retransmitting the request at the data link layer along the path to a next intermediate controller until the second network controller is reached.

3. The method of claim 2 further comprising:

retrieving the data from the equipment interface of the second network controller in response to the request for data.

4. The method of claim 3 further comprising:

transmitting the data to the intermediate controllers along the path between the first network controller and the second network controller, the intermediate network controllers receiving the request at the data link layer, decoding the destination address in the network layer, the intermediate network controllers retransmitting the request from the data link layer along the path to the next intermediate controller until the first network controller is reached.

5. The method of claim 4 further comprising:

routing the data between the portable computing unit and the second network controller along routes for message traffic between the first network controller and the second network controller in accordance with a routing table stored in the network controllers.

6. The method of claim 5 further comprising:

storing at each network controller a routing table when the facilities management system is initialized, the table having an entry for the destination address, the entry of the table defining the next address along the routes for message traffic.

7. The method of claim 6 further comprising:

storing portions of predetermined routes in sequences of the intermediate network controllers as a series of network addresses, each network address defining a next location along the path from the first network controller to the second network controller.

8. The method of claim 4 further comprising:

receiving the data at the data link layer of the first network controller, and providing the data to the network layer, transmitting the data from the network layer to the first drop port of the processor of the first network controller.

9. The method of claim 8 further comprising:

receiving the data with the portable computing unit at the first drop port.

10. The method of claim 4 further comprising:

storing a static routing table at each network controller, the static routing table having an entry for each destination address, the entries of the table defining the next address along the path from the first network controller to the second network controller.

11. The method of claim 4 further comprising:

storing the predetermined route portion in a table in a central processor in the facilities management system and accessing the table to define the route.

12. The method of claim 4 further comprising:

adaptively routing the request and data between the portable computing unit and the second network controller along the routes for message traffic between the first network controller and the second network controller determined by a dynamic routing strategy sensitive to message traffic throughout the facilities management system.

13. The method of claim 1 further comprising:

predetermining the routes when the facilities management system is initialized; and

storing portions of the predetermined routes in sequences of the network controllers as a series of network addresses, each network address defining a next location along a path from the first network controller to the second network controller.

14. The method of claim 13 further comprising:

storing a static routing table at each network controller, the static routing table having an entry for each destination address, the entries of the table defining the next address along paths from the first network controller to the second network controller.

15. The method of claim 13 further comprising:

storing the predetermined route portion in a table in a central processor and accessing the table to define the route.

16. The method of claim 1 further comprising:

routing the data between the portable computing unit and the second network controller along routes for message traffic between the first network controller and the second network controller.

17. The method of claim 16 further comprising:

storing at each network controller a routing table, the table having an entry for the destination address, the entry of the table defining the next address along the routes for message traffic.

18. The method of claim 16 further comprising:

adaptively routing messages between the portable computing unit and the second network controller along the routes for message traffic between the first network controller and the second network controller determined by a dynamic routing strategy sensitive to message traffic throughout the facilities management system.

19. The method of claim 1 wherein the portable computing unit is a lap top computer.

20. The method of claim 1 wherein the process is internal environmental control.