Vacuum system and method of operating the vacuum system

Abstract

To provide a more economical vacuum system with a first component and a second component, where these components each have a computer-executable software code for operating the vacuum system.SOLUTION: A vacuum system is configured to be selectively operated by a first component and / or a second component. The vacuum system is configured to be continuously operated at least partially by the second component in updating a software code of the first component.SELECTED DRAWING: Figure 1

Description

Technical Field

[0001] The present invention relates to a vacuum system and a method for operating the vacuum system.

Background Art

[0002] A vacuum system for generating, maintaining and / or measuring a vacuum includes an information processing unit that provides the functions of individual vacuum components and a data budget for the user together with corresponding actuators. Typically, a microcontroller (referred to as "embedded systems" in English) is used as the information processing unit, and a number of applications, i.e., software codes, are executed on the microcontroller. Depending on the structure, complexity and functions of the vacuum components, a number of different microcontrollers with their own software codes can exist, and these microcontrollers cooperate with the corresponding actuators and use them to provide the functions of the vacuum components.

[0003] The software code of the microcontroller is typically changed or updated multiple times during the lifetime of the vacuum system, for example, for improving the user process by error removal, improving performance, saving the working medium by optimal operation or expanding functions. For this purpose, the software of those microcontrollers is usually replaced by suitable means. Typically, for this purpose, the component has to be transferred to a state where it cannot execute the function of the component. For example, during the update, since the software code cannot be executed, the vacuum pump has to stop its operating mode or even shut down completely for the software update.

[0004] Therefore, in a conventional vacuum system, the update of software code causes an interruption of the user process, thereby resulting in an economic loss. Furthermore, the software update must be carried out at planned maintenance intervals, thereby reducing the flexibility of the system. In case of an emergency, an urgent software update may cause an unplanned interruption of the user process, thereby resulting in a temporary stop of the system.

Summary of the Invention

Problems to be Solved by the Invention

[0005] From the above, an object of the present invention is to provide a vacuum system characterized by higher economic efficiency.

Means for Solving the Problems

[0006] This problem is solved by the vacuum system according to claim 1.

[0007] The vacuum system according to the present invention includes a first component and a second component each having software code executable by a computer for operating the vacuum system. For this purpose, the present vacuum system is configured to be selectively operated by the first component and / or the second component. Furthermore, the present vacuum system is configured to be continuously operated at least partially by the second component when updating the software code of the first component.

[0008] Therefore, basically, especially during standard operation when no software update is being performed, the vacuum system can be operated using the first component and / or the second component. When performing an update of the software code of the first component, the present vacuum system can be switched to an update operation in which the present vacuum system is at least partially operated by the second component. Even if the first component fails to respond during the update of the software code of the first component and the operation of the vacuum system based on the first component is impossible or only partially possible, during the update of the software code of the first component, that is, nevertheless, the operation of the present vacuum system can continue to be executed by the second component. Thereby, an unplanned interruption of the operation of the present vacuum system and, accordingly, a possible loss of efficiency that may occur in some cases can be prevented. Therefore, a shutdown of the vacuum system for a longer period of time is prevented. Further, due to the redundancy of the components of the present vacuum system, the operation of the present vacuum system is always guaranteed, so a software update can be performed at any time. Further, due to the structure of the vacuum system according to the present invention, for example, the shutdown of the first component is compensated for by the second component, so the reliability against the shutdown of the present vacuum system in case of component failure is improved.

[0009] This vacuum system can be composed of any system that generates, maintains, or measures a vacuum using at least one vacuum component. In this case, the first and second components can be considered as any components related to the operation of the vacuum system or necessary for the vacuum system. Therefore, the first and second components can be composed of, for example, vacuum components such as vacuum pumps or vacuum gauges, components of vacuum components, such as a control board like a microcontroller, a memory medium, or the software code itself in the form of, for example, a software module. The first and second components are, in particular, functionally identical components, i.e., components that perform the same function. Therefore, this vacuum system is equipped with redundant components, thereby ensuring the continuous operation of the vacuum system. Basically, it is also possible that the second component is part of the first component or vice versa.

[0010] When updating the software code of the first component, this basically means that the first component is not available or only partially available for the operation of the vacuum system during the update. In this case, the second component takes over the operation of the vacuum system based on the software code of the second component. In particular, during the update of the software code of the first component, the software code of the first component is at least partially changed.

