Welcome to the SR20 Community Forum - The Dash.
Register
SR20 forum logo

Thread: NismoTronicSA Tuning Packages

+ Reply To Thread
Posts: 21-30 of 93
2012-02-15 21:04:36
#21
Originally Posted by Boostlee
A friendly reminder however (and at this moment, this is strictly for the OBD 2 guys), you need to factor in a step down harness into that price.

NOTE: I am NOT UNDERMINING NEMU at all by previous statements!!!


Yup, or make one. I am OBD2 32 bit, my only option was to make one. Next time I will just crimp the OBD1 ECU plug onto the wiring harness directly though.

Originally Posted by SentraThis96
Ya Their site is REALLY vague, I haven't seen too many screenshots on Nistune but NismoTronic looks relatively simple with a sleek layout which is another plus.

That's another thing, Nistune goes through the COMM port so you have to use that proprietary cable in order to tune and log, USB is SOO much easier and convenient.


Well once you go to the NISTune's order page it's not gets a lot clearer. I too though that you could have a real time ECU for just $240 until today, because I didn't now you had to buy a software license.

Now little more on COM ports, NISTune uses Consult connector, so you need a Consult to USB adapter ($95 from their website). While NEMU uses a USB (and does now non-supported Calum RT), they both also use COM ports. But that's how any external device like that will work. NismoTronic does make it very seamless though, by auto detecting and connecting to the NEMU COM port .


Originally Posted by SentraThis96
Nemu is the new Calum


It's a more then that
2012-02-15 21:30:55
#22
Originally Posted by Vadim
Yup, or make one. I am OBD2 32 bit, my only option was to make one. Next time I will just crimp the OBD1 ECU plug onto the wiring harness directly though.


You don't have to re-pin the harness connector?


Originally Posted by Vadim
It's a more then that


AND their readily available!
2012-02-22 04:28:34
#23
reading the specs and features I'm thinking this would work well with an ITB (no plenum) setup where you would not have a MAF or MAP. Am i right? I have a friend doing an ITB VE mainly for the cool factor but he does not want to deal with running a stand alone.
2012-02-22 04:34:40
#24
Originally Posted by jjkamikaze
reading the specs and features I'm thinking this would work well with an ITB (no plenum) setup where you would not have a MAF or MAP. Am i right? I have a friend doing an ITB VE mainly for the cool factor but he does not want to deal with running a stand alone.


With the new firmware you will be able to set it up however you want. You can have the fuel/ignition map load scale be by TPS, MAF or MAP.. it is up to you on how you would like to set it up.
2012-02-22 04:39:49
#25
sorry im not super up on my engine management. for what im talking about it would be by the TPS, is this far less accurate or efficient than having the ecu read actual air flow or density?
2012-02-22 04:50:27
#26
My friend is switching from MAF to MAP and told me he is going to use the stock MAF with the entire setup that he'll need (injectors, boost, timing, fuel etc.), log everything and then use the MAF readouts for his MAP, I imagine you could do something similar with individual throttle bodies?
2012-02-22 04:55:41
#27
Originally Posted by jjkamikaze
sorry im not super up on my engine management. for what im talking about it would be by the TPS, is this far less accurate or efficient than having the ecu read actual air flow or density?


It isn't near as precise, but it is rather difficult to rig up a MAF sensor to a set of ITBs and on a MAP sensor it goes to atmospheric with very little throttle.

The easiest way I have tuned ITBs was to tap each runner and run a vacuum line from each runner to a decent sized vacuum log. The attach a MAP sensor to the vacuum log.

Then setup two fuel/ignition maps. The first would be based by MAP sensor load and would be used to tune light throttle and right off idle response.

The secondary set of maps would be TPS based and would be used for WOT and heavier load conditions. You would switch to the secondary map based on pressure and TPS load. Basically you would switch to this map when the MAP sensor read right around atmoshperic (say 850-900 mBar).
2012-02-22 05:28:16
#28
Programmer's know best
2012-02-22 06:14:38
#29
Originally Posted by SentraThis96
You don't have to re-pin the harness connector?


Nope, but you can't even use the same plugs. OBD2 16 bit and OBD2 32 bit (B15 and P11) use two different plugs. Thus you have to crimp in the new connector or make a step down.
Last edited by Vadim on 2012-02-22 at 15-51-15.
2012-02-22 14:56:34
#30
Originally Posted by JKTUNING
It isn't near as precise, but it is rather difficult to rig up a MAF sensor to a set of ITBs and on a MAP sensor it goes to atmospheric with very little throttle.

The easiest way I have tuned ITBs was to tap each runner and run a vacuum line from each runner to a decent sized vacuum log. The attach a MAP sensor to the vacuum log.

Then setup two fuel/ignition maps. The first would be based by MAP sensor load and would be used to tune light throttle and right off idle response.

The secondary set of maps would be TPS based and would be used for WOT and heavier load conditions. You would switch to the secondary map based on pressure and TPS load. Basically you would switch to this map when the MAP sensor read right around atmoshperic (say 850-900 mBar).


smart guy, that sounds like a very good way to manage ITBs. thanks for the input.
+ Reply To Thread
  • [Type to search users.]
  • Quick Reply
    Thread Information
    There are currently ? users browsing this thread. (? members & ? guests)
    StubUserName

    Back to top