Firmware issue version 226

EMU PRO
1

Hello,
We are running a B58 engine on an EMU PRO 8 with GDI. We are experiencing an issue where the engine suddenly turns off. When this happens, all logged values freeze and the engine shuts down. There is no issue with power supply. I have attached logs showing when the problem occurred.

Shut Down without wakeup down.emuprolog (2.2 MB)

2

Hello
The WDT Reset causes the engine to stop. We will address this issue no earlier than January 7, as we are currently on a holiday break.

3

Hello,

As Norbert mentioned, the watchdog reset has caused the ECU to reset. This should not happen. We consider this to be a software issue.

Please tell us more:

  • Are you using the B58 basemap provided by ECUMASTER?
  • How many times has this issue occurred?
4

Yes, I’m using a basemap. Sometimes it shuts down immediately, and other times it shuts down randomly after 5 minutes, 10 minutes, or even 20 minutes.

5

We developed the B58 basemap on the PRO-16 model (using only three connectors), and we didn’t encounter any reset issues.
Today, we will test the engine on the PRO-8 model.

I will keep you posted.

6

I’m sending new logs from a cold start. The engine shut down four times during startup.

4x shut down on cold.emuprolog (639.2 KB)

1 Like
7

Thank you for today log. It’s very valuable, as it shows completely different location compared to the first one. Do you have any other logs showing the issue?

We have the “ECU Watchdog Tag” channel to identify location of a reset. The channel holds a special number used in the firmware code, and we can roughly identify the location of the reset.

Today, we tested the engine on two EMU PRO-8 units. Everything worked as expected, with no resets.

Since we are not able to reproduce this issue on our side, we will ask you for your help. Tomorrow we will prepare a modified 226.x firmware with additional debugging/instrumentation code that will help us better understand the exact location of the issue.

8

I’ve sent you direct message with the firmware links.

9

Thanks @Jan_Matlag_ECUMASTER

I’ll try to get a new logs and share with you.

10

Hello @Jan_Matlag_ECUMASTER

Probably, issue has been fixed. I attached new logs for you.. Do you know why it is cranking too long? sometimes engine running in one cycle and sometimes spinning too long.

216_1shut down.emuprolog (1.3 MB)

216_2 shut down.emuprolog (1.9 MB)

In last log still shutting down engine.

206_1_still_turning_off.emuprolog (4.3 MB)

Also Interesting with Knock sensor. Did you calibrate oem Knock sensor in base map?

1 Like
11

Hello @GVX111,

Thank you for the logs.

  1. Random resets
    Yes, indeed, the issue is still present on two of your logs. However, the locations indicated in the logs are very hard to explain. We are still analyzing the problem. Could you please email me your current project at jan.matlag@ecumaster.com ?

  2. Long cranking
    We already have a solution for the long cranking. We prepared a modified basemap that uses a different secondary trigger. We will be testing this next week and will get back to you with the results.

  3. Knock
    I’ve been informed that we are already using the factory knock sensor and that the knock strategy is calibrated in the basemap. Please let us know if you have any questions or suggestions regarding knock control.

12

My tuner is Shota Babilodze . @RACKER Could you please share details about knocks?

13

Attached new log during driving. Its still switching off

2026_0104_2255_switching_off_during_running.emuprolog (593.1 KB)

Also attaching logs for Knock sensors

Knock Logs.emuprolog (4.9 MB)

14

I’ve sent you an e-mail with a custom firmware update that will help us fix the reset problem.

I also asked the person that prepared the basemap to help you with the knock. He will be back in office after holiday leave at 7th January.