rev limit
#17
100% not fuel cut nor mis-fire.
It's like hitting a rev limiter in 5th gear only at 7500 rpm (bounces of the rev at 7500 rpm although limiter set to 9k rpm) and the speed reached is 186 mph, I think it is hitting the speed limiter that is causing it to cut the rev at 7500 rpm.
Anyone can confirm the definition in the rom is correct?
?
It's like hitting a rev limiter in 5th gear only at 7500 rpm (bounces of the rev at 7500 rpm although limiter set to 9k rpm) and the speed reached is 186 mph, I think it is hitting the speed limiter that is causing it to cut the rev at 7500 rpm.
Anyone can confirm the definition in the rom is correct?
?
#18
I'll try that too.
I think you are right razorlab.
btw http://www.lancerregister.com/showthread.php?t=355182
I think you are right razorlab.
btw http://www.lancerregister.com/showthread.php?t=355182
#21
i could be wrong... it was ages and ages ago... but i am sure that the speed limiter didnt work under a particular speed.... could be 40kph.... i would try setting it at say 100kph or 60mph and testing again
#22
8857008 Andy.
OK Ziad will do.
OK Ziad will do.
#23
118e should be the speed limit Address most IXs are the same in the XMLs but iv not tested them but iv also noticed there is another table using the same address (boost controlled speed limit)
#29
The fact that it's around 180mph suggests that the definition is wrong though as it ties in with the 180km/h limit that is std in Japan.
Let me have a look through the actual code section though because I know on my E3, the speed sensor input signal is only accurate at speeds below approx. 40/50mph because of the way in which the sensor signal comes into the ECU and is processed.
Basically put, in the E3 code, a speed sensor input value of 1 = 360mph, a value of 2 = 180mph, a value of 3 is 120mph etc. etc.
So I'm not convinced that the ability to change the speed limit to small changes may actually achieve anything.
I suppose the easiest way would be to change the speed limit definition in the xml to the raw 16 bit value and then just try using 0000 and compare it with FFFF and see if there is any difference.
Andy
Let me have a look through the actual code section though because I know on my E3, the speed sensor input signal is only accurate at speeds below approx. 40/50mph because of the way in which the sensor signal comes into the ECU and is processed.
Basically put, in the E3 code, a speed sensor input value of 1 = 360mph, a value of 2 = 180mph, a value of 3 is 120mph etc. etc.
So I'm not convinced that the ability to change the speed limit to small changes may actually achieve anything.
I suppose the easiest way would be to change the speed limit definition in the xml to the raw 16 bit value and then just try using 0000 and compare it with FFFF and see if there is any difference.
Andy
#30
Is 1e14 correct? Can you check Andy?
Would setting it to 510 work?
The fact that it's around 180mph suggests that the definition is wrong though as it ties in with the 180km/h limit that is std in Japan.
Let me have a look through the actual code section though because I know on my E3, the speed sensor input signal is only accurate at speeds below approx. 40/50mph because of the way in which the sensor signal comes into the ECU and is processed.
Basically put, in the E3 code, a speed sensor input value of 1 = 360mph, a value of 2 = 180mph, a value of 3 is 120mph etc. etc.
So I'm not convinced that the ability to change the speed limit to small changes may actually achieve anything.
I suppose the easiest way would be to change the speed limit definition in the xml to the raw 16 bit value and then just try using 0000 and compare it with FFFF and see if there is any difference.
Andy
Let me have a look through the actual code section though because I know on my E3, the speed sensor input signal is only accurate at speeds below approx. 40/50mph because of the way in which the sensor signal comes into the ECU and is processed.
Basically put, in the E3 code, a speed sensor input value of 1 = 360mph, a value of 2 = 180mph, a value of 3 is 120mph etc. etc.
So I'm not convinced that the ability to change the speed limit to small changes may actually achieve anything.
I suppose the easiest way would be to change the speed limit definition in the xml to the raw 16 bit value and then just try using 0000 and compare it with FFFF and see if there is any difference.
Andy
Thread
Thread Starter
Forum
Replies
Last Post