[0011] This update can be performed in a wired connection mode or a wireless connection mode, that is, the data associated with the update is transmitted to the vacuum system via a physical wiring or by a wireless connection such as, for example, Bluetooth, WLAN, Zigbee, or NFC. In order to confirm whether an update is necessary in the first place, before performing an update of the software code of the first component, the then-current state or the then-current version of the software code of the first component can be queried. Each update has, for example, a version number representing the version of the software code. In order to confirm whether an update is necessary or to prevent the software code of the first component from being reverted to a previous version, the then-current version number of the software code of the first component can be compared, for example, with an update version number. This update of the software code can be performed automatically when the corresponding update or update query becomes available. Alternatively, the update can be initiated or started manually by the user.

[0012] The improved configuration of the present invention can be read from the present specification, the dependent claims, and the drawings.

[0013] In a first implementation configuration, the present vacuum system continues to operate without being interrupted when updating the software code of the first component. In order to provide an uninterrupted operation of the present vacuum system, the present vacuum system can be pre-operated, for example, using a second component, starting from a predefined time before starting the update, particularly just shortly before. During the update, the operation of the present vacuum system is performed without depending on the first component. In particular, the present vacuum system can remain in a state where it can perform its functions without being restricted during the update, that is, the capabilities of the present vacuum system do not decrease during the update. In other words, ideally, the update process cannot be perceived by an external observer. Alternatively, the present vacuum system can also be made to perform its functions only partially during the update, for example, only execute some functions of the present vacuum system, such as basic functions.

[0014] In another implementation configuration, the software code of the second component at least partially matches the software code that existed before the update of the first component. Based on the matching part in the software code of this second component, the operation of this vacuum system can continue to be executed. In this case, "matching" does not mean that the software code of the second component is unconditionally identical to the software code of the first component. Rather, it means that the matching parts of the software codes of the first component and the second component can be associated with the same function of this vacuum system. Furthermore, the matching parts of the software code of the second component can be associated with the standard operation of this vacuum system. In other words, this vacuum system can be equipped with a first software component and a second similar software component, and when the first software component is updated, the second software component guarantees the operation of this vacuum system.

[0015] In another implementation configuration, the software code of the first component consists of multiple modules, and during the update, only one of the modules of the software code of the first component is updated. In this case, all single modules can be associated with a predetermined function of this vacuum system. During the update of one module, the remaining modules that are not updated can continue to operate this vacuum system in a restricted mode. In this case, the modules that continue to operate constitute a certain function, that is, the software code of the second component.

[0016] In another implementation configuration, the software code of the first component is stored in the first memory, and the software code of the second component is stored in the second memory. In particular, the first component includes the first memory, and the second component includes the second memory. For example, the software codes of the first and second components can be stored in a separate memory medium such as a USB stick, a memory card, a hard disk, a semiconductor memory, a flash memory, or a RAM memory. Advantageously, it is possible to access or call the second memory during the update of the software code stored in the first memory. Therefore, based on the software code stored in the second memory, the operation of this vacuum system can be continuously executed. The first and second memories can be further arranged on the same control board or, alternatively, on different control boards and / or different components of this vacuum system.

[0017] In another implementation configuration, before updating the software code of the first component, at least a part of this software code is saved to the second component. When updating the software code of the first component, based on this saved part of the software code, the second component continues to operate this vacuum system. This saved part of the software code, for example, guarantees the operation of this vacuum system, while the non-saved part of the software code of the first component, which is responsible for the communication function, for example, is updated and thus temporarily becomes unavailable. Further, the first component can include a flash memory, and the second component can include a RAM memory. Before updating the software code, at least part of the software code of the first component stored in the flash memory can be saved to the RAM memory.

[0018] In this implementation configuration, since additional memory is secured only when necessary, it is particularly advantageous that the available memory is utilized efficiently. For example, a memory space is secured to realize an additional software instance that guarantees the operation of this vacuum system only when the update is unprocessed. In other words, the software code of the second component is generated only when an update is imminent. After the execution of the update, the associated memory space can be freed again by deleting the saved part of the software code.

