RomRaider

Hello everyone !

Great workwith RomRaider editor, nisprog, and whole knowledge and tutorials.
Awesome work!

I am newbie here, with some experience already.
I want to share and ask for help.

I attach stock rom CK001 + DEF XML (working 99%, read below)
car: NIssan Quest 2004 3,5 SL (VQ35DE)

Using nisprog I am able to connct with guess key funtions.

Findings:
- connection needs kspeed set to 9600 (most stable)
- need rxe set to 20-80
- p3 set to level "2"
- other setting on default.

NOTE: I had my engine replaced by previous owner. ECU was definietly altered - no VIN available in ECU (ECU could have been replaced as well - I have no data here) So, CK001 might be Murano ROM alternatively.
NOTE 2: my wirings are in OK-ish condition, so connection problems may be my specific issue.

Now kindly please help.
When I edit AFR map (my primary reason to use ROMRider) or anything else I can't make my car to run.
What I do:
1. edit org rom & save as new file. (editor v1.0.0, nisprog v1.05)
2. flash flblock 6 (only this single block)
- using kernel npk_SH7055_35.bin
3. stop,quit, etc...
4. start car.
5. Enginge goes into some limp mode (SLIP + TC lamps "ON" and accelerator is able to push revs to 1500 rpm max).
Whatever I change in my ROM and flash, the outcome is the same.

I approached flashing block 6 & 15 as well, but it bricked ECU - process stopped at 20-30% on block 15. I tried few times when kernel was in RAM but no luck, battery dided quite fast. I recoverd ECU by now.

After flashing back block 6 from original ROM, everything is back to normal.

What am I missing to have block 6 flashed without issues ??
I guess something with checksum, but checsum looks to be in block 6 as well, so I am bit concerned.

Are you sure your container is original? I'm seeing a bit of a strange target fuel. I can offer an alternative to Maximа 04 AT with the same definitions. Usually I rewrite all blocks.

Try un-commenting the unconfirmed alt2 checksum in that XML

No, his checksum for SH705513N is correct. I think the problem is in the cable.

A flverif after flashing would rule out the cable.

I personally flverif after flashing every time. I've never had one fail in over 350 Nissan flashes but I still do it out of habit haha.

Hi,

Thanks for all replies. Good points and help.
It was quite some time, before my post was published here - dunno why...
During that time I figured it out.

I was flashing block 6, as I modifed maps in block 6, BUT one map was exceeding bock 6 endding in block 7.
After flashing block 6 + 7 all is working fine.

i have still a lot of connection issues with my car - which are quite random. Still not sure about correct settings.

I found more maps in my rom, and updated XML. it is quite easy to find what is what when coparing other roms from this site with coresponding XML files.

SO, PROBLEM SOLVED with flashing for now.

I am now looking for stock Quest ROM, as I have doubts about my values compared to all maxima's maps found on this page.
But Quest is 2000kg beast (when empty), so I presume Maxima settings might not be something to use as plug and play.
If anyone here has access to a 2004 - 2007 Quest ECU, I would appreciate a dump file.

I will post any finding on my quest, when I get it to work smoothly with modifed maps .

SH705828N
11ZVK7NN8
1JR6C
Nissan Quest Ecm 23710-1JR6D
This is the original file from Nissan Qest 3.5 cvt. I don't remember the year of the car

Hi,

Thank you Supra030.
I see yor rom is from Quest 2012, with VTC transmission. Quite different in HEX editor to figure out all maps.

I managed to "guess" dig out VVT map and 3 Ignition maps (whre your rom has more than 3 maps inside), but it is way different than all 2004-2007 Maximas, Muranos, and my stock rom.
I am affraid the code that calculates engine parameters may be different as well in your ROM, so applying any timings from it, is risky IMO.

GENERAL UPDATE to my experiment with my ECU tuning:

So far I found my map is almost identical to Maxima 2004 (map 7Y210) on ignition & VVT parameters.
but is far from 7Y210 in fuel compensation for example in high rpm, and mid load.

My findings so far:
- changeing ignition timing has very little to no impact (monitored wih OBD fast scaner). Like the maps were not used ?? my quests runs WOT allways in range of 17-19 deg. (while my 2005 350z WOT is 27+ deg / same engine, different manifold).
- advancing VVT by 5 or more degrees, gives noticable changes in mild load between 1200 - 2400 rpm.
- advancing VVT more than 10 deg. (from 10ish to 20ish range), is causing engine to heat more
- playing with advancing VVT together with advancing ignition (by 2 to 5 deg) in general increases fuel usage by 10+ percent.

I wonder if my knock sesnor is not broken, and car drives notoriuos on HIGH DET map. (especially in mid/full load)
PLease share if you know how to test it without taking it out from engine bay.

Cheers !