Pages: [1] 2
Author Topic: 018 CB ESKONF - can someone please check  (Read 19225 times)
carsey
Sr. Member
****

Karma: +7/-4
Offline Offline

Posts: 401


« on: June 22, 2013, 10:34:56 AM »

Hi

Just found the ESKONF for the 1.8T BAM ECU i have here 018 CB file and I think the ESKONF is AA FF 00 30 FF FB 3C

I am wanting to run my engine without the following:

Rear 02 sensors
VVT (for now)
N80 (evap/charcoal canister)
SAI (N112)
N249

Im basically running a AGU hardware setup on a BAM ECU without all the extras.

I have worked out (hopefully correct) the bytes for the above hex code which relates to.

byte 0: AA = 10 10 10 10    Coil        Coil        Coil          Coil
byte 1: FF = 11 11 11 11    NC          NC          NC            NC
byte 2: 00 = 00 00 00 00    Injector    Injector    Injector      Injector
byte 3: 30 = 00 11 00 00    Rear02      ErrorLamp   N75           N80(evap)
byte 4: FF = 11 11 11 11    BrakeBoost  NC          Shutoffvalve  MIL Light
byte 5: FB = 11 11 10 11    NC          NC          EKP FuelPump  SAI relay
byte 6: 3C = 00 11 11 00    N249        EGRValveamp N112 SAIRelay VVT 

so to turn these off in ESKONF... are the following changes correct.



byte 0: AA = 10 10 10 10    Coil        Coil        Coil          Coil
byte 1: FF = 11 11 11 11    NC          NC          NC            NC
byte 2: 00 = 00 00 00 00    Injector    Injector    Injector      Injector
byte 3: F3 = 11 11 00 11    Rear02      ErrorLamp   N75           N80(evap)
byte 4: FF = 11 11 11 11    BrakeBoost  NC          Shutoffvalve  MIL Light
byte 5: FB = 11 11 10 11    NC          NC          EKP FuelPump  SAI relay
byte 6: FF = 11 11 11 11    N249        EGRValveamp N112 SAIRelay VVT

This then gives me the following hex to reconfigure in the ECU.

AA FF 00 F3 FF FB FF


Can anyone confirm the above?


Obvilously I will have to chance the relevent maps elsewhere to completely remove them, which Ill work on and post up.

Thanks
Logged
carsey
Sr. Member
****

Karma: +7/-4
Offline Offline

Posts: 401


« Reply #1 on: July 10, 2013, 09:45:12 AM »

anyone??
Logged
catbed
Sr. Member
****

Karma: +8/-2
Offline Offline

Posts: 300


« Reply #2 on: July 10, 2013, 09:52:54 AM »

anyone??

Looks correct to me, but there is really no way of knowing its correct unless you disassemble or guess and check.

Where did you find ESKONF? 10BED?
Logged
carsey
Sr. Member
****

Karma: +7/-4
Offline Offline

Posts: 401


« Reply #3 on: July 10, 2013, 10:03:44 AM »

That's it yeah, straight before the KFKHFM map.

Does anyone know if I also have to code out the single ones that are also listed?  or is ESKONF enough?   

Is it simple case of just setting ESKONF correct?
Logged
littco
Hero Member
*****

Karma: +52/-7
Offline Offline

Posts: 903


« Reply #4 on: July 10, 2013, 10:58:28 AM »

That's it yeah, straight before the KFKHFM map.

Does anyone know if I also have to code out the single ones that are also listed?  or is ESKONF enough?   

Is it simple case of just setting ESKONF correct?

Just as easy to delete/code them out individually.

Not sure if this XDF matches up with your CB as there are 2 versions, but this xdf has all the scalars needed to delete them, if you need to know which ones then look at the s4wiki for label names etc
Logged
ddillenger
Hero Member
*****

Karma: +641/-21
Offline Offline

Posts: 5640


« Reply #5 on: July 10, 2013, 11:00:04 AM »

Just as easy to delete/code them out individually.

Not sure if this XDF matches up with your CB as there are 2 versions, but this xdf has all the scalars needed to delete them, if you need to know which ones then look at the s4wiki for label names etc

ESKONF is required in order to remove the hardware and prevent the malfunction in circuit DTC. It prevents the need to resistor the components being removed to preserve trims. You still need to complete the standard deletes via CW.
Logged

Please, ask all questions on the forums! Doing so will ensure the next person with the same issue gets the opportunity to learn from your experience!

Email/Google chat:
DDillenger84(at)gmail(dot)com

Email>PM
carsey
Sr. Member
****

Karma: +7/-4
Offline Offline

Posts: 401


« Reply #6 on: July 10, 2013, 11:13:17 AM »

So effectively, if I code them both out via ESKONF and the CW then its all done right and I dont have to worry about silly fuel trims or anything like that?

Only thing I can realistically seeing me putting back on, is the VVT as can help out a lot.  But currently I dont have a VVT tensioner at the minute.

Can the VVT even be 'turned off' via the CW values without touching the ESKONF?
Logged
ddillenger
Hero Member
*****

Karma: +641/-21
Offline Offline

Posts: 5640


« Reply #7 on: July 10, 2013, 11:45:16 AM »

You can turn VVT off, but the solenoid must remain plugged in. I repeat, if you want to run with hardware removed, you MUST change ESKONF (or resistor).
Logged

Please, ask all questions on the forums! Doing so will ensure the next person with the same issue gets the opportunity to learn from your experience!