[0019] In another implementation configuration, if the update of the software code of the first component fails, the vacuum system is switched to a safe operating state, or the vacuum system is operated based on a previous version of the software code. This is particularly advantageous when the vacuum system is operated solely by the first component in standard operation. The failed update can be indicated, for example, by an error signal. This error signal can be generated by different operating devices. For example, when the vacuum system has been operating for a longer period than a predefined time duration based on a second component, an error signal can be generated. Exceeding the predefined time duration can, for example, mean that the update of the software code of the first component has failed. This predefined time duration can be determined, for example, based on the size of the software code to be updated or based on the type of component. In particular, this predefined time duration can be different for each update. When the failure of the update is confirmed, the vacuum system can be stopped, switched to a state with reduced functionality, an acoustic and / or visual error signal can be output, or a combination of the above actions can be performed. Alternatively, in such a case, the vacuum system can continue to operate based on a previous version of the software code. For example, the software code that has been successfully updated in the past can be stored in an independent backup memory, and when the software update fails, the operation of the vacuum system is based on the last successfully updated version of the software code. For this purpose, for example, the first component can be overwritten with the last executable version of the software code, while during this overwrite, the second component continues to execute the operation of the vacuum system.

[0020] In another implementation configuration, the first and second components of the present vacuum system are arranged to perform the same partial functions of the present vacuum system. In other words, for example, the same components are redundantly used to provide uninterrupted operation of the present vacuum system. This partial function is composed of one or more functions among functions such as vacuum generation, process control, drive, communication, and data storage. For example, the first and second components are composed of a vacuum pump, a drive device, a measuring instrument, or a microcontroller having the same function.

[0021] In another implementation configuration, this partial function is executed by the first component and / or the second component in the standard operation, that is, in a state where no update is performed, and is executed only by the second component when updating the software code of the first component. In this way, the present vacuum system can operate using two components in the standard operation. The present vacuum system can include, for example, two vacuum pumps that operate together in a form where their respective performances are reduced, and during the update of the software code of the first vacuum pump, only the other vacuum pump executes vacuum generation. In this case, during the software update, the second vacuum pump can be operated in a form where its performance is temporarily improved to compensate for the stop of the first component. Alternatively, the present vacuum system can be executed solely by the first vacuum pump in the standard operation and solely by the second component during the software update.

[0022] In another implementation configuration, the first component and the second component each include a hardware device having at least one computing module that executes computer-executable software code. For example, the first component and the second component can each include a vacuum component, a component of the vacuum component, such as a control board like a microcontroller, or any other suitable hardware device. Further, this computing module can include a control board such as a microcontroller.

[0023] In another implementation configuration, in a standard operation, the first component is connected to the present vacuum system. In contrast, to update the software code of the first component, the connection between the first component and the present vacuum system is disconnected, and a connection between the second component and the present vacuum system is established. Accordingly, the second component is selectively connected to the present vacuum system only when implementing an update of the software code of the first component. For example, the second component can be an alternative vacuum component having software code for operating the present vacuum system, an alternative component, an alternative microcontroller, an alternative memory such as a USB memory or an SD card memory, or any other suitable component.

[0024] To update the software code of the first component, for example, a update module, for example, connect the first component to a computer or connect with that module to update the software code of the first component. For example, the memory of the first component that stores the software code of the first component is overwritten with the software code for update. After the update process is completed, the connection between the present vacuum system and the first component can be newly established and the connection between the present vacuum system and the second component can be disconnected. In addition to this, after the update of the software code of the first component is successful, the software code of the second component can be updated correspondingly.

[0025] In another implementation configuration, this hardware device and / or computing module is configured as a plug-and-play module. For example, it can be assumed that this hardware device and / or computing module can be inserted into the present vacuum system or can be connected to the present vacuum system. This hardware device and / or computing module advantageously functions without the need for installation or setting. In particular, the present vacuum system has terminals for accommodating the plug or plug-in card of this hardware device and / or computing module, and the terminals of this vacuum system are configured to complement the plug or plug-in card of this hardware device and / or computing module. Therefore, incorrect connection of the hardware device can be eliminated. By configuring this hardware device and / or computing module as a plug-and-play module, each component can be easily connected to the present vacuum system, and the interruption of operations that may occur during the update can be shortened.

