The amount of input/output afforded by the standard Enginuity models is not sufficient for my particular needs. Is there a way to change the I/O?
If a components-based engine model is used (as opposed to an s-function-based engine model) there is literally access to any engine signal anybody may want to analyze (down to the cylinder level). We recommend that components-based models are being used unless the user exactly knows that a s-function-based model is suitable for a particular application. Enginuity is an “open architecture” model. That is, one can make changes to the model configuration to fit any particular needs. For example, some customers may want to implement their own plant model features; or some customers may want to customize the top level model I/O interface and add appropriate port blocks to internal subsystems in order to feed local block signals (e.g., valve lift outputs of cylinder head models, etc.) all the way to the top model level (add signals to the I/O interface).
