DeusEx
Well-Known Member
Haven't seen a new APIM update since 6.14 rolled out. Guessing this is new in FDRS? @Jeff-NoVA do you have the latest update that changes your GUI icons?
Sponsored
Haven't seen a new APIM update since 6.14 rolled out. Guessing this is new in FDRS? @Jeff-NoVA do you have the latest update that changes your GUI icons?
Yes, I already had the new icons. This latest APIM bumped me up to Sync 1270.Haven't seen a new APIM update since 6.14 rolled out. Guessing this is new in FDRS? @Jeff-NoVA do you have the latest update that changes your GUI icons?
Do you still have the Mongoose?I've been having intermittent issues with BC disengaging randomly for ~1 second when driving. It will say "resume control" then "lane centering not available" and then go right back to BC. It used to happen very infrequently, but now it's been happening almost every time I drive on the highway and sometimes multiple times. Most of the time it recovers, but there have been a few instances where BC doesn't come back until I shut off the car for a while.
This time it happened and BC didn't recover, I got the front facing camera fault (which usually doesn't happen), so I pulled the codes. I got:
U3000(04) from the CMR
U0565(86) from the IPMA
I have seen in multiple threads that issues with the coax cable can cause the front facing camera fault intermittently but the error codes don't seem to line up with that. I was going to pull off the panel behind the rear view mirror to do a quick check on that cable for a sharp bend anyways since it seems like an easy check.
Any other ideas? Do I have a bad module potentially?
Thanks!
YesDo you still have the Mongoose?
CMR code has reported with the 8F software byte a few times. There are a few TSB's linked to some of the codes you car has reported. I went down a rabbit hole looking through a few different pinpoint tests, but without being plugged in with FDRS, it's difficult to troubleshoot the issue. One of the TSB's mentions updating the IPMA to the latest version, and you do have the new version pending, but I think the CMR update you have pending may be the better route to fixing it as per 24-2251. TSB 23-2040 was referenced in some of the codes your car reported, but that TSB asks to update the IPMA and your IPMA software if from 12/23 which is newer than the TSB itself.
Gladly. I'll message you.@rugedraw can you assist me as well with Forscan for BC 1.3?
Updating through FDRS as we speak.Gladly. I'll message you.
Edit: You don't have the write software in place to enable it. The IPMA/PSCM must be updated to the latest version.
Thank you for the help!CMR code has reported with the 8F software byte a few times. There are a few TSB's linked to some of the codes you car has reported. I went down a rabbit hole looking through a few different pinpoint tests, but without being plugged in with FDRS, it's difficult to troubleshoot the issue. One of the TSB's mentions updating the IPMA to the latest version, and you do have the new version pending, but I think the CMR update you have pending may be the better route to fixing it as per 24-2251. TSB 23-2040 was referenced in some of the codes your car reported, but that TSB asks to update the IPMA and your IPMA software if from 12/23 which is newer than the TSB itself.
I'm listing everything FYI, but I'd try to update the CMR and then run the procedure outlined in SSM 51776.
Yes, but who knows when they'll get sent?Thank you for the help!
I'll grab a FDRS license this weekend and try that out. Really hoping it's just a software issue and not a hardware issue.
Do those module updates ever come via OTAs?
Yes, that would help! No major rush though. I won't be able to get to it till the weekend.Yes, but who knows when they'll get sent?
No guarantee this will fix it, but with FDRS, you'll be able to run the pinpoint tests to see if you can trace the issue if it is hardware related. I can get you the pin point tests associated with the codes if you need them.
Service advisor didn’t even take my VIN and seemed annoyed that’d I’d even ask for a loaner since I didn’t schedule this well in advance.SOBDMC: P0D1B:00; This DTC sets when the SOBDMC receives a LIN message indicating that the system is unable to determine the position of the High Voltage Battery Coolant Control Valve "B".
What did the service advisor tell you when you asked them?