New software 3.047 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_047e.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:

Missing for official release:

  1. V2 importer
  2. DSG Help
  3. Minor bugs

Change log:

  • NITROUS
    • Strategy added for dry, wet, and progressive systems
    • Two-stage operation
  • TRANS-BRAKE
    • Trans-brake strategy added
  • FUEL
    • 3D tables for injector trim
  • MQB
    • DSG RPM signal generation via H-BRIDGE 2A
    • Idle target modified based on gearbox feedback
  • DSG
    • Idle target increase added based on DSG torque losses table
  • OTHER
    • Latency control for AUX and ignition outputs improved
    • Base maps directory added (first available base map: AUDI A3, R32 BUB DSG)
  • EMU CAN STREAM
    • Injector PW channel fixed
    • TPS, PPS fixed
    • Functions 1–8 status replaces Virtual outputs and parametric outputs from V2
  • ALS
    • Short-term trim is disabled during ALS
  • TC
    • RPM condition bug fixed
  • PADDLE SHIFT
    • Fixed cut issue when shifting to 1st gear
    • XAP controller CAN support added
  • TRIGGER
    • COLT CZ CAM and CKP trigger decoders added
    • CAM-based pattern with 2 missing teeth added
  • HBRIDGES
    • Configuration of H-bridges (DBW, EWG, MQB, Outputs) rewritten
    • New log channels for HBRIDGE1 and HBRIDGE2 modes added
  • DBW (Drive by Wire)
    • Mode selection changed; new DBW mode parameters introduced (reconfiguration required after upgrade)
    • ECUMASTER DUAL H-BRIDGE OVER CAN support added (mainly for BMW S54 ITB throttle)
  • DBW TUNER
    • New throttle type support (Standard throttle, BMW S54 ITB)
    • Single-output PWM S54 BMW ITB support added
  • CAN BUS
    • Clio 3RS code optimized
    • MQB CAN can operate in parallel with other CAN streams
  • TIMERS
    • Drag racing timer added
    • Timer resolution increased to 0.1s (from 0.25s)
    • Timer strategy rewritten
  • OVERRUN
    • Fixed error involving high ignition entry and exit rates
  • VVTI
    • Cam angles reset to 0 when engine is not running
  • HELP
    • DBW help added, covering various methods of controlling the S54 ITB throttle
    • Nitrous help added
    • Ignition help completed
  • SCOPE
    • Data collection bug fixed (progress bar freeze issue resolved)
  • GAUGES
    • Coolant pressure gauge added
  • GRAPH LOG
    • When all channels are removed, a message (“Please select channel(s) to display”) replaces the black screen
  • LOG
    • Knock voltage peak for each cylinder range changed from 30V to 5V
  • OTHER
    • LC indicator in the status bar fixed
    • V2 Importer crash fixed (sensor and ignition settings now import correctly)
    • Missing files for Trigger Wizard’s supported engines added

Available Triggers:

  • BMW E36 M52B20/M54
  • BMW E46 N42B18
  • FORD FOCUS MK2 ST225 (B5254)
  • LEXUS IS200 (1G-FE)
  • NISSAN VQ35
  • VW R32 (BUB, BFH)
  • LOTUS EXIGE 380 CUP
9 Likes
3

I don’t see the cranking ignition angle option in the engine start parameters :thinking:

1 Like
4

Thank you for your feedback. This parameter was hidden by accident.
I’ve updated link from 1st email to new version (e)

5

Has the Dual H-Bridge modification been addressed to control a separate stepper motor in Haldex?

6

What is the purpose of generating a DSG RPM signal via an H-Bridge 2A, and what advantages does this method offer?

7

(Automatic translation from Japanese)

This may not be limited to this firmware version, but please let me know.
How do MinRPM, MaxRPM, and MinTPS in the Knock Sensor Action window work?
Also, does this parameter change the state of Knock Action Status ‘Active’ in the Knock Sensing Log?

Furthermore, after the first cranking, a knock count always occurs when the engine starts.
Is it possible to wait a little while after the engine starts before processing the knock count?

One more question.
In the changelog for this firmware,

  • Latency control for AUX and ignition outputs improved
  • Configuration of H-bridges (DBW, EWG, MQB, Outputs) rewritten
    Can you provide more details about the above?
8

Have you also tested an DQ500? Or any other customer here in community?

Because a friend tested already and said that the ecu is sending 0Nm at shift and gearbox goes in fault and do something random…

9

How is this possible working the software?

Thanks
Ben

10

There is a support in black for Dual H-Bridge but the H-Bridge team didn’t add a support for stepper motors control :frowning:

11

MQB gearbox requires RPM digital signal proportional to RPM (1Hz per RPM)

1 Like
12

The Knock action is only allowed when the RPM is in range MinRPM and MaxRPM and the TPS is above minTPS.

There are 4 statuses:

  • Disabled - the knock sensor action strategy is not enabled.
  • Inactive - condition not met The necessary conditions for the strategy (e.g., too low RPM) have not been met.
  • Inactive no knock - the conditions for the action strategy have been met, but no knock has been detected.
  • Active - knock has been detected, and the action strategy is active.

Furthermore, after the first cranking, a knock count always occurs when the engine starts.
Is it possible to wait a little while after the engine starts before processing the knock count?

I’ve added this to the bug tracker to be fixed.

  • Latency control for AUX and ignition outputs improved
    I’ve made some code optimisation what lower the latency of outputs by 32ns

  • Configuration of H-bridges (DBW, EWG, MQB, Outputs) rewritten

The H-Bridges are controlled by 2nd microcontroller. In new FV versions hbridges have more specific functions like EWG, MQB RPM signal generation, etc. So the whole configuration and communication with h-bridges were rewritten. It has no visible effects for the end user (until there is a bug :))

I’ve mentioned it because if someone will have issues with H-Bridges function it will be easier to track potential reason.

13

The DQ500 communication is very very similar to DQ250. Are you sure the connection is ok ?
Most of DQ500 has component protection. With component protection active it is not possible to use the gearbox, and it must be removed first.

1 Like
14

You need to select you desired CAN stream, and enable DSG support.
The only requirement is that there is no clash between DSG CAN Ids and vehicle CAN ids.

15

Do I need to wire something for that on an A3 8P? Or is it only important for cars that didn’t originally come with DSG?

16

It is only for MQB platform. I assume you have PQ35 so there is no need for that.
With this release there is a base ma for audi A3 R32 with the BUB engine and dsg gearbox

1 Like
17

Ok, and will they ever prepare support for the stepper motor?

18

BMW E36 M52B20/M54 tigger wizards firing order doesn’t look right.
why just not going 1,5,3,6,2,4?

19

Thank you for your answer.

In my environment, when the knock sensor action is enabled, KnockActionStatus in the Log window remains Active in any state.

Is there a problem with the settings?

スクリーンショット 2025-04-05 21.23.13
スクリーンショット 2025-04-05 21.23.131920×1048 197 KB

スクリーンショット 2025-04-05 21.24.18
スクリーンショット 2025-04-05 21.24.181920×1048 197 KB

20

I need to talk to our engine engeneers that provides me this settings.
Thank you for submission.