Jump to content
SAU Community

Recommended Posts

In the process of tuning rb20det to standard specs. car is very slugish on standard base ignition timing also has been converted from auto to manual running standard auto ecu.

car has following mods

-unopened rb20det

-rb25 turbo

-walbro 255 pump

-pod with custom box and air duct

-12psi

-fmic

-3" exhaust no cat strait to rear muffler

-yellow jacket coil packs

-new iridium plugs gapped down to .8 from 1.1

i put the timing to the auto's 20 deg btdc with aac unplugged and idle @700rpm like this you put your foot down and it makes alot of noise but isn't pulling very well compared to if its on 30 deg btdc which it really gets up and goes (with no pinging). 20 deg, kick cluch in second will bog! 30 deg kick in second lets loose and abit of third? do i have to maybe gap the plugs back to 1.1 to bring ignition back to 20???

Link to comment
https://www.sau.com.au/forums/topic/392159-slugish-15-20deg-timing/
Share on other sites

I assume your using the wire loop at the rear of the engine? Cheap timing lights tend to read double or half while using it.. i can't remember. Best place to get a timing signal is from coil #1

I assume your using the wire loop at the rear of the engine? Cheap timing lights tend to read double or half while using it.. i can't remember.

DOUBLE. So you probably only have 10 BTDC.

Most accurate is to insert a spark plug lead between #1 coil and #1 plug, and time it "old school".

You are running good coils and fairly stock power, so I would suggest you open the gap back out to around 1mm.

timing was done with ignition lead between coil 1 and plug. also just moved it to 25 and i can live with thepower it has there but any thing under and its really boggy till your up around 6000rpm. This is all assuming the orange mark is 0 and 7th mark is 30 btdc?

Edited by domo88

my thought is if i make the spark gap bigger it will ignite the fuel quicker therefore i can make it fire closer to tdc (more retard) at the moment the spark is weaker and to ignite the fuel properly its having to fire that much more early or advaced. does this sound right?

no worries well its running well where it is and not pinging so i'll leve it there till i get money for nistune and get it on dyno. also when i had the timing backed off it was super fuely and poping when going down gears wich is nothing different when running rich but when i was pushing the accelerator and was running slugish and bogging down at 6000rpm it hit fuel cut??? my theory is that because it was running so rich the computer tryed to compensate for it by trying to correct a/f mixture with more air and maxed out the afm making it hit fuel cut??? this is possible? coz hasn't done it since got it running right... cheers for replys

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

    • 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.
    • When I said "wiring diagram", I meant the car's wiring diagram. You need to understand how and when 12V appears on certain wires/terminals, when 0V is allowed to appear on certain wires/terminals (which is the difference between supply side switching, and earth side switching), for the way that the car is supposed to work without the immobiliser. Then you start looking for those voltages in the appropriate places at the appropriate times (ie, relay terminals, ECU terminals, fuel pump terminals, at different ignition switch positions, and at times such as "immediately after switching to ON" and "say, 5-10s after switching to ON". You will find that you are not getting what you need when and where you need it, and because you understand what you need and when, from working through the wiring diagram, you can then likely work out why you're not getting it. And that will lead you to the mess that has been made of the associated wires around the immobiliser. But seriously, there is no way that we will be able to find or lead you to the fault from here. You will have to do it at the car, because it will be something f**ked up, and there are a near infinite number of ways for it to be f**ked up. The wiring diagram will give you wire colours and pin numbers and so you can do continuity testing and voltage/time probing and start to work out what is right and what is wrong. I can only close my eyes and imagine a rat's nest of wiring under the dash. You can actually see and touch it.
    • So I found this: https://www.efihardware.com/temperature-sensor-voltage-calculator I didn't know what the pullup resistor is. So I thought if I used my table of known values I could estimate it by putting a value into the pullup resistor, and this should line up with the voltages I had measured. Eventually I got this table out of it by using 210ohms as the pullup resistor. 180C 0.232V - Predicted 175C 0.254V - Predicted 170C 0.278V - Predicted 165C 0.305V - Predicted 160C 0.336V - Predicted 155C 0.369V - Predicted 150C 0.407V - Predicted 145C 0.448V - Predicted 140C 0.494V - Predicted 135C 0.545V - Predicted 130C 0.603V - Predicted 125C 0.668V - Predicted 120C 0.740V - Predicted 115C 0.817V - Predicted 110C 0.914V - Predicted 105C 1.023V - Predicted 100C 1.15V 90C 1.42V - Predicted 85C 1.59V 80C 1.74V 75C 1.94V 70C 2.10V 65C 2.33V 60C 2.56V 58C 2.68V 57C 2.70V 56C 2.74V 55C 2.78V 54C 2.80V 50C 2.98V 49C 3.06V 47C 3.18V 45C 3.23V 43C 3.36V 40C 3.51V 37C 3.67V 35C 3.75V 30C 4.00V As before, the formula in HPTuners is here: https://www.hptuners.com/documentation/files/VCM-Scanner/Content/vcm_scanner/defining_a_transform.htm?Highlight=defining a transform Specifically: In my case I used 50C and 150C, given the sensor is supposedly for that. Input 1 = 2.98V Output 1 = 50C Input 2 = 0.407V Output 2 = 150C (0.407-2.98) / (150-50) -2.573/100 = -0.02573 2.98/-0.02573 + 47.045 = 50 So the corresponding formula should be: (Input / -0.02573) + 47.045 = Output.   If someone can confirm my math it'd be great. Supposedly you can pick any two pairs of the data to make this formula.
×
×
  • Create New...