Marine electric propulsion systems, master-slave control methods, equipment, and storage media
By distributing independent propulsion subsystems on the ship and adopting a master-slave competition mechanism, the problem of single point of failure in centralized control architecture is solved, and high fault tolerance and flexible multi-thruster cooperative control are achieved.
Patent Information
- Application Number
- CN202611117155.2
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2026-07-24
- Publication Date
- 2026-11-17
AI Technical Summary
Existing ship propulsion control systems are susceptible to failures in the industrial control computer or communication interruptions in centralized control architectures, making it difficult to guarantee the overall system's safety and fault tolerance.
The system adopts a distributed control architecture, which involves distributing multiple independent propulsion subsystems on the hull. Each subsystem is equipped with an independent energy storage device, local controller, electric thruster and remote control component. The master control node is dynamically selected using a master-slave competition mechanism to achieve unified parsing and distribution of control commands. The independent power output control of each slave unit is achieved through a communication bus.
It fundamentally eliminates the risk of single point of failure, improves the system's fault tolerance, and at the same time takes into account the convenience of multi-thruster coordinated operation and the flexibility of mode switching, while reducing control loop delay.
Smart Images

Figure CN123104899A_ABST
Abstract
Description
Technical Field
[0001] This application relates to the field of computer technology, and in particular to a marine electric propulsion system, a master-slave control method, an apparatus, and a storage medium. Background Technology
[0002] With the development of ship electric propulsion technology, ship power systems equipped with multiple propulsion units are gradually being applied to various special-purpose vessels and civilian ships. Currently, ship propulsion control systems generally adopt a centralized control architecture, where the system's industrial control computer receives control commands from the bridge, performs centralized parsing and processing, and then distributes the drive commands to each propulsion unit.
[0003] For ship propulsion platforms with multiple propulsion units, the system's industrial control computer can easily become a single point of failure. Once the industrial control computer fails or communication is interrupted, the entire propulsion system will stop working, and the system's safety and fault tolerance will be difficult to guarantee. Summary of the Invention
[0004] This application provides a marine electric propulsion system, a master-slave control method, an apparatus, and a storage medium to eliminate single-point-of-failure risks and improve system fault tolerance.
[0005] This application provides a marine electric propulsion system, including at least two independent propulsion subsystems. Each propulsion subsystem is distributed along the hull in different areas and independently drives a corresponding electric thruster. Each propulsion subsystem is equipped with an independent energy storage device, a local controller, an electric thruster, and a remote control component. The local controller is electrically connected to the energy storage device, the electric thruster, and the remote control component, controlling the charging and discharging of the energy storage device, controlling the power output of the electric thruster, and communicating with the remote control component. The local controller competes with other local controllers to determine whether it is the master or slave unit. The propulsion subsystem corresponding to the master unit is configured as follows: The master control system, with its corresponding slave propulsion subsystem configured as a slave system, receives raw control commands. The master system parses these raw control commands into a first control command executed by the master system and a second control command executed by each slave system. The master system distributes each of the second control commands to each slave system via a communication bus, allowing each slave system to independently manage the power output of its corresponding electric propulsion unit based on the received second control command. Each slave system feeds back its corresponding slave system's operating status information to the master system via the communication bus, which is then aggregated and fed back to the master system's remote control component.
[0006] Optionally, the local controller's master determination method includes a manual designation mode, a default strategy mode, and an automatic fault switching mode: When a manual selection operation is received from the human-machine interface of the remote control component, the manual designation mode is used, in which the local controller corresponding to the selected propulsion subsystem is identified as the master; when no manual selection operation is received, the default strategy mode is used, in which the local controller corresponding to the propulsion subsystem located in the bow area or the central stern area is identified as the master; when a fault is detected in the original master control system, the automatic fault switching mode is used, in which the local controllers compete for master-slave status, and any set of slave controllers in normal operating condition is re-identified as the new master.
[0007] Optionally, each of the aforementioned remote control components is connected to the local controller of the corresponding propulsion subsystem via an independent communication link; in master-slave control mode, the remote control component corresponding to the master control system acquires control authority, while the remote control components of each slave system are in a state of disabled control authority; after the master-slave relationship is terminated, each remote control component regains independent control authority.
[0008] Optionally, the master-slave competition follows the following determination rules: when any set of the remote control components receives a control command, the local controller of the propulsion subsystem corresponding to that set of remote control components is identified as the master, and the other local controllers are identified as slaves; and / or, the local controller of each propulsion subsystem obtains the energy storage capacity of the corresponding energy storage device, and by comparing the energy storage capacity, identifies the local controller of the propulsion subsystem with the largest energy storage capacity as the master.
[0009] This application also provides a ship master-slave control method, applied to a ship electric propulsion system comprising at least two independent propulsion subsystems. Each propulsion subsystem is equipped with an independent energy storage device, a local controller, an electric thruster, and a remote control component. The method includes: each local controller determining itself as the master or slave through master-slave competition; the propulsion subsystem corresponding to the master is configured as the master control system, and the propulsion subsystem corresponding to the slave is configured as the slave system; the remote control component of the master control system receives input raw control commands; the master parses the raw control commands into a first control command for execution by the master control system itself and a second control command for execution by each slave system; the master distributes each second control command to each slave via a communication bus, and each slave independently manages the power output of the electric thruster of its corresponding slave system; each slave feeds back the operating status information of its corresponding slave system to the master via the communication bus, and the master summarizes and feeds it back to the remote control component of the master control system.
[0010] Optionally, it also includes: in response to a mode switching command issued by the remote control component, entering the master-slave control mode, or exiting the master-slave control mode and restoring the independent control mode; when exiting the master-slave control mode, the instruction parsing and distribution linkage between the master and each slave is released, and each propulsion subsystem resumes independent operation.
[0011] Optionally, after restoring the independent control mode, the following additional features are included: In the independent control mode, the remote control components of each propulsion subsystem are simultaneously active, receiving independent control inputs from the operator for the three propulsion subsystems on the port, starboard, and stern respectively; each remote control component sends the corresponding operation command to the local controller of its subsystem through its own independent communication link; each local controller independently manages the electric propulsion power output of its subsystem according to the received operation command of its subsystem, and there is no command linkage relationship between the propulsion subsystems.
[0012] Optionally, the main engine parses the original maneuvering commands into a first control command to be executed by the main control system itself and a second control command to be executed by each subordinate system. This includes: the main engine parses the original maneuvering commands based on the current ship motion mathematical model and / or a preset propeller coordination strategy, and generates a first control command to be executed by the main control system itself and a second control command to be executed by each subordinate system.
[0013] Optionally, the main engine parses the original maneuvering command based on the current ship motion mathematical model and / or a preset propeller coordination strategy, generating a first control command executed by the main control system itself and a second control command executed by each subordinate system. This includes: when the original maneuvering command is a forward / reverse command, the main engine generates control commands for each subordinate system that are consistent with the thrust direction and thrust value of the main control system, so as to achieve multi-propeller coordinated propulsion; when the original maneuvering command is a turning command, the main engine generates thrust reduction or reverse thrust commands for the subordinate system on the inside of the turning direction and thrust increase commands for the subordinate system on the outside of the turning direction, so as to achieve ship turning through differential thrust; when the original maneuvering command is a stationary rotation command, the main engine generates thrust commands in opposite directions for the subordinate systems on both sides, while the main control system maintains neutral thrust or minimum thrust, so as to achieve the ship turning around its own center in place.
[0014] This application also provides an electronic device, including: a memory and a processor; the memory is used to store a computer program, and the processor is coupled to the memory and used to execute the computer program for use in the steps of the master-slave control method.
[0015] This application also provides a computer-readable storage medium storing a computer program, which, when executed by a processor, enables the processor to implement the steps in the master-slave control method.
[0016] In this embodiment, the ship's electric propulsion system includes at least two independent propulsion subsystems distributed along the hull. Each subsystem has an independent energy storage device, a local controller, an electric thruster, and a remote control component. Each local controller determines the master or slave unit through master-slave competition. The remote control component of the master control system receives the original control commands, which are then parsed by the master control system into a first control command executed by the master control system itself and a second control command corresponding to each slave system. These commands are then distributed to each slave unit via a communication bus. Each slave unit independently manages the power output of its corresponding electric thruster according to the second control command and feeds back its operating status information to the master control system. The master control system then aggregates this information and feeds it back to the remote control component. This master-slave redundancy eliminates the risk of single-point failure and improves the system's fault tolerance, while also ensuring the convenience of multi-thruster coordinated operation and the flexibility of mode switching. Attached Figure Description
[0017] The accompanying drawings, which are included to provide a further understanding of this application and form part of this application, illustrate exemplary embodiments and are used to explain this application, but do not constitute an undue limitation of this application. In the drawings: Figure 1a A schematic diagram of the structure of a ship electric propulsion system provided in an exemplary embodiment of this application; Figure 1b A schematic diagram of the internal electrical structure of a first propulsion subsystem provided as an exemplary embodiment of this application; Figure 2 A schematic diagram of each propulsion subsystem and its corresponding electric thruster provided for an exemplary embodiment of this application; Figure 3 A schematic flowchart of a ship master-slave control method provided for an exemplary embodiment of this application; Figure 4 A schematic diagram of the structure of an electronic device provided for an exemplary embodiment of this application. Detailed Implementation
[0018] To make the objectives, technical solutions, and advantages of this application clearer, the technical solutions of this application will be clearly and completely described below in conjunction with specific embodiments and corresponding drawings. Obviously, the described embodiments are only a part of the embodiments of this application, and not all of them. Based on the embodiments in this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.
[0019] It should be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for analysis, stored data, and displayed data) involved in this application are all information and data authorized by the user or fully authorized by all parties. Furthermore, the collection, use, and processing of such data must comply with the relevant laws, regulations, and standards of the relevant countries and regions, and corresponding access points are provided for users to choose to authorize or refuse. In addition, the various models involved in this application (including but not limited to language models or large models) comply with relevant laws and standards.
[0020] This application provides a technical solution that constructs multiple independent propulsion subsystems distributed along the hull to form a distributed control architecture. Each propulsion subsystem is equipped with independent energy, control, execution, and manipulation units, eliminating the traditional centralized central controller. The master control node is dynamically selected based on the master-slave competition mechanism among the local controllers. The master unit uniformly parses global manipulation commands and distributes matching cooperative control commands to each slave unit. Each slave unit independently completes propulsion power management locally based on the received commands. At the same time, the master unit summarizes the operating status of all subsystems on the ship and centrally feeds it back to the control terminal. This eliminates the risk of single-point failure from the root, improves the system's fault tolerance, and takes into account the convenience of multi-propulsion cooperative control and the flexibility of mode switching.
[0021] The technical solutions provided by the various embodiments of this application will be described in detail below with reference to the accompanying drawings.
[0022] Figure 1a This is a schematic diagram of the overall architecture of a ship electric propulsion system provided for an exemplary embodiment of this application. Figure 1a As shown, the ship's electric propulsion system includes at least two independent propulsion subsystems. For ease of explanation, Figure 1a The example illustrates a first propulsion subsystem 11 (or simply propulsion subsystem 11), a second propulsion subsystem 12 (or simply propulsion subsystem 12), and a third propulsion subsystem 13 (or simply propulsion subsystem 13), but this application is not limited thereto. Each propulsion subsystem is independent at the hardware level and is distributed along the hull in different areas—for example, such as... Figure 2 As shown, the first propulsion subsystem 11 is located in the bow area, the second propulsion subsystem 12 is located in the port side area, and the third propulsion subsystem 13 is located in the starboard side area (or the central area of the stern) – and each subsystem independently drives its corresponding propeller (such as the first propeller 113a, the second propeller 123a, and the third propeller 133a).
[0023] The following will take the first propulsion subsystem 11 as an example to explain in detail the specific implementation of the propulsion subsystem. The structures of other propulsion subsystems (such as the second propulsion subsystem 12 and the third propulsion subsystem 13) are the same as those of the first propulsion subsystem 11, with the only difference being the arrangement position and the corresponding thrusters, which will not be repeated here.
[0024] In the first propulsion subsystem 11, the energy storage device 111, the local controller 112, the electric thruster 113 and the remote control component 114 form a complete power and control link within the subsystem, which is physically independent of the hardware links of other propulsion subsystems.
[0025] The energy storage device 111 provides independent power to the first propulsion subsystem 11 and can be a lithium iron phosphate battery pack, fuel cell pack, supercapacitor pack, or any combination thereof. Its power output terminal is electrically connected to the local controller 112 and the electric thruster 113 to power the various components of the first propulsion subsystem 11. The local controller 112 is electrically connected to the management unit (such as the battery management system) of the energy storage device 111 and can collect parameters such as voltage, current, remaining power, and cell temperature of the energy storage device 111 in real time. It can also control the charging and discharging switching, charging and discharging power, and charging and discharging protection logic of the energy storage device 111 to realize the internal power management of the first propulsion subsystem 11.
[0026] The electric propulsion unit 113 is a thrust actuation component and can be a podded electric propulsion unit or an electric internal engine, such as... Figure 1b As shown, its power input terminal is connected to the frequency converter 115, and the frequency converter 115 is connected to the output terminal of the energy storage device 111 via the power distribution device 116. Figure 1b This is a schematic diagram of the internal electrical structure of a first propulsion subsystem provided as an exemplary embodiment of this application; the internal electrical structures of other propulsion subsystems are similar. Figure 1b As shown, the electric thruster 113 includes a motor 1131 and a propeller 1132. The motor 1131 is electrically connected to a frequency converter 115. The frequency converter 115 obtains DC power from the power distribution unit 116 and converts the DC power into AC power to supply the motor. The power distribution unit 116 obtains DC power from the energy storage unit 111 and provides it to the frequency converter 115.
[0027] Optionally, such as Figure 1bAs shown, the first propulsion subsystem 11 also includes an independent onboard charger 117. The independent onboard charger 117 is electrically connected to an AC shore power box and is used to charge the energy storage device 111. A local controller 112 is electrically connected to the independent onboard charger and is used to control the on / off state of the charging path and the charging power limit. The AC shore power box provides AC input power to the onboard charger 117 via a contactor, and the local controller 112 remotely controls the opening and closing of the charging path by controlling the contactor coil. The onboard charger 117 converts AC power to DC power and outputs it to the energy storage device 111. During charging, the energy storage device 111 feeds back real-time state of charge and voltage values to the local controller 112 via a communication bus. The local controller 112 dynamically adjusts the charging power limit accordingly to prevent overcharging or exceeding the charging current limit. In an optional implementation, when the ship is in range-extending mode and needs to connect a temporary diesel generator, the output of the diesel generator can be connected to the AC input terminal of the independent onboard charger via a manual switch, while simultaneously disconnecting from the AC shore power box. Since each propulsion subsystem is equipped with an independent onboard charger and charging path, the three systems can be charged simultaneously without sharing charging equipment, which shortens the overall charging time and avoids the risk of the entire ship being unable to recharge due to the failure of a single charger.
[0028] The power distribution unit 116 includes a DC bus 1161 and an auxiliary chopper unit 1162. The DC bus 1161 connects to an energy storage device 111 and a frequency converter 115. The auxiliary chopper unit 1162 connects to the DC bus 1161 and an onboard charger 117. The energy storage device 111 provides DC power to the DC bus 1161, and the DC bus 1161 provides AC power to the electric thruster 113 via the frequency converter 115. The DC bus 1161 provides high-voltage power to the electric thruster 113 via the frequency converter 115, enabling the electric thruster 113 to output high-power propulsion. The frequency converter 115 can provide high-voltage power higher than 60V to the electric thruster 113, such as 120V or 220V. The DC bus 1161 enables the DC network of the first propulsion subsystem 11.
[0029] Optionally, such as Figure 1bAs shown, the power distribution unit 116 can also be connected to a cooling system 118, which includes a circulating pump and a temperature sensor. The local controller 112 is electrically connected to the circulating pump and temperature sensor, and is used to adjust the speed of the circulating pump according to the operating parameters of the energy storage device 10, the frequency converter 115, and the electric propulsion unit 40. The temperature sensor collects the coolant return temperature in real time and transmits the temperature signal to the local controller 112 via an analog acquisition loop. The local controller 112 calculates the target pump speed according to a preset temperature-flow curve and drives the circulating pump frequency converter to adjust the motor speed through a pulse width modulation signal, thereby achieving on-demand distribution of cooling flow. When the return temperature is lower than the dew point temperature +2°C, the local controller 112 automatically starts the anti-condensation heater; when the return temperature is higher than the dew point temperature +5°C, the local controller 112 automatically stops the anti-condensation heater to prevent condensation inside the compartment from causing a decrease in electrical insulation. Because the cooling circuits of each propulsion subsystem are physically isolated and there are no shared cooling water pipes across compartments, even if a coolant leak occurs in one compartment, it will not affect the heat dissipation capacity of equipment in other compartments, thus ensuring the consistency of the thermal management system and the electrical isolation architecture.
[0030] In an optional implementation, the independent cooling system 118 may further include a heat exchanger connected in series with a circulating pump in the cooling loop to exchange the heat carried by the coolant with the external environment or the ship's seawater cooling system 118. A local controller 112 is electrically connected to the heat exchanger's fan or seawater valve and can dynamically adjust the heat exchange intensity based on the difference between the return temperature and the external ambient temperature. When the ship is navigating in low-temperature waters or the equipment is operating under low load, the local controller 112 can reduce the heat exchanger fan speed or close the seawater valve opening to avoid over-cooling and energy waste. When the equipment is operating under high load or the ambient temperature is high, the local controller 112 increases the heat exchange intensity to ensure heat dissipation efficiency. It should be noted that the heat exchanger is not a necessary component of the independent cooling system 118. In some embodiments, the cooling loop may use an open-loop circulation or direct air cooling method instead of a heat exchanger, as long as effective heat removal from the equipment can be achieved; all such methods fall within the scope of this application.
[0031] Optionally, such as Figure 1b As shown, the power distribution device 116 may also be connected to an energy-consuming braking circuit 119. The energy-consuming braking circuit 119 includes at least a braking control unit (BCU) and a braking resistor R. The input terminal of the braking control unit is connected to the DC bus 1161, and the output terminal is connected to the braking resistor R. When the electric thruster 113 is in braking or deceleration mode, the regenerative energy fed back to the DC bus 1161 by the electric thruster 113 is converted into heat energy and consumed through the braking resistor, thereby maintaining the voltage stability of the DC bus 1161.
[0032] Optionally, such as Figure 1bAs shown, the propulsion subsystem 11 also includes a steering system 80. The steering system 80 includes a servo motor 81 and a steering drive unit 82. The servo motor 81 is electrically connected via a DC bus 70 to obtain operating power; the control terminal of the servo motor 81 is connected to a local controller 112, and the output terminal of the servo motor 81 is mechanically connected to the steering drive unit 82. The output terminal of the steering drive unit 82 is connected to the rudder (not shown in the figure). The servo motor 81 responds to steering commands from the first local controller 112, driving the steering drive unit 82 to deflect the rudder, thereby changing the ship's course. The steering system 80 and the electric propulsion unit 113 are functionally independent: the electric propulsion unit 113 is responsible for generating propulsion, and the steering system 80 is responsible for changing the course; the two work together to achieve navigation control of the ship.
[0033] In this embodiment, the local controller 112 includes a central controller and a logic circuit controller. The central controller can be connected to the remote control component 114, energy storage device 111, frequency converter 115, logic circuit controller, and power distribution device 116 via a communication bus. The central controller is responsible for receiving, distributing, parsing, and processing the operating information of the energy storage device 111, frequency converter 115, logic circuit controller, and power distribution device 116. The power distribution device 116 includes electrical sensors installed on power distribution components such as the DC bus 1161 and auxiliary chopper unit 1162, which feed back electrical parameters to the central controller via the communication bus. Figure 1b As shown, the power distribution unit 116 also includes multiple electrical switches configured at the connection nodes of the DC bus 1161, energy storage device 111, frequency converter 115, and auxiliary chopper unit 1162. The logic circuit controller includes multiple relay control circuits connected to corresponding electrical switches to enable emergency power distribution control of the power distribution unit 116 independent of the communication bus. For example, the logic circuit controller can be used to perform emergency start / stop of the energy storage device 111 and emergency start / stop of the frequency converter 115. The logic circuit controller is also configured with drive relay control circuits connected to the frequency converter 115 to enable emergency acceleration and deceleration control of the electric propeller 113. The central controller is connected to the logic circuit controller to implement permission decisions for emergency control in master-slave control mode. For example, in master-slave control mode, only the emergency control input of the master unit is valid, while the emergency control of the slave unit is invalid.
[0034] In this embodiment, the frequency converter 115 is connected to the central controller of the local controller 112. The central controller of the local controller 112 can control the speed, torque and rotation direction of the electric thruster 113 through any means such as pulse width modulation signals, communication bus commands or analog outputs, thereby adjusting the magnitude and direction of the thrust.
[0035] The remote control component 114 serves as the interface between the operator and the propulsion subsystem. It may include at least one input device 1141, such as a control handle, touchscreen, steering wheel, throttle lever, button panel, or knob, and at least one output device, such as an LCD screen or indicator lights. The remote control component 114 is connected to the local controller 112 via an independent communication link (such as CAN (Controller Area Network) or Ethernet) to send operation commands to the local controller 112 and receive operating status information from the local controller 112 for display. It is understood that devices such as the control handle, touchscreen, and throttle lever can be connected to the central controller of the local controller 112 via a communication bus to achieve communication and interaction with the central controller. Devices such as button panels and knobs can be hardwired to the logic circuit controller of the local controller 112 to achieve emergency control. Of course, in other embodiments, the local controller 112 may only be configured with a central controller.
[0036] In this embodiment, the various propulsion subsystems are interconnected via a communication bus 130 (such as an industrial fieldbus like a CAN bus, Ethernet, or RS-485 (serial communication interface standard)). Specifically, the central controller of the first local controller 112, the central controller 1221 of the second local controller 122, and the central controller 1321 of the third local controller 132 all serve as nodes on the communication bus 130 and can exchange data with each other.
[0037] During system startup or operation, the central controller of each local controller (such as 112, 122, 132) competes with other local controllers via communication bus 130 to determine whether it will act as a master or slave in the system. The specific implementation of the master-slave competition will be detailed below. The propulsion subsystem corresponding to the master is configured as the master control system, and the propulsion subsystem corresponding to the slave is configured as the slave system. For example, if the first local controller 112 competes to become the master, then the first propulsion subsystem 11 is the master control system, and the second propulsion subsystem 12 and the third propulsion subsystem 13 are slave systems.
[0038] In master-slave control mode, the remote control component of the master control system (such as the first remote control component 114) is granted control authority and serves as the input interface for the master control system's control commands. The operator inputs raw control commands through the remote control component 114 of the master control system (e.g., issuing control intentions such as forward, reverse, left turn, right turn, or rotation in place via input devices such as joysticks, buttons, touchscreens, or knobs). After receiving the raw control commands, the local controller of the master control system (i.e., the host 112) parses and processes them, generating two types of control commands: a first control command—executed by the master control system's own electric thruster 113; and a second control command—executed by the electric thrusters 123 and 133 of each subordinate system (such as the second propulsion subsystem 12 and the third propulsion subsystem 13), respectively.
[0039] The host 112 distributes the second control commands to the corresponding slave units (such as the second local controller 122 and the third local controller 132) via the communication bus 130. Upon receiving the second control command, each slave unit independently manages the power output of the electric propulsion system corresponding to it, including adjusting parameters such as the propulsion motor's speed, torque, and direction. During task execution, each slave unit continuously collects the operating status information of its corresponding slave system. This operating status information includes, but is not limited to, at least one of the following: propulsion motor speed, torque, temperature, current; remaining power and output voltage of the energy storage device; and the operating status of the local controller. This information is then fed back to the host 112 via the communication bus 130. After receiving the operating status information from each slave unit, the host 112 summarizes it with the operating status information of its own main control system and feeds back the summarized information to at least the remote control component 114 of the main control system, allowing operators to monitor the real-time operating status of all propulsion subsystems on the ship.
[0040] This embodiment constructs a distributed propulsion system. At the hardware level, each propulsion subsystem is independent and distributed. At the control level, a master-slave competition mechanism dynamically determines the control center (master), and the master role can be dynamically transferred between subsystems. This approach fundamentally eliminates the single point of failure risk of a centralized architecture—if any propulsion subsystem (including its local controller, energy storage device, electric thruster, or remote control component) fails, other propulsion subsystems can still operate independently and provide propulsion capability. Simultaneously, since each slave unit executes its own propulsion control independently based on instructions distributed by the master unit, without secondary forwarding through the central controller, control loop latency is significantly reduced.
[0041] This embodiment does not limit the specific implementation method of the master-slave competition described above. In some optional embodiments, master-slave competition can be executed based on various triggering conditions and judgment rules, including but not limited to the following methods: Method 1: Master-slave contention triggered by control commands: When any remote control component of the propulsion subsystem (such as the first remote control component 114) receives a control command from the operator, the local controller corresponding to that remote control component (such as the first local controller 112) is automatically identified as the master, and the other local controllers (such as the second local controller 122 and the third local controller 132) are identified as slaves. This method realizes the intuitive control logic of "whoever is operated first becomes the master".
[0042] Specifically, each local controller continuously monitors the input status of its respective remote control component. When the first local controller 112 detects a new control command input to its remote control component 114, the first local controller 112 broadcasts a master declaration message to other local controllers via the communication bus 130. The message carries the identifier and timestamp of the first local controller 112. After receiving the declaration message, other local controllers confirm that the first local controller 112 is the master and switch to slave mode. If two or more local controllers issue master declarations simultaneously within a preset time window, the master is determined according to preset arbitration rules (such as comparing the size of the controller identifier, comparing the current energy storage capacity of the corresponding energy storage device, etc.).
[0043] Method 2: Master-slave competition based on comparison of energy storage capacity: Each propulsion subsystem's local controller (e.g., 112, 122, 132) acquires the current energy storage capacity of its corresponding energy storage device (e.g., 111, 121, 131) and exchanges their respective energy storage capacity information with each other via communication bus 130. Each local controller compares the energy storage capacity of each energy storage device and identifies the local controller corresponding to the propulsion subsystem with the highest energy storage capacity as the main control system. The advantage of this approach is that it prioritizes the subsystem with the most abundant energy as the main control system, which is beneficial for achieving balanced energy utilization throughout the ship.
[0044] The two methods described above can be used individually or in combination, and this embodiment does not impose any restrictions on this. For example, in one combined implementation, a master-slave contention method based on energy storage capacity is used by default, but when a remote control component is operated, it immediately switches to a method triggered by control commands.
[0045] Of the two methods mentioned above, the rule based on control command triggering realizes the intuitive control of "whoever operates first becomes the main unit", which enables the system to respond to the user's control intentions in real time without complicated configuration procedures, and is especially suitable for emergency control scenarios; the rule based on energy storage capacity comparison prioritizes the propulsion subsystem with the most abundant energy as the main unit, which helps to distribute energy consumption evenly throughout the ship and avoid premature failure of a certain energy storage device due to over-discharge.
[0046] Method 3: Manually specified mode, default policy mode, and automatic fault switching mode: The master controller determination method includes a manual designation mode and a default policy mode. When a manual selection operation is received from the remote control component's human-machine interface, the manual designation mode is used, and the local controller corresponding to the selected propulsion subsystem is identified as the master controller. When no manual selection operation is received, the default policy mode is used, and the local controller corresponding to the propulsion subsystem located in the bow area or the central stern area is identified as the master controller. When a failure is detected in the original master control system, an automatic fault switching mode is used, and the master-slave competition among the local controllers is re-executed. Any local controller corresponding to a slave controller that is in normal operating condition can be re-identified as the new master controller.
[0047] In this embodiment, by setting three main control system determination modes—manual designation, default strategy, and automatic fault switching—the adaptability and reliability of the system under different operating conditions are significantly improved. The manual designation mode gives operators the ability to directly intervene, facilitating the rapid designation of the most suitable subsystem as the main control system during special operations (such as berthing / unberthing and dynamic positioning). The default strategy mode simplifies the operation process under normal navigation, automatically determining the main control system without manual intervention. The automatic fault switching mode ensures that when the original main control system fails, the system can automatically select a new main control system, achieving a seamless migration of the main control role, thereby reducing system downtime caused by single point of failure and significantly improving the availability of the entire ship's propulsion system.
[0048] In some alternative embodiments, the host resolves the original manipulation instructions into first control instructions and second control instructions, which can be achieved in the following ways: After receiving the original control commands, the main unit (such as the first local controller 112) needs to convert them into specific control commands to be executed by each propulsion subsystem. This parsing process can be achieved based on at least one of the current ship motion mathematical model and the preset propulsion coordination strategy.
[0049] A ship motion mathematical model is a model that mathematically describes the motion characteristics of a ship in multiple degrees of freedom (e.g., sway, roll, pitch, and bow). In one implementation, a three-degree-of-freedom motion model of the ship in the horizontal plane can be established, including equations for sway, roll, and bow motion. These equations incorporate parameters such as the ship's mass, added mass, and hydrodynamic damping coefficient, as well as the thrust and torque generated by each propeller as inputs. Based on this ship motion mathematical model, the main engine can inversely solve for the magnitude and direction of the thrust required by each propeller based on the desired ship motion state (i.e., the control intention expressed in the original maneuvering commands), thereby generating control commands corresponding to each subsystem.
[0050] The thruster coordination strategy consists of preset control logic rules used to determine the thrust distribution scheme for each thruster under different control scenarios. The following examples illustrate this with several typical control scenarios: Forward / Reverse Command: When the original control command is forward or reverse, the host generates control commands for each slave system that are consistent with the thrust direction and thrust value of the main control system, so that the thrust direction of all thrusters is consistent, and multi-thruster coordinated propulsion is realized.
[0051] Steering command: When the original control command is a steering command, the main engine generates a thrust reduction or thrust reversal command for the slave system on the inside of the steering path and a thrust increase command for the slave system on the outside of the steering path, thereby achieving ship steering through differential thrust.
[0052] Rotate in place command: When the original control command is the rotate in place command, the main engine generates thrust commands in opposite directions for the two subordinate systems, while the main control system maintains neutral or minimum thrust, so that the ship rotates in place around its own center.
[0053] After the host completes the parsing, it executes the generated first control command locally and encodes each second control command into a data frame according to a preset communication protocol, which is then distributed to the corresponding slave unit via the communication bus 130. Each data frame contains at least the target slave unit's identifier, command type, thrust direction, thrust magnitude, and execution timestamp. Upon receiving the data frame, the slave unit decodes and verifies it, and executes the corresponding propulsion control operation after confirming that it is correct.
[0054] In this embodiment, the main engine performs command parsing based on the ship's motion mathematical model and the propeller coordination strategy. Compared with the simple average or fixed ratio distribution of thrust in the traditional centralized architecture, it can calculate the optimal thrust distribution scheme of each propeller in real time according to the actual motion state and control objectives of the ship. This can reduce the trajectory deviation of the ship during turning maneuvers, reduce the sway overshoot during acceleration / deceleration, and significantly improve the overall energy efficiency of the propulsion system.
[0055] The following example illustrates the complete process of a ship's electric propulsion system from startup to the completion of master-slave determination.
[0056] After the system is powered on, the local controller of each propulsion subsystem first executes a self-test program to check whether the energy storage device, electric thruster, remote control components, and communication interface of its subsystem are in normal working condition. After the self-test passes, each local controller broadcasts its own message through the communication bus. The message includes the local controller's identifier, current status (normal / fault), and the energy storage capacity of the energy storage device.
[0057] After receiving messages from other controllers, each local controller begins master-slave contention. Optionally, master-slave contention can proceed in the following priority order: First priority: Check if any remote control components are being operated. If so, the local controller corresponding to the operated remote control component directly becomes the host.
[0058] Second priority: If no remote control component is being operated, check if the system is in manual designation mode. If the operator has manually selected a propulsion subsystem as the master control system through the human-machine interface of the remote control component, the selected local controller becomes the master.
[0059] Third priority: If neither remote control operation nor manual designation is performed, the default strategy is adopted—the local controller corresponding to the propulsion subsystem located in the bow or center stern area is identified as the main controller. This default strategy is based on common ship handling practices—propellers in the bow or center stern area typically offer better maneuverability and control convenience.
[0060] Fourth priority: If none of the above conditions are met (for example, the propulsion subsystem corresponding to the default position fails), then each local controller compares the energy storage capacity of the energy storage device, and the local controller corresponding to the propulsion subsystem with the largest energy storage capacity acts as the master.
[0061] It should be specifically noted that this application does not impose any restrictions on the execution priority order of various determination rules (including but not limited to rules triggered by control commands, rules based on energy storage capacity comparison, manual specification mode, default strategy mode, and automatic fault switching mode) used in the master-slave competition process. In actual implementation, the priority order of the above rules can be flexibly configured according to the ship's navigation conditions, operational task requirements, operator preferences, or the system's adaptive strategy. For example, in some scenarios, the comparison based on energy storage capacity can be set as the highest priority to achieve balanced energy management across the ship; in emergency control scenarios, the rule triggered by control commands can be set as the highest priority to ensure the system's immediate response to operational intentions; in normal navigation, the default strategy or manual specification method can be used. All implementations that use at least one or more combinations of the above rules and determine the master-slave relationship in any priority order should be considered to fall within the scope of protection claimed in this application.
[0062] Once the master is determined, it sends a master-slave relationship confirmation message to all slaves via the communication bus. Upon receiving the confirmation message, each slave records the master's identification information and enters slave working mode. Subsequently, each slave periodically sends heartbeat messages to the master to report its own operating status, and the master periodically broadcasts system status information to all slaves.
[0063] When the master unit fails (such as a local controller crash or communication interface failure), if each slave unit does not receive a broadcast message from the master unit for several consecutive heartbeat cycles, it determines that the original master unit has failed or is unavailable, automatically triggering a new round of master-slave contention. During this process, any local controller corresponding to a slave unit that is in normal operating condition can participate in the contention and be re-identified as the new master unit, thereby achieving seamless switching of the master role and ensuring that the system can continue to operate even when the master control system fails.
[0064] In some optional embodiments, after system startup and master-slave determination, each propulsion subsystem has established a stable master-slave control relationship according to predetermined rules—the master unit is responsible for command parsing and distribution, and each slave unit collaboratively executes propulsion tasks according to the master unit's commands. However, in the actual navigation and operation of ships, different operating conditions have different requirements for the control methods of the propulsion system: during long-distance navigation in open waters, operators often want to achieve coordinated propulsion of multiple thrusters with the simplest operation; while in delicate operation scenarios such as narrow waterways, berthing and unberthing, or dynamic positioning, it may be necessary to independently control each thruster to achieve more flexible maneuverability. Therefore, this embodiment provides a switching mechanism between master-slave control mode and independent control mode to meet the application needs of the above different scenarios. The following will explain the switching mechanism between master-slave control mode and independent control mode: Optionally, each remote control unit (e.g., 114, 124, 134) is connected to the local controller of its corresponding propulsion subsystem via an independent communication link. In master-slave control mode, the master system's remote control unit (e.g., remote control unit 114) acquires full system control authority, while the remote control units of each slave system (e.g., remote control units 124, 134) are in a disabled control state. This means that when an operator operates a slave system's remote control unit, its commands will not be executed by the corresponding local controller. After the master-slave relationship is terminated, each remote control unit regains independent control authority, and each unit can normally control its corresponding propulsion subsystem. This method, connecting each remote control unit to the local controller via an independent communication link and disabling the permissions of slave remote control units in master-slave mode, effectively avoids command conflicts and confusion caused by simultaneous input from multiple control terminals. Furthermore, after the master-slave relationship is terminated, each remote control unit automatically regains independent control authority without requiring reconfiguration or a system restart, ensuring smooth mode switching. This mechanism enables the system to quickly switch between centralized collaborative and decentralized independent control modes, which not only meets the unified command requirements during collaborative operations, but also takes into account the flexibility of multi-point control under special working conditions, significantly improving the ease of operation and safety.
[0065] Optionally, when the operator issues a mode switching command (e.g., by clicking "Exit Master-Slave Mode" or "Enter Master-Slave Mode" on the touchscreen), the master unit broadcasts the mode switching notification to all slave units via the communication bus. Each slave unit confirms and exits or enters the master-slave control mode. When exiting the master-slave control mode, the command parsing and distribution linkage between the master unit and each slave unit is released, and each propulsion subsystem resumes independent operation. That is, each local controller performs propulsion control only according to the remote control component commands of its own subsystem. In this way, the system can freely switch between master-slave cooperative mode and independent mode. When exiting master-slave mode, the linkage is released, and each propulsion subsystem immediately resumes independent operation, eliminating the dependency of the slave system on the master unit in master-slave mode and enhancing the system's resilience. This switching mechanism allows the vessel to flexibly adjust its control strategy according to the navigation environment—for example, using master-slave mode to simplify operation in open waters, and switching to independent mode for precise control in narrow waterways or when berthing or unberthing, thus balancing operational convenience and maneuverability.
[0066] Optionally, in independent control mode, the remote control components of each propulsion subsystem (such as 114, 124, and 134) are simultaneously active, each receiving independent control inputs from the operator for its respective propulsion subsystem. Taking a vessel with three propulsion subsystems (located on the port, starboard, and stern respectively) as an example: In independent control mode, the remote control components of the port, starboard, and stern propulsion subsystems can all simultaneously receive control inputs from the operator. Each remote control component sends its corresponding operation command to the local controller of its subsystem via its own independent communication link. Each local controller independently manages the electric propulsion power output of its subsystem based on the received operation commands. In this mode, there is no command linkage between the propulsion subsystems; each subsystem operates completely independently.
[0067] The specific operational procedures described above for the independent control mode ensure that each propulsion subsystem can be controlled completely independently. Independent communication links between each remote control unit and the local controller guarantee the real-time performance and reliability of command transmission, avoiding bus contention or data congestion. This mode allows multiple operators to control different propulsion units, providing a technical foundation for collaborative operations on large vessels (such as one person steering, one person controlling the side thrusters, and one person controlling the main thrusters). It also facilitates the independent assumption of propulsion tasks by other subsystems in the event of a failure in one subsystem, further enhancing the system's fault tolerance and operational flexibility.
[0068] Based on the above embodiments, this embodiment also provides a ship master-slave control method, applied to a ship electric propulsion system comprising at least two independent propulsion subsystems, each propulsion subsystem being configured with an independent energy storage device, a local controller, an electric thruster, and a remote control component. For example... Figure 3As shown, the method may include: Step 31: Each local controller determines whether it is the master or slave through master-slave competition. The propulsion subsystem of the corresponding master is configured as the master control system, and the propulsion subsystem of the corresponding slave is configured as the slave system.
[0069] Step 32: The remote control component of the main control system receives the input raw control command. The host parses the raw control command into a first control command for the main control system to execute itself and a second control command for each subordinate system to execute accordingly.
[0070] Step 33: The host computer distributes each second control command to each slave computer via the communication bus, and each slave computer independently manages the power output of the electric thruster of its corresponding subordinate system.
[0071] Step 34: Each slave device feeds back the corresponding slave system's operating status information to the host through the communication bus, and the host summarizes and feeds it back to the remote control component of the main control system.
[0072] By using steps 31-34 above, the risk of single point of failure can be eliminated at the source, the system's fault tolerance can be improved, and the convenience of multi-thruster coordinated operation and the flexibility of mode switching can be taken into account.
[0073] Optionally, the method further includes: in response to a mode switching command issued by the remote control component, entering a master-slave control mode, or exiting the master-slave control mode and resuming independent control mode; when exiting the master-slave control mode, the instruction parsing and distribution linkage between the master and each slave is released, and each propulsion subsystem resumes independent operation.
[0074] Optionally, after restoring the independent control mode, the following additional features are included: In the independent control mode, the remote control components of each propulsion subsystem are simultaneously active, receiving independent control inputs from the operator for the three propulsion subsystems on the port, starboard, and stern respectively; each remote control component sends the corresponding operation command to the local controller of its subsystem through its own independent communication link; each local controller independently manages the electric propulsion power output of its subsystem according to the received operation command of its subsystem, and there is no command linkage relationship between the propulsion subsystems.
[0075] Optionally, the main engine parses the original maneuvering commands into a first control command to be executed by the main control system itself and a second control command to be executed by each subordinate system. This includes: the main engine parses the original maneuvering commands based on the current ship motion mathematical model and / or a preset propeller coordination strategy, and generates a first control command to be executed by the main control system itself and a second control command to be executed by each subordinate system.
[0076] Optionally, the main engine parses the original maneuvering command based on the current ship motion mathematical model and / or a preset propeller coordination strategy, generating a first control command executed by the main control system itself and a second control command executed by each subordinate system. This includes: when the original maneuvering command is a forward / reverse command, the main engine generates control commands for each subordinate system that are consistent with the thrust direction and thrust value of the main control system, so as to achieve multi-propeller coordinated propulsion; when the original maneuvering command is a turning command, the main engine generates thrust reduction or reverse thrust commands for the subordinate system on the inside of the turning direction and thrust increase commands for the subordinate system on the outside of the turning direction, so as to achieve ship turning through differential thrust; when the original maneuvering command is a stationary rotation command, the main engine generates thrust commands in opposite directions for the subordinate systems on both sides, while the main control system maintains neutral thrust or minimum thrust, so as to achieve the ship turning around its own center in place.
[0077] The specific implementation methods of the above embodiments have been described in detail above, and can be continued here without further explanation.
[0078] It should be noted that the execution subject of each step of the method provided in the above embodiments can be the same device, or the method can be executed by different devices. For example, the execution subject of steps 11 to 14 can be device A; or the execution subject of steps 11 to 12 can be device A, and the execution subject of steps 13 to 14 can be device B; and so on.
[0079] Furthermore, some processes described in the above embodiments and accompanying drawings include multiple operations that appear in a specific order. However, it should be clearly understood that these operations may not be executed in the order they appear herein, or they may be executed in parallel. The operation numbers, such as 12, 13, etc., are merely used to distinguish different operations and do not represent any execution order. In addition, these processes may include more or fewer operations, and these operations may be executed sequentially or in parallel.
[0080] It should be noted that the terms "first" and "second" in this article are used to distinguish different messages, devices, modules, etc., and do not represent a chronological order, nor do they limit "first" and "second" to different types.
[0081] Figure 4 This is a schematic diagram of the structure of an electronic device provided in an exemplary embodiment of this application. This electronic device is applicable to the ship master-slave control method provided in the foregoing embodiments, such as... Figure 4 As shown, the electronic device may include: a memory 401, a processor 402, and a communication component 403.
[0082] Memory 401 is used to store computer programs and can be configured to store various other data to support operation on the electronic device. Examples of this data include instructions for any application or method used to operate on the electronic device, contact data, phone book data, messages, pictures, videos, etc.
[0083] In some exemplary embodiments, processor 402, coupled to memory 401, is used to execute computer programs in memory 401 for: each local controller determining itself as a master or slave through master-slave competition; the propulsion subsystem of the corresponding master is configured as the master control system, and the propulsion subsystem of the corresponding slave is configured as a subordinate system; the remote control component of the master control system receives input raw control commands; the master parses the raw control commands into first control commands for execution by the master control system itself and second control commands for execution by each subordinate system; the master distributes each second control command to each slave via a communication bus, and each slave independently manages the electric propulsion power output of its corresponding subordinate system; each slave feeds back the operating status information of its corresponding subordinate system to the master via the communication bus, and the master summarizes and feeds it back to the remote control component of the master control system.
[0084] Optionally, the processor 402 is also configured to: enter the master-slave control mode or exit the master-slave control mode and restore the independent control mode in response to the mode switching command issued by the remote control component; when exiting the master-slave control mode, the instruction parsing and distribution linkage between the master and each slave is released, and each propulsion subsystem resumes independent operation.
[0085] Optionally, after the processor 402 resumes independent control mode, it is also used for: in independent control mode, the remote control components of each propulsion subsystem are simultaneously active, respectively receiving independent control inputs from the operator for the three propulsion subsystems on the port side, starboard side, and stern; each remote control component sends the corresponding operation command to the local controller of its subsystem through its own independent communication link; each local controller independently manages the electric propulsion power output of its subsystem according to the received operation command of its subsystem, and there is no command linkage relationship between the propulsion subsystems.
[0086] Optionally, when the processor 402 parses the original manipulation command into a first control command to be executed by the main control system itself and a second control command to be executed by each subordinate system, it specifically performs the following: parses the original manipulation command based on the current ship motion mathematical model and / or a preset propeller coordination strategy, and generates a first control command to be executed by the main control system itself and a second control command to be executed by each subordinate system.
[0087] Optionally, the main engine parses the original maneuvering command based on the current ship motion mathematical model and / or a preset propeller coordination strategy, generating a first control command executed by the main control system itself and a second control command executed by each subordinate system. This includes: when the original maneuvering command is a forward / reverse command, the main engine generates control commands for each subordinate system that are consistent with the thrust direction and thrust value of the main control system, so as to achieve multi-propeller coordinated propulsion; when the original maneuvering command is a turning command, the main engine generates thrust reduction or reverse thrust commands for the subordinate system on the inside of the turning direction and thrust increase commands for the subordinate system on the outside of the turning direction, so as to achieve ship turning through differential thrust; when the original maneuvering command is a stationary rotation command, the main engine generates thrust commands in opposite directions for the subordinate systems on both sides, while the main control system maintains neutral thrust or minimum thrust, so as to achieve the ship turning around its own center in place.
[0088] This application also provides a computer-readable storage medium storing a computer program, which, when executed by a processor, enables the processor to implement the steps in the ship master-slave control method.
[0089] This application also provides a computer program product, including a computer program / instruction, which, when executed by a processor, enables the processor to implement the steps in the ship master-slave control method.
[0090] In this embodiment, each subsystem has an independent energy storage device, a local controller, an electric thruster, and a remote control component. Each local controller determines whether to be the master or slave unit through master-slave competition. The remote control component of the master control system receives the original control commands, which the master parses into a first control command executed by the master control system itself and a second control command corresponding to each slave system. This second control command is then distributed to each slave unit via a communication bus. Each slave unit independently manages the power output of its corresponding electric thruster according to the second control command and feeds back its operating status information to the master, which then aggregates and feeds it back to the remote control component. This approach eliminates the risk of single-point failures at the source, improves system fault tolerance, and simultaneously ensures the convenience of multi-thruster coordinated control and the flexibility of mode switching.
[0091] Furthermore, such as Figure 4 As shown, the electronic device also includes other components such as a power supply component 404. Figure 4 The diagram only shows some components and does not mean that the electronic device includes only these components. Figure 4 The components shown.
[0092] The aforementioned memory can be implemented by any type of volatile or non-volatile storage device or a combination thereof, such as Static Random-Access Memory (SRAM), Electrically Erasable Programmable Read Only Memory (EEPROM), Erasable Programmable Read Only Memory (EPROM), Programmable Read-Only Memory (PROM), Read-Only Memory (ROM), magnetic storage, flash memory, magnetic disk, or optical disk.
[0093] The aforementioned communication components are configured to facilitate wired or wireless communication between the device containing the communication components and other devices. The device containing the communication components can access wireless networks based on communication standards, such as WiFi, 2G, 3G, 4G / LTE, 5G, or combinations thereof. In one exemplary embodiment, the communication components receive broadcast signals or broadcast-related information from an external broadcast management system via a broadcast channel. In one exemplary embodiment, the communication components also include a Near Field Communication (NFC) module to facilitate short-range communication. For example, the NFC module may be implemented based on Radio Frequency Identification (RFID), Infrared Data Association (IrDA), Ultra Wide Band (UWB), Bluetooth (BT), and other technologies.
[0094] The aforementioned power supply components provide power to various components within the device in which they reside. These power supply components may include a power management system, one or more power sources, and other components associated with generating, managing, and distributing power to the device in which they reside.
[0095] Those skilled in the art will understand that embodiments of this application can be provided as methods, systems, or computer program products. Therefore, this application can take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, this application can take the form of a computer program product embodied on one or more computer-readable storage media (including, but not limited to, disk storage, compact disc read-only memory (CD-ROM), optical storage, etc.) containing computer-usable program code.
[0096] This application is described with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of this application. It will be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in one or more blocks of the flowchart illustrations and / or one or more blocks of the block diagrams.
[0097] These computer program instructions may also be stored in a computer-readable storage medium that can direct a computer or other programmable data processing device to function in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of manufacture including instruction means that implement the functions specified in one or more flowcharts and / or one or more block diagrams.
[0098] These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer-implemented process, such that the instructions, which execute on the computer or other programmable apparatus, provide steps for implementing the functions specified in one or more flowcharts and / or one or more block diagrams.
[0099] In a typical configuration, a computing device includes one or more processors (Central Processing Unit, CPU), input / output interfaces, network interfaces, and memory.
[0100] Memory may include non-persistent storage in computer-readable media, such as random access memory (RAM) and / or non-volatile memory, such as read-only memory (ROM) or flash RAM. Memory is an example of computer-readable media.
[0101] Computer-readable media includes both permanent and non-permanent, removable and non-removable media that can store information by any method or technology. Information can be computer-readable instructions, data structures, program modules, or other data. Examples of computer storage media include, but are not limited to, phase-change random access memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technologies, CD-ROM, Digital Video Disc (DVD) or other optical storage, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other non-transferable medium that can be used to store information accessible by a computing device. As defined herein, computer-readable media does not include transient computer-readable media, such as modulated data signals and carrier waves.
[0102] It should also be noted that the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such process, method, article, or apparatus. Unless otherwise specified, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes that element.
[0103] The above are merely embodiments of this application and are not intended to limit the scope of this application. Various modifications and variations can be made to this application by those skilled in the art. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of this application should be included within the scope of the claims of this application.
Claims
1. A marine electric propulsion system, characterized in that, It includes at least two independent propulsion subsystems; each propulsion subsystem is distributed along the hull in different areas and independently drives the corresponding electric thruster. Each propulsion subsystem is equipped with an independent energy storage device, a local controller, an electric thruster and a remote control component. The local controller is electrically connected to the energy storage device, the electric thruster and the remote control component, controls the charging and discharging of the energy storage device, controls the power output of the electric thruster and communicates with the remote control component. The local controller is used to compete with other local controllers to determine whether the local controller is the master or slave. The propulsion subsystem of the corresponding master is configured as the master control system, and the propulsion subsystem of the corresponding slave is configured as the slave system. The remote control component of the main control system is used to receive the original control commands. The host parses the original control commands into a first control command executed by the main control system and a second control command executed by each corresponding slave system. The host computer distributes each of the second control commands to each slave computer via a communication bus, and each slave computer independently manages the power output of the electric thruster of the corresponding slave system according to the received second control commands. Each slave device feeds back the operating status information of its corresponding slave system to the host through the communication bus. The host then aggregates the information and feeds it back to the remote control component of the main control system.
2. The system according to claim 1, characterized in that, The host determination methods for the local controller include manual specification mode, default policy mode, and automatic failover mode: When a manual selection operation is received from the human-machine interface of the remote control component, the manual designation mode is adopted. In the manual designation mode, the local controller corresponding to the selected propulsion subsystem is identified as the host. In the absence of the manual selection operation, the default strategy mode is adopted, in which the local controller corresponding to the propulsion subsystem located in the bow area or the central area of the stern is identified as the master. If a fault is detected in the original master control system, an automatic fault switching mode is adopted. In the automatic fault switching mode, the local controllers compete for master and slave status, and the local controller corresponding to any set of slaves that are in normal operation is re-identified as the new master.
3. The system according to claim 1, characterized in that, Each remote control component is connected to the local controller of the corresponding propulsion subsystem via an independent communication link. In master-slave control mode, the remote control component corresponding to the master control system obtains control authority, while the remote control components of each slave system are in a state of disabled control authority. After the master-slave relationship is terminated, each remote control component regains independent control authority.
4. The system according to claim 1, characterized in that, The master-slave competition follows the following determination rules: When any of the aforementioned remote control components receives a control command, the local controller of the propulsion subsystem corresponding to that remote control component is identified as the master, and the remaining local controllers are identified as slaves; and / or, The local controller of each propulsion subsystem obtains the energy storage capacity of the corresponding energy storage device, and by comparing the energy storage capacity, identifies the local controller of the propulsion subsystem with the largest energy storage capacity as the master.
5. A ship master-slave control method, characterized in that, An electric propulsion system for ships comprising at least two independent propulsion subsystems, each subsystem being equipped with an independent energy storage device, a local controller, an electric thruster, and a remote control assembly; the method includes: Each local controller determines whether it is the master or slave through master-slave competition. The propulsion subsystem of the corresponding master is configured as the master control system, and the propulsion subsystem of the corresponding slave is configured as the slave system. The remote control component of the main control system receives the input raw control command, and the host parses the raw control command into a first control command for the main control system to execute itself and a second control command for each subordinate system to execute accordingly. The host computer distributes each second control command to each slave computer via the communication bus, and each slave computer independently manages the power output of the electric thruster of its corresponding subordinate system. Each slave device feeds back the operating status information of its corresponding slave system to the host through the communication bus, and the host summarizes and feeds it back to the remote control component of the main control system.
6. The method according to claim 5, characterized in that, Also includes: In response to a mode switching command issued by the remote control component, it enters master-slave control mode, or exits master-slave control mode and resumes independent control mode; When exiting the master-slave control mode, the linkage between the master and each slave device for instruction parsing and distribution is terminated, and each propulsion subsystem resumes independent operation.
7. The method according to claim 6, characterized in that, After restoring independent control mode, it also includes: In independent control mode, the remote control components of each propulsion subsystem are active simultaneously, receiving independent control inputs from the operator for the three propulsion subsystems on the port side, starboard side, and stern. Each remote control component sends its corresponding operation command to the local controller of its subsystem via its own independent communication link. Each local controller independently manages the power output of its own electric thruster based on the operating instructions received from its own subsystem, and there is no instruction linkage between the various propulsion subsystems.
8. The method according to claim 5, characterized in that, The host parses the original control commands into a first control command for execution by the main control system itself and a second control command for execution by each slave system, including: The main engine parses the original control commands based on the current ship motion mathematical model and / or the preset propeller coordination strategy, and generates the first control command to be executed by the main control system itself and the second control command to be executed by each subordinate system.
9. The method according to claim 8, characterized in that, The main engine parses the original maneuvering commands based on the current ship motion mathematical model and / or a preset propeller coordination strategy, generating a first control command to be executed by the main control system itself and a second control command to be executed by each subordinate system, including: When the original control command is a forward / reverse command, the host generates control commands for each slave system that are consistent with the thrust direction and thrust value of the host system, so as to realize the coordinated propulsion of multiple thrusters; When the original control command is a steering command, the main engine generates a thrust reduction or thrust reversal command for the slave system on the inside of the steering path and a thrust increase command for the slave system on the outside of the steering path, so as to achieve ship steering through differential thrust. When the original control command is a stationary turn command, the main engine generates thrust commands in opposite directions for the two subordinate systems on both sides, while the main control system maintains neutral or minimum thrust to achieve the ship's stationary turn around its own center.
10. An electronic device, characterized in that, include: Memory and processor; The memory is used to store a computer program, and the processor is coupled to the memory to execute the computer program for implementing the steps of the method according to any one of claims 5-9.
11. A computer-readable storage medium storing a computer program, characterized in that, When the computer program is executed by a processor, it causes the processor to perform the steps of the method according to any one of claims 5-9.
