debugfile
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
debugfile [2009/06/22 10:03] dmertz |
debugfile [2024/03/15 11:16] (current) |
||
|---|---|---|---|
| Line 12: | Line 12: | ||
| - Grab the applog.txt file and edit/post it up on our forums | - Grab the applog.txt file and edit/post it up on our forums | ||
| - Edit the logging.properties file and undo the changes you made above | - Edit the logging.properties file and undo the changes you made above | ||
| + | |||
| Line 27: | Line 28: | ||
| com.ecmtuning.ecmlink.level = FINE | com.ecmtuning.ecmlink.level = FINE | ||
| - | Change that FINE to FINEST and you'll get a LOT more debug data. If you are running Windows Vista, you'll need to be running as administrator to be able to edit the logging.properties file. | + | If you are running Windows Vista, you'll need to be running as administrator to be able to edit the logging.properties file. |
| + | |||
| + | |||
| + | ==== Basic device data ==== | ||
| + | |||
| + | Now there are a couple choices to make. If you want a reasonably manageable log file and you're just having basic communication problems, then just add the following line to the end of that file. | ||
| + | |||
| + | com.ecmtuning.ecmlink.device.ecmlink.level = FINER | ||
| + | |||
| + | You can change that FINER to FINEST if you want to log more debugging data related specifically to the ECMLink connection process. But be forewarned that this file will be *megabytes* in size and can cause the application to slow down substantially. I would not recommend attempting to datalog while logging is set to FINEST. | ||
| + | |||
| + | |||
| + | ==== Full-blown debug data ==== | ||
| + | |||
| + | If you want to turn on full-blown debugging to get all SORTS of information about application initialization, configuration files, communication bytes, etc., etc, then change the existing line in the logging.properties file to read: | ||
| + | |||
| + | com.ecmtuning.ecmlink.level = FINEST | ||
| + | |||
| + | But be forewarned that this file will be *megabytes* in size and can cause the application to slow down substantially. I would not recommend attempting to datalog while logging is set to FINEST. | ||
| + | |||
| + | |||
| ===== applog.txt file ===== | ===== applog.txt file ===== | ||
| - | When running under Windows XP, the debug file can be located in the following directory: | + | Under Windows, you can find the applog.txt file here: |
| + | |||
| + | %userprofile%\ecmlink\applog.txt | ||
| + | |||
| + | You can actually just type that directly into a file browser (like while you're trying to attach to an e-mail or forum post) and Windows will automatically load it up. | ||
| - | C:\Documents and Settings\<username>\ecmlink | + | The specific location when running under Windows XP is: |
| - | When running under Windows Vista, the debug file can be located in the following directory: | + | C:\Documents and Settings\<username>\ecmlink\applog.txt |
| - | C:\Users\<username>\ecmlink | + | When running under Windows Vista/7, the debug file can be located in the following directory: |
| - | The filename will be applog.txt. | + | C:\Users\<username>\ecmlink\applog.txt |
debugfile.1245679436.txt.gz · Last modified: 2009/06/22 10:03 by dmertz
Page Tools
Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Share Alike 4.0 International
