|
nyet
|
 |
« Reply #60 on: May 29, 2016, 10:51:13 AM »
|
|
|
probably, i'll ask. but how do i add those ram locations to the logging program?
RAM locations are specified in the .ecu file generated by ME7Info, where else?  |
|
|
|
|
Logged
|
|
|
|
q_dubz
Full Member
Karma: +3/-0
 Offline
Posts: 154
|
|
« Reply #61 on: May 29, 2016, 10:52:31 AM »
|
|
|
RAM locations are specified in the .ecu file generated by ME7Info, where else? AH, DUH. so open in notepad and edit the bish.  |
|
|
|
|
Logged
|
|
|
|
|
Gonzo
|
|
« Reply #62 on: May 29, 2016, 11:02:10 AM »
|
|
|
The topic says, MAF reading normal and rising, but one of your other logs show the MAF dip. I was hoping OP would make a new thread since in the beginning there was 2 different issues to begin with and now that I'm in involved there is only one. So shouldn't your tuner be able to provide you at least a few RAM locations to help logging?
Kinda hoping this forum could help OP on that since I'm working pro bono on this. What should OP log? |
|
|
|
« Last Edit: May 29, 2016, 11:06:34 AM by Gonzo »
|
Logged
|
|
|
|
|
nyet
|
|
« Reply #63 on: May 29, 2016, 11:11:34 AM »
|
|
|
I was hoping OP would make a new thread since in the beginning there was 2 different issues to begin with and now that I'm in involved there is only one.
Ya, i think it is quite clearly slow path intervention via cutting load request. Kinda hoping this forum could help OP on that since I'm working pro bono on this. What should OP log?
The load request path, specifically. |
|
|
|
|
Logged
|
|
|
|
q_dubz
Full Member
Karma: +3/-0
Offline
Posts: 154
|
|
« Reply #64 on: May 31, 2016, 09:56:51 PM »
|
|
|
was digging thru the FR and found something but maybe it's nothing...
"At higher speeds it is possible that the available theoretical maximum injection time is not sufficient to obtain the required target torque. Therefore, an injection time timx_w that is larger than the maximum possible injection time timxth_w is deployed until the desired torque is withdrawn and timx_w is not larger than timxth_w. For this purpose, the control error dtimx_w is assigned to a PI controller. When the controller is active, the output controlled variable mitibgr_w represents the desired torque. When the controller is inactive, mitibgr_w receives the value 100%. The desired torque in %MDBGRG is obtained by initializing with mifab_w and mitibgr_w. In order to avoid jumps in the nominal torque, the integrator of the integral component is initialized with mifab_w."
MIFAB_W = Limited indexed driver-desired torque
|
|
|
|
|
Logged
|
|
|
|
q_dubz
Full Member
Karma: +3/-0
Offline
Posts: 154
|
|
« Reply #65 on: May 31, 2016, 10:06:43 PM »
|
|
|
Or is it possible it has to do with my ecu's version of "PS_W'?? Hitting a cap...?
|
|
|
|
|
Logged
|
|
|
|
q_dubz
Full Member
Karma: +3/-0
Offline
Posts: 154
|
|
« Reply #66 on: June 01, 2016, 03:15:31 PM »
|
|
|
Anyone?
|
|
|
|
|
Logged
|
|
|
|
|
nyet
|
|
« Reply #67 on: June 01, 2016, 03:16:37 PM »
|
|
|
Without logging the load request path, you're not going to find any answers...
Add a turbo to an NA ECU, you'd better have a full complement of tools at your fingertips, or forget it.
|
|
|
|
|
Logged
|
|
|
|
q_dubz
Full Member
Karma: +3/-0
Offline
Posts: 154
|
|
« Reply #68 on: June 01, 2016, 03:18:36 PM »
|
|
|
Without logging the load request path, you're not going to find any answers...
Add a turbo to an NA ECU, you'd better have a full complement of tools at your fingertips, or forget it.
which variable(s) cover the load request path exactly? |
|
|
|
|
Logged
|
|
|
|
|
nyet
|
|
« Reply #69 on: June 01, 2016, 03:19:39 PM »
|
|
|
which variable(s) cover the load request path exactly?
Backtrace rl_w in the FR. |
|
|
|
|
Logged
|
|
|
|
|
nyet
|
|
« Reply #70 on: June 01, 2016, 03:22:24 PM »
|
|
|
minimally: $ grep ^rl 8D0907551M.ecu | cut -f 1 -d ,
rl
rl_um
rl_w
rldkofk_w
rlmax_w
rlmx_w
rlmxko_w
rlroh_w
rlsol_w
rlzuhfs_w
|
|
|
|
|
Logged
|
|
|
|
q_dubz
Full Member
Karma: +3/-0
Offline
Posts: 154
|
|
« Reply #71 on: June 01, 2016, 03:22:58 PM »
|
|
|
Backtrace rl_w in the FR.
ok, cool I was digging thru the FR for hours last night, hence how I found that fuel injector time meeting target torque I posted about. |
|
|
|
|
Logged
|
|
|
|
|
nyet
|
|
« Reply #72 on: June 01, 2016, 03:25:31 PM »
|
|
|
err I mean rlsol_w (requested) not rl_w (actual)
|
|
|
|
|
Logged
|
|
|
|
q_dubz
Full Member
Karma: +3/-0
Offline
Posts: 154
|
|
« Reply #73 on: June 01, 2016, 10:13:50 PM »
|
|
|
minimally: $ grep ^rl 8D0907551M.ecu | cut -f 1 -d ,
rl
rl_um
rl_w
rldkofk_w
rlmax_w
rlmx_w
rlmxko_w
rlroh_w
rlsol_w
rlzuhfs_w
sadly i only have rl, rl_w, and rlsol_w in this wonderfully NA ME7.1.1 |
|
|
|
|
Logged
|
|
|
|
q_dubz
Full Member
Karma: +3/-0
Offline
Posts: 154
|
|
« Reply #74 on: June 05, 2016, 05:53:48 PM »
|
|
|
SOLVED! Finally finding an a2l really helps. |
|
|
|
|
Logged
|
|
|
|
|
