Appendix B: Software Reference Manual
11.2
Building Application
Creating a new engine control strategy takes significant experience and knowledge. It is recommended
that you work with one of the demo applications to get a feel for a basic application using this software
before creating a new one. If you choose to work with a ground up application or a demo one, there are
several files that are intended for use: User Management.c, Engine Management.c, and Data
Management.c. Each file also has an associated header file. Additionally, each file is designed to contain
a single task that is periodically executed. These tasks are User Management(), Engine Management(),
and Data Management(). The file Tasks.h is used to determine when each of these application tasks are
called and should be modified by the user to customize the application. Tasks are broken out into 1.0 ms,
2.0 ms, 10 ms, 50 ms, and 100 ms function calls. The scheduler is very simple and the user must take
into account the real time aspects of making these function calls.
11.2.1 User Files
The software architecture allows the user to work with four C-code files to create a custom engine control
application, User Management, Data Management, Engine Management, and Application Maps. Each of
these files has a header file associated with it as well for declaring functions and making definitions
specific to the application. Each of these files, with the exception of the Applications Maps, has a specific
function call associated with it that is invoked by the task scheduler. The scheduling of these tasks can
be modified in the tasks.h file as discussed previously. The tasks.h file should include a function call to
each of the user functions: User_Management(), Data_Management(), and Engine_Management().
These user functions provide interaction with the low level driver functions necessary to control an
engine.
11.2.2 User_Management()
This function provides the interface between the engine user/operator and the engine control software.
The highest level of control is performed through this function. It must take the user inputs and turn them
into data for engine control as well as maintain basic operating conditions related to engine's current
operating point. For example, a fundamental user control is the throttle. User_Management() will take the
throttle position data and provide this data to the fuel and spark controllers so that the fuel and spark is
adjusted for the current throttle position. Another fundamental user control is the engine kill switch. The
ability of the user to shut off the engine at anytime must be maintained through the User_Management()
function.
Examples of a more complete User_Management() function is provided in the example application. This
examples use a state machine approach as running an engine has natural control states desired by most
users. When getting started, it may beneficial to keep it simple and have a minimal number of inputs. This
will allow the designer to get familiar with the entire software architecture before getting into a more
complex application.
11.2.3 Data_Management()
All inputs to the system are collected by the Data_Management() function. There are two exceptions.
Engine tooth/position data is handled specifically by the low level crank position functions. Also, the MAP
signal may be defined to be collected on a tooth basis, not a time basis, which is defined in the application
header file.
Digital and analog signals are collected and filtered by the Data_Management() task. Each signal must
be defined and configured in the application header file. The Data_Management() must then collect the
data and filter the data when buffers are full. The filtered data can then be used by User_Management().
Freescale Semiconductor
59
相关PDF资料
KIT33812EKEVBE BOARD EVALUATION FOR MC33812
KIT33879AEKEVBE BOARD EVALUATION FOR MC33879
KIT33880DWBEVB KIT EVAL FOR MC33880 8X SW W/SPI
KIT33886DHEVB KIT EVAL FOR MC33886 H-BRIDGE
KIT33887EKEVBE BOARD EVALUATION FOR MC33887
KIT33887PNBEVB KIT EVAL 33887 5A H-BRIDGE PQFN
KIT33905D5EKEVBE KIT EVALUATION FOR MC33905
KIT33912EVME KIT EVALUATION FOR MC33912
相关代理商/技术参数
KIT33812ECUEVME 制造商:Freescale Semiconductor 功能描述:Small Engine Control Reference Design
KIT33812EKEVBE 功能描述:电源管理IC开发工具 INTEGRATED DUAL LOW & HI RoHS:否 制造商:Maxim Integrated 产品:Evaluation Kits 类型:Battery Management 工具用于评估:MAX17710GB 输入电压: 输出电压:1.8 V
KIT33813AEEVBE 功能描述:电源管理IC开发工具 2 Cylinder Small Engine RoHS:否 制造商:Maxim Integrated 产品:Evaluation Kits 类型:Battery Management 工具用于评估:MAX17710GB 输入电压: 输出电压:1.8 V
KIT33814AEEVBE 功能描述:交换机 IC 开发工具 2 Cylinder Small Engine RoHS:否 制造商:Maxim Integrated 产品:Evaluation Kits 类型:USB Power Switches 工具用于评估:MAX4984E 工作电源电压:2.8 V to 5.5 V
KIT33816AEEVM 功能描述:电源管理IC开发工具 Engine Control Module RoHS:否 制造商:Freescale Semiconductor 产品: 类型: 工具用于评估: 输入电压: 输出电压:
KIT33879AEKEVBE 功能描述:电源管理IC开发工具 CONFIGURABLE OCTAL RoHS:否 制造商:Maxim Integrated 产品:Evaluation Kits 类型:Battery Management 工具用于评估:MAX17710GB 输入电压: 输出电压:1.8 V
KIT33880DWBEVB 功能描述:电源管理IC开发工具 33880DWB COSS KIT RoHS:否 制造商:Maxim Integrated 产品:Evaluation Kits 类型:Battery Management 工具用于评估:MAX17710GB 输入电压: 输出电压:1.8 V
KIT33883DWEVB 功能描述:KIT EVAL FOR MC33883 PRE-DRIVER RoHS:否 类别:编程器,开发系统 >> 过时/停产零件编号 系列:- 标准包装:1 系列:- 传感器类型:CMOS 成像,彩色(RGB) 传感范围:WVGA 接口:I²C 灵敏度:60 fps 电源电压:5.7 V ~ 6.3 V 嵌入式:否 已供物品:成像器板 已用 IC / 零件:KAC-00401 相关产品:4H2099-ND - SENSOR IMAGE WVGA COLOR 48-PQFP4H2094-ND - SENSOR IMAGE WVGA MONO 48-PQFP