Hello everyone.
This is my first time posting.
I am Japanese so my English may not be correct.
Well, I have created the data to start with V3 firmware.
However, I encountered a problem.
The engine starts, but the injector open/close time at startup is long.
In V2 firmware, it was about 4ms.
The cranking map is also increased only 150%.
Please advise if there is anything else to check.
The car is a JZX100 1JZ engine.
The data uploaded.
v3 first start.emublog3 (74.1 KB)
running_test v3 jzx100_2.emub3 (62.0 KB)
Hello,
Please do a scope file from cranking.
There is no sign of a running engine in the log file—only cranking. The “executed spark count” remains at zero, which suggests that the engine may not be correctly decoding the trigger.
1 Like
HI i hope this help you
Cranking fuel 1
The Cranking fuel table defines the scale by which the calculated fuel dose should be changed based on the coolant temperature and engine revolutions. It is important to emphasize that a value of 0% means no change to the calculated dose, while 100% represents a doubling of the calculated fuel dose, and so on.
The main VE table is used for calculating the base fuel dose in cranking state!
The fuel dose at startup also depends on the Lambda target parameter in the Cranking/Parameters menu. The smaller the Lambda target value, the larger the fuel dose will be delivered.
In the case of using fuel with a variable ethanol content, it is possible to create two Cranking fuel tables, one for pump gas and one for the maximum predictable ethanol content, and then blend them depending on the reading from the Flex Fuel sensor.
This allows for optimal starting on both pump gas and E85 or even E100 fuel.
To achieve this, the Flex Fuel sensor must be activated, and the blending map FF Crank. fuel (FF Crank. fuel blend) in Tables switching options must be configured.
2 Likes
Thank you all for your help.
I loaded an old log file by mistake. 
I will try the cranking fuel as I have not reduced the fuel.
