What Is a Float Switch?
A float switch is one of the simplest and most reliable level devices in the field: a buoyant float that rises and falls with the liquid and mechanically trips a switch at a set height. It gives a discrete on-off signal rather than a continuous reading. This guide explains how a float switch works, where it differs from a level transmitter, and its oil and gas role.
Float Switch in one line: A float switch is a point-level device in which a buoyant float rides on the liquid surface and, when the level reaches a set height, mechanically actuates an electrical switch to open or close a contact. It provides a discrete on-off signal used for alarms, pump control, and interlocks rather than a continuous level value.
How a Float Switch Works
A float switch pairs a buoyant float with a switch mechanism. In a common magnetic design, the float contains a magnet and slides on a stem; as the float rises to the trip height, its magnet actuates a sealed reed switch inside the stem, changing the contact state. Other designs use a hinged float arm that mechanically toggles a microswitch, or a mercury-free tilt element in a tethered float. Because the actuation is mechanical and the switch contacts are sealed, float switches are rugged, need no external power to sense, and fail predictably.
A single float switch detects one threshold - level reached or not reached - and reports it as a discrete contact. Installations often stack several floats on one stem, or use several separate switches, to mark distinct setpoints such as pump-on, pump-off, high-high alarm, and low-low alarm. The contacts wire straight into a discrete input on a PLC or RTU, or directly into a motor control or shutdown circuit.
Where Float Switches Fit in Oil and Gas
Because they are simple and independent of any transmitter's electronics, float switches are widely used as safety and control point-level devices: high-level and high-high shutdown on tanks and vessels, low-level pump protection, and pump start-stop control on sumps and water tanks. They are frequently used as an independent backup to a continuous level transmitter so that a critical high-level trip does not depend on the same instrument that drives normal control.
Their discrete contact wires into a PLC or RTU digital input, or directly into an interlock. A cloud SCADA such as Merobix reads that switch state from the controller over Modbus or DNP3 as a digital status point, so an operator sees a high-level or pump-fault condition and can be alarmed remotely. The float switch does the sensing and, often, the hard-wired trip; SCADA provides the visibility and notification on top of it.
Selecting a Float Switch for the Service
Selection starts with the liquid, not the switch. The float must be buoyant in the actual process fluid, so its rated minimum specific gravity has to sit below the fluid's, with margin for temperature and composition swings; the float's figure is on the manufacturer's datasheet and the fluid's is site-specific. Materials come next - the float, stem, and any gaskets must tolerate the fluid chemistry and temperature - followed by the pressure and temperature rating of the process connection itself.
Electrical selection is the other half. The contact arrangement (normally open, normally closed, or changeover), the contact rating against the real circuit load, and the hazardous-area situation all matter. Reed contacts switching a low-level signal into a controller input are a different duty from contacts breaking an inductive pump-starter coil, and in classified areas the circuit design - intrinsically safe loops or suitably rated equipment - follows the site's area classification drawings and the applicable code, with the design signed off by qualified personnel.
Commissioning Checks That Catch Most Problems
- Verify the float moves freely through its whole travel with no rubbing on the stem, chamber wall, or nearby internals.
- Prove the trip by moving real liquid past the setpoint where the process allows, or by manipulating the float per the site's test procedure, and confirm the contact change at the controller input, not just at the switch.
- Confirm the installed orientation matches the design - many designs are direction-sensitive, and a float assembled inverted trips backwards.
- Check the as-found contact logic against the loop drawing: which state is normal and which is alarm.
- Record the as-left trip level and contact configuration in the loop documentation.
The end-to-end proof in step two is the one most often skipped. A float that clicks convincingly at the switch can still be dead at the controller because of a wiring, polarity, or input-configuration fault, and the entire value of the device is that the trip works when demanded.
Failure Modes and Their Signatures
Float switches fail in a small number of characteristic ways, which makes a signature table useful during troubleshooting:
| Failure mode | Typical signature |
|---|---|
| Float stuck from solids, wax, or scale buildup | No trip despite level clearly past the setpoint |
| Punctured or waterlogged float | Float rides low or sinks; trip late or never |
| Degraded or welded contact | Chattering input, or a contact frozen in one state |
| Process density change | Trip point shifted from the documented level |
| Wiring or input fault | Switch proves good locally but the controller never sees the change |
Because a failed point-level switch is silent until demanded, periodic proof testing at an interval set by the site's procedures is the only way to know it still works. Where the switch protects against a hazardous overfill, the testing discipline and trip philosophy belong with the site's safety instrumented system practice rather than with informal maintenance.
Contact Sense and Fail-Safe Wiring
The safer convention for alarms and trips is a circuit that is closed and energized in the healthy state and opens on alarm. Wired that way, a broken conductor, a lost supply, or a corroded terminal produces an alarm rather than a hidden dead switch, converting the most common wiring failures into detectable events. Which physical contact achieves that depends on whether the float rests above or below its trip point in normal operation, which is why the loop drawing and the site's trip philosophy, not habit, should decide it.
Where a continuous reading also exists from a level transmitter, comparing the switch state against the transmitter's value is a cheap ongoing plausibility check between proof tests: a switch showing dry while the transmitter reads above the trip level is a discrepancy worth a work order, whichever device turns out to be wrong.
Frequently Asked Questions
What is the difference between a float switch and a level transmitter?
A level transmitter reports a continuous, proportional level value across a range. A float switch reports only a discrete on-off state at one set height - reached or not reached. Transmitters drive normal level control and trending; float switches drive alarms, pump start-stop, and safety trips, and are often installed as an independent backup to a transmitter.
Why use a float switch when you already have a level transmitter?
Independence and simplicity. A hard-wired float switch does not share electronics, power, or firmware with the continuous transmitter, so a critical high-level shutdown does not depend on the same device that runs normal control. Its mechanical, low-complexity design also fails in predictable ways, which is valued for safety interlocks and high-high trips.
How does a float switch connect to SCADA?
Its contact closure wires into a discrete (digital) input on a PLC or RTU, which turns it into an on-off status tag. It may also be wired directly into a motor or shutdown circuit for the actual trip. A cloud SCADA then reads that digital status from the controller over a protocol like Modbus or DNP3 to display and alarm the state remotely.
How is a float switch proof tested in service?
By demonstrating the actual trip, not just the electronics: raising real liquid past the setpoint where operations permit, or manipulating the float per the site's written test procedure, while confirming the state change arrives at the controller and any hard-wired trip acts as designed. Bypasses must be applied and removed under the site's procedures, and the interval between tests is set by the site's integrity or safety program, since a point-level switch reveals nothing about its own health between demands.
Why did a float switch's trip point drift?
The usual causes are a change in fluid density, buildup adding mass to the float, or a slow leak waterlogging it. The float trips where its buoyancy balances, so anything that changes fluid density or float weight moves the trip level even though nothing was adjusted. Comparing the trip against an independent continuous level reading identifies the drift; the fix ranges from cleaning to float replacement depending on the cause.
Sources and verification
This page references the protocol specifications published by the organizations below. Editions, product capabilities, and documentation change over time - confirm current requirements and specifications directly with the source.
- Modbus Application Protocol Specification - Modbus Organization
- Overview of DNP3 (IEEE Std 1815) - DNP Users Group
Merobix is not affiliated with, endorsed by, or sponsored by these organizations; their names are used only to identify the standards and products discussed.
Automation services
Need help turning this into a working system?
Merobix integrates SCADA, programs Allen-Bradley and Siemens PLCs, and designs and fabricates industrial control panels.
Meeting requests are reviewed before confirmation.