Jump to content
SAU Community

Recommended Posts

Hey all,

apparetly my ECU in my car has failed froma common fault. Im not overly convinced that it can simply break like this for no reason at all. and before being played into buying a haltech, i was wondering if anyone out there with a r34 auto turbo will be willing to lend me their ecu to fit into my car and to see if things work out fine. ( really dont want to spend 2200 bucks unless i have to)

im willing to pay to borrow it, if no one is trusting enough :)

sorta need asap

thanks guys

Bryn

Link to comment
https://www.sau.com.au/forums/topic/211966-r34-turbo-auto-guys-can-you-help-me/
Share on other sites

What's it done? Not shifting properly? Depending on the issue, a manual ECU might be ok for testing, unless you need to actually drive it to test the problem. I can't help you either way unfortunately but it might widen your options a little :ninja:

Bryn, you're welcome to borrow mine. I obviously need my car during normal work hours, but if you're able to work something out around that, I'm fine with it.

You'll have to come pull it out though. Hell, I need to do an oil change soon, so I'll just do that while you're off playing with the ECU.

Yeah my ECU isn't so stock anymore so is no use.....but Marc is correct you can put the manual one in and everything will work A-OK except you'll be stuck in 3rd

I don't understand why the GTt isn't like the N/A model and has the auto-shift computer built into the actual car not the ECU :S

So who told you about the "common fault" I've never heard of anything go with the R34 ECU's ever, ever, ever....maybe we can diagnose via the internets for you? :thumbsup:

Try calling Markimak or his brother, they've got the ECU from the stacked R34 that they could lend as far as I know, linky, linky

http://www.skylinesaustralia.com/forums/Wr...34-t176434.html

hey, the common fault is that the ignition section of my ECU has failed. so i got warning lights on the dsah and dirty missfiring.

Hacker X thanks for the offer,, sadly my car is at the mechanics still, so they are only open during the hours ya need ya car.

Ill message markimark and see if i he can help me.

thanks

Edited by Silver_R34_GT-T
hey, the common fault is that the ignition section of my ECU has failed. so i got warning lights on the dsah and dirty missfiring.

Hacker X thanks for the offer,, sadly my car is at the mechanics still, so they are only open during the hours ya need ya car.

Ill message markimark and see if i he can help me.

thanks

Sure it's just not the coilpacks???? That's the common fault with R34's not the ECU side of the ignition

apparently they checked all that, and after looking at it they determined that the ecu was giving out the wrong stuff as were random or something (im not very good at technical shit)

the only reason i knew something was wrong was i had the traction control, slip and engine warning light on, they said that the traction control system was turning itself of as it couldnt get a correct reading from the ecu or throttle or something.

:thumbsup: markimark is out of country)

apparently they checked all that, and after looking at it they determined that the ecu was giving out the wrong stuff as were random or something (im not very good at technical shit)

the only reason i knew something was wrong was i had the traction control, slip and engine warning light on, they said that the traction control system was turning itself of as it couldnt get a correct reading from the ecu or throttle or something.

:ermm: markimark is out of country)

Can you PM me the workshop so I may pass judgment :ermm:

apparently they checked all that, and after looking at it they determined that the ecu was giving out the wrong stuff as were random or something (im not very good at technical shit)

the only reason i knew something was wrong was i had the traction control, slip and engine warning light on, they said that the traction control system was turning itself of as it couldnt get a correct reading from the ecu or throttle or something.

:cheers: markimark is out of country)

mine was turning on the same lights. no missfire, ran fine. was setting i think code 24 - igntion signal primary.

i suspected faulty igniter in one coil causing incorrect feedback to ecu, setting fault code.

new set of splitfires, no more lights & idles smoother.

mine was turning on the same lights. no missfire, ran fine. was setting i think code 24 - igntion signal primary.

i suspected faulty igniter in one coil causing incorrect feedback to ecu, setting fault code.

new set of splitfires, no more lights & idles smoother.

Yeah exactly why I think it's been misdiagnosed as the ECU...the packs are 1000000 times more likely to fail and brings up all of the other lights as it causes the sub-systems to fail at the same time.

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

    • 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.
    • Nah, that is hella wrong. If I do a simple linear between 150°C (0.407v) and 50°C (2.98v) I get the formula Temperature = -38.8651*voltage + 165.8181 It is perfectly correct at 50 and 150, but it is as much as 20° out in the region of 110°C, because the actual data is significantly non-linear there. It is no more than 4° out down at the lowest temperatures, but is is seriously shit almost everywhere. I cannot believe that the instruction is to do a 2 point linear fit. I would say the method I used previously would have to be better.
×
×
  • Create New...