Back up camera recall FIX?

[KevCuRaoi]

I wonder what hoops Ford will have to jump through to satisfy NHTSA's requirements in order to lift the No Sell Hold on new 2024 xl and XLT

Me too! Now w/ 25s out, I expect that there will be some rebates on 24s once those can be sold.

Sponsored

 

[Hunters Edge]

Me too! Now w/ 25s out, I expect that there will be some rebates on 24s once those can be sold.

Could be, but doubt it. With the difference in the fascia, no knob controls, and the significant price increase I think the 24's won't have a hard sale. I would rather believe majority have deposits on them and waiting to take delivery.

 

[23grayXLT84]

Ahhhh

The replacement didn't show in the parts catalog...but I looked in DOW (parts ordering tool) and NZ6Z-3B436-F is superseded by SZ6Z-3B436-E and NZ6Z-3B437-B has been replaced by SZ6Z-3B437-C.

So info in parts catalog wasn't updated yet...but if you ordered the old #, but would probably automatically reorder the new number for you.

The S in the part number indicates 2025 MY. Just like the N in NZ6Z shows that the part was originally designed for 22 MY.


There are still additional changes for 25 MY Mavericks, but the new designs for 22-24 Mavericks must be related to the updates made for 25 Mavericks? It is sometimes hard to find the "logic" behind the part #s.

Perfect . Basically it sounds like if you order the NZ's you will get the new 25MY SZ's which utilizes upgraded design.

If above is true we should start a CV axles fix confirmed for 22-24s explaining this.

 

[Waterick]

......To save money.....I assume Ford will try to fix it w/a software update. APIM replacement would likely be quite expensive? . ....... ..........I think that there will be a software update first. Then, they will find that that doesn't work. And then there will be a new recall that involves part replacement (or maybe they will offer "extended coverage" on APIM after software update). That's what I think will happen, but we'll see!

As much as I've come to respect your insightful input here and you're usually correct, I think you might be wrong in this case. This is a very high visibility case: stop sale, unsellable inventory, Ford's infinite recalls ECT. Ford must get this right the first time or there will be unmeasurable damage to their reputation/credibility. Hence, why this fix is taking so long, Ford really is trying to get it right the first time here. At least hope that's the case.

 

[KevCuRaoi]

Perfect . Basically it sounds like if you order the NZ's you will get the new 25MY SZ's which utilizes upgraded design.

If above is true we should start a CV axles fix confirmed for 22-24s explaining this.

The NZ6Z's both show 0 in stock. So it only the SZ6Z's can be ordered from Ford.

 

[KevCuRaoi]

As much as I've come to respect your insightful input here and you're usually correct, I think you might be wrong in this case. This is a very high visibility case: stop sale, unsellable inventory, Ford's infinite recalls ECT. Ford must get this right the first time or there will be unmeasurable damage to their reputation/credibility. Hence, why this fix is taking so long, Ford really is trying to get it right the first time here. At least hope that's the case.

I hope so too! But I've seen quite a few other recalls follow this same path... software recall, and then extended coverage "N" program that extends warranty on a certain part for a specific failure.

But I agree, I hope they get the fix right the first time too!

 

[itzyoboipaul]

Hmmmm

I just checked OASIS. This recall is still in "advanced notice" status. Ford has not released full bulletin to dealers detailing what the repair will be yet.....

Either your dealership has access to info Ford hasn't released to other dealerships yet... or they are confusing with a different camera recall..... or they don't know what they are talking about!!

UPDATE: I called him after a few hours and was told you are correct, still advance notice

Not sure why he said there's a part and fix for it when I called this morning

 

[colinl]

UPDATE: I called him after a few hours and was told you are correct, still advance notice

Not sure why he said there's a part and fix for it when I called this morning

not surprising, but could you also go back to your first post and change the thread title? otherwise an army of folks are going to continue to comment as if there actually is a fix.

 

[Glen Baker LLC]

not surprising, but could you also go back to your first post and change the thread title? otherwise an army of folks are going to continue to comment as if there actually is a fix.

I don't believe a lot of folks who start threads, know that they can change the title in order to show an update to the thread.
.At least it seems that way. I don't know how many realize they can edit their post either.

 

[BankableWhee]

My local dealership replaced my Maverick's reverse camera about a year ago when I documented and reported the freezing and lagging issues to them, and unfortunately the replacement camera continues to have the same issues. Anybody else hoping for a fix involving a complementary upgrade to SYNC 3?

 

[23grayXLT84]

The NZ6Z's both show 0 in stock. So it only the SZ6Z's can be ordered from Ford.

I called a dealer today trying to get pricing but all said mine required the NZs with no other options. Didn't feel like discussing it more.

@fordvideoguy would you be able to dig in and confirm if the 25MY CV axles SZ's are indeed replacements for NZ's...hybrid ?

 

[Scott Asheville]

Guys I would ask for empathy for the Ford engineers and QA right now. I used to work in a Fortune 50 data storage company as a software engineer - in advanced research and development. I probably cannot clearly relate how painful a really stubborn field support issue can be when it involves hundreds of thousands of fielded units, many with different revisions of hardware and software, and external vendors.

