Jump to content
SAU Community

Recommended Posts

Basic setup of the car Rb25Det Deatchwerks 740cc Injectors Rb20 ECU running nistune and a VCT controller.

Installed the injectors, all looks good nothing leaking. Run the Injector change function on nistune and the Injector multiplier is nearly halfed. Stupid thing starts to barly idle at a very lean 19AFR. Im adding nearly an extra 60% to the Multiplier to get it to idle at 14.9AFR the idle is just shit sounds liek a wrx on 3 cylinders.

Up the multiplier some more and AFR head towards 12.5 and the idle is alot nicer.

Now if the idle is set to what it should be the rest of the map becomes extremely rich, so rich in fact that the car splutters and stops moving.

So now i have 0'ed out the fuel map in the cruise section and cruising along adjust the multiplier to sround what it was when the injector change function was run.

Car seams to drive alot better comming on to boost it is still very rich but drivable(In the 11-12AFR range), no spluttering at all felt more like before the injector change.

Now to get it to idle thoses fuel cells are now adjusted to theroetical 10AFR

The way the nissan ecu's work theoretical AFR sound be pretty close to actual AFR expecially in the light cruize/idle range.

Any ideas? Deatchwerks sell them as drop in replacements from what i can see of the injector report lag tims are correct.

Is thi normal for larger injectors? Any one else with Deatchwerks experiance?

Link to comment
https://www.sau.com.au/forums/topic/369944-tuning-with-bigger-injectors/
Share on other sites

Ahh - the difference between theory and practise.

1. Your using quite a large injector how much power are you after?

2. Those injectors are quite poor in terms of spray pattern and low end drivability.

3. The test benches that injector manufactures use don't always match the how the factory ecu's drive injectors so the provided latencies aren't always that good of a guide.

The problem you are experiencing is non-linearity of the injector from driving a too smaller pulse width. You can correct it by increasing your latency time or to increase your ttp min. I would put in your calculated k value and try increasing your latency first, failing that increase your ttp min.

you have to adjust the latency corrections, if the 740s are anything like the 1000s i got from Deatchwerks the latency is massively different to stock. you should have got a flow report with the injectors with latency figures on it

Here is the report from Deatchwerks

post-28286-0-81601500-1309776814_thumb.jpg

Report says 756cc avg flow static and 645cc avg flow dynamic. Which figure do i use in my calculations?

And yes I can see 1.3ms Latency @ 14V I will give this a go tomorrow

The lean at idle symptoms you describe in your first post is typical of having the latency too low, whereas at WOT latency setting is not important. So - fixing the latency setting should help a lot!

Here is the report from Deatchwerks

post-28286-0-81601500-1309776814_thumb.jpg

Report says 756cc avg flow static and 645cc avg flow dynamic. Which figure do i use in my calculations?

And yes I can see 1.3ms Latency @ 14V I will give this a go tomorrow

use 756. cant remember exactly how nistune works the latency but for reference the standard 25 injectors are .63ms

Finally got around to trying this again. Set injector latency to 1300 resized injectors to 756 saved changes and started the car.

Car started and idled better than ever before(Even before the injector change)

Didn't have time to let it fully warm up and fine tune the multiplier but so far very happy with the hiflow injectors.

I was always told the hiflowed rb25 injectors were bad at cold start. These being Suburu hiflowed injectors seam absolutly fine.

Oh and to answer the previous question. Why did I buy such large injectors.

My power goal is 400hp for now but I do plan on building a 3L and run E85 so only buying injectors the one time

  • 1 month later...

Still having issues with these injectors haven't driven my car since installing them.

Here is an email I got from Deatschwerks regarding the problem.

Jason,

If the OE latency is displayed as 530us for the OE RB25 ECU, then think using 1300us for our injectors would be way off. The RB25 uses a OE side feed injector with almost the same coil properties as our 740’s. I would suggest trying something in the 700 rang and see if that helps then adjust from there. Our injector would not have anywhere close to more than twice the latency time as the OE injector

Thanks

-Mike

Now as you can see from the flow report I posted @14v(My car runs 13.9-14v at idle) the latency is 1.3MS or 1300us for Nistuns sake.

From what Mike at Deatschwerks is saying this is incorrect??? Does this mean the latency data provided is for both opening and closing time?

Ho can I accurately measure latency time my self?

Your spending too much time on latency and concentrating on theory (very often the case text book tuning is useless in real world applications), best bet is to concentrate on your idle and cruise with latency within 10% of the factory setting as they are high flowed. Use your K value.

Once cruise and idle is set to a reasonable setting then retune the rest of the map,it is not uncommon to rewrite the whole map so it resembles nothing like your old one.

