A vibrating level switch detects the change in resonance that occurs when liquid or bulk solid covers its fork, rod or blade. It is widely used for high-level alarms, low-level alarms, pump protection and chute blockage detection because it does not require a moving float or a field calibration based only on vessel geometry. However, the word vibrating does not define one universal device. Liquid forks and solids forks use different frequencies, mechanics and sensitivity ranges. Selection must identify the medium, minimum density, viscosity, particle size and expected deposits before a model is approved. The switching point is determined by the sensing element and mounting orientation, not simply by the process connection centreline. Define normal and abnormal level movement, response time, retained material after shutdown and the consequence of a missed or false trip. Review temperature, pressure, corrosion, vibration, washdown and hazardous-area classification. A safety-related alarm also needs a documented fail-safe state and a proof-test method through the final relay or control action. Commission with representative product when practical and record the as-found signal or diagnostic condition before cleaning. These steps distinguish an engineered point-level loop from a switch that only operates during a dry workshop check.
Match the sensor to the medium
State whether the duty is liquid, slurry, granules or powder. Provide minimum density, viscosity, particle size, moisture and credible composition changes.
Check aerated liquid, foam, settling solids and fluidized product separately. Some conditions delay coverage or reduce the mechanical damping needed for a reliable trip.
Define the alarm function
Specify high, high-high, low, low-low or blockage duty, switching elevation, allowed delay and process movement after shutdown.
Separate routine control from independent protection. State relay logic, energized-normal philosophy, power-loss response and any required diagnostic coverage.
Select mounting and insertion
Choose top, side or angled mounting according to flow, deposits and access. Keep the fork away from inlet impact, agitators and structural contact.
Account for the actual switching point and insertion depth. Nozzle length or internal buildup must not leave the active area shielded from the product.
Evaluate buildup and vibration
Describe sticky coating, crystallization and material bridges. A vibrating switch can tolerate some deposits, but heavy or asymmetric buildup may change resonance or prevent clearing.
Distinguish process vibration from genuine coverage. Use approved supports and settings rather than adding arbitrary delays that could weaken alarm response.
Verify construction and electrical interface
Confirm wetted materials, process seal, pressure and temperature ratings, enclosure, cable entry and hazardous-area approval for the exact configuration.
Match relay, transistor or electronic output to the receiving input. Document contact rating, fault state, cable supervision and grounding.
Proof-test the installed loop
Test uncovered and covered states through the PLC alarm and final action using actual product or an approved simulation. Record response and reset behaviour.
Inspect the fork, seal, wiring and mounting before cleaning. Retain as-found evidence and repeat the test after process, set-point or control-logic changes. The interval should follow fouling rate and failure consequence.
Engineering checklist
- Identify liquid or solids duty.
- Use minimum density and worst viscosity.
- Define switching point and stopping margin.
- Check buildup, inlet impact and vibration.
- Specify fail-safe output and fault response.
- Proof-test the complete alarm loop.
Frequently asked questions
Can one vibrating switch handle both liquids and powders?
Only when the manufacturer explicitly rates that design for both duties; liquid and solids sensors normally have different mechanical characteristics.
Does foam operate a tuning fork?
Often not, but dense or sticky foam can affect some sensors and must be tested for the application.
How often should it be proof-tested?
Set the interval from buildup, service history and alarm consequence rather than using one universal calendar period.
Need a project-specific review? Send process data, drawings, photographs and acceptance criteria through our contact page.
