Systems and methods for a robust underwater vehicle
12 claims: 1 independent, 11 dependent
- 1An underwater vehicle, comprising:a hull;an actuation system (408) connected to the hull;and a fin (404) configured to steer the vehicle, characterized in that the fin is connected to the actuation system using a force-limiting coupler (406).
68 paragraphs in 4 sections, as filed
BACKGROUND
0001Underwater vehicles are typically controlled using actuated fins that protrude from the vehicle into the flow field around the hull. If the fins on the vehicle come into contact with a foreign object moving with a different velocity than the vehicle, the inertia of the vehicle can cause extremely high forces to develop on the fin, coupling, and actuation system. In order to prevent transmission of these forces into the structure of the vehicle and limit damage to the actuators driving the fins, there exists a need for a force limiting coupler between the actuation system and the fin.
0002Furthermore, the hull of an underwater vehicle is typically designed and manufactured in separate sections. The separate hull sections typically are joined by metal rings that are bonded to the hull by adhesives or fasteners. However, hull sections made out of composite materials generally cannot accommodate sharp angles as well as metal, making it difficult to use trapezoidal cross section band clamps typically used on torpedoes. Moreover, since underwater vehicles are generally engineered to be similar in density to water, any saved weight can translate to greater buoyancy, greater payload volume, and lower manufacturing and operating costs. Thus, these hull interfaces present an opportunity to design a robust underwater vehicle with a joint geometry that is light, low cost, strong, and relatively rigid.
0003Forward looking sonar arrays also present an opportunity to increase robustness of underwater vehicles. Most forward looking sonars are precariously placed in the front of a vehicle and are often destroyed in the event of a collision. Furthermore, a front-mounted sonar array typically results in a planar-shaped bow section, which may expose the sonar to damage. Moreover, the hydrodynamics of the vehicle are often disrupted due to the planar bow shape and the constraints of the sonar (planar boxes to accommodate planar arrays, etc). Thus, there exists a need to design a robust underwater vehicle with improved protection for forward-facing sonar arrays.
0004<patcit id="pcit0001" dnum="US5540065A"><text>US 5,540,065</text></patcit> discloses a water vehicle with a directional control device comprising a single arm with a multiplicity of fins. <patcit id="pcit0002" dnum="US3818853A"><text>US 3,818,853</text></patcit> discloses a stop permitting the limitation of angular clearance of a rudder blade in a ship. <patcit id="pcit0003" dnum="US6640740B1"><text>US 6,640,740 B1</text></patcit> discloses an unmanned sea vehicle comprising a retractable control device that includes a fin member. <patcit id="pcit0004" dnum="GB2164612A"><text>GB 2164612 A</text></patcit> discloses a vehicle, such as a guided missile, fitted with nozzles that are each coupled to at least two fins, where pivotal movement of a nozzle results in movement of its associated fins about respective pivot axes. <patcit id="pcit0005" dnum="EP0350332A1"><text>EP 0 350 332 A1</text></patcit> discloses a submarine with a large number of individual fins, which are controlled in a way which is dependent on which of them may be in service at a particular time.
SUMMARY
0005Systems and methods for a robust underwater vehicle are described herein.
0006According to one aspect, an underwater vehicle comprises a hull, an actuation system connected to the hull, and a fin configured to steer the vehicle, wherein the fin is connected to the actuation system using a force-limiting coupler.
0007In some embodiments, the force-limiting coupler may be configured to break away from the actuation system upon receiving a threshold force. The force-limiting coupler may be made from bronze, brass, plastic, or any other suitable material.
0008In some embodiments, the force-limiting coupler may comprise a hollow rod with at least one circumferential notch. The circumferential notch may be designed to fracture and break at or above a predetermined force threshold.
0009In alternate embodiments, the force-limiting coupler may comprise a truncated cone with a flange, and the force-limiting coupler may include a score line along the intersection of the flange and the truncated cone. The score line may be designed to fracture, tear, or break at or above a predetermined force threshold. The force-limiting coupler may further comprise a hollow truncated cone attached to the actuation system, wherein the truncated cone with the flange and the hollow truncated cone are aligned axially. The truncated cone with the flange may be configured to push into the hollow truncated cone upon receiving an axial force. In some embodiments, the fin is designed to separate and reconnect to the force-limiting coupler.
0010In some embodiments, the force-limiting coupler may be attached to the fin and/or the actuation system using adhesive, fasteners, live hinges, or any other suitable connector. The force-limiting coupler may be stiff in bending and rotation with respect to the actuation system, but may be designed to fracture, break, tear, or separate from the fin and/or the actuation upon receiving a threshold force. The threshold force may be designed to be below a damage threshold of a component of the underwater vehicle, such as the actuation system.
0011Other objects, features, and advantages of the present invention will become apparent upon examining the following detailed description, taken in conjunction with the attached drawings.
BRIEF DESCRIPTION OF THE FIGURES
0012The systems and methods described herein are set forth in the appended claims. However, for purpose of explanation, several illustrative embodiments are set forth in the following figures. <ul id="ul0001" list-style="none" compact="compact"><li><figref idref="f0001">FIG. 1</figref> is a block diagram depicting an exemplary remote vehicle.</li><li><figref idref="f0002">FIG. 2</figref> is block diagram of an exemplary computer system for implementing at least a portion of the systems and methods described in the present disclosure.</li><li><figref idref="f0003">FIG. 3</figref> depicts one illustrative force-limiting coupler that may be used in an embodiment.</li><li><figref idref="f0004">FIG. 4</figref> depicts a vehicle with a fin attached using a force-limiting coupler, according to one illustrative embodiment.</li><li><figref idref="f0005">FIGS. 5A</figref> and <figref idref="f0006">B</figref> depict one illustrative force-limiting coupler that may be used in an embodiment.</li><li><figref idref="f0007">FIG. 6</figref> depicts a vehicle with a fin attached using a force-limiting coupler, according to one illustrative embodiment.</li><li><figref idref="f0008 f0010">FIGS. 7A-C</figref> depict a vehicle with two hull sections connected using a turnbuckle.</li><li><figref idref="f0011 f0013">FIGS. 8A-C</figref> depict the bow section of a vehicle with slits for a blazed sonar array.</li></ul>
DETAILED DESCRIPTION
0013To provide an overall understanding of the invention, certain illustrative embodiments will now be described. However, it will be understood by one of ordinary skill in the art that the systems and methods described herein can be adapted and modified for other suitable applications and that such other additions and modifications will not depart from the scope hereof.
0014Systems and methods are described herein for a robust underwater vehicle. Examples of force-limiting couplers are described to connect a fin to an actuator system of the underwater vehicle. In order to prevent transmission of potentially damaging forces into the structure of the vehicle and limit damage to the actuators driving the fins, a force limiting coupler can separate from the underwater vehicle upon receiving a force above a predetermined threshold.
0015In some embodiments, the force-limiting coupler may comprise a notched brass tube. In another embodiment, the force-limiting coupler may comprise a scored plastic disk. In each case, the coupler is stiff in rotation and bending until a brittle failure occurs, and the fin is allowed to break away at a controlled force higher than the designed hydrodynamic loading in normal operation but below the damage threshold of other components. The brass tube may be a hexagonal rod with a hollow bore that fastens or is bonded into a pocket in the fin and into the driving shaft from the actuator. The tube between the fin and the actuator may be circumferentially notched to create a stress concentration. The diameter and sharpness of the notch may be designed to cause fracture and therefore loss of strength at a desired bending load. The fin may also be designed to separate and reattach to the force-limiting coupler.
0016In some embodiments, the force-limiting coupler may comprise a truncated cone with a flange. The force-limiting coupler may be machined of a single piece of material and attached by adhesive or fasteners to a fin. An offset mating hollow truncated cone may be attached to the actuator. In some embodiments, the flange of the fin-side cone may have a score line on the flange to create a stress concentration. The depth and sharpness of the score line may be designed to cause fracture, tearing, or breaking at or above a predetermined force. The flange may fasten to the actuator side with living hinges, fasteners, or any other suitable connector. Under bending stress, the cone may break out of the flange by tearing or fracturing at the score line. In such embodiments, the very large diameter score ring may make the fin attachment relatively stiff right up to the breaking point. For example, small deflections at the outer diameter prior to breaking may create only very minor changes in angle of the fin. This geometry may also allow the cones to be manufactured such that there is a gap between them axially. In such embodiments, an axial impact may push the fin-side cone into the actuator-side cone and break the flange free. If the outer end of the fin is designed with a slope relative to the axis, the fin may pivot out of the way once the flange is broken and reduce the force transmitted axially to the actuator, preventing damage.
0017Also described is a robust underwater vehicle outside the scope of the present claims, which comprises a first hull section connected to a second hull section using a threaded turnbuckle. Axial strength members may be composed of carbon fiber composite material and may be joined to the composite hull skin. The axial strength members may also be composed of carbon fiber, fiberglass, quartz, Kevlar, graphene, or any other high strength and/or anisotropic material. The axial strength members may have ends with eyes to accommodate pins that join them to the turnbuckles. Each hull section has a pressure bearing face that butts against its adjacent section(s). Optionally, one of the two sections at each joint may have a tapered lip to guide assembly and support shear at the joint. The hull section may also have features to index the joint alignment rotationally if the hull is circular in cross section.
0018Access to the turnbuckles may be provided from the outside of the hull by creation of openings in the composite skin. These openings may expose the ends of the axial strength members, the turnbuckle, and/or its joining pins. The openings may be covered with fairing pieces when the vehicle is in operation. The joining pins may be removable so that the turnbuckles can be separated from the sections without being completely unscrewed. The pins may be retained by a flap or tab when the turnbuckle is not tensioned. The turnbuckle may pull the sections together axially to a specified preload tension, creating a solid and joined vehicle hull.
0019Bulkheads for structural rigidity and mounting can be included in the hull composite structure and biased to one side of a joint or another so that internal components can be loaded axially into separated sections on the side that does not have the bulkhead. This configuration may significantly increase the size of components that can be loaded, leading to low cost of manufacturing and high packing efficiency of components in the hull.
0020Also described is a robust underwater vehicle outside the scope of the present claims, which includes a sonar array, such as a blazed sonar array, a non-blazed array sonar, or a squinted sonar. The classical blazed array consists of a pair of staves (also referred to herein as transducers) inside a rectangular rubber boot. Most forward looking sonars are precariously placed in the front of a vehicle and are often destroyed in the event of a collision. Furthermore, a front-mounted sonar array typically results in a planar-shaped bow section, which may expose the sonar to damage. Moreover, the hydrodynamics of the vehicle are often disrupted due to the planar bow shape and the constraints of the sonar (planar boxes to accommodate planar arrays, etc).
0021However, blazed array sonars do not typically operate at broadside; they are designed to transmit and receive over a range of squint angles. Blazed array staves can also be placed with a degree of flexibility. In some embodiments, a forward looking blazed sonar array may be positioned to line the sides of a vehicle with staves so that the staves are approximately arranged in a parabola. The array may be protected by hiding the array behind a carbon fiber bow with narrow slits. By being placed in a parabola, the arrangement is more compatible with a low drag bow, rather than a flat planar shape. Also, by arranging the arrays end-to-end rather than stacking them, the hole in the bow becomes longer and narrower, making it more difficult for large objects to impact the arrays. In some embodiments, the staves may be arranged to image in multiple planes. The staves may be configured to image a horizontal plane and a vertical slice. The slits may be sufficiently narrow to provide significant protection to the sonar array while simultaneously allowing each stave sufficient space to image in a two-dimensional plane. The slit may be smaller than a golf ball, or, in some examples, a barnacle-encrusted golf ball.
0022<figref idref="f0001">FIG. 1</figref> is a block diagram depicting an illustrative remote vehicle. The system 100 includes a sonar unit 110 for sending and receiving sonar signals, a preprocessor 120 for conditioning a received (or reflected) signal, and a matched filter 130 for performing pulse compression and beamforming. The system 100 is configured to allow for navigating using high-frequency (greater than about 100 kHz) sonar signals. To allow for such HF navigation, the system 100 includes a signal corrector 140 for compensating for grazing angle error and for correcting phase error. The system 100 also includes a signal detector 150 for coherently correlating a received image with a map. The system 100 may include an on-board navigation controller 170, motor controller 180 and sensor controller 190. The navigation controller 170 may be configured to receive navigational parameters from a GPS/RF link 172 (when available), an accelerometer 174, a gyroscope, and a compass 176. The motor controller 180 may be configured to control a plurality of motors 182, 184 and 186 for steering the vehicle. The sensor controller 190 may receive measurements from the battery monitor 172, a temperature sensor 194 and a pressure sensor 196. The system 100 further includes a central control unit (CCU) 160 that may serve as a hub for determining navigational parameters based on sonar measurements and other navigational and sensor parameters, and for controlling the movement of the vehicle.
0023In the context of a surface or underwater vehicle, the CCU 160 may determine navigational parameters such as position (latitude and longitude), velocity (in any direction), bearing, heading, acceleration and altitude. The CCU 160 may use these navigational parameters for controlling motion along the alongtrack direction (fore and aft), acrosstrack direction (port and starboard), and vertical direction (up and down). The CCU 160 may use these navigational parameters for controlling motion to yaw, pitch, roll or otherwise rotate the vehicle. During underwater operation, a vehicle such as an automated underwater vehicle (AUV) may receive high-frequency real aperture sonar images or signals at sonar unit 110, which may then be processed, filtered, corrected, and correlated against a synthetic aperture sonar (SAS) map of the terrain. Using the correlation, the CCU may then determine the AUV's position, with high-precision and other navigational parameters to assist with navigating the terrain. The precision may be determined by the signal and spatial bandwidth of the SAS map and/or the acquired sonar image. In certain embodiments, assuming there is at least a near perfect overlap of the sonar image with a prior SAS map with square pixels, and assuming that the reacquisition was performed with a single channel having a similar element size and bandwidth, and assuming little or no losses to grazing angle compensation, the envelope would be about one -half the element size. Consequently, the peak of the envelope may be identified with high-precision, including down to the order of about 1/100<sup>th</sup> of the wavelength. For example, the resolution may be less than 2.5 cm, or less than 1 cm or less than and about 0.1 mm in the range direction.
0024As noted above, the system 100 includes a sonar unit 110 for transmitting and receiving acoustic signals. The sonar unit includes a transducer array 112 having a one or more transmitting elements or projectors and a plurality of receiving elements arranged in a row. In certain embodiments the transducer array 112 includes separate projectors and receivers. The transducer array 112 may be configured to operate in SAS mode (either stripmap or spotlight mode) or in a real aperture mode. In certain embodiments, the transducer array 112 is configured to operate as a multibeam echo sounder, sidescan sonar or sectorscan sonar. The transmitting elements and receiving elements may be sized and shaped as desired and may be arranged in any configuration, and with any spacing as desired without departing from the scope of the present disclosure. The number, size, arrangement and operation of the transducer array 112 may be selected and controlled to insonify terrain and generate high-resolution images of a terrain or object. One example of an array 112 includes a 16 channel array with 5 cm elements mounted in a 12 ¾ inch vehicle.
0025The sonar unit 110 further includes a receiver 114 for receiving and processing electrical signals received from the transducer, and a transmitter 116 for sending electrical signals to the transducer. The sonar unit 110 further includes a transmitter controller 118 for controlling the operation of the transmitter including the start and stop, and the frequency of a ping.
0026The signals received by the receiver 114 are sent to a preprocessor for conditioning and compensation. Specifically, the preprocessor 120 includes a filter conditioner 122 for eliminating outlier values and for estimating and compensating for hydrophone variations. The preprocessor further includes a Doppler compensator 124 for estimating and compensating for the motion of the vehicle. The preprocessed signals are sent to a matched filter 130.
0027The matched filter 130 includes a pulse compressor 132 for performing matched filtering in range, and a beamformer 134 for performing matched filtering in azimuth and thereby perform direction estimation.
0028The signal corrector 140 includes a grazing angle compensator 142 for adjusting sonar images to compensate for differences in grazing angle. Typically, if a sonar images a collection of point scatterers the image varies with observation angle. For example, a SAS system operating at a fixed altitude and heading observing a sea floor path will produce different images at different ranges. Similarly, SAS images made at a fixed horizontal range would change if altitude were varied. In such cases, changes in the image would be due to changes in the grazing angle. The grazing angle compensator 142 is configured to generate grazing angle invariant images. One such grazing angle compensator is described in <patcit id="pcit0006" dnum="US8374054B"><text>U.S. Patent Number 8,374,054</text></patcit>, titled "Apparatus and Method for Grazing Angle Independent Signal Detection".
0029The signal corrector 140 includes a phase error corrector 144 for correcting range varying phase errors. Generally, the phase error corrector 144 breaks the image up into smaller pieces, each piece having a substantially constant phase error. Then, the phase error may be estimated and corrected for each of the smaller pieces.
0030The system 100 further includes a signal detector 150 having a signal correlator 152 and a storage 154. The signal detector 150 may be configured to detect potential targets, estimate the position and velocity of a detected object and perform target or pattern recognition. In one embodiment, the storage 154 may include a map store, which may contain one or more previously obtained SAS images real aperture images or any other suitable sonar image. The signal correlator 152 may be configured to compare the received and processed image obtained from the signal corrector 140 with one or more prior images from the map store 154.
0031The system 100 may include other components, not illustrated, without departing from the scope of the present disclosure. For example, the system 100 may include a data logging and storage engine. In certain embodiments the data logging and storage engine may be used to store scientific data which may then be used in post-processing for assisting with navigation. The system 100 may include a security engine for controlling access to and for authorizing the use of one or more features of system 100. The security engine may be configured with suitable encryption protocols and/or security keys and/or dongles for controlling access. For example, the security engine may be used to protect one or more maps stored in the map store 154. Access to one or more maps in the map store 154 may be limited to certain individuals or entities having appropriate licenses, authorizations or clearances. Security engine may selectively allow these individuals or entities access to one or more maps once it has confirmed that these individuals or entities are authorized. The security engine may be configured to control access to other components of system 100 including, but not limited to, navigation controller 170, motor controller 180, sensor controller 190, transmitter controller 118, and CCU 160.
0032Generally, with the exception of the transducer 112, the various components of system 100 may be implemented in a computer system, such as computer system 200 of <figref idref="f0002">FIG. 2</figref>. More particularly, <figref idref="f0002">FIG. 2</figref> is a functional block diagram of a general purpose computer accessing a network. The holographic navigation systems and methods described in this application may be implemented using the system 200 of <figref idref="f0002">FIG. 2</figref>.
0033The exemplary system 200 includes a processor 202, a memory 208, and an interconnect bus 218. The processor 202 may include a single microprocessor or a plurality of microprocessors for configuring computer system 200 as a multi-processor system. The memory 208 illustratively includes a main memory and a read-only memory. The system 200 also includes the mass storage device 210 having, for example, various disk drives, tape drives, etc. The main memory 208 also includes dynamic random access memory (DRAM) and high-speed cache memory. In operation and use, the main memory 208 stores at least portions of instructions for execution by the processor 202 when processing data (e.g., model of the terrain) stored in main memory 208.
0034In some embodiments, the system 200 may also include one or more input/output interfaces for communications, shown by way of example, as interface 212 for data communications via the network 216. The data interface 212 may be a modem, an Ethernet card or any other suitable data communications device. The data interface 212 may provide a relatively high-speed link to a network 216, such as an intranet, internet, or the Internet, either directly or through another external interface. The communication link to the network 216 may be, for example, any suitable link such as an optical, wired, or wireless (e.g., via satellite or 802.11 Wi-Fi or cellular network) link. In some embodiments, communications may occur over an acoustic modem. For instance, for AUVs, communications may occur over such a modem. Alternatively, the system 200 may include a mainframe or other type of host computer system capable of web-based communications via the network 216.
0035In some embodiments, the system 200 also includes suitable input/output ports or may use the Interconnect Bus 218 for interconnection with a local display 204 and user interface 206 (e.g., keyboard, mouse, touchscreen) or the like serving as a local user interface for programming and/or data entry, retrieval, or manipulation purposes. Alternatively, server operations personnel may interact with the system 200 for controlling and/or programming the system from remote terminal devices (not shown in the Figure) via the network 216.
0036In some embodiments, a system requires a processor, such as a navigational controller 170, coupled to one or more coherent sensors (e.g., a sonar, radar, optical antenna, etc.) 214. Data corresponding to a model of the terrain and/or data corresponding to a holographic map associated with the model may be stored in the memory 208 or mass storage 210, and may be retrieved by the processor 202. Processor 202 may execute instructions stored in these memory devices to perform any of the methods described in this application, e.g., grazing angle compensation, or high frequency holographic navigation.
0037The system may include a display 204 for displaying information, a memory 208 (e.g., ROM, RAM, flash, etc.) for storing at least a portion of the aforementioned data, and a mass storage device 210 (e.g., solid-state drive) for storing at least a portion of the aforementioned data. Any set of the aforementioned components may be coupled to a network 216 via an input/output (I/O) interface 212. Each of the aforementioned components may communicate via interconnect bus 218.
0038In some cases, the system requires a processor coupled to one or more coherent sensors (e.g., a sonar, radar, optical antenna, etc.) 214. The sensor array 214 may include, among other components, a transmitter, receive array, a receive element, and/or a virtual array with an associated phase center/virtual element.
0039Data corresponding to a model of the terrain, data corresponding to a holographic map associated with the model, and a process for grazing angle compensation may be performed by a processor 202. The system may include a display 204 for displaying information, a memory 208 (e.g., ROM, RAM, flash, etc.) for storing at least a portion of the aforementioned data, and a mass storage device 210 (e.g., solid-state drive) for storing at least a portion of the aforementioned data. Any set of the aforementioned components may be coupled to a network 216 via an input/output (I/O) interface 212. Each of the aforementioned components may communicate via interconnect bus 218.
0040In operation, a processor 202 receives a position estimate for the sensor(s) 214, a waveform or image from the sensor(s) 214, and data corresponding to a model of the terrain, e.g., the sea floor. In some embodiments, such a position estimate may not be received and the process performed by processor 202 continues without this information. Optionally, the processor 202 may receive navigational information and/or altitude information, and a processor 202 may perform a coherent image rotation algorithm. The output from the system processor 202 includes the position to which the vehicle needs to move to.
0041The components contained in the system 200 are those typically found in general purpose computer systems used as servers, workstations, personal computers, network terminals, portable devices, and the like. In fact, these components are intended to represent a broad category of such computer components that are well known in the art.
0042It will be apparent to those of ordinary skill in the art that methods involved in the systems of a remote vehicle according to an embodiment of the invention may be embodied in a computer program product that includes a non-transitory computer usable and/or readable medium. For example, such a computer usable medium may consist of a read only memory device, such as a CD ROM disk, conventional ROM devices, or a random access memory, a hard drive device or a computer diskette, a flash memory, a DVD, or any like digital memory medium, having a computer readable program code stored thereon.
0043Optionally, the system may include an inertial navigation system, a Doppler sensor, an altimeter, a gimbling system to fixate the sensor on a populated portion of a holographic map, a global positioning system (GPS), a long baseline (LBL) navigation system, an ultrashort baseline (USBL) navigation, or any other suitable navigation system.
0044<figref idref="f0003">FIG. 3</figref> depicts a force-limiting coupler that may be included in one illustrative embodiment. The force- limiting coupler 300 may comprise a hollow tube 302 and a circumerential notch 304.
0045Although the hollow tube 302 is depicted as having a hexagonal shape in <figref idref="f0003">FIG. 3</figref>, the hollow tube 302 may have any suitable cross-section, including, but not limited to, rectangular, circular, oval, or sp lined. The hollow tube 302 may be made out of any suitable material, including, but not limited to, steel, aluminum, brass, bronze, or plastic.
0046The circumferential notch 304 may be located at any location along the length of hollow tube 302. In some embodiments, hollow tube 302 may have more than one circumerential notch. In some embodiments, the notch may follow a non-circumferential path. The circumferential notch 304 may have a predetermined depth, sharpness, and location. In some embodiments, the circumferential notch 304 may be designed to break at a predetermined force threshold. The predetermined force threshold may be determined by a damage threshold of other components of an underwater vehicle, such as the actuation system or the vehicle hull. The hollow tube 302 may be relatively stiff in bending and rotation until breakage occurs.
0047<figref idref="f0004">FIG. 4</figref> depicts a vehicle with a fin attached using a force-limiting coupler, according to one illustrative embodiment. System 400 includes vehicle 402, fin 404, force-limiting coupler 406, and actuation system 408.
0048Vehicle 402 may be any suitable vehicle, including, but not limited to, an AUV, a remotely operated vehicle (ROV), a buoy, an unmanned aerial vehicle (UAV), an autonomous surface vessel, or an exploratory robot. Vehicle 402 may include actuation system 408, which may be any suitable actuation system for controlling fin 404. As an illustrative example, actuation system 408 may comprise a motor or servo for tilting the fin 404 to varying degrees according to control inputs. The fin 404 may be any suitable shape for vehicle 402. Fin 404 may be connected to the actuation system 408 using force-limiting coupler 406. In the illustrative example depicted in <figref idref="f0004">FIG. 4</figref>, the force-limiting coupler 406 is the force-limiting coupler 300 depicted in <figref idref="f0003">FIG. 3</figref>. As discussed above, the force-limiting coupler 406 may comprise a hollow tube with a circumferential notch that may be designed to break at a predetermined force threshold. The predetermined force threshold may be determined by a damage threshold of other components of an underwater vehicle, such as the actuation system 408 or the hull of vehicle 402. The force-limiting coupler 406 may be relatively stiff in bending and rotation until breakage occurs.
0049<figref idref="f0005">FIG. 5A</figref> depicts a force-limiting coupler that may be used in one illustrative embodiment. Force- limiting coupler 500 includes truncated cone 502, flange 504, and scored line 506.
0050The truncated cone 502 and the flange 504 may be made from the same material and machined from a single piece. The truncated cone 502 and the fiange 504 may be made out of any suitable material, including, but not limited to, steel, aluminum, brass, or plastic.
0051In some embodiments, the scored line 506 may be machined at the interface of the truncated cone 502 and the flange 504. In alternate embodiments, the scored line 506 may be machined at any circumference along the flange 504. In some embodiments, flange 504 may have more than one scored line at varying circumferences. The scored line 506 may have a predetermined depth, sharpness, and location. In some embodiments, the scored line 506 may be designed to fracture, tear, break, or separate at a predetermined force threshold. The predetermined force threshold may be determined by a damage threshold of other components of an underwater vehicle, such as the actuation system or the vehicle hull. The truncated cone 502 and/or the flange 504 may be relatively stiff in bending and rotation until breakage occurs.
0052<figref idref="f0006">FIG. 5B</figref> depicts a force-limiting coupler that may be used in one illustrative embodiment. Force- limiting coupler 510 includes truncated cone 512, flange 514, scored line 516, hollow cone 518, connector 520, drive shaft 522, fin 524, and fin root 526.
0053Truncated cone 512, flange 514, and scored line 516 may be substantially similar to truncated cone 502, flange 504, and scored line 506 discussed in relation to <figref idref="f0005">FIG. 5A</figref>. Truncated cone 512 may attach to fin 524 using any suitable connector, such as adhesive or fasteners. In some embodiments, fin root 526 may be used to attach fin 524 to truncated cone 512.
0054Hollow cone 518 may be configured to mate with truncated cone 512. For example, truncated cone 512 may be designed to fit inside hollow cone 518. Hollow cone 518 may be made from the same, or different material as truncated cone 512. Hollow cone 518 may be coupler, the fin 604 may pivot out of the way once the flange is broken and reduce the force transmitted axially to the actuator system 608, preventing damage.
0055<figref idref="f0008 f0010">FIGS. 7A-C</figref> depict a vehicle outside the scope of the present claims, with two hull sections connected using a turnbuckle. <figref idref="f0008">FIG. 7A</figref> depicts system 700 comprising a first hull section 702, a second hull section 704, a turnbuckle 706, a first axial strength member 708, a second axial strength member 710, and turnbuckle pin access holes 712.
0056The axial strength members 708 and 710 may be composed of carbon fiber composite material and may be joined to the composite hull skin. The axial strength members 708 and 710 may have ends with eyes to accommodate pins that join them to the turnbuckles. Access to the turnbuckles may be provided from the outside of the hull through turnbuckle pin access holes 712, which are openings in the composite skin. The access holes 712 may expose the ends of the axial strength members, the turnbuckle, and/or its joining pins. The access holes 712 may be covered with fairing pieces when the vehicle is in operation.
0057The axial strength members 708 and 710 may be configured to mate with threaded turnbuckle 706. The turnbuckle 706 may be configured to pull the hull sections 702 and 704 together axially to a specified preload tension, creating a solid and joined vehicle hull.
0058<figref idref="f0009">FIG. 7B</figref> depicts a top view of system 700, including the first hull section 702, the second hull section 704, and an overlapping section 714. In the system depicted in <figref idref="f0009">FIG. 7B</figref>, first hull section 702 may have a tapered lip to guide assembly and support shear at the joint. Second hull section 704 may be designed to mate with the tapered lip of first hull section 702 in the overlapping section 714. In some embodiments, one or more of the hull sections 702 or 704 may also have features (not shown) to index the joint alignment rotationally if the hull is circular in cross section.
0059<figref idref="f0010">FIG. 7C</figref> depicts a cross-sectional view of system 700, including the first hull section 702, the second hull section 704, carbon fiber plates 718 and 720, and turnbuckle pins 716.
0060Access to the turnbuckle pins 716 may be provided by access holes 712, depicted in <figref idref="f0008">FIG. 7A</figref>. The turnbuckle pins 716 may be removed so that the turnbuckle 706 can be separated from the sections 702 and 704 without being completely unscrewed. The pins 716 may be retained by a flap or tab when the turnbuckle 706 is not tensioned.
0061Each hull section 702 and 704 may have a carbon fiber plate 718 and 720 that butts against its adjacent section(s). The plates 718 and 720 may support their respective hull sections 702 and 704 when the turnbuckle 706 is axially tightened.
0062<figref idref="f0011 f0013">FIGS. 8A-C</figref> depict the bow section of a vehicle outside the scope of the present claims, with slits for a blazed sonar array. <figref idref="f0011">FIG. 8A</figref> depicts system 800 including a front view of the bow section 802, horizontal slits 804, and vertical slit 806.
0063Bow section 802 may be made from carbon fiber, fiberglass, or any other suitable material. Although the slits 804 and 806 are depicted in a "T" pattern in <figref idref="f0011">FIG. 8A</figref>, bow section 802 may include any number of slits in any suitable configuration. Slits 804 and 806 may be aligned with sonar transducers which are contained within the bow section 802 (shown in connection with <figref idref="f0012">FIGS. 8B</figref> and <figref idref="f0013">8C</figref>) and allow the sonar transducers to transmit sonar signals in a 2D plane. For example, horizontal slits 804 may allow their respective sonar transducers to sweep a substantially horizontal plane in front of the bow section 802, while vertical slit 806 may allow its respective sonar transducer to sweep a substantially vertical plane in front of bow section 802. In this manner, the slits 804 and 806 may be designed to provide significant protection to the sonar array while still allowing sonar signals to pass through the bow section 802.
0064<figref idref="f0012">FIG. 8B</figref> depicts a side view of system 800 including bow section 802, horizontal slit 804, horizontal transducer 808, vertical transducer 810, horizontal sonar signal 812, and vertical sonar signal 814.
0065As discussed above, the horizontal slit 804 may allow horizontal transducer 808 to transmit a horizontal sonar signal 812 in a relatively horizontal plane. Similarly, vertical transducer 810 may transmit a vertical sonar signal 814 through vertical slit 806 (not shown in <figref idref="f0012">FIG. 8B</figref>). Horizontal sonar signal 812 and vertical sonar signals 814 are depicted in <figref idref="f0012">FIG. 8B</figref> as illustrative examples and are not intended to represent actual shapes or ranges of sonar sweeps. Transducers 808 and 810 may be any suitable sonar equipment for transmitting and receiving sonar signals, as is typical for use in AUV or ocean applications. Transducers 808 and 810 may be configured to transmit and receive over a range of squint angles.
0066<figref idref="f0013">FIG. 8C</figref> depicts a top view of system 800 including bow section 802, horizontal transducers 808, vertical transducer 810, and horizontal sonar signals 812.
0067As discussed above, slits in the bow section 802 may allow horizontal transducers 808 and vertical transducer 810 to transmit and receive sonar signals through the bow section 802. Horizontal sonar signals 812 are depicted in <figref idref="f0013">FIG. 8C</figref> as illustrative examples and are not intended to represent actual shapes or ranges of sonar sweeps. The transducers 808 and 810 may be shaped to follow the curvature of bow section 802. In some embodiments, horizontal transducers 808 and 810 may be positioned in a substantially parabolic arrangement. In this manner, the slits in bow section 802 may allow the transducers 808 and 810 to image in multiple planes while still providing significant protection to the transducers.
0068It will be apparent to those skilled in the art that such embodiments are provided by way of example only. It should be understood that numerous variations, alternatives, changes, and substitutions may be employed by those skilled in the art in practicing the invention. Accordingly, it will be understood that the invention is not to be limited to the embodiments disclosed herein, but is to be understood from the following claims, which are to be interpreted as broadly as allowed under the law.
Contents4
13 sheets
Sheet 1 Sheet 2 Sheet 3 Sheet 4 Sheet 5 Sheet 6 Sheet 7 Sheet 8 Sheet 9 Sheet 10 Sheet 11 Sheet 12 Sheet 13
Every citation, both ways
| Document | Relation | Office | Cited during |
|---|---|---|---|
| US11597481B2 | Cited by | United States of America | Applicant |
| WO2021242413A3 | Cited by | World Intellectual Property Organization (WIPO) | International search |
| EP0350332A1 | Cites | European Patent Office (EPO) | – |
| EP2469507A1 | Cites | European Patent Office (EPO) | – |
| GB2164612A | Cites | United Kingdom | – |
| GB191502000A | Cites | United Kingdom | – |
| US2727485A | Cites | United States of America | – |
| US3818853A | Cites | United States of America | – |
| US3832965A | Cites | United States of America | – |
| US4158189A | Cites | United States of America | – |
| US4421050A | Cites | United States of America | – |
| US5549065A | Cites | United States of America | – |
| US6640740B1 | Cites | United States of America | – |
119 members in 15 offices
Priority claims9
| Document | Office | Kind | Date |
|---|---|---|---|
| 201361792708 | United States of America | P | |
| 201361792708 | United States of America | P | |
| 201361792708P | United States of America | – | |
| 2014029615 | United States of America | W | |
| 2014029615 | United States of America | W | |
| 201361792708P | – | – | – |
| US201361792708P | – | – | – |
| US2014029615 | – | – | – |
| WO2014US29615 | – | – | – |
Members119
| Document | Office | Kind | |
|---|---|---|---|
| CA2904675A1 | Canada | A1 | |
| CA2904681A1 | Canada | A1 | |
| CA2904785A1 | Canada | A1 | |
| CA2904796A1 | Canada | A1 | |
| CA2904798A1 | Canada | A1 | |
| CA2904807A1 | Canada | A1 | |
| CA3076295A1 | Canada | A1 | |
| CA3108934A1 | Canada | A1 | |
| CA3110814A1 | Canada | A1 | |
| CA3177431A1 | Canada | A1 | |
| US2014259618A1 | United States of America | A1 | |
| US2014261138A1 | United States of America | A1 | |
| US2014272230A1 | United States of America | A1 | |
| US2014272475A1 | United States of America | A1 | |
| WO2014144928A1 | World Intellectual Property Organization (WIPO) | A1 | |
| WO2014144976A1 | World Intellectual Property Organization (WIPO) | A1 | |
| WO2014144982A2 | World Intellectual Property Organization (WIPO) | A2 | |
| WO2014145017A2 | World Intellectual Property Organization (WIPO) | A2 | |
| WO2014145027A2 | World Intellectual Property Organization (WIPO) | A2 | |
| WO2014145055A1 | World Intellectual Property Organization (WIPO) | A1 | |
| CA2907211A1 | Canada | A1 | |
| WO2014151864A1 | World Intellectual Property Organization (WIPO) | A1 | |
| WO2014144928A4 | World Intellectual Property Organization (WIPO) | A4 | |
| US2014328141A1 | United States of America | A1 | |
| US2014345511A1 | United States of America | A1 | |
| WO2014144982A3 | World Intellectual Property Organization (WIPO) | A3 | |
| WO2014145027A3 | World Intellectual Property Organization (WIPO) | A3 | |
| TW201500551A | Taiwan Province of China | A | |
| WO2014145017A3 | World Intellectual Property Organization (WIPO) | A3 | |
| AP2015008757A0 | African Regional Intellectual Property Organization (ARIPO) | A0 | |
| AU2014236813A1 | Australia | A1 | |
| AR095337A1 | Argentina | A1 | |
| AU2014228448A1 | Australia | A1 | |
| AU2014233413A1 | Australia | A1 | |
| AU2014233441A1 | Australia | A1 | |
| AU2014233454A1 | Australia | A1 | |
| AU2014233460A1 | Australia | A1 | |
| AU2014233495A1 | Australia | A1 | |
| SG11201507457SA | Singapore | A | |
| US9180940B2 | United States of America | B2 | |
| EP2969734A1 | European Patent Office (EPO) | A1 | |
| EP2969735A1 | European Patent Office (EPO) | A1 | |
| EP2969736A2 | European Patent Office (EPO) | A2 | |
| EP2969737A2 | European Patent Office (EPO) | A2 | |
| EP2969738A1 | European Patent Office (EPO) | A1 | |
| EP2969739A2 | European Patent Office (EPO) | A2 | |
| EP2971015A1 | European Patent Office (EPO) | A1 | |
| US2016017398A1 | United States of America | A1 | |
| EA201591769A1 | Eurasian Patent Organization (EAPO) | A1 | |
| KR20160026828A | Republic of Korea | A | |
| JP2016512038A | Japan | A | |
| US9321510B2 | United States of America | B2 | |
| JP2016515486A | Japan | A | |
| JP2016515972A | Japan | A | |
| JP2016515973A | Japan | A | |
| AU2014228448B2 | Australia | B2 | |
| MX2015013116A | Mexico | A | |
| JP2016518284A | Japan | A | |
| JP2016519741A | Japan | A | |
| AU2014233460B2 | Australia | B2 | |
| JP2016520810A | Japan | A | |
| US9399503B2 | United States of America | B2 | |
| AU2014233495B2 | Australia | B2 | |
| ZA201506731B | South Africa | B | |
| US9630686B2 | United States of America | B2 | |
| US2017267319A1 | United States of America | A1 | |
| AU2014233454B2 | Australia | B2 | |
| US9776693B2 | United States of America | B2 | |
| AU2014233413B2 | Australia | B2 | |
| EP2969739B1 | European Patent Office (EPO) | B1 | |
| EP3326902A2 | European Patent Office (EPO) | A2 | |
| NO3020034T3 | Norway | T3 | |
| US10000260B2 | United States of America | B2 | |
| JP2018128469A | Japan | A | |
| JP2018135093A | Japan | A | |
| EP3326902A3 | European Patent Office (EPO) | A3 | |
| JP2018158724A | Japan | A | |
| EP2969736B1This record | European Patent Office (EPO) | B1 | |
| JP6434488B2 | Japan | B2 | |
| US2018362121A1 | United States of America | A1 | |
| JP6449230B2 | Japan | B2 | |
| JP6506735B2 | Japan | B2 | |
| EP2969735B1 | European Patent Office (EPO) | B1 | |
| EP3501967A1 | European Patent Office (EPO) | A1 | |
| JP2019154230A | Japan | A | |
| EP3572315A1 | European Patent Office (EPO) | A1 | |
| JP6656302B2 | Japan | B2 | |
| JP2020052053A | Japan | A | |
| JP2020059503A | Japan | A | |
| EP3326902B1 | European Patent Office (EPO) | B1 | |
| JP6691476B2 | Japan | B2 | |
| JP6698516B2 | Japan | B2 | |
| EP2969734B1 | European Patent Office (EPO) | B1 | |
| EP2969737B1 | European Patent Office (EPO) | B1 | |
| CA2904675C | Canada | C | |
| JP6752841B2 | Japan | B2 | |
| JP2020147280A | Japan | A | |
| CA2904798C | Canada | C | |
| EP3744625A1 | European Patent Office (EPO) | A1 | |
| EP3744626A1 | European Patent Office (EPO) | A1 |
67 legal events, as 10 offices reported them to INPADOC
Over the term
Point at a mark for the eventEvents
| Event | Code | Office | |
|---|---|---|---|
| Annual fee paid to national office [announced via postgrant information from national office to epo]GrantedPGFP | PGFP | EP | |
| Annual fee paid to national office [announced via postgrant information from national office to epo]GrantedPGFP | PGFP | EP | |
| Annual fee paid to national office [announced via postgrant information from national office to epo]GrantedPGFP | PGFP | EP | |
| Annual fee paid to national office [announced via postgrant information from national office to epo]GrantedPGFP | PGFP | EP | |
| Annual fee paid to national office [announced via postgrant information from national office to epo]GrantedPGFP | PGFP | EP | |
| Annual fee paid to national office [announced via postgrant information from national office to epo]GrantedPGFP | PGFP | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed because of non-payment of the annual feeLapsedMM | MM | BE | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Patent ceasedCeasedPL | PL | CH | |
| No opposition filedOpposition26N | 26N | EP | |
| No opposition filed within time limitOppositionORIGINAL CODE: 0009261PLBE | PLBE | EP | |
| Information on the status of an ep patent application or granted ep patentGrantedSTATUS: NO OPPOSITION FILED WITHIN TIME LIMITSTAA | STAA | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| No opposition filed against granted patent, or epo opposition proceedings concluded without decisionGrantedR097 | R097 | DE | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Lapsed in a contracting state [announced via postgrant information from national office to epo]LapsedPG25 | PG25 | EP | |
| Deletion acc. to par. 5 (withdrawal of the translation of the ep patent)MK05 | MK05 | AT | |
| Invalidated european patentMG4D | MG4D | LT | |
| Patent invalid in the netherlands as no translation has been filedMP | MP | NL | |
| Entry of ep patent into national phase of norway [publ. of translation]T2 | T2 | NO | |
| European patents granted designating irelandGrantedFG4D | FG4D | IE | |
| Dpma publication of mentioned ep patent grantGrantedR096 | R096 | DE | |
| European patent takes effect as a national patent in ch/liEP | EP | CH | |
| Reference to at number (ep patent validated in austria)REF | REF | AT | |
| Designated contracting statesAK | AK | EP | |
| European patent grantedGrantedFG4D | FG4D | GB | |
| (expected) grantORIGINAL CODE: 0009210GRAA | GRAA | EP | |
| Information on the status of an ep patent application or granted ep patentGrantedSTATUS: THE PATENT HAS BEEN GRANTEDSTAA | STAA | EP | |
| Intention to grant announcedINTG | INTG | EP | |
| Grant fee paidORIGINAL CODE: EPIDOSNIGR3GRAS | GRAS | EP | |
| Despatch of communication of intention to grant a patentORIGINAL CODE: EPIDOSNIGR1GRAP | GRAP | EP | |
| Information on the status of an ep patent application or granted ep patentGrantedSTATUS: GRANT OF PATENT IS INTENDEDSTAA | STAA | EP | |
| Request for extension of the european patent (deleted)DAX | DAX | EP | |
| Request for examination filed17P | 17P | EP | |
| Designated contracting statesAK | AK | EP | |
| Request for extension of the european patentAX | AX | EP | |
| Public reference made under article 153(3) epc to a published international application that has entered the european phaseORIGINAL CODE: 0009012PUAI | PUAI | EP |
Numbers
- Publication
- 2969736
- Publication, DOCDB
- 2969736
- Publication, EPODOC
- EP2969736
- Application
- 147235766
- Application, DOCDB
- 14723576
- Application, EPODOC
- EP20140723576
Titles3
- German
- SYSTEME UND VERFAHREN FÜR EIN ROBUSTES UNTERWASSERFAHRZEUG
- English
- SYSTEMS AND METHODS FOR A ROBUST UNDERWATER VEHICLE
- French
- SYSTÈMES ET PROCÉDÉS POUR UN VÉHICULE SOUS-MARIN ROBUSTE
Classification
- CPC, 34
- B22D31/00
- B63B35/40
- B29C44/3415
- H01M10/4257
- B63B27/16
- B63B27/36
- B63B2027/165
- F17C1/00
- Y10T29/49989
- Y10T29/49893
- Y10T29/49826
- Y10T428/1352
- Y10T29/5176
- Y10T428/1376
- Y10T29/49117
- B63G8/00
- B63G8/39
- B63B3/13
- B63B2035/405
- B63G8/001
- B63G2008/004
- B63G2008/008
- H01M50/138
- B64U80/84
- Y02T70/10
- Y02E60/10
- G01S7/52004
- G01S15/104
- G01S15/107
- G01S15/60
- G01S15/8904
- H01M10/052
- G01S15/02
- G01S15/588
- IPC, 15
- B63G8 00
- B63G8 18
- B63G8 39
- B63B3 13
- F42B19 06
- G10K11 00
- G01S15 10
- G01S15 60
- G01S15 89
- B22D31 00
- B29C44 34
- B63B27 16
- B63B27 36
- F17C1 00
- G01S7 52
Designated states1
- Contracting states, 1
- Türkiye
