I use the Innovate Auxbox / or LM-2 and attached a 3-Pin device from Analog Devices.
The AD Chip is actually a highly integrated sensor and is powered by the Auxbox.
Nistune connects to the Innovate device, so I have temperatures appearing in the log-view.
Of course it would be nice to have the temperature read by the ECU, but strangely enough the ECU (Z32) is not bothered by intake temperatures or boost pressure at all.
(The ECU lives by the moto of 'what goes in, must come out' )
How to get external data into NIStune?
Moderator: Matt
Re: How to get external data into NIStune?
So with the 26 ecu it is possible to have ignition/fuel correction based on inlet air temperature?PL wrote:Yeah, that'll be the big difference between RB20 and RB26 systems - RB26 has inlet air temp sensor. Might be worth scrounging a 26 loom and ECU for this reason.
PL
Assuming this is the type 2 r32 gtr ecu you are talking about?
Is there a comparison of the different features between different ECU/Nistune board combinations? Curious what features the type 4 r34 boards have compared to the type 2 as all of these ECUs could be fairly easily adapted to quite a few engines.
Thanks.
Re: How to get external data into NIStune?
Theres no comparison
ER34 doesnt have IAT. It has boost control which requires investigation and VE tables
Still to look at the AIT tables on the GTR but just dual maf and this are the differences to normal R32 ECU
ER34 doesnt have IAT. It has boost control which requires investigation and VE tables
Still to look at the AIT tables on the GTR but just dual maf and this are the differences to normal R32 ECU
Re: How to get external data into NIStune?
The different features come down to the ECU, not the NIStune board itself. If the feature is present in the ECU then we can use it - once we know the address.
It's also a matter of digging out the addresses for all the different parameters in the code for each ECU. This is a time consuming and ongoing process. That's why if you look at the Z32 you'll find there are stacks of parameters available to edit - that's because these ECU's are very well known. This usually comes down to one (or a sometimes a small group) of dedicated enthusiasts (like Eric in the Z32's case) going through the ECU's code line by line and working out the functionality.
PL
It's also a matter of digging out the addresses for all the different parameters in the code for each ECU. This is a time consuming and ongoing process. That's why if you look at the Z32 you'll find there are stacks of parameters available to edit - that's because these ECU's are very well known. This usually comes down to one (or a sometimes a small group) of dedicated enthusiasts (like Eric in the Z32's case) going through the ECU's code line by line and working out the functionality.
PL