Jump to content
SAU Community

Recommended Posts

  • Replies 101
  • Created
  • Last Reply

Top Posters In This Topic

Top Posters In This Topic

Posted Images

  • 5 weeks later...

Umm, I know I'm a bit Jonny-come-lately, but, which wire is it that people are cutting/switching? Sounds like something I need to do.:thumbsup:

Yeah Andy, you do! Everyone with a M35 should do this. Then crossing a busy road won't require such a big gap.

It's pin 55 on the ECU, but run it via a switch so you can "cut" the wire at will (& reconnect it also). If the ECU doesn't see the brake switch every so often (days normally) it will eventually throw a code. Good news is the code disappears if you switch the wire back into circuit & put your foot on the brake.

For more info have a read of this thread from about here (or even a few pages before -it's very interesting): http://www.skylinesa...ost__p__5832870

Edited by Commsman
  • 1 month later...

I found out today, after months driving with the wire cut, it will eventually go into throttle limp. I was driving when I suddenly noticed the throttle wouldn't go past 24% on the informeter. A quick roadside ecu reset didn't clear it, unplugging the ecu did as I couldn't get to the wires.

I have a switch in the dash now... :)

  • 3 months later...

>_< I'm getting DTC 1805. In theory once you flick the switch and press the brake does it go away? Or do you need to clear the code?

If its like other error codes Ive experienced in the M35 (eg dead AFM) the code wont clear automatically when the problem is resolved (ie plug the new AFM in and its still showing you a CEL - but the car is operating fine). If its no longer in limp mode, I would suggest that it will self clear over the next couple of days; but if you're feeling pedantic you can clear the codes manually thumbsup.gif

Funny thing is that I haven't noticed a drop in power, although I wasn't giving it much this morning. Better take it for a drive at lunch and see what's up.

If the limp mode caused by the wire cut is the same as the one with a blown AFM you'd definitely notice, even when not giving it much. Basically theres a ~2100 RPM rev limiter in place and it bounces off that once when you try and move your foot much more than 1/4" on the pedal.

If the limp mode caused by the wire cut is the same as the one with a blown AFM you'd definitely notice, even when not giving it much. Basically theres a ~2100 RPM rev limiter in place and it bounces off that once when you try and move your foot much more than 1/4" on the pedal.

Pure weirdness then. I'm sure it's 1805 but I would have revved it higher than 2100 RPM this morning. I know I was tired this morning but surely not that much! :rolleyes:

If its the wire cut you just have to reconnect the wire and press the brake, you will be good for another few months. If you leave it the car will go into limp mode eventually and limit the throttle.

If its the wire cut you just have to reconnect the wire and press the brake, you will be good for another few months. If you leave it the car will go into limp mode eventually and limit the throttle.

I just read Andys first post in this thread, he suggested that the limp mode imposed was that "Under hard acceleration = reduced response" which is a bit different to the rev limited limp mode. So, given how tired you were Jase you mightnt have noticed :P but as Scotty said - flick that switch you put in and see if it seems normal now?

I just read Andys first post in this thread, he suggested that the limp mode imposed was that "Under hard acceleration = reduced response" which is a bit different to the rev limited limp mode. So, given how tired you were Jase you mightnt have noticed :P but as Scotty said - flick that switch you put in and see if it seems normal now?

The above could be true as in my experience when the light came on (from the brake wire cut) I didn't notice any drop in performance or rev limit being imposed, but I also wasn't doing anything considered 'hard acceleration'. As for resetting the code, for me it was as simple as flicking the switch back to normal & pressing the brake pedal. Maybe it is different if the MIL has been on for a long time.... Also, I don't know how Scotty got a months driving between resetting. I got about 500km before my light came on.

Edit: just thinking about this - it's probably because Scotty has a light on permanently due to the Emanage. He is probably talking about a proper limp mode, which is quite on the cards if left for an extended period.

Edited by Commsman

^lol.

It's just 12V that needs to be applied to the ECU pin to clear the code. Can get it from anywhere. Of course if you don't use the original brake wire & switch in some permanent 12V, you'll have restricted throttle all the time.

I'm starting to think of a good idea for a "valet mode"....:whistling:

Yeah I get coming on around every 500km. Ive never noticed any difference, but its usually when im just cruising along so just press the brake slightly with my left foot while holding the button and the light goes out after a couple of seconds

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now



  • Similar Content

  • Latest Posts

    • For once a good news  It needed to be adjusted by that one nut and it is ok  At least something was easy But thank you very much for help. But a small issue is now(gearbox) that when the car is stationary you can hear "clinking" from gearbox so some of the bearing is 100% not that happy... It goes away once you push clutch so it is 100% gearbox. Just if you know...what that bearing could be? It sounding like "spun bearing" but it is louder.
    • Yeah, that's fine**. But the numbers you came up with are just wrong. Try it for yourself. Put in any voltage from the possible range and see what result you get. You get nonsense. ** When I say "fine", I mean, it's still shit. The very simple linear formula (slope & intercept) is shit for a sensor with a non-linear response. This is the curve, from your data above. Look at the CURVE! It's only really linear between about 30 and 90 °C. And if you used only that range to define a curve, it would be great. But you would go more and more wrong as you went to higher temps. And that is why the slope & intercept found when you use 50 and 150 as the end points is so bad halfway between those points. The real curve is a long way below the linear curve which just zips straight between the end points, like this one. You could probably use the same slope and a lower intercept, to move that straight line down, and spread the error out. But you would 5-10°C off in a lot of places. You'd need to say what temperature range you really wanted to be most right - say, 100 to 130, and plop the line closest to teh real curve in that region, which would make it quite wrong down at the lower temperatures. Let me just say that HPTuners are not being realistic in only allowing for a simple linear curve. 
    • I feel I should re-iterate. The above picture is the only option available in the software and the blurb from HP Tuners I quoted earlier is the only way to add data to it and that's the description they offer as to how to figure it out. The only fields available is the blank box after (Input/ ) and the box right before = Output. Those are the only numbers that can be entered.
    • No, your formula is arse backwards. Mine is totally different to yours, and is the one I said was bang on at 50 and 150. I'll put your data into Excel (actually it already is, chart it and fit a linear fit to it, aiming to make it evenly wrong across the whole span. But not now. Other things to do first.
    • God damnit. The only option I actually have in the software is the one that is screenshotted. I am glad that I at least got it right... for those two points. Would it actually change anything if I chose/used 80C and 120C as the two points instead? My brain wants to imagine the formula put into HPtuners would be the same equation, otherwise none of this makes sense to me, unless: 1) The formula you put into VCM Scanner/HPTuners is always linear 2) The two points/input pairs are only arbitrary to choose (as the documentation implies) IF the actual scaling of the sensor is linear. then 3) If the scaling is not linear, the two points you choose matter a great deal, because the formula will draw a line between those two points only.
×
×
  • Create New...