New software 3.051 available!

New version of V3 is available!

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

EDL firmware ver 21 required for V3 firmware in version 3.051 and higer
[https://www.ecumaster.com/files/EMU_BLACK_V3/edl_firmware_1_21.zip ]

Change log file: changeLogV3.pdf

CHANGE LOG:

CAN:

  • Lotus Elise S3: Added option to define a switch input for Sport mode.

IDLE:

  • Added Inactive State Airflow table for both PWM and stepper motor actuators.

OTHER

  • H-Bridge startup behavior unified with V2 version.
  • Communication speed between microcontrollers decreased to reduce CRC error occurrence.
  • Added EDL diagnostic channels.
  • Added Flex Fuel Status : “Connection error” is now indicated when no signal is received from the sensor.

TRIGGER WIZARD:

  • Added support for Mazda MX-5 NC.

IMPORTER

  • DBW (Drive-By-Wire) settings import added.
  • Imported calibrations are now properly transferred to the connected device.

HELP

  • Added a step-by-step setup guide for idle control
9 Likes

Hi,

Can we get in boost control

Tables to correct duty cycle table ??

Custom axis table please.

We have now 2x7 tables that actually kind of do the same…

Delete 7 of them and add duty correction…

Depending on gear I have a lot of cars that needs percentage wise different duty cycle table and closed boost control isn’t able to solve it.

Thanks !

Btw dead times from injectors are not correct
Bosch 900cc

2 Likes

It seems to me that the gear calculation from the engine speed and the vehicle speed works slow especially if the speed is not high.
I checked in the log from a month ago where the firmware was 3.048 and the calculation after a gear change takes about 0.5s
Yesterday after upgrading to firmware 3.051 I noticed that the gear display after a gear change works slower. I checked in the log and the calculations after a gear change take about 1-3s depending on how fast you drive

And in addition, yesterday the system time display in the log was working correctly but today something is wrong


20250618_0858_gear_calc_3.051.emublog3 (1.3 MB)
20250618_0910_gear_calc_3.048.emublog3 (920.8 KB)

delay is caused by clutch pedal when pressed gear wont change.

ok, thanks I will check it out

@Jadzwin_ECUMASTER .

Since there will be an app to connect to the EDL, is it wise to already connect the EDL-1’s TXD to the ecu RXD?

I had never seen this before, could it be the cause of the misfire that I have never found?
Cylinder 6 653 degree and other 328


scope 21 06 25.emubscp3 (643 Bytes)

Today i’m try to get back to 3.043,this log was correct
scope_2025213_1616.emubscp3 (649 Bytes)

I add two DC correction tables. One for gear and one with the custom X axis.
Thanks for injector data.

1 Like

That’s correct. We have recently updated the EDL-1 manual to reflect that.

1 Like

Could you post your base map ?
I would like to run it on simulator.

Yes. Now you can see some statuses from EDL. Also in the future you will be able to set some switches and rotary switches from Android / IOs application

1 Like

Hi,

can we get clutch forces open loop idle ??

during clutch press idle up it go into adaption to much and when release idle drops to far below target. if i tune the table better then the slow idle down doesnt work as i use upper rows of idle table to get more air so rpm doesnt drop below target

It seems to VE #2 table does not import the correct range and rise up to 9500 rpm

I did the test 3.051 and 3.043
the engine works better with 3.043, I have just rpm at idle, but the problem I think is the map reading… I tried with mercury test 50/100/150/200 kpa, but when the engine is running it does not have the right reading

You ahve probably set somethibg in configuration that makes the problem with 3.051.
Could you post your both maps and log files from idle for both versions ?

I will take a look at this.

No my DC isn’t calibrated on purpose on that idle rpm.

So when clutch is pushed idle up is 1800rpm
And PID comes active. Turning idle from 2200 to 1800 like request.

But denk I release clutch. Request is 1000.

But PID is still -10 kind off and then idle drops to 780 and slowly climes up to 1000 where PID is 1 or 2

Hi, there is a problem with overrun,

it comes active or stays active when not wanted
20250626_0958 overrun.emublog3 (2.6 MB)

frimware 50 and 51

Set different values for Activate when PPS below and Inactive when PPS above. There must be hysteresis. Out there 0,5% or so. The same for RPM there must be hysteresis.