Cross traffic alert system fault 2019 ford ranger lariat

[Klmb32]

I have a 2019 Ford Ranger Lariat. The issues is with the cross traffic alert system. My driver side taillight got cracked from someone backing into it. Water did get into where the module was and it went bad. I replaced the module and taillights. The driver side works but as for the passenger side it quit working after the driver side module went bad. I used forscan to see what the issue is. The SODL shows up but SODR doesn't. The module is programmed to the truck. I've gone through the wiring including grounds and can't find the problem. The led on the passenger mirror doesn't come on but is getting power.

Sponsored

 

[RangerBill]

Do you have power and ground to the right side BLIS module? Here are the wiring diagrams for the BLIS modules. The right side mirror BLIS lamp isn't working because the right side BLIS module is not working.

 

[RangerBill]

If the power and ground checks out, I would think that the left BLIS module with the water in it may have damaged the right module. Have you checked the right module for water in it?

 

[fjwlobo]

I think the module needs to be programmed to the truck to recognize it. @airline tech may be able to confirm this.

 

[RangerBill]

I think the module needs to be programmed to the truck to recognize it. @airline tech may be able to confirm this.

Yes it does, but the OP states that the left side was programmed. He is now having trouble with the right side, if I am reading him correctly.

 

[fjwlobo]

Yes it does, but the OP states that the left side was programmed. He is now having trouble with the right side, if I am reading him correctly.

Missed it from the OP message.

@Klmb32, You can try switching the modules and see if the problem follows with the module.

This is I information I found online:

There is no difference in the programming between the left and right BLIS module. I have a working right module, plug it into the left module wiring connector, pull the current program with the Autel, and then write the stored programming to the virgin / replacement BLIS module.

It worked. If one has one working BLIS module on a super duty (and likely other Ford trucks), a person can pull the programming from it and use that program to configure the replacement module. The programming is driver side/ passenger side neutral.

 

[Klmb32]

If the power and ground checks out, I would think that the left BLIS module with the water in it may have damaged the right module. Have you checked the right module for water in it?

I did and I swapped the new with the old to see if it would come on and the passenger side still didn't work also there was no water in thw passenger side

 

[Klmb32]

If the power and ground checks out, I would think that the left BLIS module with the water in it may have damaged the right module. Have you checked the right module for water in it?

I did when I replaced the taillights and it was dried

 

[RangerBill]

Have you checked (measured) the grounds and power leads on the passenger side BLIS module?

One other thing to try is to disconnect the battery for a few minutes and see if that resets the BLIS function.

 

[airline tech]

If you run a scan, what code shows up?
Since both BLIS modules tie together, the remaining code (in history) still has the BLIS shutdown.
You should get a code for the Module or a Communication Code for loss of data.

You may need to reload both (modules) Left & Right, which is nothing more than reloading the As-Built Data files - They are VIN # specific.

As another post stated (INCORRECT) Information - They are not the same Left/Right are different As-Built data codes. (Same module for Left / Right) but the As-Built data files are different)

If you have no failure codes, you have some options
Run a Self-Test on both SODL / SODR Modules

You can also try, going into the IPC menu and deselect / select BLIS to see if that brings it back online.

Since you have a confirmed short in the circuit, (SODL) and replaced it - Lets do the following to confirm if the (SODR) is shorted out from that.

So, you can take the new module and install it in the Right, Re-Load the (SODR) to it to confirm if it works, if it does the circuit is good, and then as a (2nd) confirmation of a shorted module - Install the (off) module from the Right and install it on the Left, then Re-Load the Left (SODL) to it, if it does not work then you can confirm the (Module) is internally shorted out.

 

[airline tech]

I did and I swapped the new with the old to see if it would come on and the passenger side still didn't work also there was no water in thw passenger side

If this is installing the Left in the Right position, it is still programmed to see and read as the left, so this is an invalid test.

 

[fjwlobo]

If you run a scan, what code shows up?
Since both BLIS modules tie together, the remaining code (in history) still has the BLIS shutdown.
You should get a code for the Module or a Communication Code for loss of data.

