Mag's OSE 12P Thread

[mag]

Antus, that was my understanding if the baro parameter flag option was unticked (clear). Set bit should "update during run" or have I misunderstood what this flag means.

[VL400]

We are going to need more help mag, no log and no cal and just saying you have a problem makes it very difficult to diagnose.

I have bench tested it and it all works as it should, baro gets set at key on/engine off and stays there with the flag clear. With the flag set it gets adjusted everytime you go WOT and the MAP is > current baro, or the TPS is > 37.5% and RPM is between 1200 and 3600RPM it gets offset according to "Baro params - Baro Adjustment offset to MAP A/D reading vs RPM & TPS".

[mag]

Thanks VL400, now I know what criteria is used to update the baro while running I can analyse my log data.

[VL400]

It was actually discussed on page 6 of this thread .. https://pcmhacking.net/forums/viewtopi ... 8&start=50

Also note in there that jayme mentioned "Baro params - Maximum MAP offset for baro adjustment" . Might pay to check that item also.

[mag]

VL400, hope you did not bench test simply because of my question, just wanted update criteria. Anyway can confirm works in real world just as you described. Easy to see in the logs once I knew what I was looking for.

[mag]

Keeping all my 12P problems together, here is a flashtool one. Tried using flashtoov v1.27 to edit flexitable. All ok until part way through "modify adx" when error message appeared "unknown error when writing xdf". Any ideas? Have used flashtool v1.25 without any issues that I can remember.

[antus]

can you upload here a zipped copy of the xdf thats not working?

[VL400]

If its a TP5 XDF it wont work as I have not added support for that yet.

[mag]

Thanks to you both for the quick response. Simple answer, it is a TP5 adx. I await further develoment from the master.

[mag]

Posted a question on the forum the other day but seems to have gone astray, so here it is again.

More questions regarding the poor mid range rpm performance of my v6. Appears from a few loggs I have that the knock sensor kicks-in (4 dregrees reatard) on odd occassions when cruising but more importantly also just when the auto changes up a gear (upto 12 degrees retard). Is this normal. Can knock sensors become over-sensitive when faulty, will an overly mechanically noisy engine give false triggers.

Specific detail regarding the performance hole follows; when I hit WOT at approx 80kph the auto downshifts but the engine rpm only jumps to 3000rpm. It sits at 30000rpm until I back-off the throttle & then the rpm begins to increase. Much like severe lean/rich fueling. If I simply start off with WOT from standing start the auto shift through the gears ok and the engine runs out to 5000 rpm. Have not yet go logs associated with the WOT/3000rpm condition so cannot comment yet if knock retarding is occuring when problem arises but should soon now that I can replicate the problem conditions. Anyway thought someone might have experienced similar problem that related to knock sensor failure.

What engine parameters are factored into the the knock retard equation or Is simply progressive incremental control driven by the duration of the output flag from the knock sensing circuitry.