Setting a parameter to "sampgroup=1" will log it every other polling period. By default, a parameter is sampled for each line of log output. Sampgroups allow you to have some parameters polled less often than others. Some of the parameters have "sampgroup" definitions on them. The second set of conditions (which are commented out) log anytime the throttle position sensor (TPS) shows more than 75% throttle. The first set of conditions have the OpenPort log any time the engine is running. This defines when the OpenPort logs the data to the MicroSD card. Near the end of the file is a section labeled "logging conditions". To log these additional items, or stop logging a parameter that you don't need, either remove or add the semicolon from the lines associated with that parameter. This means that the lines for that parameter begin with a semicolon: " ". Many of the more extraneous parameters that you probably won't log on a regular basis have been commented out. It has all the parameters defined that I think you would want to be able to log at some point.
I've attached a text file which is a sample logcfg.txt that you can use with Chrome. Only worry about that after you've gained some experience with logging and feel totally comfortable messing with such things. The OpenPort is communicating with my ECU at 62500 baud just fine, and EvoScan gets about a 25% increase in logging rate at that baudrate. For OpenPort logging, changes to baudrate don't make any difference in how fast logging works, so only change the baudrate if you want quicker EvoScan logging. The default baudrate for Chrome is the factory rate of 15625, so unless you specifically went in Chrome and changed it and flashed it to your ECU, you will want to leave that at 15625. You could use OBD2, but its parameters are more limited and the rate of logging is slower.
We use the MUT2 method of communicating with the ECU for logging. Once you have your MicroSD card set up to work in the OpenPort adapter, you need to put a logcfg.txt file on the card that contains the connection method, baudrate, and parameters that you want logged. I've had success with FAT32 on mine as well, but the OpenPort guys say that there's a lot of additional overhead writing to FAT32, so to keep it streamlined use FAT (default). Format as "FAT (default)" for best results. If it doesn't mount, and you get a warning message that the disk is not readable, you probably have to format it. You should see the MicroSD "disk" mount as a drive letter. The OpenPort adapter functions as a MicroSD card reader whenever it is connected to your laptop with a USB cable. Anyone who is using Chrome 2.0 should already have an OpenPort 2.0 to perform flashing, so here's the easy way to datalog using the OpenPort without needing to have your laptop connected to the OpenPort and running EvoScan.įlashable 3/S ECU ('98, '99, "Clone", etc)ĢGB or smaller MicroSD card, formatted as FAT16
0 kommentar(er)
