- 您现在的位置：买卖IC网 > Sheet目录1223 > KIT33812ECUEVME (Freescale Semiconductor)KIT DESIGN FOR 33812/S12P
Application Overview
In the application state machine, clear areas are defined to implement engine strategy. A simple example
is provided based on using an Alpha N engine control strategy. The software is not intended to show an
optimized strategy, however it is designed to provide a starting point for development of an engine
management application that is modular and can be successful in running an engine. Thorough
understanding and optimization are required when applying this software to any engine application.
Updating Low Level Code
There are no committed support plans for the example application software. It is recommended to
continue the customizing of the software down to the lowest level if it is to be used beyond a
demonstration purpose. This would include correction of errors for compilations and operation as well as
application hardening of software both at the application level and microcontroller level. In event of a
significant low level driver update or third party software addition, low level code can be updated in two
different ways.
Method 1: Using the new software project containing the new low level driver code, copy in the contents
of the user functions. These include User_Management(), Engine_Management(), Data_Management(),
and Application Map data. Include any custom definitions in the header files as well.
Method 2: Import new driver files on an individual basis. For specific file updates, copy and overwrite the
specific file and header file of interest into the project directory folder structure. Be sure to do a clean build
by removing all object code as well as back up the project before overwriting files. Additional
dependencies may need to be considered as new code could make use of other new code not found in
the replaced file.
6.1
28
Application Testing
Before going to a real system with your application, extensive testing is recommended to ensure that any
engine control signals, specifically fuel and spark, meet your timing requirements and the application
provides the desired high level operation and user control. This is best achieved with the simulated
system set up previously. Once the application is validated at the bench level, it may be necessary to
reduce system functionality and test basic operation when migrating to real engine hardware. Data
collection, load control, and system start/stop conditions can be easily tested without the engine running.
Additional testing can be performed with fuel and spark controls physically disabled which provides an
opportunity for analysis of the rotating engine with no combustion events. Control signals for fuel and
spark can then be verified using the actual loads in preparation for calibration of engine control
parameters.
Testing the application can be done in real-time using the Hi-wave debugger built into the CodeWarrior
IDE. This tool allows non-intrusive debugging through the microcontroller ’s BDM pin while the processor
is running. Using the Hi wave debugger will allow you to set breakpoints, step though code, view and
modify software variables, and directly control the registers of the S12X microcontroller. Assistance
learning the debugger can be found in the Virtual Lab mentioned in previous sections. Through the use
of calibration variables that are able to be modified using the debugger, testing can be performed to find
working values for system control parameters.
One of the most difficult aspects to master is the angle based operation of the engine. It may take many
iterations of software building and testing to get the timing right for the delivery of the fuel and spark
pulses. Some of this confusion may come from the generic implementation of the example application.
The crankshaft state machine that synchronizes to the rotation of the engine, through the teeth pulses on
the crankshaft, uses the missing tooth as the definition of top dead center or 0 degrees. The first tooth
after the missing tooth gap is then tooth 1. This is not always the case and an offset will need to be created
to compensate for specific engine implementation. In the example application, the missing tooth gap is
actually at bottom dead center. This creates an offset of 6 teeth (12 minus 1 wheel defined) that must be
Freescale Semiconductor
发布紧急采购，3分钟左右您将得到回复。
相关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