reasons to not go into pe
04-01-2005, 11:02 PM
#1
TECH Enthusiast
Thread Starter
iTrader: (1)
Join Date: Mar 2003
Location: fresno, ca
Posts: 613
Likes: 0
Received 0 Likes
on
0 Posts
reasons to not go into pe Ok im trying to figure out why im running lean. im starting to belive its not going into PE. Now im wondering what are some things that will cause it not to go into PE. Also is 15 a PE cell i hear that it is just a heavy load cell but not necisarely PE.. here is where im at if anybody wants to read http://www.monodax.com/forums/showth...6&page=1&pp=10
04-04-2005, 04:32 PM
#4
TECH Enthusiast
Thread Starter
iTrader: (1)
Join Date: Mar 2003
Location: fresno, ca
Posts: 613
Likes: 0
Received 0 Likes
on
0 Posts
Originally Posted by Black02SS
Do you have COT enabled or disabled? What program are you using to do your tune? If it is HPT, can you post it up?
04-04-2005, 05:18 PM
#5
TECH Fanatic
iTrader: (4)
Join Date: May 2002
Location: Fairview Heights Illinois
Posts: 1,851
Likes: 0
Received 0 Likes
on
0 Posts
Originally Posted by rcfast
Ok im trying to figure out why im running lean. im starting to belive its not going into PE. Now im wondering what are some things that will cause it not to go into PE. Also is 15 a PE cell i hear that it is just a heavy load cell but not necisarely PE.. here is where im at if anybody wants to read http://www.monodax.com/forums/showth...6&page=1&pp=10
04-04-2005, 05:41 PM
#6
TECH Enthusiast
Thread Starter
iTrader: (1)
Join Date: Mar 2003
Location: fresno, ca
Posts: 613
Likes: 0
Received 0 Likes
on
0 Posts
Originally Posted by white2001s10
You're not running through catalytic converters are you?
Trending Topics
04-05-2005, 04:24 AM
#8
TECH Enthusiast
Thread Starter
iTrader: (1)
Join Date: Mar 2003
Location: fresno, ca
Posts: 613
Likes: 0
Received 0 Likes
on
0 Posts
my buddy who was watching the tech 2 a couple months ago (was still having the same problem then) said that the a/f on the screen was 13.0 which would be the commanded. I tried logging what it was commanding again tonight to see but im using autotap and for some reason when i did a software upgrade it won't let me use that parameter anymore
04-05-2005, 09:15 AM
#9
Moderator
iTrader: (11)
Join Date: Mar 2002
Location: East Central Florida
Posts: 12,605
Likes: 0
Received 6 Likes
on
6 Posts
You should be able to log the fuel air multiplier
since that's more of a "native" param, used
directly. 1.000 will be your closed loop target,
1.250 is stock PE table value (11.7:1 commanded
AFR), 1.13 is stock Open Loop Fuel Air table which
would be PE disabled, open loop, high MAP (about
13.0:1 target). If you catch the fuel air multiplier
PID and back-reference the tables you can deduce
what mode it's been in.
since that's more of a "native" param, used
directly. 1.000 will be your closed loop target,
1.250 is stock PE table value (11.7:1 commanded
AFR), 1.13 is stock Open Loop Fuel Air table which
would be PE disabled, open loop, high MAP (about
13.0:1 target). If you catch the fuel air multiplier
PID and back-reference the tables you can deduce
what mode it's been in.
04-05-2005, 11:54 PM
#10
TECH Enthusiast
Thread Starter
iTrader: (1)
Join Date: Mar 2003
Location: fresno, ca
Posts: 613
Likes: 0
Received 0 Likes
on
0 Posts
Originally Posted by jimmyblue
You should be able to log the fuel air multiplier
since that's more of a "native" param, used
directly. 1.000 will be your closed loop target,
1.250 is stock PE table value (11.7:1 commanded
AFR), 1.13 is stock Open Loop Fuel Air table which
would be PE disabled, open loop, high MAP (about
13.0:1 target). If you catch the fuel air multiplier
PID and back-reference the tables you can deduce
what mode it's been in.
since that's more of a "native" param, used
directly. 1.000 will be your closed loop target,
1.250 is stock PE table value (11.7:1 commanded
AFR), 1.13 is stock Open Loop Fuel Air table which
would be PE disabled, open loop, high MAP (about
13.0:1 target). If you catch the fuel air multiplier
PID and back-reference the tables you can deduce
what mode it's been in.
http://67.181.237.183/calfiles/screenshot/450522.csv