[Water Methanol Injection fully controlled via G4X ? Bypassing AEM controller]

Hi, I'm using Mini R53 plugin G4X and also using WMI kit from AEM.
I would like to get rid of the AEM controller and drive the pump directly via the ECU.

Could this be possible using a general puprose PWM auxiliary ? Is the ECU capable of providing enough current to the pump ?

[Ignition Timing Setpoint during Cranking]

16 hours ago, Adamw said:

At the moment probably the best workaround would be to turn off idle ign control and instead use a 4D or dual ign table that gets activated only during idle conditions and set this up with idle target error Vs ECT similar to how the old "idle ignition table" in G4+ worked.

I would like to see if in the future we can have an option to enable a table for idle ign target instead of just a fixed single value but I have yet to discuss this with the firmware guys and havent put much thought into it so im not sure if it is possible or difficult yet.  

Thanks Adam for your answer. Unfortunately 4D, 5D and dual ignition tables are already used.
 

Having a table instead of a single value would be great as I'm sure I'm not the only one struggling with Ethanol based fuels. Or maybe just a Low RPM lock out setting in the idle control function, quick and easy.
 

[Ignition Timing Setpoint during Cranking]

Hello,

I'd like some feedback on how to handle ignition timing during cranking, especially from people using Ethanol.

After searching the software and the guide, I understand that Ignition timing during cranking could come from 2 different sources : 
1. Idle Ignition control is OFF : Ignition Timing setpoint comes from the Main ignition table (+ corrections)
2. Idle Ignition control is ON : ignition timing setpoint during cranking will be equal to ignition idle target

I'm in the second case and it's a problem because my sweet spot for idle control is +5°CRK whereas the sweet spot for cranking the engine with the tank full of ethanol E85 during the winter is more like +25/30°CRK.
With 5°CRK the engine starts, but it's a bit chaotic to be honest, and crank enrichment is not the problem here, stock ECU would start the engine perfectly, in the same conditions, thanks to a dedicated spark map during cranking.

Any workaround ideas ?

Would it be possible to have a dedicated Spark map during cranking ? Or maybe a Low RPM lock out setting in the Idle function that would disengage idle control during cranking so we could use the main ignition map and keep Idle Ignition Control ON ?

Thanks
Charles

[Knock Ignition trims very low when using Normalised Knock]

Hi Adam, thank you very much for this explanation.
I think I was tricked by the unit : Ignition Retard Gain 1.0 degrees/knock. Thinking that 1 degree would be withdraw per knock event.

I will give it a new try with boosted gains in Normalised mode.

Thanks a lot Adam
 

[Knock Ignition trims very low when using Normalised Knock]

V42 Normal test.llgxV42 absurd test.llgxHello,
I've fully mapped my Mini R53 using traditional knock detection (ignition only). Everything works well and ignition trims are coherent when knock level is above knock threshold.

Then wanted to try Normalised knock and I'm facing a weird issue : when knock level is above knock threshold, knock ingition trims are moving but instead of seeing 1.0 deg/knock event of igntion retard as calibrated, I see only 0.1 knock I-trim.
I thought I had some gain to adjust but I found nothing.

Then I tried to make an "absurd" test by setting the knock threshold very low compared to normalised level, and instead of seeing very high and sudden knock retard, I only see the knock trims slowly ramping up.

To sum up : when I use Normalised knock, I see knock Ignition Trims being about 10 times less as they should be (0.1deg of retard instead of 1.0 deg of retard)

Am I missing something here ? All the gains look well calibrated, I don't understand...

PS : I see knock events counter incrementing as it should