The present disclosure generally relates to systems and methods for proximity sensing on a marine vessel, and more specifically to proximity sensing systems and methods that automatically estimate proximity sensor location on a marine vessel and calibrate the system accordingly.
The following U.S. patents 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. 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.
In one embodiment, a system for proximity sensing on a marine vessel includes a main inertial measurement unit (IMU) positioned on the marine vessel at a main installation attitude and a main location, a first proximity sensor configured to measure proximity of objects from a first sensor location on the marine vessel, and a first sensor IMU positioned on the marine vessel at the first sensor location and at a first installation attitude. A sensor processor is configured to receive main IMU data from the main IMU and first IMU data from the first sensor IMU, wherein the main location of the main IMU on the marine vessel is known and at least one of the first sensor location and first installation attitude of the first sensor IMU on the marine vessel are initially unknown. The sensor processor determines a relative orientation transform between the main installation attitude and the first installation attitude by comparing the main IMU data and the first IMU data, and then determines a relative position transform between the main location and the first sensor location based on the relative orientation transform and comparison of the main IMU data and the first IMU data.
In one embodiment, a method of calibrating a proximity sensor on a marine vessel includes receiving, at a processor, main IMU data from a main inertial measurement unit (IMU) positioned on the marine vessel at a main installation attitude and a main location, and receiving first IMU data from a first sensor IMU co-located with a first proximity sensor at a first sensor location on the marine vessel and at a first installation attitude. The first proximity sensor is configured to measure proximity of objects from the first sensor location, wherein the main location of the main IMU on the marine vessel is known and at least one of the first sensor location and first installation attitude of the first sensor IMU on the marine vessel are initially unknown. A relative orientation transform is determined between the main installation attitude and the first installation attitude by comparing the main IMU data and the first IMU data, and a relative position transform is determined between the main location and the first sensor location based on the relative orientation transform and comparison of the main IMU data and the first IMU data.
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 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, each control module 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 are stored. The processor can access the computer-readable code and, upon executing the code, carries out functions, such as the navigation control functions and/or the proximity sensing calibration 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 lever(s) 34 functions 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 lateral translation or rotation of the vessel 10.
The propulsion 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, stern, and 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 may provide this distance and/or direction information to one or more control modules, such as to the sensor processor 70 and/or the controller 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 controller 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
In certain embodiments, the sensor processor 70 may integrate all available sensor data from all sensor types into one or more maps or occupancy grids integrating all proximity measurement data. In such an embodiment, the proximity data from all of the various sensors needs to be translated into a common reference frame.
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 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 automatic maneuver-limiting control, all of the data sources are translated to a common reference frame. This requires precise knowledge of the location and installation attitude, or orientation, of each sensor relative to the common reference frame such that the data measured therefrom can be translated appropriately. Regardless of whether a map or occupancy grid is created, the relevant sensor positions and installation attitudes of each sensor on the marine vessel must be known so that the proximity measurements from each respective sensor can be properly interpreted for navigation purposes.
Determination of the location and orientation of each sensor is a tedious process involving measurement of each sensor location from a defined location on a marine vessel and precise definition of the installation attitude of each installed sensor. This can be prohibitively expensive for boat builders and is a source of error and a potential failure point for vessel control systems. Some prior art systems have attempted to reduce proximity sensing installation costs by designing systems that include pre-determined sensor locations built into the vessel design, where each sensor incorporated in the system is pre-specified and must be installed precisely at a predetermined location and orientation. However, many boat builders find such systems to be overly constraining, especially given the variability of vessel configurations demanded by buyers. Moreover, such systems are error-prone because sensors are not always properly installed exactly to specifications.
In view of their recognition of the problems with current systems and challenges faced in the relevant industry, the inventors have developed the disclosed proximity sensing systems and methods, which are “plug-and-play” sensor systems that do not require laborious and exacting installation measurements, but also do not require a priori sensor configuration and specification and instead provide unlimited customization options to boat builders. The disclosed system provides flexibility for installing sensors in a variety of locations, where installation variability is automatically accounted for in an automated system configuration process.
The disclosed system and method utilize a main inertial measurement unit (IMU) installed at a known location on the marine vessel. Referencing the example in
The disclosed system is configured to automatically locate each proximity sensor 72, 74, 76, 78 on the marine vessel 10 by relying on measurements from a co-located IMU with each proximity sensor 72-78. Namely, each proximity sensor 72, 74, 76, 78 has a respective IMU 62, 64, 66, 68 provided therewith at a known orientation relative to the view angle, or reporting frame, of the respective sensor 72-78. Each sensor IMU 62, 64, 66, 68 provides IMU data describing linear acceleration, angular acceleration, attitude, and/or heading. For example, each sensor IMU 62-68 may include a rate gyro, an accelerometer, and a magnetometer, and thus the IMU data provided may consist of rate gyro measurements, accelerometer measurements, and magnetometer measurements. Each sensor IMU 62-68 may be incorporated within the housing of each sensor device 72-78, or may be a separately-housed device located as close as possible to the respective proximity sensor 72-78 and installed at a known relative orientation thereto.
In one embodiment, the IMU data from each sensor IMU 62-68 is provided to a sensor processor 70. For example, the IMU data from each sensor IMU 62-68 may be transmitted along with the proximity measurements from the respective proximity sensor 72-78. In other embodiments, each sensor IMU 62-68 may have an integrated microprocessor configured to process the respective sensor IMU data and compute an attitude estimate for that IMU 62-68. In the embodiment shown in
In the embodiment in
In one embodiment, the sensor processor 70 is programmed to automatically perform a sensor configuration process where it determines the installation location on the marine vessel and the installation attitude of each proximity sensor 72-78 without requiring such information to be inputted by an installer or performed in accordance with pre-set installation instructions. More specifically, the sensor processor 70 is configured to solve for the sensor location and sensor installation attitude of each sensor 72-78 based on the IMU data received from each sensor IMU 62-68. As described above, the installation location of the main IMU (herein referred to as the “main location”) is known by the sensor processor 70. Such information may be known based on user input at the time of installation of the INS 60, for example, or may be assumed based on system specifications. In certain embodiments and the installation attitude of the main IMU (herein referred to as the “main installation attitude”) may also be known, such as specified upon installation. Alternatively, the main installation attitude may be automatically determined during the automated system configuration process using similar algorithms as used to solve for the installation attitudes of the sensor IMUs 62-68, disclosed herein. Either way, the main installation attitude of the main IMU 36 is determined such that the attitude of the sensor IMUs 62-68 can eventually be calculated with respect to the main installation attitude of the main IMU 36.
The locations and installation attitudes of each sensor IMU 62-68, and thus each proximity sensor 72-78, may be initially unknown to the sensor processor 70 upon installation of the proximity sensing system. Thus, an installer may place the sensors 72-78 (and co-located IMUs 62-68) at any location on the marine vessel 10. The sensor processor 70 comprises software that automatically performs a system configuration whereby the locations and installation attitudes of each proximity sensor 72-78 are determined. Specifically, a relative orientation transform is determined that maps the installation attitude of each sensor 72-78 to the main installation attitude of the main IMU 36, and a relative position transform is determined mapping the sensor location of each proximity sensor 72-78 and sensor IMU 62-68 to the location of the main IMU 36 or to some other point on the marine vessel 10 with respect to which the relative position of the main IMU 36 is known. The relative position transform is determined based on the relative orientation transform and comparison of the first IMU data to the main IMU data. Thus, the locations of all sensors 72-78 and the main IMU 36 may be defined with respect to a particular point on the marine vessel (such as the center of gravity (COG) or center of rotation (COR)), which it may also be the point used for navigation calculations. Thereby, all proximity sensor locations are defined with respect to a common reference frame.
The graphs at
The sensor processor 70 is configured to analyze the IMU datasets to estimate the installation attitude and sensor location of each proximity sensor 72-78 with respect to the main installation attitude of the main IMU 36. In one embodiment, the sensor processor 70 includes estimation algorithms that hone in on the installation attitude and sensor location of the first sensor (e.g. 62, 72) over time. For example, the estimation algorithms may implement estimation filtering over time, such as Kalman filtering (sometimes referred to as linear quadratic estimation), to produce increasingly accurate estimates of the installation attitude and sensor location, which are unknown variables to the sensor processor 70 prior to the calibration procedure. Referring to
From there, the main attitude estimate 91a and the sensor attitude estimate 91b are provided to a sensor attitude processing algorithm 93 that calculates a relative orientation transform 94 for that first sensor IMU 62 based on a difference between the first installation attitude of the first sensor IMU 62 and the main installation attitude of the main IMU 36. For example, the sensor orientation transform 94 may be calculated to describe the attitude of the respective sensor IMU 62-68 with respect to the Earth's horizon, which may be equated to a plane of the boat (e.g., defined as the plane parallel to the keel and the transom). Such calculation is a difference between sensor attitude estimate 91b and the main attitude estimate 91a adjusted for the known main installation attitude.
The estimator filters or attitude estimation algorithms 90a and 90b may also generate an uncertainty value for the estimated attitude of the respective IMUs 36, 62. Namely, the attitude estimation algorithm 90a may output a main attitude uncertainty value 92a describing the uncertainty of the main attitude estimate 91a, and the attitude estimation algorithm 90b may output a sensor attitude uncertainty value 92b describing the uncertainty of the sensor attitude estimate 91b for the first sensor IMU 62. The uncertainty value is expected to decrease over time as the filter converges on a more accurate estimate for the attitude—e.g. as the system effectively identifies and eliminates noisy sensor data and other random external factors. The time to convergence may vary depending on, for example, the amount of noise in the measurement data and the amount of vessel motion that occurs during the calibration measurements. The time to convergence may increase in situations where the IMU data 80, 82 is especially noisy or where the marine vessel 10 is very still. A lack of motion of the marine vessel can deprive the filter estimator of the data needed to make accurate comparisons and calculations of the unknown variables, thus increasing the time to convergence for the estimated attitudes 91a, 91b.
In certain embodiments, an uncertainty value may also be generated for the relative orientation transform 94. The sensor attitude processing algorithm 93 may generate a sensor orientation uncertainty value 95 calculated based on the uncertainty values 92a, 92b for the estimated attitudes of the IMUs 36, 62. For example, the orientation uncertainty value 95 may be the root-mean-square of the uncertainty values 92a, 92b.
A relative position transform 98 for the first sensor IMU 62 is then calculated using the relative orientation transform 94, as well as the main IMU data 80 and the sensor IMU data 82 as input to a relative position estimation algorithm 96. The relative position estimation algorithm 96 includes another filter estimator to compute an estimated first sensor location. For example, a Kalman filter may be utilized to estimate the first sensor location relative to the main location of the main IMU 36 based on the estimated first installation attitude, the vessel attitude (e.g. attitude measurements from the main IMU 36), the main IMU data 80, and the first sensor IMU data 82. Specifically, the Kalman filter estimator may utilize the rate gyro measurements and the accelerometer measurements from the respective IMU datasets 80, 82. For example, the governing equation for the position estimation by the relative estimation algorithm may be provided by the following:
Asensor=Amain−[{dot over (ω)}×r]−[ω×ω×r]
where Asensor is the vector of the three-body frame linear accelerations at the sensor in question (e.g., the first sensor IMU 62), Amain is the vector of the three-body frame linear accelerations measured by the main IMU, ω is the vector of three-body axis rotation rates, {dot over (ω)} is the derivative of the rotation rates along each axis, and r is the vector of three cartesian (x, y, z) position offsets between the location of sensor in question (e.g., the first sensor IMU 62) and the location of the main IMU 36. Accordingly, this is a three-dimensional equation where the r values in each of the x, y, and z directions are unknown and can be solved for. The sensor orientation transform 94 derived at the first portion of the calibration is utilized to rotate the acceleration vector Asensor for the first sensor IMU 62 to be in the same reference frame as the acceleration vector Amain of the main IMU 36. Then, since the devices are attached to the same vessel, which is a rigid body, ω and {dot over (ω)} (the derivative of the measured ω) should be the same. Thus r, representing the position of the first sensor IMU 62 relative to the position of the main IMU 36, can be solved for.
This solution will be provided by the filter estimator, such as a Kalman filter, which will converge on an accurate estimated sensor location value over time. The filter estimator may generate an uncertainty value for the estimated first sensor location, the sensor position uncertainty 99, which will decrease as the estimator filter converges on the correct r value over some period of time. The sensor position uncertainty 99 is based on the sensor orientation uncertainty, as well as the attitude uncertainties 92a, 92b. Thus, as described below, the system may be configured to first minimize those uncertainties before calculating the sensor position transform 98. As described above, this period of time for convergence may be situationally-dependent, such as based on the water conditions and noise in the system. For example, convergence may be reached when the sensor position 99 reaches a minimized uncertainty threshold, which is a pre-set threshold at which point the estimated position value can be considered reliable. Upon reaching the minimized uncertainty threshold, the estimated first installation attitude and estimated first sensor location may be stored, such as in memory of the sensor processor 70 for future use by the system 20. The same process is applied for each sensor IMU (e.g., 62-68) within the system 20 so that the installation attitude and the location of each can be determined.
In certain embodiments, the sensor processor 70 may continue to compare the main IMU data 80 and the sensor IMU data 82 and calculate the estimated first installation attitude and estimated first sensor location, along with the respective uncertainty values, in order to verify that the sensor calibration remains accurate. For example, if a sensor is moved or rotated such that the location or attitude changes, then the uncertainty value will increase and the system 20 can act accordingly until the estimated sensor installation attitude and/or sensor location determination is accurate again (i.e., the uncertainty value is less than the minimized uncertainty threshold).
In certain embodiments, the navigation algorithm, such as executed at the controller 24, may weight the proximity data from the respective sensor 72-78 according to the uncertainty value when the uncertainty value is greater than the minimized uncertainty threshold. In other embodiments, a fault condition may be generated when the uncertainty value is less than the minimized uncertainty threshold and the navigation controller may be configured to not operate in an autonomous or semi-autonomous mode until removal of the fault condition (i.e., the uncertainty value is greater than the minimized uncertainty threshold).
In various embodiments, the sensor processor 70 may be configured to adjust the proximity measurements from each proximity sensor 72-78 based on the relative orientation transform and the relative position transform for the respective sensor in order to present all of the proximity measurements in the same coordinate system. Thereby, proximity measurements from all sensors can be presented in a common coordinate frame and easily correlated for making navigation determinations. Given that the relative orientation is known between each proximity sensor 72-78 field of view and the installation attitude of the corresponding sensor IMU 62-68, the proximity measurements from all of the sensors can be adjusted to a common coordinate frame. Where the sensor processor 70 is separate from the navigation controller, such as central controller 24, the adjusted proximity measurements may be communicated to the navigation controller for use in navigation. In certain examples, the adjusted proximity measurements may be transmitted via a dedicated bus, a wireless transmission protocol, or via a CAN bus comprising part of the vessel network. The adjusted proximity measurements may be similarly communicated to other control elements within the system 20, as necessary.
Instructions are then executed as represented at step 108 to determine the relative position transform and uncertainty value for the estimated sensor location. In the depicted example, the relevant proximity measurements are weighted according to the uncertainty value until the uncertainty value reaches the minimized uncertainty threshold. Namely, the adjusted proximity measurements may be calculated at step 112 based on the relative position transform and the relative orientation transform, and then the adjusted proximity measurements may be weighted based on the uncertainty value, as represented at step 114. Thus, where the sensor processor has not yet converged on reliable installation attitude and location estimations for certain sensors 72-78, the data from those sensors may be weighted less heavily in the navigation algorithm. In other embodiments, the system 20 may be configured to wait until all sensors are calibrated (i.e., all uncertainty values are less than the minimized uncertainty threshold) before activating any autonomous or semi-autonomous navigation functions.
In certain embodiments, the system may be configured to track the amount of time spent on calibration and to only allow a maximum time for the calibration process prior to generating a fault action and/or fault alert if the sensor position uncertainty 99 (and thus also the sensor orientation uncertainty 95) does not reach the minimized uncertainty threshold (step 110) within the maximum allotted time. In certain embodiments, the system may also be configured to identify the error path. For example, the system may be configured to determine whether the problematic sensor IMU is too close to the main IMU, and thus insufficient data is available for sufficiently accurate resolution of the sensor position transform 98 (i.e., the “r” vector of three cartesian (x,y,z) position offsets is too small to be accurately resolved). Alternatively or additionally, the system may be configured to determine whether the problematic sensor IMU is too noisy, or whether insufficient acceleration data is available (i.e., the vessel is too still).
Once the uncertainty value for the estimated sensor location reaches the minimized uncertainty threshold at step 110, then the relative position transform and the relative orientation transform and/or the estimated installation attitude and the estimated sensor location may be stored at step 116, such as in memory of the sensor processor 70. Thereby, the values can be later utilized for calculation of the adjusted proximity measurements from each sensor, so as to reduce processing demand on the sensor processor 70. In certain embodiments described above, the estimation algorithms may continually run, or selectively run, in order to verify that the calibration is still correct and that the uncertainty values are still below the minimized uncertainty thresholds.
Once the uncertainty values reach the minimized uncertainty threshold, a calibration completion alert is generated at step 118 to alert the user/installer that the calibration is complete and the proximity measurements being utilized by the navigation system are properly calibrated and reliable. Adjusted proximity measurements are then calculated at step 120 using the calibrated values so that all of the proximity measurements by the various sensors are provided on a common coordinate frame. In certain embodiments, the sensor processor 70 may communicate only the adjusted proximity measurements to the navigation controller, such as the CCM 24.
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.
Number | Name | Date | Kind |
---|---|---|---|
5515287 | Hakoyama et al. | May 1996 | A |
6234100 | Fadeley et al. | May 2001 | B1 |
6273771 | Buckley et al. | Aug 2001 | B1 |
7267068 | Bradley et al. | Nov 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 |
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 |
20030137445 | Rees et al. | Jul 2003 | A1 |
20050075016 | Bertetti et al. | Apr 2005 | A1 |
20060058929 | Fossen et al. | Mar 2006 | A1 |
20070089660 | Bradley | 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 |
20160320190 | Wu | Nov 2016 | A1 |
20160370187 | Gatland et al. | Dec 2016 | 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 | 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 |
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 |
Number | Date | Country |
---|---|---|
2279165 | Jan 2001 | CA |
2282064 | Jan 2001 | CA |
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 |
2018162933 | Sep 2018 | WO |
2018183777 | Oct 2018 | WO |
2018201097 | Nov 2018 | WO |
2018232376 | Dec 2018 | WO |
2018232377 | Dec 2018 | WO |
2018232377 | Dec 2018 | WO |
2019011451 | Jan 2019 | WO |
2019096401 | May 2019 | WO |
2019126755 | Jun 2019 | WO |
2019157400 | Aug 2019 | WO |
2019201945 | Oct 2019 | WO |
Entry |
---|
European search report dated Mar. 31, 2020 in counterpart European Patent Application 19210025.3. |
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. |
Number | Date | Country | |
---|---|---|---|
20200160725 A1 | May 2020 | US |
Number | Date | Country | |
---|---|---|---|
62770499 | Nov 2018 | US |