Hello David,
I try to explain the problem better I can:

On my EVO 7 RS the clutch switch are not installed (both the upper and lower).
I know NLTS needs the upper swicth only, so I bought a genuine Mitsubishi EVO 8/9 upper clutch switch and I wired it to the correct ECU pin and to the ground.

I had as reference an EVO8 in my garage to verify my work, and I think it is OK because the EVO8 with OEM switch installed has the same problem than my EVO7. This EVO8 is RS model, and ECU works good with 90550001 def.
I test your mods 5.10 on EVO9 (88580014) too, but with this definition the same switch works good.

This switch is "normally-closed" because the clutch pedal push it when released and let it open, when the pedal is down the switch is released -> active.

With NLTS=1 (90550001) this switch works reversed (on both EVO7 manually wired and EVO8 OEM):
With pedal released, the fuel cut comes when the NLTS threshold values are achieved (load / TPS / speed).
With pedal pushed down the cut does not come: exactly the opposite way respect EVO9 88580014.

Do you think it could be possible to reverse the ECU PIN by "normally-closed" to "normally-open" by software with a fixed .bin file? Or the only possible solution could be to change the switch with a "normally-open" one?

Please let me know if you need my xml and hex files to verify it, I work with SD mod too on my car.

Thank you,
Nik

 

i didn't see those settings in my ROM.. so i was a bit confused. i was advised to upgrade to a different ROM. i haven't had time to check out the coding on the newer one.

 

well iv been searching but i have not found it yet but whats this i heard about a mod for a launchmap (anti-lag) is it under the V5.10 mods or is it something totally differnt. any help would be great thanks

 

another noob question while im trying to figure out how to do this is where do i find the differnt 1.30 and below stuff or the 1.31 and higher stuff. im reading the how to mod your rom thread and it says i need either or. or does this new V5.10 mod not need it? again any help is great

 

^^^bump for me and my questions?

 

I'm lost with your questions, what are you looking for? Anti-lag stuff?

 

Launch maps not on V5.10 check later mod thread.

Antilag? What do you need to know?

I think you're referring to the endian change?

Bump for extra clarity from yourself

 

well i know its not antilag but i was refeering to the launch maps that i heard and seen a vid of and as for my other post but if its in the newer V6 then ill wait for that,

well i was reading a how to for how to change my rom id to an id that tephra supports so i can have all the mods but as i was reading it said that i have to check mu current version of ecuflash and chose between the 2 (1.30version)-(1.31version) to copy and past into my rom id. when i find it ill post it up if you still dont understand what i mean. but i didnt know where to find that info

 

V6 has some launch features yes, you need V6.

ECUflash 1.3 and earlier has an endian flip issue. Basically there is a small difference in the xml definitions for the tables. That is the only reason it asks. There is no functionality differences between the ECUflash versions. just make sure you know which version of ecuflash you have and copy the appropriate XML stuff.

 

RE: the endian issue, the instructions are in the supplied 5.10 xml.

You'll be using a newer version of ecuflash i presume, so just change the endian=''little'' to endian=''big'', if it's not already 'big' obviously...


i.e.

<-- THE BLOCK BELOW GOES INTO ECUFLASH XML BEFORE "</ROM>" at end of file -->
<scaling name="1bytefactor" units="units" toexpr="x/((32/10)*100)" frexpr="x*((32/10)*100)" format="%.1f" min="1" max="2" inc="0.1" storagetype="uint16" endian="big"/>
<scaling name="ECUTime" units="ms" toexpr="1000*x/102" frexpr="102*x/1000" format="%.0f" min="0" max="100000" inc="1" storagetype="uint16" endian="big"/>

 

is there a version of ThepraMod for 93660005 ROM ? If so, where I can find it ?

 

Hi guys, I hope you R doing good!
I have this question for you on patch 5.1 (88590015): How many Knock Sum the alt map need to switch from high to low map??? I have been doing some new logs last week and in first instance, I think there is a bug since I get some 7-9 knocks during 3 seconds, the WGDC seems to switch (use to peak 28 PSI on alt map) but timing is not...
Here is the log file.
Can someone please have a look?
Thank you,
Cheers,
Christian.

 

It works the same as the stock maps. A knock count higher than 6 decreases the octane number, which in turn begins interpolation to the low octane map. There is no 'switch' to the low octane map, so to speak.

In your case, you would get about 3* timing being pulled for the 9 counts of knock from the knock control and then if knock continued for long periods of time, above 6, then the octane would lower until it reached 0. Then you would be on the low octane maps. But, I would highly doubt you would ever see that. So, you will never get to your low octane maps unless there is a major knock problem for long durations.

From your log, it looks like you are trying to run 7* of timing at 3500 RPM along with getting a rich spike to about 10.9. That may be a little too much timing. Lower that a degree or two in that area and try again and/or lean it out just a tad.


Eric

 

I can't get EvoScan and my Zeitronix ZT2 to log together at the same time. Can someone please let me know the changes I have to make to the XML of Mitsulogger V2.0 in order to read 1byte load? Thanks.

Dan

 

My ZT2 logs perfectly. Are you sure it isn't your usb adaptor cable? Make sure the driver is up to date and that the connections are good.