Hey fellas, been wanting to write up a little something about data logging to help some members get a better understanding about this.. Me and Randy have been data logging for a while now, and its been alot of fun and really helpful!
Data logging
What it is:
Data logging has been a normal practice for me for years, esp in my N54 335i days when I was modding and expanding tuning for Terry @ burger tuning, testing alpha and beta tunes.
Datalogging is important whether you are stock or modded. It gives you a great idea of how your car is running, if its running at its peak performance and gives you a great view of values that might surprise and interest you.. Feel like your car isnt feeling fast? Time for a datalog to check.. Numbers dont lie..
What to use to log:
First lets start with what to use to data log on these engines…
The easiest software/cable i found is the software and cable combo from BimmerSoftware.com | Welcome to BMWSW.com
You can also use Bavarian technic cable which is more expensive and complicated/advanced for logging but also comes with 3 vins, so it can be used on 3 cars.
Both will read fault codes as well.. But The BT software will also read errors in every module of the car.
What the data means:
Some of the most important values to log would be RPM, IGN, IAT’s B1/B2, lamba B1/B2, Fuel pressure, throttle, etc. the bmw logger data logs many many parameters by default so no worries.
RPM: self explanatory, you want this logged to show RPM’s.
IGN: This is an important value. Most data logging tools will usually only show 1 cylinder, but that’s acceptable data to give a general idea of how the engine is feeling. All cylinders IGN logging would be ideal!
Through the rev range, you don’t want to see your IGN take a dive, or have multiple drop outs ( sharp downward spikes), this would indicate pinging, misfire, detonation etc. Want a nice relatively smooth IGN curve. You also want to see that during WOT, esp high RPM’s, you are able to hit the ign targets for this engine, which would mean the car is performing at its peak. If you aren’t hitting the IGN targets or having timing dropouts, then it is time to figure out why by first checking for any codes then possibly bad gas, spark plugs/coils not up to the task aka are too old, as this S85 engine loves fresh plugs, hot/humid weather might play a factor, high IAT’s, etc.
IAT: Intake Air temperature, always a interesting value to log. Always fun to log while you are driving
(be careful and pay attention to the road! Only use when parked)
Get to see how the IAT's fluctuate while stopped, in traffic, on the highway, and during WOT runs.
The Lower the IAT or closer to ambient, the happier the engine runs, and more power you will get.. You will be able to hit IGN targets. Higher the IAT’s go, power begins to get lost, as does your IGN will begin to retard and not hit its targets. So of course, closer to ambient temps IAT are, the better it is for performance.
Lamba:
A figure to use to see if your engine is running lean or running rich.. Can be converted to get a AFR..
How to datalog:
When you want to get a log, a few things to note to make sure you get a clean log!
For performance reasons, most logs are at WOT. So when you hit the log or record button make sure it’s before you go WOT so it is easier to get to the data at WOT and get rid of the part throttle driving.
Traction control should be 100% disabled so there is no interference to effect the data.
Also use comfort suspension mode and a smooth road.
3rd gear or 4th gear is ideal as it puts a higher load and sustains RPM’s longer then first and second gear to get a better look at the data.
You want to start the pull WOT from around 2-3K RPM all the way to red line to get a full power band log, this way you get to see how the engines is behaving at every RPM up to red line. Like mentioned, choose 3rd gear or 4th gear depending on the road available, 3rd gear has been successful.
For example, 3rd gear, around 3K rpm, press record on the logging software on your laptop, then go WOT all the way to redline, then you can hit end and save on your logging software. You have captured a clean log!
Data logging like anything else gets easier to do and easier to understand what each parameter does, and where those parameters should be from experience, and practice.
EXTRAS:
Via the bmw logger software, there are some parameters that aren’t converted to the log, but you will have to play back your data log on the bmw logger software to see the data.
1.)Throttle angle for bank 1 and bank 2.. This would be the throttle bodies sensor for each bank. When your throttle pedal is at 100% you want both these banks to be at 100% and be at 100% throughout the entire WOT run, you don’t want to see any throttle closure in either bank and of course this helps make sure your pedal, and both throttle bodies banks are opening at 100%
2.) Fuel pressure.. The second fuel pump kicks in around 5,000 RPM (also load dependent) and both fuel pumps are at 100%, the max fuel pressure is set to 6 bar here, or around 87 psi.. So on your logs you would like to see at WOT and high RPM your fuel pressure is around 87 psi.
Here are some numbers I roughly put together to help everyone compare their logs and get an idea where their numbers should be at:
5K RPM
IGN= 36-37 Fuel pressure= 87ish psi Fuel pulse= 9-10 Vanos in= 90-100 Vanos out= 110-120 Lamb= 0.87-0.91
Pedal angle= 100% DKPB1 and DKPB2= 100%
7K RPM
IGN= 31-34 Fuel pressure= 87ish psi Fuel pulse= 11-12 Vanos in=105-112 Vanos out= 105-112 Lamb= 0.87-0.91
Pedal angle= 100% DKPB1 and DKPB2= 100%
Here is the S85 IGN targets: Remember these are ideal numbers and most of the time we wont even hit them, but you want to be in the ballpark..
Here is a log showing a clean IGN log, no drop outs, and hitting its target, you can see the line is nice and smooth.. The spike to the right at WOT is a shift, that is normal.
Always remember, everything needs to be taken into consideration when logging and looking at data.. Everything effects one another within this data.. Octane level, fuel quality, seal level, pressure, ambient temps, heatsoak, plug health, etc.
Here are a bunch of sample logs that have been takin out from bmw logger software via .CSV and uploaded on datazap from me and Randy..
Scroll your mouse over the graph to see data and numbers.
93 octane evolve tune
datazap.me | 5soko | Evolve tune/RPI exhaust.. 93 octane
91 octane evolve FBO
datazap.me | randywei | LTH Run 08/31/15 Sal's Stage3 91oct Tune
93 octane evolve FBO
datazap.me | randywei | 95oct, LTH, Mateen Old Tune
Here is a example of how datalogging can help at times.
This setup had a few installation errors, and as you can see the IAT's were very high and after a WOT, IAT's were not decreasing which isnt normal for this engine..
This member had some bad airflow to his intake and ducting.
datazap.me | 5soko | built 240
Lets talk dyno's!
Most guys here will hop on a dyno, do a few pulls, see the numbers and wonder/guess how or what happened..
Dyno operators get their money, and all is well..
Well, datalogging helps in so many ways.. First and foremost, you get to see data of each run, specifically temperatures! Coolant, oil, intake air temperatures especially all have an effect on power and consistent power..
So what do you want to look at on a dyno? Well our S85 loves air, so make sure your shop has some good air slapping the front end of the car.. Next start up your logging software and check those temps.. The most crucial being IAT's since this is where most users and shops fault..
The s85 hates hot air, so keeping an eye on iat's is a must on a dyno to make good power.. You want to get as close as possible to ambient temps as possible.. Then do a run, again next run let the car cool off, bringing the iats back down to where they were your first run.. You will see using datalogging that shutting off the car and letting it cool down will only heat soak the intake further as this sytem wants moving air..
Also checking and keeping an eye on the coolant temp and oil temps of course, iats being the more fluctuating of the three is why we focus more on it then the other two...
Ive seen guys dyno their cars with iats over doubling that of ambient temps! So datalogging gives you a great deal of info at the dyno to help us users get good results, consistent results and information to work with...
Here is a older thread by Sal @ Evolve showing what happens when iats get really hot on our s85's:
http://www.m5board.com/vbulletin/e6...ion/200376-effects-inlet-air-temperature.html
Hope this helps everyone get an idea of what data logging is about and to help begin data logging on their cars. Im no expert by any means and im sure there are alot smarter guys here on the topic. But this is a start Enjoy guys
As always big thanks to Randy (Randywei), The Evolve team, Imran, Mateen and Sal, for their great tunes, helping understand these engines and parameters.
Data logging
What it is:
Data logging has been a normal practice for me for years, esp in my N54 335i days when I was modding and expanding tuning for Terry @ burger tuning, testing alpha and beta tunes.
Datalogging is important whether you are stock or modded. It gives you a great idea of how your car is running, if its running at its peak performance and gives you a great view of values that might surprise and interest you.. Feel like your car isnt feeling fast? Time for a datalog to check.. Numbers dont lie..
What to use to log:
First lets start with what to use to data log on these engines…
The easiest software/cable i found is the software and cable combo from BimmerSoftware.com | Welcome to BMWSW.com
You can also use Bavarian technic cable which is more expensive and complicated/advanced for logging but also comes with 3 vins, so it can be used on 3 cars.
Both will read fault codes as well.. But The BT software will also read errors in every module of the car.
What the data means:
Some of the most important values to log would be RPM, IGN, IAT’s B1/B2, lamba B1/B2, Fuel pressure, throttle, etc. the bmw logger data logs many many parameters by default so no worries.
RPM: self explanatory, you want this logged to show RPM’s.
IGN: This is an important value. Most data logging tools will usually only show 1 cylinder, but that’s acceptable data to give a general idea of how the engine is feeling. All cylinders IGN logging would be ideal!
Through the rev range, you don’t want to see your IGN take a dive, or have multiple drop outs ( sharp downward spikes), this would indicate pinging, misfire, detonation etc. Want a nice relatively smooth IGN curve. You also want to see that during WOT, esp high RPM’s, you are able to hit the ign targets for this engine, which would mean the car is performing at its peak. If you aren’t hitting the IGN targets or having timing dropouts, then it is time to figure out why by first checking for any codes then possibly bad gas, spark plugs/coils not up to the task aka are too old, as this S85 engine loves fresh plugs, hot/humid weather might play a factor, high IAT’s, etc.
IAT: Intake Air temperature, always a interesting value to log. Always fun to log while you are driving
(be careful and pay attention to the road! Only use when parked)
Get to see how the IAT's fluctuate while stopped, in traffic, on the highway, and during WOT runs.
The Lower the IAT or closer to ambient, the happier the engine runs, and more power you will get.. You will be able to hit IGN targets. Higher the IAT’s go, power begins to get lost, as does your IGN will begin to retard and not hit its targets. So of course, closer to ambient temps IAT are, the better it is for performance.
Lamba:
A figure to use to see if your engine is running lean or running rich.. Can be converted to get a AFR..
How to datalog:
When you want to get a log, a few things to note to make sure you get a clean log!
For performance reasons, most logs are at WOT. So when you hit the log or record button make sure it’s before you go WOT so it is easier to get to the data at WOT and get rid of the part throttle driving.
Traction control should be 100% disabled so there is no interference to effect the data.
Also use comfort suspension mode and a smooth road.
3rd gear or 4th gear is ideal as it puts a higher load and sustains RPM’s longer then first and second gear to get a better look at the data.
You want to start the pull WOT from around 2-3K RPM all the way to red line to get a full power band log, this way you get to see how the engines is behaving at every RPM up to red line. Like mentioned, choose 3rd gear or 4th gear depending on the road available, 3rd gear has been successful.
For example, 3rd gear, around 3K rpm, press record on the logging software on your laptop, then go WOT all the way to redline, then you can hit end and save on your logging software. You have captured a clean log!
Data logging like anything else gets easier to do and easier to understand what each parameter does, and where those parameters should be from experience, and practice.
EXTRAS:
Via the bmw logger software, there are some parameters that aren’t converted to the log, but you will have to play back your data log on the bmw logger software to see the data.
1.)Throttle angle for bank 1 and bank 2.. This would be the throttle bodies sensor for each bank. When your throttle pedal is at 100% you want both these banks to be at 100% and be at 100% throughout the entire WOT run, you don’t want to see any throttle closure in either bank and of course this helps make sure your pedal, and both throttle bodies banks are opening at 100%
2.) Fuel pressure.. The second fuel pump kicks in around 5,000 RPM (also load dependent) and both fuel pumps are at 100%, the max fuel pressure is set to 6 bar here, or around 87 psi.. So on your logs you would like to see at WOT and high RPM your fuel pressure is around 87 psi.
Here are some numbers I roughly put together to help everyone compare their logs and get an idea where their numbers should be at:
5K RPM
IGN= 36-37 Fuel pressure= 87ish psi Fuel pulse= 9-10 Vanos in= 90-100 Vanos out= 110-120 Lamb= 0.87-0.91
Pedal angle= 100% DKPB1 and DKPB2= 100%
7K RPM
IGN= 31-34 Fuel pressure= 87ish psi Fuel pulse= 11-12 Vanos in=105-112 Vanos out= 105-112 Lamb= 0.87-0.91
Pedal angle= 100% DKPB1 and DKPB2= 100%
Here is the S85 IGN targets: Remember these are ideal numbers and most of the time we wont even hit them, but you want to be in the ballpark..
Here is a log showing a clean IGN log, no drop outs, and hitting its target, you can see the line is nice and smooth.. The spike to the right at WOT is a shift, that is normal.
Always remember, everything needs to be taken into consideration when logging and looking at data.. Everything effects one another within this data.. Octane level, fuel quality, seal level, pressure, ambient temps, heatsoak, plug health, etc.
Here are a bunch of sample logs that have been takin out from bmw logger software via .CSV and uploaded on datazap from me and Randy..
Scroll your mouse over the graph to see data and numbers.
93 octane evolve tune
datazap.me | 5soko | Evolve tune/RPI exhaust.. 93 octane
91 octane evolve FBO
datazap.me | randywei | LTH Run 08/31/15 Sal's Stage3 91oct Tune
93 octane evolve FBO
datazap.me | randywei | 95oct, LTH, Mateen Old Tune
Here is a example of how datalogging can help at times.
This setup had a few installation errors, and as you can see the IAT's were very high and after a WOT, IAT's were not decreasing which isnt normal for this engine..
This member had some bad airflow to his intake and ducting.
datazap.me | 5soko | built 240
Lets talk dyno's!
Most guys here will hop on a dyno, do a few pulls, see the numbers and wonder/guess how or what happened..
Dyno operators get their money, and all is well..
Well, datalogging helps in so many ways.. First and foremost, you get to see data of each run, specifically temperatures! Coolant, oil, intake air temperatures especially all have an effect on power and consistent power..
So what do you want to look at on a dyno? Well our S85 loves air, so make sure your shop has some good air slapping the front end of the car.. Next start up your logging software and check those temps.. The most crucial being IAT's since this is where most users and shops fault..
The s85 hates hot air, so keeping an eye on iat's is a must on a dyno to make good power.. You want to get as close as possible to ambient temps as possible.. Then do a run, again next run let the car cool off, bringing the iats back down to where they were your first run.. You will see using datalogging that shutting off the car and letting it cool down will only heat soak the intake further as this sytem wants moving air..
Also checking and keeping an eye on the coolant temp and oil temps of course, iats being the more fluctuating of the three is why we focus more on it then the other two...
Ive seen guys dyno their cars with iats over doubling that of ambient temps! So datalogging gives you a great deal of info at the dyno to help us users get good results, consistent results and information to work with...
Here is a older thread by Sal @ Evolve showing what happens when iats get really hot on our s85's:
http://www.m5board.com/vbulletin/e6...ion/200376-effects-inlet-air-temperature.html
Hope this helps everyone get an idea of what data logging is about and to help begin data logging on their cars. Im no expert by any means and im sure there are alot smarter guys here on the topic. But this is a start Enjoy guys
As always big thanks to Randy (Randywei), The Evolve team, Imran, Mateen and Sal, for their great tunes, helping understand these engines and parameters.