Maniplutaion of the MAF curve is generally a given too. The maps Tao has posted the last few pages of his highflow thread have around 1.5 to 2hours spent on the MAF curve alone... so much detail in there athat changing turbos generally only requires a run or 2 on the dyno to touch up each time.

So what problems is it now having.

Still the same issue idle is only perfect when running really rich.

Status, that is some really good advise. I will get the latency and K value as good as I can get it then just start re tuning the rest of the map.

When you talk about tuning the MAF curve as you referring to adjusting the MAF table so real world AFR's resemble the theoretical AFR on the fuel map?

I guess that kinda like a 2D VE map isn't it?

If only the dyno my mate and me are building was complete would make this a lot easier.

One more question.

What is the stock latency figure for the rb25?

I have a nistuned rb20 ecu running my car and the latency in there is different to the latency of the stock rb25 ecu.

Maybe this value was forgotten when I had the base image built by Nistune? This could be the reason my car has always run really rich and had a bad idle?

Any way cheers for all the help again guys.

Still the same issue idle is only perfect when running really rich.

Status, that is some really good advise. I will get the latency and K value as good as I can get it then just start re tuning the rest of the map.

When you talk about tuning the MAF curve as you referring to adjusting the MAF table so real world AFR's resemble the theoretical AFR on the fuel map?

I guess that kinda like a 2D VE map isn't it?

If only the dyno my mate and me are building was complete would make this a lot easier.

One more question.

What is the stock latency figure for the rb25?

I have a nistuned rb20 ecu running my car and the latency in there is different to the latency of the stock rb25 ecu.

Maybe this value was forgotten when I had the base image built by Nistune? This could be the reason my car has always run really rich and had a bad idle?

Any way cheers for all the help again guys.

any conversion ecu required a full retune to get it working sweet, if you look in your rom pack under type 6 he rb25 bin files are all there..

Yes your reasoning on the maf map is correct, ive been spending more and more time in this map now that nistune changed the scale manipulation for me (on other ecus like pfc its where i spend most time), it used to be a tedious job as the values would only scale up and down in 10's... they have since changed it for me so it scales in 100's and it has been absolute bliss :P

Cant fault the Nistune guys as they are quick to react and help with any suggestions or upgrades.

Still the same issue idle is only perfect when running really rich.

Status, that is some really good advise. I will get the latency and K value as good as I can get it then just start re tuning the rest of the map.

When you talk about tuning the MAF curve as you referring to adjusting the MAF table so real world AFR's resemble the theoretical AFR on the fuel map?

I guess that kinda like a 2D VE map isn't it?

If only the dyno my mate and me are building was complete would make this a lot easier.

One more question.

What is the stock latency figure for the rb25?

I have a nistuned rb20 ecu running my car and the latency in there is different to the latency of the stock rb25 ecu.

Maybe this value was forgotten when I had the base image built by Nistune? This could be the reason my car has always run really rich and had a bad idle?

Any way cheers for all the help again guys.

The issue sounds like your operating the injector outside its linear zone. You may have to leave it on the rich side. I would do as I said above and not modify the maf curve.

Little update:

Planned to spend the day tuning my car. Ended up spending most of the time help my mate on his 3L and installing a Deatschwerks 300LPH fuel pump.

We had great sucess apart from my fuel gauge no longer working and i think the filter the fuel pump cam with dosn;t quite reach as far down as the stock setup, both can be fixed easily i guess.

Can you but a new stock fuel pump filter setup?

Started the car with the new pump and no tune adjustment.

Started really well but again very rich. After the car warmed up a little and closed loop took over the fueling the car idle fu*king beautiful and sat with a 14.8 - 14.9 AFR.

Starting the car I can see its still got way too much fuel in it but thats expected as I still need to adjust to injector settings.

So i'm thinking all these rough idle and missing issues for the last 2 years have been a stuffed fuel pump the whole time. Changing the injectors over just made the symptoms a lot worse.

The Deatschwerks pump was a tad over $200 including a nissan filling kit, purchased from Kudos motorsports web site. It is very quiet compaired to the noisy as hell r32GTR pump that was just removed.

