Cross traffic alert system fault 2019 ford ranger lariat

[Klmb32]

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)

So the first picture I took the driver side taillight assembly and plugged it in at the passenger and vice-versa with the passenger side taillight the passenger side worked but not the driver side so it narrowed down to either thw assembly is bad or thw module itself

Sponsored

 

[RangerBill]

So the first picture I took the driver side taillight assembly and plugged it in at the passenger and vice-versa with the passenger side taillight the passenger side worked but not the driver side so it narrowed down to either thw assembly is bad or thw module itself

It's looking like your passenger side BLIS module is bad then.

 

[Klmb32]

It's looking like your passenger side BLIS module is bad then.

I found my original passenger side taillight that wasn't damaged I plugged the module into it and plug the harness in the SODR showed on the forscan with a code u0534 which is a " not yet calibrated" I've looked over the aftermarket module wires I've counted 6 prongs on it the module has 8 prongs so I'm pretty sure that why it isn't working

 

[airline tech]

So, to be clear as it is somewhat confusing from your posts, I am now understanding you had OEM Taillights, LR got damaged, and you bought a pair of aftermarkets Lt & Rt and the current issue you have is the (aftermarket) is not working on the Right Side.

So, we need to correct that issue, either way, I might have a solution vs replacing the Right assembly again. (if I fully understand the issue and specifics)

Unfortunately, the Wiring Diagrams for the BLIS are lacking (DETAILED) wiring pinouts and if you are not attentive to it, you can get confused.

1. Ref Ranger Bills - Diagram above, 1 item on that diagram is the C4483 & C4484 are not at the Taillamp connectors - They are located just below them.

2. The Taillamp Connectors - Downstream of those connectors are C4471 & C4472 - The ones at the taillamps.

3. No detail is given past those connectors, C4471 & C4472 as it is not part of the chassis wiring and that is the (BLIS) module connector (internal & integrated) to the taillamp assembly itself
I saw it somewhere in a wire print, (listed C #) but that number is not found in a search and for the like of me I cannot locate that diagram again.

4. No detail is given on why the RH side has an extra Ground- (Pins 9 & 10), this is something I have not had time to dig into (Indepth) as I am curious for the need.
I believe this is for (Bulb Outage) Monitor - Not sure yet

So, if you view the following pics (via eBay) - these are the Connectors that are not listed in the manuals.
Note both sides have 6 wires on those connectors
They will be feeds from the Taillamp Connectors C4471 & C4472) to the modules

These are - GUESSES of Pinout

Power - Yellow
Ground - Black
Mirror Indication (power - Output) -(?)
MS Can Bus + (?)
MS Can Bus - (?)
Reverse (Lights) Trigger for the - Cross Traffic (Alert) function of the module (?)

The only way to know for sure would be to split the harness open and see where the BLIS module connector taps into the main taillamp connector, as the wire colors changed from that point, and the manuals do not cover that split-off.
The broken one would be a good candidate for this.
Or Ohm out the pins to confirm location

So, I would look at the pinout on the Taillamp (itself) it appears to be pinned incorrectly, use the OEM as a guide.

Ref: The Module (itself) Pins - 6 vs 8

Note: 1 - These modules also fit a transit, so that may be the reason for it being pinned for 8
I would have to get into the Transit Manual to be sure, but it does not really matter as both sides Left & Right are only using 6 of them.

Note 2: - Pay attention to the OEM connectors from the Ebay posts, note they are pinned exactly the same (location & color)

Note: 3: Note they both are 6 wires and (2 ea.) open cavities on the end of the connector

So, if the wiring pinout does not match the OEM the module is not going to work correctly.
Just re-pin the connector to the correct pinout.

If the aftermarket (Module) is bad and you have a working (OEM) module, why not just swap the module from the OEM to the aftermarket as if I am following your issue correctly.
I am sure (1) of the above solutions will get it working again as we have confirmed that there is power to the Taillamp Assy, and the issue is either the Module or Internal Wiring (pinout) of the Taillamp itself (aftermarket unit)

The most important question is - are the Part Numbers the same Left & Right (BLIS Aftermarket Modules)
and

Are the 6 Pins on the (Aftermarket Module) aligned with the (internal / Intergrated) connector and is there 6 wires on it to match the OEM (exactly) note with the Aftermarket they may be a different color (IDK) the color is not important its the exact pinout from the connector to the module (matching the OEM) as that is what the truck wants to see.



Left Side Connector:

Right Side Connector:

 

[RangerBill]

I found my original passenger side taillight that wasn't damaged I plugged the module into it and plug the harness in the SODR showed on the forscan with a code u0534 which is a " not yet calibrated" I've looked over the aftermarket module wires I've counted 6 prongs on it the module has 8 prongs so I'm pretty sure that why it isn't working

I didn't realize that we were dealing with an aftermarket taillight for the passenger side. If it was mentioned earlier, I missed that.

 

[seasprite]

Personally I would get rid of the aftermarket parts and go with factory. Seen to many problems with non OE electronics.

 

[Big Blue]

Personally I would get rid of the aftermarket parts and go with factory. Seen to many problems with non OE electronics.

Factory parts are expensive. Some people go for aftermarket tailights for the look, not because of damage. This is the first I've heard of this being an issue with aftermarket tailights.

Want I am still a little confused about is, are the BLIS (radar) modules also aftermarket? I did not know those were available other than OEM.

 

