2 Byte RPM for IX - 88590015?
2 Byte RPM for IX - 88590015?
Has anyone done a write-up on this or can post a write up? (yes I searched)
I did the 2 byte load and im looking to do the 2 byte rpm as well on my IX so any info. would be greatly appreciated.........
I did the 2 byte load and im looking to do the 2 byte rpm as well on my IX so any info. would be greatly appreciated.........
Switch to a 13 or 14, and if you need to change the injector scaling use the method I posted up a month or so ago. Other than having to build a new map by copying everything over, its not that difficult.
JB
JB
Trending Topics
pd1 pm'd me today asking about this so I thought I would post here as well:
2byte RPM was easy - BUT i think there might be something wrong with it.
find your high octane map, then look up the rpm axis andd find that in the ROM
the previous 2 bytes should be 00 0F, the previous 4 bytes to that will be FF FF XX YY.
Thats the memory address for RPM that the ECU uses when looking up MAPS...
BUT when I log that and normal RPM, 2byte RPM seems to LAG behind normal RPM by 1 request if you know what I mean...
let me know how you get on!
cheers
d.
2byte RPM was easy - BUT i think there might be something wrong with it.
find your high octane map, then look up the rpm axis andd find that in the ROM
the previous 2 bytes should be 00 0F, the previous 4 bytes to that will be FF FF XX YY.
Thats the memory address for RPM that the ECU uses when looking up MAPS...
BUT when I log that and normal RPM, 2byte RPM seems to LAG behind normal RPM by 1 request if you know what I mean...
let me know how you get on!
cheers
d.
I believe the normal RPM log is always in "steps" of a certain value and the 2-byte can respond with any RPM value. The 2-byte is faster also I think. I'm not really sure though. the 2-byte mods are always about accuracy and extra information.
For calculating HP, etc, having a resolution better than 31.25 will help out and make your RPM less steppy in your logs.
Eric
