Yes it was updated and tested in 3.037
1 Like
Thank you!
Everything is ready with car now just canbus stuff.
Its 2011 with electric rack.
Also if passible it would be great to implement fuel pump also i have canbus stream with fuel pump off and on if you need.
Hello,
I updated v3 to 2nd car but diferent type of triggerwheel instead of 36-1 in this config Iam using 36-2.
In both version I noticed much longer start - gap detection calibration have no affect to improvement.
I have more revolution than in V2 till ECU starts to squirt and sparks.
In both cars Iam still using wastespark and “squirt twice”…
In case ov 36-2 config i noticed that “quirt twice per cycle” is not applyed even though Iam using recomended setting for that function (in version 36-1 it works).
I would say that car was able to start much faster in v2.
Iam also missing the function “afterstart ignition lock”
publish your setup, i think your config is wrong.
in v3 the engines starts much faster than in v2.
I can see that the spark is performed immediately after sync so it should fire the mixture from prime pulse).
If I will have a map I will test it on simulator.
On second scope all injectors work twice per cycle.
Hello,
thank you for fast feedback (as always 
)
Here Iam sharing both configs.
B_169_013.emub (145.6 KB)
the most important settings was implemented here:
B_037_001.emub3 (62.9 KB)
The socond picture its 36-1 triggerwheel, first picture its 36-2.
CANBUS: Mazda MX5 stream added
Exciting!
However, It’s my experience that DSC vs/ Non-DSC CAN streams are different. What year/trim was this developed on?
Thanks!
the car what we had for CAN logging was MX 5 NC 2010
Try the following settings. Also disable fuel during cranking and adjust prime pulse to get primed fuel ignited. Then work with the cranking fuel dose.
Also you can try the following firmware. There is small improvement for Squrt twice per cycle and engine cranking:
Firmware 3.037 cranking squirt twice per cycle improved
When you set up everything please send me a scope from cranking.
Hello thank you for your crazy fast support.
I tryed your new FW and recomanded settings with no success.
Than I tryed your new FW and my setting and it works.
It works so well that Iam crying and laughting at the same time - Engine runs in half second. Much better than from factory.
Bellow Iam sending you all data - look for the the file naming.
I noticed that prime pulse is missing - but in my case it has no efect to final peformance 
Is there any other measuremen I should deliver to you?
NewFW+My original settings.emublog3 (41.9 KB)
NewFW+My original settings.emubscp3 (620 Bytes)
NewFW+recomended settings.emubscp3 (628 Bytes)
1 Like
Ok so make it step by step:
- Change trigger tooth from 0 to 2 and change trigger angle from 88 to 68
Check if the engine starts.
- Change injector phase from 1->1, 2->2, 3->3, 4->4 to 1->2, 2->3, 3->4, 4->1
Check if the enginge starts
According prime pulse it is executed when firs pulse from the trigger comes.
So you need press the scope button first and then start to crank.
On your socpes there is no beginning of the cranking
Hello,
in all cases engine starts well.
Becouse of many cold starts with heated lambda - sensor is already out of order.
Here you have the results ( I hope my dislexy was this time out so all settings wer set properly )
TEST - 1
TEST_1.emublog3 (104.5 KB)
TEST_1.emubscp3 (635 Bytes)
TEST - 2
TEST_2.emublog3 (123.2 KB)
TEST_2.emubscp3 (634 Bytes)
TEST - 3 (“original” settings)
TEST_3 - OrigSettings.emublog3 (155.2 KB)
TEST_3 - OrigSettings.emubscp3 (630 Bytes)
I tought that scope is proceded all the time Iam pressing the trigger button.
Then I realized that when the time frame is out new measurement is made. That was probably the reason.
In new measurements its visible.
the test 2 scope ia the best. keep that settings.
1 Like
Thank you for your feedback and recomandation.
Would you be so kind to explain me what are you watching for to analyze whats the best settings?
I was setting the trigger wheel position via osciloscope and was comparing the teeth and starter current (A) peak.
In the log that I sent you, whats are the parameters you are looking for to decide that?
Thanks a lot in advance for your answer.
I take randomly only one measurement from each test and all of tests I provided were really similar by driver feeling.
First change (the trigger tooth) makes the first injection faster (before the spark).
In your original file your spark events are offseted with the injectors events.
If you look at your scope the injectors inject fuel but the spark is on a different pair of cylinders. So the second change fixes this.
So both changes should improve engine start, however, I think the prime pulse is working for you.
1 Like
I found the issue with the vvti. It is already fixed for 3.038.
For now you can fix it by entering 0 to VTEC off delay parameter
2 Likes
Thats great! Thank you sir 
Hello, I found another issues.
Log graph:
When new measurement is started and you want to stop/pause the measurement, its possible to click the button but nothing happens till log findow is filled till the end.
When measurement lines are drawn from left site of the windor till to the right, then log is stopped.
Log graph / Log condition
When you want to measure (in my case) only when TPS is mpre than 95% and condition log is enabled, it always acts like measurement is stopped.
F2 button
I miss the functionality of F2 button from v2 where implemented changes are visible as bold numbers/values.
Last thing is only question:
I really like to overtaking possibility from the calibration in “Compare current project” window.
Ist spossible to overtake only variables, but its not possible to overtake table values.
Is thare a reason? Its becouse of possibility that dimensions of the axes are diferent?
In my case Iam focused to two engines types and Iam trying to design my calibrations by the same way.
All tables have same dimensions for whole fleet.
If its like that, isnt the solution just some note before overtaking "your calibration can be damaged becouse of possibility that table axes are differently calibrated, plese check the compatability"
?