[rusEfi] hello all - Mitsubishi #31

[AndreyB]

Yes but I suspect this does not matter much.

please execute enable trigger_details and post logs - would it synchronize properly with both triggers? (same setting is "print sync details to console" on TS

[AndreyB]

update: enable trigger_details is the right command

[matt]

with mitsu trigger it not start. with miata it runs ok at begining(with dyno chart i attach before). but after i change the pull-up setup, it can't start.

[AndreyB]

with mitsu trigger it not start. with miata it runs ok at begining(with dyno chart i attach before).

this is not enough hard data for me to understand what's going on. Please remember that I am really, really far and I know very little about what's going on with your car. if you are looking for help please provide much more data. please enable detailed trigger and report.

Any reason why you do not want to just run as Miata NA?

[matt]

yes i know it is lack of data. i am at office now, i will provide you detailed trigger and report once i reach home.

Any reason why you do not want to just run as Miata NA?

i scare if it can cause any problem to my engine.

[AndreyB]

i scare if it can cause any problem to my engine.

You need a timing gun, regardless on which trigger. We can work on shape definition but the only way to know angles is a timing gun.

[matt]

i try to configure rusefi console, but no luck.
did i miss something?

console.png (115.5 KiB) Viewed 25606 times

[AndreyB]

You do not need serial <> TCP adapter to run console. You need to disconnect TS and point console at the same port with same speed, should be very easy.

[matt]

ok. got it!!
i thought it generate via mini usb.

[AndreyB]

i thought it generate via mini usb.

mini usb on frankenso board, not mini usb on discovery

[matt]

and here is my trigger shape..

2017-02-23_21_55_33rpm_1037_maf_NaN.png (28.94 KiB) Viewed 25610 times

[AndreyB]

I need more precise data. Please run with sensor sniffer set to 'trigger' and publish your .csv file

see http://rusefi.com/wiki/index.php?title=Manual:Software:UnknownTrigger#Step_2:_record_tooth_angles

[matt]

here is my mitsubishi trigger.

2017-02-24_10_10_50_rpm_1051_sensor.png (5.54 KiB) Viewed 25591 times

[matt]

enable trigger_detail

trigger detail.png (137.07 KiB) Viewed 25588 times

[AndreyB]

I need more precise data. Please run with sensor sniffer set to 'trigger' and publish your .csv file

see http://rusefi.com/wiki/index.php?title=Manual:Software:UnknownTrigger#Step_2:_record_tooth_angles

Please run with sensor sniffer set to 'trigger' (this I see above)
and publish the full log - it's going to be a something.csv file in the out folder where console was running

[matt]

got it.

[AndreyB]

I've extracted angle information from your log. See before and after pictures - you would need firmware 20170223

before

trigger_11_before_matt.png (5.3 KiB) Viewed 25578 times

after


PS: you really need a timing gun

[matt]

finally its start..
trigger offset is 620 and if lower then this it advance the ignition timing. i dont have timing gun yet, just try and error test.
only issue is i got trigger error 4-5 times while cranking. once it come a stable rpm, engine start. any i can adjust to solve this issue?

[AndreyB]

any i can adjust to solve this issue?

Nothing at this point

[stefanst]

Trigger errors during cranking are fairly common. My Megasquirt usually takes about two or more full crank rotations before it syncs up. Rusefi is actually working better for me here.

[matt]

what i notice, i got very stable 12v while cranking and engine running. maybe it something is wrong somewhere i guess.

[matt]

Trigger errors during cranking are fairly common. My Megasquirt usually takes about two or more full crank rotations before it syncs up. Rusefi is actually working better for me here.

yes. agree with you. i don't know why, my car can't sync with 5v pull up. with ms2 i must use opto-isolator and then it will sync nicely. same as speeduino. but with rusefi it can start even without opto isolator.

[matt]

for crank and cam input must be at PA7 and PC5? or i can use other pin?
i think something is going wrong at my channel 9 and 11.

[AndreyB]

for crank and cam input must be at PA7 and PC5?

I think you mean PA5 and PC6?

No, there are a couple of options for these pins - see TunerStudio project it would give you selection.

[matt]

done some testing today and sorry, i don't know any about trigger calculation/firmware code.
my car start faster with miata n/a (snapshot_20170218_2011_rusefi) but with (snapshot_20170224_0905_rusefi) it can't start and got some trigger error. with mitsubishi trigger i use with (snapshot_20170224_0905_rusefi) it start once with 630 off set, after that no luck at all.

[AndreyB]

i dont have timing gun yet

we are blind without a timing gun.

[matt]

i got found something. if cranking dwell is set over 5ms, it will interrupt rpm sync and cause a false trigger.
now i set cranking dwell to 3ms, and it start pretty fast with new mitsubishi decoder.

[matt]

done on the road testing yesterday. my engine can pull to rpm7200, but around rpm 6900 i can fell something like rpm cut. i dont know what it is. rpm cut is set to 8000. trigger set to miata na. gonna fix it in this week before i dyno it again.
any suggestion?

[AndreyB]

I am opening your .msl file and looking at "err: last" - it's always 6050.

If you open the error codes file you will see http://rusefi.com/wiki/index.php?title=Manual:Error_codes
CUSTOM_TOO_LONG_FUEL_INJECTION = 6050.

So let's look at fuel parameters individually. If you go over all individual "fuel:" values you will quickly find that "fuel: load extra" always happens at the same time with the error.

"fuel: load extra" is about engine load acceleration enrichment which is a feature in need of some modifications. For now please disable engine load-based acceleration by setting multiplier to zero.

[matt]

i can feel good rpm pull to 7000, but 6050 error is still there.

rusefi.png (101.28 KiB) Viewed 25408 times