[Dmitriy]

Something wrong whit MAP sensor or vacuum leak ?

I think dwell is to low try something between 2.0 - 3.0 msec, be careful check temperature on ignition coils.
2.4 seems to work better then 1.8 msec

And AFR looks very rich I see 12.00 at 13000 rpm.
Maybe change your settings so AFR is around 13.5 at 13000 rpm.

MAP is connected to one cylinder so it makes noise.
according to my observations, on a throttle 90% AFR 12.0 produces the best power.
The operating time of the spark changed 1.5-3.7 milliseconds. I did not notice a special difference, apart from a strong heating of the wiring.
It just seems to me that speeduino stops registering engine speeds above 13000. If it is not critical for the operation of the injectors, they continue to pour fuel, but for the formation of a spark it is critical.

For MAP you can set some filtering if needed.
Dwell, seems like you worked it out already.
Can you set the crank sensor filtering to off ?
Any change to measure ignition timing at 13000 rpm ?
At 13000 rpm every crank revolution only takes 4,6 msec !

Hello LAV1000.
I turned off the filtering of the crankshaft sensor. Judging by the logs, speeduino does not record rpm above 13000.
I continue to use standard ignition for now.
I plan to try again to the semi-sequential injection option and not use the camshaft sensor, I'll see what the results will be.

[Dmitriy]

I recorded part of the trip around the city and the highway. https://youtu.be/_K1JUVjbzNQ

[Dmitriy]

Hi friends.
Help solve the next question. In my project I am using a VE table refueling with a TPS sensor. Everything works well, but I want to improve the system even more. I need to make it possible to enter the TPS sensor steps with odd numbers in the VE table, for example 1%, 3%, 5% ... At the moment, you can only enter even numbers, for example 2, 4, 6 ... Tell me where in the firmware code can I change this parameter so that odd numbers can be entered?
In some topic on the forum this question was once raised, but I cannot find in which topic.

[theonewithin]

You might be better off using the features of the latest firmware which gives better control of maps using MAP and TPS options?

Which version are you currently using?

[Dmitriy]

Firmware 202005 works well for it. MAP in my case does not work well, so everything is tied to the TPS sensor. I just need to make it possible to enter the values ​​into the scale of the TPS sensor in steps of 1%.

[theonewithin]

Firmware 202005 works well for it. MAP in my case does not work well, so everything is tied to the TPS sensor. I just need to make it possible to enter the values ​​into the scale of the TPS sensor in steps of 1%.

Update your firmware and use map switching.

You can then get even more resolution where you need it.

[Dmitriy]

Firmware 202005 works well for it. MAP in my case does not work well, so everything is tied to the TPS sensor. I just need to make it possible to enter the values ​​into the scale of the TPS sensor in steps of 1%.

Update your firmware and use map switching.

You can then get even more resolution where you need it.

To change the step of the TPS sensor, you need to change the data type in the firmware code. I do not yet find where exactly to change the data type.

[theonewithin]

Update your firmware...

Seriously. There have been major improvements I need last couple of releases.

You may find you don't need the 1%

[Dmitriy]

Update your firmware...

Seriously. There have been major improvements I need last couple of releases.

You may find you don't need the 1%

This is also not implemented on the new firmware, I checked it before asking a question.

[theonewithin]

Once again...

The last few version of firmware has had major improvements.

You may find that you don't actually need 1% resolution.