Jump to content
SAU Community

Recommended Posts

Hey all,

Took my line out for a drive over the weekend and it looks like I've finally broken my tacho (stock) after all those trips to the redline :P On start up the tacho works fine and shows idle around the 1k mark (normal). When driving the tacho reads fine between 0-2500rpm but once the revs go past that mark it either drops to 0 or jumps all over the place. Funny thing is that when changing gears etc and the revs drop down past the 2500 mark the tacho starts reading fine again???

Now when something mech goes wrong in my car, I'm pretty good at diagnosing the prob but with gauges and other elec items I'm pretty clueless. Are the stock tacho sensors off the gearbox or do they read off a pulse from the coil packs? Also are there simple things I can check to make sure a connection hasn't come loose or something? Finally has this happened to anyone in vic and can you recommend a fix or a good auto elec?

Any info or help would be much appreciated.....

Link to comment
https://www.sau.com.au/forums/topic/56544-finally-broke-my-tacho/
Share on other sites

As I understand it, the ECU works out RPM based on the crank angle sensor, ie it calculates the CAS's speed. Then the ECU send signals to the tacho and the tacho just shows what's happening.

I'm no electronics genius so I have NFI what's actually wrong here, but losing the tacho feed is not uncommon on R33s. I lost mine, but it stayed on zero, it didn't move no matter what. I just changed the ECU and off it went again. Maybe scab someone else's ECU for a test?

Revhead.....thanks for the info......hmmm interesting considering I have a wolf 3d replacement comp!!! I have my stock ecu so I might spend some time swapping them over to see if it is the comp...thanks I'll look into that (at least I'll be able to determine if it is the ecu or something else)

Benjiman74......very interested in the nismo item if it does end up being the tacho, if you could hold onto it for a couple of days till I check ecus etc that would be great otherwise if you get an offer you are happy with before that, so be it.

Ant mine does the same, even after I changed to PFC.

Apparently the tacho can be pulled out easily and the tracks cleaned as they get a bit corroded or something. Hearsay only but worth a look. Unfortunately I'm snowed for time to check but will do so after I get back from OS on 5th Dec

hey ant i had this exact same problem. past around 2500rpm it would go nuts. i found it was when i got my apexi rsm installed, the stock rev output signal is set to about 3000 rpm so when it triggers that it somehow made the tacho go nuts, no idea why. you can use the rev output relay on the rsm to control things like shifts lights etc but mine wasnt hooked up to anything but the setting was still there, go over 3000rpm bang tachno goes psycho as no idea why. fix was to set the rev output value to 8500rpm as i can never reach that

not sure what it could be in your case but i have seen what you are talking aobut

also when it would happen the hicas light would flash for some random reason too

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...