[0026] In another implementation configuration, after the software code of the first component is successfully updated, the present vacuum system is operated by the first component again, and the software code of the second component is updated. In other words, after the update is successful, the first component takes over the operation of the present vacuum system again. When the software code of the first component is updated next time, in order to ensure the operation of the present vacuum system based on the version of the software code at that time, especially when the software code of the second component is equal to the software code of the first component before the update of the first component, the software code of the second component is also updated correspondingly after the software code of the first component is successfully updated.

[0027] Alternatively, the software code of the second component can be preconfigured from the updated version of the software code. For example, before the software code of the first component is updated, the software code of the second component can be pre-updated. As a result, when the software code of the first component is updated, the present vacuum system is operated by the second component consisting of the already updated version of the software code.

[0028] In another implementation configuration, before and / or after updating the software code of the first component, the software code of the first component is stored in the backup memory as a backup version. Therefore, the latest executable software code version is stored in the backup memory, and when the software code update fails, the version of the executable software code for operating this vacuum system becomes available. Further, multiple versions of the software code can be stored in the backup memory. For example, for testing purposes, it may be useful to retrieve an old version of the software code. In addition to this, a time stamp can be attached to the version of the software code stored in the backup memory to facilitate arranging the software code versions in time order.

[0029] In another implementation configuration, the first microcontroller of the vacuum component of this vacuum system has software code for at least one other microcontroller of the same vacuum component. In addition to this, or alternatively, the first microcontroller of the first vacuum component of this vacuum system has software code for the microcontroller of at least one other vacuum component of this vacuum system. By this method, the update of each different microcontroller can be executed by the first microcontroller, and thus can be executed without communicating with the outside, especially at a suitable time. For example, the update of another microcontroller by the first microcontroller can be executed when this vacuum system is just in the inactive mode.

[0030] Another aspect of the present invention relates to a method of operating a vacuum system, in which the vacuum system is selectively actuated by a first component and / or a second component each having computer-executable software code for operating the vacuum system, and the vacuum system is at least partially continuously actuated by the second component when updating the software code of the first component. It is clear that the aforementioned advantages of the vacuum system according to the present invention are equally effective with respect to this method.

[0031] Hereinafter, the present invention will be described by way of example only with reference to the accompanying drawings based on possible embodiments.

Brief Description of the Drawings

[0032]

Figure 1

Figure 2

Figure 3

Figure 4

Figure 5

Figure 6

Embodiments for Carrying Out the Invention

[0033] Figure 1 illustrates a vacuum system 2 comprising a first component and a second component. In this case, the first component is a first vacuum pump 4 and the second component is a second vacuum pump 6. Basically, the first and second components can also be composed of other components of the vacuum system, such as a vacuum gauge, drive equipment, a control board, and / or software code. The first vacuum pump 4 and the second vacuum pump 6 are each connected to a central control unit 8 that adjusts the operation of these vacuum pumps 4, 6. These vacuum pumps 4, 6 each comprise a control board (not shown) and a drive motor (not shown) that is controlled by this control board respectively. For that purpose, these control boards comprise a memory in which the software code of each vacuum pump 4, 6 is stored and a processor that executes that software code. In the standard operation of this vacuum system 2, these vacuum pumps 4, 6 are operated simultaneously, specifically, each is operated at 50% of its maximum performance.

[0034] When updating the software code of the first vacuum pump 4, the central control unit 8 transmits an update signal to the first and second vacuum pumps 4, 6. In response to receiving the update signal from the central control unit 8, the first vacuum pump 4 switches to a standby mode in which the first vacuum pump 4 is stopped until this vacuum pump becomes inactive, and waits for the start of the update of the software code of the first vacuum pump 4. In contrast, in response to receiving the update signal, the second vacuum pump 6 improves its activity level and operates the vacuum system 2 at 100% of its maximum performance. Thus, the second vacuum pump 6 compensates for the inactivity of the first vacuum pump 4. Here, the update of the software code of the first vacuum pump 4 can be started. For example, the entire software code of the first vacuum pump 4 or only a part of the software code of the first vacuum pump 4 is updated.

[0035] When the update process is completed, the first vacuum pump 4, or more precisely, the control board of the first vacuum pump 4, sends a confirmation signal indicating that the update has been successfully completed to the central control unit 8. When the central control unit 8 receives the confirmation signal from the first vacuum pump 4, the central control unit 8 transmits the corresponding confirmation signal to the second vacuum pump 6. In addition to this, or alternatively, the first vacuum pump 4 can directly send the confirmation signal to the second vacuum pump 6. In response to the reception of the confirmation signal by the second vacuum pump 6, the vacuum system 2 reverts to the standard operation. For this purpose, the first vacuum pump 4 improves its operating state again until it starts operating at 50% of its maximum performance. In parallel with this, the second vacuum pump 6 reduces its operating state from 100% of its maximum performance to 50% of its maximum performance.