Email/Google chat:
DDillenger84(at)gmail(dot)com

Email>PM
carsey
Sr. Member
****

Karma: +7/-4
Offline Offline

Posts: 401


« Reply #8 on: July 30, 2013, 05:12:06 PM »

Thanks.  Missed your last post there.  Seems like its pretty easy to code out in ECU with ESKONF and the CW deletes.

The other thing im not sure about, and could do with another topic maybe, is the lamfa map in the 018CB file.   The axis is pretty messed up.   Am I ok to take this from another 1.8T ecu with a correct scaled axis between 0 and 100% in the left column?
Logged
littco
Hero Member
*****

Karma: +52/-7
Offline Offline

Posts: 903


« Reply #9 on: July 31, 2013, 12:35:43 AM »

Thanks.  Missed your last post there.  Seems like its pretty easy to code out in ECU with ESKONF and the CW deletes.

The other thing im not sure about, and could do with another topic maybe, is the lamfa map in the 018CB file.   The axis is pretty messed up.   Am I ok to take this from another 1.8T ecu with a correct scaled axis between 0 and 100% in the left column?

0x1C98E --- Map

0x1C982  ---Axis 6

0x1C972 ---- Axis  15

Not sure which CB file you have as there are 2 main ones V002 and V003 but this should help
Logged
carsey
Sr. Member
****

Karma: +7/-4
Offline Offline

Posts: 401


« Reply #10 on: July 31, 2013, 04:26:58 AM »

0x1C98E --- Map

0x1C982  ---Axis 6

0x1C972 ---- Axis  15

Not sure which CB file you have as there are 2 main ones V002 and V003 but this should help

That sorted the axis out, but the RPM ones are still a little muddled up.

Its the file in this post.
http://nefariousmotorsports.com/forum/index.php?topic=1457.0title=

Thanks
Logged
littco
Hero Member
*****

Karma: +52/-7
Offline Offline

Posts: 903


« Reply #11 on: July 31, 2013, 08:20:24 AM »

That sorted the axis out, but the RPM ones are still a little muddled up.

Its the file in this post.
http://nefariousmotorsports.com/forum/index.php?topic=1457.0title=

Thanks

Its fine.. Maybe you have the wrong settings in the xdf..

0x1C972
40.00000 * X

15 columns

Heres a waterdown version of my latest cb.xdf for you, it's all correct and should help
Logged
carsey
Sr. Member
****

Karma: +7/-4
Offline Offline

Posts: 401


« Reply #12 on: July 31, 2013, 06:36:19 PM »

Sweet, cheers
I just need to make the decision whether to use lamfa for all the fuelling.  I guess the axis is pedal position with RPM and the map is the AFR requested at that particular point?

So, just the decision whether to use lamfa or have a lower trigger of the BTS map and use that, but that then renders the EGT protection useless and would prefer to try keep that model in place to protect components should it be required with high EGTs.

Does anyone have any advice with what to use.  Is the 6 rows of lamfa for given pedal position enough to tune a k03s 1.8t with heavy mods?

PS ... sorry for all the questions Tongue

Logged
littco
Hero Member
*****

Karma: +52/-7
Offline Offline

Posts: 903


« Reply #13 on: August 02, 2013, 02:05:17 AM »

Sweet, cheers
I just need to make the decision whether to use lamfa for all the fuelling.  I guess the axis is pedal position with RPM and the map is the AFR requested at that particular point?

So, just the decision whether to use lamfa or have a lower trigger of the BTS map and use that, but that then renders the EGT protection useless and would prefer to try keep that model in place to protect components should it be required with high EGTs.

Does anyone have any advice with what to use.  Is the 6 rows of lamfa for given pedal position enough to tune a k03s 1.8t with heavy mods?



PS ... sorry for all the questions Tongue



Lamfa is more than adequate.

You only need to change the last line to run the afr you want at WOT. Providing the lambda sensor is functioning well, the injectors are good and the pump can keep up then there is no reason to use anything but lama for fuelling.. Like you say leave bts for protection, but as you will have no egt and no doubt deleted it will be modelled.. If you want the get protection stick the egt probe in the DP and lower the bts temp threshold by 100 degrees and it should be good..
Logged
carsey
Sr. Member
****

Karma: +7/-4
Offline Offline

Posts: 401


« Reply #14 on: August 02, 2013, 02:21:01 AM »

Lamfa is more than adequate.

You only need to change the last line to run the afr you want at WOT. Providing the lambda sensor is functioning well, the injectors are good and the pump can keep up then there is no reason to use anything but lama for fuelling.. Like you say leave bts for protection, but as you will have no egt and no doubt deleted it will be modelled.. If you want the get protection stick the egt probe in the DP and lower the bts temp threshold by 100 degrees and it should be good..

I have a EGT probe thats in the downpipe about 2" from the flange that bolts onto the turbo.

What happens with the part throttle/load fuelling?     Is that ok even without altering any of the tables that are lower down in lamfa.....all part load will be lambda 1??   I guess the ECU is pretty clever in altering fuelling in that area.  Is that calculated off the MAF readings and lambda?

Thanks

Logged
Pages: [1] 2
  Print  
 
Jump to:  

Powered by SMF 1.1.21 | SMF © 2015, Simple Machines Page created in 0.023 seconds with 17 queries. (Pretty URLs adds 0s, 0q)