Differences

This shows you the differences between two versions of the page.

--- debugfile [2009/04/17 14:44]
twdorris created
+++ debugfile [2024/03/15 11:16] (current)
@@ Line 1: / Line 1: @@
 ====== Creating an ECMLink application debug file ======
 In some debugging situations, it's necessary to collect more information from a customer's runtime environment.  You do that by increasing the debug level in our logging system.  Doing so dramatically increases log volume, though.  So you do not want to leave the configuration in this state permanently.
+===== Usage =====
+To create a fresh applog.txt file:
+  - Exit the ECMLink application
+  - Edit the logging.properties file (more details below)
+  - Start the ECMLink application
+  - Recreate the problem you were having
+  - Exit the ECMLink application
+  - 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
 ===== logging.properties file =====
-Location the logging.properties file in the installation root directory.  Under Windows, this will typically be:
+Locate the logging.properties file in the installation root directory.  Under Windows, this will typically be:
   C:\Program Files\ECMLink
@@ Line 15: / Line 28: @@
   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.
+==== 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 =====
-The debug file can be located in the following directory:
+Under Windows, you can find the applog.txt file here:
-  C:\Documents and Settings\<username>\ecmlink
+  %userprofile%\ecmlink\applog.txt
-The filename will be 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.
-===== Usage =====
+The specific location when running under Windows XP is:
-To create a fresh applog.txt file:
-  - Exit the ECMLink application
+  C:\Documents and Settings\<username>\ecmlink\applog.txt
-  - Edit the logging.properties file as explained above
-  - Start the ECMLink application
-  - Recreate the problem you were having
-  - Exit the ECMLink application
-  - Grab the applog.txt file and edit/post it up on our forums
+When running under Windows Vista/7, the debug file can be located in the following directory:
+  C:\Users\<username>\ecmlink\applog.txt

ECMTuning - wiki

User Tools

Site Tools

Differences

Page Tools