zenboy99
Founding Member
tweecer noob
- Thread starter broken_joke
- Start date
a50sn95
Founding Member
the cam i have to replace the tfs stg 1 is a xfi comp cam. the specs on that are 236/248 and 579/579 and 114 lsa if i rember correctly. they are kinda new but i'm gonna try it out maybe after i get a little more tweecing experience. to answer your question if it fits under a stock hood is, no. i really wish it did. i think it'll fit under a cobra r hood 1 1/2 cowl but not entire sure on this. it will depend on intake manifold.
this morning i drove the car about 40 miles and it feels real good. should i be cautious about going full throttle yet?
thanks for all the help!
this morning i drove the car about 40 miles and it feels real good. should i be cautious about going full throttle yet?
thanks for all the help!
broken_joke said:
E A has great help files and I would follow them to get started for sure
I have dialed in my 30lb inj's using three different tuning methods and the E A method was the most accurate. We are talking idle and C L here btw.
With every method I used, I got better results with the low slope at 1.1 to 1.2 times the amount of inj size and high slope close to the inj size.
You may find the following interesting reading
The same value for each slope, which the j4j1 is famous for, was due to quick and dirty tuning by a contractor outside of Ford. This is a story I have heard more than once. Slopes of equal value was supposed to take the breakpoint out of the tuning process.
Same slope values just never worked too well for my combo but ...... I do have a narrow lsa which I suspect has been the reason I've had to do several things differently from the main-stream of peeps.
The offsets can make a noticable difference when dialing in your inj's so don't forget to deal with them.
Lately there has been a good bit of talk about those offsets and I have given my findings along with others in detail on the support site.
Your battery voltage drifts WAY more than the average person suspects and that is all about what offsets are for.
You will use your K's to track your progress as you most likely already know.
btw ... I got a tip or two about tuning on my site that may help you
Good to see you're making headway
Grady
i'll probably try that in a few min going back to the 1.2 X slope and see how it runs.
i will definetly check out your site grady.
again thanks!
i will definetly check out your site grady.
again thanks!
i think i am ready to mess with the base spark table. just one question about how i should start tweaking on that. i read the write up by cmant and got some good info from that. looking at my datalog. the advance is maxed out at 40+ degrees the whole time till i am at wot then it is pegged at 26 degrees. i am guessing things need to be somewhat opposite of that. so i imagine this needs attention.when looking at the table on the load side of the graph reads a 2 in the corner then straight down there is .7999 to .049988. which number is the higher load? i am guessing it .7999 but i have been wrong before!
thanks!
thanks!
I understand you want to start tuning to make improvments
but
You will have a better understanding of what is really going on if you put aside tuning changes for a while and get grounded on how things work.
Unless you have a basic understanding of how this stuff works, you'll be dependent on others and that will defeat your whole purpose of getting involved in self tuning.
What I did that helped me a lot was drive around while d logging and see how the load changed during those different driving conditions.
Same kind of deal for spark, fuel, and anything else you want to know about.
Thats whats so great about the Tweecer ......
YOU CAN SEE DATA IN REALTIME!
Use that ability to teach your self.
Hard data don't lie ...... you can trust it!
See where I'm goin here?
It is basiclly a two step process!
1) Research your topic - search faqs & threads
2) Confirm your research by using d logging
To sum it up ..............
How can one possibly make changes to improve a thing if ..........
One does not understand how that thing works in the first place?
Grady
but
You will have a better understanding of what is really going on if you put aside tuning changes for a while and get grounded on how things work.
Unless you have a basic understanding of how this stuff works, you'll be dependent on others and that will defeat your whole purpose of getting involved in self tuning.
What I did that helped me a lot was drive around while d logging and see how the load changed during those different driving conditions.
Same kind of deal for spark, fuel, and anything else you want to know about.
Thats whats so great about the Tweecer ......
YOU CAN SEE DATA IN REALTIME!
Use that ability to teach your self.
Hard data don't lie ...... you can trust it!
See where I'm goin here?
It is basiclly a two step process!
1) Research your topic - search faqs & threads
2) Confirm your research by using d logging
To sum it up ..............
How can one possibly make changes to improve a thing if ..........
One does not understand how that thing works in the first place?
Grady
thanks grady
i should have done a little more research when i wrote that. after i wrote that i looked at the tweecer defs spreadsheet and looked at the example for the base table. i inputted that and tweaked a little on that. i took it for a ride and woow! what a difference taking some advance out of the low loads and placing in the higher loads! it smoothed out alot on the low loads and drastically improved the high loads! what you were saying about the seeing real time is kinda what i was doing but was just a little unsure at first.i am learning alot from the forums and threads and it is as valuable a tool as the datalog in my opinion. hey thanks for all the help! 
i should have done a little more research when i wrote that. after i wrote that i looked at the tweecer defs spreadsheet and looked at the example for the base table. i inputted that and tweaked a little on that. i took it for a ride and woow! what a difference taking some advance out of the low loads and placing in the higher loads! it smoothed out alot on the low loads and drastically improved the high loads! what you were saying about the seeing real time is kinda what i was doing but was just a little unsure at first.i am learning alot from the forums and threads and it is as valuable a tool as the datalog in my opinion. hey thanks for all the help!
broken_joke said:thanks grady
i should have done a little more research when i wrote that. after i wrote that i looked at the tweecer defs spreadsheet and looked at the example for the base table. i inputted that and tweaked a little on that. i took it for a ride and woow! what a difference taking some advance out of the low loads and placing in the higher loads! it smoothed out alot on the low loads and drastically improved the high loads! what you were saying about the seeing real time is kinda what i was doing but was just a little unsure at first.i am learning alot from the forums and threads and it is as valuable a tool as the datalog in my opinion. hey thanks for all the help!
Thats great
It does take a while to get an idea of what you can do with all that data or what it might be telling you
Looks like you are getting into the swing of things
btw ... 30 second search right here on our own little forum :SNSign: turned up these threads that may help you with your topic of intrest.
http://forums.stangnet.com/showthread.php?t=492446&highlight=mbt
http://forums.stangnet.com/showthread.php?t=491446&highlight=mbt
http://forums.stangnet.com/showthread.php?t=485784&highlight=mbt
http://forums.stangnet.com/showthread.php?t=484207&highlight=mbt
http://forums.stangnet.com/showthread.php?t=482154&highlight=mbt
Grady
Similar threads
