Thread: NismoTronic Tuning Software for TunerCode

Actually the OBD2 system is a completely different system than the OBD2 stuff, hence why it hasn't been developed yet.

What is available (other systems) for the OBD2 cars right now is the STOCK OEM firmware and at that it is not very well documented or understood. I am not going to fully support something that I don't trust in the application. Once Dave moves onto it in the future then it will definitely be added in there!

It is plausible in the future to run an OBD1 style bin/tune in an OB2 ECU.. but that still needs to be worked on.

The only issue with that is emissions. Luckily for me it's easier to just run a stepdown, but not for most others.



I understand where you are coming from, I used to think the exact same way until I started using TunerCode and then NismoTronic.

Right now if you look at the B13 or B14 XDF (Definition) files, you will see a that there are a ton of unknowns in there. Unknown table xyz. Known Table against an unknown RPM/TP/CLT scale. etc.

Nistune gets around this by simply restricting you to a specific set of functions that you can tune. While TunerPro XDF files are build by the community/Calum, thus they are not restricted to just the known functions.

Now If John as to make NismoTronic for OBD2 cars, you would have a few things you can modify, just like Nistune, and he would have to ignore the unknown/undefined items. If he lets you modify the unknown/undefined items and you break your car you will try to hold him liable.

There is no point in making NismoTronic work with non-tunercode bins, simply because you already have that functionality with TunerPro. Now NismoTronic does make it geared towards our specific ECU's. Thus it becomes easier to tune it, because you don't have to look through menu's just to find the cold start table.

BUT on another side of the spectrum NismoTronic does have great reporting and now has AEM UEGO support, two big pluses that TunerPro doesn't have. Which for that alone it would be nice to have NismoTronic work with non-TunerCode bins, but the whole liability mess then comes to mind.

The only problem you have with emissions is if you try to pass using the OBD1 ECU.. just convert it back to OBD2 ECU/injectors/maf and you will pass without an issue.

I have personally done this my personal cars that I have had to convert to OBD1 for tuning purposes (Hondas).. but the exact same concept applies here.

I would just unplug the OBD1 ECU and plug in the OBD2 ecu and make sure all of the sensors were atleast there. Now, I understand that some people may not want to go through all of the hassle, but for the most part it wouldn't be that difficult to do.

I have my stepdown harness ready, just waiting for your OBDI Realtime ECU/Tunercode/Nismotronic...

I need a harness and the ECU!!!! Go Go Go John, Go!

sorry wrong section

OK so say I were to convert to OBD1 I would need:
Step down harness
OBD1 ECU
Tunercode installed on obd1 board?
and nismotronic?
Is this correct as i'm confused on who mods the obd1 ecu.

Need a step down and OBD1 Calum ECU/JKTuning Basic. Then just buy TunerCode for that ECU. Or you can wait for the NEMU boards that we are all waiting for :-D

Make sure to grab the new version 1.9.95 for a bunch of updates.

Also have a few things coming in the next release, watch for it around the 1st of the October.

Anyone use the PLX SM-AFR series widebands or anything with the iMFD protocol?

I am planning on integrating this into the program and am looking for a tester. My test unit should be on the way to me this week, but was looking for another person that could test it as well.

Shoot me a PM if you would like to help.