pcmhacking.net

I did some debug test, but couldn`t duplicate any of the issues you are experiencing.

One thing that is odd is that in csv log it saves 11 as data and than displays it as 17 which means it saves it as hex and than convert it to decimal on display.

On my tests it should save in csv in decimal and display in decimal.

can you log pid 1141, ignition voltage is not super steady so it may fluctuate a bit. At least we can rule out the hex bug. It can also be some pid config bug. In profile.xml data format is converted to other format for Universal patcher use.

Can you share some info on windows version you are using.

Added test profile to rule out some PID config issues.

I'm on Windows 10 Pro. 10.0.19045 Build 19045. My Surface Pro 2 that I'm trying to use in the car is on the same build.

Your xml logged correctly.

Time,Elapsed time,Ignition 1 Signal,engineoff
21:11:26.4989,00:00:00.4295652,11.7,1203
21:11:26.5226,00:00:00.4305630,11.7,1203
21:11:26.5480,00:00:00.4305630,11.7,1203
21:11:26.5726,00:00:00.4305630,11.7,1203
21:11:26.6000,00:00:00.4305630,11.7,1203
~~
21:11:26.8726,00:00:00.5456900,11.7,1204
21:11:26.8989,00:00:00.5456900,11.7,1204
21:11:26.9226,00:00:00.6551874,11.7,1204
21:11:26.9481,00:00:00.6551874,11.7,1204
~~
21:11:27.9223,00:00:01.6425256,11.7,1205
21:11:27.9478,00:00:01.7510785,11.7,1205
21:11:27.9723,00:00:01.7510785,11.7,1205
21:11:27.9986,00:00:01.7510785,11.7,1205
~~
21:11:28.6723,00:00:02.4115503,11.7,1206
21:11:28.6987,00:00:02.4115503,11.7,1206
21:11:28.7223,00:00:02.4115503,11.7,1206
21:11:28.7478,00:00:02.5231475,11.7,1206

After looking at your file, I see what I did wrong now. It's good old user error. I originally specified the time as a byte instead of a word. I fixed it in the Parameters.xml, but not the logging profile. I didn't realize those details had to be specified in both files. Correcting my logging profile got it to show up correctly.

I'll have to double check the test file I was trying to run on my car, and retest it when it gets back from the body shop. I was logging some transmission data, and I can't simulate that on my bench.

Thanks for explaining this.

BTW, Tactrix also appears to log correctly, with the same settings my MDI used.

Great it worked for you.

I think something messed up with adding the pid as byte, than changing it to word somehow didn`t went through.

On my test it converts correctly in user profile. Can you test with this file if it is converts as per the screenshot when added.