pcmhacking.net

I have never had to desolder it chip clip works fine in place.

Interesting I wonder why the 7b/3b didn’t work for me probably the elm327 format. I can try again someday with a j2534. Or avt852.

However you need to program the chip anyway for mileage.

04colyZQ8 wrote: ↑Sat Feb 08, 2025 1:01 pm I have never had to desolder it chip clip works fine in place.

Weird. I tried reading it with a clip, tried it with a pogo probe, and it would return garbled data all the time. Maybe it's different from part number to part number.

04colyZQ8 wrote: ↑Sat Feb 08, 2025 1:01 pm Interesting I wonder why the 7b/3b didn’t work for me probably the elm327 format. I can try again someday with a j2534. Or avt852.

Keep in mind, it only worked on two part numbers. Other part number from the same model year didn't not work and would always return "permission denied".
I was testing with the OBDLink MX+

04colyZQ8 wrote: ↑Sat Feb 08, 2025 1:01 pm I have never had to desolder it chip clip works fine in place.

Interesting I wonder why the 7b/3b didn’t work for me probably the elm327 format. I can try again someday with a j2534. Or avt852.

However you need to program the chip anyway for mileage.

I wonder if it's like writing the vin in ecm's and tcm's where a code clear command prior is usually needed?

Well, I just got another 15951589 BCM and I tried to change the VIN via command and the change wasn't allowed. I suspect it has something to do with the calibration version rather than a part number.

On P/N 15802491 I was able to change the VIN via the command.

04colyZQ8 wrote: ↑Sat Feb 08, 2025 1:01 pm I have never had to desolder it chip clip works fine in place.

Interesting I wonder why the 7b/3b didn’t work for me probably the elm327 format. I can try again someday with a j2534. Or avt852.

However you need to program the chip anyway for mileage.

Which programmer did you use to read the chip in-circuit?