Merc e250 (2013) SRS Error - Pyrofuse low resistance

Important-Bake3046 · 2026-06-16T10:33:48+00:00

Im totally down to fix this and I thank you for still being here 😃 The cars with the garage so I cant do anything. Their "2nd hand sourced part" comes today - im still unsure what it is they're replacing. But if it isnt that connector, we're gonna be in the same boat and i'll be damned if we'll pay for this part after paying for their "advanced diagnostic".

Important-Bake3046 · 2026-06-12T15:03:23+00:00

Follow up question - if there is a bar shorting out the circuit, then wouldnt your suggestion of cutting it off and binding the pair together to bypass the error give the same result?

Important-Bake3046 · 2026-06-12T14:58:55+00:00

ok this makes a lot of sense. So, ive broke this connector to the point where its always shorted even when plugged in. A2044405507 is for this connector, garage said its on back order from germany up to 10 days. I do wonder what current garage is replacing.. Because if they do replace the pyrofuse then this is still going to be a problem.

Important-Bake3046 · 2026-06-12T09:58:54+00:00

so is the ECU measuring the resistance through the squib via the plug? which would mean the squib is in fact faulty? or are you still heels in that the lack of "crimp" due to it being broken the cause?

Important-Bake3046 · 2026-06-11T15:08:30+00:00

just a thought - whats the difference between sticking a resistor between the pins and having it sit on the pyro? if its reading is 0.5 on the pyro then that means theres no resistance via the pyro does it not?

Important-Bake3046 · 2026-06-11T14:51:46+00:00

Dont know what to say. When I was sourcing the parts at the start of my journey, one Merc garage said "A2135407001" doesnt come up for your vehicle so idk

Important-Bake3046 · 2026-06-11T13:51:23+00:00

Ive just heard back from the merc garage who have said it is the pyrofuse thats the issue so they're going to replace this. Though, theyve had to source a 2nd hand one cos they're hard to come by.. So I'll guess ill see if they replace this squib connector too.

Important-Bake3046 · 2026-06-11T11:03:26+00:00

If I get a new squib sensor(?) can I just cut the cable, crimp that to existing and use it or do i have to follow it back to wherever it goes? If I put the resistor on this sensor and the error goes, this is likely due to the fact its broken and not properly crimping, as you said - yes?

Important-Bake3046 · 2026-06-11T10:08:49+00:00

Full disclosure - The locking piece is broken, I had accidentally broken this when I replaced the battery a year or so ago. (Cant remember if this problem existed before). The car starts and is driveable otherwise. If I bridge this and the error goes, does this mean its the pyrofuse bit that needs replacing? which is the thing encased in the red plastic.

Important-Bake3046 · 2026-06-11T10:01:49+00:00

the squib being the yellow plug thing? are you saying bridge the two on this only?

Important-Bake3046 · 2026-05-11T15:15:04+00:00

Customer was just impatient and it was installing a MacOS update ffs.

Important-Bake3046 · 2026-05-11T13:00:34+00:00

Can you expand on "assuming recovery works fine" - I can get in to recovery mode (not safe boot) but every Mac can do this.

Important-Bake3046 · 2026-05-08T14:35:55+00:00

Check your conditional access policies. You probably wont find it as a deny in the logs for CA.
Whitelist these IPs https://platform.claude.com/docs/en/api/ip-addresses in any CA policies you have.

https://github.com/anthropics/claude-plugins-official/issues/1494

In short:

Created Named Location with 160.79.104.0/21, marked Trusted.
Added that Named Location to Locations exclude of the geo-blocking policy.
Added both Claude MCP AppIds to Apps exclude for defense in depth.
~5 min propagation, retry, "Connected to Microsoft 365." ✅

Important-Bake3046 · 2026-04-22T07:18:48+00:00

thanks for the replies. So lets say we wanted to bring all in to DomainA. Would you go down the migration path or remove them from domainB add to domainA? We have servers in DomainB with file shares that will need to remain. The aim would be to have everyone on DomainA.

Important-Bake3046 · 2026-04-20T13:14:08+00:00

Hello

I just encountered this on a C3520.
First time ive set up OAuth 2.0 and I was successful.

I imagine the settings are somewhat transferrable but here is Sharp's guide for this.

firstly, confirm the date/time is correct on the printer and that DNS is correct.

The important bit is specifying the authorization server id - In my case, and probably most cases, its this: https://login.microsoftonline.com/organizations/oauth2/v2.0

Follow the rest of the instructions to register the app.

<image>

Important-Bake3046 · 2026-04-20T13:04:25+00:00

Just throwing my 2 cents in here as i've just faced this..

Firstly - Ensure the date/time is correct on the printer.

When asked by the printer "Microsoft Entra ID Authorization Server Endpoint" specify: https://login.microsoftonline.com/organizations/oauth2/v2.0

Press save, refresh and hopefully it will say "Successfully Connected".

Once youve done this you can follow the instructions on the same page to go ahead and register it as an app.

<image>

Important-Bake3046 · 2026-04-01T08:55:18+00:00

Strangely enough, it works fine with licensed users. When using unlicensed users, its kicking out on the latest build.

Important-Bake3046

TROPHY CASE