Creek
Registered Member
Good deal! Now let's see if we can make use of the data. Check your Pms.
David
David
CK5
Register an account today to become a member! Once signed in, you'll be able to participate on this site by adding your own topics and posts, as well as connect with other members.
Aldl Woes (Problems Solved Discussion Continues)
- Thread starter Kiqman
- Start date
If you guys don't mind, translating the data from winALDL's output would be helpful for a lot of folks, (to my knowledge there isn't anything out there showing the spreadsheets, and what you are actually looking at) you should make it public! 
Kiqman
1/2 ton status
Sensor Data Excel Spreadsheet
Here's an example of a spreadsheet made up of the data from a trip down the freeway. I've only included the first bit of data but it goes on like this for pages. You can read down a column and see how the sensor readings changed as time progressed. You can also easily convert the column into a chart once your pasted into Excel.
Here's an example of a spreadsheet made up of the data from a trip down the freeway. I've only included the first bit of data but it goes on like this for pages. You can read down a column and see how the sensor readings changed as time progressed. You can also easily convert the column into a chart once your pasted into Excel.
Creek
Registered Member
Dorian,
Do your logs in sensor mode and save them along with the BLM tables and KNOCK (Spark) tables. Make sure you set up your TPS values in the WinALDL configuration. I'm a little busy right now trying to pay the mortgage and put the kid through college but when I have a little extra time, I'll try to address this. WinALDL is a great tool but it can only help you know what you need to do. To really tune your setup, you need to be able to make changes to your binary and burn eproms.
David
Do your logs in sensor mode and save them along with the BLM tables and KNOCK (Spark) tables. Make sure you set up your TPS values in the WinALDL configuration. I'm a little busy right now trying to pay the mortgage and put the kid through college but when I have a little extra time, I'll try to address this. WinALDL is a great tool but it can only help you know what you need to do. To really tune your setup, you need to be able to make changes to your binary and burn eproms.
David
I've got all that down, but it looks like your experience and effort helping Kigman in PM's would be worthwhile to folks that aren't to that point yet, and don't quite understand what is going on.
I can tell by your other posts you know how a great deal about this, so if you are helping Kigman interpret his findings, I think that info would be well served to be here in the "public realm" which would save time in the future from explaining.
It comes up a fair amount, and more people are getting on board with datalogging and burning, but there is still mystery as to how to interpret the data. To my knowledge there isn't much in the way of fairly easy to understand information as to what someone is looking at in a log if say, in one Excel spreadsheet row the BLM is 140 at 25% throttle, etc. and what would need done to correct any issues.
Kigman's post where you next offered to help: "Now the question is what do I do with all this data. For instance...I've been wondering if my coolant temp sensor is working properly, when I logged 10 minutes of data, if I'm reading this right, my CTS reading repeatedly climbs to over 200* and then drops back down to 5* and starts the climb all over again. I think I'm reading this right so me thinks it's time for a new CTS. I heard I can e-mail my data to someone that can translate? Anyone know what "DRP Occured" means or "Old High Gear" flag?" Is a prime example. People finally get around to logging, then get a mass of data that seems overwhelming to understand.
You can get all the info on thirdgen.org if you really search, but it is for the most part fragmented and as I've seen, nothing showing "log A", and then the description or interpretation of said log A.
Make sense? I just think a fair amount of people would be helped by seeing the log you guys are working with, and how you go about figuring out the problems or understanding what's hapening with the system.
I can tell by your other posts you know how a great deal about this, so if you are helping Kigman interpret his findings, I think that info would be well served to be here in the "public realm" which would save time in the future from explaining.
It comes up a fair amount, and more people are getting on board with datalogging and burning, but there is still mystery as to how to interpret the data. To my knowledge there isn't much in the way of fairly easy to understand information as to what someone is looking at in a log if say, in one Excel spreadsheet row the BLM is 140 at 25% throttle, etc. and what would need done to correct any issues.
Kigman's post where you next offered to help: "Now the question is what do I do with all this data. For instance...I've been wondering if my coolant temp sensor is working properly, when I logged 10 minutes of data, if I'm reading this right, my CTS reading repeatedly climbs to over 200* and then drops back down to 5* and starts the climb all over again. I think I'm reading this right so me thinks it's time for a new CTS. I heard I can e-mail my data to someone that can translate? Anyone know what "DRP Occured" means or "Old High Gear" flag?" Is a prime example. People finally get around to logging, then get a mass of data that seems overwhelming to understand.
You can get all the info on thirdgen.org if you really search, but it is for the most part fragmented and as I've seen, nothing showing "log A", and then the description or interpretation of said log A.
Make sense? I just think a fair amount of people would be helped by seeing the log you guys are working with, and how you go about figuring out the problems or understanding what's hapening with the system.
