Timing issues

Nistune topics related specifically to the 6303 cpu

Moderator: Matt

Matt
Site Admin
Posts: 8242
Joined: Sun Jan 29, 2006 1:45 am
Location: Adelaide, Australia
Contact:

Re: Timing issues

Post by Matt » Wed Oct 22, 2014 5:45 pm

I may not be able to fix the Consult reporting when in/out of gear. This is something Nissan consult reports to us. I provide the ability to report the consult values, but it appears they are not correct when at idle (ie 5 deg BDTC out) since you have confirmed the table values are now correct

Idle timing maps are referenced when in gear/neutral

Injector size - I used the same values as Z32. If you can confirm the M30 is 180CC (this seems very low, I would expect 200CC at a minimum same as RB30E) then I can update it

my1path
Posts: 50
Joined: Fri Apr 06, 2012 8:06 am
Location: Southern CA, USA

Re: Timing issues

Post by my1path » Thu Oct 23, 2014 12:25 am

Ok, I think I can live with a minor reporting discrepancy since I know that it is really doing what the map says and not what Consult reports.
Matt wrote:I may not be able to fix the Consult reporting when in/out of gear. This is something Nissan consult reports to us. I provide the ability to report the consult values, but it appears they are not correct when at idle (ie 5 deg BDTC out) since you have confirmed the table values are now correct

Idle timing maps are referenced when in gear/neutral

Injector size - I used the same values as Z32. If you can confirm the M30 is 180CC (this seems very low, I would expect 200CC at a minimum same as RB30E) then I can update it
The M30 was an NA Single Overhead Cam VG30E like the NA Z31, 85–94 Maxima and 90-95 & 96-00 Pathfinder(Presently I am running the 96-00 Pathfinder Injectors). The Turbo motors came with 260cc But the NA motors came with 180cc.

If I can find my test results from my injector cleaning a few years ago I will share it. In the mean time I did find this:
Z31_VG30_128_E_86 wrote:#ENGINE SPECIFIC PARAMETERS
CYLINDER=6
INJECTORCC=185
ENGINECC=3000
EMULATOR_OFFSET=&HC000
J30_VG30_256_E wrote:#ENGINE SPECIFIC PARAMETERS
CYLINDER=6
ENGINECC=3000
INJECTORCC=185

Matt
Site Admin
Posts: 8242
Joined: Sun Jan 29, 2006 1:45 am
Location: Adelaide, Australia
Contact:

Re: Timing issues

Post by Matt » Thu Oct 23, 2014 9:25 pm

Thanks. I've updated it. Only used for the resize option

my1path
Posts: 50
Joined: Fri Apr 06, 2012 8:06 am
Location: Southern CA, USA

Re: Timing issues

Post by my1path » Wed May 06, 2015 4:19 am

I found this on an older thread. I'm going to add it to the file and see If I can get any closer to my actual Idle numbers. I will report back with all my offsets so they can be included with future updates.
viewtopic.php?f=8&t=588
IDLE_TIMING_MAP_OFFSET=
EDIT: Nope, 0, 5, 10, -5, no effect on reported Idle timing.
The other settings work fine;

CONSULT_TIMING_OFFSET=45
TIMING_MAP_OFFSET=5

Matt
Site Admin
Posts: 8242
Joined: Sun Jan 29, 2006 1:45 am
Location: Adelaide, Australia
Contact:

Re: Timing issues

Post by Matt » Thu May 07, 2015 6:20 pm

Did you view Idle timing map in 'filtered' rather than 'raw' mode?

my1path
Posts: 50
Joined: Fri Apr 06, 2012 8:06 am
Location: Southern CA, USA

Re: Timing issues

Post by my1path » Thu May 07, 2015 11:44 pm

