Control system, control method, and program
The integration of safety and non-safety units through a shared bus with prioritized data relay addresses wiring complexity and terminal underutilization, enhancing flexibility and efficiency in factory automation control systems.
Patent Information
- Application Number
- PCT/JP2025/017431
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Filing Date
- 2025-05-13
- Publication Date
- 2026-11-19
AI Technical Summary
Existing control systems for factory automation require separate CPU and dedicated buses for safety and non-safety units, leading to increased wiring complexity, difficulty in connecting non-adjacent safety units, and underutilization of input/output terminals.
A control system that integrates safety and non-safety units via a shared bus, utilizing a bus control unit to relay data and prioritize safety functions, allowing flexible unit arrangement and utilization of all input/output terminals.
Facilitates easy coordination and efficient use of resources by ensuring reliable safety functions while reducing wiring complexity and enabling flexible unit placement and terminal utilization.
Smart Images

Figure JP2025017431_19112026_PF_FP_ABST
Abstract
Description
Control System, Control Method, and Program
[0001] The present disclosure relates to a control system, a control method, and a program.
[0002] In the field of FA (Factory Automation), it is widely practiced to control robot machines, machine tools, and the like by a control system configured by combining a plurality of PLCs (Programmable Logic Controllers). It is also common practice to provide control systems with safety functions such as stopping the operation of the system when the status of a controlled target system is monitored and a risk is detected. For example, Patent Document 1 discloses a method of constructing a control system by combining a safety unit and a non-safety unit. In this method, all units are connected via a CPU (Central Processing Unit) bus to make all units cooperate with each other, and further, the safety units are connected to each other via a dedicated bus, whereby the safety functions are reliably realized.
[0003] Japanese Unexamined Patent Application Publication No. 2007-193843
[0004] In the technique of Patent Document 1, a CPU bus and a dedicated bus for safety control are arranged. This requires two systems of signal wiring. Accordingly, there is a problem that the wiring space, the number of terminals of components, and the like increase, and control also becomes complicated.
[0005] Further, when the safety units are not adjacent to each other, it is physically difficult to connect the safety units with the dedicated bus.
[0006] In addition, I / O information is not passed from the CPU unit that executes the control program of the PLC to the safety unit. For this reason, the input / output terminals of the safety unit cannot be used as inputs and outputs for non-safety control. Therefore, when the number of input / output terminals possessed by the safety unit is excessive with respect to the required number of safety inputs and outputs, it is not possible to construct a system in which the surplus input / output terminals are utilized for non-safety control.
[0007] This disclosure has been made in view of the above-mentioned problems, and aims to provide a control system, control method, and program that can control a controlled object by easily linking a safety unit and a non-safety unit.
[0008] To achieve the above objective, the control system relating to this disclosure comprises a safety unit that performs safety function processing including the control of external safety devices, a non-safety unit including a CPU unit that controls the controlled device, a shared bus connecting the safety unit and the non-safety unit, and bus control means that relay data transmitted and received from the non-safety unit or the safety unit via the shared bus. The bus control means determines the content of the data and performs relay processing to relay the data.
[0009] According to this disclosure, the bus control means that relays data transmitted and received from a non-safety unit or a safety unit via a shared bus determines the content of the data and performs relay processing to relay the data. Therefore, safety units and non-safety units can be easily controlled in coordination.
[0010] Figures 1 and 2 show an example of the overall configuration of a safety control system having safety functions according to the embodiment. Figure (a) shows an example of the configuration of the bus control unit shown in Figure 1 and 2. Figure (b) shows an example of the priority table stored in the frame analysis unit shown in Figure 3. A flowchart of an example of the bus adjustment process performed by the frame analysis unit based on the priority table. Figures for explaining control via a safety leader and individual safety follower control according to the embodiment. Figures for explaining the operation of reading data from a safety leader unit to a safety follower unit according to the embodiment. A sequence diagram for explaining the operation of reading data from a safety leader unit to a safety follower unit according to the embodiment. Figures for explaining the operation of writing data from a safety leader unit to a safety follower unit according to the embodiment. Figure 2 shows a sequence diagram illustrating the operation of writing data from the leader unit to the safety follower unit. Figure 2 shows an example of separating the storage area of the storage unit into a storage area for safety system control data and a storage area for non-safety system control data. Figure 3 shows a modified example illustrating the operation of resetting by software control. Figure 4 shows a sequence diagram illustrating the operation of resetting by software control. Figure 5 shows a modified example illustrating the operation of resetting the safety follower unit from the safety leader unit by switch operation. Figure 6 shows a sequence diagram illustrating the operation of resetting the safety follower unit from the safety leader unit by switch operation. Figure 7 shows an example of the processing flow when an output control request that does not go through the safety leader unit occurs in the embodiment. Figure 8 shows an example of the processing flow when the safety unit detects an abnormality in the embodiment.
[0011] (Embodiments) The control system, control method, and program according to embodiments of the present disclosure will be described in detail with reference to the drawings. In the drawings, the same or corresponding parts are denoted by the same reference numerals.
[0012] The control system according to the embodiment of this disclosure is configured by combining a safety unit and a non-safety unit, and is characterized in that the safety unit and the non-safety unit share a single bus while being coordinated to ensure that safety functions are reliably realized. A safety unit refers to a unit that performs processing for ensuring safety (hereinafter referred to as safety processing), and a non-safety unit refers to a unit that performs processing other than safety processing. Ensuring safety means, for example, operating the controlled system only when safety has been confirmed, and stopping the controlled system when safety cannot be confirmed. For example, this is a function that forcibly stops the operation of the controlled system when a sensor detects a person entering a dangerous area, or when an emergency stop switch is pressed. Safety processing is an example of safety function processing according to this disclosure.
[0013] The control system according to this disclosure will be described below using the safety control system 100 shown in Figure 1 as an example. The safety control system 100 is a system that controls a system to be controlled (hereinafter referred to as the controlled system) in a safe state. The safety control system 100 comprises a plurality of safety devices 6, seven units, a shared bus 33 that connects the seven units to each other, and a bus control unit 34 that controls the shared bus 33. The seven units, the shared bus 33, and the bus control unit 34 correspond to an example of the control system according to this disclosure. Each unit and the bus control unit 34 are each composed of a PLC.
[0014] Safety equipment 6 includes input devices such as various sensors that detect the operating state and operating environment of controlled equipment such as robotic machines and machine tools, and output devices such as emergency stop switches or power switches that emergency stop the controlled equipment.
[0015] The seven units consist of four non-safety units and three safety units. The four non-safety units include a CPU unit 11 and non-safety units 21a, 21b, and 21c. The three safety units include a safety leader unit 31 and safety follower units 32a and 32b. The seven units 11, 21a, 21b, 21c, 31, 32a, and 32b work together to safely control the controlled system. The non-safety units 11 and 21 are examples of non-safety units including the CPU unit described herein. The safety units 31, 32a, and 32b are examples of safety units described herein.
[0016] Furthermore, when individual non-safety units 21a, 21b, and 21c are not distinguished, they may be collectively referred to as non-safety unit 21, and when safety follower units 32a and 32b are not distinguished, they may be collectively referred to as safety follower unit 32. Also, when safety leader unit 31 and safety follower unit 32 are not distinguished, they may simply be referred to as safety units 31 and 32. In addition, the CPU unit 11 and non-safety units 21a, 21b, and 21c may be collectively referred to as non-safety system units 11 and 21.
[0017] The CPU unit 11 is the central control unit and executes the PLC control program. The safety leader unit 31 and safety follower units 32a and 32b are connected to the safety device 6 in a communicative manner. The safety leader unit 31 and safety follower units 32a and 32b control the safety device 6 by executing control programs. The control programs are stored in the memory units of the safety leader unit 31, safety follower units 32a and 32b, etc.
[0018] Each of the seven units is composed of a PLC and, as shown in Figure 2, includes an MPU (Micro Processing Unit) 101 responsible for control functions, a storage unit 102 for storing data, and a bus IF (Interface) 103 responsible for connecting to the bus. The MPU 101 corresponds to the control and calculation unit and performs processing such as sending and receiving data and storing data. The storage unit 102 includes RAM (Random Access Memory), ROM (Read Only Memory), etc., and stores, for example, input / output data, operation programs, setting data, etc. The bus IF 103 is responsible for connecting to the shared bus 33. With the CPU unit 11 as the reference, the safety leader unit 31, safety follower unit 32, and non-safety unit 21 can be placed in any arrangement area. Therefore, as shown in Figure 1, it is also possible to construct a configuration in which the safety units 31 and 32 are not adjacent to each other.
[0019] In addition to the functions of each of the seven units described above, as shown in Figure 2, the CPU unit 11 is equipped with a tool interface 104 that plays a role in connecting to various tools. For example, by connecting the tool interface 104 to a personal computer, various information can be collected from the personal computer. Furthermore, setting values can be written to the safety reader unit 31 and the safety follower unit 32 via the CPU unit 11 from a support device including a personal computer.
[0020] Furthermore, one non-safety unit 21 has a communication IF 105 that, in addition to the MPU 101, storage unit 102, and bus IF 103, is responsible for connecting to various networks. The communication IF 105 is connected to the non-safety network. A non-safety network system can be constructed that includes non-safety equipment connected to this non-safety network. The remaining two non-safety units 21, the safety leader unit 31, and the two safety follower units 32 have an I / O circuit 106 that is responsible for connecting input / output devices. As shown in Figure 1, for example, the safety leader unit 31 and the two safety follower units 32 are connected to the safety equipment 6 via the I / O circuit 106.
[0021] The shared bus 33 corresponds to a system bus shared by safety control, including the control of external safety equipment 6, and non-safety control, including the control of external non-safety system equipment, and connects seven units. The CPU unit 11 can read data stored in, for example, the safety reader unit 31 and the safety follower unit 32 via the shared bus 33, and can also write data to them. Note that the data that the CPU unit 11 can write to the safety reader unit 31 and the safety follower unit 32 is limited to programs, setting values, and non-safety control data (hereinafter referred to as non-safety data). The CPU unit 11 cannot write safety control data (hereinafter referred to as safety data) to the safety reader unit 31 and the safety follower unit 32.
[0022] The bus control unit 34 is a type of computer that identifies the address, data type (safe or unsafe), etc., from the data received from each unit and processes the data according to a predetermined priority. The bus control unit 34 identifies the data by identifying the address, data type (safe or unsafe), etc., of the data received from each unit.
[0023] The bus control unit 34 determines the content of the data and performs relay processing to relay the data. As shown in Figure 3, the bus control unit 34 has a frame transmission / reception unit 35 that sends and receives frames containing information about the requested processing, and a frame analysis unit 36 that analyzes the information stored in the frames. The frame transmission / reception unit 35 receives frames transmitted from each unit and sends them to the frame analysis unit 36. The frame transmission / reception unit 35 also transmits the frames received from the frame analysis unit 36 to each unit corresponding to the destination.
[0024] The frame analysis unit 36 determines processing information such as the address indicating the destination of the frame received from the frame transmission / reception unit 35, the access type including a data read request, and the data type representing the type of data.
[0025] The frame analysis unit 36 stores a priority table illustrated in Figure 4(a). The priority table associates processes that use the shared bus 33 with the priority assigned to those processes. From a safety perspective, safety-related requests are given higher priority in the pre-set priority settings.
[0026] When the frame analysis unit 36 receives a request from the frame transmission / reception unit 35 to use the shared bus 33, it receives the request (step P1) as shown in Figure 4(b), determines whether the requests conflict (step P2), and if it determines that there is a conflict (step P2: Yes), it instructs the frame transmission / reception unit 35 to prioritize processing the request with the highest priority among the conflicting requests (step P3). In this case, processing of low-priority requests that are in progress may be interrupted. If it determines that there is no conflict (step P2: No), it instructs the frame transmission / reception unit 35 to process the received request (step P4). Through this processing, the CPU unit 11, non-safety unit 21, and safety units 31 and 32 can share the shared bus 33 while ensuring a high level of safety.
[0027] The formatting rules for frames, including request frames, output from each unit are shared among the units and the bus control unit 34.
[0028] A control IC such as a bus switch can be used as the bus control unit 34. The bus control unit 34 is an example of a bus control means according to this disclosure.
[0029] The safety device 6 can be controlled by the safety follower unit 32 in two ways: by responding to instructions from the safety leader unit 31, and by the safety follower 32 alone. These methods will be explained with reference to Figure 5.
[0030] The safety follower unit 32 controls the output to the safety device 6 in response to a request from the safety reader unit 31, as shown by the dashed line L1 in Figure 5. The safety follower unit 32 can also provide data to the safety reader unit 31 based on input from the safety device 6 connected to it, as shown by the dashed line L2. These controls are referred to as control via the safety reader.
[0031] Furthermore, as shown by the dashed line L3, the safety follower unit 32 can also control its own output without going through the safety reader unit 31, based on input from the safety device 6 connected to it. This control is called safety follower standalone control. Whether the safety follower unit 32 controls its own output based on a control signal from the safety reader unit 31 or performs safety follower standalone control is determined by the setting values stored in the memory units of the safety reader unit 31 and the safety follower unit 32.
[0032] Next, with reference to Figures 6 and 7, the control of the safety device 6 by the safety reader unit 31 via the safety follower unit 32 will be specifically explained. As an example, the operation in which the safety reader unit 31 reads data stored inside the safety follower unit 32 for the purpose of controlling the safety device 6 will be explained.
[0033] The safety reader unit 31 sends a data read request frame to the bus control unit 34 to read data from the safety follower unit 32 (S1). The request frame contains information such as the unit address of the safety reader unit 31, the access type, the unit address of the safety follower unit 32, the data address, and the data type. In this example, the access type corresponds to a "read request," and the data type corresponds to "safety data."
[0034] The request frame transmitted from the safety reader unit 31 is received by the frame transmission / reception unit 35 of the bus control unit 34 and sent to the frame analysis unit 36. The frame analysis unit 36 analyzes the received request frame and determines the destination unit address, data type, etc. (S2).
[0035] The frame analysis unit 36 sends an instruction to the frame transmission / reception unit 35 to send the request frame to the target security follower unit 32. The frame transmission / reception unit 35 transmits the request frame to the target security follower unit 32 (S3). Note that if there is a conflict with access to non-security data from other units, access to security data takes precedence. Access to security data corresponds to data access between security units, while access to other data, in other words, access via non-security units 11 and 21, corresponds to access to non-security data.
[0036] Upon receiving the request frame, the secure follower unit 32 reads data from its storage unit 102 according to the access type and the address of the data to be read specified in the frame (S4).
[0037] The safety follower unit 32 stores the read data in a response frame and transmits it to the bus control unit 34 (S5). In addition to the read data value, the response frame contains information such as the unit of the safety follower unit 32 itself, the unit address of the safety reader unit 31, and the data type.
[0038] The response frame transmitted from the safety follower unit 32 is received by the frame transmission / reception unit 35 of the bus control unit 34 and sent to the frame analysis unit 36. The frame analysis unit 36 analyzes the received response frame and determines the destination unit address, data type, etc. (S6).
[0039] The frame analysis unit 36 sends an instruction to the frame transmission / reception unit 35 to send a response frame to the safety reader unit 31 to be accessed. The frame transmission / reception unit 35 transmits the response frame to the safety reader unit 31 to be accessed (S7). Note that if the reading of safety data by the safety reader unit 31 conflicts with access to non-safety data by other non-safety units 11 and 12, the reading of safety data takes priority.
[0040] As a next example, an operation in which the safety leader unit 31 writes data for controlling the safety device 6 into the storage unit 102 of the safety follower unit 32 will be described with reference to FIGS. 8 and 9. The safety leader unit 31 transmits a data write request frame for requesting data writing to the safety follower unit 32 to the bus control unit 34 (S11). In addition to the write value, information such as the unit address of the safety leader unit 31, the access type, the address of the safety follower unit 32, the data address, and the data type is stored in the request frame. Note that the access type in this example corresponds to a "write request". The data type corresponds to "safety data".
[0041] The request frame transmitted from the safety leader unit 31 is received by the frame transmitting / receiving unit 35 of the bus control unit 34, and is sent to the frame analysis unit 36. The frame analysis unit 36 analyzes the received request frame, and determines the destination unit address, the data type, and the like (S12).
[0042] The frame analysis unit 36 sends an instruction to transmit the request frame to the access target safety follower unit 32 to the frame transmitting / receiving unit 35. The frame transmitting / receiving unit 35 transmits the request frame to the access target safety follower unit 32 (S13).
[0043] The safety follower unit 32 that has received the request frame writes the data into the storage unit 102 of the safety follower unit 32 itself according to the access type and the data address specified in the frame (S14).
[0044] The safety follower unit 32 transmits a response frame indicating that the data writing is completed to the bus control unit 34 (S15). Note that in addition to a write completion flag, information such as the unit address of the safety follower unit 32 itself, the unit address of the safety leader unit 31, and the data type is stored in the response frame.
[0045] The response frame transmitted from the safety follower unit 32 is received by the frame transmission / reception unit 35 of the bus control unit 34 and sent to the frame analysis unit 36. The frame analysis unit 36 analyzes the received response frame and determines the destination unit address, data type, etc. (S16). The destination unit address is an example of a destination address related to this disclosure.
[0046] The frame analysis unit 36 sends an instruction to the frame transmission / reception unit 35 to send a response frame to the safety reader unit 31 to be accessed. The frame transmission / reception unit 35 transmits the response frame to the safety reader unit 31 to be accessed (S17). Note that if the writing of safety data by the safety reader unit 31 conflicts with the access of non-safety data by other non-safety units 11 and 12, the writing of safety data takes priority. Furthermore, the CPU unit 11 acts as a reader and controls the non-safety systems when processing non-safety data by non-safety units 11 and 21. Specifically, the CPU unit 11 sends processing instructions to the bus control unit 34, similar to the safety reader unit 31 described above. The processing flow of non-safety systems via non-safety units 11 and 21 is the same as the processing flow of safety systems between safety units described above. When enabling such processing, it is necessary to ensure that the control data of non-safety systems does not affect the control data of safety systems. Therefore, as illustrated in Figure 10, it is effective to separate the storage area of the storage unit 102 of the safety leader unit 31 and the safety follower unit 32 into a storage area 1021 for safety-related control data and a storage area 1022 for non-safety-related control data. In this case, it is desirable to separate both the physical and logical addresses of both storage areas. This prevents the safety-related control data from being unintentionally overwritten. The safety-related control data is an example of control data used in safety function processing related to this disclosure. The non-safety-related control data is an example of control data used in function processing that is not safety function processing related to this disclosure.
[0047] As described above, in the safety control system 100 according to the embodiment, the bus control unit 34 relays non-safety-related data and safety-related data via the shared bus 33. Further, the bus control unit 34 determines the content of data transmitted from each unit, and processes data relay with priority given to safety processing. Therefore, the safety units 31, 32 and the non-safety unit 21 can be easily linked and controlled.
[0048] In the embodiment, the units of the safety control system 100 are configured with seven units, but the system may be configured with any number of units as long as there is one CPU unit 11, one non-safety unit 21, and one safety unit 31, 32 each. For example, the units of the safety control system 100 may be configured with six units, namely one CPU unit 11, two non-safety units 21, and three safety units 31, 32. These combinations are arbitrary.
[0049] Further, in the embodiment, as shown in FIG. 1, two non-safety units 21, a safety leader unit 31, a non-safety unit 21, and two safety follower units 32 are connected in sequence starting from the CPU unit 11, but the connection arrangement may be any arbitrary order.
[0050] Of the input / output terminals provided by the safety leader unit 31 and the safety follower unit 32, terminals not used as safety input / output can also be used as non-safety input / output that can be controlled by the CPU unit 11. Specifically, among the input / output terminals provided by the I / O circuit 106 of the safety leader unit 31 and the safety follower unit 32, terminals used for non-safety input / output can be made controllable by the CPU unit 11, for example, by setting parameters in the storage unit 102. For example, for each input / output terminal of the I / O circuit 106 of the safety follower unit 32, it is possible to set whether it is for safety input / output or non-safety input / output using control parameters set in the storage unit 102. In this case, it is desirable to prevent the contents of the safety system control data from being unintentionally overwritten by separating the storage areas for safety system control data and non-safety system control data within the storage unit 102 of the safety leader unit 31 and the safety follower unit 32, so that non-safety system control data does not inadvertently affect the safety system control.
[0051] When rewriting the settings of each unit, a process to reset the safety control system 100 may be performed. In this case, for example, all or part of the settings of each unit are stored in the auxiliary storage units of the CPU unit 11 and the safety reader unit 31. For example, when the safety control system 100 is started, the CPU unit 11 and the safety reader unit 31 store the settings stored in their auxiliary storage units in, for example, the storage unit 102 of each unit. This enables each unit to operate according to its settings. The settings can be written to the CPU unit 11 or the safety reader unit 31 using a support device including a personal computer. Alternatively, in order to reflect the rewriting of the settings in the operation of each unit, each unit may be returned to its initial state by a reset, and the updated settings may be loaded back into the storage unit 102 of each unit.
[0052] The operation of software-controlled reset of the CPU unit 11 will be explained with reference to Figures 11 and 12. The CPU unit 11 can reset any unit by sending a reset command, or in other words, a reset request frame, to the unit to be reset. The specific process is as follows: First, the CPU unit 11 sends a reset command, or in other words, a reset request frame, to the frame transmission / reception unit 35 of the bus control unit 34 (S21). The frame contains information indicating that it is a reset request, as well as the address of the unit to be reset. In Figure 11, the non-safe unit 21, safe leader unit 31, and safe follower unit 32 are the units to be reset. The frame analysis unit 36 of the bus control unit 34 analyzes the frame and determines the data type, the destination unit address, etc. (S22). The frame transmission / reception unit 35 of the bus control unit 34 sends the frame to the units 21, 31, and 32 to be reset (S23). When the MPU 101 of units 21, 31, and 32 receives a reset command, it initializes, for example, the main memory 102a in the storage unit 102, in other words, clears it to zero, and also returns the operation of the MPU 101 itself to its initial state (S24). Units 21, 31, and 32 that have been reset start processing from their startup operation (S25). According to this modified example, by specifying the unit address to be reset, the non-safe unit 21 and safe units 31 and 32 can be reset all at once. It is also possible to reset only safe units or only non-safe units by selecting the address of the unit to be reset. In this case, by allowing the operation of units that do not need to be reset to continue, the increase in the recovery time of the control system due to the reset can be suppressed.
[0053] Alternatively, the MPU 101 in the safety leader unit 31, upon receiving a reset request via switch operation, may issue a reset command to the follower unit on the safety control system 100, thereby enabling the unit to be reset. An example of resetting a unit via switch operation will be described with reference to Figures 13 and 14. The safety leader unit 31 is provided with a reset switch 45. The auxiliary storage unit 102b of the safety leader unit 31 stores in advance setting information indicating which unit to reset when the switch 45 is operated. In this example, the safety follower unit 32 is the target of the reset. The specific process is as follows: First, when the switch 45 is operated, a reset signal is input to the MPU 101 of the safety leader unit 31, and the safety leader unit 31 recognizes the reset request (S31). The MPU 101 of the safety leader unit 31 transmits a reset command, in other words, a request frame, to the frame transmission / reception unit 35 of the bus control unit 34 according to the setting information stored in the auxiliary storage unit 102b (S32). In addition to information indicating a reset request, the frame also stores the unit address of the unit to be reset. In this example, the unit address of the safety follower unit 32 is also stored in the frame. The frame analysis unit 36 of the bus control unit 34 analyzes the frame and determines the destination unit address (S33). The frame transmission / reception unit 35 of the bus control unit 34 transmits the frame to the safety follower unit 32, which is the unit to be reset (S34). The MPU 101 in the safety follower unit 32, upon receiving the reset command, initializes the main memory unit 102a, in other words, clears it to zero, and also returns the operation of the MPU 101 itself to its initial state (S35). The safety follower unit 32, which has been reset, starts processing from its startup operation (S36). According to this modified example, the increase in the recovery time of the control system due to the reset can be suppressed by allowing the operation of units that do not require a reset, such as the non-safety unit 21, to continue.
[0054] As explained with reference to Figure 5, the safety follower unit 32 may perform safety control without exchanging information with the safety leader unit 31 via the shared bus 33, that is, it may perform the safety follower-only control described above. In this case, even if an abnormality occurs in the shared bus 33, the safety function processing, including the control of the external safety device 6, will not be stopped; in other words, the output to the safety device 6 will not be turned off. If this setting (hereinafter referred to as output continuation setting) is possible, for example, when a request to perform safety follower-only control occurs, the MPU 101 determines whether or not an abnormality has occurred in the shared bus 33 (step P11), as shown in the flowchart of Figure 15. If an abnormality has occurred (step P11: Yes), it determines whether or not the output continuation setting has been made (step P12). If the output continuation setting has been made (step P12: Yes), the output to the external safety device 6 will be continued and the safety function processing will continue (step P13). If no abnormality has occurred (step P11: No), step P12 will be skipped and the process will proceed to step P13, and the safety function processing will continue. Furthermore, if the output continuation setting is not configured (Step P12: No), for example, the output to safety device 6 is stopped and the safety function processing is stopped (Step P14).
[0055] Furthermore, when a malfunction occurs in the safety unit and safety function processing stops, the non-safety units 11 and 21 can be configured to continue control operation (hereinafter referred to as "control continuation setting"). If this control continuation setting is possible, when a malfunction occurs in the safety units 31 and 32, for example, as shown in the flowchart of Figure 16, it is determined whether or not the control continuation setting is enabled (step P21). If the control continuation setting is enabled (step P21: Yes), the safety units 31 and 32 do not perform any special control on the non-safety units 11 and 21 (step P22). Therefore, the non-safety units 11 and 21 continue control. On the other hand, if the control continuation setting is not enabled (step P21: No), the safety units 31 and 32 request the non-safety units 11 and 21 to stop control (step P23). As a result, the non-safety units 11 and 21 stop control. The setting values for the output continuation setting and the control continuation setting are stored in the storage unit 102 of the CPU unit 11 or the safety reader unit 31. The relevant settings are pre-entered by the user, for example, using a support device including a personal computer, into the CPU unit 11 or the safety reader unit 31. This modified configuration allows for the design of a safety control system that eliminates the impact of abnormalities in the shared bus 33, thereby suppressing the frequency of safety function processing stoppages and the increase in recovery man-hours. If an abnormality in the shared bus 33 occurs due to a non-safety unit 21, the safety function processing does not need to be stopped. Furthermore, by allowing settings to continue the operation of the non-safety unit 21 when safety function processing stops, downtime for controls unrelated to safety control can be suppressed.
[0056] Various embodiments and modifications are possible without departing from the broad spirit and scope of this disclosure. Furthermore, the embodiments described above are for illustrative purposes only and do not limit the scope of this disclosure. In other words, the scope of this disclosure is indicated by the claims, not by the embodiments. Various modifications made within the scope of the claims and the equivalent significance of the disclosure are considered to be within the scope of this disclosure.
[0057] 6 Safety equipment, 11 CPU unit, 21, 21a, 21b, 21c Non-safety unit, 31 Safety leader unit, 32, 32a, 32b Safety follower unit, 33 Shared bus, 34 Bus control unit, 35 Frame transmission / reception unit, 36 Frame analysis unit, 45 Switch, 100 Safety control system, 101 MPU, 102 Memory unit, 102a Main memory unit, 102b Auxiliary memory unit, 103 Bus IF, 104 Tool IF, 105 Communication IF, 106 I / O circuit, 1021, 1022 Memory area.
Claims
1. A control system comprising: a safety unit that performs safety function processing including the control of external safety devices; a non-safety unit including a CPU unit that controls the controlled device; a shared bus connecting the safety unit and the non-safety unit; and bus control means that relays data transmitted and received from the non-safety unit or the safety unit via the shared bus, wherein the bus control means determines the content of the data and performs relay processing to relay the data.
2. The control system according to claim 1, wherein the safety unit and the non-safety unit each have a destination address for receiving the data, the relay process includes a process for transmitting the data to the destination address included in the data in a predetermined priority order, and the bus control means transmits the data subject to the safety function processing to the destination address with priority over the data not subject to the safety function processing.
3. The control system according to claim 1 or 2, wherein the number of safety units is multiple, one of which is a safety leader unit, and the remaining safety units are safety follower units, and the safety follower units control the output to safety devices connected to them in accordance with instructions from the safety leader unit, or control the output to safety devices connected to them independently of instructions from the safety leader unit.
4. The control system according to any one of claims 1 to 3, wherein, among the input and output terminals of the safety unit, terminals not used for the safety function processing are used for function processing other than the safety function processing that can be controlled by the CPU unit, the safety unit has a storage unit that stores control data used for the safety function processing and control data used for function processing other than the safety function processing, and the storage unit separates the storage area for control data used for the safety function processing and the storage area for control data used for function processing other than the safety function processing.
5. The control system according to any one of claims 1 to 4, wherein the data includes data representing the content of resetting at least one of the safety unit and the non-safety unit.
6. The control system according to claim 3, wherein the safety follower unit controls the output to the safety device without going through the safety leader unit, and furthermore, does not stop the control of the output if an abnormality occurs in the shared bus.
7. The control system according to claim 4, wherein the safety follower unit controls the output to the safety device without going through the safety leader unit, and if an abnormality occurs in the safety unit and the safety function processing between the safety units stops, the non-safety unit continues to operate the function processing that is not its own safety function processing.
8. A control method comprising connecting a safety unit that performs safety function processing including the control of external safety devices and a non-safety unit including a CPU unit, relaying data transmitted from the non-safety unit or the safety unit, determining the content of the data, and processing the relay of the data.
9. A program that connects a computer to a safety unit that performs safety function processing including the control of external safety devices, and a non-safety unit that includes a CPU unit, relays data transmitted from the non-safety unit or the safety unit, determines the content of the data, and processes the relay of the data.
