METHOD FOR CONFIGURING AN INTELLIGENT CONTROL SYSTEM FOR THE DISTRIBUTION OF ELECTRICITY

Abstract: The invention relates to a method for configuring an intelligent control system for the distribution of electricity. The system comprises a number of mutually communicating nodes (1), to which can be connected controlling and/or con trolled devices (1.1, 2). The nodes (1) contain a node software and a node configuration, the latter identifying functions controlled by the node software to match functions required by the devices (2) connected to each node (1). A configuration editor (8) is used to engineer a system configuration (9) by using preset functions as input data. On the basis of a preset order code, the system configuration (9) is searched to select node-specific configuration data, which is loaded in the memories of individual nodes (1) in the system. In the electrical distribution systems for vehicles, for example, the country- and model-specific configurations can be designed from a common function file and the completed configurations can be selected on the basis of an order code.

Description: Method for configuring an intelligent control system for the distribution of electricity The invention relates to a method for configuring an intelligent control system for the distribution of electricity, said system comprising a plurality of mutually communicating nodes, to which are connectable controlling and/or controlled devices and which nodes contain a node software and a node configuration, the latter identifying the functions controlled by the node software to match the functions required by the devices connected to each node. For example, the distributed control system for vehicular wiring comprises a multitude of control units or nodes, which are connected to devices to be controlled and which can be e.g. intelligent control units coupled directly with a cable by way of the connection pins thereof. There are different functions for each control unit. A problem with this type of system is how to design it to be readily configurable and maintainable, and also as attractive as possible in terms of costs. Attempts have been made to solve the problem e.g. by designing each control unit individually in terms of both hardware and software. The solution is awkward regarding its configuration and maintenance as the control units must be dealt with as different entities. This prior known solution requires further that, in order to secure a compatibility of versions, the sub-contractors of control units be provided with an access to special hardware supplied by an automobile manufacturer for establishing a communication with the automobile manufacturer's version management system. It is an object of the invention to provide a configuring method capable of overcoming the above problem in such a way that the building of configurations is supported by way of libraries, whereby, e.g. in vehicle production, the country- and model-specific configurations can be built from a once-designed configuration base or template automatically on the basis of an order code or, if modifications or additions are needed, those can be readily affixed to a predesigned configuration template. This object is achieved on the basis of the characterizing features set forth in the appended claim 1 or 5. The non-independent claims disclose preferred embodiments of the invention. The method of the invention is particularly useful in connection with a current distribution system of the type described in the Applicant's International Patent applications WO 99/25585 and WO 99/25586. These prior known systems contain a standard node software and a separately loadable node configuration capable of identifying the functions controlled by the node software. The invention will now be described in more detail with reference to the accompanying drawings, in which fig. 1 shows a block diagram relating to information flows in a control system of the invention for the distribution of electricity, and fig. 2 shows a performance diagram for a configuring method of the invention. Prior to describing a method of the invention in further detail, reference is made to conceptual definitions for explaining the invention. Operation is an entity, which consists of one or more functions. The inclusion of this entity is optional in the determination of a system configuration. Example operations: automobile turning signals, a windshield wiper, stop signal buttons in a bus. Function is an undivided logical entity, which attends to a single control feature. The function uses one or more input values, from which the node software calculates one or more output values by means of the function. The values can be obtained either from devices connected to a common node or across the grid from some other node. For example, the operation "bus blinkers" could be constituted by the following functions: right-hand front blinker, left-hand front blinker, right-hand rear blinker, left-hand rear blinker. Option refers to an optionality associated with an operation. The configurer is able to select a desirable one of the options associated with an operation. On the basis of selection options, the operation adopts a set of additional functions. The options can be entirely optional, or else just one must be selected from a number of alternatives. The operation "bus blinkers" could include the following options: side blinkers (optional), rear blinkers normal design/rear blinkers double design (either one must always be selected). Node is a physical hardware unit, which contains a node software and a node configuration and which has connected therewith a certain number of controlling and/or controlled devices. For example, the nodes used in the distribution systems of vehicles are intelligent control units provided with an input connection, an output connection, and a connection to the electric and data wires of a cable. Control system consists of an arbitrary number of mutually communicating nodes 1 , which have a common task of controlling a certain hardware configuration constituting a control system for power distribution configurable in accordance with the invention. Node software is a standard software, which is included in each node 1 and which, on the basis of a node configuration, is capable of adapting the features of a node to certain devices 2, 1.1 connected to the node. One or more of these devices can be connected to a node input connection 1.2 and/or output connection 2.2. Input and output indicate the direction for a data stream of the nodes. Instead of being used independently, these definitions appear in conjunction with the following concepts pin, connection, device, driver, value Pin is a physical pin in the node 1 and enables the node software to be supplied with data coming and going through the connections The connection may be a node input connection 1 2, or it may be a connection of the node 1 to a common data bus in a cable 3 Device is a controlled or controlling physical system entity, which can be linked via one or more connections 2 2, 1 2 to the node 1 One example of the device is a motor for the windshield wiper Connection transmits a single signal from the pin of the node 1 to a device 2, or from a device 1 1 , 2 to the pin of the node 1 Driver is a part of the node software, which is capable of writing a value for a pin or reading a value from a pin The node software uses the drivers according to driver parameters defined in driver descriptors Value is a logical data unit, which is used by the function in its calculation The input and output values are used for communicating with an extra-nodal system Configuring is a process, which results in a system configuration This process will be subsequently described in more detail with reference to fig 2 System configuration is an entity, which contains configuration data and dependencies thereof for all nodes in the system Node configuration contains configuration data for a single node, including functions to be performed in the node and values used thereby, as well as necessary driver descriptors On the basis of a node configuration, the node software is able to conclude which pins are in use and how to read and supply values therefrom and thereto, respectively Configuration file is a file, in which is stored the node configuration of a single node and which can be loaded in the flash memory of the node 1 Parameter is an attribute, which has an impact on the operation of the function or the driver The function parameters are determined during the process of determining the system configuration The function may calculate new values for the parameters while driving continues An example of the function parameter a number of strokes performed during the washing action of a windshield wiper An example of the driver parameter a supply current for the controlled device 2 Driver descriptor is a segment of the node configuration, which determines the way of using a certain driver in a certain context The driver descriptor contains default values for the parameters of a driver Function descriptor is a segment of the node configuration, which determines the behaviour of a single function Order code is a selector, which selects for each individual socket configuration from the system configuration a subset of functions allocated to said selector Socket configurations can be generated for an arbitrary number of order codes Fig 1 depicts a general diagram for the data streams of a node or socket 1 A required number of the sockets 1 are provided with an input device 1 1 , which is coupled by way of an input connection 1 2 of the socket with an input pin 1 3 of the socket The input value read by an input driver 1 4 from the pin 1 3 constitutes a calculation basis for a function 1 6 As a result of performing the function 1 6 included in an operation 2 1 , the function 1 6 has its output value 1 7 written by means of an output driver 1 8 onto an output pin 1 9 of the socket, from which the output value 1 7 proceeds by way of an output connection 2 2 to an output device 2, which adjusts its service on the basis of the output value 1 7 The configuration of drivers, values, and functions for the system configuration of an entire power distribution system is performed as follows. A driver editor 4 shown in fig. 2 is used for defining components contained in node software, which are capable of writing values, i.e. logical units used by a function in its calculation, to the output pins of nodes 1 or reading values from the input and output pins of nodes, for drivers in such a mode that such values can be summoned from the functions. The drivers are stored in a driver library 5, which is used as the input of a function editor 6. After the definition of drivers, an essential segment of the configuring process is to define operations 2.1 and functions 1.6 required by one or more distribution systems, each of said functions serving a single control feature of the controlling or controlled device 1.1 , 2. After defining the functions, the function editor 6 is used to engineer an information description for each function, which is stored in a function library 7. The information description of a single function 1.6 contains a description of the calculation performed by the function 1.6, information regarding input and output values 1.5, 1.7 used by the function, as well as information regarding optional controlling and controlled devices 1.1 , 2 capable of being used for reading and writing the input and output values 1.5, 1.7, and driver descriptors required by these devices 1.1 , 2. This is followed by using a configuration editor 8 to engineer a system configuration, which may be a system configuration for each individual control system or a system configuration common to a number of individual control systems. The system configuration contains configuration data for all nodes in a system (or systems), and inter-dependencies thereof. When engineering the system configuration, the information descriptions of functions present in the function library 7 are used as input information for the configuration editor 8. The configuration editor 8 is used for listing and selecting the operations 2.1 for a system and the options for operations, which jointly define functions 1.6 included in the system configuration, function parameters used by the functions 1.6, and controlling and controlled devices 1.1 , 2 operated by the functions 1.6, as well as for appropriating the input and output connections 1.2, 2.2 of the devices to the input and output pins 1.3, 1.9 of the nodes 1. There is further defined optional order codes 12 and selections influenced by each order code. The resulting system configuration is stored in a system configuration file 9. After performing the above process steps for one or more power distribution systems, said steps need not be repeated as similar systems are being configured. Instead, a translator 9 is used for compiling node-specific configuration data from the system configuration file 9 on the basis of a preset order code 12, said data being stored in a node configuration file 11 for loading therefrom the node-specific in the memories of the individual nodes 1 in the system. Naturally, the nodes must carry index numbers, such that the operations and devices defined as early as in an engineering stage II can be appropriated in a production stage III to certain nodes as required by the order code. As a system configuration has been created for the first time by means of the configuration editor 8, a check-up for its functionality is performed by means of a simulation 14, wherein it is possible to simulate e.g. vehicular functions in a variety of operating situations. If the simulation detects defects or flaws in the system configuration, the configuration editor 8 is used for corrective actions. As pointed out above, the attributes need only be determined once for each system configuration or a hybrid configuration of several system configurations. For example, with regard to the production of electrical distribution systems for buses, the configuring can be carried out by designing for each order an individual system configuration 9, which is given an order number. On the other hand, in view of electrical distribution systems for passenger cars, the orders are identified by means of order-code combinations in such a way that various order codes can be used for producing from a common system configuration 9 node configuration files 11 corresponding to various system configurations 9'. The invention provides the following benefits. - The method enables the use of standardized node software regardless of variations in node hardware and devices to be connected to each node. - The configuration method is an essential part of the production of a power distribution system. The production process of the entire system becomes simpler and more flexible. - The method provides distinct interfaces between various stages of a configuration process. - The method favours the construction of various configurations by way of libraries, such that a common template can be used for designing e.g. country- and model-specific configurations (e.g. 30 countries x 5 models = 150 configurations), the selection being made among these at the order stage on the basis of an order code. - The method is independent from type of vehicle (bus/passenger car/boat/etc. ). Naturally, power supply systems other than those associated with vehicles can be configured by making use of the inventive method. - The method makes it possible to organize the ordering and production process of an electrical distribution system optimally in terms of business, since the configuring process can be modularized in such a way that on top level said configuring process amounts to making operation choices on a "check the box" basis. - The method is independent regarding changes in node hardware, which only involve restricted parts of node software. - The method offers an effective support for producing order-specific documentation. - The method enables the configuring system to be integrated with a testing system capable of verifying both the analogy of the functions of completed configurations with what is desired (e.g. a car factory) and the validity of function libraries to be supplied to a car factory or the like. - The method favours fine-grained version management for verifying the compliance of function libraries 7 and configurations 9. - The method provides a solid support for the maintenance of configured control systems (addition of new equipment, configuration changes). - The method enables the verification of certain configurations at a work station by means of a separate simulation test system 14 prior to physically configuring the nodes 1.

