V2 shows FF temperature, V3 does not? Is that just not added to logs yet?
V3
V2
V2 shows FF temperature, V3 does not? Is that just not added to logs yet?
V3
V2
It is not free air calibration. It is calibration of internal WBO circuit (the offset is measured) and the sensor must be disconnected fro this procedure. I already changed description for the message that appears before calibration.
You need select Flex Fuel as a temperature sensor input.
And fuel temperature is present in Temperature group log.
Oh well… that was my bad understanding then. Sorry
Hi guys,
thanks for adding me to this group. I was able to load the new software since yesterday. I think a lot of it is very good, but there are several points that I would have liked that were missing.
In my opinion, we should ask ourselves whether the goal is to create the best possible device from the Emu Black, or whether the goal is to take a middle path that you can be satisfied with. I suspect that at the end of the day, the product that offers the best performance on the market will also sell the most in this price segment.
Anyone who has ever worked with 4D maps and freely parameterizable axes will no longer want to do without them in the future. As a tuner, this makes some things easier and tries to advise the customer so that they can choose the better product in their opinion.
I know the Emu Pro has features like Long therm Ego Correction. However, other products have had this for a long time. why aren’t such functions implemented, at least not yet? This works perfectly and is the best there is, in my opinion.
What is the goal of this software?
I will be happy to work with you on it or help, but it is not clear to me what the main goal is and what is not desired.
Please don’t get me wrong, I’m just trying to work as efficiently as possible and that’s why I’m asking this basic question right at the beginning
There is hardware limitation with the available memory. The 4D tables and long term trim are very very memory consuming. It is the only reason. We still working on short term correction strategies in the company. Our goal is to make such good short term fuel trim strategy that the long term will not be required. For 4D tables the only option is EMU PRO.
Thank you for the explanation. That makes absolutely sense to me.
I think, the input and output overview button in the old version was a helpful tool.
Also, please don’ t forget to update the help buttons. We users can understand much easier, if we know exactly, what we are changing
There is completly new help system on the right side of the application. It is already done for the whole Sensor and inputs subtree (and partially for others). It will be finished for official launch.
According input / outputs assignment windows it will be available again soon.
Boost DC in log does not show true output DC. Ie if min solenoid dc is set to 50 and dc from table + corrections is ie 30 log shows 30 but actually dc from aux is 50.
Dunno if this is a feature that we want.
Max gear ratio value limited to 14.6484?
2 questions:
As I need to use 4250cc engine size and 8-cyl setup for V2 odd fire engine, that makes estimated airflow much bigger than it actually is. How estimated airflow affects fuel calculations? If its per cylinder then it should not matter, right?
Short term trim is really really slow… It works ok at idle and stable engine loads but it´s not usable at all if load changes even a little rapidly. Should I see faster response?
Gear ratio is the VSS / RPM so it will be always very small number.
In V2 it was multiplied by constant so it is not compatible.
You can easily read this value from the log “Gear speed to RPM ratio” channel
If you change the num cylinders from 2 to 8 you need to increase the engine displacement as you did, and leave the injector size as for 2 cylinder engine.
It is a workaround for even fire engines. I will try to figure out better solution in the future.
As you said the estimated airflow will be 4 times larger. However it is not an issue as you can adjust the kP and kI scale of PID according to the airflow from the log.
So if you need better response under load (higher airflow) increase the kP, kI scale at higher airflow (read data from the log).
I’ve just realised that kP and kI scales table are now not consistent with the scale tables (100% is no change instead of 0%). For the next version I will change it and also increase the range to 1000%
Is it possible to add a second boost target gear correction table that can be blended between via ethanol content?
if i need to just switch between boost targets - it is not obvious how to do it: first need to assign rotary switch to 0/1 switch, after this fill calibration of this rotary switch
0=0
9 = max value from this switch volts from log (if it logged)
and after - set rotary switch taget blending
may be need to write some notes about this into help…
PLS, add to PWM outputs - ignition outputs.
No GearCut strategy at all? and not planing to realize?
may be return additional fuel into FlatShift - ?
please tell what it is equal to in v2
So set the boost blend table like below:
PWM for ingition outputs: It is not possible due technical limitations
In V2 the ratio was multiplied by 32. So if you want to convert it to v3 divide it by 32
Gear cut (it is called now Gear shifts) is under test right now and it will be available in next version in next week. The closed loop strategy is also implemented.
For flat shift it is not a problem to add fuel enrichment.
For what do you need such enrichment ?
in v2 it works, sad to lose alredy utilizing in car option.
For flat shift, fuel enrichment need to not melt pistons, when retard ign angle, and cut iginition and staying on boost.
but, i like to use Gear cut, for more precise tuning for different gears, and no cut rpm… (MT gearbox)