Stellantis B1552-2A and SOS Unavailable? The Code Name Is Not the Verdict

B1552: The Code Name Isn’T Proof

Keep normal emergency-call alternatives available until the message is resolved, save B1552-2A and U114F-00 as active or stored, and record any jump-start event. On a truly matched vehicle, the service path checks the overhead-console connector, reconnect behavior, button-edge obstruction and LIN wake state before replacement. The phrase ‘button stuck’ is being revised because Stellantis says several communication disruptions can set it, so the label should not order an overhead console.

The useful tool category here is a compatible starting-battery health and charging check after a jump-start or drain event has been documented, but only after the safe test point and decision are clear. The AUTOOL BT360 is one practical route for that bounded step. BT360 can document the health, cranking and charging condition of a compatible lead-acid starting battery after a drain event; it cannot diagnose LIN communication, prove the overhead console stayed awake, wake a sleeping module correctly or establish STAR-case applicability.

Treat B1552-2A as a witness whose name is misleading. Cross-check what the emergency-call function does now, whether the code is active or stored, whether the overhead console is awake on LIN, and whether a physical connector or button-edge problem is actually present. Only then is replacement even a question.

Quick answer: Keep another emergency-call route available, save active/stored status and check connector, reconnect and LIN wake evidence before replacing the console.

B1552: The Code Name Isn'T Proof — conceptual diagnostic scene
B1552: The Code Name Isn’T Proof

Plan for emergency calling without the roof button

Until service restores the feature, assume the roof SOS button may not place a call. Keep a charged phone accessible and know the local emergency number; do not press the button simply to test emergency services. If an accidental live call begins during service, stop testing and follow the operator’s instructions rather than hanging up without explanation. If a collision or medical emergency is happening, use any reliable alternative immediately. Photograph the exact radio message and check the owner’s manual for the equipped connected-service behavior. An ‘unavailable’ message can describe a lost communication path, account/network limits or hardware conditions, so avoid promising what one repair will restore.

Save active versus stored status

Scan before clearing or disconnecting power. Save B1552-2A and U114F-00 with module, active/stored status and timestamps, along with body-controller, telematics and low-voltage codes. Record whether the car needed a jump, how long it sat, whether the message began afterward and whether interior/map lamps acted strangely. Active means the condition is present at the test moment; stored preserves history. That difference becomes the hinge of Stellantis’s sleep/wake branch.

Do not literalize ‘button stuck’

STAR case S2423000008 Rev. A explicitly says B1552-2A is being revised to remove ‘Button Stuck’ because multiple factors can disrupt communication between the button and body controller path. Therefore, do not pry, lubricate or replace the switch merely because the scanner expands the code that way. Inspect for a real obstruction and observe the button feel, but let connector state and communication behavior testify too. A code description is a clue written for identification, not a confirmed failure analysis.

ObservationWhat it means
B1552 active; connector not lockedCorrect engagement and observe state change
Becomes inactive after 30-second reconnectContinue service path; do not replace by reflex
Active after reconnect; real edge obstruction foundCorrect obstruction carefully, then verify
Changes active to stored only after wakeSleep state explained the code; drain still needs proof

Confirm VIN and equipment outside the model-less bulletin

The STAR communication does not publish a model-year applicability table. That omission matters. Confirm the VIN, overhead-console equipment, radio/telematics configuration and current Service Library procedure before lowering trim or ordering parts. Similar messages on another Stellantis product can have a different architecture or known issue. The case itself says it records prior experience, does not authorize warranty repairs and leaves the technician responsible for the course of action.

Check connector engagement before replacement

On a matched vehicle, Stellantis first has the technician lower the overhead console and verify that the headliner-harness connector is fully engaged and locked. Protect the trim, headliner and restraint zones using the current removal procedure. Look for a backed-out terminal, incomplete latch or evidence of prior accessory work. If locking the connector makes the DTC no longer active, the case allows clearing and reinstalling; the changed connector state is the evidence, not the convenience of having touched it.

Use the 30-second reconnect as a controlled branch

If the code remains active, the documented next branch is to unplug the connector, wait 30 seconds and reconnect it. If the DTC then becomes inactive, Stellantis says to clear it, reinstall and continue with the Service Library rather than replace the console. If it stays active, inspect the SOS-button periphery for plastic flash or film using the care specified in the case. This is a controlled sequence: preserve each before/after state instead of repeatedly cycling connectors until the evidence is ambiguous.

Separate a sleeping LIN channel from a continuing drain

After a battery-drain event, the console may still be asleep. The STAR case describes waking the LIN channel with an equipped console button, or using a key-on/key-off followed by a bus-sleep period of two minutes or more and key-on. This branch is about module state, not proof of a parasitic drain. If the code changes from active to stored after wake-up, clear and verify. If parked current remains excessive after all networks should sleep, perform a proper timed draw diagnosis rather than declaring a sleeping console the drain source.

Verify the message, current draw and next sleep cycle

Verify three separate outcomes: the SOS-unavailable message remains absent, B1552/U114F do not return active, and the vehicle completes another sleep/wake cycle without an abnormal current draw or weak restart. Confirm interior controls still work and trim is secure. The emergency-call function may also depend on subscription, cellular coverage and backend status, so a quiet dashboard alone is not a live-call certification. Escalate through current Stellantis technical support when the documented branches do not resolve the state.

A useful appointment note includes the exact message, VIN/equipment, jump-start history, full code report with active/stored state, connector observations, each controlled state change and a measured sleep-current result if drain is still suspected. That gives the owner both things they need: a dependable way to seek help now and a repair based on communication evidence rather than the unfortunate words ‘button stuck.’

Official references

6 min read
0 commentsSave

Comments 0

Questions, fixes, and real-world diagnostic notes from readers.

Join the discussion

No account required. Your email is never published. Guest ID · CD65CD

Be the first to share a diagnostic result or ask a follow-up question.

Popular Articles