While I don't do anything with the Nissan ECU (I'm using a GM ECM on my Nissan L28), I would hesitate to use an XDF that makes the maps look like that. The maps should be somewhat smooth, at least no LARGE transitions and no negative numbers.
I can get the same thing or similar to display any of my bins, just by using the wrong xdf.
The other thing that might be happening is that when the E/EPROM was read the wrong chip was selected and has moved the information to the wrong addresses. I.E. using the 27C128 selection of a programmer to read a 27C256 E/EPROM. This would cut off the first half of the information, and then display very oddly with ANY xdf. Same thing happens when going the other way, though I know with my Willems programmers the bin will just be read twice into the buffer, still doesn't usually display correctly in Tuner pro though.
That's just how Nissan decided to do it. The pictured map is correct. Take a look at the conversion tab to see how the numbers displayed in the map are converted.
I stated in my prev post, that it is only in the primary fuelmap, but it is also in the ignitionmaps. so the problem is solved with the conversion table. But.... 1 question left....
Mangus wrote:I haven't yet, but plan to add support for these Nissan "MSB" maps to TunerPro. I just need to figure out a smooth, generic way to do it.
I tried using the & operator (X & 127) and all the map values displayed as 0, so maybe thats not working.
You might implement the conditional and relational operators in the conversion tab. (ex: (X > 128) ? X-128 : X) It would be nice to specify signed vs. unsigned values also.
Your best bet is to search and read through the Nissan tuning forums (I linked one in my original post), then join the forum and ask Nissan specific questions there. You'll find other Nissan tuners using TunerPro also.
taiajam wrote:I stated in my prev post, that it is only in the primary fuelmap, but it is also in the ignitionmaps. so the problem is solved with the conversion table. But.... 1 question left....
ok here is another printscreen
its the primary and Feedback of the primary.
what does the feedback map do?
Note that for both 'maps' I've got the xdf pointing at the same address. This is because Nissan is using a bit in each value to represent something within the map. In the case of the fuel map this is the region where the ecu is going to use the O2 sensor to make adjustments. In the case of the timing map this is where the ecu is going to use the knock sensor.
Because this flag is embedded in the values, just looking at the raw numbers looks weird. Think about the different views like a pair of bi-focals- one view is for editing the feedback region of the map, and the other is for editing the no feedback. When your editing one, its really obvious what your supposed to be editing- if the numbers are negative or look odd, they're for the other view!
Yea, if/then in the expression evaluator would be slick.
