Fuel Tuning
#2
#3
I was there for that thread. I don't recall the process of adjusting fuel. The thread was mostly theory and no instruction on how to use the program. Do I just install it and start playing with it? If the software is intuitive enough I'm sure I'd be able to figure it out.
#4
It seemed like you wanted a yes or no answer.
The easiest way to do what you want is to adjust the injection k factor by 15%, assuming the software has one, then adjust the MAF table from there for the other 5% where you actually need it.
The easiest way to do what you want is to adjust the injection k factor by 15%, assuming the software has one, then adjust the MAF table from there for the other 5% where you actually need it.
#5
I'll put RomRaider on my laptop and start familiarizing myself with it. I'll get back to this thread soon, have a few things to get done today.
Thanks for responding.
#7
Wish I knew all along it was that simple. I still haven't had a chance to plug the laptop into the car or even open the program. I have a couple ECU's in case I brick one. I'll get on this on the weekend at the latest. Pulled some extra shifts. Thanks, guys.
#9
I'll just follow this guide:
http://www.romraider.com/forum/viewt...p?f=64&t=14867
I'm off tomorrow. I'll report back tomorrow eve after I add fuel and WOT test runs.
http://www.romraider.com/forum/viewt...p?f=64&t=14867
I'm off tomorrow. I'll report back tomorrow eve after I add fuel and WOT test runs.
#10
Yep, and link to defs found here: https://www.romraider.com/forum/view...p?f=64&t=13325
#11
#20
Your ECU architechure is 7055_35, that's the kernel you'll need to run. So once you've connected and you have the kernel saved in the same directory as you are running nisprog from...
setdev 1
runkernel npk_7055_35.bin
flrom MYNEWROM.bin
setdev 1
runkernel npk_7055_35.bin
flrom MYNEWROM.bin
Last edited by freezer; 01-28-2021 at 05:57 AM.
#21
Right on, thanks. Thought I needed to pull by base image before I flashed it. Still putting this all together. The nisprog I had ran fine, I used several commands while connected to the car. That's how I got my ECUID. What "keys" did I need? I'll work on this when the sun comes up.
#22
Do I have to convert the 6Y314.xml to .bin or something? I added 6Y314.xml from the defs master into RomRaider. Didn't make sense because I thought it wanted binary files but I added anyway and of course it can't be found.
#23
6y314 is an update of 6y310. There's a TSB out for it. Supposed to improve MAF, reduce a transient hesitation issue IIRC. Always best to grab all the factory fixes you can.
I dunno the condition of your fuel pump, but I got a 15% fuel bump when I replaced my failed stock pump with a DW100.
#25
Ha! This from the guy who spent his much time on his BBK?
I don't know what part you're having trouble with, but if you've managed to connect with nisprog you're ahead of 90% of the crowd. I'm already set up to do this, but your scope of work would take me 5 minutes start to finish.
I don't know what part you're having trouble with, but if you've managed to connect with nisprog you're ahead of 90% of the crowd. I'm already set up to do this, but your scope of work would take me 5 minutes start to finish.
#26
nisprog, code, scripts, COM issues, none of that is a problem for me. I need a .bin that doesn't exist. I have yet to find, or even open a .bin, (any .bin at all) with romraider. If it's that ridiculously retarded of a process just to obtain and OPEN an ECU base image, then it'll be nothing but problems, it's faulty and I'm not interested. I'm not even wasting anymore time on this. Got a BBK to finish.
#28
I gave it one last stab and took the time to complete the painfully arduous process of registering for RomRaider.com and downloaded 6Y314. As a non-member, you do not have access to view or download posted files. So tired of signing up for ****.
I'll check back someday after I have the time to learn the program enough to understand and decrypt post #6
I'll check back someday after I have the time to learn the program enough to understand and decrypt post #6
#30
It that's the case, I'm ready to flash. kernel is in the same disk location as nisprog.
#This is just an example .ini file to show some of the possible commands.
set
interface dumb
#Customize this to your hardware
port \\.\COM3
#This should always be OK
dumbopts 0x48
# No need to touch these unless you know what they are
l2protocol iso14230
initmode fast
testerid 0xfc
destaddr 0x10
addrtype phys
up
setdev 1
runkernel npk_7055_35.bin
flrom C:\Users\JQual\Downloads\ECU ROMs\6y314_edited.bin
#This is just an example .ini file to show some of the possible commands.
set
interface dumb
#Customize this to your hardware
port \\.\COM3
#This should always be OK
dumbopts 0x48
# No need to touch these unless you know what they are
l2protocol iso14230
initmode fast
testerid 0xfc
destaddr 0x10
addrtype phys
up
setdev 1
runkernel npk_7055_35.bin
flrom C:\Users\JQual\Downloads\ECU ROMs\6y314_edited.bin
#31
Connected to car, no fans, no worries, all was good. Did not flash yet. At work and don't want to risk needing an Uber home in the morning. While we're at it, may as well up the rev limiter to 7,200. How do I do this
#33
No, don't need to do reverse limiter. And you've got the fuel K and mTP100 adjusted properly. When flashing over 6y314 it'll change almost all of the blocks, so a reflash will take a couple minutes. I'd also suggest doing it at home, it would suck to have a brick at work. Especially the first time around.
I quickly forget you have to register at RR to download stuff, I could have uploaded a copy but I was responding from my phone.
I quickly forget you have to register at RR to download stuff, I could have uploaded a copy but I was responding from my phone.
#35
No cigar. Your lines in post #20 are different than stated in the RR tutorial. Tried running the kernel line alone to see if it would grab the rom, didn't work. Tried adding the rom address after the kernel command and still no cigar.
#40
Saw it in the earlier post. "ECU ROMs"
setdev 1
runkernel "your_directory"\npk_SH7055_35.bin (the SH was missing)
flrom "your_directory"\6y314_edited.bin
I put nisprog in a root directory on c:, eg C:\NISPROG to save typing out long directories. Put nisprog, the .ini, the kernel you need and the rom you want to flash in there.
setdev 1
runkernel "your_directory"\npk_SH7055_35.bin (the SH was missing)
flrom "your_directory"\6y314_edited.bin
I put nisprog in a root directory on c:, eg C:\NISPROG to save typing out long directories. Put nisprog, the .ini, the kernel you need and the rom you want to flash in there.