Guys posting questions>POST IN FREEGIN DETAIL
09-29-2007, 08:57 AM
#1
Guys posting questions>POST IN FREEGIN DETAIL Guys, theres plenty of help here to be had. Some really bright tuners offering free help. Cant ask for more than that.
But, you HAVE TO POST SOME DETAILS!! EVERYONE!!
Not stuff like "it feels doggy" or "it runs like ****" or "it goes rich"
We want stuff like numbers, A/F ratios, tunes posted, data logs posted. Stuff like that.
All the help you could ever want or need is hangin out on this board. Do all of us/them a favor and help out by giving as much detailed information as possible.
Thanks
Ed
But, you HAVE TO POST SOME DETAILS!! EVERYONE!!
Not stuff like "it feels doggy" or "it runs like ****" or "it goes rich"
We want stuff like numbers, A/F ratios, tunes posted, data logs posted. Stuff like that.
All the help you could ever want or need is hangin out on this board. Do all of us/them a favor and help out by giving as much detailed information as possible.
Thanks
Ed
09-29-2007, 10:23 AM
#2
1. use meaningful titles; titles likes 'i have a question' or 'help me' or 'newb here' or 'tuning issue' are worthless. you're already in a tuning section, so we already know you're asking a question about a tuning issue. 'rich idle regardless of VE value' or 'day to night differences in AFR' make it clear and easy to search.
2. if you find a similar issue already discussed, add to the old thread, do not start a new one. for example: SD vs MAF is discussed in like 10 good threads, they should've been combined, as a lot of info repeats itself which makes it boring to read.
3. link info, do not duplicate info. if you find something good elsewhere, place a link to it, not a copy. this way we can find a thread we haven't seen before, or get more contextual information. google works off links--if you have few different threads point to the same thread, it means it's probably some good info, so it should be marked as such. help google do their job, as it will pay off by returning more quality information
4. spelling and acronyms--tech boards are notorious for this; we overdo techno-babble and slang, making it impossible to search on. remember that two and three letter acronyms are not searchable through most search engines. all the usual slang and plain old bad spelling make it worse (they're/their, through/threw, etc...)
5. tuning is very scientific, so talk like a scientist if you want good answers. state your assumptions. post your units explicitly, don't assume everyone runs default scanner setups. if you use a custom PID, post a formula for it.
6. pictures are worth a 1000 words. in our case, a chart of a histogram can be worth thousands of samples. posting logs is even better, because i can look at it the same data differently and maybe spot the problem. however, if you're posting a log with a specific event you find suspicious, post a frame number around where it happens.
7. post additional info, not everything is stored in logs. if you live at 5000' the logs are gonna look goofy to someone used to sea level data. things like fog, extreme temperatures, driving in hills will all throw the data off and until you post it, people looking at it will be seriously confused. also, post which modes the logs were taken in--you can still log things like MAF flow and MAF frequency in SD mode, so just looking at the logs is not enough.
8. when posting multiple logs/tunes, name them in such a way that we can figure out which log came from which tune. i like to do Tune001.hpt and then have Log001a, Log001b... sort of naming scheme. it really helps to keep track. 'mytune' and 'secondscan' don't mean much.
the general idea here is to keep the information in a form that search engines can deal with. we've built a goldmine of information here, but it's all going to be useless if you can't find the info you need. be precise and try to state things in a way the reader doesn't have to 'decypher' what you tried to convey.
2. if you find a similar issue already discussed, add to the old thread, do not start a new one. for example: SD vs MAF is discussed in like 10 good threads, they should've been combined, as a lot of info repeats itself which makes it boring to read.
3. link info, do not duplicate info. if you find something good elsewhere, place a link to it, not a copy. this way we can find a thread we haven't seen before, or get more contextual information. google works off links--if you have few different threads point to the same thread, it means it's probably some good info, so it should be marked as such. help google do their job, as it will pay off by returning more quality information
4. spelling and acronyms--tech boards are notorious for this; we overdo techno-babble and slang, making it impossible to search on. remember that two and three letter acronyms are not searchable through most search engines. all the usual slang and plain old bad spelling make it worse (they're/their, through/threw, etc...)
5. tuning is very scientific, so talk like a scientist if you want good answers. state your assumptions. post your units explicitly, don't assume everyone runs default scanner setups. if you use a custom PID, post a formula for it.
6. pictures are worth a 1000 words. in our case, a chart of a histogram can be worth thousands of samples. posting logs is even better, because i can look at it the same data differently and maybe spot the problem. however, if you're posting a log with a specific event you find suspicious, post a frame number around where it happens.
7. post additional info, not everything is stored in logs. if you live at 5000' the logs are gonna look goofy to someone used to sea level data. things like fog, extreme temperatures, driving in hills will all throw the data off and until you post it, people looking at it will be seriously confused. also, post which modes the logs were taken in--you can still log things like MAF flow and MAF frequency in SD mode, so just looking at the logs is not enough.
8. when posting multiple logs/tunes, name them in such a way that we can figure out which log came from which tune. i like to do Tune001.hpt and then have Log001a, Log001b... sort of naming scheme. it really helps to keep track. 'mytune' and 'secondscan' don't mean much.
the general idea here is to keep the information in a form that search engines can deal with. we've built a goldmine of information here, but it's all going to be useless if you can't find the info you need. be precise and try to state things in a way the reader doesn't have to 'decypher' what you tried to convey.
