Jiggle syphon

A jiggle syphon (or siphon) is the combination of a syphon pipe and a simple priming pump that uses mechanical shaking action to pump enough liquid up the pipe to reach the highest point, and thus start the syphoning action.

Principle of operation

The jiggle pump consists of a chamber, in line with the end of the pipe that sits in the liquid to be moved. The chamber is somewhat wider than the pipe, and narrows to approximately the pipe diameter at both ends. One end attaches to the pipe, the other end is open to the liquid. Within the chamber is a sphere, denser than the liquid to be pumped, small enough to move freely within the chamber but large enough to not be able to leave the chamber.[1]

To begin with, gravity holds the sphere at the bottom, open, end of the chamber, although hydrostatic pressure will force the liquid up and around the sphere upon immersion. When the pipe is vigorously shaken up and down, the sphere moves upwards, lifting some liquid in the pipe; then when it falls down again, the increased hydrostatic pressure within the pipe (which now has a higher head of fluid in it than the surrounding container) pushes the sphere down and prevents the liquid flowing back. Repeated "jigglings" lift the fluid up the pipe until it reaches the highest point in the pipe, whereupon gravity causes it to start to flow down the other side, and the syphon action will "suck" the liquid through the system. This causes the pressure in the pipe to drop below the hydrostatic pressure in the container, so the sphere is lifted upwards, allowing the liquid to flow.

History
gollark: Maybe I should adapt the potatOS privacy policy as a code license.
gollark: MPL?
gollark: There is also the "secondary processor exemption" thing, which caused the Librem people to waste a lot of time on having a spare processor on their SoC load a blob into the SoC memory controller from some not-user-accessible flash rather than just using the main CPU cores. This does not improve security because you still have the blob running with, you know, full control of RAM, yet RYF certification requires solutions like this.
gollark: It would be freer™, in my opinion, to have all the firmware distributed sanely via a package manager, and for the firmware to be controllable by users, than to have it entirely hidden away.
gollark: So you can have proprietary firmware for an Ethernet controller or bee apifier or whatever, but it's only okay if you deliberately stop the user from being able to read/write it.

See also
  • Syphon for the principles and practice of syphoning.

References
  1. Instructions for building a jiggle syphon Archived 2008-04-06 at the Wayback Machine
This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.