[airline tech]

I didn't realize that we were dealing with an aftermarket taillight for the passenger side. If it was mentioned earlier, I missed that.

It was never stated, I deduced it from the posts - not 100% on it - though

 

[seasprite]

I didn't realize that we were dealing with an aftermarket taillight for the passenger side. If it was mentioned earlier, I missed that.

Post 18 is where its mentioned

 

[airline tech]

Ok,

Looked at various Transits and they are mostly wired the same (Transits)
They all use 6 of the 8 - Contact Pins

I imagine the Ranger would be the same (2 ea. of those are Grounds), My assumption is that 1 of those grounds from the BLIS module is the Power Feed Ground, and the other is a (Ground Strap) for the module itself (protection) since it is mounted on plastic.
or (it may possibly be using the (reverse lights) ground as a trigger for the Cross Traffic Alert Function, either way it APPEARS that (2 of the wires are grounds)


By using the wire pinout below (from the Transit) we can POSSIBLY assume that this would be the same on the Ranger - being that they are the same Part Number, but a meter check (resistance) would be needed (pin to pin) continuity to confirm.
Note: Wire colors are different
And this shows that all Communication Data (vehicle status) comes from the MS-Can bus

List of All information that the BLIS receives
FT. Wiper Status, Gear Lever Position, Ignition Status, Park Lamp Status, Vehicle Configutation Data, Vehicle Speed, Vehicle Yaw Rate, Wheel Rotation Data.

Note: This shows the SODL / SODR whereas the Ranger Diagrams do not.

Note: Even the Transit - uses a different Ground Pinout for the BLIS, (Hmm)


2022 Transit (Example)

Ref the Ranger Diagram Below:

In trying to determine the reason for the Right Taillight Assembly to have an internal ground wire difference from the Left Side.
I believe that the when the Right Side gets a Reverse signal, it triggers the Ground to close via Pin 9 - which is spliced with Pin 10 - Pin 10 is used by both sides for BLIS Ground.

So, my theory is that Pin 9 is the Trigger for the BLIS to switch from BLIS to Cross Traffic (CTA)
In other words, All Lighting uses Pin 1 as Ground and the BLIS uses Pin 10 as the BLIS Function Ground and uses Pin 9 (Which is spliced with Pin 10 - On the Right Side (Only) provides the Ground for the CTA function.

This is just a theory as none of the manuals cover this part of the operation and the only thing that makes sense is Pin #9 is a - Trigger from an input and the only thing would be to switch the module from a BLIS Function to CTA Function when it sees Reverse Gear (either from the MS-Can) or seeing Power applied to the Reverse Lights Circuit.

Another Possible Theory and that ties to - Trailer Connected & Cross Traffic, I do not tow but the manuals are not 100% clear as it states both (Active & Deactivated) for CTA with a Trailer Connected. (And if a Message is Displayed) CTA Deactivated - Pin 9 may be taking away the ground from pin 10 when it sees Reverse Input & Trailer Connected
In other words, this could possibly be the way the CTA gets deactivated with a Trailer Connected.
Again - Another (Switched based input - Trigger)

 

[Klmb32]

Factory parts are expensive. Some people go for aftermarket tailights for the look, not because of damage. This is the first I've heard of this being an issue with aftermarket tailights.

Want I am still a little confused about is, are the BLIS (radar) modules also aftermarket? I did not know those were available other than OEM.

Both are OEM I got the new one at ford garage. The taillights are made by Anzo which I never had an issue with them in the past this is a first

 

[Klmb32]

So this is what I got yesterday when I plugged my OEM passenger taillight in

 

[airline tech]

So this is what I got yesterday when I plugged my OEM passenger taillight in

The SODR needs As-Built data loaded to it

If you don't have your As-Built data files go here:

Index - FordServiceInfo.Com (motorcraftservice.com)

Note if you download the file it will be an (AB) file and unreadable, so save it as a PDF file.

Scroll down to your SODL & SODR - Data

SODL = 7C4
SODR = 7C6

Then go to the Forscan (As-Built) SODL & SODR and ensure each line matches the As-Built data you got from the Ford Database.
Make a note of all lines or take a picture or back up the file before you change and write new data. This way if something goes array you can set it back to the previous data.

For ease of finding the lines that do not match - only look at the last 2 characters of each line
as the last 2 of each line are the (checksum) for the data line - if any character is changed on the line the (checksum) will change

The lines that are the most important is the Vin # lines, that is what is triggering the code
But check ALL lines to ensure they match, note SODL & SODR are coded different

An example:
7C6-08-01 - will most likely be 3146-5445-5238 (this is the first 6 of you Vin# in Hex)
(1FTER4) almost all Rangers the first 6 are the same

SODL
7C4-08-01 - Vin# 1-6 (in hex format)
7C4-09-01 - Vin# 7-12 (in hex format)
7C4-10-01 - Vin# 13-17 (in hex format)

SODR
7C6-08-01 - Vin# 1-6 (in hex format)
7C6-09-01 - Vin# 7-12 (in hex format)
7C6-10-01 - Vin# 13-17 (in hex format)

When the dealer performs a PMI- they download the As-Built data from the site above or from the installed module and then load that data onto the new module.
Being that you have swapped modules around, it appears that module data just needs to be loaded and the most likely item its looking for is Vin data

Sponsored