[0036] After the software code of the first vacuum pump 4 has been successfully updated, the software code of the second vacuum pump 6 can also be updated. For this purpose, after the software code of the first vacuum pump 4 has been successfully updated, the first vacuum pump 4 operates the vacuum system 2 at 100% of its maximum performance, while the second vacuum pump 6 switches to the inactive mode in which the software code of the second vacuum pump 6 can be updated. After the software code of the second vacuum pump 6 has been successfully updated, the first and second vacuum pumps 4, 6 can revert to the standard operation in which the first and second vacuum pumps 4, 6 operate at 50% of their maximum performance respectively.

[0037] If the software code update of the first vacuum pump 4 and / or the second vacuum pump 6 fails, or if this update continues for a longer time than a predefined time period, an error signal is sent to the central control unit 8 and / or the other vacuum pump respectively. In response to this error signal, the vacuum system 2 is shifted to a safe operating state, or continues to operate based only on the other vacuum pump respectively. In addition to this, or instead of this, it is also possible to operate the vacuum pumps 4, 6 to be updated based on the software code that has been successfully implemented most recently by overwriting the software code of the corresponding vacuum pump with the software code that has been successfully implemented most recently. For example, after the software code update has been successful, the version of the corresponding software code is stored in the backup memory, and in such a case, access to this backup memory can be made. Then, after the update has failed, the software code to be updated is overwritten using the version of the software code in the backup memory.

[0038] Figure 2 illustrates a vacuum system 2 equipped with a first vacuum pump 4 and a second vacuum pump 6. In this case, in the standard operation, only the first vacuum pump 4 is connected to the central control unit 8. When updating the software code of the first vacuum pump 4, the connection between the first vacuum pump 4 and the central control unit 8 is disconnected, and the second vacuum pump 6 is connected to the central control unit 8 so that the second vacuum pump 6 can take over the function of the first vacuum pump 4 during the software update. When the software code update of the first vacuum pump 4 is completed, the first vacuum pump 4 is connected to the central control unit 8 again, and the second vacuum pump 6 is disconnected from the central control unit 8. Subsequently, the software code of the second vacuum pump 6 can also be updated. It is obvious that it is basically possible to first update the software code of the second vacuum pump 6 and then gradually update the software code of the first vacuum pump 4.

[0039] FIG. 3 illustrates a vacuum system 2 equipped with an actuator 10 connected to an insertion housing 12 into which control boards 14, 16 can be inserted, for example, a drive device. In FIG. 3, a first control board 14 is inserted into the insertion housing 12 and controls the actuator 10. When updating the software code executable on the first control board 14, the first control board 14 is pulled out of the insertion housing 12, and a second control board 16 is inserted into the insertion housing 12 and replaces it. While the first control board 14, or more precisely, the software code of the first control board 14 is being updated, the second control board 16 controls the actuator 10. When the update of the first control board 14 is completed, the second control board 16 is pulled out, and the first control board 14 is inserted into the insertion housing 12 again. As a result, the first control board 14 controls the actuator 10 again. Subsequently, the software code of the second control board 16 can be updated. However, it is also possible to pre-update the software code of the second control board 16 before the first control board 14. In that case, it is obvious that the second control board 16 can be left inserted into the insertion housing 12 after the update of the first control board 14.

[0040] FIG. 4 illustrates a vacuum system 2 equipped with an actuator 10. This actuator, unlike in FIG. 3, is continuously connected to a first control board 14 and a second control board 16. The vacuum system 2 in FIG. 4 can be operated using either the first control board 14 or the second control board 16. As a result, in order to update the software of one of the control boards 14, 16, it is only necessary to switch to the other control board 16, 14 respectively. Specifically, it is not necessary to interrupt the operation of this vacuum system 2 for that purpose.

