Ci Engine model connections

Im modeling a Ci engine using powertrain blocksted,i find myself connecting the signals, but i have a few ones i dont know how to connect or how they work even thougth i have read all block info . The goal of this proyect it to succesfully control a ci engine model of a real one, of wicht we have the fuel map info and geometry.

Here is a picture of my model:

And here is the signal example im using, that comes from the Ci controler help page:

• The first question is, where is the signal for the VGTpos, i didnt find it in the bus info of the turbine, and i guess i have to connect it to the ECU as am doing with the others. Can it refers to the driveshaftpower or one of those?.

• How should i controll the waste gate, if the controller does not have any signals to it?
• Im using the insructions of the CI controller for connecting everything but i dont know how to connect the PWinj,Fuelmainsoi (they are scalars) with the fuel mass(vector), SOI(vector), and fuel pressure(scalar) of the core engine. Arent they controlled by the controller? if not,How can i implemment the vectors, by a table, a funtion or anythings else?
• The torque command is the one i specfy? If so, what shoud I do, do i create a Load variable (accelerator) and connect it there?

Im currently experimenting with the model, as i am trying to recreate a real 2.2l hdi psa engine with 136cv.

Answer 1

[Peter]

Hi Antonio-

First, I'd like to suggest that you take a look at our existing CI Engine model as it is used in our CI Dynamometer Reference Application so you can see how we have already connected the turbo VGT and fuel delivery. You can start up the CI Dynamometer using this command:

>> autoblkCIDynamometerStart

You can see below the parts of the CI Dynamometer Reference Application to review and understand how to connect up a CI Engine to the controller.

As an alternative to creating a new engine from scratch block-by-block and parameter-by-parameter to match your PSA engine, you could try our CI Engine Re-size tool (also shown below) that may get you close enough to the performance characteristics of your PSA engine without having to change each and every parameter to match the power and architecture of the engine.

Thank you,

Pete