Jump to content
SAU Community

Recommended Posts

ok so here it goes:

*cars a s13 with a rb20 in it, all wiring is fine to the ecu and such, there were problems but all fixed!

*so i currently have no speedo or reverse lights, i did have the rpm but i tried to install a tacho in, by using the yellow wire with red stripe, still tacho did not work, and when i reconnected the wires together the way i found them, the rpm meter wont move now???? FFS argh

car currently has the ca18de electric instrument cluster, will i need to get a r32 one + the cable wires so it all works? will the cluster bolt straight in?

any help would be absolutely helpful as the other forums i posted the same question in, did not help 1 bit

thanks all!!!

If youre running rb20 ecu ca18 cluster will not work. You need rb20 cluster. Mate has R31 skyline with dodgy cluster we tried pintara cluster which look almost completely identical, plug in and readings are out of wack.

Good luck.

mate for starters the original tacho will never work with the rb20 computer as the signal is different. secondly i'm pretty sure the s13 came out with a transducer type speedo where the r32 comes out with a cable driven speedo. the reverse lights don't work because they're not hooked up or fuse could be blown.

Edited by 116.hks

i am about to aquire a silvia with the same problem has rb20det in the s13 which is runnning a ca18 dash, the speedo works apparently but that is it...i was going to try find a rb20pin out diagram for the ecu and try match it to the wires off the back of the ca18 cluster..this won't work? if not like the original post said..will an r32 dash bolt in? cheers, Hame.

  • 1 month later...

I has rb20 in s13 with ca18 cluster.. u need to use the ca18 sender from the gearbox and slap that on the rb20 gearbox.. but im still running into afew problems myself. over all rb20 >.> into s13 is a shit idea better off getting a rb25 works out alot cheaper

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