Openport 2.0, Bad connection, or bad o2 sensor?
Posted: Sat Mar 10, 2018 12:30 pmFirst time trying to log with the Openport 2.0, it appears to stop working when it gets to the o2 sensor.
Here is what I get:
[13:45:11.580] using metadata XML ID read_wrx02 from file C:/Program Files (x86)/OpenECU/EcuFlash/rommetadata/read templates/read_wrx02.xml
[13:45:11.592] J2534 API Version: 04.04
[13:45:11.592] J2534 DLL Version: 1.02.4798 Jun 13 2016 17:17:10
[13:45:11.592] Device Firmware Version: 1.16.4769
[13:45:11.592] Device Serial Number: TA5iX$Ld
[13:45:21.180] denso02_bootloader_cmd_start
[13:45:22.416] denso02_bootloader_cmd_start
[13:45:23.652] denso02_bootloader_cmd_start
[13:45:24.889] denso02_bootloader_cmd_start
[13:45:26.125] denso02_bootloader_cmd_start
[13:45:26.537] kernel get version
[13:45:26.849] interface close
[13:45:26.853] interface close
I have other reasons to suspect a bad o2 sensor, is this the case, or is my interface bad?
Here is what I get:
[13:45:11.580] using metadata XML ID read_wrx02 from file C:/Program Files (x86)/OpenECU/EcuFlash/rommetadata/read templates/read_wrx02.xml
[13:45:11.592] J2534 API Version: 04.04
[13:45:11.592] J2534 DLL Version: 1.02.4798 Jun 13 2016 17:17:10
[13:45:11.592] Device Firmware Version: 1.16.4769
[13:45:11.592] Device Serial Number: TA5iX$Ld
[13:45:21.180] denso02_bootloader_cmd_start
[13:45:22.416] denso02_bootloader_cmd_start
[13:45:23.652] denso02_bootloader_cmd_start
[13:45:24.889] denso02_bootloader_cmd_start
[13:45:26.125] denso02_bootloader_cmd_start
[13:45:26.537] kernel get version
[13:45:26.849] interface close
[13:45:26.853] interface close
I have other reasons to suspect a bad o2 sensor, is this the case, or is my interface bad?