I think it is obvious now that something in ur fule system or calibration is not okay. But with playing with injector dead time is not good. U should measure this value one time with a clean method and then keep it like it is and tune VE. The pressure impact is also realistically irrelevant for the value here. Especially if u dont mearue fuelpressure.
U should verify ur injector data and the details of ur fuel system and then go on tuning. For me it seems u somehow try to try and error find ur injector data, which wont result in a happy end in my opionion.
maybe but at one point my config was set to a 24t can trigger instead of the 12 that emu support helped me with and when it was at 24 I was able to get it all right
Yes, that’s exactly what I’m doing. I was lucky enough to have IAT temperatures close to 20°C over the last couple of mornings, so I could use that as a proper reference condition. From the measured airflow in g/s at around 960–980 rpm idle, I calculated the estimated volumetric efficiency and obtained a VE value of around 42% for that operating point. From there I could work backwards and determine the injector dead time required at 3 bar under the actual operating conditions.
Interestingly, the result is very close to the values provided by the injector wizard. In hindsight, I probably should have tested the injectors at 3 bar first rather than trying to make the 4 bar setup work from the beginning. That may have saved me a lot of time.
After the software updates and the changes in airflow/fueling strategy, I believe there was probably a combination of factors involved: some calibration choices on my side and possibly differences in the software behaviour at the time.
the engine is now starting to run properly and the excessive smoke is basically gone.
The remaining job is to extrapolate the dead-time values for the different fuel-pressure points that the MAP-referenced regulator will operate at.
Hello, I have noticed that there is issue with gear detection in V3 software when you are using gear sensor.
So I am using turbolamik but lamik sends current gear in the standart stream and I want target gear.
Please see attached log and tune. I have current gear on can analog 3 and target gear on can analogue 3.
so when I am choosing CAN analog 2 in gear indicator sensor it still takes data from can because shows current gear and not target.
gear det tune.emub3 (73.1 KB)
gear det log.emublog3 (248.2 KB)
Hello, has one a clue on how to setup the cam2 trigger position? I can’t seem to figure it out on V3, trying to setup my M54B30 dual vanos Cam2 is the intake cam and cam1 is ext, ext works and VVT tracks,
if i do DC override on the cam i get the car to stall which means its wired right i just think its a cam angle setup issue. any help out be greatly appreciated
M54map.emub3 (67.5 KB)
The remaining job is to extrapolate the dead-time values for the different fuel-pressure points that the MAP-referenced regulator will operate at.
Emu “?” says :
The effective fuel pressure should have a constant value defined by the Base pressure parameter
So EMU always sees the “base pressure”. If you set 300kpa then it will see 300kpa deadtimes everytime. If you dont have fuel pressure sensor you can paste 300kpa (or whatever pressure you use) into whole table. When you check the log from driving EMU always show 300kpa if u set base pressure for 300kpa. In case of bosch 630cc injectors (for example) deadtimes from wizard are higher than you can find online… I dont know yet which one should I use already.
Hello,
i updatet my old classic from 0.67 to 0.68 with coils unplugged. Update was succesful. After the update my car didn´t start anymore, it synchronized, but it didnt start. Ignition on off and after this i can´t connect anymore to the emu classic. You hear the windows connection sound, but no connection. USB Data cable allready changed and I also connected the emu outside of the car directly. Nothing changed. What can i do now?
You can force bootloader by shorting rx and tx in extension port, and then power the ECU.
If you connect v3 Client it should ask about upgrading the firmware.
Hello,
Stuck with some troubles and questions:
- When I press clutch pedal (it’s connected to switch 3 by ground), AC turns off shortly.
In log its looks like shortly switching of switch 1 (where is the AC IN is connected).
Firstly I stuck with problem that Switch 2 was connected with Brake pedal by Power (12v as stock wire for Toyota did) and it turns off 1&3 that is connected by ground. I did inverion for the switch 2 by relay. This problem gone.
But this problem I dont see any parametr for this. Is it a bug or an interesting thing with connection? The wire of clutch switch goes from ECU Ground through pedal stock oem “button” at pedal and goes around to ecu to switch 3 input.
-
Is there any opportunity to choose filter from CAN analog inputs from CAN Switch board v3, i connected there a some pressure&temperature sensors and its a little bit oscillate - want to filter it just for comfort.
-
I use onboard UEGO and have a habbit to look at AFR, and when its full lean - it shows 7.2 AFR.
-
Does Ignition Correction curve (by Ign Angle) work by 0,5 angle? Or it only shows it by 0,5? And for the main ignition advance the same question (I’m not sure that there is important to work by 0,1 for example, but still interesting)
-
Why if I want to turn off only the PID or overdrive a Idle Airflow it stops even a ignition correction by curve? Is there an opportunity to be cofident that my correction is work properly without any help from other systems?
-
May be it would be good to ignore AC Press parameters to stop work AC system if AC press status is unassigned - I get it out that it is a problem, but…
-
In future is there any plans to upgrade the log viewer inside V3 studio? In would be good with oppotunity to delete before or after chosed moment, may be search of parametrs (like a list of parameters and for any of it it would be great to choose search greater than or less than). Sometimes its diffcult to search something in 1-2 hours log file.
20260820_2203.emublog3 (128.1 KB)
Log, project and the picture pinned.
Big thanks!
Toyota Soarer JZZ30 98, EMU Black REV F, CPU REV G.
200826_2105.emub3 (69.2 KB)
Its Not working, the Emu Software on the pc is After connecting the emu very laggy, i cant Even Switch through the menu and the disconnect Field is also flashing in irregular Intervals