Software opinions

Yea, I was thinking to do that to trace voltages, just didn´t have time to do that yet. Was thinking also to use my oscilloscope.
Did quick V3 scope however.


(it seems that .emubscp3 scope files are not allowed as attachment)

Edit: not sure if that screenshot is correct or not as it changed 8->2 every power off, but I´ll do more testing when 3.017 comes out.

The place of ignition and injectors events are for sure proper.
The displayed cylinders mark are improper. They are calculated on PC based on data from file. Your configuration is untypical and for sure the algorithm need to be improved. Also ignition trims are not taken into consideration when display TDC and ignition angle marks.

1 Like

It´s working nice with wasted spark, but in full seq. mode cyl 1 does not fire.
Dunno if I´ve made some misconf.

wastedSparkStart_ok.emublog3 (26.7 KB)
VROD_V3_livetesti_3_017_seq_not_ok.emub3 (53.2 KB)
VROD_V3_livetesti_3_017_seq_not_ok.emublog3 (88.1 KB)
wastedSparkStart_ok.emub3 (53.3 KB)
start_log_map_analog4.emublog3 (264.7 KB)

edit. added log from map sensor wired to An4

Hi SamiN!

I tested your project on the test bench. I think your problem in full seq. mode is wrong engine phase when the spark appears. If the cyl #2 ignitie, you need to change the firing order like that:

image

If you set wasted spark then the spark for each cylinder appears twice so phase is not important then.

1 Like

Also I would suggest to change trims. Now you have 0 and 30. I would change it to -15 and 15 and adjust trigger angle.

1 Like

Thanks! Will test with lamp again.

I can confirm that now it works perfectly well! Full seq with map sensor as cam sync and -15 +15 trims :+1:
With wasted spark crank, it fires up as soon as you touch the button. :smiley:

1 Like

You can still select wasted spark for cranking only. I put a lot of efforts to improve the engine start by providing the spark and fuel as soon as possible.
Also proper setting of prime pulse allow to start the engine with the 1st spark.

2 Likes

Yes, that´s what I was meaning. Without WS cranking it did fire up nicely after 1 full 720 cycle but with WS cranking it did fired up immediately. :heart_eyes: Huge improvement to V2!

V2 engines like those HD´s dont like much cranking as they kill their batterys very quickly.

Not strictly V3 related (same with v2, but is there any plans to improve lambda accuracy near L1?
What I noticed once again yesterday, V3 (bosh 4.2) was showing 0.07 richer than our dyno. You can indeed feel it too that it´s off.

It is improved in V3 as I added option for calibration lambda sensor circuit. In board revision O we made small improvement in lambda circuit, however in the older boards the calibration procedure should improve Lambda readings precision around 1.0 a lot. 0.07 seems to be a lot (lambda 0.93 instead of 1).

To make the calibration just make sure the sensor is cold, turn ignition on and then immediately from the menu tool select option calibrate WBO circuit.
Then go to into logbook and post here the value of WBO calibration (WBO cal)

Ok, thanks. didnt notice that there is tool for that.

But error 0.07 seems huge. Are you sure the wbo sensor rcal is connected ?

Here is a log from BLACK, LSU 4.9 (green) and reference lambda controller connected via CAN 2 (violet color). As you can see at lambda 1 error is small.

Checked that all 6 wires are in place… not much more. Tried with new sensors also. changed new 4.2 to bike and new 4.9 to dyno with same results.

I have couple of hours of log from yesterday if you want to look at.

But do you have both sensors logged ? And are you sure it shows 0.93 instead of 1.0 ?
I’m very curious how it will calibrate

Negative. Dyno lambda is not in logs. Was using my eyeballs.
I can connect it to Black an do some more testing.

But it is sure that it was .07 off

Here is my lambda cal. It is still like 0,04 off based what I´ve tested. (both with AEM and Zeintronix).

I can also confirm that autotune now works with 019b

Capture_Lcal
20240212_1954_V3019b.emublog3 (731.0 KB)

I’m very surprised of the caluvration value.
U didnt expect it can be higher than 4096.

Did you make autocalibration with the sensor disconnected ?

Yes, free air cal.

Did a test today with 3 lsu4.2sensors.
Sensor 1 WBO cal.: 4115
Sensor 2 WBO cal.: 4075
Sensor 3 WBO cal.: 4121

BUT… Now when I changed emub sensor position to place where my “reference” sensor was (40cm further on pipe) there was very little difference so i assume that it was more sensor placement that caused original .07 big difference with uncalibrated sensor.