You may need to reload both (modules) Left & Right, which is nothing more than reloading the As-Built Data files - They are VIN # specific.

As another post stated (INCORRECT) Information - They are not the same Left/Right are different As-Built data codes. (Same module for Left / Right) but the As-Built data files are different)

If you have no failure codes, you have some options
Run a Self-Test on both SODL / SODR Modules

You can also try, going into the IPC menu and deselect / select BLIS to see if that brings it back online.

Since you have a confirmed short in the circuit, (SODL) and replaced it - Lets do the following to confirm if the (SODR) is shorted out from that.

So, you can take the new module and install it in the Right, Re-Load the (SODR) to it to confirm if it works and that the water took out both modules and add a (2nd) confirmation of installing the (off) module from the Right and install it on the Left, then Re-Load the Left (SODL) to it, if it does not work then you can confirm the (Module) is internally shorted out.

I new it was a good idea to include you in my response earlier. I'd rather be corrected than for someone to have the wrong information.

Thanks ?

 

[Klmb32]

If you run a scan, what code shows up?
Since both BLIS modules tie together, the remaining code (in history) still has the BLIS shutdown.
You should get a code for the Module or a Communication Code for loss of data.

You may need to reload both (modules) Left & Right, which is nothing more than reloading the As-Built Data files - They are VIN # specific.

As another post stated (INCORRECT) Information - They are not the same Left/Right are different As-Built data codes. (Same module for Left / Right) but the As-Built data files are different)

If you have no failure codes, you have some options
Run a Self-Test on both SODL / SODR Modules

You can also try, going into the IPC menu and deselect / select BLIS to see if that brings it back online.

Since you have a confirmed short in the circuit, (SODL) and replaced it - Lets do the following to confirm if the (SODR) is shorted out from that.

So, you can take the new module and install it in the Right, Re-Load the (SODR) to it to confirm if it works, if it does the circuit is good, and then as a (2nd) confirmation of a shorted module - Install the (off) module from the Right and install it on the Left, then Re-Load the Left (SODL) to it, if it does not work then you can confirm the (Module) is internally shorted out.

I get a 0233 code for lost communication with obstacle B

 

[Klmb32]

If you run a scan, what code shows up?
Since both BLIS modules tie together, the remaining code (in history) still has the BLIS shutdown.
You should get a code for the Module or a Communication Code for loss of data.

You may need to reload both (modules) Left & Right, which is nothing more than reloading the As-Built Data files - They are VIN # specific.

As another post stated (INCORRECT) Information - They are not the same Left/Right are different As-Built data codes. (Same module for Left / Right) but the As-Built data files are different)

If you have no failure codes, you have some options
Run a Self-Test on both SODL / SODR Modules

You can also try, going into the IPC menu and deselect / select BLIS to see if that brings it back online.

Since you have a confirmed short in the circuit, (SODL) and replaced it - Lets do the following to confirm if the (SODR) is shorted out from that.

So, you can take the new module and install it in the Right, Re-Load the (SODR) to it to confirm if it works, if it does the circuit is good, and then as a (2nd) confirmation of a shorted module - Install the (off) module from the Right and install it on the Left, then Re-Load the Left (SODL) to it, if it does not work then you can confirm the (Module) is internally shorted out.

 

[airline tech]

Thats a lot of codes, but I believe most tie into the Lost Com with SODR, which is not getting powered up, so I would try (for elimination T/Shoot) to install and program the new SODL in the SODR position, to ensure you can communicate (as far as wiring) to the Right side.
If you can, then that alone confirms that the current SODR is bad.
If you move the current SODR to the left position and program it, will more than likely provide (Com Loss) and the multiple codes (the same you have now)
By dropping the suspected (Shorted) module this should eliminate some of those codes.

If the above does not provide any positive results, then the shorted SODL melted some wiring with it or shorted another module in the circuit, but my hunch is the opposite side SODR

This is assuming the new SODL and Taillight assembly is good, if bought from a wrecked vehicle it is unknown at this point. (Just a possible)

Sponsored