mazda cx5 eps invalid data received from image processing module
#1
mazda cx5 (2015) eps invalid data received from image processing module
Try as I may I can't clear the code U053B:820A which apparently is something to do with the EPS. Anyone able to shed light on what the problem may be? There are other codes that clear without issue although they keep coming back which I presume is linked to this 1. It's an absolute mystery as the system appears to be working normally. Apart from the auto high beam function.
Last edited by MJ81; 02-06-2023 at 02:19 PM. Reason: Missing Information
#2
Welcome to the forum.
Well, the first advice is to use a true scanning (professional) device directly connected to the OBDII Diagnostic connector.
After you have done that re-check for DTC also go into pending DTC which many blue tooth devices will not allow. Then go to the monitors and note their state of readiness. Nots everything you find than completely clear ll history in all files and cycle engine at least one time and then recheck using the same process.
Well, the first advice is to use a true scanning (professional) device directly connected to the OBDII Diagnostic connector.
After you have done that re-check for DTC also go into pending DTC which many blue tooth devices will not allow. Then go to the monitors and note their state of readiness. Nots everything you find than completely clear ll history in all files and cycle engine at least one time and then recheck using the same process.
#3
Welcome to the forum.
Well, the first advice is to use a true scanning (professional) device directly connected to the OBDII Diagnostic connector.
After you have done that re-check for DTC also go into pending DTC which many blue tooth devices will not allow. Then go to the monitors and note their state of readiness. Nots everything you find than completely clear ll history in all files and cycle engine at least one time and then recheck using the same process.
Well, the first advice is to use a true scanning (professional) device directly connected to the OBDII Diagnostic connector.
After you have done that re-check for DTC also go into pending DTC which many blue tooth devices will not allow. Then go to the monitors and note their state of readiness. Nots everything you find than completely clear ll history in all files and cycle engine at least one time and then recheck using the same process.
#4
Those that work well run several hundred dollars. Unfortunately, there are so many BS and junk out there that access the OBDII and CAN-bus via blue tooth and even directly connected unless you plan on doing more future Diagnostic work it may be better to simply have a service shop dp the scanning?
You may invest in what you think will work and then find you are right back here with asking the same information?
I invested in a NEW Solus about 2 years ago and it was 600 USD plus I get all the latest update and software for the next 2 more years.
ASE
You may invest in what you think will work and then find you are right back here with asking the same information?
I invested in a NEW Solus about 2 years ago and it was 600 USD plus I get all the latest update and software for the next 2 more years.
ASE
#5
Sounds like it could be some kind a bad/loose sensor code . It could very well be a bad /corroded, loose connection somewhere. It is going to be cheaper to get a real Mazda tech with the proper tools and experience to diagnose and fix it. A good scan tool is a must, but even than you may not have the ability to track it down and fix it .
Last edited by THE CHIEF; 02-07-2023 at 02:40 PM.
Thread
Thread Starter
Forum
Replies
Last Post