[0041] FIG. 5 illustrates a vacuum system 2 having an actuator 10 also connected to a control board 17. This control board 17 has a memory 18 in which software code executable by a computer is stored. Further, this memory 18 has a flash memory 20 and a RAM memory 22. In the standard operation of this vacuum system 2, the software code executable by this computer is stored in the flash memory 20. When updating the software code, the software code is saved to the RAM memory 22. In particular, the portion of the software code that is unconditionally required for the standard operation of this vacuum system 2 is saved to the RAM memory 22. Therefore, during the update, while the software code in the flash memory 20 can be updated, the operation of this vacuum system 2 continues to be executed using the software code saved to the RAM memory 22. If the update of the software code in the flash memory 20 is successfully completed, the portion of the software code saved to the RAM memory 22 is erased, and as a result, the memory space occupied corresponding to it in the RAM memory 22 is released.

[0042] FIG. 6 diagrammatically illustrates in generalized form a flowchart regarding the update of the software of this vacuum system 2. In step 24, this vacuum system 2 is operating in a standard operation, that is, in a state where the update process is not in progress, using the first and / or second components, for example, the first and / or second vacuum pumps 4, 6 or the first and / or second control boards 14, 16.

[0043] In step 26, for example, an upcoming update of the software of the first component is presented by an update signal. In response to this update signal, the first and second components transition to a state where they can start updating the software of the first component. For example, the first component transitions to an inactive state where it no longer contributes to the operation of the vacuum system 2, while the second component transitions to an active state and takes over the operation of the vacuum system 2 alone.

[0044] In step 28, while the software of the first component is updated, the present vacuum system 2 operates using the second component.

[0045] In step 30, it is inspected whether the update of the software of the first component has been successful. In addition to this, it is possible to inspect whether the update process has continued for a longer time than a predefined time duration, and if this is confirmed affirmatively, the update is regarded as having failed. If one or more of the update being successful and not exceeding the predefined time duration are confirmed, the first component takes over the operation of the present vacuum system 2, and the software of the second component is updated correspondingly (step 32).

[0046] On the other hand, if this inspection indicates that the update of the software of the first component has not been successful, the present vacuum system 2 is switched to a safe operating state or continues to operate using the second component (step 34).

[0047] In step 36, furthermore, it is inspected whether the update of the software of the second component has been successful. If the update of the software of the second component has been successful, the present vacuum system 2 is switched back to the standard operation (see step 38). Instead of this, if it is confirmed that the update of the software of the second component has failed, the present vacuum system 2 is switched to a safe operating state or continues to operate using the first component (step 40). Although this application relates to the invention described in the claims, it includes the following as other aspects. 1. A vacuum system (2) comprising a first component and a second component, each of these components having computer-executable software code for operating this vacuum system (2), this vacuum system (2) being configured to be selectively operated by the first component and / or the second component, this vacuum system (2) being configured to be continuously operated at least partially by the second component when updating the software code of the first component, Vacuum system. 2. In the vacuum system (2) of 1 above, This vacuum system (2) is a vacuum system that continues to operate without interruption when updating the software code of the first component. 3. In the vacuum system (2) of 1 or 2 above, The software code of the second component described above at least partially matches the software code existing before the update of the first component. Vacuum system. 4. In any one of the vacuum systems (2) from 1 to 3 above, The software code of the first component described above is composed of a plurality of modules, and when updating, only one of these modules of the software code of the first component is updated. Vacuum system. 5. In any one of the vacuum systems (2) from 1 to 4 above, The software code of the first component described above is stored in a first memory, and the software code of the second component described above is stored in a second memory. Vacuum system. 6. In any one of the vacuum systems (2) from 1 to 5 above, Before the software code of the first component described above is updated, this software code is at least partially backed up to the second component, and during the update, the second component continues to operate the vacuum system (2) based on the backed-up part of this software code. Vacuum system. 7. In any one of the vacuum systems (2) from 1 to 6 above, A vacuum system (2) that can be switched to a safe operating state or operated based on a previous software code version if the update of the software code of the first component fails. 8. In any one of the vacuum systems (2) from 1 to 7 above, A vacuum system in which the first and second components of the vacuum system (2) are provided to perform the same partial functions of the vacuum system (2). 9. In the vacuum system (2) of 8 above, A vacuum system in which the partial function is executed by the first component and / or the second component in a standard operation and is executed only by the second component when updating the software code of the first component. 10. In any one of the vacuum systems (2) from 1 to 9 above, A vacuum system in which the first component and the second component each include a hardware device having at least one computing module that executes computer-executable software code. 11. In the vacuum system (2) of 10 above, In a standard operation, only the first component is connected to the vacuum system (2). To update the software code of the first component, the connection between the first component and the vacuum system (2) is disconnected and the connection between the second component and the vacuum system (2) is established. 12. In the vacuum system (2) of 10 or 11 above, A vacuum system in which the hardware device and / or the computing module is configured as a plug-and-play module. 13. In any one of the vacuum systems (2) from 1 to 12 above, After the software code of the first component is successfully updated, the vacuum system (2) is operated by the first component again and the software code of the second component is updated. 14. In any one of the vacuum systems (2) from 1 to 13 above, Before and / or after the update of the software code of the first component, the software code of the first component is stored in a backup memory as a backup version. 15. A method for operating a vacuum system (2), This vacuum system (2) is selectively actuated by a first component and / or a second component each having computer-executable software code for operating this vacuum system (2), and this vacuum system (2) is continuously actuated at least in part by the second component when updating the software code of the first component, Method.

