The structural integrity of a vessel hull is an important safety an economical concern. For example, frictional resistance due to buildup on or fouling of the hull by algae, sea grass, barnacles, and the like as a vessel moves through the water can increase the fuel consumption of the vessel. The result is added cost to operate the vessel and increased emissions. Moreover, monitoring of damage to the hull is useful in determining when and where repairs should be made.
A variety of methods are currently employed to lower the chance of bio-fouling and to monitor the structural integrity of the hull. For example, typically, while the ship is dockside and/or during normal unlading conditions, the hull can be periodically inspected manually, such as by scuba divers using various equipment. The cost of such an inspection procedure can be costly. This type of inspection effort may be repeated at a predetermined period of months, such as every ten to twenty months or sooner, particularly if there is suspicion of damage to the vessel hull. To properly inspect the vessel hull, the hull often must first be cleaned. As a complication, however, some jurisdictions have made dockside cleaning illegal due to the release of contaminants into the water, and particularly particles of anti-fouling paint which is toxic, and which has been found to contaminate the water.
Most prior hull cleaning robots suffer from various shortcomings. Typically, robots are connected to a cable and powered and controlled by an on-board power supply and control system and are able to operate only on a stationary vessel. Further, inspection techniques for determining the cleanliness of the hull are inefficient. The monetary cost and intrinsic value of such robots can be high, and therefore, there is a desire to properly secure the robot to avoid damage or loss.
A hull robot is disclosed for operation on a surface of a hull of a vessel in accordance with an example of the present technology. The robot can include a drive subsystem onboard the robot for driving and maneuvering the robot about the hull. A sensor subsystem onboard the robot can sense an attachment state of the robot to the hull. The attachment state can include at least one of attached and detached. A signal generation subsystem onboard the robot can emit a distress signal when the attachment state of the robot is that of detached, or in other words, when the robot becomes detached from the hull.
A method of detecting detachment of a hull robot from a surface of a hull of a vessel, in accordance with an example of the present technology, includes positioning the robot about the hull and sensing an attachment state of the robot to the hull using a sensor subsystem onboard the robot. The attachment state can include at least one of attached and detached. A distress signal can be emitted using a signal generation subsystem onboard the robot when the attachment state of the robot is that of detached.
A system for detecting detachment of a hull robot from a surface of a hull of a vessel is described in accordance with an example of the present technology. The system can include a processor, a memory for storing hull property data, and a sensor carried by the hull robot, the sensor being configured to detect an attachment state of the robot relative to the hull. A distress module carried by the hull robot can identify a distress situation when an attachment state of the robot is that of detached.
a is a side view of a ship with a hull cleaning robot attached thereto in accordance with the subject technology;
b is an end view of a ship with a hull cleaning robot attached thereto in accordance with the subject technology;
a-11b are cross-sectional side views of a hull robot body including a buoyant material in accordance with the subject technology;
a-12b are cross-sectional side views of a hull robot body including a buoyant air pockets and bladders in accordance with the subject technology;
a-13b illustrate inflation of an inflatable flotation device carried by the robot in accordance with the subject technology;
Before the present disclosure is described herein, it is to be understood that this disclosure is not limited to the particular structures, process steps, or materials disclosed herein, but is extended to equivalents thereof as would be recognized by those ordinarily skilled in the relevant arts. It should also be understood that terminology employed herein is used for the purpose of describing particular embodiments only and is not intended to be limiting.
Definitions
The following terminology will be used in accordance with the definitions set forth below.
As used herein, “robot body” is intended as a broad term to define one or more structural components (e.g., a frame, chassis, cover, etc.) capable of supporting one or more other components of a hull robot or its subsystems, and/or capable of providing covering and/or concealment of one or more components or subsystems of the hull robot.
As used herein, the singular forms “a,” and, “the” include plural referents unless the context clearly dictates otherwise.
As used herein, the term “substantially” refers to the complete or nearly complete extent or degree of an action, characteristic, property, state, structure, item, or result. For example, an object that is “substantially” enclosed would mean that the object is either completely enclosed or nearly completely enclosed. The exact allowable degree of deviation from absolute completeness may in some cases depend on the specific context. However, generally speaking the nearness of completion will be so as to have the same overall result as if absolute and total completion were obtained. The use of “substantially” is equally applicable when used in a negative connotation to refer to the complete or near complete lack of an action, characteristic, property, state, structure, item, or result. For example, a composition that is “substantially free of” particles would either completely lack particles, or so nearly completely lack particles that the effect would be the same as if it completely lacked particles. In other words, a composition that is “substantially free of” an ingredient or element may still actually contain such item as long as there is no measurable effect thereof
As used herein, the term “about” is used to provide flexibility to a numerical range endpoint by providing that a given value may be “a little above” or “a little below” the endpoint.
As used herein, a plurality of items, structural elements, compositional elements, and/or materials may be presented in a common list for convenience. However, these lists should be construed as though each member of the list is individually identified as a separate and unique member. Thus, no individual member of such list should be construed as a de facto equivalent of any other member of the same list solely based on their presentation in a common group without indications to the contrary.
Example Embodiments
Reference will now be made to the exemplary embodiments illustrated, and specific language will be used herein to describe the same. It will nevertheless be understood that no limitation of the scope of the technology is thereby intended. Additional features and advantages of the technology will be apparent from the detailed description which follows, taken in conjunction with the accompanying drawings, which together illustrate, by way of example, features of the technology.
It is noted in the present disclosure that when describing the system, or the related devices or methods, individual or separate descriptions are considered applicable to one another, whether or not explicitly discussed in the context of a particular example or embodiment. For example, in discussing an energy harvester configuration per se, the device, system, and/or method embodiments are also included in such discussions, and vice versa.
Furthermore, various modifications and combinations can be derived from the present disclosure and illustrations, and as such, the following figures should not be considered limiting.
The result is a robot able to maneuver, at a minimum, about hull 12 as shown by arrows 24. Furthermore, the robot is typically able to maneuver in one or more controlled paths about the hull, which are not necessarily aligned with vector 14 and which are in addition to the directions shown by arrows 24. The robot can be powered by the action of the water flowing past the hull while the vessel is underway. In this way, cleaning and/or inspection and the like can be undertaken even continuously while the vessel is in operation. The robot is thus configured to harvest the energy it needs from the action of a fluid flowing past the robot.
Typically, other subsystems can be included as components of robot 10, for example, a cleaning subsystem, a navigation subsystem, a communications subsystem, and the like. Moreover, although certainly possible in some embodiments, in many embodiments the robot body 16 need not be tethered to any kind of an on-board power or control subsystem. The turbine subsystem can operate drive subsystem 18 (and, in one example, a cleaning subsystem) directly or via a generator charging a power supply or power subsystem (e.g., a battery pack) which supplies power to one or more motors driving the drive subsystem and/or the cleaning subsystem. The battery pack can also be used to energize the other electronic and/or electromechanical subsystems associated with the robot. In one aspect, the generator may drive one or more motors directly.
In one particular example, robot 10′,
Referring to
As shown in
Referring again to
In one example, an endless belt 34 is disposed over rollers 50a and 50b and includes magnets and/or magnetic materials 52 embedded (e.g., encapsulated) in the material of the belt, which can be made of rubber. Such a magnetic belt may effectively secure the robot to the hull of the vessel. Other magnetic subsystems used to engage a robot with the hull of a vessel are also contemplated.
In the example shown in
If the cleaning subsystem is active, e.g., driven, it may be beneficial to operate the cleaning apparatus to assist in robot maneuvering operations. For example, two rotating cleaning brushes could be operated in opposite directions so there is no net force on the robot. With a larger single front and/or rear brush rotatable on an axle oriented transverse to the primary direction of robot travel, the brush could be operated to rotate opposite the direction of travel of the track when the robot is maneuvering in the direction of the water flowing past the hull (i.e., downstream). When the robot is maneuvering upstream, it may be desirable to run the brush in the same direction as the track When the robot is maneuvering in a direction transverse to the water flow direction, it may also be desirable to operate the brush and the track in the same direction.
A hull robot can have significant benefits in inspection, cleaning, maintenance and other operations with respect to a vessel, and particularly a vessel in motion. However, there may be situations where a robot inadvertently becomes detached from the hull of a vessel or ship. For instance, in the case where an electromagnet is used to secure the robot to the hull of the vessel, any loss of power may result in the electromagnet being unable to secure the robot to the hull, and the detachment of the robot from the hull. In other situations, the vessel may strike or come close to an obstacle, such as a rock, river or ocean floor, iceberg, etc. that may knock the robot off of the hull. In still other situations, strong waves may dislodge the robot from the hull. Obviously, other situations may exist where a robot is inadvertently caused to be detached from the hull. Because of the monetary cost and intrinsic value of such robots, it is desirable to not only properly secure the robot to avoid damage or loss, but to be able to retrieve a robot which has become detached from the hull.
In one example, the present technology provides separation countermeasures to address situations where the hull robot does become separated from the vessel. The separation countermeasures can be implemented in any of a variety of different ways with any of a variety of different devices. For example, the separation countermeasures may include sensors or detectors for sensing separation of the robot from the vessel, such as visual, motor current detectors, g-vector sensors, pressure sensors, functional GPS (global positioning system) sensors for detecting discrepancies with respect to a vessel, flow field detectors, noise fiduciary detectors, magnetic sensors, and so forth. Any of a variety of other sensors may also be used which are suitable to detect the presence of the vessel or the attachment state of the robot to a hull of the vessel. The sensors may also be used in any suitable combination.
Therefore, referring to
In the example shown in
In another example, the detector 215 can be an ultrasonic detection device. For example, the hull robot may be equipped with an ultrasonic inspection device for use in inspecting the hull of a vessel. In a similar operation as when the ultrasonic inspection device inspects the hull, operation of the ultrasonic inspection device can detect when the hull is not present (i.e., when the hull robot has been separated from the hull). The ultrasonic inspection device can be configured to recognize ultrasonic signatures of a clean hull, a fouled hull, and/or a lack of presence of the hull. For ultrasonic inspection, an ultrasound transducer connected to a diagnostic machine (both of which may be supported on the hull robot and included in the detector 215) is passed over the hull, wherein ultrasonic pulse-waves, such as those with center frequencies ranging from 0.1-50 MHz, can be directed into the hull to detect internal flaws or to characterize hull properties. Ultrasonic inspection can also be used to determine a thickness of the hull, for example, to monitor corrosion. The transducer may be separated from the hull by a couplant, wherein the couplant facilitates transmission of the ultrasonic energy from the transducer into the hull. While oil as a couplant may be used in some examples, the couplant is preferably water, due to the likely immersion of the robot under water on the vessel in motion. Referring to
The flow field may be different about various locations of the hull of the vessel. For example, the fluid dynamics of the water can vary from the front of the ship to the back and can vary from near the surface of the water to the bottom of the vessel. This information can be stored in a database and later referenced for use in determining whether, based on the detected fluid flow, the robot has potentially separated from the ship. For instance, in the event a flow field or fluid flow is detected that is outside of a pre-determined range of acceptable fluid flow field parameters, then it may be determined that the robot has detached from the vessel.
With the fluid flow detector configuration, the robot can be configured with a receiver or transceiver to receive a wireless signal from an emitter or other signal generator on the vessel when the vessel is moving or stopping in addition to what is being detected by the fluid flow detector in properly identifying whether the robot is attached to the ship. The wireless signal can be transmitted using any suitable wireless transmission technology such as, but not limited to, radio frequency (RF) communication, microwave communication, infrared (IR) short-range communication, and so forth. RF signals generally do not transmit well through water. As a result, when RF signals are used, the robot can be navigated above the water line to detect the signals. Acoustic modems are an example device can carry out underwater communication. However, the bandwidth of acoustic modems is typically a fraction of what is transmissible in air. As a solution, the signals can be transmitted without the use of high bandwidth signals. For applications where communications require additional bandwidth the acoustic modem can be used to signal the robot to come to the surface to receive a message transmitted via RF signals. Another approach is to have the robot travel above the waterline at regular intervals and to wait to transmit important information during one of these above-waterline intervals. In the event that the robot has become detached from the hull and is resident on a surface of the water, then RF transmission can be a viable way of communicating.
For example, if the ship is moving and the fluid flow detector fails to identify the flow of fluid, the robot may indicate a possible separation from ship as a valid indication. Other factors, such as equipment malfunction on the robot, for example, can also lead to a failure to identify the flow of the fluid, and thus the separation from the vessel in this example may be a valid separation. If the vessel slows or has come to a stop and this relayed to the hull robot, then when the fluid flow detector fails to detect an acceptable fluid flow, the robot can be configured to not identify the lack of fluid flow as a possible indicator that the robot has separated from the vessel.
When the robot detaches from the ship, there may still be at least a minimal flow of water being detected due to currents or waves in the water, movement of the robot within the water (i.e., floating, sinking, driving), and so forth. Therefore, when a flow of water is still detectable and not usable as a basis for identifying a separation from the vessel, communication with the vessel can be useful to determine whether a speed of the vessel corresponds with the detected flow of water to identify whether the robot has potentially become detached from the hull.
In other examples, rather than communicating with the vessel to receive a signal indicative of the stopping, slowing or moving of the vessel, the sensor subsystem can comprise an acoustic detector, such as a microphone, configured to detect sound from the engine of the vessel or from the rotation of turbines or propellers disturbing the water to propel the vessel. When the vessel starts or stops movement, or changes speed, the acoustic detector can detect the change in sound and factor in this information in detecting an attachment state of the robot.
In another example, the sensor subsystem may comprise a detector 219 such as a gravity vector (g-vector) detector configured to detect an angular orientation of the robot relative to a direction of gravity. More specifically, the g-vector detector can be a gravitometer or gravimeter for detecting a direction of gravity. A ship or vessel generally may have a hull with a specific contoured shape. Various positions about the hull (e.g., between a top and a bottom of the hull) may be angled differently with respect to one another. A hull robot equipped with a gravimeter can detect a unique g-vector for substantially any location about the hull. For example, a direction of gravity may remain substantially the same, but an orientation of the robot with respect to the direction of gravity may change as the robot traverses the hull. Thus, in some examples, the g-vector can be determined relative to an orientation of the robot, or more specifically to a longitudinal and/or lateral axis or angular orientation with respect to the detected direction of gravity. The unique g-vectors for the various vertical locations about the hull can be pre-determined and stored in a database that can be referenced when the gravimeter detects the direction of gravity with respect to a current robot position or orientation.
In the event that the robot separates from the ship, a g-vector subsequently detected will likely not be consistent with those acceptable unique g-vectors corresponding to positions of the robot when secured about the hull. Therefore, the robot can identify that detachment has occurred. For example, the robot may be configured to float in the water at an orientation different than the various possible orientations experienced by the robot while on secured to the hull of the vessel. Thus, if the hull robot analyzes a change in vertical orientation of the hull robot by detecting a corresponding g-vector and comparing this with acceptable unique g-vectors, separation or attachment of the robot with respect to the hull can be identified. In another example, rather than, or in addition to, use of the gravimeter, an accelerometer may be used to determine an orientation of the hull robot relative to the ship. The detected orientation data can be used similarly to the gravity data described above.
In accordance with one example, the detector 219 of the sensor subsystem can be a pressure detector configured to detect a pressure of fluid (e.g., water pressure) about the robot. Pressure generally will have a direct correspondence with a depth beneath a surface of the water. Pre-determined pressure information can be generated and stored in a database onboard the robot for later comparison to facilitate identification of an approximate vertical position on the side of the vessel hull. In one aspect, with the robot and the pressure sensor submersed, when a pressure is detected, reference to the database using a processor can identify the current pressure and the associated approximate vertical position about the hull by comparing the current pressure to those stored. In another aspect, the pressure sensor, or one or more different sensors, can further be configured to detect a pressure out of water as well. Thus, the pressure sensor(s), alone or in combination if multiple sensors are present, can determine whether the robot is above or beneath (or at) the water level, as well as an approximate vertical position about the hull. In addition, the pressure sensor can also be configured to determine a distance the robot is away from the water level, with depth or pressure measurements corresponding to a distance above or below the water, wherein an at-the-water line pressure can be determined and used for comparison.
In operation about the hull and as secured to the hull, water pressure about the robot may generally be identifiable. In addition, the navigation subsystem can be used to identify a given position about the hull. Using this information, the robot can then determine what the water pressure should be at this given position. If the detected pressure is different from than expected, or if outside of an acceptable range, then potential separation from the ship can be identified. In another example, if the robot is using the drive system to navigate the hull in a direction that should result in a change of pressure, but the pressure sensor does not detect a change in pressure, the cause could be that separation has been occurred. In another example, the pressure sensor can be configured to identify a rapid change in pressure, such as with a sinking or rising event. Typically such rapid changes in pressure will not occur during normal operation on the vessel hull, thus indicating possible separation of the robot from the hull. Still further, pressure changes can be monitored to ensure that these are consistent with acceptable movements of the robot about the hull. For example, if the robot is commencing a cleaning function at a particular location, the water pressure at that location can be identified. If the water pressure begins to change, and the robot has not initiated locomotion from that position (e.g., known because the drive subsystem has not initiated), this could indicate that the robot has been separated from the hull.
In another example, the detector 219 of the sensor subsystem can be a global positioning system or GPS device configured to track or provide a location of the robot, and may further be configured to track the location of the robot relative to the vessel. The robot, via its GPS device, can be in communication with the vessel, particularly in the event of separation from the hull. The GPS can detect whether relative movement between the vessel and the robot is increasing.
In one example, the detector 219 of the sensor subsystem can be a magnetometer or compass. The presence of the metallic hull may generally skew magnetic readings with respect to magnetic North. Therefore, the sensor subsystem can identify the presence of the hull when the magnetic reading is different than magnetic North and may identify a potential separation from ship when the reading is magnetic North. Because the ship may navigate in a direction that causes the biased reading to read the same as the direction of magnetic North, the robot can be configured to change an orientation or position on the hull when a magnetic North reading is detected in order to determine whether the reading potentially represents a separation from the ship as opposed to an orientation of the ship.
Similarly, the sensor subsystem can comprise one or more magnets supported and positioned a given elevation about the hull, which magnets can be associated with a magnetic sensor. An attraction of the magnet to the hull can be detected and compared with pre-determined acceptable attraction valued. For example, the detector 219 can be an electromagnet with detection capabilities to identify the magnetic attraction or field. Other implementations, such as a spring-loaded permanent magnet 221 may also be used where the detector 219 is configured to detect whether the spring 223 is extended due to a magnetic attraction between the permanent magnet and the hull. If a currently measured attraction falls below an acceptable threshold, or no longer exists, such a condition may indicate separation of the robot from the hull. Since magnetic fields vary as the cube of the distance, the drop-off rate is very fast.
The detector 219 of the sensor subsystem in some examples can be a noise detector configured to detect noise of the vessel, water coming in contact with the vessel, etc. as has been briefly mentioned above. Noise or sound can be used to determine the presence of the vessel. More specifically, the sensor subsystem can make use of existing or natural boat derived noise fiduciaries to identify whether the ship is present and/or operational. The sensor subsystem can include a microphone or other suitable acoustic detector for detecting the noise. In this example, noise generation systems onboard the vessel can generate the identifying noise. The vessel need not include specially designed noise generation systems as the vessel typically already generates identifying noises, such as engine noise and bow noise (i.e., propeller operation and water hitting the bow of the vessel). In some instances, equipment with or on the vessel at locations other than the engine, propeller, or bow may also provide identifying noises. The location of the bow noise and the engine noise are known. The noises from these generally have certain frequencies that can be measured to determine which noise is being detected. The sensor subsystem can use one or both of these (or any other noise fiduciaries) to determine the presence of the ship. If a noise fiduciary is not detected, or if such falls below an acceptable level, this could indicate separation of the robot from the hull.
The sensor subsystem can include a spring-loaded or other suitable device configured to apply a force or pressure against the hull 212 of the vessel, such as the device as illustrated in
In another exemplary implementation, the arm 216 supported by the base 214 can be magnetized. The base can include a strain gauge, rotation detector, or other suitable device for detecting a force on or rotation of the arm. The spring-loaded magnetic arm can be biased away from the hull, and a magnetic attraction between the arm and the metal hull can draw the arm closer towards the hull or into contact with the hull. When a strain on the arm or a rotation of the arm changes to a relaxed or non-attracted position, a separation from the hull surface can be identified.
In another example, the sensor subsystem can emit sound waves for reflection from the hull. When reflected sound waves are detected, the robot can identify the hull presence. When sound waves are not detected, a potential separation from ship may have occurred. The sound waves can be generated by tapping the hull or through the use of a speaker. A microphone or other acoustic detector can detect the sound of the tapping or the reflected sound waves.
In yet another exemplary embodiment, the sensor subsystem can comprise a non-destructive hull inspection system operable about the robot to perform one or more inspections of the hull of the vessel. The non-destructive hull inspection system can be operable with the signal generation subsystem, such that when the inspection system is in operation yet nothing is being detected, or in other words, in the event the inspection system is detected as not inspecting a portion of the hull as it otherwise should, this can indicate a detached state and the signal generation subsystem can provide a distress signal as described below. The non-destructive inspection system can comprise any number of inspection type systems, such as an ultrasonic inspection system, an eddy current detection system, a magnetic field detection system, a displacement gauge system, an optical interferometry system, a paint integrity inspection system, an acoustic emission-based inspection system, and others.
When the robot has identified a potential separation from the ship, or in the event the robot confirms separation from the vessel, the robot can indicate a distressed state, wherein a signal generation subsystem of the robot can generate a distress signal via a distress signal module and can emit/transmit the distress signal with a distress signal emitter. The distress signal can be encrypted if desired. In one aspect, the distress signal generated can be one that causes the robot to take a particular action, one that can be transmitted wirelessly to the vessel, or one that can be broadcast to enable any vessel or land-based receiver to detect the signal. It is contemplated herein that the signal can be any suitable type of signal depending on how and where the signal is being transmitted, such as a wired, wireless, radio, optical, acoustical, or other signal, or a combination of these.
In one exemplary embodiment, the distress signal can comprise a position indicator configured to notify the vessel (or another receiving location) so that an appropriate action can be taken, such as to retrieve the robot. In one aspect, the position indicator can be GPS based, wherein the robot and the vessel GPS systems can communicate back and forth, or otherwise be coordinated, such that one or both of the vessel and robot GPS systems can identify a discrepancy between the relative position of the vessel and the robot. In another aspect, the GPS on the robot can be activated only upon separation and caused to be operable with the signal generation subsystem to allow the distress signal to comprise and transmit the GPS coordinates of the robot. The vessel can be configured to receive a transmitted GPS signal from the robot, thus signaling to the vessel that separation has occurred. In this case, the coordinates can be relayed to the vessel (or any receiver located on the water or on land) to facilitate retrieval of the robot.
In another exemplary embodiment, the distress signal can comprise a signal generated from a satellite phone. The signal generation subsystem can comprise a satellite phone operable to send the distress signal. Again, the signal generation subsystem can be operable with a global positioning system to enable the distress signal to comprise the GPS coordinates of the robot.
In other examples, when the robot detects a potential separation from ship, or confirms separation, the distress signal can comprise an optical beacon (e.g., pulsing light, spotlight, etc.), an audio signal, a flare, etc. Essentially, the robot can be configured to provide an indication of its separation, as well as a signal for locating the robot after separation. Other methods and systems capable of facilitating location of the robot after separation, other than those described herein, will be apparent to those skilled in the art, and are contemplated herein.
In yet other examples, the present technology further comprises various systems and methods to surface the hull robot after a separation from the vessel so as to prevent the robot from sinking and being likely unrecoverable. For example, the robot can be equipped with one or more internal and/or external inflatable buoyancy elements. In other examples, the hull robot can be configured to be inherently buoyant by including or being formed from, at least in part, a buoyant material, such as closed cell foam. It is contemplated that an inherently buoyant robot may also include built-in air bladders, and so forth.
A robot surfacing device can cause the robot to float to the surface in the event the robot becomes separated from the hull. For example, as shown in
In further examples, the robot surfacing device can comprise an inflatable flotation device supported about the robot and operable with an inflation element (e.g., compressed gas tank) in fluid communication with the inflatable flotation device, wherein the inflation element is operable to inflate the inflatable flotation device upon separation of the robot from the hull. For example, inflatable flotation devices in the form of inflatable air bladders or tubes can be supported on the inside or outside of the robot and can be caused to inflate when the attachment state is detached. In the example shown in
The inflatable tubes may at least partially circumscribe a perimeter of the robot body and can be configured to float the robot when inflated.
Referring to
Referring now to
In more detailed examples, the method can include buoying or surfacing the robot to float to a water surface when the attachment state is one of detached. Surfacing the robot can further include inflating an inflatable flotation device coupled to the robot using a compressed gas tank carried by the robot.
In accordance with other examples which have been described in greater detail above, sensing an attachment state of the robot can include optically detecting the presence of the hull using an optical detector; detecting the flow of fluid past the robot using a fluid flow detector; detecting an angular orientation of the robot relative to gravity using a gravity vector detector; detecting a pressure of fluid surrounding the robot using a pressure detector; tracking a location of the robot using a global positioning system device; detecting noise of the vessel using a noise detector; and so forth.
Sensing an attachment state of the robot can further include operating a non-destructive inspection system to inspect the hull of the vessel, and monitoring the output of the inspection system. Under normal operating scenarios, inspection of the hull, and the output by the inspection system thereof, can indicate an attached state of the robot. In the event the output indicates no inspection is taking place when it otherwise should be, and when the inspection system is operating normally, this can indicate a detached state of the robot and the signal generation subsystem (which can be made to be operable with the inspection system) can generate a distress signal, as taught herein.
Referring now to
The system can include a sensor 420 supported on the hull robot and configured to detect an attachment state of the robot relative to the hull, the attachment state comprising at least one of attached and detached. The sensor may be any suitable type of sensor operating in any suitable manner to detect the attachment state, as has been set forth above. A distress module 430 carried by the hull robot can be configured to identify a distress situation when the attachment state of the robot relative to the hull is detached.
In one aspect, the system can include a hull detection analysis module 425 carried by the hull robot can be configured to use the processor to analyze the data obtained by the sensor 420, and/or to compare the data obtained by the sensor with stored data to identify the presence of the hull and/or to determine an attachment state of the robot relative to the hull. In some examples, the distress module 430 can identify the distress situation when the presence of the hull is not identified or detected.
In one embodiment, the detection analysis module 425 can detect a separation from the ship based on an amount of electrical current a cleaning, drive or other subsystem is able to draw. For example, a cleaning subsystem will draw limited to no current when the hull robot is separated from the hull and not generating power as opposed to when the robot is attached to the hull, generating power, and/or actively cleaning the hull. Likewise, a drive system will draw a much lower amount of current (or no current at all) when the robot is separated from the ship as opposed to when the drive subsystem is used to facilitate locomotion of the robot about the hull. Stated differently, the load on the track motors (i.e., the motor current draw) will be measurably different in the situation where the robot is separated from the hull versus the situation where the robot is driving about the hull.
In another embodiment, the detection analysis module 425 can detect a separation from the ship based on an electrical and/or physical load on a drive subsystem. For example, the electrical current draw for a motor driving the track for navigation of the hull robot upon the hull will be markedly different when the track is operating on a hull surface as compared with moving freely in water or in air. Further separation detection examples can include detecting the power being generated by the power scavenging systems, wherein the power generated will likely be little to no power upon separation.
In one aspect, a velocity threshold may exist for passing fluid to actuate drive subsystems, cleaning subsystems, energy extraction devices and so forth. A velocity of passing fluid may be a result of the vessel to which the hull robot is attached being in motion at a velocity meeting or exceeding a pre-determined velocity or the velocity threshold. When the separation from the ship is detected, the fluid flow past the hull robot may decrease below the velocity threshold such that driving and cleaning functions are ceased and energy may be used for emitting the distress signal, inflating buoyancy devices and so forth as has been described.
The methods and systems of certain examples may be implemented in hardware, software, firmware, or combinations thereof The methods disclosed herein can be implemented as software or firmware that is stored in a memory and that is executed by a suitable instruction execution system (e.g., a processor). If implemented in hardware, the methods disclosed herein can be implemented with any suitable technology that is well known in the art.
Also within the scope of this disclosure is the implementation of a program or code that can be stored in a non-transitory machine-readable medium to permit a computer or processor to perform any of the methods described above.
Some of the functional units described in this specification have been labeled as modules, in order to more particularly emphasize their implementation independence. The various modules, engines, tools, etc., discussed herein may be, for example, software, firmware, commands, data files, programs, code, instructions, or the like, and may also include suitable mechanisms. For example, a module may be implemented as a hardware circuit comprising custom VLSI (very large scale integration) circuits or gate arrays, off-the-shelf semiconductors such as logic chips, transistors, or other discrete components. A module may also be implemented in programmable hardware devices such as field programmable gate arrays, programmable array logic, programmable logic devices or the like.
Modules may also be implemented in software for execution by various types of processors. An identified module of executable code may, for instance, comprise one or more blocks of computer instructions, which may be organized as an object, procedure, or function. Nevertheless, the executables of an identified module need not be physically located together, but may comprise disparate instructions stored in different locations which comprise the module and achieve the stated purpose for the module when joined logically together.
A module of executable code may be a single instruction, or many instructions, and may even be distributed over several different code segments, among different programs, and across several memory devices. Similarly, operational data may be identified and illustrated herein within modules, and may be embodied in any suitable form and organized within any suitable type of data structure. The operational data may be collected as a single data set, or may be distributed over different locations including over different storage devices. The modules may be passive or active, including agents operable to perform desired functions.
While the forgoing examples are illustrative of the principles of the present technology in one or more particular applications, it will be apparent to those of ordinary skill in the art that numerous modifications in form, usage and details of implementation can be made without the exercise of inventive faculty, and without departing from the principles and concepts of the technology. Accordingly, it is not intended that the technology be limited, except as by the claims set forth below.
This application claims the benefit of the following provisional patent applications, the contents of each of which are incorporated herein by reference in their entirety: U.S. provisional patent application Ser. No. 61/701,512, filed on Sep. 14, 2012; U.S. provisional patent application Ser. No. 61/701,517, filed on Sep. 14, 2012; U.S. provisional patent application Ser. No. 61/701,523, filed on Sep. 14, 2012; U.S. provisional patent application Ser. No. 61/701,529, filed on Sep. 14, 2012; U.S. provisional patent application Ser. No. 61/701,534, filed on Sep. 14, 2012; and U.S. provisional patent application Ser. No. 61/701,537, filed on Sep. 14, 2012. This application is related to copending nonprovisional U.S. patent application Ser. Nos. 13/769,337, filed on Feb. 17, 2013, and entitled, “Hull Robot for Autonomously Detecting Cleanliness of a Hull”; Ser. No. 13/769,339, filed on Feb. 17, 2013, and entitled, “Autonomous Hull Inspection”; Ser. No. 13/769,342, filed on Feb. 17, 2013, and entitled “Autonomous Hull Navigation”; Ser. No. 13/769,344, filed on Feb. 17, 2013, and entitled, “Hull Cleaning Robot”; and Ser. No. 13/769,346, filed on Feb. 17, 2013, and entitled, “Magnetic Track”, the contents of each of which is hereby incorporated by reference herein in their entirety. This application is also related to the following copending U.S. patent application Ser. No. 12/313,643, filed on Nov. 21, 2008; Ser. No. 12/583,346, filed on Aug. 19, 2009; Ser. No. 12/586,248, filed on Sep. 18, 2009; Ser. No. 12/587,949, filed on Oct. 14, 2009; and Ser. No. 12/800,486 filed on May 17, 2010; the contents of each of which is hereby incorporated herein by reference in their entirety.
Number | Name | Date | Kind |
---|---|---|---|
2104062 | Temple | Jan 1938 | A |
2132661 | Temple | Oct 1938 | A |
2386650 | Bell | Oct 1945 | A |
3088429 | Johannessen | May 1963 | A |
3285676 | Hetteen | Nov 1966 | A |
3439937 | Dixon | Apr 1969 | A |
3554300 | Rosenberg | Jan 1971 | A |
3638600 | Modrey | Feb 1972 | A |
3682265 | Hiraoka et al. | Aug 1972 | A |
3777834 | Hiraoka et al. | Dec 1973 | A |
3906572 | Winn | Sep 1975 | A |
3922991 | Woods | Dec 1975 | A |
3934664 | Pohjola | Jan 1976 | A |
3946692 | Sierra et al. | Mar 1976 | A |
3960229 | Shio | Jun 1976 | A |
3984944 | Maasberg et al. | Oct 1976 | A |
4046429 | Pohjola | Sep 1977 | A |
4079694 | Galinou | Mar 1978 | A |
4119356 | Pohjola | Oct 1978 | A |
4135492 | Heitland | Jan 1979 | A |
4135592 | Wincent | Jan 1979 | A |
4202453 | Wilkes | May 1980 | A |
4251791 | Yanagisawa et al. | Feb 1981 | A |
4401048 | Rogers | Aug 1983 | A |
4444146 | DeWitz et al. | Apr 1984 | A |
4574722 | Orita et al. | Mar 1986 | A |
4674949 | Kroczynski | Jun 1987 | A |
4690092 | Rabuse | Sep 1987 | A |
4697536 | Hirata | Oct 1987 | A |
4697537 | Smith | Oct 1987 | A |
4734954 | Greskovics et al. | Apr 1988 | A |
4736826 | White et al. | Apr 1988 | A |
4788498 | Uemura | Nov 1988 | A |
4789037 | Kneebone | Dec 1988 | A |
4809383 | Urakami | Mar 1989 | A |
4841894 | Nellessen, Jr. | Jun 1989 | A |
4890567 | Caduff | Jan 1990 | A |
4926775 | Andorsen | May 1990 | A |
5048445 | Lever et al. | Sep 1991 | A |
5174222 | Rogers | Dec 1992 | A |
5203646 | Landsberger et al. | Apr 1993 | A |
5249631 | Ferren | Oct 1993 | A |
5253605 | Collins | Oct 1993 | A |
5253724 | Prior | Oct 1993 | A |
5285601 | Watkin et al. | Feb 1994 | A |
5366038 | Hidetsugu et al. | Nov 1994 | A |
5378994 | Novak et al. | Jan 1995 | A |
5435405 | Schempf et al. | Jul 1995 | A |
5569371 | Perling | Oct 1996 | A |
5628271 | McGuire | May 1997 | A |
5831432 | Mohri | Nov 1998 | A |
5849099 | McGuire | Dec 1998 | A |
5852984 | Matsuyama et al. | Dec 1998 | A |
5894901 | Awamura et al. | Apr 1999 | A |
5947051 | Geiger | Sep 1999 | A |
6000484 | Zoretich et al. | Dec 1999 | A |
6053267 | Fisher | Apr 2000 | A |
6064708 | Sakamaki | May 2000 | A |
6102145 | Fisher | Aug 2000 | A |
6125955 | Zoretich et al. | Oct 2000 | A |
6209473 | Jones et al. | Apr 2001 | B1 |
6276478 | Hopkins et al. | Aug 2001 | B1 |
6317387 | D'Amaddio et al. | Nov 2001 | B1 |
6564815 | McGuire | May 2003 | B2 |
6595152 | McGuire | Jul 2003 | B2 |
6698375 | Delfossie | Mar 2004 | B2 |
6698376 | Delahousse et al. | Mar 2004 | B2 |
6792335 | Ross et al. | Sep 2004 | B2 |
6886486 | Van Rompay | May 2005 | B2 |
6886651 | Slocum et al. | May 2005 | B1 |
6974356 | Hobson | Dec 2005 | B2 |
7286214 | Reinersman et al. | Oct 2007 | B2 |
7290496 | Asfar et al. | Nov 2007 | B2 |
7296530 | Bemstein et al. | Nov 2007 | B1 |
7390560 | Wallach | Jun 2008 | B2 |
7496226 | Negahdaripour et al. | Feb 2009 | B2 |
7520356 | Sadegh et al. | Apr 2009 | B2 |
7866421 | Moore et al. | Jan 2011 | B2 |
7934575 | Waibel et al. | May 2011 | B2 |
8214081 | Choi et al. | Jul 2012 | B2 |
8342281 | Rooney, III | Jan 2013 | B2 |
8386112 | Rooney, III | Feb 2013 | B2 |
8393286 | Rooney, III et al. | Mar 2013 | B2 |
8393421 | Kornstein et al. | Mar 2013 | B2 |
8506719 | Holappa et al. | Aug 2013 | B2 |
8723536 | Miyazaki et al. | May 2014 | B2 |
20030000445 | McGuire | Jan 2003 | A1 |
20040089216 | Van Rompay | May 2004 | A1 |
20040133999 | Walton | Jul 2004 | A1 |
20040250934 | Hamdan | Dec 2004 | A1 |
20050027412 | Hobson et al. | Feb 2005 | A1 |
20050156562 | Cohen et al. | Jul 2005 | A1 |
20050199171 | Ecklund | Sep 2005 | A1 |
20050216125 | Huston et al. | Sep 2005 | A1 |
20060175439 | Steur et al. | Aug 2006 | A1 |
20060191457 | Murphy | Aug 2006 | A1 |
20060249622 | Steele | Nov 2006 | A1 |
20060261772 | Kim | Nov 2006 | A1 |
20070089916 | Lundstrom | Apr 2007 | A1 |
20070276552 | Rodocker et al. | Nov 2007 | A1 |
20070284940 | Koolhiran | Dec 2007 | A1 |
20080009984 | Lee et al. | Jan 2008 | A1 |
20080202405 | Kern | Aug 2008 | A1 |
20080276407 | Schnittman | Nov 2008 | A1 |
20080281470 | Gilbert et al. | Nov 2008 | A1 |
20080300821 | Frank et al. | Dec 2008 | A1 |
20080308324 | Moser et al. | Dec 2008 | A1 |
20090078484 | Kocijan | Mar 2009 | A1 |
20090094765 | Osaka et al. | Apr 2009 | A1 |
20090166102 | Waibel et al. | Jul 2009 | A1 |
20090301203 | Brussieux | Dec 2009 | A1 |
20100000723 | Chambers | Jan 2010 | A1 |
20100126403 | Rooney, III et al. | May 2010 | A1 |
20100131098 | Rooney, III et al. | May 2010 | A1 |
20100217436 | Jones et al. | Aug 2010 | A1 |
20100219003 | Rooney, III et al. | Sep 2010 | A1 |
20100238050 | Rhodes et al. | Sep 2010 | A1 |
20110050374 | Dvorak | Mar 2011 | A1 |
20110067615 | Rooney, III et al. | Mar 2011 | A1 |
20110083599 | Kornstein et al. | Apr 2011 | A1 |
20110208417 | Fink et al. | Aug 2011 | A1 |
20110282536 | Rooney, III | Nov 2011 | A1 |
20120006352 | Holappa et al. | Jan 2012 | A1 |
20120215348 | Skrinde | Aug 2012 | A1 |
20140076223 | Smith | Mar 2014 | A1 |
20140076224 | Smith | Mar 2014 | A1 |
20140076225 | Smith | Mar 2014 | A1 |
20140076226 | Smith | Mar 2014 | A1 |
20140077587 | Smith | Mar 2014 | A1 |
20140081504 | Smith | Mar 2014 | A1 |
20140090906 | Kornstein et al. | Apr 2014 | A1 |
Number | Date | Country |
---|---|---|
2405719 | Nov 2000 | CN |
2552648 | May 2003 | CN |
1864944 | Nov 2006 | CN |
101387687 | Mar 2009 | CN |
3611750 | Oct 1987 | DE |
1352056 | Feb 1964 | FR |
2861457 | Apr 2005 | FR |
2948920 | Feb 2011 | FR |
2038721 | Jul 1980 | GB |
2103162 | Feb 1983 | GB |
2165330 | Apr 1986 | GB |
S48-014096 | Feb 1973 | JP |
S49-001434 | Jan 1974 | JP |
S50-012797 | Feb 1975 | JP |
S50-81487 | Jul 1975 | JP |
58-012075 | Jan 1983 | JP |
S58-14096 | Jan 1983 | JP |
S60-131174 | Jul 1985 | JP |
S62-130999 | Aug 1987 | JP |
04-002592 | Jan 1992 | JP |
H05-19086 | Jan 1993 | JP |
06-099888 | Apr 1994 | JP |
08-310384 | Nov 1996 | JP |
H10-16884 | Jan 1998 | JP |
2003025265 | Jan 2003 | JP |
2005-335882 | Dec 2005 | JP |
WO 9907489 | Feb 1999 | WO |
WO 02074611 | Sep 2002 | WO |
WO 02074611 | Sep 2002 | WO |
WO 2005014387 | Feb 2005 | WO |
WO 2010059195 | May 2010 | WO |
WO 2010134022 | Nov 2010 | WO |
WO 2011022037 | Feb 2011 | WO |
WO 2011015786 | Feb 2011 | WO |
WO 2011034558 | Mar 2011 | WO |
WO 2011046592 | Apr 2011 | WO |
WO 2011142800 | Nov 2011 | WO |
WO 2011146103 | Nov 2011 | WO |
WO 2012104109 | Aug 2012 | WO |
Entry |
---|
A Copenhagen Climate Treaty; Version 1.0 Draft; A Proposal for a Copenhagen Agreement by Members of the NGO Community; published Jun. 2009; pp. 1-78 (80 pages total). |
Anti-Fouling Systems; Focus on IMO, International Maritime Organization; UK; 2002; pp. 1-31; http://www.uscg.mil/hq/cg5/cg522/cg5224/docs/FOULING2003.pdf. |
Borchardt; Grooming the Fleet, Biofouling Slows Vessels and Wastes Fuels, so the Navy is Looking at an Underwater Robot to Keep its Hulls Shipshape; Mechanical Engineering; Apr. 2010; pp. 33-35; vol. 132, No. 4. |
Fernandez; NAFTA and Member Country Strategies for Maritime Trade and Marine Invasive Species; Journal of Environmental Management; 2008; pp. 308-321; vol. 89. |
Garelick, et a; RTI International EnSys Energy & Systems, Inc.; Navigistics Consulting; Global Trade and Fuels Assessment—Future Trends and Effects of Designating Requiring Clean Fuels in the Marine Sector: Task Order No. 1; Draft Report; RTI Project No. 0209701.001; Apr. 2006; 82 pages. |
Hismar; Hismar News Report No. 2; 2008; http://hismar.ncl.ac.uk/public—docs/News—Reports/News%20Report%20No2—UNEW.pdf; 4 pages. |
Hismar; Hull Identification System for Maritime Autonomous Robots; http://hismar.ncl.ac.uk/public—docs/HISMAR—Poster.pdf ; 1 page. |
Kohli; Biofouling and Design of a Biomimetic Hull-Grooming Tool; Naval Surface Warfare Center Carderock Division; West Bethesda; MD; NSWCCD-CISD-2007/002; Ship Systems Integration & Design Department Technical Report; Sep. 2007; 38 pages. |
Man; B&W, Basic Principles of Ship Propulsion; Basics of Ship Propulsion; Apr. 2004; pp. 1-30. |
Munk; Fuel Conservation Through Managing Hull Resistance; Motorship Propulsion Conference; Copenhangen; Apr. 26, 2006; pp. 1-10. |
Paik et al.; Condition Assessment of Aged Ships; Proceedings of the 16th International Ship and Offshore Structures Congress; Dec. 31, 2006; pp. 273-283; vol. 2; The 16th International Ship and Offshore Structures Congress, Southampton, UK. |
Preiser et al.; Energy (Fuel) Conservation Through Underwater Removal and Control of Fouling on Hulls of Navy Ships, Naval Research and Development Center, Materials Department, Annapolis. |
U.S. Appl. No. 12/313,643, filed Nov. 21, 2008; James H. Rooney III; office action dated Aug. 25, 2014. |
U.S. Appl. No. 12/583,346, filed Aug. 19, 2009; James H. Rooney III; office action dated Aug. 26, 2014. |
U.S. Appl. No. 13/769,337, filed Feb. 17, 2013; Fraser M. Smith; office action dated Sep. 3, 2014. |
U.S. Appl. No. 13/769,339, filed Feb. 17, 2013; Fraser M. Smith; office action dated Sep. 3, 2014. |
U.S. Appl. No. 13/769,342, filed Feb. 17, 2013; Fraser M. Smith; office action dated Sep. 10, 2014. |
Research and Development Report, Dec. 1975; 52 pages. |
Reed et al; Automatic Ship Hull Inspection Using Unmanned Underwater Vehicles; Proceedings from the 7th International Symposium on Technology and the Mine Problem; Monterey, USA; May 2006; 10 pages. |
Rosenhahn et al; Advanced Nanostructures for the Control of Biofouling: the FP 6 EU Integrated Project AMBIO; Biointerphases; Mar. 2008; Published Feb. 21, 2008; pp. IR1-IR5; vol. 3; No. 1. |
Serene et al; Design of a Remotely Operated Vehicle (ROV) for Underwater Ship Hull Cleaning; National University of Singapore; pp. 1-6; 2003. |
Tallett et al; Potential Marine Fuels Regulations: Impacts on Global Refining; Costs & Emissions; Joint IFQC & IPIECA Roundtable; Impacts of CO2 Emissions form Refining & Shipping; London, England; Oct. 1, 2007; 17 pages. |
Townsin; The Ship Hull Fouling Penalty; Biofouling; Jan. 2003; pp. 9-15; vol. 19 (supplement). |
Vaganay et al; Ship Hull Inspection with the HAUV: US Navy and NATO Demonstrations Results; OCEANS 2006; Sep. 2006; pp. 1-6. |
Yuan et al.; The Design of Underwater Hull-Cleaning Robot; Journal of Marine Science and Application; Jun. 2001; pp. 41-45; vol. 3; No. 1. |
Written Opinion of the International Searching Authority, International Application No. PCT/US2011/000787, Jul. 20, 2011, 7 pgs. (unnumbered). |
Written Opinion of the International Searchign Authority, International Application No. PCT/US2011/000770, Aug. 9, 2011, 5 pgs. (unnumbered). |
Written Opinion of the International Searching Authority, International Application No. PCT/US2010/002163, Oct. 13, 2010, 5 pgs. (unnumbered). |
Written Opinion of the International Searching Authority, International Application No. PCT/US2010/002164. Oct. 8, 2010, 5 pgs. (unnumbered). |
Written Opnion of the International Searching Authority for PCT Application No. PCT/US2009/006122 mailed Feb. 3, 2010 9 (seven pages). |
Written Opinion of the International Searching Authority, International Application No. PCT/US2010/002693, Dec. 9, 2010, 8 pages (unnumbered). |
PCT Application PCT/US2010/02693; filing date Oct. 6, 2010; Raytheon Company; International Search Report mailed Dec. 9, 2010. |
PCT Application PCT/US2011/000787 filing date May 5, 2011; James H. Rooney; International Search Report mailed Jul. 20, 2011. |
PCT Application PCT/US2011/000770; filing date May 3, 2011; James H. Rooney III; INternationa Search Report mailed Aug. 9, 2011. |
PCT Application PCT/US2010/002163; filing date Aug. 4, 2010; James H. Rooney; International Search Report mailed Oct. 13, 2010. |
PCT Application PCT/US2010/002164; filing date Aug. 4, 2010; James H. Rooney; International Search Report mailed Oct. 8, 2010. |
PCT Application PCT/US2009/006122; filing date Nov. 16, 2009; James H. Rooney III; International Search Report mailed Feb. 3, 2010. |
PCT Application PCT/US2013/059552; filing date Sep. 12, 2013; Raytheon Company; International Search Report mailed Dec. 20, 2013. |
PCT Application PCT/US2013/059552; filing date Sep. 12, 2013; Raytheon Company; International Search Report mailed Feb. 21, 2014. |
PCT Application PCT/US2013/059527; filing date Sep. 12, 2013; Raytheon Company; International Search Report mailed Mar. 3, 2014. |
PCT Application PCT/US2013/059548; filing date Sep. 12, 2013; Raytheon Company; International Search Report mailed Apr. 16, 2014. |
PCT Application PCT/US2013/059551; filing date Sep. 12, 2013; Raytheon Company; International Search Report mailed Mar. 10, 2014. |
PCT Application PCT/US2013/059546; filing date Sep. 12, 2013; Raytheon Company; International Search report mailed Jan. 20, 2014. |
PCT Application PCT/US2013/059527; filing date Sep. 12, 2013; Raytheon Company; International Search Report mailed May 13, 2014. |
PCT Application PCT/US2013/059550; filing date Sep. 12, 2013; Raytheon Company; International Search Report mailed Jun. 3, 2014. |
PCT Application PCT/US2013/059548; filing date Sep. 12, 2013; Raytheon Company; International Search Report mailed Jun. 30, 2014. |
EP Application EP09827853; filed Aug. 11, 2011; Raytheon Company; Supplemental European Search Report Apr. 23, 2014. |
U.S. Appl. No. 12/313,643, filed Nov. 21, 2008; James H. Rooney III; office action dated Sep. 17, 2012. |
U.S. Appl. No. 12/583,346, filed Aug. 19, 2009; James H. Rooney III; office action dated Sep. 25, 2012. |
U.S. Appl. No. 12/313,643, filed Nov. 21, 2008; James H. Rooney III; office action issued Apr. 13, 2012. |
U.S. Appl. No. 12/586,248, filed Sep. 18, 2009; James H. Rooney III office action issued May 24, 2012. |
U.S. Appl. No. 12/587,949, filed Oct. 14, 2009; Howard R. Kornstein; office action issued May 25, 2012. |
U.S. Appl. No. 12/800,174, filed May 10, 2010; James H. Rooney III; office action issued Feb. 24, 2012. |
U.S. Appl. No. 12/583,346, filed Aug. 19, 2009; James H. Rooney, III; office action dated Feb. 27, 2013. |
U.S. Appl. No. 12/583,346, filed Aug. 19, 2009; James H. Rooney III; office action dated Feb. 27, 2014. |
U.S. Appl. No. 12/586,248, filed Sep. 18, 2009; James H. Rooney III; office action mailed Dec. 13, 2011. |
U.S. Appl. No. 12/586,248, filed Sep. 18, 2009; James H. Rooney III; Notice of Allowance issued Oct. 24, 2012. |
U.S. Appl. No. 12/587,949, filed Oct. 14, 2009; Howard R. Kornstein; notice of allowance mailed Sep. 21, 2012. |
U.S. Appl. No. 12/800,486, filed May 17, 2010; James H. Rooney III; notice of allowance dated Sep. 27, 2012. |
U.S. Appl. No. 12/800,174, filed May 10, 2010; James H. Rooney III; notice of allowance dated Aug. 17, 2012. |
U.S. Appl. No. 13/313,643, filed Nov. 21, 2008; James H. Rooney III; office action dated Feb. 26, 2014. |
U.S. Appl. No. 13/794,594, filed Mar. 11, 2013; Howard R. Kornstein; office action dated May 1, 2014. |
Hover et al.; A Vehicle System for Autonomous Relative Survey of In-Water Ships; Marine Technology Society Journal; Jul. 2007; pp. 44-55; vol. 41, No. 2; Marine Technology Society, Washington, D.C. |
Menegaldo et al.; Development and Navigation of a Mobile Robot for Floating Production Storage and Offloading Ship Hull Inspection ; IEEE Transactions on Industrial Electronics; Sep. 2009; pp. 3717-3722; vol. 56, No. 9; IEEE Service Center, Piscataway, New Jersey. |
Vaganay et al.; Hovering Autonomous Underwater Vehicle-System Design Improvements and Performance Evaluation Results; 30th International Symposium on Unmanned Untethered Submarine Technology; Jul. 9, 2009; pp. 1-14. |
EP Application 11783852.4; filing date May 5, 2011; Raytheon Company; European Search Report; dated Aug. 18, 2014. |
U.S. Appl. No. 13/794,594, filed Mar. 11, 2013; Howard R. Kornstein; office action dated Oct. 15, 2014. |
U.S. Appl. No. 13/769,344, filed Feb. 17, 2013; Fraser M. Smith; office action dated Oct. 28, 2014. |
U.S. Appl. No. 13/769,339; filed Feb. 17, 2013; Fraser M. Smith; Notice of Allowance mailed Jan. 30, 2015. |
U.S. Appl. No. 13/769,337; filed Feb. 17, 2013; Fraser M. Smith; Notice of Allowance mailed Feb. 10, 2015. |
U.S. Appl. No. 13/794,594; filed Mar. 11, 2013; Howard R. Kornstein; office action dated Mar. 04, 2015. |
U.S. Appl. No. 13/769,344; filed Feb. 17, 2013; Fraser M. Smith; office action dated Mar. 10, 2015. |
U.S. Appl. No. 13/769,342; filed Feb. 17, 2013; Fraser M. Smith; office action dated Mar. 10, 2015. |
U.S. Appl. No. 12/313,643; filed Nov. 21, 2008; James H. Rooney, III; office action dated Apr. 08, 2015. |
U.S. Appl. No. 12/583,346; filed Aug. 19, 2009; James H. Rooney, III; office action dated Apr. 08, 2015. |
Number | Date | Country | |
---|---|---|---|
20140076223 A1 | Mar 2014 | US |
Number | Date | Country | |
---|---|---|---|
61701512 | Sep 2012 | US | |
61701517 | Sep 2012 | US | |
61701523 | Sep 2012 | US | |
61701529 | Sep 2012 | US | |
61701534 | Sep 2012 | US | |
61701537 | Sep 2012 | US |