New software 3.048 available!

V3 BETA TESTS
1

New version of V3 is available!

Link to the software:
https://www.ecumaster.com/files/EMU_BLACK_V3/EMUBlackV3Setup_3_048b.exe

EDL firmware ver 18 required for V3 firmware in version 3.044 and higer
[https://www.ecumaster.com/files/EMU_BLACK_V3/edl_firmware_1_18.zip ]

Change log file:

CHANGE LOG

V2 Importer

  • Engine start and fuelling import added.

Idle Control

  • Ignition target table is now 3D (RPM target vs CLT).
  • Fixed issue where ignition min/max torque clamp did not work.
  • Idle ignition target log channels now correctly display negative angles.

CAM Inputs

  • CAM1: When the CAM 1 decoder is set to ā€œDo not useā€, the input is active only during scope capture.
  • CAM2: When the CAM 2 decoder is set to ā€œDo not useā€, the input is active only during scope capture.

Knock Control

  • TPS can now be used as the Y-axis of the engine noise table.
  • Fixed bug related to knock detection status.

Start

  • Ignition angle lock feature added.

Fuel Control

  • MAP can be used as the lambda target when Alpha-N strategy is selected (ā€œUse MAP for Lambda targetā€).

Wideband Oxygen (WBO)

  • Increased the sensor temperature range where lambda readings are considered valid.
  • WBO no longer reinitializes when changing fuel settings (e.g., injector phase, squirt twice per cycle, etc.).

Nitrous

  • CAN analog input can now be used for the nitrous pressure sensor.

CAN Communication

  • Subaru GH CAN stream modified.
  • MQB CAN stream improved.

Gear Shift

  • Added blip support using throttle kicker.

Log Book

  • Oil pressure error is now registered only when RPM > 600 and engine runtime > 5 seconds.

Help

  • DSG documentation work in progress.
  • Various bug fixes and minor changes.

Other

  • Channel ā€œECU Reset Causeā€ added.
  • Watchdog functionality enabled.
  • Injection angle table now supports ā€œLoadā€ on the Y-axis.
  • Treeview items for available strategies are properly filtered after client startup.
  • Coil dwell wizard for VW coil ā€œ06E 905 115 Eā€ fixed.
  • Trigger error field added to the status line.
  • Graph log channel selector: if the channel is not found and Enter is pressed, the channel list displays instead of showing a warning message.
2 Likes
3

Little change. Big impact!

1 Like
4

I replaced the firmware with a new one and tested it.

Itā€™s a little hard to tell because the TPS threshold is set to 20%, but in the part where the knock count changes from 1 to 2 (4:50~4:51), I think the knock action status is ā€˜condition not metā€™, but the count is increasing.

Where does this come from?

Also, the count up when starting the engine has not improved. (But this is not a critical issue.)

QNC10_Passo_K3VET.emub3 (67.6 KB)
20250430_1108.emublog3 (2.5 MB)

5

The count is independent on the actions settings. It registers all ā€œknockā€ situations if the engine is running (emu state > cranking).
So maybe it is wise to use action setting for the knock count update. I need to think about it.

6

What is the ignition lock on startup used for? Strategy?

7

The explanation helped me understand the meaning of the parameters.

Personally I would like something to let me know when the knock has exceeded the threshold while the action is enabled.

However, that algorithm assumes that all the signals picked up by the knock sensor are (real) knocking.
In the case of V3ā€™s knock retard, currently IgnitionRetard occurs according to the knock level regardless of the influence of engine noise (actually, it does not retard unless it exceeds a threshold).

Since we have EngineNoiseMap, shouldnā€™t we be able to determine whether itā€™s noise or knocking there?
If the engine noise map is set to a relatively high level, I donā€™t think it can be avoided with the minimum retard.
Shouldnā€™t it be possible to generate IgnitionRetard according to the knock level from a value that exceeds the engine noise map?

8

I changed the direction of our strategy.

If want to enable knock action with the current strategy, might be able to get a retard according to the sensing amount even if you set MaxIgnitionRetard to a relatively high value by setting the knock signal level as small as possible using Integrator and Gain and setting EngineNoiseMap to a value as close to zero as possible.

This strategy seems like it will work in my current environment, so Iā€™ll give it a try.

However, this does not have a lot of freedom in setting, and if you cannot get the desired result (different engine, knock sensor, etc.), I think it will be very difficult to adjust.

(This is an automatic translation by Google. There may be some strange expressions.)

1 Like
9

@Jadzwin_ECUMASTER would it be possible to see the injector dc for each injector, so you can see whats the actual dc incl. +/- inj. trim?

10

I thought the ignition retard strategy after knock sensing should be like 2 below, but currently it is 1 and it seems that the engine noise map is only the threshold for whether to actually retard or not.
Is there any reason for this?

  1. KnockIgnCorrection = Proportional to Knocksensor signal level
  2. KnockIgnCorrection = Proportional to (Knocksensor signal level - EngineNoiseLV)

With strategy 1, it seems that it is not possible to achieve a small retard in the event of minor knocking in a situation where there is a certain amount of engine noise.

11

Hi Gents, when decelerating, where is the option to switch off the injectors or cut the fuel? Under deceleration, AFR goes to 10 AFR, not switching off.

12

Just wanting to point out that the ignition timing for predefined triggers ā€œBMW e36 M52b20 M54ā€ is incorrect. Currently Stating firing order is 1-5-3-4-2-6 when it is suppose to be 1-5-3-6-2-4

13

Overrun has what you are looking for

14

Thanks, bud. I just tested this; it activated the overrun strategy.

Sometimes when i come to a stop the car dies .Starts right up and does it again only when i stop. When cold it doesnt do this. AFR is 13.7 on idle .I am stumped Thanks, bud. I just tested this; it activated the overrun strategy.

Sometimes when I come to a stop, the car dies. It starts right up and does it again only when I stop. When cold, it doesnā€™t do this. AFR is 13.7 on idle. I am stumped.

15

log and project difficult say whatā€™s going on without it

16

ā€œI noticed in the logs that the vehicle speed is not displaying correctly. However, when I select the speed of any individual wheel, it shows the correct value.ā€

image
image1109Ɨ583 32.3 KB

image
image1131Ɨ643 37 KB

17

Not ascreenshot log and project

18

Today was Track Day so I did some testing.

This course is at a high altitude (91 Baro).
I should also mention in advance that my vehicle is currently having problems with the water temperature and intake temperature.

As I pointed out before, when looking at the log, there is indeed a difference on the time axis between the peak position on the graph and the peak display displayed in the Log window.

Furthermore, even though high values ā€‹ā€‹are entered for KnockVoltagePeak 1 and 2, knock is only detected in Cyl2.

20250502_2020.emublog3 (1.8 MB)

19

Additionally, there is something strange about the MAP sensor display around 24:22 in the log. Is this just a hardware problem?

20

Log is very big how to you guys upload