here's a hint

this is probably what i'll be using JDiff

 

so which is the easiest way? to take his rom and compare it to a stock rom and then make those changes? or match all the values on my preexisting rom onto his rom?

 

ill tell you what, nothing on this is easy. or im a complete idiot. this has been taking me 3 hours and im still getting the same messgee from ecuflash . no response to any known code. i have tried everything people told me and no luck. i dont get it.

 

i understand the whole situation, i just need to figure out what is the best advice with my preexisting rom.

 

HELP!!! I have no clue what i did wrong... I did the patch, moved my maps over then went to flash, but before I flashed i wanted to read the current rom on my car for a fresh back up. When i click read ecu the screen comes up but I cant select any model (mitsu, subi ect.ect.) They dont show up???? I have re installed ecuflash 1.30 and the tatrix drivers and still same issue, any clue? I want that fresh rom just in case, Thanks!!!!

 

So what do you guys suggest for 'easy to use' hex editors available online for free download?

 

I think you guys would be better off asking tephra if he minds you trying to rip his patch out of the roms he has done.

I am sure if enough people wanted to apply the patch to there modded roms, then he would make some kind of patch tool availiable.

 

I asked about the hex editor for other applications...like finding MUT locations and such. I used Daves roms and also donated for his great efforts

 

Less asking, more copying. There's no "best advice", there's ONLY one. It took me longer to type this than it would take you to copy all tables.

 

XVI32

 

i copied the fuel maps and few others things over. what are the parts of tephra's stock rom should i save? turbo information?

 

ohthree if you are having difficulties email me the ROM and add $15 onto whatever you planned to donate and I will patch YOUR rom and email it back..

 

i planned on sending a donation, but i dont want to waste your time. i have a pretty good grasp of all of this, instead of sending this id rather do it myself so if any problems arise in the future ill know what i did. just need some help .

 

after 6 hours of work i fially got it to write to my ecu but it doesnt work lol nlts doesnt work at all, no clue what i have done wrong any ideas? it shows up under mnods and i can change the settings of them all but they didnt work any thoughts thanks"?

 

I copied the data from my old ROM into this one. Going through everything in EcuFlash couldn't have taken me more than 10 minutes of "CTRL-A, CTRL-C, CTRL-TAB, CTRL-V, repeat".

FYI, I can confirm that at least NLTS and the knock light works great on 96940011. I'll check valet mode later, but I suspect that's working fine.

The only complaint I have (if you can even call it that; this is a huge improvement over what we had before) is that I'm very used to how NLTS on DSMLink and the code I wrote for our old 1g DSM worked: that is, rather than an RPM "drop", you have a fixed target NLTS RPM. So, rather than revving to 7000 RPM, then having an offset applied to current RPM for target shift RPM, you'd have an ideal target shift RPM set statically, so that no matter where you shifted, you'd get a consistent mid-shift RPM. Handy for the occasional freeway pull where you'd like to build a bit of boost before accelerating.

I've also noticed that, unless I set the TPS threshold very high, quick throttle blips when downshifting get squashed. (ie. You're at 3000 RPM in third, clutch in, blip the throttle to get the RPMs up, shift to second; NLTS as implemented here trips me up pretty good, because it doesn't allow engine speed to rise higher than 2500 RPM, while the fixed RPM version does pretty much exactly what you'd expect.)

But regardless, thanks for putting this together, tephra! Is there a more technical discussion thread either here or on AktiveMatrix about the NLTS code you've added? (I'm curious about the rest, but the NLTS stuff is what I'm most keen on).