Question about PE mode and delay
Question about PE mode and delay
Using TunerCat for my 16147060 ECM using the $85 def file. My truck program has a WOT delay setting which I think is the same PE mode delay in the $42 def file the comes with TunerCat. While the ABUL bin file (using the $42 def) PE delay is set to 5 seconds by default, mine is 110 seconds by default.
Okay, so I look at my DataMaster scan and see that the bit for what DataMaster calls Acell Enrichment changes from 0 to 1 saying that I have entered what I assume is WOT or PE mode. I assume this means that I'm in PE mode, correct? All the requirements for PE (MAP, TPS%, RPM, etc) have been met. However, when I look at the spark advance, it does not match what I thought PE mode advance should be. Maybe because the 110 sec has not elapsed? Does this mean that, although my Acell Enrichment bit is on, I don't actually enter PE until I'm in that mode for 110 seconds? If so, that's like having to be on the gas for almost two minutes.
I plan on setting my WOT delay to something less than 5 seconds and also changing the RPM threshold where the delay is bypassed. Right now, I have to be over 4250 RPM in order to bypass the delay. Something I don't normally do with a truck engine designed for low RPM torque.
Okay, so I look at my DataMaster scan and see that the bit for what DataMaster calls Acell Enrichment changes from 0 to 1 saying that I have entered what I assume is WOT or PE mode. I assume this means that I'm in PE mode, correct? All the requirements for PE (MAP, TPS%, RPM, etc) have been met. However, when I look at the spark advance, it does not match what I thought PE mode advance should be. Maybe because the 110 sec has not elapsed? Does this mean that, although my Acell Enrichment bit is on, I don't actually enter PE until I'm in that mode for 110 seconds? If so, that's like having to be on the gas for almost two minutes.
I plan on setting my WOT delay to something less than 5 seconds and also changing the RPM threshold where the delay is bypassed. Right now, I have to be over 4250 RPM in order to bypass the delay. Something I don't normally do with a truck engine designed for low RPM torque.
I am not sure if this helps but sometimes in the code, numbers must be converted. Ie, your "110" number may translate into 5 seconds, or some other lower number... Ie, it (110) may be divided by 20 to get the conversion into seconds...
EDIT: From the ASDZ hack, it looks like the value in the PROM is "seconds * 20", so I guess the appropriate wording is multiply seconds desired by 20 and put that number in the PROM, not divide the PROM number by 20...
[This message has been edited by fast_broker (edited October 15, 2001).]
EDIT: From the ASDZ hack, it looks like the value in the PROM is "seconds * 20", so I guess the appropriate wording is multiply seconds desired by 20 and put that number in the PROM, not divide the PROM number by 20...
[This message has been edited by fast_broker (edited October 15, 2001).]
<font face="Verdana, Arial" size="2">Originally posted by fast_broker:
I am not sure if this helps but sometimes in the code, numbers must be converted. Ie, your "110" number may translate into 5 seconds, or some other lower number... Ie, it (110) may be divided by 20 to get the conversion into seconds...
EDIT: From the ASDZ hack, it looks like the value in the PROM is "seconds * 20", so I guess the appropriate wording is multiply seconds desired by 20 and put that number in the PROM, not divide the PROM number by 20...
[This message has been edited by fast_broker (edited October 15, 2001).]</font>
I am not sure if this helps but sometimes in the code, numbers must be converted. Ie, your "110" number may translate into 5 seconds, or some other lower number... Ie, it (110) may be divided by 20 to get the conversion into seconds...
EDIT: From the ASDZ hack, it looks like the value in the PROM is "seconds * 20", so I guess the appropriate wording is multiply seconds desired by 20 and put that number in the PROM, not divide the PROM number by 20...
[This message has been edited by fast_broker (edited October 15, 2001).]</font>
Thanks for the reply. I also thought the 110 seconds was a loooong time. I'm using TunerCat and I might ask them to double check to make sure that is correct.
In my scans I have never seen the spark advance that PE mode calls for. As a test, I think I'll reduce the delay from 110 seconds to 0 seconds and see if I get the PE advance when I meet all the PE perameters.
Heck, even 5 seconds is a long time when compared to "0" in a carb...
Exactly what is delayed for 5 seconds??? Fuel AND spark or just one of the parameters??? I may want to change that, too...
Exactly what is delayed for 5 seconds??? Fuel AND spark or just one of the parameters??? I may want to change that, too...
<font face="Verdana, Arial" size="2">Originally posted by fast_broker:
Heck, even 5 seconds is a long time when compared to "0" in a carb...
Exactly what is delayed for 5 seconds??? Fuel AND spark or just one of the parameters??? I may want to change that, too...</font>
Heck, even 5 seconds is a long time when compared to "0" in a carb...
Exactly what is delayed for 5 seconds??? Fuel AND spark or just one of the parameters??? I may want to change that, too...</font>
I think this only applies to truck ECM's. My truck was meant for heavy towing and hauling (over 8500 GVWR) so that's apparently why they delay WOT. I guess to keep you from tearing something up by flooring it when your towing a 18,000 lb cattle trailer. Since the truck is no longer towing trailers, I don't want this delay.
------------------
1991 Chevy C2500HD 5.7L HD. 16147060 ECM
Mods: Crane PowerMax 2030 cam 204I 214E @ .050 and 423I 446E lift, Jacobs Pro Street Ignition System. Using DataMaster and TunerCat with $85 ECM files.
Thread
Thread Starter
Forum
Replies
Last Post
dhonda200
Transmissions and Drivetrain
6
Aug 11, 2015 11:50 PM