Now I can start seeing what the real quality of these injectors are fuel pump are.

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

    • Any update on this one? did you manage to get it fixed?    i'm having the same issue with my r34 and i believe its to do with the smart entry (keyless) control module but cant be sure without forking out to get a replacement  
    • So this being my first contribution to the SAU forums, I'd like to present and show how I had to solve probably one of the most annoying fixes on any car I've owned: replacing a speedometer (or "speedo") sensor on my newly acquired Series 1 Stagea 260RS Autech Version. I'm simply documenting how I went about to fix this issue, and as I understand it is relatively rare to happen to this generation of cars, it is a gigantic PITA so I hope this helps serve as reference to anyone else who may encounter this issue. NOTE: Although I say this is meant for the 260RS, because the gearbox/drivetrain is shared with the R33 GTR with the 5-speed manual, the application should be exactly the same. Background So after driving my new-to-me Stagea for about 1500km, one night while driving home the speedometer and odometer suddenly stopped working. No clunking noise, no indication something was broken, the speedometer would just stop reading anything and the odometer stopped going up. This is a huge worry for me, because my car is relatively low mileage (only 45k km when purchased) so although I plan to own the car for a long time, a mismatched odometer reading would be hugely detrimental to resale should the day come to sell the car. Thankfully this only occurred a mile or two from home so it wasn't extremely significant. Also, the OCD part of me would be extremely irked if the numbers that showed on my dash doesn't match the actual ageing of the car. Diagnosing I had been in communication with the well renown GTR shop in the USA, U.P.garage up near University Point in Washington state. After some back and forth they said it could be one of two things: 1) The speedometer sensor that goes into the transfer case is broken 2) The actual cluster has a component that went kaput. They said this is common in older Nissan gauge clusters and that would indicate a rebuild is necessary. As I tried to figure out if it was problem #1, I resolved problem #2 by sending my cluster over to Relentless Motorsports in Dallas, TX, whom is local to me and does cluster and ECU rebuilds. He is a one man operation who meticulously replaces every chip, resistor, capacitor, and electronic component on the PCB's on a wide variety of classic and modern cars. His specialty is Lexus and Toyota, but he came highly recommended by Erik of U.P.garage since he does the rebuilds for them on GTR clusters.  For those that don't know, on R32 and R33 GTR gearboxes, the speedometer sensor is mounted in the transfer case and is purely an analog mini "generator" (opposite of an alternator essentially). Based on the speed the sensor spins it generates an AC sine wave voltage up to 5V, and sends that via two wires up to the cluster which then interprets it via the speedometer dial. The signal does NOT go to the ECU first, the wiring goes to the cluster first then the ECU after (or so I'm told).  Problems/Roadblocks I first removed the part from the car on the underside of the transfer case (drain your transfer case fluid/ATF first, guess who found out that the hard way?), and noted the transfer case fluid was EXTREMELY black, most likely never changed on my car. When attempting to turn the gears it felt extremely gritty, as if something was binding the shaft from rotating properly. I got absolutely no voltage reading out of the sensor no matter how fast I turned the shaft. After having to reflow the solder on my AFM sensors based on another SAU guide here, I attempted to disassemble the silicone seal on the back of the sensor to see what happened inside the sensor; turns out, it basically disintegrated itself. Wonderful. Not only had the electrical components destroyed themselves, the magnetic portion on what I thought was on the shaft also chipped and was broken. Solution So solution: find a spare part right? Wrong. Nissan has long discontinued the proper sensor part number 32702-21U19, and it is no longer obtainable either through Nissan NSA or Nissan Japan. I was SOL without proper speed or mileage readings unless I figured out a way to replace this sensor. After tons of Googling and searching on SAU, I found that there IS however a sensor that looks almost exactly like the R33/260RS one: a sensor meant for the R33/R34 GTT and GTS-T with the 5 speed manual. The part number was 25010-21U00, and the body, plug, and shaft all looked exactly the same. The gear was different at the end, but knowing the sensor's gear is held on with a circlip, I figured I could just order the part and swap the gears. Cue me ordering a new part from JustJap down in Kirrawee, NSW, then waiting almost 3 weeks for shipping and customs clearing. The part finally arrives and what did I find? The freaking shaft lengths don't match. $&%* I discussed with Erik how to proceed, and figuring that I basically destroyed the sensor trying to get the shaft out of the damaged sensor from my car. we deemed it too dangerous to try and attempt to swap shafts to the correct length. I had to find a local CNC machinist to help me cut and notch down the shaft. After tons of frantic calling on a Friday afternoon, I managed to get hold of someone and he said he'd be able to do it over half a week. I sent him photos and had him take measurements to match not only the correct length and notch fitment, but also a groove to machine out to hold the retentive circlip. And the end result? *chef's kiss* Perfect. Since I didn't have pliers with me when I picked up the items, I tested the old gear and circlip on. Perfect fit. After that it was simply swapping out the plug bracket to the new sensor, mount it on the transfer case, refill with ATF/Nissan Matic Fluid D, then test out function. Thankfully with the rebuilt cluster and the new sensor, both the speedometer and odometer and now working properly!   And there you have it. About 5-6 weeks of headaches wrapped up in a 15 minute photo essay. As I was told it is rare for sensors of this generation to die so dramatically, but you never know what could go wrong with a 25+ year old car. I HOPE that no one else has to go through this problem like I did, so with my take on a solution I hope it helps others who may encounter this issue in the future. For the TL;DR: 1) Sensor breaks. 2) Find a replacement GTT/GTS-T sensor. 3) Find a CNC machinist to have you cut it down to proper specs. 4) Reinstall then pray to the JDM gods.   Hope this guide/story helps anyone else encountering this problem!
    • So this being my first contribution to the SAU forums, I'd like to present and show how I had to solve probably one of the most annoying fixes on any car I've owned: replacing a speedometer (or "speedo") sensor on my newly acquired Series 1 Stagea 260RS Autech Version. I'm simply documenting how I went about to fix this issue, and as I understand it is relatively rare to happen to this generation of cars, it is a gigantic PITA so I hope this helps serve as reference to anyone else who may encounter this issue. NOTE: Although I say this is meant for the 260RS, because the gearbox/drivetrain is shared with the R33 GTR with the 5-speed manual, the application should be exactly the same. Background So after driving my new-to-me Stagea for about 1500km, one night while driving home the speedometer and odometer suddenly stopped working. No clunking noise, no indication something was broken, the speedometer would just stop reading anything and the odometer stopped going up. This is a huge worry for me, because my car is relatively low mileage (only 45k km when purchased) so although I plan to own the car for a long time, a mismatched odometer reading would be hugely detrimental to resale should the day come to sell the car. Thankfully this only occurred a mile or two from home so it wasn't extremely significant. Also, the OCD part of me would be extremely irked if the numbers that showed on my dash doesn't match the actual ageing of the car. Diagnosing I had been in communication with the well renown GTR shop in the USA, U.P.garage up near University Point in Washington state. After some back and forth they said it could be one of two things: 1) The speedometer sensor that goes into the transfer case is broken 2) The actual cluster has a component that went kaput. They said this is common in older Nissan gauge clusters and that would indicate a rebuild is necessary. As I tried to figure out if it was problem #1, I resolved problem #2 by sending my cluster over to Relentless Motorsports in Dallas, TX, whom is local to me and does cluster and ECU rebuilds. He is a one man operation who meticulously replaces every chip, resistor, capacitor, and electronic component on the PCB's on a wide variety of classic and modern cars. His specialty is Lexus and Toyota, but he came highly recommended by Erik of U.P.garage since he does the rebuilds for them on GTR clusters.  For those that don't know, on R32 and R33 GTR gearboxes, the speedometer sensor is mounted in the transfer case and is purely an analog mini "generator" (opposite of an alternator essentially). Based on the speed the sensor spins it generates an AC sine wave voltage up to 5V, and sends that via two wires up to the cluster which then interprets it via the speedometer dial. The signal does NOT go to the ECU first, the wiring goes to the cluster first then the ECU after (or so I'm told).  Problems/Roadblocks I first removed the part from the car on the underside of the transfer case (drain your transfer case fluid/ATF first, guess who found out that the hard way?), and noted the transfer case fluid was EXTREMELY black, most likely never changed on my car. When attempting to turn the gears it felt extremely gritty, as if shttps://imgur.com/6TQCG3xomething was binding the shaft from rotating properly. After having to reflow the solder on my AFM sensors based on another SAU guide here, I attempted to disassemble the silicone seal on the back of the sensor to see what happened inside the sensor; turns out, it basically disintegrated itself. Wonderful. Not only had the electrical components destroyed themselves, the magnetic portion on what I thought was on the shaft also chipped and was broken. Solution So solution: find a spare part right? Wrong. Nissan has long discontinued the proper sensor part number 32702-21U19, and it is no longer obtainable either through Nissan NSA or Nissan Japan. I was SOL without proper speed or mileage readings unless I figured out a way to replace this sensor. After tons of Googling and searching on SAU, I found that there IS however a sensor that looks almost exactly like the R33/260RS one: a sensor meant for the R33/R34 GTT and GTS-T with the 5 speed manual. The part number was 25010-21U00, and the body, plug, and shaft all looked exactly the same. The gear was different at the end, but knowing the sensor's gear is held on with a circlip, I figured I could just order the part and swap the gears. Cue me ordering a new part from JustJap down in Kirrawee, NSW, then waiting almost 3 weeks for shipping and customs clearing. The part finally arrives and what did I find? The freaking shaft lengths don't match. $&%* I discussed with Erik how to proceed, and figuring that I basically destroyed the sensor trying to get the shaft out of the damaged sensor from my car. we deemed it too dangerous to try and attempt to swap shafts to the correct length. I had to find a local CNC machinist to help me cut and notch down the shaft. After tons of frantic calling on a Friday afternoon, I managed to get hold of someone and he said he'd be able to do it over half a week. I sent him photos and had him take measurements to match not only the correct length and notch fitment, but also a groove to machine out to hold the retentive circlip. And the end result? *chef's kiss* Perfect. Since I didn't have pliers with me when I picked up the items, I tested the old gear and circlip on. Perfect fit. After that it was simply swapping out the plug bracket to the new sensor, mount it on the transfer case, refill with ATF/Nissan Matic Fluid D, then test out function. Thankfully with the rebuilt cluster and the new sensor, both the speedometer and odometer and now working properly!   And there you have it. About 5-6 weeks of headaches wrapped up in a 15 minute photo essay. As I was told it is rare for sensors of this generation to die so dramatically, but you never know what could go wrong with a 25+ year old car. I HOPE that no one else has to go through this problem like I did, so with my take on a solution I hope it helps others who may encounter this issue in the future. For the TL;DR: 1) Sensor breaks. 2) Find a replacement GTT/GTS-T sensor. 3) Find a CNC machinist to have you cut it down to proper specs. 4) Reinstall then pray to the JDM gods.   Hope this guide/story helps anyone else encountering this problem!
    • perhaps i should have mentioned, I plugged the unit in before i handed over to the electronics repair shop to see what damaged had been caused and the unit worked (ac controls, rear demister etc) bar the lights behind the lcd. i would assume that the diode was only to control lighting and didnt harm anything else i got the unit back from the electronics repair shop and all is well (to a point). The lights are back on and ac controls are working. im still paranoid as i beleive the repairer just put in any zener diode he could find and admitted asking chatgpt if its compatible   i do however have another issue... sometimes when i turn the ignition on, the climate control unit now goes through a diagnostics procedure which normally occurs when you disconnect and reconnect but this may be due to the below   to top everything off, and feel free to shoot me as im just about to do it myself anyway, while i was checking the newly repaired board by plugging in the climate control unit bare without the housing, i believe i may have shorted it on the headunit surround. Climate control unit still works but now the keyless entry doesnt work along with the dome light not turning on when you open the door. to add to this tricky situation, when you start the car and remove the key ( i have a turbo timer so car remains on) the keyless entry works. the dome light also works when you switch to the on position. fuses were checked and all ok ive deduced that the short somehow has messed with the smart entry control module as that is what controls the keyless entry and dome light on door opening   you guys wouldnt happen to have any experience with that topic lmao... im only laughing as its all i can do right now my self diagnosed adhd always gets me in a situation as i have no patience and want to get everything done in shortest amount of time as possible often ignoring crucial steps such as disconnecting battery when stuffing around with electronics or even placing a simple rag over the metallic headunit surround when placing a live pcb board on top of it   FML
    • Bit of a pity we don't have good images of the back/front of the PCB ~ that said, I found a YT vid of a teardown to replace dicky clock switches, and got enough of a glimpse to realize this PCB is the front-end to a connected to what I'll call PCBA, and as such this is all digital on this PCB..ergo, battery voltage probably doesn't make an appearance here ; that is, I'd expect them to do something on PCBA wrt power conditioning for the adjustment/display/switch PCB.... ....given what's transpired..ie; some permutation of 12vdc on a 5vdc with or without correct polarity...would explain why the zener said "no" and exploded. The transistor Q5 (M33) is likely to be a digital switching transistor...that is, package has builtin bias resistors to ensure it saturates as soon as base threshold voltage is reached (minimal rise/fall time)....and wrt the question 'what else could've fried?' ....well, I know there's an MCU on this board (display, I/O at a guess), and you hope they isolated it from this scenario...I got my crayons out, it looks a bit like this...   ...not a lot to see, or rather, everything you'd like to see disappears down a via to the other side...base drive for the transistor comes from somewhere else, what this transistor is switching is somewhere else...but the zener circuit is exclusive to all this ~ it's providing a set voltage (current limited by the 1K3 resistor R19)...and disappears somewhere else down the via I marked V out ; if the errant voltage 'jumped' the diode in the millisecond before it exploded, whatever that V out via feeds may have seen a spike... ....I'll just imagine that Q5 was switched off at the time, thus no damage should've been done....but whatever that zener feeds has to be checked... HTH
×
×
  • Create New...