We bought Emu black ecu for my friend’s project car. For testing I connected it to my car, updated firmware and loaded my configuration file. With this new ecu lambda reading around 20 to 25 percent richer. I am using the internal wideband controller on the emu black and using bosch lsu 4.9 sensor. only difference is this new emu black using type c connection and my 6 months old emu black is micro usb.Is the new emu black reading the right value or the old one ?
You may be have older emu black who needed resistor for lambda, if you have it remove, but only if you will leave new emu black with usb c in that car.
Do I need a Resistor for LSU 4.2 and Black without USb-c ?
Wideband readings where always strange, the reading startet late, even with fast heatup…
Doesnt need a resistor. The sensor is heated up according the Bosch documentation to protect the sensor. It takes quite a long time.
There is an option to calibrate the WBO circuit. You need to disconnect the sensor and select the Calibrate WBO from TOOLS menu. It improves the readings around lambda 1.0.
1 Like
This is my ecu with micro usb version O it does not need a resistor as the info
Or type c version have a problem reading rich ?
Type c ecu have a version of R
The resistor doesn’t influence the lambda readings.
Try to disconnect the sensor and make calibration. Maybe there was made calibration with connected sensor.
Each device before shipment is tested and the test results are written to the database. So we can always check the test results based on the device serial number. Of course the device needs to pass all test to get the serial number sticker.
For confirmation electrically disconnecting o2 sensor not free air calibration.
I connected the AEM wideband to the car. The AEM is reading 15.1–15.3 AFR, while the EMU Black reads 14.5–14.7 AFR.
I changed the O2 sensors between the ECUMaster and the AEM AFR gauge, but the same problem persists.
I tested with electrically disconnected calibration did not solve the problem.
I would assuem AEM reads wrong.
All was tested many times in calibration gases without any issue.
The offset you calibrate with the disconnected sensor influences the readings around lambda 1.0 (0.98 - 1.02)
How did you test ? On idle ?
Yes i did test on idle.
I doubt in stable idle with AFR 15.4
I have this exact same issue. Any resolution? Aem reads 1.5 value higher than emu controller. Same aem gauge ran on car for ten years prior to emu black upgrade. I’m running two sensors at the same time and the idle feels better following the aem controller vs emu. When aem reads 14.7 emu reads 13.2 and idle is smooth. When I adjust the ve table to lean emu reading up to 14 plus the aem reads 16 plus and starts slightly misfiring. Swaping sensors with controllers doesn’t make the problem switch.
Im my Black USB B with LSU 4.9 + resistor got the same results . Emu shows 13,8-14 but the innovate got 14,5 afr and engine run ok .
1 Like
What are yours Lambda reading (not AFR).
I really doubt that engine can idle with AFR 16 (for gasoline).
We have 5 gas analyzer as well as Bosch lambda controller.
The V3 software was tested many times with black as well with the classic and the lambda readings were in spot wiht 5 gas and Bosch controller (logged via can).
Especially form Lambda 1.0 I cannot imagine that the readings are wrong (the IP current is 0).
Also make sure the calibration resisotr is properly connected, it influence the lambda readngs a lot.
The calibration of WBO that is present in V3, just correct small offset around lambda 1 (we are talking about 0.01-0.02), For lambda lower than 0.95 the calibration doesnt matter .
1 Like