Nistune Release 0.11

[ricardomendes]

hi matt tried this night and i notice a strange thing, with the engine running if i push the connect button the engine start to go lean, if i disconnect he goes to target. my normal idle is 14.6afr and it goes to 15.1afr with nistune on.

nistune ecu on ca18det.

regards

[Matt]

has this only just started happening? What was the previous version you were using?

[ricardomendes]

I was using 10.21 and only download the new one because have passed the 90days, and it started right on the first connect, I tried today and happened again, I will try with an older version and see what happens.

[bachig24u]

have you tried downloading from the ECU and comparing the tune to the one on the PC?
maybe they are not synchronized.

[Matt]

0.10.21 was released 1 Aug so it should still be in the current valid period (90 days). Future versions are now 6 month windows (180 days)

[RomChip200]

Something strange with (Z32):
FUEL_INCREASE_RATE,&H79FF,1,1,1,1,Fuel increase rate adjustment

When the memory location contains 0x0A (OEM value), you display 0x03 in Nistune (you assume it's 30% but 30% of what !?)
If I increase to 0x06 to give it a try, you seem to apply it but the bin gets 0x02.
I need to put 0x19 to get back 0x0A in the bin.

What's the rationale ?

And btw, have a look to this:
viewtopic.php?f=8&t=1956&p=18252#p18252

[Matt]

This new iMFD functionality sounds poised to take Nistune to the next level and I will definately volunteer to share any information I get from working with iMFD hardware as I should be in possession of a PLX kiwi with the iMFD expansion by month's end.

iMFD functionality is completed. will be in next version ready for people to try out. Seems to work with my simulation

Temp conv: the horizontal scale hit 28 volts. The log I took the other day before our trusty test bed died showed 8v but I think its actually half of the displayed value.

It was actually 1..32 cells on the horizontal scale. I've updated this to display as 1 .. 5.12 volts now

FUEL_INCREASE_RATE,&H79FF,1,1,1,1,Fuel increase rate adjustment
When the memory location contains 0x0A (OEM value), you display 0x03 in Nistune (you assume it's 30% but 30% of what !?) If I increase to 0x06 to give it a try, you seem to apply it but the bin gets 0x02.

Japanese documentation for this parameter:

79FF 08FF KMRPAR KMR increasing rate initial value 1 100/256%

Basically value is /256 * 100 to get a percentage but discussing with a tuner last week and found the same problem as you. Parameter is not being converted correctly in that window. I'm looking into it now

[RomChip200]

Japanese documentation ?

Well, I found that:
http://tangentrix.com/forums/viewtopic. ... ht=skyline

I can tell you what is found on R32 is not applicable to Z32 (except few locations).
A typical example is all the addresses of params starting with 0x78xx, 0x7800 is a timing map on Z32 !!
So, 79FF has not the same meaning on Z32 ... and most of the params are differents in the 0x79xx range ....

Note: I don't even understand the organization of the params on R32, starting from 7200 to 7FFE, this is NOT COMPARABLE to Z32, Z32 has reset vector @0x7FFE !
Is R32 ECU Hitachi 6303 family based !? I think not ...

[Torque]

Has it ever been established what FUEL_INCREASE_RATE actually does and how it is related
to the elusive throttle enrichment table?

I asked about throttle enrichment a few times but it was never made clear how it works.
Especially the 'accessing the last column of fuel map' explanation I always found a bit cumbersome.

Something strange with (Z32):
FUEL_INCREASE_RATE,&H79FF,1,1,1,1,Fuel increase rate adjustment

When the memory location contains 0x0A (OEM value), you display 0x03 in Nistune (you assume it's 30% but 30% of what !?)
If I increase to 0x06 to give it a try, you seem to apply it but the bin gets 0x02.
I need to put 0x19 to get back 0x0A in the bin.

What's the rationale ?

And btw, have a look to this:
viewtopic.php?f=8&t=1956&p=18252#p18252

[RomChip200]

Everything I read up to now confuses me, and particularly, b/c I don't manage to crosscheck it on Z32. So, I prefer sticking to the code I have, it always tells me the truth.
See my other post viewtopic.php?f=8&t=1956&p=18252#p18252 to discover that FUEL_INCREASE_RATE param (@ location) on R32 is something completely different meaning on Z32 ....

[Matt]

From that document the addresses are R32 based. Some of them overlap with the Z32. Yes both are 6303 based and there are groups of tables which dont appear to be valid for even the R32 ECU.

As you mention areas with timing tables and vector tables were obvious. I'm not sure where those definitions came from (even the same applies for the R33 ECU definitions)

As you mention there are many differences between the two, so these are covered specficially in the Z32_VG30_256_E.adr file

So I'll remove this one out given this is not valid for Z32. Looking at the HCR32 code I cannot make much sense from the address either

[ricardomendes]

I made a movie to show the problem found, start the engine then open nistune software and only connect the wideband, then connected and disconnected to the vehicle.

See please :

[img=http://img87.imageshack.us/img87/5877/bialzlqcbzxjtmqffdgzpg.mp4.th.jpg]

[Matt]

Movie seen. AFRs going leaner when connected at idle. Does it do this still when you roll back? I'm going to lock this thread now (this report should be in the bug section...)

Please email me when you try the previous version and will try and sort via email instead