Nistune Forums

You found a glitch (of sorts) in the software You see most MAFs are 0-5V but the R31/VLT/Z31 are 2-7V There is a fixed limit for condition checking in the software, and that is hard coded to 5V. We will need to put in a fix to check the vehicle type so if it is set to 2-7V MAF that the range is incr...

Use consult active tests to force timing (otherwise disconnect TPS when warm to get about 15 BDTC)

See attached

Replied via email. Consult connection showing corruption over lines

It's been a long time since I've done the code for this, but there was a MAF calibration input, which was hard set at the MAF. So we were able to reuse this line without affecting the MAF otherwise

We didn't want to accidently activate/deactivate for each gear change with neutral switch (for example if no speed input working, or if not wanted). So other switch was added (it was difficult to get working too) FP1 is push on/push off. I updated that in FP1.1 to temporary push on, as that worked b...

We only support the N1 unit as you can see in the drop file for the MAF list

I've got my crank tables set as pictured for 1000CC (HPX MAF with mine)

1150uS for the latency

Not sure about your UEGO. Bad placement or sensor not working properly. Add more to the 'total injection multiplier' to add more fuel over the whole range

This is what the ECU does when it is reaching about mid rpm/load it will switch from sequential to batch mode with the two banks of injectors. Effectively firing them twice as often, so reducing the injection time by 50% to compensate If this causes an issue when going on boost, you can tweak the ba...

You need to sync (either download or upload to the board) before making changes

Yes you understood correctly with the fix for the RPM limit As you noticed, the current version address file also had the DTC flags. This only stops check engine light and DTC codes appearing in Nistune Mapping guide on our website has the details for each map. The Alpha/N table simply tells the ECU...

I've fixed in this file, so upload this first with the current address file (WORD) addressing if you uploaded/burnt this in the ECU

Then move to the fixed address file with BYTE addressing after and adjust RPMs

Might had used the wrong version address file when I posted the updates for the offset on here The numbers should show as single bytes, not words like you had REV1_LIMIT,&HFFB4,1,1,1,50,Rev. Limit 1 REV2_LIMIT,&HFEF5,1,1,1,50,Rev. Limit 2 REV3_LIMIT,&HFE75,1,1,1,50,Rev Limit CEL See atta...

Log is looking better Would put min load (TP) a bit higher to prevent such a lean out on decel. This will increase minimum TP allowed For acceleration you can see stock AlphaN (where throttle enrich makes TP go to max load). You can reduce this to prevent over fuel on full acceleration I'll have to ...

With fueling, I'm not sure yet from the log since the TP was an issue. Might need another log, but the early ramping in your fuel map is an indicator of an issue. Probably you had this due to early spool up of the super charger. We are seeing 45% duty in the logs

With the TP. That is strange, it is not added properly to the consult table You will need to manually add it in, then burn to keep it for next time 1. File > Config > Misc > User Mode => Set to Expert 2. restart Nistune 3. Display > Hex Editor 4. Browse to Line E700 (as per screen shot) Nistune [Inf...