We are ready to work with Beta testers for the MS6 v1XX calibrations. I have spent extensive time familiarizing myself with the MSD DashHawk (DH) which seems to be the preferred datalogger for this community. I have organized various datalogging batches below. Datalogging in these PID batches will better organize the data and allow us to focus on specific aspects of a calibrations during this testing process.
For those who are familiar withe the DH, I have prepared four different Profiles that you upload to your DH. Each profile has a batch of three datalogs; Profile 1 has Boost Batch 1, Fuel Batch 1, and Ignition Batch 1. Profile 2 has Boost Batch 2, Fuel Batch 2, and Ignition Batch 2. This will make the data analysis process more organized and revisions quicker.
Unfortunately, you will need a DH or other datalogging software in order to be a Beta tester for these calibrations. We are fine tuning various aspects of the calibrations and organized data is necessary for this process. We need to be able to focus on various aspects of a tune and data will help provide us with effective feedback.
The Beta testing process is simple. After you are accepted as a Beta tester, I will e-mail you with a AccessPORT Beta calibration, then you will be instructed with what batch to datalog and how to drive the vehicle while datalogging. Datalogging must be safe and will need to take place on a closed-course like your local drag strip or road coarse. Street driving is an unsafe environment for datalogging.
To apply for Beta testing, you will need to e-mail me christian.krahenbuhl@cobbtuning.comwith "MS6 v100 Beta Tester" in the subject line. I will need to know the year and model (CA or Federal) of your vehicle, a full list of installed hardware, what elevation you operate the vehicle at, and the fuel you are using.
MAF Batch 1:
RPM
AbsTPS
STFTB1
LTFTB1
Mass Air Flow Sensor
This test should be done carefully. Allow the vehicle to idle for a few minutes, then drive for about 50 miles at light throttle. Start in 3rd or 4th gear at 1500 RPM then very slowly modulate throttle from there to ~50% over the next 30 seconds. After you have completed this test to 50% throttle, please put the car in neutral and allow the car to idle for a few seconds before stopping the log. This will allow us to see what type of learning the stock ECU is doing to compensate for the intake system that is installed on this car. Ideally, you want your LTFT values to be closer to zero. Anything +/- 8% is acceptable, but closer to 0 LTFT is ideal.
GREAT SAMPLE MAF BATCH LOG BELOW, notice how smooth the throttle transition is and how the car was allowed to idle for a few seconds after reaching the end of the throttle transition. This will allow you to capture the idle LTFT as well.
MAF Batch 2:
RPM
AbsTPS
Mass Air Flow Sensor
LTFTB1
MAF Volts
I have downloaded the latest DH firmware, which is supposed to be v2.51. The screen still says 2.50? You are welcome to try this new release from MSD to see if it will resolve your compatibility issues.
I live in portland, or. Surgeline is around the corner or so. I don't own a dashhawk but maybe they have one I can borrow. The only problem is the gas here in Oregon is 92 with 10% ethonol. Just got knock today on accident in second gear. I can test out the product and maybe the access port with a 91 octane tune will fix my car. Car is stock.
Reply With Quote
MS6 v1XX Calibrations testing with DH Datalogging
Posting Permissions