Description of Symbols

[0048] 2 Vacuum system 4 First vacuum pump 6 Second vacuum pump 8 Central control unit 10 Actuator 12 Insertion housing 14 First control board 16 Second control board 17 Control board 18 Memory 20 Flash memory 22 RAM memory 24 - 40 Steps of the method

Claims

1. A vacuum system (2) comprising a first component and a second component, wherein these components each have computer-executable software code for operating this vacuum system (2), this vacuum system (2) is configured to be selectively operated by the first component and / or the second component, this vacuum system (2) is configured to be continuously operated at least in part by the second component when updating the software code of the first component, before updating the software code of the first component, this software code is at least in part backed up to the second component, and during the update, the second component continuously operates the vacuum system (2) based on the backed-up part of this software code, A vacuum system.

2. The vacuum system (2) according to Claim 1, wherein this vacuum system (2) is a vacuum system that operates continuously without interruption when updating the software code of the first component.

3. The vacuum system (2) according to Claim 1 or 2, wherein the software code of the second component at least partly matches the software code existing before the update of the first component.

4. The vacuum system (2) according to Claim 1 or 2, wherein the software code of the first component is composed of a plurality of modules, and during the update, only one of these modules of the software code of the first component is updated.

5. The vacuum system (2) according to Claim 1 or 2, wherein the software code of the first component is stored in a first memory, and the software code of the second component is stored in a second memory.

6. The vacuum system (2) according to Claim 1 or 2, wherein when the update of the software code of the first component fails, this vacuum system (2) is switched to a safe operating state or operates based on the previous software code version.

7. The vacuum system (2) according to Claim 1 or 2, A vacuum system in which a first and a second component of the vacuum system (2) are provided to perform the same sub - functions of the vacuum system (2).

8. In the vacuum system (2) according to claim 7, a vacuum system in which the sub - functions are performed by the first component and / or the second component in a standard operation and are performed only by the second component when updating the software code of the first component.

9. In the vacuum system (2) according to claim 1, a vacuum system in which the first component and the second component each comprise a hardware device having at least one computing module that executes computer - executable software code.

10. In the vacuum system (2) according to claim 9, in a standard operation, only the first component is connected to the vacuum system (2), and for updating the software code of the first component, the connection between the first component and the vacuum system (2) is disconnected and the connection between the second component and the vacuum system (2) is established.

11. In the vacuum system (2) according to claim 9 or 10, a vacuum system in which the hardware device and / or the computing module is configured as a plug - and - play module.

12. In the vacuum system (2) according to claim 1 or 2, after the software code of the first component is successfully updated, the vacuum system (2) is operated again by the first component, and the software code of the second component is updated.

13. In the vacuum system (2) according to claim 1 or 2, before and / or after the update of the software code of the first component, the software code of the first component is stored in a backup memory as a backup version.

14. A method of operating a vacuum system (2), wherein the vacuum system (2) is selectively operated by a first component and / or a second component each having computer - executable software code for operating the vacuum system (2). This vacuum system (2) is at least partially continuously operated by a second component when updating the software code of the first component, before updating the software code of the first component, the software code is at least partially stored in a second component, and during the update, the second component continuously operates the vacuum system (2) based on the stored part of the software code, Method.

Images