[techforge]

What's the best way to tell if I'm maximizing my V3 settings or going too far with different fuel grades? Should I increase the UT until it starts pulling timing and then back off?

[Sniz]

..

[techforge]

Oh I thought it would log whether timing was being advanced or retarded.

[Sniz]

[scalbert]

Originally Posted by techforge

Oh I thought it would log whether timing was being advanced or retarded.

It does show the amount of retard being induced but not overall timing. The amount of retard induced is static and not adaptive in the PROcede, it is based on boost and IAT values.

To fully determine when the octane versus boost threshold is reached, you need to know true overall timing. And I am still skeptical if the DME shows this including any knock retard.

[RedGT3]

What about OBII scanners that say you can see live boost, timing and other info?

[chiefsotos]

Originally Posted by techforge

What's the best way to tell if I'm maximizing my V3 settings or going too far with different fuel grades? Should I increase the UT until it starts pulling timing and then back off?

Maybe it is sounds silly but what do you mean by saying "starts pulling timing"? Are you refer to the ignition or fuel correction?

[scalbert]

Originally Posted by fll335

What about OBII scanners that say you can see live boost, timing and other info?

There is some debate on whether or not the OBDII scanners show actual timing or basae timing. In other words, does it show the timing being run with knock correction or just the base timing.

This should be determined soon and will be moot as the AutoEnginuity software will read the knock activity as well as knock correction values. This is ultimately what we want to see.

[scalbert]

Originally Posted by chiefsotos

Maybe it is sounds silly but what do you mean by saying "starts pulling timing"? Are you refer to the ignition or fuel correction?

That is correct, when does the DME start trying to reduce power through ignition retardation. You want to run just at or below this threshold.

[techforge]

Originally Posted by chiefsotos

Maybe it is sounds silly but what do you mean by saying "starts pulling timing"? Are you refer to the ignition or fuel correction?

Ignition timing. I was under the assumption that a good way to max the tune would be to run it up until it starts to knock and hence pull timing - then back off from that. But I guess there's no clear way to monitor that with what I have at my disposal.

[BavarianBullet]

Originally Posted by scalbert

There is some debate on whether or not the OBDII scanners show actual timing or basae timing. In other words, does it show the timing being run with knock correction or just the base timing.

This should be determined soon and will be moot as the AutoEnginuity software will read the knock activity as well as knock correction values. This is ultimately what we want to see.

That autoenginuity tool an interesting tidbit. Have you tried it/recommend it? http://www.autoenginuity.com/order.html


Does that mean the OBD tool from AE isn't available yet or that you've just not seen enough data from various sources to prove whether OBD in general displays the (net) total advance vs static ignition timing map?

[scalbert]

Originally Posted by BavarianBullet

That autoenginuity tool an interesting tidbit. Have you tried it/recommend it? http://www.autoenginuity.com/order.html


Does that mean the OBD tool from AE isn't available yet or that you've just not seen enough data from various sources to prove whether OBD in general displays the (net) total advance vs static ignition timing map?

The generic OBDII from AE works fine. But it doesn't provided the Extended data as per the below link. The last contact I had with them stated it should be ready this winter. I was going to give them an other couple of weeks and drop them a note.

http://www.autoenginuity.com/BMW-All-Systems-List.html

[techforge]

I don't see the N54 in their list. Am I missing something

[scalbert]

Originally Posted by techforge

I don't see the N54 in their list. Am I missing something

Correct, they haven't included it yet. It was supposed to be out back in May/June. It was then later delayed to September and now January. But they supposedly have read and reset the non-OBDII codes (OEM specific) back in the summer. They were trying to finalize the logging ability.

[techforge]

Originally Posted by scalbert

But they supposedly have read and reset the non-OBDII codes (OEM specific) back in the summer. They were trying to finalize the logging ability.

Would that cover the manipulation code or no?

[scalbert]

Originally Posted by techforge

Would that cover the manipulation code or no?

It should.