Jump to content
SAU Community

Recommended Posts

Interesting,

Didn't think this topic would surface again.

I had the too many points in my charts before ^^60 not ^^6F, there are only 16 points not 32 thus the rpm scale is in 400 rpm increments.

The divide by 10 to convert to dwell % was gleened for some ecu tuning forum somewhere.

This appears not to be the case thankfully as 25.5% seemed to be max dwell duty % before.

so i guess i need to work out the constant to convert from ecu values in dec to dwell duty %.

will post back later.

  • 2 years later...

Bump.

I know this thread is old, but I'm going to be doing an LS2 coil swap in favour of the garbage RB20 coils I'm running on my RB30.

Can anyone explain the correlation between dwell duty cycle and actual dwell time so i can set them up properly?

Bump.

I know this thread is old, but I'm going to be doing an LS2 coil swap in favour of the garbage RB20 coils I'm running on my RB30.

Can anyone explain the correlation between dwell duty cycle and actual dwell time so i can set them up properly?

They are 2 different things. If frequency didn't change then there would a correlation between the 2 but because frequency increases (with RPM), then duty cycle must increase to achieve the same ON time (in milliseconds) in order to reach coil saturation.

The pic shows that duty cycle has to increase as rpm increases, simply because we have less time.

post-536-1286344473_thumb.jpg

Ah ok... Makes sense. Do you know if i can even adjust actuall dwell to suit other coils then with nistune?

That pic i posted was from nistune. You can adjust it, but if you add too much duty cycle you will just burn out coils.

Millisecond adjustments with nistune are simply to compensate for lower battery voltages. Duty cycle adjustments are for the on time, which will increase as rpm rises.

Easiest way to find out what is required is to hook coil up to a scope, you will see when full saturation is acheived because current will stop climbing and level out.

Otherwise, provided the primary winding are resistances are massively dissimilar, i would just leave them.

Edited by kjb_r33
That pic i posted was from nistune. You can adjust it, but if you add too much duty cycle you will just burn out coils.

Millisecond adjustments with nistune are simply to compensate for lower battery voltages. Duty cycle adjustments are for the on time, which will increase as rpm rises.

Easiest way to find out what is required is to hook coil up to a scope, you will see when full saturation is acheived because current will stop climbing and level out.

Otherwise, provided the primary winding are resistances are massively dissimilar, i would just leave them.

Thanks a lot man you've been super helpful. The thing is, I'm going from R32 coils to LS2 coils which have a WAY higher spark energy and a significantly different dwell time (I think), I guess I'll just play with it slowly. Heres some interesting data on the coils I'm using: http://www.megamanual.com/seq/coils.htm

Do you know what the "nominal dwell" would be on the stock coils?

Edited by ST240
Thanks a lot man you've been super helpful. The thing is, I'm going from R32 coils to LS2 coils which have a WAY higher spark energy and a significantly different dwell time (I think), I guess I'll just play with it slowly. Heres some interesting data on the coils I'm using: http://www.megamanual.com/seq/coils.htm

It actually states on there to use no more than 6 milliseconds. It also states that the millisecond compensation is for dropping battery voltages. (both can be adjusted with nistune).

Id be inclined to get them wired up, then adjust the dwell duty cycle to achieve the 6ms.

This will give you max coil output at a duty cycle thats not going to shorten coil life excessively.

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

    • Take the value it measured as, and pick the closest range available that is above the reading on the screen.   Also, no point just testing the coils. Read what has been said again. You need to test all your wiring, everything.
    • Does the scanner do all the CUs in the car, or only the ECU?
    • @666DAN sorry to bring you and old thread.     I've got my de+t done and it's all running great other than 1 small issue.    Car has remained auto with the na auto and tcm, I've used a stagea ecu with. NIstune board and everything is great other than my gear selection on the dash. It illuminates park, reverse, neutral, 3rd and 2nd when selected . But nothing when in  drive or what gear your in when you pop it into tiptronic. I'm sure there is maybe 1 wire in the ecu plug I need to move to rectify this. Do ya have any ideas?     Cheers man
    • Well I recently changed my rear axles and was thinking if I bumped anything, I have been driving the car for a while now though... But it has been raining today so everything is wet under the wheel arches. Brakes feel fine and can't hear any of the metal screamers, I had a squeak coming from one of the handbrake drums but that seems to have gone away a while ago. I was going down a hill when it lit up and I did feel the abs bite for a second and question why it did it?
    • Correct. Um. I dunno. I haven't cared enough about the way that the NA cars work to know for sure. But..... The 33/34 turbo manual cars have an electronic speed sensor in the gearbox that outputs a +/- (ie, sawtooth AC) voltage signal. That is connected to the speedo. The speedo then outputs a 0-5v square wave (ie, PWM) signal that the ECU (and any other CU on the bus) sees. The speed sensor is NOT directly connected to the ECU. So here's the problem. Your new ECU expects to see the PWM signal, but must somehow be getting a direct signal from the diff speed sensor. Which would suggest that the wiring of the NA car is not the same as the turbo cars. I think you will need to spend some time with (hopefully the wiring diagram for the car) and a multimeter to see what is connected to what. Then, presuming I am correct**, you would then want to separate the ECU speed signal input from the rest of the car's wiring, and probably either buy a speed signal converter, or build one using an arduino (or similar). That would take in the speed sensor signal and output a scaled (and suitably rearranged) signal for the ECU. ** We shouldn't presume that I am correct here, because there might be something else crazy going on. I don't think you could convert the speedo to be fed from the gearbox sensor, because the pulse rate from that sensor is probably different to the diff sensor and then the speedo would read wrongly. And this also wouldn't fix the ECU's problem either, because the ECU doesn't want to see the gearbox signal direct either (assuming that they are all on the same wiring, for some odd NA related reason, see above caveat!) Does this help? Probably not. Can you make it work? Almost certainly. With the above work. You should buy a handheld oscilloscope from Aliexpress so that you can view these signals directly. Connect up the probes and drive the car. Show photos of the screen when drving at known speeds and connected to different places, and we'll see what we can learn about it.
×
×
  • Create New...