MPC5634 eTPU synchronous exception

キャンセル
次の結果を表示 
表示  限定  | 次の代わりに検索 
もしかして: 

MPC5634 eTPU synchronous exception

982件の閲覧回数
Jasting
Contributor II

When I was conducting engine tests, I encountered an eTPU crankshaft tooth counting error that caused the engine to no longer synchronize.

When I check "*cpba_tooth_period_log" in “crank_instance_t",I foung some member become very small。

Jasting_0-1730678411092.png

 

The experimental results are as follows.While running, etpu_tooth_period_log[80] suddenly drops from 33800 to 21800.And crank states err occur.The rest of the etpu tooth period log(log[0],log[40],log[119],) data looks normal.

 

Jasting_1-1730678411079.png

 

I checked the input crankshaft original signal and there was no signal anomaly when the fault occurred.I tested the duration of the first 1 and 2 teeth of the failure,They all last around 820us.

Jasting_2-1730678411083.png

 

Here are some of my eTPU parameter matching values.

 

Jasting_3-1730678411054.png

 

Jasting_4-1730678411062.png

 

 

    I also added an IO flag to the crankshaft interrupt function, which outputs the current state of the IO output after entering the interrupt.In the figure below, the blue signal is a sign that the entry crankshaft is interrupted. 

    Green indicates synchronization. When the green signal is high power level, it indicates non-synchronization("crank_states.eng_pos_state" is not "FS_ETPU_ENG_POS_FULL_SYNC").

    As can be seen from the diagram, the crankshaft abnormal entry break caused the engine to no longer synchronize.

 

Jasting_5-1730678411123.png

 

Could you help me analyze the cause of this problem and how to solve it?

Thank you very much!

0 件の賞賛
返信
1 返信

890件の閲覧回数
MilanBrejl
NXP Employee
NXP Employee
0 件の賞賛
返信