ECU module programming guide using FDRS

[rugedraw]

The DTC is continuous. It comes back after a "Clear and Retest".

Message me the VIN.

Sponsored

 

[rugedraw]

@RyanRick Got your message. You do have a few active faults. See below:

The SSM's and TSB referenced by the codes is attached for you to read through. Seems like you already tried to configure the TRM as mentioned in the TSB, but there is a procedure with the door modules it recommends you can try, too.

Did you update every module you could? You only show the BCM pending and nothing else?

 

[JEB]

The DTC is continuous. It comes back after a "Clear and Retest".

Have you tried resolving the comms error from the other side—resetting the BCMC?

 

[RyanRick]

@RyanRick Got your message. You do have a few active faults. See below:

The SSM's and TSB referenced by the codes is attached for you to read through. Seems like you already tried to configure the TRM as mentioned in the TSB, but there is a procedure with the door modules it recommends you can try, too.

Did you update every module you could? You only show the BCM pending and nothing else?

The ACM is showing as available, but I've already run it several times.

 

[RyanRick]

Have you tried resolving the comms error from the other side—resetting the BCMC?

I have not tried this. How do you reset the BCM? Run the BCMC Configuration task?

 

[rugedraw]

The ACM is showing as available, but I've already run it several times.

The ACM not coming off is normal. Ignore that.

I have not tried this. How do you reset the BCM? Run the BCMC Configuration task?

Clicked the BCMC in the first page of FDRS to open up all the guided routines you can do to it and look for a BCMC reset or reboot procedure.

 

[RyanRick]

@RyanRick Got your message. You do have a few active faults. See below:

The SSM's and TSB referenced by the codes is attached for you to read through. Seems like you already tried to configure the TRM as mentioned in the TSB, but there is a procedure with the door modules it recommends you can try, too.

Did you update every module you could? You only show the BCM pending and nothing else?

I'll try the door module procedures and see what happens.

 

[JEB]

I have not tried this. How do you reset the BCM? Run the BCMC Configuration task?

No. I wouldn’t do that. Click on the BCMC and find the self-test routine. You can also do a module reboot from the service procedures section of FORScan.

 

[RyanRick]

Ok I ran the power door window initialization per TSB 22-2307.

I also ran the self-test "Clear and Retest" for the BCMC and TRM. Does the self test reset the module?

 

[JEB]

Ok I ran the power door window initialization per TSB 22-2307.

I also ran the self-test "Clear and Retest" for the BCMC and TRM. Does the self test reset the module?

Sort of. Run it and see what happens. Might get lucky. I usually use FORScan for this stuff. On-Demand Self Test under the Test section and Module Reboot under the Service section. Both should also be in FDRS.

When you do a network scan, what color is the TRM and BCMC? If green, I wouldn’t worry about it. The DTC might actually be one that isn’t currently causing issues.

 

[RyanRick]

I have three yellow modules in FDRS here are the DTCs:

I've run both SSM 53236 (disconnect battery) and SSM 51352 (TRM configuration).

 

[JEB]

I have three yellow modules in FDRS here are the DTCs:

I've run both SSM 53236 (disconnect battery) and SSM 51352 (TRM configuration).

Yellow is a “permanent” historical code that you can’t clear as far as I know. You can see it, but it isn’t current. It should eventually go away if the same DTC doesn’t show up again. But it will take awhile. If you look at your readout, the first line for the IPC, SCCM and the TRM all came back as having passed.

 

[rugedraw]

I have three yellow modules in FDRS here are the DTCs:

I've run both SSM 53236 (disconnect battery) and SSM 51352 (TRM configuration).

Are there any faults on the dash, or are the codes only in FDRS?

 

[RyanRick]

No codes on the dash. Just this pop up window upon each startup.

 

[JEB]

No codes on the dash. Just this pop up window upon each startup.

I know you did this already, but check the #91 fuse again, preferably with a multimeter set for continuity. I’ve seen this fault with a bad #91 fuse.

Sponsored