Automation system and method of controlling automation system

FIELD: physics, control.

SUBSTANCE: invention relates to an automation system with an automation control means, a peripheral block and a system bus, as well as a method of controlling such an automation system. The automation system (1) includes a first automation control means (3.1) and a backup second automation control means (3.2). The automation system (1) also includes a peripheral block and a system bus (4) which connects both automation control means (3.1, 3.2) and the peripheral block. The peripheral block is connected to the system bus (4) through a corresponding bus connection module (5.1, 5.2, 5.3). The bus connection module (5.1, 5.2, 5.3) comprises a first bus controller (7.1) which is associated with the first automation control means (3.1), a second bus controller (7.2) which is associated with the second automation control means (3.2) and a switching unit (9) for switching between both bus controllers (7.1, 7.2).

EFFECT: high reliability of the automation system.

10 cl, 2 dwg

The invention relates to an automation system with a management tool automation, at least one peripheral unit and the bus system, and method of controlling such an automation system.

Known automation systems of this type are often based on the so-called communication master-slave between management tool automation and managed peripheral blocks. This management tool automation assumes the role of master, and the peripheral blocks of the role of the slave. Leading communicates via a bus system with a slave, while the slave does not communicate among themselves or have it only in a restricted way. Automation systems, which have to meet high requirements of readiness of equipment, such as automation of rail vehicles must provide the ability to perceive failures or lack of readiness for automation control or compensate for them.

The basis of the invention lies task is to offer an automation system with improved reliability. In addition, the basis of the invention lies task is to propose a method for secure management of the automation system.

The task is solved in accordance with the invention regarding the automation system is a sign of the mi, paragraph 1 of the claims, and about the way - signs of paragraph 4 of the claims.

Preferred embodiments of the invention are subject of the dependent claims.

Corresponding to the invention, the automation system has a first control automation and backup the second management tool automation. In addition, it has at least one peripheral unit and a system bus that connects both controls automation and at least one peripheral unit. At least one peripheral unit connected to the bus system via the corresponding module connected to the bus. Module connected to the bus includes a first bus controller, which is associated with the first management tool automation, and through a system bus connected to it, the second bus controller, which is associated with the second management tool automation, and through a system bus connected to it, and a switch unit for switching between the two bus controllers.

Due to the fact that the automation system has two identical controls automation, failure or unavailability of one of the management tools automation compensated by the second management tool automation. This is the preferred way increases the reliability of the system auto is Itachi.

Due to the fact that the modules connected to the bus of the peripheral blocks are, respectively, two bus controller, which are respectively associated with a different from both controls automation and connected with it, when changing controls automation Manager automation system, the host running the management tool automation can very quickly completely through its associated bus controller to access peripheral blocks, because the connection with these bus controller already exists and should only be installed. Due to this, the switching time when changing controls automation is reduced, which is particularly preferred, if the automation system high demands on reliability with short switching times.

The reduction in switching time is achieved with this preferred manner at low cost hardware and without the additional cost of software, as only the number of bus controllers increases, while all other components are connected to the bus, and peripheral blocks remain unchanged.

In the preferred implementation of the system bus is a Fieldbus system.

Thus the automation system to implement Southsea known preferred system properties Fieldbus. In particular, costs are reduced wiring cost, high reliability and availability due to short signal paths and simple extensions and modifications of the automation system.

The preferred first bus controller module connected to the bus directly connected to the system bus and the second bus controller is connected to the first bus controller and through this connection indirectly connected to the system bus.

Thus it must be connected to the Fieldbus system only one of the two bus controller module connected to the bus, so that a connection module connected to the bus to the bus system in relation to one module connected to the bus with only one bus controller must not change. Due to this, the cost of hardware for the second bus controller is the preferred way be reduced and the implementation corresponding to the invention of the automation system is simplified.

In accordance with the invention method for controlling corresponding to the invention of the automation system, depending on the situation selects one of the two tools of management automation management automation system. In addition, this module connect to the bus at least one peripheral unit for access to the peripheral unit you who Iraida the bus controller, which is associated with a management tool automation, selected for control by the automation system.

Due to the dependent situation of selecting one of the management tools automation for system management automation management can be coordinated with conditioned by the situation demands. In particular, the automation system failure or unavailability of funds management automation can respectively be controlled by other management tools automation, through which, as described above, the preferred way increases the reliability of the automation system.

The choice of the controller associated with the corresponding managing management tool automation, access controls automation to a peripheral unit enables the above-mentioned preferred reduction of switching times when managing change management tools automation.

In one implementation of the method of the automation system is controlled by the first control means automation, if it is available to control and ready for operation, and by the second management tool automation, if the first management tool automation is not ready for operation or defects in the PNA.