Claims: Claims 1. A method for configuring an intelligent electrical distribution system, said system comprising a plurality of mutually communicating nodes (1 ), to which are connectable controlling and/or controlled devices (1.1 , 2) and which nodes (1 ) contain a node software and a node configuration, the latter identifying the functions controlled by the node software to match the functions required by the devices (1.1 , 2) connected to each node (1 ), characterized by - defining functions (1.6) required by one or more distribution systems, each of said functions attending to a single control feature of the controlling or controlled device (2); - engineering an information description for each function by means of a function editor (6); - storing the information descriptions for the functions in a function library (7); - engineering a system configuration for one or more distribution systems, which contains configuration data and inter-dependencies for all nodes (1 ) of the system or systems; - engineering a system configuration by means of a configuration editor (8), whose input data comprises the information descriptions for functions present in the function library (7) and which is used for listing and selecting the functions (1.6) and the devices (1.1 , 2) controlling the same and controlled thereby, as well as performing the appropriation of the devices' (1.1 , 2) connections to various nodes (1 ); - storing the system configuration in a system configuration file (9); - selecting from the system configuration file, on the basis of a preset order code (12), node-specific configuration data which is stored in a node configuration file (11 ); and - loading the node-specific configuration data from the node configuration file in the memories of single nodes (1 ) in the system. 2. A method as set forth in claim 1 , characterized by - using a driver editor (4) to produce drivers, whereby the information descriptions for the functions can be used for controlling components of the node software, which are capable of writing values, i.e. the logical units used by a function in its calculation, to output pins of the nodes (1 ) or reading values from input or output pins of the nodes (1 ); - storing the drivers in a driver library (5); and - using the drivers of the driver library (5) as an input for the function editor (6). 3. A method as set forth in claim 1 or 2, characterized in that the method is used to configure a control system for electrical distribution, wherein the nodes (1 ) are intelligent control units connected by their protruding contact pins directly to the wires of a cable (3) for power supply and linking to a data bus. 4. A method as set forth in any of claims 1 -3, characterized in that the distribution system orders are singled out by means of order-code combinations in such a way that, with various order codes (12), a common system configuration (9) is capable of producing node configuration files (11 ) corresponding to various system configurations (9'). 5. A method for configuring an intelligent electrical distribution system, said system comprising a plurality of mutually communicating nodes (1 ), to which are connectable controlling and/or controlled devices (1.1 , 2) and which nodes (1 ) contain a node software and a node configuration, the latter identifying the functions controlled by the node software to match the functions required by the devices (1.1 , 2) connected to each node (1 ), characterized in that the system uses its various nodes to operate a standardized node software disregarding variations of node hardware and devices to be connected to each node, and that the node software units are configured to function individually by means of order-code combinations in such a way that various order codes are used to select from a common system configuration (9) node configuration files (11 ), which correspond to various system configurations and from which the node- specific configuration data is loaded in the memories of individual nodes in the system.

Inventors: LAMBERG LAURI, VISKARI JUHA, LAMBERG, LAURI, VISKARI, JUHA
Applicants: IWS INTERNAT OY, LAMBERG LAURI, VISKARI JUHA, IWS INTERNATIONAL OY, LAMBERG, LAURI, VISKARI, JUHA
Application year: 2000
Main classification: H02J
IPC codes: B60R16, B62D65, H02J1