Thread: NismoTronic Tuning Software for TunerCode

function of history tables are also incorporated into nismotronic?

ahh i see

I haven't really ever used the "history tables". I might have had something in mind that was similar to what you mean, but I am not sure exactly.

I will have a RPM vs TP vs AF graph though for a simulated dyno pull. I am working on that next. It is very useful to have something like this especially when tuning on the dyno. It will basically populate the graph anytime the TPS is > 90% and pretty much will look just like a a/f chart that you would see at the bottom of a dyno graph.

yes,also for monitoring knock detection.

I will look into doing some sort of user definable overlay table for comparing sensors to the main fuel table, similar to the lambda table that is shown at the end of the vid.

how is it youre connecting to the maptrace? is it a realtime board or via the consult?

It supports logging via the Calum RTV1 board and via the consult port if you are running a chip based board.

TunerCode logging protocol doesn't use regular consult commands. Don't confuse the information you can view with NismoTronic with what would be normally visible via regular consult commands as TunerCode is no longer limited by the factory consult logging.

i meant if its connected via the consult port in the car dude... and i do run tunercode also, so i am fully aware of what it can do. keep up the good work however

Actually, it supports logging through the consult port with ANY daughter board running TunerCode.

Dave

Map trace is a functionality provided by the logging software, Nismotronic in this case, regardless of what type (basic vs. realtime) daughter board is being used. The logged data is transferred from TunerCode, running on the ECU daughter board, to Nismotronic, running on the PC, via the consult port, but using a special TunerCode logging protocol.

Dave