Due to this simple and effective method available and ready to use management tool automation is selected for reliable operation management automation system.

The preferred way availability and operational readiness of each of the management tools automation is continuously monitored.

Due to this, can reliably and timely detection of the failure or unavailability of controls automation and, if necessary, the system management automation is transmitted respectively to another management tool automation.

The implementation of the method requires that both controls automation mutually controlled on the availability and readiness for operation.

Thus the availability and operational readiness management tools automation is controlled by means of control, automation, so does not require any additional controls.

In addition, the bus controller module connected to the bus at least one peripheral unit, the preferred way through the system bus are reported each shift controls automation, selected for control by the automation system.

Thus, the bus controller immediately listed on the exchange Manager controls automation, so access to peripheral blocks can switch to the bus controller, which is associated with a management tool automation, which took over the control.

Alternative or additionally, the bus controller module connected to the bus at least one peripheral unit preferably cyclically, with predetermined time intervals on the bus system are reported, which both controls automation is currently selected for control by the automation system.

It also allows the bus controller to recognize the change control management tools automation and respond to it. If circular, the notice of the controller in addition to the notification at each change control management tools automation, may, in addition, the preferred way to compensate for transmission errors, for example, loss of messages about the occurred change control management tools automation.

Another preferred alternative or additional implementation of the method provides that when changing bus controller, accessing at least one peripheral unit, the receiving access to the bus controller from transmitting the access bus controller reported the current system state is less than the least one peripheral unit.

In the event of a change control management tools automation and the associated switching associated with this management tool automation bus controller, the bus controller, which assumes access to the peripheral block, sending him access to the bus controller can be transmitted vital information that is necessary for error-free access to the peripheral unit. Thus the host access to the bus controller is not required first to determine this information, due to which the switching time is additionally preferred way is reduced. Such information represents, for example, information about inserting and removing modules on the peripheral unit or units and the write operations that were undertaken peripheral unit on the transmitting access the bus controller, such as port configuration or logging diagnostic information.

Additional characteristics and details of the invention are further described in the examples with reference to the drawings showing the following:

Fig. 1 is a block diagram of an automation system with two controls automation and three United with them through the system bus modules connected to the bus of the peripheral blocks and

Fig. 2 is a block diagram of the module connected to the bus with two controllers ø what are the peripheral unit and one module connected to the bus.

Match parts in all drawings provided with the same reference position.

In Fig. 1 schematically shows a block diagram of the automation system 1 with two tools 3.1, 3.2 automation management and three United with them through the system bus 4 modules 5.1, 5.2, 5.3 connection to the bus detail is not presented peripheral blocks.

The automation system 1 may, for example, to provide a system for door control rail vehicle. Possible peripheral unit can in this example be represented, for example, the vehicle door control automatic control automatic closing and opening the doors of rail vehicles. The invention, however, does not depend on the specific objectives of the system 1 automation and peripheral blocks.

Tools 3.1, 3.2 management automation is implemented as the same type of processors for controlling peripheral units through the corresponding operating system or at least one application program.

System 4 tires performed as Fieldbus system, for example, as so-called Profibus (high-speed digital bus technology equipment).

Tools 3.1, 3.2 management automation using the corresponding switching unit 6.1, 6.2 attached to the system is ins 4.

Each module 5.1, 5.2, 5.3 connection to the bus contains two identical controller 7.1, 7.2 bus to control data exchange via the bus system 4. The first controller 7.1 bus associated with the first tool 3.1 management automation and constantly connected with it via a system bus 4. Accordingly, the second controller 7.2 bus associated with the second tool 3.2 management automation and constantly connected with it via a system bus 4.

This is shown in Fig. 1 example, the first module 5.1 connection to the bus and the second module 5.2 connection to the bus via their respective first controller 7.1 bus directly connected to the system bus 4, while the third module 5.3 connection to the bus only indirectly via the first module 5.1 connection to the bus to which it is connected via an additional connection 8 data connected to the system bus 4. The invention allows embodiments of respectively extended or modified network connections modules 5.1, 5.2, 5.3 connection to the bus. In addition, in alternative examples of implementation the controllers 7.1, 7.2 bus one or more of the modules 5.1, 5.2, 5.3 connection to the bus can also be connected in series to the system bus 4.

Both switching unit 6.1, 6.2 are, respectively, the third controller 7.3 bus to control the population of its communication system 4 tires, and both tools 3.1, 3.2 management automation are, respectively, the fourth controller 7.4 bus.

