Pages: 1 ... 16 17 [18] 19 20 ... 40
Author Topic: Anti-lag launch and no-lift-shift secrets inside  (Read 529921 times)
sn00k
Sr. Member
****

Karma: +59/-2
Offline Offline

Posts: 277


« Reply #255 on: September 20, 2012, 04:33:50 PM »

yeah, sorry, i forgot you dont have a throttle threshold to trigger the LC part.. in the original code posted here Grin
Logged
Gonzo
Sr. Member
****

Karma: +21/-30
Offline Offline

Posts: 483


« Reply #256 on: September 20, 2012, 06:58:09 PM »

The funny thing is that the code I currently use doesn't use TPS for antilag, just for no lift shift and for launch speed adjustment.
E.g. If you are not completely stopped and have your foot on the gas all the way down, you cannot adjust the launch speed. I would post a video but I don't wanna brag  Tongue
« Last Edit: September 20, 2012, 08:02:22 PM by Gonzo » Logged
Vdub-dub
Full Member
***

Karma: +4/-1
Offline Offline

Posts: 136


« Reply #257 on: October 06, 2012, 01:02:39 PM »

right had this enabled for while now still loving it but with NLS shift noticed a bit of a problem every now and again when change up a gear via NLS seem to lose power and boost drops down between .2 to .4 bar (random), simply lift off the throttle then back on brings back full boost/power, now obviously had computer on nothing comes up fault code wise (not logged anything as of yet) but feels as if lambda adjusting fueling maybe???
anyone had this or cure ?
Logged
Jason
Hero Member
*****

Karma: +38/-0
Offline Offline

Posts: 500


Breaks everything!


« Reply #258 on: October 06, 2012, 02:17:38 PM »

Personally I only think it happens when you shift too slow.  What the acceptable duration is, I don't know.
Logged
sn00k
Sr. Member
****

Karma: +59/-2
Offline Offline

Posts: 277


« Reply #259 on: October 06, 2012, 06:35:59 PM »

ive noticed this too.. shifting from 1-2 and 2-3 seem to work fine, but 3-4 and it shifts like butter, BUT after about 2 seconds the boost drops and AFR is spooky... im rewriting the code to fix this, ill post the updated code here when i have solved it =)
Logged
Vdub-dub
Full Member
***

Karma: +4/-1
Offline Offline

Posts: 136


« Reply #260 on: October 07, 2012, 02:59:49 PM »

Personally I only think it happens when you shift too slow.  What the acceptable duration is, I don't know.

Tried few different technics first trying very hard fast shifting then settled for less aggressive change which I found better for me and feel of the car/power


Glad not just my car getting this issue can't wait now for code now ,makes car I think so much quicker though the gears, like to time before/ after on 1/4 mile run
Logged
automan001
Full Member
***

Karma: +47/-0
Offline Offline

Posts: 153


« Reply #261 on: October 17, 2012, 11:29:24 PM »

Question, what means bit 2BH.6 in the code:
0002E : 8A 2B 22 60       JB       2BH.6,0076H ; =0x00FD56.0x0040
Is it b_brems? I have not found it in *.ecu file for the M-box.
Logged
automan001
Full Member
***

Karma: +47/-0
Offline Offline

Posts: 153


« Reply #262 on: October 18, 2012, 12:43:13 AM »

Sounds like killing some parts when you see fireballs ... Maybe you need to tune the
IgnitionCutDuration to a reasonable value, in the file are only some default values.
When I analysed NLS code line by line comparing values with the dump 8D0907551M_AlNls_v2.zip I found following in NoLiftShift part of function:
AccPedalThreshold is defined in .bin with value E6 FF which won't work if map defined as byte and you leave it default or will try to change the byte. There should be word.
I guess it was supposed to be E6 00 = 230 * 0.392157 = 90 grad
The part of code which compares threshold reads word from 017E08H address:
0004A : C2 F9 08 7E       MOVBZ    R9,7E08H   ;AccPedalThreshold, 81H:7E08H (017E08H in bin), value = E6 FF???
0004E : 40 49             CMP      R4,R9
Therefore IMHO there should be word E6 00 and AccPedalThreshold map should be defined as word.

P.S: already sorted out, MOVBZ: Moves and zero extends the contents of the source byte specified
by op2 to the word location specified by the destination operand
op1. The contents of the moved data is examined, and the
condition codes are updated accordingly.
« Last Edit: October 18, 2012, 01:02:09 AM by automan001 » Logged
New2Tune
Full Member
***

Karma: +3/-1
Offline Offline

Posts: 55


« Reply #263 on: December 12, 2012, 10:50:22 AM »

So this approach works fine on one of my cars.  On the 02 A4 1.8t though it is destroying ignition coils rapidly.  There was some talk on here about the dwell going to zero causing illegal ignition signals on some ECU's.  Has anyone found out more about this or a way around it? 

I was considering setting the min to the lowest possible time greater than zero.  I'm assuming the error is caused by zero as an input to the dwell time?  but I've trashed 3 sets of coils already and if anyone knows that zero as the time is the issue that would really help.
Logged
prj
Hero Member
*****

Karma: +1072/-480
Online Online

Posts: 6035


« Reply #264 on: December 12, 2012, 01:26:41 PM »

Are you using stock coils? Or did you convert to later 2.0 TFSI coils?
Logged

PM's will not be answered, so don't even try.
Log your car properly - WinOLS database - Tools/patches
New2Tune
Full Member
***

Karma: +3/-1
Offline Offline

Posts: 55


« Reply #265 on: December 12, 2012, 01:33:22 PM »

Did it with both types.  They get crazy hot and the grey goo oozes out of them.
« Last Edit: December 12, 2012, 01:35:31 PM by New2Tune » Logged
Gonzo
Sr. Member
****

Karma: +21/-30
Offline Offline

Posts: 483


« Reply #266 on: January 14, 2013, 12:00:03 PM »

You need code that doesn't change dwell time...

0 dwell time is what makes the coils explode.
Logged
catbed
Sr. Member
****

Karma: +8/-2
Offline Offline

Posts: 300


« Reply #267 on: January 14, 2013, 03:11:40 PM »

Did it with both types.  They get crazy hot and the grey goo oozes out of them.

All four of my coils did this, but I was not using NLS/LC any time close to when they went out. The problem might have started after testing LC a few times, but when they actually died it was just misfiring. I had to keep driving as I was going to school, and it kept getting worse. When I pulled over and took the coils out, they were all very very hot.

Has someone come up with code that does not manipulate ignition dwell? I would like to know if there is.
Logged
prj
Hero Member
*****

Karma: +1072/-480
Online Online

Posts: 6035


« Reply #268 on: January 15, 2013, 07:55:04 AM »

I have done this before on other ECU's.

Guess it's time to write this for ME7 too...
Logged

PM's will not be answered, so don't even try.
Log your car properly - WinOLS database - Tools/patches
sweegie
Full Member
***

Karma: +10/-2
Offline Offline

Posts: 137


« Reply #269 on: January 15, 2013, 10:57:31 AM »

Gents, is this code not already present in some form or another in the tiptronic engine binaries? Certainly looking at the traces from my car, ignition timing is retarded to TDC on shifts to cut torque while maintaining boost pressure. Throttle plate angle isn't touched at all really.
Logged
Pages: 1 ... 16 17 [18] 19 20 ... 40
  Print  
 
Jump to:  

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