Wanted the check the following is correct, I noticed when I lift of the PPS 100% to 0% the DBW is being taken from the Idle, where I thought it would be taken from the DBW table until the conditions for idle are met.
I realise that this is possible because in the Overrun settings I do not have the override dbw section selected.
However in idle parameters Idle is only on if Map over 25kpa.
I have added in some Overun DBW %’s now, which has also made me notice there is no overrun fuel, just complete fuel cut, what % fuel cut is normal?
We are currently working on standardizing the build release rules for all our products.
Starting from the next build, the firmware will use a main version number, e.g., 3.060, followed by a subversion ranging from 00 (first release) to 99. This subversion will increase when a firmware bug is fixed and there is no need to modify the XML file.
For official releases, if a bug is discovered in the future that affects the official build, the firmware can then be updated accordingly.
We aim to maintain backward compatibility as much as possible. However, in some cases—such as the short-term trim changes in V2—modifications may require reconfiguring the strategy.
So all the functionality (computation, logic, triggers…) resides in the firmware (e.g. emuBlack_3_054.bin) and the HTML file (e.g. version3_054.xml) contains the UI dialog definitions used by the client application (EMU_BLACK_V3.exe). Correct?
So the release notes for each firmware upgrade will detail all the fixes and allow us to decide to upgrade immediately or let it “age” a bit. Sounds great.
For Flat Shift Strategy -
Could you add FN options as Activation Input? In V2, there are options for virtual/param out.
I’m running 8HP with Turbolamik and I need to set certain boolean values before flat shift activates.
Yes. The each firmware have separate xml file that defines all available parameters.
The latest windows client work with ALL previous firmware (it just load appropriate xml file when connect to the device). So based on release notes you can decide if upgrade firwmare or not.
Understood. If it is a case of modifier, my TQ Reduction Cut % at that time of log was -
TQ Reduction = 100%
Down Shift Blip - Post Shift Cut - Cut 30%
In this case if Post Shift Cut is a modifier of TQ Reduction Cut Table, shouldn’t downshift blip cut be 30%?
Also- please let me know if you receive recommendation of being able to turn off brake pedal required when CC strategy is on.
So if you request 30% torque reduction, then the ECU reads from Torque reduction cut table valuue for 30% (for example belowe it is 12-13% of cut) and also apply the igniton retard from Torque reuction ign. correction (in this case - 20)
I’m using the dyno module in V3.059 RC2 and getting HP values that appear low for the torque numbers.
I’m assuming torque is in Nm and power is horsepower. If both are plotted against the same left side axis, then the torque and HP should cross at 7127 RPM, correct?
hi Jadzwin so i have a issue with the over run functions .
as you can see the setting in the pic below the settings used . if you set the over runn spark cut to any value above 0 and it will randomly start to to do spark cuts almost like rotational ideal or even when you driving . at this time when you look at the overrun log window its not active . i have now tested this kind of settings on 2 cars both v3 and both cars have the same issue .
on the one car i end up striping the engine to rebuild the engine because of this misfire looking issues .
i need you to look at my settings or check the a bug in the firmware with the spark cut function
Hello Guys ….. Something I observed today and don’t know if this is the intention or an issue. Under → Fueling → Corrections → IAT user correction, when I add or subtract a value it not change my fuel pulse width. What I did notice is that it changes my Lambda Target, I don’t expect that is the intended behavior. So …. if my target lambda is 1.0 and I head over to “IAT user correction” → and change 140(f) to -6, I see that my target lambda change from 1.0 to 1.06…. I assumed that the intent was not to change the lambda target by 6% but to change the PW by 6%. Is this something that needs to be looked at ?
But for IAT the fuel model automaticaly adjust PW. This correction is rather to make the car richer when there is unexpected high IAT. So changing lambda target is much better way to do it. If you change PW and your short term fuel trim is active it will always change PW towards your target lambda.
The spark cut for overrun is only active when the overrun is active.
Do you have any log file ? It could be easy to track as the spark cut source log channel should indicate overrun as well as spark cut percent should be different than 0.
I will also simulate it to check if there is no bug connected to this.
I am quite new at the ecumaster black so it’s maybe a noob question.
Is there any function to make a Boost - Time Table?
I found the timer option but there i can only add 100% to the Target Boost an not a concrete Boost Target.
For example the Picture show a strategie from a NLR AMS 2000 Boost Controller