This sets the redundancy (redundancy) management, which is that both tools 3.1, 3.2 management automation at the same time establishes a data connection to peripheral units installed and maintained. Due to the existence of these data connections, perform reserve funds 3.1, 3.2 management automation, by switching between these tools 3.1, 3.2 management automation can be provided sufficiently fast switching time; if the data connection must be set only when switching, the requirements to short switching times, for example, in the second range, is not performed.

Due to the two controllers 7.1, 7.2 bus in each module 5.1, 5.2, 5.3 connection to the bus, it becomes possible that each tool 3.1, 3.2 management automation supports exactly one connection to peripheral units, each of the first and second controller 7.1, 7.2 tires exactly is associated with one tool 3.1, 3.2 management automation. The funds 3.1, 3.2 automation management see separate instances of the corresponding peripheral unit, presents both USB circuits is Rami 7.1, 7.2 bus. Each module 5.1, 5.2, 5.3 connection to the bus and each peripheral unit as a hardware device, however, the preferred way there only once, so that duplication of hardware is limited only by the controllers 7.1, 7.2 bus.

Fig. 2 shows in more detail the first module 5.1 connection to the bus in the form of a flowchart. Other modules 5.2, 5.3 connection to the bus is made in the same way.

The first module 5.1 connection to the bus contains the first controller 7.1 bus, the second controller 7.2 tires, block 9 of the switch and the memory block 11. Both controllers 7.1, 7.2 bus are controlled respectively by the software 13 of the controller. The memory block 11 is controlled by a driver 15 memory.

The first controller 7.1 bus directly connected to the system 4 tires, while the second controller 7.2 bus is connected to the first controller 7.1 bus and through this connection indirectly connected to the system bus 4.

Each software 13 bus controller controls to your controller, 7.1, 7.2 tyres own stack memory and own a gateway through which the corresponding controller 7.1, 7.2 tires constantly communicates with an associated tool 3.1, 3.2 management automation.

Due to the described in more detail below management accessible is the key and the connection between the two controllers 7.1, 7.2 bus first module 5.1 connection to the bus is reported which of the two tools 3.1, 3.2 management automation is currently executing process, i.e. what tool 3.1, 3.2 automation management currently manages the automation system 1. In accordance with this information through the block 9, the switching unit 11 to the memory and, thereby, also connected to the first module 5.1 connection to the bus of the peripheral unit associated with one of the two controllers 7.1, 7.2 bus. Through the connection between the two controllers 7.1, 7.2 bus is the exchange of information required in the case of switching between the two controllers 7.1, 7.2 bus.

Through the above-described control reserve is governed by which of the two tools 3.1, 3.2 automation management currently manages the process. For this control, reserve from the prior art already known various methods, which, due to their popularity, are mentioned only briefly, but not explained in detail and can be used an alternative and/or together:

Division on the main and secondary system: when the first tool 3.1 management automation is available and ready for use, it takes control of the process; only when the failure or unavailability of the second tool 3.2 management automation takes n the management of the process.

- Continuous mutual control of both tools 3.1, 3.2 management automation: both tools 3.1, 3.2 automation management continuously monitored mutually in the current mode to be able to recognize the failure is not managing at the moment tools 3.1, 3.2 management automation.

- Current control and deciding what tool 3.1, 3.2 management automation performs a process is carried out at the level of the application program funds 3.1, 3.2 management automation and in the case where the functionality of the control and decision-making does not depend on the respective application,

- Current control and deciding what tool 3.1, 3.2 automation management manages the process is carried out at the operating system level tools 3.1, 3.2 management automation through process of the operating system.

- Constant synchronization of the two tools 3.1, 3.2 automation management: application management at both facilities 3.1, 3.2 management automation always display the current operational status of the automation system 1.

- Sync when switching: the host on the management tool 3.1, 3.2 automation management recognizes at the time of adoption of the management is not fully current operational status of the system 1 auto is Itachi and determines its after switching, that is, after it took control system 1 of automation.

- Information modules 5.1, 5.2, 5.3 connection to the bus of the current control process tool 3.1, 3.2 automation management: modules 5.1, 5.2, 5.3 connection to the bus cyclically with predetermined time intervals and/or when changing the control means 3.1, 3.2 management automation bus system is reported which of the two tools 3.1, 3.2 automation management currently manages the automation system 1; both controller 7.1, 7.2 tires separately receive this information, while still necessary alignment between them.

Those controllers 7.1,7.2 tyres, which are not currently connected to a peripheral unit, deliver its payload with a guide of useful data. The data can be issued with a valid or invalid escort useful data. Following the reception of the access to the peripheral unit by the controller 7.1, 7.2 bus is signaled to the control means 3.1, 3.2 management automation through alarm or cyclic data in the message header data; only after that, the control means 3.1, 3.2 automation management has access to useful data of the respective peripheral unit.

