V3 studio 3.068

There is a new software version with new features and bug fixes.

More information can be found in the change log.

https://www.ecumaster.com/files/EMU_BLACK_V3/V3StudioSetup_3_068.exe

EDL firmware 1.28

Change log file: https://www.ecumaster.com/files/EMU_BLACK_V3/changeLogV3.pdf

EMU Classic:

  • Added Flex Fuel sensor support.

  • Alternative analog inputs can now be assigned to CLT and IAT sensors in Analog Inputs configuration.

Boost:

  • Boost Target Correction is now applied before the Boost Target Limit.

  • The Boost Target Correction log channel is now zero-based: 0% indicates no correction.

Idle control:

  • Added the Armed Airflow CLT Correction table.

User CAN:

  • The Lambda scaling divider has been changed from 1024 to 1000.

Overrun:

  • Fixed an issue with spark cut when Overrun was blocked by Idle Control.

Logbook:

  • Improved filtering of false errors registered during ECU startup.

Lamik TCU:

  • Fixed an issue where the strategy could consume CAN messages with unrelated IDs.

CAN BUS:

  • Fixed BMW E46 DSC button support.

Trigger system:

  • Modified position calculation parameters for Subaru WRX STI engines using three CAM sensors when a CAM sensor is connected to the VSS input.

Gear cut:

  • The minimum allowable value of the Min TPS to Cut parameter has been reduced from 5% to 1%.

DSG:

  • Modified the automatic upshift strategy.

Logbook - EGT 1052 on system startup .

Do you have connected sensor ? Or egt inputs are not connected ?

Connected sensor , when i errase it and run engine the max egt shows normal . Ignition off , ignition on and the logbook still shows wrong egt .

When i connect second egt sensor there is no problem in logbook , no errors .

I am currently using the “Custom Air Flow Correction” feature to adjust the airflow in response to the increased load when the A/C compressor is engaged.
Have there been any changes to how this is handled since updating to version 3.068?
The idle speed does not drop to the target value even when the A/C is turned off.
Am I overlooking something? I recall it working correctly prior to the firmware update.

The log sequence is: engine start → A/C switch ON → OFF.

18212114.BG3 (646.5 KB)

QNC10_Passo_K3VET_RHF5_34.emub3 (71.3 KB)

No modification for that.

Only armed air CLT correction added

I will check for a physical failure of the ISCV.

The issue was resolved by replacing the ISCV.
I briefly reverted to version 3.065 during the replacement, but the control transition feels smoother with the latest firmware. Everything is functioning perfectly, including the lambda control.

Hello, I am trying to update to the new software 3.068 in V3 Studio. This is an older ECU updated to 3.061 but is not recognized in the V3 Studio software. Thank you, Stratos

What do you mean ? You cannot connect to the ECU ?

Yes, i cannot connect to ECU.

I cant see the reason in the software as communication module wasnt changed. Also no negative feedback from the customers.

Are you sure you usb cable is ok ? Is your windows recognize the device when you plug usb cable ?

I cannot see the reason too. I opened the V3 Studio 3.068 software to FW update to V3. The ECU was already connected to V2 software to the same Laptop. So i tried the older V3 3.061 with the EMU V3 software and the ECU was connected.Yes, the device is recognized .

Thanks,

Stratos

HI @Jadzwin_ECUMASTER.
If there’s any chance in the next software release you might be able to include the BT Toggle Switches and BT Rotary Switches in the ‘Show assigned inputs’ screen, and the ‘User Names’ screen, that would be useful. I’ve got the edash working on my head unit now. Not a huge issue, more of a ‘nice to have’.

Thanks for all your work!

Cheers,

Jon

Is the AC setting in the AirflowCustomCorrection operating conditions in the Idle settings the same as the current AC switch operation?

I am currently using a function to adjust fuel delivery prior to A/C clutch engagement.
It would be very helpful if the ‘AC’ in airflow correction could be switched ON and OFF like the clutch operation at the timing before the ‘Time to engage’ of the clutch operation.

That was an oversight on my part. I’ve confirmed that AirflowCustomCorr does indeed track the clutch status even with the AC setting enabled (applying correction before the clutch engages).

The issue is that I want to delay the cut-off for AirflowCorr and fuel when the AC clutch disengages.
To achieve this, I would like to request either adding AC as a selectable element within the ‘Function’ settings or adding a delay option to the AirflowCustomCorr configuration.

The meaning has been reversed in the automatic translation.

AirflowCorr off a specified time earlier than the AC clutch, or adding a delay off to the AC clutch.

Any update on the increase of rev limiters higher than 15000 RPM?

I tested 3.068 and the highest possible spark cut rev limiter is still 15000 RPM.

Confirmed with the scope that the ignition outputs are disabled above 15000 RPM. Fuel injection continues up to the hard fuel cut limiter set to the maximum of 20000 RPM.

Yellow is an ignition output, purple is a secondary staged fuel injection output, blue is a main injection output.

Interestingly if I change to Fuel Cut Type limiter the rev limiter does not take effect on the secondary injection events and I can rev up to 20000 RPM with fully functional ignition and secondary fuel injection outputs.

14500 RPM, no limiters active.

Yellow is an ignition output, purple is a secondary staged fuel injection output, blue is a main injection output.

15500 RPM. Main injection is disabled by the rev limiter which it should not be until 16000 RPM as calibrated. Secondary injection continues. Ignition continues. The fuel cut percent log variable indicates 38 % fuel cut.

19500 RPM. Main injection is disabled by the rev limiter. Secondary injection and ignition output continues to very high RPM.

20500 RPM. Finally above 20000 RPM the secondary staged fuel injection is cut by the hard Fuel Cut limiter.

Ignition outputs are fully working and the EMU Black V3 can apparently support much higher RPM than 15000 RPM for a 24-2 trigger at least.

It seems like the EMU Black can support both ignition and injection up to 20000 RPM with no issue for 24-2 trigger.

Is it the rev limiter strategy that saturates or is limited to 15000 RPM?
Is this so that all supported high tooth count trigger wheels can be accommodated within timing limits?
Can some sort of adaptive max rev limit be implemented based on what trigger is used?
Can an option for a simpler hard cut rev limiter cut be implemented that supports higher RPM? Or can an option for completely disabling it and relying on the hard cut fuel limiter be implemented?