Fluidic Impulse Generator
AssigneeBaker Hughes Incorporated
InventorsRobert Standen, Douglas James Brunskill
Life of this patent
Estimating the term…
Abstract
A device for vibrating tubing as it is inserted into a wellbore is disclosed. The device has a fluidic switch that has no moving parts. The fluidic switch is connected to a piston that oscillates back and forth in a cylinder. The piston is the only moving part. As the piston oscillates, it blocks and unblocks openings in the cylinder or other components. The movement of the piston controls the timing of the oscillation, and also generates an impulse or vibration. The vibration may reduce the friction between the tubing and the wellbore.
Claims20
A vibratory impulse generator assembly comprising:
- a source of fluid flow that provides fluid to a first input;
- a fluidic switch having a first power path and a second power path, wherein the first input provides fluid to the first power path and the second power path;
- a piston in communication with the fluidic switch and positioned within a cylinder;
- and
- an interruption valve positioned inline with a fluid passage, the piston being configured to actuate the interruption valve,
- wherein the first power path is connected to a first side of the cylinder and the second power path is connected to a second side of the cylinder, and wherein the source of fluid also provides fluid to the fluid passage.
A fluidic switch comprising:
- a power input path;
- a connecting power path connected to the power input path;
- a first power path connected to the connecting power path;
- a second power path connected to the connecting power path;
- a first trigger path connected to the connecting power path;
- a second trigger path connected to the connecting power path;
- a first feedback path connected to the connecting power path, the first feedback path being separate from the first trigger path and the second trigger path;
- and
- a second feedback path connected to the connecting power path, the second feedback path being separate from the first trigger path and the second trigger path.
Dependencies are inferred from the claim text.