The present disclosure generally relates to propulsion control systems and methods for controlling propulsion of a marine vessel, and more specifically to propulsion control systems and methods that limit the velocity of the marine vessel in a direction of an object based on the proximity of that object.
The following U.S. Patents are each 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. 9,927,520 discloses a method of detecting a collision of the marine vessel, including sensing using distance sensors to determine whether an object is within a predefined distance of a marine vessel, and determining a direction of the object with respect to the marine vessel. The method further includes receiving a propulsion control input at a propulsion control input device, and determining whether execution of the propulsion control input will result in any portion of the marine vessel moving toward the object. A collision warning is then generated.
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.
U.S. Patent Application Publication No. 2018/0057132 discloses a method for controlling movement of a marine vessel near an object, including accepting a signal representing a desired movement of the marine vessel from a joystick. A sensor senses a shortest distance between the object and the marine vessel and a direction of the object with respect to the marine vessel. A controller compares the desired movement of the marine vessel with the shortest distance and the direction. Based on the comparison, the controller selects whether to command the marine propulsion system to generate thrust to achieve the desired movement, or alternatively whether to command the marine propulsion system to generate thrust to achieve a modified movement that ensures the marine vessel maintains at least a predetermined range from the object. The marine propulsion system then generates thrust to achieve the desired movement or the modified movement, as commanded.
U.S. Pat. No. 10,429,845 discloses a marine vessel is powered by a marine propulsion system and movable with respect to first, second, and third axes that are perpendicular to one another and define at least six degrees of freedom of potential vessel movement. A method for controlling a position of the marine vessel near a target location includes measuring a present location of the marine vessel, and based on the vessel's present location, determining if the marine vessel is within a predetermined range of the target location. The method includes determining marine vessel movements that are required to translate the marine vessel from the present location to the target location. In response to the marine vessel being within the predetermined range of the target location, the method includes automatically controlling the propulsion system to produce components of the required marine vessel movements one degree of freedom at a time during a given iteration of control.
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.
A propulsion control system on a marine vessel includes at least one propulsion device configured to propel the marine vessel and at least one proximity sensor system configured to generate proximity measurements describing a proximity of an object with respect to the marine vessel. The system further includes a controller configured to receive proximity measurements, access a preset buffer distance, and calculate a velocity limit in a direction of the object for the marine vessel based on the proximity measurements and the preset buffer distance so as to progressively decrease the velocity limit as the marine vessel approaches the object such that the marine vessel is maintained at least the preset buffer distance from the object.
A marine propulsion control method includes receiving proximity measurements measured by one or more proximity sensors on a marine vessel wherein the proximity measurements describe a proximity of an object. The control method further includes accessing a preset buffer distance and then calculating a velocity limit for the marine vessel in a direction of the object based on the proximity measurements and the preset buffer distance so as to progressively decrease the velocity limit as the marine vessel approaches the preset buffer distance from the object. The at least one propulsion device is then controlled such that a velocity of the marine vessel does not exceed the velocity limit in the direction of the object. In certain embodiments, the method may further include limiting user input authority over propulsion output in a direction of the object by at least one propulsion device to the velocity limit so as to maintain the marine vessel at least the buffer distance from the object. In certain embodiments, the velocity limit may include each of a positive x-direction velocity limit, a negative x-direction velocity limit, a positive y-direction velocity limit, and a negative y-direction velocity limit, and in certain embodiments may further include a positive yaw direction velocity limit and/or a negative yaw direction velocity limit.
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.
The vessel 10 also houses various control elements that comprise part of the propulsion control system 20. The 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 and a programmable processor. As is conventional, each controller 24, 26a, 26b includes a processor communicatively connected to a storage system comprising a computer-readable medium that includes volatile or nonvolatile memory upon which computer readable code and data is stored. The processor can access the computer readable code and, upon executing the code, carry out functions, such as the navigation control functions and/or the proximity sensing functions, as described in detail below.
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 control instructions to the first and second propulsion devices 12a, 12b by communicating with the PCMs 26a, 26b. 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 control input 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 lateral translation or rotation of the vessel 10.
The propulsion control system 20 also includes one or more proximity sensors 72, 74, 76, and 78. Although one proximity sensor is shown on each of the bow, stem, port and starboard sides of the vessel 10, fewer or more sensors could be provided at each location and/or provided at other locations, such as on the hardtop of the vessel 10. The proximity sensors 72-78 are distance and directional sensors. For example, the sensors could be radars, sonars, cameras, lasers (e.g. lidars or Leddars), Doppler direction finders, or other devices individually capable of determining both the distance and direction (at least approximately), i.e. the relative position of an object O with respect to the vessel 10, such as a dock, a seawall, a slip, another vessel, a large rock or tree, etc. The sensors 72-78 provide information regarding both a direction of the object with respect to the marine vessel 10 and a shortest distance between the object O and the vessel 10. Alternatively, separate sensors could be provided for sensing direction than are provided for sensing distance, or more than one type of distance/direction sensor can be provided at a single location on the vessel 10. The sensors 72-78 provide this distance and/or direction information to one or more controllers, such as to the sensor processor 70 and/or the CCM 24, such as by way of a dedicated bus connecting the sensors to a controller, a CAN bus, or wireless network transmissions, as described in more detail below.
Regarding the proximity sensors, 72, 74, 76, 78, note that different types of sensors may be used depending on the distance between the vessel 10 and the object O. For example, radar sensors may be used to detect objects at further distances. Once the vessel 10 comes within a particular distance of the object, lidar, ultrasonic, Leddar, or sonar sensors may instead be used. Camera sensors may be used, alone or in combination with any of the sensors mentioned above, in order to provide object proximity information to the CCM 24. Sensors are placed at positions on the vessel 10 so that they are at the correct height and facing direction to detect objects the vessel 10 is likely to encounter. Optimal sensor positions will vary depending on vessel size and configuration.
In
Autonomous and/or advanced operator assistance (i.e., semi-autonomous) controls for improved vessel handling qualities requires placement of multiple proximity sensors on the vessel 10. In general, these various types of proximity sensing devices (examples described above) are positioned to detect the presence of objects in the marine environment surrounding the marine vessel 10, such as a dock, swimmer, or other obstruction in the path of the vessel. Each sensor reports proximity relative to its own frame of reference—i.e. the distance from the sensor to the object as measured along the view angle of the sensor. Depending on the type of sensor, the application of use, boat size, hull shape, etc., multiple sensor types and sensor locations may be required to provide adequate proximity sensing around the marine vessel 10 for operation in all marine environments. To create a cohesive dataset that can be used for purposes of vessel control and vessel navigation, including autonomous vessel navigation and semi-autonomous control (such as automatic maneuver-limiting control), all of the data sources are preferably translated to a common reference frame. This requires precise knowledge of the location and orientation of each sensor relative to the common reference frame such that the data measured therefrom can be translated appropriately.
In the example of
Referencing the example in
The INS 60 receives orientation information from the main IMU 36 and may also receive information from a GPS receiver 40 comprising part of a global positioning system (GPS). The GPS receiver 40 is located at a pre-selected fixed position on the vessel 10, which provides information related to global position of the marine vessel 10. The main IMU 36 is also located at a known and fixed position with respect to the center of navigation determined for the marine vessel 10, such as the COR or COG.
In
The inventors have recognized unique problems presented by autonomous and semi-autonomous vessel control systems for operating in marine environments where marine vessels have additional degrees of freedom of movement compared to automotive applications—for example, they can effectuate only lateral and yaw movement without any forward or reverse movement (e.g., in a joysticking mode). Additionally, marine environments pose unique external environmental factors acting on the marine vessel, such as current, wind, waves, or the like. The present inventors have recognized that autonomous and semi-autonomous control systems for marine vessels need to be “aware” of relevant vessel acceleration limits to avoid colliding with obstacles. By knowing the acceleration limit, and by having an awareness of the distance range to obstacles, the control system can determine a maximum vessel velocity that can be realized where the control system has the ability to avoid colliding with known obstacles. The acceleration limit is the maximum acceleration a vessel can reach for both speeding up and slowing down, where maximum deceleration of a marine vessel is accomplished by effectuating a maximum acceleration in the opposite direction.
The inventors have recognized that the above-mentioned operational challenges posed by a marine environment can be effectively dealt with by establishing and maintaining a buffer distance around the marine vessel, where the control authority provided to a user is limited based on the buffer distance. For example, the propulsion control system may continuously calculate a maximum velocity, or velocity limit, for the marine vessel as it approaches an object O, and may limit a user's authority in controlling propulsion of the marine vessel 10 such that the propulsion system will not effectuate a thrust that will cause the marine vessel to travel toward the object at a velocity that is greater than the velocity limit. Thus, the propulsion system does not respond to, or carry out, commands that would cause the vessel to violate the buffer distance and venture too close to an object. In certain embodiments, the propulsion control system may be configured to automatically maintain a predetermined buffer distance between the marine vessel 10 and an object O, such as to automatically effectuate propulsion controls in order to force the marine vessel 10 away from a marine object O when the buffer zone is violated.
The autonomous or semi-autonomous control algorithms, such as effectuated by the controller 24 include velocity control software performing algorithms to calculate a maximum velocity for the marine vessel 10 as it approaches an object O and effectuates velocity limits accordingly. In one embodiment, the velocity limits may be calculated based on a known maximum acceleration for the marine vessel. The maximum acceleration for the marine vessel may be based on the maximum vessel capabilities, such as the maximum positive or negative acceleration that can be effectuated by the propulsion system on the marine vessel 10 in the relevant direction of travel. Alternatively or additionally, the maximum acceleration for the marine vessel 10 may be predetermined, such as based on handling, comfort, or safety metrics.
The velocity limit, then, may be calculated based on that known acceleration limit based on the distance of an object O from the marine vessel 10, accounting for the buffer distance 50. Given that acceleration is the derivative of velocity, the relationship between a maximum acceleration for the marine vessel and a maximum velocity with respect to a distance to an object can be provided according to the following:
In the embodiment represented at
As also illustrated in
In one embodiment, the proximity sensor system, e.g., the proximity sensors 72-78 in concert with the sensor processor 70, may be configured to generate a most important object (MIO) dataset identifying a select set of closest proximity measurements. For example, the MIO dataset may identify distances in each of the six directions that a boat has control authority—+/−X, +/−Y, and +/− yaw directions—thereby informing the navigation controller of navigation constraints based on the location of objects O around the marine vessel. For example, the closest proximity measurements may be identified based on one or more simplified two-dimensional vessel outlines representing the vessel hull. In such an embodiment, the MIO dataset may be calculated using the simplified boat profile and low-computation-load geometry to generate the MIO dataset identifying the closest proximity measurements in each possible direction of movement of the marine vessel 10. In one embodiment, the MIO dataset includes six values specifying one closest proximity measurement in each of the +/−X directions, +/−Y directions, and +/− yaw rotational directions.
In certain embodiments, the MIO dataset may always contain six values defining the closest proximity measurements in each of the aforementioned directions of movement. Thus, if no proximity measurements are detected in a particular direction, then a default large number may be provided which will be interpreted as non-limiting in the respective direction. To provide just one example, the default distance in the +/− yaw direction may be +/−180°. The navigation controller (e.g. controller 24) will interpret that default large rotation angle range to mean that the vessel can turn 180° without colliding with any object in the yaw direction. In other embodiments, the default large number may be greater than 180° (even as large as 360°), or may be smaller than 180°, such as 90°. The default large value in the X and Y directions may be a large, such as 10,000 meters, 50,000 meters, or more. In any such case, the default distance is large enough that the navigation controller will not limit any vessel movement based on the relevant default MIO data point. In other embodiments, the system 20 may be configured such that less than six numbers may be provided for the MIO dataset. Thus, where no proximity measurements 90 are detected in a particular direction, a null value or no value may be reported as part of the MIO dataset.
As illustrated in
In
In addition to the linearly-closest proximity measurements, rotationally-closest proximity measurements may also be calculated, which are the closest proximity measurements in the positive yaw direction and the negative yaw direction. In other words, the rotationally-closest proximity measurements include the point that will first touch the two-dimensional vessel outline 80 as it rotates about the point of navigation Pn in the positive yaw direction (clockwise) and the point that will first touch the two-dimensional vessel outline 80 as it rotates about Pn in the negative yaw direction (counterclockwise). The two rotationally-closest proximity measurements may be used to identify the yaw angles to which the marine vessel can rotate without colliding with an object. The smallest positive yaw angle and smallest negative yaw angle may be included in the MIO dataset so that the vessel navigation controller can properly limit the movement of the marine vessel to avoid collision.
For those proximity measurements 90 near the marine vessel 10, at least one yaw path will be calculated between the respective proximity measurement and one or more intersection points on the two-dimensional vessel outline 80. Referring to
Velocity limits are then calculated based on the MIO dataset providing the closest proximity measurements in each of the +/− X direction, +/− Y direction, and +/− yaw direction. For example, a velocity limit may be calculated for each point in the MIO dataset, thus resulting in continual calculation of a velocity limit in each of the +/− X directions, +/− Y directions, and +/− yaw directions.
In
In certain embodiments, the marine vessel may be configured to autonomously control the propulsion devices 12a, 12b to maintain at least the predetermined buffer distance 50 between the marine vessel 10 and an object O. Thus, where the buffer zone 51 is violated, the relevant controller executing velocity control software 25, the propulsion controller, may generate instructions to the propulsion devices 12a, 12b to move the marine vessel such that the buffer zone 51 is not violated. Where an object O, such as a dock Od or seawall, spans the length of the marine vessel 10, positive and negative yaw direction limits will come into play, where zero or negative yaw velocity limits in one or the other direction will result in propulsion control instructions that rotate the marine vessel so as not to violate the buffer zone 51.
The positive and negative yaw direction limits and control instructions to maintain the buffer zone 51 will result in the marine vessel self-aligning with the object O, such as a seawall or a dock. The propulsion controller, such as the central controller 24 executing velocity control software 25, will operate to rotate the marine vessel to align with the dock Od because a thrust instruction causing rotation of the vessel will be generated if a portion of the marine vessel becomes closer to the object Od and thus violates a portion of the buffer zone 51. In such an instance, the relevant yaw velocity limit 90+w, 90−w, will become negative, which will result in a thrust instruction to rotate the marine vessel to move the closest end of the vessel away from the object. Referring to
Similarly, where a marine vessel is being steered within a tight space, such as in a slip, the propulsion controller will operate to maintain the buffer distance on all sides of the marine vessel where the object O appears. Where the marine vessel is being positioned in a slip or a similar tight space, the buffer distance on two sides of the marine vessel must be violated. The controller 70 implementing the autonomous thrust instructions based on negative velocity limits, as described above, will act to center the marine vessel 10 within the objects appearing on either side. There, a negative thrust control will be generated based on objects on opposing sides of the marine vessel, such as both in the positive Y direction and the negative Y direction. Where the marine vessel ventures closer to the object on one side than the other, the negative thrust instruction in the opposite direction of the closer side will be greater than that generated in the opposite instruction. Thus, the thrust instructions generated from the negative velocity limits will only be executed if the marine vessel is closer to an object on one side than the other, and the velocity limits will tend to cancel each other out and cause the marine vessel to center within the objects on either side.
The velocity limit calculation is executed by one or more controllers with the control system 20. Referring again to
In other embodiments, the sensor processor 70 may store and execute the velocity control software 25 and thus may perform as the propulsion controller. In still other embodiments, a dedicated, special-purpose propulsion controller may be provided, such as a computing system storing and executing the velocity control software 25 and configured to receive proximity measurements, such as from the sensor processor 70, and to output velocity limits, which in various embodiments may be provided to the CCM 24 or to each PCM 26a, 26b. In still other embodiments, the proximity assessment functionality described herein as belonging to the sensor processor 70 and the velocity control functionality may both be performed by a single controller, such as the central controller 24.
Given the large amount of proximity data produced by the proximity sensors 72-78, the connection between the sensors 72-78 and the sensor processor 70 may be via a dedicated bus or network connection. This dedicated bus or network connection is separate from the vessel network in order to allow transmission of a large amount of proximity measurement data (and, in some embodiments, IMU data) to the sensor processor 70. Such massive data transmission may not be possible on a typical vessel network, such as a CAN bus or wireless network where multiple devices are communicating. The sensor processor 70 may be configured to communicate filtered proximity data on the vessel network, such as a CAN bus or wireless network, such as the MIO dataset. In still other embodiments, a dedicated communication link may be provided between the sensor processor 70 and the propulsion controller, such as the central controller 24.
The velocity limit is then calculated accordingly based on the distance values and the maximum acceleration set for the marine vessel. In the example, the linear maximum acceleration is 0.05 m/s2 and the angular acceleration limit is 0.01 rad/s2. The maximum linear acceleration is provided to each of blocks 107a-107d, which is the maximum acceleration in the relevant Cartesian direction. Similarly, the maximum angular acceleration is provided to each of blocks 107e and 107f, which is the maximum acceleration in the relevant positive or negative yaw direction. At block 107 the relevant distance range (e.g., Δr described above) is multiplied by the corresponding maximum acceleration. Before the absolute value is taken of the outputs at blocks 110a-110f, the sign of the relevant velocity calculation is determined at signum function blocks 109a-109f The square root of the absolute value is then calculated at blocks 111a-111f. The velocity limit is then determined at blocks 112a-1 if for each of the six directions, and all six velocity limit values 113a-113f are outputted at block 114.
The outputs of blocks 125b and 126b, which are the zero-bounded velocity limits, are provided to block 135, where they are implemented to limit the user control input 122. Depending on the sign of the user control input 122, either one of the positive velocity limit 125b or the negative velocity limit 126b is used at block 135 to limit the user input authority. The resulting velocity command based on the user control input 122 is outputted at block 136. In an embodiment where no autonomous control is implemented, only this zero-bounded portion of the control diagram may be implemented to deprive the user authority to move the marine vessel closer to the object O than is permitted.
In an embodiment where autonomous control is provided, the output of blocks 125a and 126a may be utilized to determine an autonomous velocity command. The outputs of blocks 125a and 125b or 126a and 126b are summed at blocks 127 and 128, respectively. If the buffer zone is not violated then the outputs of the summed blocks will cancel each other out and the output of the summation blocks 127 and 128 will be zero. If the output of the summation block 127, 128 is non-zero, then the buffer zone has been violated and a propulsion command is calculated to move the marine vessel away from the object. The absolute value of the respective summed output is determined at blocks 129 and 130, and a negative gain is applied at blocks 131 and 132. Blocks 133 and 134 are provided to implement a user override, where the autonomous propulsion control to actively maintain the buffer distance is suspended when the user-generated instruction 121 is active, or positive, by setting the output of blocks 133 and 134 to zero. Assuming that the user-generated instruction 121 is not active, the output of block 133 or 134 (whichever is nonzero) is provided to block 137, which reapplies the relevant sign. The resulting propulsion command is outputted at block 139.
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 application is a continuation of U.S. patent application Ser. No. 17/846,635, filed Jun. 22, 2022, which is a continuation of. Ser. No. 16/694,587, filed Nov. 25, 2019, which claims the benefit of priority to U.S. Provisional Application No. 62/780,028, filed on Dec. 14, 2018, the contents of which are all hereby incorporated by reference in entirety.
Number | Name | Date | Kind |
---|---|---|---|
6234100 | Fadeley et al. | May 2001 | B1 |
6273771 | Buckley et al. | Aug 2001 | B1 |
7267068 | Bradley et al. | Sep 2007 | B2 |
7725253 | Foxlin | May 2010 | B2 |
8195381 | Arvidsson | Jun 2012 | B2 |
8622778 | Tyers et al. | Jan 2014 | B2 |
9039469 | Calamia et al. | May 2015 | B1 |
9183711 | Fiorini et al. | Nov 2015 | B2 |
9355463 | Arambel et al. | May 2016 | B1 |
9615006 | Terre et al. | Apr 2017 | B2 |
9650119 | Morikami et al. | May 2017 | B2 |
9729802 | Frank et al. | Aug 2017 | B2 |
9734583 | Walker et al. | Aug 2017 | B2 |
9778657 | Tyers | Oct 2017 | B2 |
9878769 | Kinoshita et al. | Jan 2018 | B2 |
9996083 | Vojak | Jan 2018 | B2 |
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 |
10126748 | Akuzawa et al. | Nov 2018 | B2 |
10191153 | Gatland | Jan 2019 | B2 |
10191490 | Akuzawa et al. | Jan 2019 | B2 |
10431099 | Stewart et al. | Jan 2019 | B2 |
1027977 | Hashizume et al. | Apr 2019 | A1 |
10281917 | Tyers | May 2019 | B2 |
10338800 | Rivers et al. | Jul 2019 | B2 |
10429845 | Arbuckle et al. | Oct 2019 | B2 |
10444349 | Gatland | Oct 2019 | B2 |
10507899 | Imamura et al. | Dec 2019 | B2 |
10746552 | Hashizume et al. | Aug 2020 | B2 |
11373537 | Derginer | Jun 2022 | B2 |
11403955 | Derginer | Aug 2022 | B2 |
11804137 | Derginer | Oct 2023 | B1 |
11862026 | Derginer | Jan 2024 | B2 |
20030137445 | Van Rees et al. | Jul 2003 | A1 |
20050075016 | Bertetti et al. | Apr 2005 | A1 |
20060058929 | Fossen et al. | Mar 2006 | A1 |
20070089660 | Bradley et al. | Apr 2007 | A1 |
20110153125 | Arbuckle et al. | Jun 2011 | A1 |
20110172858 | Gustin et al. | Jul 2011 | 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 |
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 |
20160070265 | Liu 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 | Johnson et al. | Jun 2017 | A1 |
20170184414 | Johnson 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 |
20170277189 | Johnson et al. | Sep 2017 | A1 |
20170285134 | Stokes et al. | Oct 2017 | A1 |
20170300056 | Johnson et al. | Oct 2017 | A1 |
20170365175 | Harnett | Dec 2017 | A1 |
20170371348 | Mou | Dec 2017 | A1 |
20180023954 | Rivers | Jan 2018 | A1 |
20180050772 | Koyano et al. | Feb 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 |
20190098212 | Shain et al. | Mar 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 |
Number | Date | Country |
---|---|---|
2279165 | Jan 2001 | CA |
2282064 | Jan 2001 | CA |
110325823 | Oct 2019 | CN |
11 2013 004908 | Jun 2015 | DE |
1 775 212 | Apr 2007 | EP |
1873052 | Jan 2008 | EP |
3 182 155 | Jun 2017 | EP |
2824528 | Mar 2019 | EP |
7-246998 | Oct 1999 | JP |
2016049903 | Apr 2016 | JP |
2017178242 | Oct 2017 | JP |
20140011245 | Jan 2014 | KR |
9305406 | Mar 1993 | WO |
2006040785 | Apr 2006 | WO |
2006 062416 | Jun 2006 | WO |
2008 066422 | Jun 2008 | WO |
2012010818 | Jan 2012 | WO |
2017 095235 | Jun 2017 | WO |
2017167905 | Oct 2017 | WO |
2017168234 | Oct 2017 | WO |
2017205829 | Nov 2017 | WO |
2018162933 | Sep 2018 | WO |
2018172849 | Sep 2018 | WO |
2018183777 | Oct 2018 | WO |
2018201097 | Nov 2018 | WO |
2018232376 | Dec 2018 | WO |
2018232377 | Dec 2018 | WO |
2019011451 | Jan 2019 | WO |
2019096401 | May 2019 | WO |
2019126755 | Jun 2019 | WO |
2019157400 | Aug 2019 | WO |
2019180506 | Sep 2019 | WO |
2019201945 | Oct 2019 | WO |
Entry |
---|
European Search Report dated Apr. 29, 2020, in counterpart European Patent Application 19216250.1. |
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. |
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). |
Number | Date | Country | |
---|---|---|---|
62780028 | Dec 2018 | US |
Number | Date | Country | |
---|---|---|---|
Parent | 17846635 | Jun 2022 | US |
Child | 18514144 | US | |
Parent | 16694587 | Nov 2019 | US |
Child | 17846635 | US |