I'll update this thread later if I get the parameters scaled properly. If anybody catches errors with my scaling let me know. Uncomment that and comment the engine speed block if that is the trigger you want to use. But there is an additional block commented out that uses the defogger as a trigger.
Right now I have it where it logs as soon as the engine is started. But anybody can feel free to use the following as a basis for whatever they want to log. I don't know why, since I got all of the scaling straight from the logger defs file that romraider uses. I created a first cut version of a logcfg.txt file, but there are some issues with the way a few of the variables are scaled. The logcfg.txt file is what dictates which parameters you log, what the variable names are, which ECU addresses are accessed, and what the final scaling is (conversion from raw ECU value to a dimensional value).
You basically need to install the latest beta version of ecuflash that supports stand alone logging, then upgrade the firmware on the openport through ecuflash, and finally put a logcfg.txt file on the microsd card. It just generates CSV files for each logging session directly on the card, with whatever parameters you choose. This allows you to log data directly to a microsd card in the openport, without carrying a laptop in the car with you.
So I finally got the stand alone datalogging to work with the openport 2.0.