This is in reference to Reported timing in the consult window view vs actual timing.
But I guess you're right, that modifier line would affect the map view and not the consult view.
It says [RAW] on the top of the Idle map window(I don't see a drop down for filtered views) and the reported timing Still becomes correct when I get into the regular timing map.


EDIT: found it by right clicking. I'm gonna try some things I'll get back to you.

Howlermonkey
Posts: 6
Joined: Sun Mar 22, 2009 4:11 am
Location: west palm beach
Contact:

Re: Timing issues

Post by Howlermonkey » Mon Oct 24, 2016 9:33 am

I know this an old thread but want to confirm the 180cc injectors.

It's also possible that the "temp enrich" has to do with a fuel temp sensor mounted in the fpr and that over a certain fuel temp, it enriches to combat vapor lock and is mostly used during a start after a hot soak.

300zx single cam vg30e had the same thing.

I may be mistaken about thier term "temp enrich" usage but i do know nissan did use a fuel temp sensor......just not sure if this is where it's used.

Matt
Site Admin
Posts: 8242
Joined: Sun Jan 29, 2006 1:45 am
Location: Adelaide, Australia
Contact:

Re: Timing issues

Post by Matt » Mon Oct 24, 2016 10:29 am

Thanks for confirming the injectors

There is the possibility some of the temperature tables use the fuel temp as input (rather than coolant temp) but would need to check the code to verify the indexing

Matt
Site Admin
Posts: 8242
Joined: Sun Jan 29, 2006 1:45 am
Location: Adelaide, Australia
Contact:

Re: Timing issues

Post by Matt » Thu Sep 27, 2018 12:37 pm

Just an update
CLOSED_LOOP_TABLE_TPS_MAX is actually the ADD_FUEL table location (used to access last column in fuel map on full throttle, M30 ECU code slightly different from other models)

Updated for next release

my1path
Posts: 50
Joined: Fri Apr 06, 2012 8:06 am
Location: Southern CA, USA

Re: Timing issues

Post by my1path » Fri Sep 06, 2019 5:26 am

I adjusted my timing gears yesterday and had to reset the ignition timing. Reported timing via nistune in both idle and in the main map match my timing light.

But my Idle/Decel and Idle/Decel Neutral maps are 5 degrees high in filtered view. (says 15, nistune reports 10)

I honestly haven't touched timing in years. The similar issues were resolved in this thread and I left it alone until now. What's changed? The address files? Nistune updates? Is there a new line I should insert like last time?

Matt
Site Admin
Posts: 8242
Joined: Sun Jan 29, 2006 1:45 am
Location: Adelaide, Australia
Contact:

Re: Timing issues

Post by Matt » Fri Sep 06, 2019 10:22 pm

Nothing has changed since 2018 with the above change

If you see a difference, try adding to the address file
IDLE_TIMING_MAP_OFFSET=5

That will add '5' to filtered view. Let me know if that fixes it, and I can update the address file

my1path
Posts: 50
Joined: Fri Apr 06, 2012 8:06 am
Location: Southern CA, USA

Re: Timing issues

Post by my1path » Mon Sep 09, 2019 5:42 am

Matt wrote:
Fri Sep 06, 2019 10:22 pm
Nothing has changed since 2018 with the above change

If you see a difference, try adding to the address file
IDLE_TIMING_MAP_OFFSET=5

That will add '5' to filtered view. Let me know if that fixes it, and I can update the address file
Thanks Matt, Until this week I literally haven't touched timing since 2016 ish I am going to re-check (and make sure everything is in filtered view) and get back you you.

my1path
Posts: 50
Joined: Fri Apr 06, 2012 8:06 am
Location: Southern CA, USA

Re: Timing issues

Post by my1path » Thu Sep 12, 2019 12:02 pm

my1path wrote:
Mon Sep 09, 2019 5:42 am
Matt wrote:
Fri Sep 06, 2019 10:22 pm
Nothing has changed since 2018 with the above change

If you see a difference, try adding to the address file
IDLE_TIMING_MAP_OFFSET=5

That will add '5' to filtered view. Let me know if that fixes it, and I can update the address file
Thanks Matt, Until this week I literally haven't touched timing since 2016 ish I am going to re-check (and make sure everything is in filtered view) and get back you you.
That did it. Here are my current offsets from M30_VG30_256_E.adr

CONSULT_TIMING_OFFSET=45
TIMING_MAP_OFFSET=0
IDLE_TIMING_MAP_OFFSET=5

Consult timing matches light at idle TPS closed and running TPS open.
Timing Map, Idle/Decel & Idle/Decel Neutral match consult.

Thankyou

my1path
Posts: 50
Joined: Fri Apr 06, 2012 8:06 am
Location: Southern CA, USA

Re: Timing issues

Post by my1path » Sun Sep 15, 2019 9:59 am

Offset corrected above

Matt
Site Admin
Posts: 8242
Joined: Sun Jan 29, 2006 1:45 am
Location: Adelaide, Australia
Contact:

Re: Timing issues

Post by Matt » Tue Sep 17, 2019 9:39 am

Awesome, I'll update the address file in the installer

Post Reply