New software 3.030 is available!

New software 3.030 is available!

Link to the software:
[https://www.ecumaster.com/files/EMU_BLACK_V3/EMUBlackV3Setup_3_030b.exe ]

EDL firmware 2.15 required for V3 firmware

EDL firmware
[https://www.ecumaster.com/files/EMU_BLACK_V3/edl_firmware_1_15.zip ]

If you experience communication issues with the device, please restart your computer. We have noticed that these problems are caused by the Windows USB driver. We are working on reproducing and resolving this issue.

Change log:

BOOST: EWG support added
BOOST: Delay of PWM signal change in the case the boost output disabled is true bug fixed

DBW: Deadband parameter added
DBW: DBW calibration correctly support throttles that moves only in one direction and motor is inverted

CAN: Mazda RX8 new abs models (Model 2 A and User defined) added.
CAN: Opel Corsa VXR stream fixed
CAN: User defined CAN bitfields fixed
CAN: Porsche 998.1 CAN added

HELP: Boost help added
HELP: Mazda RX8 CAN stream description added

UI: Analog inputs CAN are shown properly in Show assigned inputs window
UI: Assigned outputs window properly display Coils Ignition outputs assignment

SYSTEM: Priority queue issue fixed (cause random engine stall)
KNOCK: KS Window duration can be as low as 10 degrees

FLEXFUEL: max tps to read sensor parameter added

LOG: idleTarget range increased to the 6000
LOG: Load log EDL extension changed from bgg3 to bg3
LOG: Ethanol correction channel fixed

OTHER: Clutch and brake pedals added to the switches list

4 Likes

Thx for adding eWG…seems to work fine :slight_smile:
Question…can u make boost target tables as a function of PPS instead of TPS?
Would make much more sense in my opinion.

I would very appreciate if you can share EWG logs.
For next version I will add an option to select TPS/PPS as an axis for boost target

1 Like

Sure…i will do some more eWG/boost calibration this weekend. I will share some logs here.
Just did the position PID calibration and played around to understand the new settings today without safeing any logs.

Edit:
Here a log with proper tuningfile:
AudiTT_AJQ_rev51_boostbase.emub3 (61.7 KB)
20240706_1602_rev51_boost1bar.emublog3 (686.2 KB)

From my point of view eWG control is behaving well.
But some questions:
Could we get back boost PID correction channel? Would help with PID tuning.
What i also don’t understand is the channel “boost DC from table”. I think it is partially buggy. I see obvious deviations:


Without load it is correct:

Those two points make boost control tuning a bit confusing.

Okay…actually the named channels are not needed for tuning. The SW is really good. With just a little efford in tuning i got better results than i could ever reach in V2. Really great job guys.

Another question…how does the blend option for boost target work?
I have a CAN signal, which i used for switching between the two tables. But i can’t get it to work, since just blend option are now available and no simple switch option. Can u help me?

It os great to hear that you see the improvements.
We put a lot efforts to make the software / firmware better, and it is not our last word :slight_smile:

According switching boost tables, just use your switch to configure rotary switch. You will get 2 position rotary siwtch. Then in blend table enter 100 for ratary switch pos 1 and 0 for others.

1 Like

There is a typo in the Porsche vehicle CAN stream. Its 997.1 not 998.1 :+1:

Thanks. I’ve just fixed

1 Like

The boost DC from table should be Boost DC feedback table.
I will add Boost PID correction channel.

What I see your Max duty cycle in Boost parameters is 90%.
It will cause the EWG plate will not close fully as the DC is converted to Target and and 100% is fully closed.

Maybe Min/Max duty cycle parameters shouldn’t be used for EWG or in the case of EWG the name of those parameters should be changed to Min / Max EWG position.

I will check again but i think in the boost DC from table channel there is something strange.

Yes my max DC/max position is partially strange cause the position sensor of my eWG seems to have a small varying offset. To have a safe closed position i set the sensor closed position voltage a bit higher than the actual closed position. Then i set max eWG position (i think u should name the variable something like that in eWG case…in first place i thought it meant DC of the motor) to get a healthy motor DC in any target closed condition.
Need to investigate this issue in my system, but the impact is quite irrelevant with good PID.

But eWG seems to work fine in general :slight_smile:

Interested to hear why you added the DBW deadband feature because I’ll probably use it.

I have experienced problems with the pid control over and under shooting the target as the integral winds up every few seconds, I try to correct this with the friction factor which almost works but then it starts oscillating around target, this is happens around the 3-4% TPS range as the engine idles, wasn’t actually sure if my TPS tracks were worn.

the deadband is rather for small errors like 0.1%
please attach the log how the throttle works after dbw autotune

This is only a small error of 0.1% but integral will wind up then over correct it, I have already done the DBW calibration, I’ll send the log.

This is the throttle searching for target by 0.1%

This is 1.030 firmware which seems to have solved the issue with the deadband function.

I also discovered in those 2 logs above that I cant use the DBW autotune anymore because “The throttle does not return to limp home position” message appears at the end.

This is the map which had the DBW setup by autotune in an earlier firmware although I did change the friction factor.

Another log of the car driving on 1.029, you can see when idling the integral winds up and undershoots target more when the engine is running.

are you sure your throttle is not seized ?

The error The throttle does not return to limp home position appears when the unpowered throttle doesnt return to the limp position by the spring.

Sorry about the last log, I think idle debug was selected

Well if it was sticking around the idle range it would explain the issues, I’ll pull it off and check when I get chance.

Hello,
1.In the log file I see knocking, but on the dashboard the check lamp does not blink at this moment, the indication through the check lamp is activated and worked normally on V2. 2.When cruise control is activated, there is also no indication on the dashboard.

I will check it. What device do you use to connect via BT (EDL or BT module) ?