kacperoooni
Full Member
Karma: +9/-2
 Offline
Posts: 124
|
 |
« on: April 24, 2021, 11:34:58 AM »
|
|
|
Hi,
I swapped my B7 for 2.7 biturbo. Unfortunately due to the lack of LDP, the cluster shows "CLOSE FUEL CAP" warning. As far as I know it is needed to code out LDP. I tried turn off LDP using CDLDP and It didn't work. Has anybody find out what codewords/maps need to be changed? I know its popular swap. My ECU is Mbox
|
|
|
|
|
Logged
|
|
|
|
|
nyet
|
|
« Reply #1 on: April 24, 2021, 12:18:44 PM »
|
|
|
Hi,
I swapped my B7 for 2.7 biturbo. Unfortunately due to the lack of LDP, the cluster shows "CLOSE FUEL CAP" warning. As far as I know it is needed to code out LDP. I tried turn off LDP using CDLDP and It didn't work. Has anybody find out what codewords/maps need to be changed? I know its popular swap. My ECU is Mbox
I have this in my notes somewhere and meant to include it into the s4wiki but can't find it now, its been a few years :/ hopefully somebody can chime in and jog my memory have you tried ESKONF TEV? |
|
|
|
« Last Edit: April 24, 2021, 12:20:58 PM by nyet »
|
Logged
|
|
|
|
|
nyet
|
|
« Reply #2 on: April 24, 2021, 12:23:01 PM »
|
|
|
|
|
|
|
|
Logged
|
|
|
|
kacperoooni
Full Member
Karma: +9/-2
Offline
Posts: 124
|
|
« Reply #3 on: April 24, 2021, 02:53:18 PM »
|
|
|
I'll try ESKONF TEV tommorow and see if the warning is still present.
|
|
|
|
|
Logged
|
|
|
|
kacperoooni
Full Member
Karma: +9/-2
Offline
Posts: 124
|
|
« Reply #4 on: April 24, 2021, 02:56:16 PM »
|
|
|
I've already changed maps mentioned in this topic: CDLDP CDTES CLATEVE CLALDPE ESKONF The LDP dtc is not present but still getting warning on the dash |
|
|
|
|
Logged
|
|
|
|
|
macxxx
|
|
« Reply #5 on: April 24, 2021, 10:32:22 PM »
|
|
|
What engine was originally in the car?
|
|
|
|
|
Logged
|
|
|
|
kacperoooni
Full Member
Karma: +9/-2
Offline
Posts: 124
|
|
« Reply #6 on: April 25, 2021, 12:25:13 AM »
|
|
|
What engine was originally in the car?
2.0t 200hp TFSI, this warning is common problem after swap. It is needed to code out ldp properly. |
|
|
|
|
Logged
|
|
|
|
|
macxxx
|
|
« Reply #7 on: April 25, 2021, 12:41:33 AM »
|
|
|
I think it's a cluster issue - it guess doesn't recieve some kind of can info
Maybe search for a 1.8t rb8 cluster for test?
|
|
|
|
|
Logged
|
|
|
|
kacperoooni
Full Member
Karma: +9/-2
Offline
Posts: 124
|
|
« Reply #8 on: April 25, 2021, 01:10:03 AM »
|
|
|
I think it's a cluster issue - it guess doesn't recieve some kind of can info
Maybe search for a 1.8t rb8 cluster for test?
The cluster gets info of fuel tank leak. If I flash 551G the warning is gone. But AC has weird behaviours then... |
|
|
|
|
Logged
|
|
|
|
|
prj
|
|
« Reply #9 on: April 25, 2021, 02:49:59 AM »
|
|
|
Stop changing fault classes and remove the fault without changing them, and your fault will be gone.
This topic is a prime example of why any "CLAxxx" should never ever be touched.
This only hides the fault from OBD but does not change the conditions for the fault being set.
You did not change ESKONF correctly and that's why you have the fault.
|
|
|
|
|
Logged
|
|
|
|
kacperoooni
Full Member
Karma: +9/-2
Offline
Posts: 124
|
|
« Reply #10 on: April 25, 2021, 03:46:44 AM »
|
|
|
Stop changing fault classes and remove the fault without changing them, and your fault will be gone.
This topic is a prime example of why any "CLAxxx" should never ever be touched.
This only hides the fault from OBD but does not change the conditions for the fault being set.
You did not change ESKONF correctly and that's why you have the fault.
Thanks for advice! Gonna revise my ESKONF and try again. Do You know what bits are for LDP in eskonf? TEV is defined on s4wiki, but LDP is not for Mbox |
|
|
|
|
Logged
|
|
|
|
kacperoooni
Full Member
Karma: +9/-2
Offline
Posts: 124
|
|
« Reply #11 on: April 25, 2021, 09:11:26 AM »
|
|
|
Changed CDTES CDLDP and ESKONF TES and AKF(Its stock off in Gbox). Unfortunately the warning still persists...
|
|
|
|
|
Logged
|
|
|
|
|
prj
|
|
« Reply #12 on: April 25, 2021, 11:14:16 AM »
|
|
|
Revert your fault classes to stock and pull the codes.
Change ESKONF via trial error until you find the bits that turn off the code.
|
|
|
|
|
Logged
|
|
|
|
|
nyet
|
|
« Reply #13 on: April 25, 2021, 02:15:19 PM »
|
|
|
Revert your fault classes to stock and pull the codes.
Change ESKONF via trial error until you find the bits that turn off the code.
I tried this before and could not figure it out (years ago, though, so my memory of what I tried is vague) If somebody finds the correct combination of ESKONF please post (especially for 551M/L), thanks. Perhaps trev's swissarmy knife can help |
|
|
|
|
Logged
|
|
|
|
HelperD
Full Member
Karma: +25/-6
Offline
Posts: 112
|
|
« Reply #14 on: July 19, 2023, 12:00:52 PM »
|
|
|
Resurrecting this from the dead to provide a solution for M box ECUs which can probably be applied to other ECUs with similar conflicts.
Had a customer recently with a B7 swapped 2.7T that had this error present.
In my case, as some of you described above no combination of ESKONF or codewords cleared the fault in the dash. The error message is being sent via CAN to the cluster, through MOTOR 5 $480 on Byte 6 specifically. After a bit of time reversing and finding the payload creation of $480 it took a few revisions to narrow down which byte we needed to target.
Simply removing the write to the 6th byte of the $480 CAN message was enough to rectify the dash error for "close fuel cap".
As one of you mentioned, the G box ECU didn't present the error (D box also does not). This is because it is not sending this byte and the cluster has nothing to freak out about.
Here is the solution spoon fed.
Stock MBOX 0002:
F7 F4 1D F8 movb byte_F81D, rl2
Modified:
F7 8E 1D F8 movb byte_F81D, ZEROS
Hope this helps someone,
Christian
|
|
|
|
|
Logged
|
|
|
|
|
