[rusEfi] Mitsubishi 4G63 and 4G92 (#6)

[AndreyB]

Great! I know what's going on.
You have "Alpha-N" selected as your fueling algorithm. Engine load 6 means 6% throttle position sensor, not 6 volts. You would need to edit the scale in Tuner Studio fuel table. You see how on the left it is now from 1.20 to 4.40? You need to edit this so it would be from 0 to 100

Say 0 8 16 24 ..... something something 100

[Tambralinga]

Have error message error fuelkeybin value 16 is too high must must be less than: 10

[AndreyB]

Please take latest rusefi.ini for the fuelkeybin fix, you would probably need latest firmware just to be sure.

[Tambralinga]

Today test can change value 0-100this ok, but TDC 17% TS move o-6 only not work.

Code: Select all

2014-09-05 14_57: EngineState: rpm=2270.00000 engineLoad=17.38317
2014-09-05 14_57: EngineState: baseFuel=3.00000
2014-09-05 14_57: EngineState: iatCorrection=1.00000 cltCorrection=1.00000 injectorLag=0.00000
2014-09-05 14_57: CommandQueue: got valid conf! fuelinfo
2014-09-05 14_57: EngineState: injection pulse width: 3.00000
2014-09-05 14_57: EngineState: WARNING: unrealistic IAT -273.14999

[AndreyB]

I think I have just fixed the issue where 0.6ms would become 6ms and 0.3ms would become 3ms - scale was off. You would need only rusefi.ini

Is this the issue you are having? Or is it something else?

[AndreyB]

Spark1 4.02 and 1.62ms It's normal, right?
I do not understand.

This is obviously not normal. Can you please post your most recent log file, I want to look if things look right.

[Tambralinga]

I think I have just fixed the issue where 0.6ms would become 6ms and 0.3ms would become 3ms - scale was off. You would need only rusefi.ini

Is this the issue you are having? Or is it something else?

My problem is TPS 17%, but it shows the horizontal position 6. Not the way to the top.
Have command for test spark?

[AndreyB]

TDC=TopDeadCenter. TPS=ThrottlePositionSensor. I think you mean TPS?

Now I understand, the blue dot is not where it should be. Give me a second to try something.

[AndreyB]

The bug was that fuel table was using MAF for y-axis, you can actually read MAF there. I've just fixed the rusefi.ini project file, it should now start showing 'engineLoad' on the left and engine load would be TPS if you are using Alpha-N. Thank you for you bug report and your patience in general

[Tambralinga]

TDC=TopDeadCenter. TPS=ThrottlePositionSensor. I think you mean TPS?

Now I understand, the blue dot is not where it should be. Give me a second to try something.

Sorry i meant the TPS

[AndreyB]

Are you online on skype?

Please tell me once you have a chance to try the new rusefi.ini, a couple of fresh pictures would help to understand the larger picture of what we are doing and where we are. Also want a log file to look into the 1.6ms spark issue

[Tambralinga]

New rusefi.ini available I will test it
If there are problems, I will send the results to you

[AndreyB]

the problem with 1.6ms dwell and 4ms dwell is still an open problem, the new rusefi.ini does not address it - that is the reason I am asking for a dev console log file

[Tambralinga]

the problem with 1.6ms dwell and 4ms dwell is still an open problem, the new rusefi.ini does not address it - that is the reason I am asking for a dev console log file

Hi rusEFI,

Let you see in the link below...
http://1drv.ms/WouTjX

Thanks.

[AndreyB]

Let you see in the link below...
http://1drv.ms/WouTjX

I've looked at the logs. The 1.6ms and 4ms ignition dwell is related to trigger event angles we have hard-coded for Mitsu. This trigger shape seems to be shared with mazda miata NA, Miata NA has more precise values defined.
Please try setting trigger to Miata NA and globaltriggeroffset to 114 and see if that would make ignition dwell better.
Like this:

[Tambralinga]

Let you see in the link below...
http://1drv.ms/WouTjX

I've looked at the logs. The 1.6ms and 4ms ignition dwell is related to trigger event angles we have hard-coded for Mitsu. This trigger shape seems to be shared with mazda miata NA, Miata NA has more precise values defined.
Please try setting trigger to Miata NA and globaltriggeroffset to 114 and see if that would make ignition dwell better.
Like this:
http://i.imgur.com/nbLsVuD.png

I set globaltriggeroffset to 114 spark1 ok but spark2 Crashes display 4.02 and 6.33.

[AndreyB]

Did you set trigger to Miata NA? Please give me a new log file

[Tambralinga]

Did you set trigger to Miata NA? Please give me a new log file

Test change Injector table not work.

[AndreyB]

Are you trying to set timing to 30 degree before top dead center?

Because the table does not control the dwell (signal LENGTH = currently 4ms) but it controls the signal POSITION (30 degrees)

Default 4ms and default zero timing should be good enough to start the car. I demand some pictures of your physical setup, I need to see what we are working on

[Tambralinga]

Are you trying to set timing to 30 degree before top dead center?

Because the table does not control the dwell (signal LENGTH = currently 4ms) but it controls the signal POSITION (30 degrees)

Default 4ms and default zero timing should be good enough to start the car. I demand some pictures of your physical setup, I need to see what we are working on

I just test functionality for you.

How much is reasonable for fuel e85?

[AndreyB]

Duration is controlled in this window
http://i.imgur.com/5TLBNV2.png

No idea on timing I know that on regular gasoline something between 10 degree before TDC and TDC is the base value

[Tambralinga]

Duration is controlled in this window
http://i.imgur.com/5TLBNV2.png

No idea on timing I know that on regular gasoline something between 10 degree before TDC and TDC is the base value

I will try to test it

[Tambralinga]

We can set the IDL ?

[AndreyB]

We can set the IDL ?

http://rusefi.com/wiki/index.php?title=Manual:Software:Idle_control

[Tambralinga]

Hi rusEFI,

How can I know he Ignition degree adjustment, if it working or not?
I mean the feedback from ignition working status or responsible.
Related in this image, below.


Thanks,
Mr.X

[AndreyB]

I cannot find the wiki page for the logic analyzer, I though there was one

Type 'triggerinfo' it would show you two logic input pins. Add a jumper wire from your spark out wires to the logic input wires. Once you do that, you should see the current advance value on 'advance0' and 'advance1' gauges

[Tambralinga]

Why advence0 in devconsole to show the value 0 at all times?



I just want to set ingnition degree and the values ​​that change only.

Code: Select all

2014-09-08 22_40: PortHolder: Sending [sec!11!triggerinfo]
2014-09-08 22_40: EngineState: confirmation_triggerinfo:11
2014-09-08 22_40: EngineState: trigger event counters 1292/1292/2585/2585
2014-09-08 22_40: EngineState: trigger type=3/need2ndChannel=1
2014-09-08 22_40: EngineState: expected duty #0=0.27900/#1=0.37200

It is a few ingnition degrees .

[AndreyB]

I have just renamed "Advance0" gauge to "Input Adv #1" since it's the advance of the INPUT pin, not the spark advance as controlled by the firmware. Which wire did you connect with which in order to feed spark signal into rusEfi input?

I will double-check the whole thing once I get home

[Tambralinga]

I have just renamed "Advance0" gauge to "Input Adv #1" since it's the advance of the INPUT pin, not the spark advance as controlled by the firmware. Which wire did you connect with which in order to feed spark signal into rusEfi input?

I will double-check the whole thing once I get home

ok


What are the steps to input pin.

[AndreyB]

What are the steps to input pin.

triggerinfo would probably confirm that your primary input is PA8 and secondary is NONE.

You would need a wire between your spark out signal and PA8, is your spark controlled by PE8 & PE10?

Another way to look at angles is on the digital chart tab, click PAUSE and move the mouse around the chart while looking at the message in the bottom-left corner of the screen.