The present disclosure relates to methods and systems for controlling movement of a marine vessel in a body of water, and more specifically to systems and methods for controlling low-speed propulsion of a marine vessel by a manually operable input device such as a joystick.
The following U.S. Patents and Applications provide background information and are incorporated herein by reference in entirety.
U.S. Pat. No. 6,273,771 discloses a control system for a marine vessel that incorporates a marine propulsion system that can be attached to a marine vessel and connected in signal communication with a serial communication bus and a controller. A plurality of input devices and output devices are also connected in signal communication with the communication bus and a bus access manager, such as a CAN Kingdom network, is connected in signal communication with the controller to regulate the incorporation of additional devices to the plurality of devices in signal communication with the bus whereby the controller is connected in signal communication with each of the plurality of devices on the communication bus. The input and output devices can each transmit messages to the serial communication bus for receipt by other devices.
U.S. Pat. No. 7,267,068 discloses a marine vessel that is maneuvered by independently rotating first and second marine propulsion devices about their respective steering axes in response to commands received from a manually operable control device, such as a joystick. The marine propulsion devices are aligned with their thrust vectors intersecting at a point on a centerline of the marine vessel and, when no rotational movement is commanded, at the center of gravity of the marine vessel. Internal combustion engines are provided to drive the marine propulsion devices. The steering axes of the two marine propulsion devices are generally vertical and parallel to each other. The two steering axes extend through a bottom surface of the hull of the marine vessel.
U.S. Pat. No. 7,305,928 discloses a vessel positioning system that maneuvers a marine vessel in such a way that the vessel maintains its global position and heading in accordance with a desired position and heading selected by the operator of the marine vessel. When used in conjunction with a joystick, the operator of the marine vessel can place the system in a station keeping enabled mode and the system then maintains the desired position obtained upon the initial change in the joystick from an active mode to an inactive mode. In this way, the operator can selectively maneuver the marine vessel manually and, when the joystick is released, the vessel will maintain the position in which it was at the instant the operator stopped maneuvering it with the joystick.
U.S. Patent Application Publication No. 2017/0253314 discloses a system for maintaining a marine vessel in a body of water at a selected position and orientation, including a global positioning system that determines a global position and heading of the vessel and a proximity sensor that determines a relative position and bearing of the vessel with respect to an object near the vessel. A controller operable in a station keeping mode is in signal communication with the GPS and the proximity sensor. The controller chooses between using global position and heading data from the GPS and relative position and bearing data from the proximity sensor to determine if the vessel has moved from the selected position and orientation. The controller calculates thrust commands required to return the vessel to the selected position and orientation and outputs the thrust commands to a marine propulsion system, which uses the thrust commands to reposition the vessel.
This Summary is provided to introduce a selection of concepts that are further described below in the Detailed Description. This Summary is not intended to identify key or essential features of the claimed subject matter, nor is it intended to be used as an aid in limiting the scope of the claimed subject matter.
One embodiment of a method for controlling low-speed propulsion of a marine vessel powered by a marine propulsion system having a plurality of propulsion devices includes receiving a signal indicating a position of a manually operable input device movable to indicate desired vessel movement within three degrees of freedom, and associating the position of the manually operable input device with a desired inertial velocity of the marine vessel. A steering position command and an engine command are then determined for each of the plurality of propulsion devices based on the desired inertial velocity and the propulsion system is controlled accordingly. An actual velocity of the marine vessel is measured and a difference between the desired inertial velocity and the actual velocity is determined, where the difference is used as feedback in subsequent steering position command and engine command determinations.
Another embodiment of a method for controlling low-speed propulsion of a marine vessel powered by a marine propulsion system having a plurality of propulsion devices includes storing a vessel dynamics model in a memory of a controller, the vessel dynamics model representing an approximation of vessel dynamics for the marine vessel and, with the controller, receiving a signal indicating a position of a manually operable input device movable to indicate desired vessel movement within three degrees of freedom, and determining a desired inertial velocity of the marine vessel based on the position of the manually operable input device. The vessel dynamics model is utilized to calculate a surge command, a sway command, and/or a yaw command based on the desired inertial velocity. A steering position command and an engine command are determined for each of the plurality of propulsion devices based on the surge command, the sway command, and/or the yaw command, and each of the plurality of propulsion devices are automatically controlled based on the steering position command and the engine command for the respective propulsion device.
Various other features, objects, and advantages of the invention will be made apparent from the following description taken together with the drawings.
The present disclosure is described with reference to the following Figures.
Current user input control systems for controlling low-speed propulsion of a marine vessel, such as systems employing joystick controls, utilize a “feed-forward” only software control strategy where the user inputs, such as via the joystick, produce a calibrated set of engine commands. This set of engine commands is developed and calibrated via a laborious process to generate a vessel response that is specific to the marine vessel on which it is installed. This vessel-specific calibration must be developed by an expert through a combination of physical measurements of a marine vessel, on-water testing and data collection for that marine vessel, and post-test analysis. This calibration is typically implemented as a map correlating engine and steering commands to joystick position, and such a map is distributed as part of a software load that is tailored to a specific vessel configuration—e.g., a specific combination of hull design and dimensions, engine size, number of engines, engine placement, and propeller type.
Though this customized joystick configuration process produces a joystick control system with desirable handling characteristics, the inventors have recognized that the calibration process for each vessel configuration is too labor intensive. Moreover, the inventors have recognized that current systems involving vessel configuration-specific calibrations require tracking and maintaining hundreds of unique configurations, which is burdensome and expensive. Additionally, the inventors have recognized that the calibration process, even when performed by expert technicians, introduces performance variation in the final product across a fleet of vessel configurations because human factors and personal preferences of the experts come in to play in creating and fine-tuning the calibration.
Upon recognition of the foregoing problems and challenges in the relevant field, the inventors developed the disclosed system that eliminates the need for vessel configuration-specific calibration and enables the provision of a unified control scheme across a fleet of marine vessels. The system and method correlate joystick commands with inertial velocity values for the marine vessel, and such inertial velocity values can be utilized for marine vessels having a wide variety of configurations. In one embodiment, the control system is a model-based system. A command model computes a desired inertial velocity based on joystick position, where the same command model can be used for multiple different vessel configurations. The command model maps user inputs, such as joystick position, to desired inertial velocity values, such as a desired surge velocity, a desired sway velocity, and/or a desired yaw velocity. The desired inertial velocity is then used to determine a steering position and an engine command for each of the plurality of propulsion devices.
In one embodiment, a second model is utilized to approximate the vessel dynamics for the particular marine vessel—e.g., a vessel dynamics model may be created and stored within the controller that approximates the vessel dynamics based on characteristics of the marine vessel, such as length, beam, and weight thereof. The vessel dynamics model is used to solve for a surge command, a sway command, and/or a yaw command that achieve the desired inertial velocity for the particular marine vessel.
By utilizing this model-based control architecture, the need for on-water testing and vessel personality development is eliminated while preserving highly accurate control systems providing desirable handling characteristics and a vessel response that is intuitive to the user. Customization of the disclosed system and method for a particular vessel configuration requires only physical traits of the vessel, such as engine location and a few size traits of the hull. These are known traits of the marine vessel, and thus the model customization can be done offline and requires only minimal expertise and time.
In certain embodiments, the vessel dynamics model may be incorporated in a closed-loop control system where the output of the vessel dynamics model, namely the surge command, sway command, and/or yaw command are compared to control feedback from one or more inertial and/or navigation sensors, wherein the steering position and engine command are calculated based on the output of the vessel dynamics model as well as feedback from the sensors. Thereby, closed-loop control is effectuated over vessel translation and yaw velocities, which are computed using a combination of sensors, such as accelerometers, gyros, magnetometers, and a global positioning system (GPS). In other embodiments, the model-based control may be implemented in a feed-forward control strategy, where outputs from the vessel dynamics model are utilized to determine a steering position command and engine command for each of the plurality of propulsion devices. Moreover, the feed-forward strategy can be utilized as a backup control strategy in the event of a failure of one or more of the feedback sensors, thereby providing a default control state that remains very drivable and safe for a user. The engine and steering commands generated based on the output of the vessel dynamics model will result in an actual vessel velocity that is very close to the desired inertial velocity, and the feedback is only used to correct for uncertainties in the model and for wind and current.
The vessel 10 also includes various control elements that comprise part of the marine propulsion system 20. The marine propulsion system 20 comprises an operation console 22 in signal communication, for example via a CAN bus as described in U.S. Pat. No. 6,273,771, with a controller 24, such as for example a command control module (CCM), and with propulsion control modules (PCM) 26a, 26b associated with the respective propulsion devices 12a, 12b. Each of the controller 24 and the PCMs 26a, 26b may include a memory 25a and a programmable processor 25b. As is conventional, the processor 25b is communicatively connected to the memory 25a comprising a computer-readable medium that includes volatile or nonvolatile memory upon which computer readable code is stored. The processor 25b can access the computer readable code and upon executing the code carries out functions as described hereinbelow.
In other examples of the marine propulsion system 20, only one control module is provided for the system rather than having a CCM and separate PCMs. In other examples, one CCM is provided for each propulsion device, and/or additional control modules are provided for controlling engine speed and functions separately from steering and trim of the propulsion devices. For example, the PCMs 26a, 26b may control the engines 14a, 14b and transmissions 16a, 16b of the propulsion devices 12a, 12b, while additional thrust vector modules (TVMs) may control their orientation. In other examples of the marine propulsion system 20, the vessel control elements are connected via wireless communication rather than by a serially wired CAN bus. It should be noted that the dashed lines shown in
The operation console 22 includes a number of user input devices, such as a keypad 28, a joystick 30, a steering wheel 32, and one or more throttle/shift levers 34. Each of these devices inputs commands to the controller 24. The controller 24, in turn, communicates with the first and second propulsion devices 12a, 12b by communicating with the PCMs 26a, 26b. The controller 24 also receives information from an inertial measurement unit (IMU) 36. The IMU 36 may comprise a portion of a global positioning system (GPS) 38 which, in the example shown, also comprises a GPS receiver 40 located at a pre-selected fixed position on the vessel 10, which provides information related to the global position of the vessel 10. In other embodiments, the IMU 36 may comprise part of an inertial navigation system (INS). Signals from the GPS receiver 40 (or INS) and/or the IMU 36 are provided to the controller 24. In one example, the IMU 36 is an inertial navigation system (INS) consists of a MEMS gyroscope, or a MEMS angular rate sensor, a MEMS accelerometer, and a magnetometer, which are used together to calculate velocity and heading of the marine vessel relative to magnetic north. In other embodiments, the motion and angular position (including pitch and roll) may be sensed by a different INS configuration or an attitude heading reference system (AHRS) that provides 3D orientation of the marine vessel 10 by integrating gyroscopic measurements, accelerometer data, and magnetometer data. Signals from the GPS receiver 40 and/or the IMU (or INS) 36 are provided to the controller 24.
The steering wheel 32 and the throttle/shift levers 34 function in a conventional manner, such that rotation of the steering wheel 32, for example, activates a transducer that provides a signal to the controller 24 regarding a desired direction of the vessel 10. The controller 24, in turn, sends signals to the PCMs 26a, 26b (and/or TVMs or additional modules if provided), which in turn activate steering actuators to achieve desired orientations of the propulsion devices 12a, 12b. The propulsion devices 12a, 12b are independently steerable about their steering axes. The throttle/shift levers 34 send signals to the controller 24 regarding the desired gear (forward, reverse, or neutral) of the transmissions 16a, 16b and the desired rotational speed of the engines 14a, 14b of the propulsion devices 12a, 12b. The controller 24, in turn, sends signals to the PCMs 26a, 26b, which in turn activate electromechanical actuators in the transmissions 16a, 16b and engines 14a, 14b for shift and throttle, respectively.
A manually operable input device, such as the joystick 30, can also be used to provide signals to the controller 24. The joystick 30 can be used to allow the operator of the vessel 10 to manually maneuver the vessel 10, such as to achieve translation or rotation of the vessel 10, as will be described below. It should be understood that in alterative examples, the various components 28, 30, 32, 34 may communicate directly with the PCMs 26a, 26b or may communicate with one or more central control modules. Referring to
In a joysticking mode, the user may operate the joystick 30 to command the rotational and/or translational movements described hereinabove with respect to
With continued reference to
In
First and second steering axes, 13a and 13b, are illustrated for the first and second propulsion devices 12a, 12b. The first and second propulsion devices 12a, 12b are rotatable about the first and second steering axes, 13a and 13b, respectively. The ranges of rotation of the first and second propulsion devices 12a, 12b may be symmetrical with respect to a centerline 62 of the vessel 10. The positioning method of the present disclosure rotates the first and second propulsion devices 12a, 12b about their respective steering axes 13a, 13b, adjusts their operation in forward or reverse gear, and adjusts the magnitude of their thrusts T1, T2 (for example, by adjusting engine speed and/or propeller pitch or transmission slip) in an efficient manner that allows rapid and accurate maneuvering of the vessel 10. The rotation, gear, and thrust magnitude of one propulsion device 12a can be varied independently of the rotation, gear, and thrust magnitude of the other propulsion device 12b.
As illustrated in
With continued reference to
The thrust vectors T1, T2 each resolve into vector components in both the forward/reverse and left/right directions. The vector components, if equal in absolute magnitude to each other, may either cancel each other or be additive. If unequal in absolute magnitude, they may partially offset each other or be additive; however, a resultant force will exist in some linear direction. For purposes of explanation,
FX=T1(sin(θ))+T2(sin(θ)) (1)
FY=T1(cos(θ))−T2(cos(θ)) (2)
Note that in the example of
Turning to
If, on the other hand, it is desired that the moment 70 be the only force on the vessel 10, with no lateral movement in the forward/reverse or left/right directions, alternative first and second thrust vectors, represented by T1′ and T2′ in
With reference to
It should be noted that the steering angles of the propulsion devices 12a, 12b need not be the same. For example, the first propulsion device 12a can be steered to angle θ1 with respect to the centerline 62, while the second propulsion device 12b can be steered to angle θ2. When an input to the joystick 30 is made, the controller 24 will determine the net thrust and the net moment desired of the marine propulsion system 20. It can be seen, therefore, that T1, T2, θ1, and θ2 can thereafter be calculated by the controller 24 using the geometric relationships described hereinabove according to the following equations:
FX=T1(sin(θ1))+T2(sin(θ2)) (1)
FY=T1(cos(θ1))−T2(cos(θ2)) (2)
MCW=(W/2)(T1(cos(θ1)))+(W/2)(T2(cos(θ2))) (3)
MCCW=L(T1(sin(θ1)))+L(T2(sin(θ2))) (4)
MT=MCW−MCCW (5)
where FX and FY are the vector components of the known target linear thrust, MT is the known total target moment (including clockwise moment MCW and counterclockwise moment MCCW) about the preselected point, and L and W/2 are also known as described above. The controller 24 then solves for the four unknowns (T1, T2, θ1, and θ2) using the four equations, thereby determining the steering angles, shift positions, and thrust magnitudes of each propulsion device 12a, 12b that will achieve the desired movement of the vessel 10. Note that equations 1-5 are particular to the thrust arrangements shown in
The above principles regarding resolution of the thrust vectors T1, T2 into X components and Y components in order to achieve lateral movement, rotational movement, or a combination of the two are the basis of a maneuvering algorithm of the present method. This maneuvering algorithm used in response to commands from the joystick 30 while in joysticking mode.
In current systems, the joystick 30 position input is associated with a target linear thrust and a target moment about a preselected point based on a map stored in memory associating joystick position with target thrust and target moment. As described above, creation of this vessel-specific map requires extensive calibration procedures to be performed by an expert, which is a labor and resource intensive process. Furthermore, this system requires tracking and maintenance of hundreds or even thousands of vessel-specific maps.
The disclosed system and method alleviate such problems and challenges. The disclosed system and method associate user input, such as a sensed joystick position, with a desired inertial velocity of the marine vessel. The desired inertial velocity can be uniform across all or many vessel configurations, and thus one map or set of maps associating joystick position with desired inertial velocity values can be installed across various marine vessel configurations. The disclosed model-based control strategy is based on extensive vessel dynamics and handling qualities research conducted by the inventors and utilizes a generic vessel model developed and tested by the inventors to calculate feed-forward commands based on the desired inertial velocity value and in a way that can be easily applied to a wide range of marine vessel configurations.
Signals from the joystick 30 (e.g., a percent deflection +/−100% in each of the axis directions) are provided to the command model 72, which computes the desired inertial velocity based on the joystick position. The inertial velocity may include translational velocity values and/or yaw velocity values. Command module 72 takes raw joystick position information and generates a desired inertial velocity, such as a desired surge, sway, and yaw response of the marine vessel. This architecture allows for easy setup and configuration of how fast the vessel will translate and/or turn in response to a user input. In certain embodiments, the command model may be tunable by a user to adjust how aggressively the propulsion system 20 will respond to user inputs. For example, secondary inputs may be provided on the operation console 22, such as button inputs or inputs on the keypad 28 or joystick 30, may allow a user to input preference as to how the vessel will respond to the joystick inputs, such as to increase or decrease the desired inertial velocity values associated with the joystick positions and/or to select stored profiles or maps associated with user input values to desired velocity values. For example, the user inputs may allow a user to instruct an increase or decrease in the aggressiveness of the velocity response and/or to increase or decrease a top speed that the full joystick position (e.g. pushing the joystick to its maximum outer position) effectuates.
For example, the command model 72 may be a map of positions of the joystick to inertial velocity values, such as associating each possible position of the joystick to a target surge velocity, a target sway velocity, and/or a target yaw velocity. For example, the neutral, or centered, position in the joystick is associated with a zero inertial velocity. In certain examples where the control system is a closed-loop system, feedback control may be utilized to maintain the vessel at its current position, similar to station keeping functionality. Accordingly, when the position of the joystick is equal to the neutral, or centered, position, the steering command and the engine command are determined so as to maintain the marine vessel at its current position, including to counteract momentum of the marine vessel and/or the effects of any wind or current. Thus, during joystick mode the marine vessel 10 only moves in response to and in accordance with user input via the joystick.
Output from the command model 72, such as desired surge, sway, and yaw velocities, are passed through a rate limiter 74. This enforces a maximum acceleration of the marine vessel, for user comfort and safety, and accounts for fault modes, such as limits on propulsion or steering commands due to faults in the engine or steering system.
The output of the rate limiter 74 is provided to the vessel dynamics model 76, which in the depicted embodiment is an inverse plant model. The same plant model may be used for designing the feedback controller to solve for the feedback gains. The plant model is derived from a combination of on-water testing-based parameter identification and computational fluid dynamics. Based thereon, a generic low-speed vessel model is developed, which is a non-dimensional model covering a range of vessel hull characteristics and factors that affect vessel dynamics. For example, the model may be developed by utilizing computational fluid dynamics to analyze parametric study data on a wide range of vessel hulls that cover the range of vessel hull dimensions for which the control system will be implemented. Plant modeling techniques may then be utilized to generate a mathematical model, a generic low-speed vessel model, of the vessel dynamics at low speeds for the range of vessel hulls. For example, the model may represent the vessel dynamics for each of the exemplary set of vessel hulls operating at a range of speeds achievable during joysticking within a ten percent accuracy requirement as compared to the parametric study data. The model can be non-dimensionalized to create a generic low-speed vessel model where vessel size and weight characteristics are represented as a set of coefficients that can be inputted to create a vessel dynamics model for any vessel hull in the range covered by the model. For example, the set of coefficients for a vessel hull may include a vessel length, a vessel beam, and a vessel weight. Additionally, this generic low-speed vessel model may include propulsion data, such as configured such that propulsion device size, type, and location can be inputted (in addition to the hull size and weight characteristics) as part of generating the vessel dynamics model 76 for a marine vessel.
In one example, the generic low-speed vessel model receives the coefficients for the vessel hull and yields three equations for that marine vessel configuration comparing vessel speed, vessel acceleration, and joystick demand for each of the surge, sway, and yaw axes of motion:
Added_Mass_Deriv*acceleration=Damping_Deriv*velocity+Control_Power_Deriv*joystick_pct
These equations are inverted and utilized as the vessel dynamics model 76—e.g., an inverse plant model—to solve for commands, such as joystick percent commands for the marine vessel that effectuate the desired inertial velocity. For example, the inverse plant model 76 may generate a surge command, a sway command, and a yaw command based on the desired inertial velocity values provided by the command model 72 (filtered by the rate limiter 74). Based on the logic above, the vessel dynamics model 76 may be configured to calculate the joystick percent (i.e., command percent) required to achieve the desired inertial velocity according to the following:
Joystick_pct=(Added_Mass_Deriv*acceleration−Damping_Deriv*velocity)/Control_Power_Deriv
where the velocity is the value outputted by the command model 72, and the acceleration is the derivative of the command model output.
In a feed-forward command regime, the output of the vessel dynamics model 76 can be utilized to control the propulsion devices—i.e., inputted to the affine control mixer 86 to generate engine and steering commands. Accordingly, the command model 72, rate limiter 74, vessel dynamics model (e.g., inverse plant model) 76, and affine control mixer 86 can be utilized, without the feedback portion of the system depicted in
In the depicted closed-loop control strategy, feedback control is provided by a feedback controller 78, which receives information about the actual vessel velocity from one or more sensors and/or navigation systems on the marine vessel. For example, the feedback controller 78 may receive information about the inertial movement of the marine vessel from one or more sensors 39, such as from the IMU 36. The output of the one or more sensors 39 is interpreted by a navigation system 41, such as a GPS 38 or an inertial navigation system. The navigation system 41 provides an actual inertial velocity (e.g. translational velocity and yaw velocity) that can be compared to the output of the command model 72 at the feedback controller 78, and such information can be utilized to refine the command values so as to more accurately effectuate the desired inertial velocity by accounting for inaccuracies in the inverse plant model and disturbances in the environment (e.g., wind and waves). The feedback controller 78 may be designed utilizing the vessel dynamics model in order to provide appropriate feedback gains based on the dynamics of the particular vessel configuration.
The output of the feedback controller 78 and the inverse plant model 76 are combined at summing point 80. Referring to the inverse plant model example described above calculating joystick percent based on desired inertial velocity, the feedback controller 78 would likewise provide output in terms of a joystick percent, and such output is added to the joystick percent value outputted by the vessel dynamics model 76. The summed output is then compared to the joystick position information at summing point 81 (e.g., to the percent deflection value). The summed output is again subject to a limiter 82, which limits the feedback authority in order to limit authority of the feedback controller and account for fault modes. The output of the limiter 82 is summed with the joystick values at summing point 83. That summed value is provided to the affine control mixer 86, which generates a total X direction command and a total Y-direction command, e.g., the X and Y components of the total thrust command for each propulsion device. From there, engine, steering, and shift commands for the propulsion devices are generated.
The affine mixing strategy implemented at mixing module 86 accomplishes a blending and smoothing of surge, sway, and yaw commands. An exemplary embodiment of affine mixing is described in more detail below, which utilizes the number of installed propulsion devices, the physical locations of those propulsion devices, and a distance of those physical locations to the estimated COR 60 of the marine vessel 10. The affine mixing strategy generates a total thrust command, including a total X direction thrust and a total Y direction thrust, from which an engine command, a steering position command, and a shift command can be generated for each propulsion device 12 in the propulsion system 20 (e.g. see
For each propulsion device, a two-dimensional (X, Y) unit normal vector between the location of the propulsion devices 12a, 12b and the COR 60. The unit normal vectors are represented in
The affine mixing strategy may be accomplished according to the following set of equations:
where Runorm is the unit normal vector for each propulsion device 12a, 12b provided by equation 6, the total X thrust command and total Y thrust command for each propulsion device is provided by equation 7, the engine, shift, and steering commands are calculated for each propulsion device according to equations 8-10. The total X direction and Y direction commands calculated for each propulsion device according to equation 7 utilize the conversion matrix based on the unit normal vector multiplied by the surge, sway, and yaw commands. This is schematically illustrated at
This written description uses examples to disclose the invention, including the best mode, and also to enable any person skilled in the art to make and use the invention. Certain terms have been used for brevity, clarity, and understanding. No unnecessary limitations are to be inferred therefrom beyond the requirement of the prior art because such terms are used for descriptive purposes only and are intended to be broadly construed. The patentable scope of the invention is defined by the claims, and may include other examples that occur to those skilled in the art. Such other examples are intended to be within the scope of the claims if they have features or structural elements that do not differ from the literal language of the claims, or if they include equivalent features or structural elements with insubstantial differences from the literal languages of the claims.
This patent application is a continuation of U.S. patent application Ser. No. 16/178,261, filed on Nov. 1, 2018, which is incorporated herein by reference in its entirety.
Number | Name | Date | Kind |
---|---|---|---|
3688252 | Thompson | Aug 1972 | A |
3715571 | Braddon | Feb 1973 | A |
3771483 | Spencer | Nov 1973 | A |
4253149 | Cunningham et al. | Feb 1981 | A |
4428052 | Robinson et al. | Jan 1984 | A |
4513378 | Antkowiak | Apr 1985 | A |
4939661 | Barker et al. | Jul 1990 | A |
4975709 | Koike | Dec 1990 | A |
5172324 | Knight | Dec 1992 | A |
5202835 | Knight | Apr 1993 | A |
5331558 | Hossfield et al. | Jul 1994 | A |
5362263 | Petty | Nov 1994 | A |
5386368 | Knight | Jan 1995 | A |
5390125 | Sennott et al. | Feb 1995 | A |
5491636 | Robertson et al. | Feb 1996 | A |
5515287 | Hakoyama et al. | May 1996 | A |
5736962 | Tendler | Apr 1998 | A |
5884213 | Carlson | Mar 1999 | A |
6059226 | Cotton et al. | May 2000 | A |
6092007 | Cotton et al. | Jul 2000 | A |
6230642 | McKenney et al. | May 2001 | B1 |
6234100 | Fadeley et al. | May 2001 | B1 |
6308651 | McKenney et al. | Oct 2001 | B2 |
6377889 | Soest | Apr 2002 | B1 |
6446003 | Green et al. | Sep 2002 | B1 |
6485341 | Layni et al. | Nov 2002 | B1 |
6604479 | McKenney et al. | Aug 2003 | B2 |
6678589 | Robertson et al. | Jan 2004 | B2 |
6705907 | Hedlund | Mar 2004 | B1 |
6995527 | Depasqua | Feb 2006 | B2 |
7268703 | Kabel et al. | Sep 2007 | B1 |
7366593 | Fujimoto et al. | Apr 2008 | B2 |
7398742 | Gonring | Jul 2008 | B1 |
7416458 | Suemori et al. | Aug 2008 | B2 |
7467595 | Lanyi et al. | Dec 2008 | B1 |
7476134 | Fell et al. | Jan 2009 | B1 |
7538511 | Samek | May 2009 | B2 |
7577526 | Kim et al. | Aug 2009 | B2 |
7727036 | Poorman et al. | Jun 2010 | B1 |
7813844 | Gensler et al. | Oct 2010 | B2 |
7876430 | Montgomery | Jan 2011 | B2 |
8050630 | Arbuckle | Nov 2011 | B1 |
8082100 | Grace et al. | Dec 2011 | B2 |
8145370 | Borrett | Mar 2012 | B2 |
8145371 | Rae et al. | Mar 2012 | B2 |
8155811 | Noffsinger et al. | Apr 2012 | B2 |
8265812 | Pease | Sep 2012 | B2 |
8417399 | Arbuckle et al. | Apr 2013 | B2 |
8478464 | Arbuckle et al. | Jul 2013 | B2 |
8480445 | Morvillo | Jul 2013 | B2 |
8510028 | Grace et al. | Aug 2013 | B2 |
8515660 | Grace et al. | Aug 2013 | B2 |
8515661 | Grace et al. | Aug 2013 | B2 |
8527192 | Grace et al. | Sep 2013 | B2 |
8543324 | Grace et al. | Sep 2013 | B2 |
8645012 | Salmon et al. | Feb 2014 | B2 |
8694248 | Arbuckle et al. | Apr 2014 | B1 |
8761976 | Salmon et al. | Jun 2014 | B2 |
8797141 | Best et al. | Aug 2014 | B2 |
8831868 | Grace et al. | Sep 2014 | B2 |
9039468 | Arbuckle et al. | May 2015 | B1 |
9039469 | Calamia et al. | May 2015 | B1 |
9132900 | Salmon et al. | Sep 2015 | B2 |
9162743 | Grace et al. | Oct 2015 | B1 |
9176215 | Nikitin et al. | Nov 2015 | B2 |
9183711 | Fiorini et al. | Nov 2015 | B2 |
9195234 | Stephens | Nov 2015 | B2 |
9248898 | Kirchhoff | Feb 2016 | B1 |
9355463 | Arambel et al. | May 2016 | B1 |
9359057 | Andrasko et al. | Jun 2016 | B1 |
9377780 | Arbuckle et al. | Jun 2016 | B1 |
9615006 | Terre et al. | Apr 2017 | B2 |
9650119 | Morikami et al. | May 2017 | B2 |
9694885 | Combee | Jul 2017 | B2 |
9729802 | Frank et al. | Aug 2017 | B2 |
9733645 | Andrasko et al. | Aug 2017 | B1 |
9734583 | Walker et al. | Aug 2017 | B2 |
9996083 | Vojak | Jan 2018 | B2 |
9904293 | Heap et al. | Feb 2018 | B1 |
9908605 | Hayashi et al. | Mar 2018 | B2 |
9927520 | Ward et al. | Mar 2018 | B1 |
9988134 | Gable et al. | Jun 2018 | B1 |
10037701 | Harnett | Jul 2018 | B2 |
10048690 | Hilbert et al. | Aug 2018 | B1 |
10055648 | Grigsby et al. | Aug 2018 | B1 |
10106238 | Sidki et al. | Oct 2018 | B2 |
10191153 | Gatland | Jan 2019 | B2 |
10191490 | Akuzawa et al. | Jan 2019 | B2 |
10272977 | Hashizume et al. | Apr 2019 | B2 |
10281917 | Tyers | May 2019 | B2 |
10296014 | Ito et al. | May 2019 | B2 |
10336427 | Ichikawa | Jul 2019 | B1 |
10338800 | Rivers et al. | Jul 2019 | B2 |
10429845 | Arbuckle et al. | Oct 2019 | B2 |
10431099 | Stewart et al. | Oct 2019 | B2 |
10444349 | Gatland | Oct 2019 | B2 |
10507899 | Imamura | Dec 2019 | B2 |
10661872 | Ito | May 2020 | B1 |
10671073 | Arbuckle et al. | Jun 2020 | B2 |
10746552 | Hashizume et al. | Aug 2020 | B2 |
20030137445 | Van Rees et al. | Jul 2003 | A1 |
20040221787 | McKenney et al. | Nov 2004 | A1 |
20050075016 | Bertetti et al. | Apr 2005 | A1 |
20050170713 | Okuyama | Aug 2005 | A1 |
20050263058 | Suemori | Dec 2005 | A1 |
20060058929 | Fossen et al. | Mar 2006 | A1 |
20060089794 | Despasqua | Apr 2006 | A1 |
20070032923 | Mossman et al. | Feb 2007 | A1 |
20070089660 | Bradley et al. | Apr 2007 | A1 |
20070093147 | Mizutani | Apr 2007 | A1 |
20070178779 | Takada et al. | Aug 2007 | A1 |
20070203623 | Saunders et al. | Aug 2007 | A1 |
20080119094 | Mizutani | May 2008 | A1 |
20090037040 | Salmon et al. | Feb 2009 | A1 |
20100076683 | Chou | Mar 2010 | A1 |
20100191397 | Nose | Jul 2010 | A1 |
20110153125 | Arbuckle et al. | Jun 2011 | A1 |
20110172858 | Gustin | Jul 2011 | A1 |
20120072059 | Glaeser | Mar 2012 | A1 |
20120248259 | Page et al. | Oct 2012 | A1 |
20130297104 | Tyers et al. | Nov 2013 | A1 |
20140316657 | Johnson et al. | Oct 2014 | A1 |
20150009325 | Kardashov | Jan 2015 | A1 |
20150032305 | Lindeborg | Jan 2015 | A1 |
20150089427 | Akuzawa | Mar 2015 | A1 |
20150134146 | Pack et al. | May 2015 | A1 |
20150172545 | Szabo et al. | Jun 2015 | A1 |
20150276923 | Song et al. | Oct 2015 | A1 |
20150288891 | Johansson et al. | Oct 2015 | A1 |
20150294660 | Stokes et al. | Oct 2015 | A1 |
20150346722 | Herz et al. | Dec 2015 | A1 |
20150375837 | Johnson et al. | Dec 2015 | A1 |
20150378361 | Walker et al. | Dec 2015 | A1 |
20160041039 | Olsson | Feb 2016 | A1 |
20160069681 | Johnson et al. | Mar 2016 | A1 |
20160125739 | Stewart et al. | May 2016 | A1 |
20160162145 | Rivers et al. | Jun 2016 | A1 |
20160187140 | Clarke et al. | Jun 2016 | A1 |
20160196653 | Grant et al. | Jul 2016 | A1 |
20160214534 | Richards et al. | Jul 2016 | A1 |
20160334794 | Johnson et al. | Jul 2016 | A1 |
20160370187 | Gatland et al. | Dec 2016 | A1 |
20170052029 | Ninomiya et al. | Feb 2017 | A1 |
20170059705 | Stokes et al. | Mar 2017 | A1 |
20170064238 | Kardashov | Mar 2017 | A1 |
20170090021 | Sayer et al. | Mar 2017 | A1 |
20170146642 | Stokes et al. | May 2017 | A1 |
20170167871 | Johnson et al. | Jun 2017 | A1 |
20170168159 | Gatland | Jun 2017 | A1 |
20170176586 | Johsnon et al. | Jun 2017 | A1 |
20170184414 | Johsnon et al. | Jun 2017 | A1 |
20170205829 | Tyers | Jul 2017 | A1 |
20170227639 | Stokes et al. | Aug 2017 | A1 |
20170243360 | Schulte | Aug 2017 | A1 |
20170253314 | Ward | Sep 2017 | A1 |
20170255201 | Arbuckle et al. | Sep 2017 | A1 |
20170277189 | Johnson et al. | Sep 2017 | A1 |
20170285134 | Stokes et al. | Oct 2017 | A1 |
20170300056 | Johnson et al. | Oct 2017 | A1 |
20170351259 | Tamura | Dec 2017 | A1 |
20170365175 | Harnett | Dec 2017 | A1 |
20180023954 | Rivers | Jan 2018 | A1 |
20180057132 | Ward et al. | Mar 2018 | A1 |
20180081054 | Rudzinsky et al. | Mar 2018 | A1 |
20180259338 | Stokes et al. | Sep 2018 | A1 |
20180259339 | Johnson et al. | Sep 2018 | A1 |
20180292529 | Hogasten | Oct 2018 | A1 |
20190092444 | Tamura | Mar 2019 | A1 |
20190098212 | Shain et al. | Mar 2019 | A1 |
20190106189 | Tamura | Apr 2019 | A1 |
20190112020 | Tamura | Apr 2019 | A1 |
20190112021 | Watanabe | Apr 2019 | A1 |
20190137618 | Hawker | May 2019 | A1 |
20190251356 | Rivers | Aug 2019 | A1 |
20190258258 | Tyers | Aug 2019 | A1 |
20190283855 | Nilsson | Sep 2019 | A1 |
20190299983 | Shalev-Shwartz et al. | Oct 2019 | A1 |
20190308712 | Akuzawa | Oct 2019 | A1 |
20190308713 | Akuzawa | Oct 2019 | A1 |
20190317504 | Akuzawa | Oct 2019 | A1 |
20200140052 | Derginer et al. | May 2020 | A1 |
20210070414 | Bondesson | Mar 2021 | A1 |
20210139123 | Osara | May 2021 | A1 |
20210163114 | Bondesson | Jun 2021 | A1 |
Number | Date | Country |
---|---|---|
2279165 | Jan 2001 | CA |
2282064 | Jan 2001 | CA |
906907 | Mar 1954 | DE |
112013004908 | Jun 2015 | DE |
0423901 | Apr 1991 | EP |
1775212 | Apr 2007 | EP |
1873052 | Jan 2008 | EP |
3182155 | Jun 2017 | EP |
1173442 | Dec 1969 | GB |
2180374 | Mar 1987 | GB |
S58061097 | Apr 1983 | JP |
H04101206 | Feb 1992 | JP |
H07223591 | Aug 1995 | JP |
2926533 | Jul 1997 | JP |
7-246998 | Oct 1999 | JP |
2007248336 | Sep 2007 | JP |
2009227035 | Oct 2009 | JP |
5042906 | Jul 2012 | JP |
5226355 | Jul 2013 | JP |
2016049903 | Apr 2016 | JP |
2017178242 | Oct 2017 | JP |
20140011245 | Jan 2014 | KR |
WO 1992005505 | Apr 1992 | WO |
WO 9305406 | Mar 1993 | WO |
WO 2006040785 | Apr 2006 | WO |
WO 2006058400 | Jun 2006 | WO |
WO 2006062416 | Jun 2006 | WO |
WO 2008066422 | Jun 2008 | WO |
WO 2008111249 | Aug 2008 | WO |
WO 2012010818 | Jan 2012 | WO |
2017095235 | Jun 2017 | WO |
WO2019011451 | Jul 2017 | WO |
2017168234 | Oct 2017 | WO |
WO 2017167905 | Oct 2017 | WO |
WO 2017168234 | Oct 2017 | WO |
2017205829 | Nov 2017 | WO |
WO 2018162933 | Sep 2018 | WO |
WO 2018183777 | Oct 2018 | WO |
WO 2018201097 | Nov 2018 | WO |
2018232377 | Dec 2018 | WO |
WO 2018232376 | Dec 2018 | WO |
WO 2018232377 | Dec 2018 | WO |
WO 2019011451 | Jan 2019 | WO |
WO 2019096401 | May 2019 | WO |
WO 2019126755 | Jun 2019 | WO |
WO 2019157400 | Aug 2019 | WO |
WO 2019201945 | Oct 2019 | WO |
Entry |
---|
Poorman et al., “Multilayer Control System and Method for Controlling Movement of a Marine Vessel”, Unpublished U.S. Appl. No. 11/965,583, filed Dec. 27, 2007. |
Mercury Marine, Axius Generation 2 Installation Manual, Jul. 2010, pp. 22-25. |
Mercury Marine, Joystick Piloting for Outboards Operation Manual, 2013, pp. 24-26. |
Mercury Marine, Zeus 3000 Series Pod Drive Models Operation Manual, 2013, pp. 49-52. |
Arbuckle et al., “System and Method for Controlling a Position of a Marine Vessel Near an Object,” Unpublished U.S. Appl. No. 15/818,233, filed Nov. 20, 2017. |
Arbuckle et al., “System and Method for Controlling a Position of a Marine Vessel Near an Object,” Unpublished U.S. Appl. No. 15/818,226, filed Nov. 20, 2017. |
Ward et al., “Methods for Controlling Movement of a Marine Vessel Near an Object,” Unpublished U.S. Appl. No. 15/986,395, filed May 22, 2018. |
Translation of rejection dated Mar. 3, 2020 in counterpart Japan Patent Application 2019-190603. |
Search Report dated Apr. 22, 2020 in counterpart European Patent Application 19205213.2. |
John Bayless, Adaptive Control of Joystick Steering in Recreational Boats, Marquette University, Aug. 2017, https://epublications.marquette.edu/cgi/viewcontent.cgi?article=1439&context=theses_open. |
Translation of reasons for rejection dated Nov. 9, 2021 in counterpart Japanese Patent Application 2020-151307. |
W. Xu et al., “Internet of Vehicles in Big Data Era.” in IEEE/CAA Journal of Automatica Sinica, vol. 5, No. 1, pp. 19-35, Jan. 2018, doi:10.1109/JAS.2017.7510736. (Year 2018). |
An Autonomous Solar-Powered Marine Robitic Ibservatory for Permanent Monitoring of Large Areas of Shallow Water by I. Gonzalez-Reolid et al.; Sensors 2018, 18(10), 3497; https://doi.org/10.3390/s18103497 (Year 2018). |
S. Reed and V.E. Schmidt, “Providing Nautical Chart Awareness to Autonomous Surface Vessel operations,” OCEANS 2016 MTS/IEEE Monterery, 2016, pp. 1-8, doi: 10.1109/OCEANS.2016.7761472 (Year 2016). |
Office Action in corresponding Canadian Patent Application No. 3,060,522, Methods and Systems for Controlling Low-Speed Propulsion of a Marine Vessel, CA Office Action dated Dec. 7, 2023, 4 pages. |
Number | Date | Country | |
---|---|---|---|
20210139126 A1 | May 2021 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 16178261 | Nov 2018 | US |
Child | 17155004 | US |