Things like a poorly made intake, a boost leak, bad tank of gas, bad sensor, and plugged cats, are just a few of things we can see with a high quality datalog. These are not things we support (unless they are our parts in question), but it does allows you to better describe the problem to a qualified mechanic. Simply plug in your AccessPORT to the OBD port, scroll to the Monitor icon and press the OK button. Scroll down to where Set Data Log List is, and press the OK button. This will display all possible data that can be logged. Simply check or uncheck the data you wish to view. When you are done press the back button and save the data to be logged.īy default we check off the important things we need to see. This default setup is perfect for what providing the data we need to see.
You do not need to check off any addition parameters unless we suggest to. There are many parameters that we do not need to see and the more parameters the slower the logging is. So please only pick the data we ask you to or leave it set to default, as this will give you the highest quality datalog possible. Once data is selected you can start logging by going to Live Data, bring up any parameter, then click the OK button. You will see "Initializing" at the bottom of the display then "Logging". When you are done logging you simply click the middle button! This then saves the log onto your AccessPORT which can later be removed and emailed to us using the AccessPORT Manager software. Removing the log will be explained further down the page. Keep in mind that every time you create a datalog, the AccessPORT saves a new file. For instance, the first time you create a log, it saves it as Datalog1.csv. Then the next one is Datalog2.csv and so on. This allows you to to make more than one while driving your car and keep track of them when you remove them from the AccessPORT. What Do You Need to Data Log?Īs we briefly mentioned before, logging too much data can effect how accurate the data is. This happens because the data from the ECU can only be collected so fast.
If you ask the AccessPORT to collect too much data, its causes the log to run slower. Example, you ask it to log 1 thing you will get 20 samples of this each second. Which provides excellent data for us to help tune your map. If you ask the ECU for 20 things you may only get 1 sample a second, and while this sounds ok and its not enough to do a proper tune or adjustment to you map. So a balance of speed and type of data works best. 7 to 10 parameters is what works best and generally gets us enough info to accurately modify your map. You can see from the below data log that we are getting roughly 5-6 samples a seconds. In this case we asked the customer to verify a hiccup he was having on his 08 STI. Calculated Load (Load Timing and Load Fuel/Boost for EVO X).Wastegate Duty Cycle (Fine and Coarse for EVO X).Boost Related Issues and Parameters to Log Had the customer needed some help with low or high boost we would have asked for different parameters.īecause different situations require different parameters to log we have put together a couple common type situations and the data we would like to see. Runs needs to be in 3 rd or 4 th gear starting at 2000 then floor it and take rpm as high possible not exceeding speed limit. Runs needs to start before and end after area of concern, in any gear. Roughly 10 seconds of run time is all that is needed. There may be more parameters we might ask you to log but those are the main ones that will cover 99% of what we need to see.
0 kommentar(er)
