Thread: TunerCode Feature Suggestions and Feedback

Yup sure did, he said it would be nice to have a thread where people can ask for features.

Yah, acceleration slew rate would be the way to do traction control IMO too.

Vadim, the way both of your suggestions are worded, they could only be accomplished with an drive-by-wire throttle. Gross.

Nate, if he has an extensive list, can that get posted here so we don't start doubling up things? Or?

Here's a list of the new TunerCodeSA (V6) features/functions for the new NEMU realtime and NismotronicSA tuning software, in no particular order:

1. Individual cylinder fuel and ignition trims.

2. Map switching via programmable IO system.

3. Load source switching via programmable IO system.
Load can be from MAF, MAP, or TPS.

4. Nitrous fuel and timing trims.

5. Programmable IO expanded to include:
Triggers on RPM, TPS, CLT, IAT, Load, VSS, AFR, Battery Voltage, Gear, 4 NEMU ADC channels
Digital inputs
4 output ON delay and/or ON delay timer reset timers.
4 Idle PWM settings (A/C, PSP Switch, Rear Window Defogger, etc.)
Functional Outputs for Nitrous trims, Map Switch, Alternate Injector Size, and Fuel Cut.
Output control on Limiters
Output control on Knock
Triggers and inputs can be ANDed or ORed.

6. Wide Band Closed Loop PID fuel control with Target AFR Map

7. Accel and Decel fuel control on TPS and/or MAP.

8. Baro Fuel trim.

9. IAT Fuel and Timing trims with Density Correction Map.

10. Knock Control, including individual cylinder knock limits by RPM.

11. 2 Step Launch w/programmable launch RPM. (Set Launch)

12. Anti-Lag Retard.

13. Flat Shift (w/clutch switch connected)

14. Flood Clear Fuel Cut.

15. Fuel Pump Control (ON/OFF with Throttle and shifter)

16. Cyclic Fuel and Ignition Cut (Selectable Spark Cut for different limits)

17. Split MAP Load/MAF Load (switch between MAF and MAP for load and fuel/timing maps using programmable input.)

18. Programmable Injector Timing.

19. PWM Boost Control w/boost by gear.

20. Enhanced DTC control/logging.

21. Fuel and Timing Maps expanded from 16x16 to 20x20. (2 Sets of fuel and timing maps, each set has Primary and Alternate maps, total 4 fuel and 4 timing maps)

22. NismotronicSA Programming and Data Logging.

23. Flex fuel support for fuel and timing.

Please comment/question.

Cheers,
Dave

I think if you accomplish even most of your list you'd have a world class solution on your hands.
I think usability of the tuning and logging software might be a place to move development effort to when you're done with all the hardware features (I haven't actually ever seen or used either though, just assuming).

The only thing that's not written yet is boost control.

Also, I currently don't have narrow band O2 closed loop control included, only wide band. Thoughts on the necessity of narrow band O2?

Thanks,
Dave

man....now i am envious,. im running nistune type 4.....maybe ill try to sell it for this...

From what I've read narrowband O2 closed loop control is identical to wideband closed loop except it is useless outside of the narrow window around 14.7:1 AFR so it can not be used in a large chunk of the operating range of the engine. Both narrowband and wideband compensation calculations have trouble keeping pace above 5k rpm or so, making them unsafe above those engine speeds. From what I've gleaned, narrowband O2 feedback is a limited subset of wideband feedback i.e. useless.

Having narrowband support is nice because not everyone has a wideband. And even if some folks do, they remove the sensor after they are done tuning. Plus narrowband sensor life usually is twice as much as wideband. It's a good feature to have basically .

Now I would love to just run my wideband, and get the ECU to read the narrow band for daily driving, then read the wideband portion when I'm tuning. Is it possible for the ECU to read actual wideband readings and just pay attention weather it's richer or leaner then 14.7 like it does now?



Nistune is miles behind even the current Calum ECU's with TunerCode.

I think just about all of them are already in some state of working at the moment and some are finished.

If you have any suggestions for software implementation.. I am all ears.

Also. adding narrowband support would be a good thing. Because some people are going to want to run their stock O2 sensor at some point.

The two major differences between wideband and narrowband code are the target voltages (narrowband ~.51 and wideband ~2.5 (depends on wideband).

The other is that the percentage change is usually backwards.. meaning the higher the voltage for a narrowband sensor means it is rich where as the higher the voltage for wideband sensors means it is lean.

In stock form and using a wideband into into the ecu, the ECU would pull fuel if you are above your target voltage and this would make it exponentially leaner as you get further from your target o2 voltage. Switching how it applies the percentage difference would take care of it for the most part.

So the code just has to be switched around for which ever type of sensor you are using to help achieve your target voltage (AFR).