DC Power Connectors

DC Jack Switching Contacts: Battery Disconnect Without Burning the Blade

Tags:

A blade rated for milliamps, in a circuit that draws amps

Most PCB-mount DC jacks include a normally-closed switch contact that opens when a plug is inserted. It exists so a product can detect external power and disconnect an internal battery. It is one of the most misunderstood features on the part.

The switch is a thin stamped blade with light contact force and no wiping action. It is designed for signalling, not for carrying the product’s load current. Designs that route the battery through it work on the bench, pass a short functional test, and fail months later in a way that looks like a dead battery.

This article covers how the switch behaves, what its real rating is, the circuit topologies that use it correctly, and the cases where a proper load switch is the right answer instead.

How the switch is built

Element Construction Consequence
Blade Thin stamped metal, low spring force Low contact force, little current capacity
Contact point Small area, often not gold plated Higher resistance, prone to film growth
Actuation Pushed aside by the plug body Opens once per insertion, with bounce
Wiping Essentially none No self-cleaning; films accumulate

Every one of those properties is the opposite of what a power contact needs. Compare it with the main barrel contact, which is a multi-finger spring with a large area and a wiping action on insertion.

The three states

State Switch position What it means Typical use
No plug Closed No external power Battery path enabled
Plug inserted Open External power present Battery path disabled
Plug partly in Transitioning Ambiguous Must be debounced

The third state is not a curiosity. A plug inserted at an angle, or one that is not fully seated, leaves the switch in an indeterminate condition and the main contacts possibly not yet engaged. Firmware that acts on the first edge will toggle between power sources.

The three wiring mistakes

These are worth naming because each one produces a distinct failure.

Mistake Circuit Failure
Load through the switch Battery → switch → load Blade heats, contact erodes, eventually welds or opens permanently
Switch used as a load switch Switch gates the main supply Logic is inverted; the switch opens when power is applied, so it never acts as intended
Switch left floating Not connected Harmless electrically, but the part pays for a feature nobody uses

The first is by far the most common. It looks logical — “the switch disconnects the battery when external power arrives” — and it destroys the switch.

Why the blade fails under load

Load through the switch Effect Timescale
Milliamps (signal) No measurable degradation Product life
100 mA Slight heating, slow film growth Years
500 mA Noticeable heating, contact resistance rises Months
1–2 A Blade heats significantly; spring relaxes Weeks to months
Above 2 A Welding or erosion at separation Could be immediate

The mechanism is the same runaway described for the main contact, but with far less thermal mass and far less contact area. A blade that loses spring force stops making contact reliably, and the product loses its battery path intermittently — which presents as “the battery is not charging” or “the unit dies when unplugged.”

Correct topology: switch as a signal

The switch should report a condition to something that can act on it, not carry the current itself.

Approach Circuit Advantages Limitations
GPIO sense Switch to a pull-up and a microcontroller input Simplest; firmware decides everything Requires firmware to act; no hardware action on power loss
MOSFET gate drive Switch controls the gate of a P-channel MOSFET in the battery path Fast, hardware-only, no firmware dependency Gate drive design must handle the full battery voltage
Load switch IC Switch enables a dedicated load switch Integrated protection, defined behaviour Extra part cost
Charger status pin Use the charger IC’s own power-good output No jack switch needed at all Only available if the charger provides it

The fourth row is worth checking first. Many charger ICs already report whether input power is present, which makes the jack switch redundant. If the charger has the signal, use it and specify the two-contact jack.

Designing the MOSFET version

The hardware approach is the most robust, and it has three requirements that are often missed.

Requirement Why Common error
Correct MOSFET orientation The body diode must block the direction you want to block Reversed source and drain; the diode conducts the wrong way
Gate pull-up to the battery rail The MOSFET must default to on when no external power is present Pull-up to the external rail, so it fails when unplugged
Gate protection Battery voltage may exceed the gate rating, or transients may Direct connection with no clamp

The second row is the one that produces a product which works on the bench with the supply connected and dies the first time it is unplugged. The gate pull-up must reference the battery, so the battery path is enabled by default and disabled only when the switch is actively pulled the other way.

Debounce and sequencing

Behaviour Requirement Reason
Switch bounce 10–50 ms of stable state The blade bounces on insertion
Power source switchover Break-before-make or make-before-break, decided explicitly Both sources connected momentarily can back-feed
Battery reconnect delay Wait until external power is confirmed stable A brief input glitch should not switch to battery and back
Charge termination Do not disconnect the battery from the charger during charge The switch is on the battery path, not the charger path

The last row is a topology question rather than a firmware one. If the switch disconnects the battery from the whole system, it also disconnects it from the charger, and the battery never charges. The switch must sit in the discharge path, with the charger connected upstream of it.

When a proper load switch is the answer

Condition Jack switch sufficient? Recommendation
Battery current below 100 mA Marginal but workable Signal use, MOSFET for the actual switching
Battery current 100 mA to 2 A No MOSFET or load switch driven by the jack switch
Battery current above 2 A No Load switch with defined current limit
Firmware may not be running when power changes No Hardware path only
Product must survive reverse polarity Not applicable Input protection stage, separate concern

The fourth row is easy to overlook. If the battery path depends on firmware, a product with a hung processor cannot switch to battery. That is exactly the condition where a battery is most needed.

FAQ

Can the jack switch carry the battery current? No. It is a thin blade with low contact force and no wiping action, designed for signalling. Load current heats it, relaxes the spring and eventually destroys the contact.

What is the correct way to use the switch? Wire it to a GPIO or to the gate of a MOSFET that does the actual switching. It reports a condition; it does not carry load.

Why does my product die when unplugged after working on the bench? Usually a MOSFET gate pull-up referenced to the wrong rail. The gate must default to enabling the battery when no external power is present.

Do I need the switch at all if my charger has a power-good pin? No. Use the charger’s signal and specify a two-contact jack without the switch.

Why does the battery never charge? If the switch disconnects the battery from the whole system, it also disconnects it from the charger. The switch belongs in the discharge path only.

How much current can the switch handle safely? Treat it as signal level — milliamps. Above roughly 100 mA the degradation becomes measurable and the failure is a matter of time.