J-series Acura/Honda

[Fred]

Default flat 60% VE and default Sean's lambda should do OK for you. Feel free to tweak the lambda table to suit your preferences. VE likely won't be far away from that figure, though. You'll need to give it some shape once it's running. Just setup the cylinder size, injector flow and scheduling and you should be good to go :-)

[Peter]

So I don't understand a few things in the code.

globalDefines.h got a #define PETERJSERIES

fuelAndIgnitionCalcs.c

Code: Select all

#elif PETERJSERIES
anglesOfTDC[0] =   0 * oneDegree;
anglesOfTDC[1] = 120 * oneDegree;
anglesOfTDC[2] = 240 * oneDegree;
anglesOfTDC[3] = 360 * oneDegree;
anglesOfTDC[4] = 480 * oneDegree;
anglesOfTDC[5] = 600 * oneDegree;
outputEventPinNumbers[0] = 0;
outputEventPinNumbers[1] = 0;
outputEventPinNumbers[2] = 0;
outputEventPinNumbers[3] = 0;
outputEventPinNumbers[4] = 0;
outputEventPinNumbers[5] = 0;
#define cliConfigredNumberOfIgnitionEvents 6
#define numberOfInjectionEvents 6
#define firstInjectionEvent 6
#define cliConfiguredOffset (0 * oneDegree)
#define numberOfInjectionsPerEngineCycle 2

//         Output Channel =    // Fuel Channel | Cylinders
outputEventPinNumbers[ 8] = 2; //      1       |  1 and 4
outputEventPinNumbers[ 9] = 3; //      2       |  2 and 5
outputEventPinNumbers[10] = 4; //      3       |  3 and 6
outputEventPinNumbers[11] = 2;
outputEventPinNumbers[12] = 3; 
outputEventPinNumbers[13] = 4; 
outputEventInputEventNumbers[ 8] =  1;
outputEventInputEventNumbers[ 9] =  3;
outputEventInputEventNumbers[10] =  5;
outputEventInputEventNumbers[11] =  7;
outputEventInputEventNumbers[12] =  9;
outputEventInputEventNumbers[13] = 11;

I have no idea what's going on with the outputEventInputEventNumbers stuff, and as you can see it's copied directly from SEANKLT1, so it's probably wrong.

FixedConfig1.c

Code: Select all

#elif PETERJSERIES
perCylinderVolume:  cylinderSize585,
injectorFlow:       injector440cc,

With the global defines to match.

FixedConfig2.c

Code: Select all

#elif PETERJSERIES
MAPMinimum:    HondaDenso183kPaMin,
MAPRange:      HondaDenso183kPaRange,	

Is that all I need to change?

[Fred]

globalDefines.h got a #define PETERJSERIES

You can drop that in on the command line too, look at the script in the bin dir with testCLIBuilds.bash or something for a name as an example.

OK, I looked at the config for a minute, started editing it in this post, then realised that we're an event short to manually configure these for semi sequential. That rewiring that you unnecessarily did screwed us. You need to make a choice:

1) One injection per cycle, timed the same on all cylinders, which results in uneven atomisation and therefore idle, among other things.
2) Three injections per cycle, in two sets of three cylinders (paired with wires or software), which results in cumulative dead time factor, which if setup/tuned wrong can give an uneven idle and make low load tuning more difficult.
3) Wait for me to move the fueling to proper scheduling like the ignition.
4) Butcher a change in to use the existing scheduling with PW instead of Dwell as the source and configure as though they were ignition channels.

4 will actually work pretty well :-) 1 and 2 won't be great, but 2 should be good if you set it up right. 3 could be a few weeks or more.

so it's probably wrong.

Don't feel bad, it wasn't possible to get it right.

Is that all I need to change?

No, you'll need to measure/research and setup your CHT and IAT sensors too, and your wideband if it's not the same as the default, which I forget.

These need to be right, but the defaults are likely close enough:

injectorDeadTimeTable
engineTempEnrichmentTablePercent

If you have the data to do better, go ahead.

Fred.

[Peter]

That rewiring that you unnecessarily did screwed us.

Re-rewired. Seems easier, and looks like it requires way less thinking. PT2 to Injector on Cylinder 1, T3 to I2, ..., T7 to I6. The firing order is 1-4-2-5-3-6.

[Fred]

How about I push a hacked version to a branch for you to try? I can bench test it here first, I guess. I have the equipment. I'm currently just beating my head against a wall with something else anyway. Might crank up the heater, fry up some food, and sit down and write make something for you to try :-)

Fred.

[Fred]

Two eggs, two sausages, a fair dose of virgin olive oil, and a decent big juicy orange. Time for some code :-)

[Fred]

Question, have you wired it:

PT2 -> Cylinder 1
PT3 -> Cylinder 2
PT4 -> Cylinder 3
PT5 -> Cylinder 4
PT6 -> Cylinder 5
PT7 -> Cylinder 6

Or in firing order order like this:

PT2 -> Cylinder 1
PT3 -> Cylinder 4
PT4 -> Cylinder 2
PT5 -> Cylinder 5
PT6 -> Cylinder 3
PT7 -> Cylinder 6

Either of them is fine, one might make more sense to you than the other.

Fred.

[Peter]

PT2 -> Cylinder 1
PT3 -> Cylinder 2
PT4 -> Cylinder 3
PT5 -> Cylinder 4
PT6 -> Cylinder 5
PT7 -> Cylinder 6

This one.

[Fred]

Success: http://stuff.fredcooke.com/ScheduledFue ... Change.png < half fuel, half ign. Will retest with legit config now and check out the trace :-)

EDIT: FreeEMS/MTX labels are old/wrong

[Peter]

So far the only thing I've came up with on the zero crossing point is that it might be hard to tell where the center of the tooth is if the tooth is fairly wide, because it will be around zero for a while. That's probably what causes the lessening of the slope around zero on the oscilloscope traces. So a leading or trailing might better. Since the starting and trailing edges aren't in the center of the tooth we need the event angle offset to account for that. If that isn't it I haven't come up with any other ideas yet.