Firmware issue version 226

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)

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.

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?

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.

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.

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

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.

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

Thanks @Jan_Matlag_ECUMASTER

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

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

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.

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

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)

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.

Update - January 21

We have prepared a firmware build for @GVX111 that resolves the issue. This version is not public yet, as we are still validating it.

We are working with @GVX111 to verify whether this was an isolated, setup-specific behavior.

Regarding the knock sensing: our tech support team is actively working with @GVX111. Since he is using a B58 Gen 1 engine and the base map was prepared for B58 Gen 2, the knock sensing requires retuning.

2 Likes

We released official EMU PRO software 226.4 today, which resolves the reset issue.

@Jan_Matlag_ECUMASTER Could you please what will be fixed in this version? Did you fix long cranking before starting?

This version contains the same fix for the USB logger interrupt that we already sent to you in firmware 226.3 and 227.1.

The long cranking time is a matter related to the project configuration. We already have a V2 version of the B58 basemap in testing that utilizes the “Signal Level” secondary trigger. This allows the system to synchronize much faster. We are still working on this basemap and will release it soon.

We are also working on an Import/Export feature for the Client, which will allow you to update your existing ECU configuration to benefit from faster cranking without having to redo all your changes again.

1 Like

Sounds cool. Would be nice if you add presets for GEN1 and GEN2 like fuel pump configuration, will be easy for other tuners to select specific preset for fuel pump like you have for injectors.

We were considering making presets for pump configuration, but it’s a bit complicated.

We want a flexible system, that can support as many engines as possible.
The same high pressure pump is often used in multiple engines that have different lobe profile and fuel rails.

Bundling all of this into a single presets lowers the flexibility of the system.
Maybe we can do presets in the future, but we have to find a smart way of doing it.

As Jan mentioned, we are working on import/export system for project files, that will allow you to copy specific settings selected by the user from one project to another.

This will allow you to copy just the pump settings from a base map to your own project file without modifying anything else.