The controller 7.1, 7.2 bus modules 5.1, 5.2, 5.3 of connectable is on the bus which at the moment does not get access to the corresponding peripheral unit, generates useful data, respectively, another controller 7.1, 7.2 bus this module 5.1, 5.2, 5.3 connection to the bus; that is, these useful data are transmitted through communication between the two controllers 7.1, 7.2 bus.

Hereinafter more particularly described, as may be implemented by communication through the system 4 tires, which is made, for example, as Fieldbus (Profibus), through a network Protocol, for example, Profinet Protocol.

For each tool 3.1, 3.2 automation management set the domain on the same physical network, e.g. an Ethernet network. Each module 5.1, 5.2, 5.3 connection to the bus reports in its commissioning tools 3.1, 3.2 automation management appropriate network address for each of your controllers 7.1, 7.2 bus. Each of these network address assigned to the own name of the device, in the case of the above-mentioned control doors for rail vehicles, for example, Dwerr, Dwerr, etc. for the corresponding first controller 7.1 tyres and 1_S, 2_S, etc. for the corresponding second controller 7.2 bus. Both tools 3.1, 3.2 management automation are designed with separate projects, each tool 3.1, 3.2 management automation individually programmare the Xia, if the software design for the system bus 4 does not support the use of two tools 3.1, 3.2 management automation and two controllers 7.1, 7.2 bus in each module 5.1, 5.2, 5.3 connection to the bus. All participants tires, such as, for example, Dwerr, Dwerr etc. then associated with the first tool 3.1 automation management, all members of the tires, for example 1_S, 2_S, etc. associated with the second tool 3.1 management automation.

1. The system (1) automation, containing the first tool (3.1) automation management and backup the second tool (3.2) automation management, and at least one peripheral unit and the system bus (4), which connects both tools (3.1, 3.2) automation management and at least one peripheral unit, and at least one peripheral unit connected to the bus system (4) via the corresponding module (5.1, 5.2, 5.3) connect to the bus and the module (5.1, 5.2, 5.3) connect to the bus contains the first controller (7.1) bus, which is associated with the first means (3.1) control through automation and system bus (4) is connected with him, the second controller (7.2) bus, which is associated with the second means (3.2) control through automation and system bus (4) is connected with him, and the block (9) switch to switch between the two controllers (7.1, 7.) tires.

2. The system (1) automation according to claim 1, characterized in that the bus system (4) is a Fieldbus system.

3. The system (1) automation according to claim 1, characterized in that the first controller (7.1) bus module (5.1, 5.2, 5.3) connections to the bus are directly connected to the system bus (4), and the second controller (7.2) bus connected to the first controller (7.1) bus and through this connection indirectly connected to the system bus (4).

4. The method of controlling the system (1) automation according to any one of the preceding paragraphs, and depending on the situation, selects one of the two tools (3.1, 3.2) control automation for the control system (1) automation, and in the module (5.1, 5.2, 5.3) connect to the bus at least one peripheral unit to access peripheral unit is selected by the controller (7.1, 7.2) bus, which is associated with means (3.1, 3.2) automation management selected to control the system (1) automation.

5. The method according to claim 4, characterized in that the system (1) automation is controlled by a first means (3.1) automation management, if it is available to control and ready for operation, and by means of the second means (3.2) automation management, if the first tool (3.1) automation management is not ready for operation or is unavailable.

6. The method according to claim 4 or 5, characterized by the eat, the availability and operational readiness of each of the tools (3.1, 3.2) automation management is continuously monitored.

7. The method according to claim 6, characterized in that both tools (3.1, 3.2) control automation mutually controlled on the availability and readiness for operation.

8. The method according to .4, characterized in that the controller (7.1, 7.2) bus module (5.1, 5.2, 5.3) connect to the bus at least one peripheral unit via the bus system (4) are reported each shift funds (3.1, 3.2) automation management selected to control the system (1) automation.

9. The method according to claim 4, characterized in that the controller (7.1, 7.2) bus module (5.1, 5.2, 5.3) connect to the bus at least one peripheral unit cyclically, with predetermined time intervals on the bus system (4) is reported, which means (3.1, 3.2) automation management is currently selected to control the system (1) automation.

10. The method according to claim 4, characterized in that the change of the controller (7.1, 7.2) bus, accessing at least one peripheral unit, the receiving access controller (7.1, 7.2) bus from the transmitting access controller (7.1, 7.2) bus reported the current system state of at least one peripheral unit.