Any strange behaviour, crashing issues etc, post them here! Problems compiling the firmware should go in the General support section rather than here
#70471
RoverMini1300 SPI
1、After a certain period of time, the engine stops
2、The crank angle sensor was changed to a new one, but there is no change.
3、When the injector is moved by hardware test, it works fine.
4、The resistance value of the SPI injector was about 1.7 ohm.
5、The resistor for Low-Z is 4.7Ω.

I seek any advice from these symptoms. Please let me know if there are other areas I should investigate.
#70498
For easier, quicker and better analysis, please post a log that includes the issue, using the exact tune posted. We prefer to see logs and tune files together in a ZIP file, ensuring correct matching (even if the tune didn't change). This allows checking the log for expected settings responses, or the settings for any anomalies seen in log data. Thanks.
#70509
Hi! first,I want to apologyze my bad english.

I saw something like this on a Seat Ibiza 2.0 16v from 2001.

The cold start worked fine,but 15 or 20 minutes later,the engine stops and was impossible to crank again.
the distribution was out of time 2 teeth,and the ECU had problems with the signals from crank and cam.

I don´t know if it could be your case.
#70516
Canary90 wrote: Fri Jan 17, 2025 10:44 am Hi! first,I want to apologyze my bad english.

I saw something like this on a Seat Ibiza 2.0 16v from 2001.

The cold start worked fine,but 15 or 20 minutes later,the engine stops and was impossible to crank again.
the distribution was out of time 2 teeth,and the ECU had problems with the signals from crank and cam.

I don´t know if it could be your case.
Sync loss appears only during cranking/stall which is not uncommon and not really a problem.

Mini1300SPI_cryman wrote:After a certain period of time, the engine stops on its own.
It appears that your PW drops off to 0 and the engine stalls as a result. I do see that a second fuel table is enabled that is all zerod out. Disable the secondary fuel table and try again.


Another thing that I have noticed is that the tune appears such that there was no base tune loaded. A LOT of the fields are broken, Load the generic base tune, and reconfigure.
All fields need *something* in them, loading the base tune will populate sane data. This matters even for functions that are not in use, invalid data that is there on a clean brand new atmega will cause problems.

Side note for the VE table, you have multiply by BARO, this should be set to FIXED for speed density, and baro table used for any baro related corrections - usually a very minor correction due to backpressure differences and MAP itself taking up the air density changes.
RPM spikes

Thank you both so much, it's working well enough t[…]

Subaru EJ25 DOHC

Ensure you turn off the hardware test when crankin[…]

The only part of this project that I've done enoug[…]

Idle advance control

Generally timing will be added (positive values) i[…]

Still can't find what you're looking for?