Over my 20 years there I saw it all. Whenever possible, the managers will all start by denying the problem exists. If that doesn't work, they'll point the finger in any direction possible. An external vendor. A software package the user is running. If you're a software engineer, point at the hardware. If you're a hardware engineer, point at the software.

So after all the finger pointing and attempts at evasion, it lands in your team's desk. Now you have to replicate the problem - which can take months (and going bald from ripping out hair) if it involves bizarrely rare scenarios. Then you have identify the cause of the problem - which can take months. Then you have to fix it - usually the easiest part. But then you have to verify the fix doesn't break all the hundreds or thousands of different combinations of hardware and software in units out in the field. Then you have to get the fix out across the fleet.

Now you cross your fingers and hope that you actually fixed it, that you didn't introduce a new worse problem, and that you will keep your job. Oh, and you have to battle with management to do the right fix. Because management wants the cheap fix.

I've seen this take a year and tens of millions of dollars, and that's just for a (ten million dollar) data storage device. I feel for these guys. It's easy to sit at your keyboard and trash Ford. You should try being the person tasked with resolving a problem like this. I've been there. It is both exhilarating and scary. A wonderful feeling as an engineer after you have fixed it. A horrible feeling when it first drops onto your desk and the entire management chain is riding your ass.

It's also easy to be snarky and say "they should have done it right in the first place". Yea, right genius. You try getting a million lines of code on embedded hardware to be perfect.

 

[Glen Baker LLC]

Guys I would ask for empathy for the Ford engineers and QA right now. I used to work in a Fortune 50 data storage company as a software engineer - in advanced research and development. I probably cannot clearly relate how painful a really stubborn field support issue can be when it involves hundreds of thousands of fielded units, many with different revisions of hardware and software, and external vendors.

Over my 20 years there I saw it all. Whenever possible, the managers will all start by denying the problem exists. If that doesn't work, they'll point the finger in any direction possible. An external vendor. A software package the user is running. If you're a software engineer, point at the hardware. If you're a hardware engineer, point at the software.

So after all the finger pointing and attempts at evasion, it lands in your team's desk. Now you have to replicate the problem - which can take months (and going bald from ripping out hair) if it involves bizarrely rare scenarios. Then you have identify the cause of the problem - which can take months. Then you have to fix it - usually the easiest part. But then you have to verify the fix doesn't break all the hundreds or thousands of different combinations of hardware and software in units out in the field. Then you have to get the fix out across the fleet.

Now you cross your fingers and hope that you actually fixed it, that you didn't introduce a new worse problem, and that you will keep your job. Oh, and you have to battle with management to do the right fix. Because management wants the cheap fix.

I've seen this take a year and tens of millions of dollars, and that's just for a (ten million dollar) data storage device. I feel for these guys. It's easy to sit at your keyboard and trash Ford. You should try being the person tasked with resolving a problem like this. I've been there. It is both exhilarating and scary. A wonderful feeling as an engineer after you have fixed it. A horrible feeling when it first drops onto your desk and the entire management chain is riding your ass.

It's also easy to be snarky and say "they should have done it right in the first place". Yea, right genius. You try getting a million lines of code on embedded hardware to be perfect.

Scott,
I understand what you're saying.
But us current owners and those waiting to buy or take delivery of their 2024 XLT or XL are in the position of knowing that the Maverick Lariat has a functioning system.
FORD and Ford alone decided to cut corners and put a cheaper in-house developed system that obviously isn't working. This problem falls squarely on the shoulders of the person or department that said we can do it as good as Sync only cheaper.

 

[HeyBales]

Interestingly - I never caught a reversing video issue prior to the BCM recall update for taillights.
And probably using camera more then as something new to me.
24MY had everything else already done. Though I wouldn't be surprised if there were more non-recall updates to apply, like new menu item, and I got them at the same time.
After that update - seen many frame drops and a few frame freezes.

 

[KevCuRaoi]

I called a dealer today trying to get pricing but all said mine required the NZs with no other options. Didn't feel like discussing it more.

@fordvideoguy would you be able to dig in and confirm if the 25MY CV axles SZ's are indeed replacements for NZ's...hybrid ?

The part #s for the 25 Mavericks are not the same as the updated parts for 22-24 Mavericks (which also start with SZ6Z).

There are various parts catalogs that dealers can use to look up parts. I looked up parts for my 22 hybrid in ECAT (Ford's electronic catalog). It did NOT show the latest supersession for my CV axles.

So your dealer probably just looked in their catalog and they saw the NZ6Zs.

However, I check on those part #s in DOW (where parts are ordered from Ford). It shows the supersession there. I'll attach some screen shots from DOW that show the "replacing parts":

For 25 hybrid Mavericks:
FWD hybrids SZ6Z-3ZB436-B & SZ6Z-3ZB437-A.
AWD hybrids: SZ6Z-3ZB436-A & SZ6Z-3ZB437-A.

So these are different from the updated parts for the 22-24 Maverick hybrids (SZ6Z-3B436-E & SZ6Z-3B437-C)

Sponsored