I would start to upload a m62 map from another user with about the same specs.
Since this was previously an ITB VX, i asume this is a fresh purchase of obdtuner.
Usually Peter will ask a gazillion questions on the current spec, and deliver a basemap that should be pretty close.
@Jimmy; such a basemap is set pretty conservative on timing and fuel (a bit rich)
You first start with a fueling session to get that closer to where it should be.
As that is measured via the normal lambda, aka closed loop, you are limited to this as the stock lambda is a narrow band one.
Roughly it will use the lambda info to around 3500 rpm, where the narrowband behavior ends.
For 3500 to 7000 it uses the open loop info (aka whatever is hard keyed in the ecu)
Again, Peter will have created those number relatively safe, yet slightly rich.
If you want real measured info you will have to put in a wideband sensor and run some WOT sessions.
The extra cost of the wideband is somehow eleviated by not burning unneeded fuel in the higher range.
After your fueling session, you will run a timing session.
The timing again is set to a safe value by Peter. The automated timing ajustment based on the run will mostly be around more safer where needed, and not setting the timing sharper.
That part is unfortunately a lot of manual labor to get right.
During the timing session, the software will also log the knock on your engine.
obdtuner will not act on anything under 0.5 degree knock.
But again, lot's of manual labor doing runs and adjusting the timing in the culprit areas to get rid of knock.
With your highly customized engine, there may be a risk of false knock, that may require taken care of.
You can upload the logs you create so we can have a look where you are and what could be done.
Then you can start looking at finetuning and squeezing out those final numbers by more aggressive timing.
With your build engine, and a 2.9 pully, you should be able to pass 300.
Rule of thumb is to get where you want to be with the biggest pully possible.
Also keep in mind that when using obdtuner standard edition, Peter will have left the build in security of retardation in place on high intake temp, so you need to monitor your intake temp on track.
I assume you have converted from map to tmap on your build.
The default security retardation:
60C - 0,0 degree retard
65C - 0,5 degree retard
70C - 1,0 degree retard
75C - 1,5 degree retard
80C - 2,0 degree retard
Once your map is complete, you can export it, and send it to Peter to have this safety feature altered to start from 80 instead of at 65.
In obdtuner pro this option is in the software and you can do it yourself.
Edited by smiley, 13 July 2021 - 04:50 PM.