Power FC Warning for Datalogit Users
06-01-03, 11:01 PM
#1
Weird Cat Man
Thread Starter
Warning for Datalogit Users
To make a long story short...
Today somehow while out working on stuff with the PFC and Datalogit, the default.dat base map got written over my single turbo map that I've spent 3 months on.
I didn't know and I went to hit the gas and instead got what felt like fuel cut around 4000 rpm. Sharp cut in power, popping out of the exhaust (not apex seal popping), and sputtering.
I pulled over, found out the problem, and reloaded my map from yesterday. Car seems to be fine luckily.
I think what happened is that I was working on some of the "SETTINGS" pages and I somehow clicked FILE -> DEFAULT without realizing it and then modified the SETTINGS page I was working on and then did a "write all" and now I had the default.dat base maps, ignition maps... etc. Did I mention that I hate those "trackpoint" things on laptops!? They are hard to control sometimes!
The tip for the day... rename your default.dat file to any other name so the Datalogit can't find it. If I had done this, when I clicked FILE -> DEFAULT it would have loaded up a mostly all blanks file including blanks on all the SETTINGS pages and I would have noticed that something was very wrong and not screwed it up.
The second tip for the day... always do a "read all" after you do a "write" operation and check ALL the pages at least glancing at each one to make sure they look like the right information.
This could have been a blown motor today but I think the only thing that saved it is that my single turbo is mapped with 30-50% more fuel than the default maps are... so when I hit those areas, it basically acted like fuel cut. Either that or the PFC boost control system cut the fuel when it tried to control non-existant twin turbo parts or maybe when the boost went too high... I'm not sure what... but whatever it was I got lucky today
Knock on wood!
Save your money, learn from my mistakes
Brian
Today somehow while out working on stuff with the PFC and Datalogit, the default.dat base map got written over my single turbo map that I've spent 3 months on.
I didn't know and I went to hit the gas and instead got what felt like fuel cut around 4000 rpm. Sharp cut in power, popping out of the exhaust (not apex seal popping), and sputtering.
I pulled over, found out the problem, and reloaded my map from yesterday. Car seems to be fine luckily.
I think what happened is that I was working on some of the "SETTINGS" pages and I somehow clicked FILE -> DEFAULT without realizing it and then modified the SETTINGS page I was working on and then did a "write all" and now I had the default.dat base maps, ignition maps... etc. Did I mention that I hate those "trackpoint" things on laptops!? They are hard to control sometimes!
The tip for the day... rename your default.dat file to any other name so the Datalogit can't find it. If I had done this, when I clicked FILE -> DEFAULT it would have loaded up a mostly all blanks file including blanks on all the SETTINGS pages and I would have noticed that something was very wrong and not screwed it up.
The second tip for the day... always do a "read all" after you do a "write" operation and check ALL the pages at least glancing at each one to make sure they look like the right information.
This could have been a blown motor today but I think the only thing that saved it is that my single turbo is mapped with 30-50% more fuel than the default maps are... so when I hit those areas, it basically acted like fuel cut. Either that or the PFC boost control system cut the fuel when it tried to control non-existant twin turbo parts or maybe when the boost went too high... I'm not sure what... but whatever it was I got lucky today
Knock on wood!Save your money, learn from my mistakes
Brian
Last edited by Wargasm; 06-01-03 at 11:03 PM.
06-03-03, 09:26 PM
#2
Eye In The Sky
iTrader: (2)
Join Date: Feb 2001
Location: In A Disfunctional World
Posts: 7,895
Likes: 0
Received 114 Likes
on
66 Posts
The SAFE procedure is to:
(1) start up the laptop and FCEDIT.
(2) turn on the ignition.
(3) read all from PFC and save it. old version in case you need it.
(4) read new dat into FCEDIT.
(5) write all to PFC.
(6) turn off ignition.
(7) turn ignition back on.
(8) read all from PFC again and compare it to the new dat that is in the laptop. There should be not differences.
Remember Murphy's law, that is why you have to be better than the average bear as Yogi would say!
(1) start up the laptop and FCEDIT.
(2) turn on the ignition.
(3) read all from PFC and save it. old version in case you need it.
(4) read new dat into FCEDIT.
(5) write all to PFC.
(6) turn off ignition.
(7) turn ignition back on.
(8) read all from PFC again and compare it to the new dat that is in the laptop. There should be not differences.
Remember Murphy's law, that is why you have to be better than the average bear as Yogi would say!
Last edited by cewrx7r1; 06-03-03 at 09:28 PM.
06-05-03, 10:00 AM
#3
Senior Member
iTrader: (1)
Join Date: Feb 2001
Location: Charleston, WV
Posts: 610
Likes: 0
Received 0 Likes
on
0 Posts
Brian,
If your normal maps are running 30-50% richer than the base maps, fuel must be pouring out of your exhaust like a freakin' fire hose! I'm thinkin you probably hit the overboost fuel cut, but who knows.
Good suggestion, sounds like it could be an easy mistake.
Wade
If your normal maps are running 30-50% richer than the base maps, fuel must be pouring out of your exhaust like a freakin' fire hose!
I'm thinkin you probably hit the overboost fuel cut, but who knows.Good suggestion, sounds like it could be an easy mistake.
Wade
06-05-03, 05:17 PM
#4
I have more fun than you.
Join Date: May 2002
Location: Sand Key/Clearwater Beach, Florida
Posts: 1,078
Likes: 0
Received 0 Likes
on
0 Posts
been there myself. I thought I had royally screwed something until I pulled over and realized I had some default map. Very very scary. Since then I do exactly the steps suggested by cewrx7r1.
My car was bucking, back firing, stinking, etc. I thought it was a goner...
My car was bucking, back firing, stinking, etc. I thought it was a goner...
06-05-03, 08:34 PM
#5
Weird Cat Man
Thread Starter
I just checked my compression today with a "real" tester (I own one ) and it's the same as in April and last August, so it's all good PHEW.
Brian
) and it's the same as in April and last August, so it's all good PHEW.Brian
Thread
Thread Starter
Forum
Replies
Last Post
The1Sun
1st Generation Specific (1979-1985)
7
09-18-15 07:13 PM