From 4ba0afbdc710f318c4d2a0c761c299ecad790bfe Mon Sep 17 00:00:00 2001 From: rusefillc Date: Sat, 10 Feb 2024 17:37:30 -0500 Subject: [PATCH] HOWTO-Make-Your-Own-ECU-Communicate-with-TCU.md --- HOWTO-Make-Your-Own-ECU-Communicate-with-TCU.md | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/HOWTO-Make-Your-Own-ECU-Communicate-with-TCU.md b/HOWTO-Make-Your-Own-ECU-Communicate-with-TCU.md index 6045bb96..918d5fa7 100644 --- a/HOWTO-Make-Your-Own-ECU-Communicate-with-TCU.md +++ b/HOWTO-Make-Your-Own-ECU-Communicate-with-TCU.md @@ -11,3 +11,9 @@ Original ECU which I am looking to replace for no good reason is BOSCH MED9.1. C ## Toolset I have PCAN USB dongle to record CANbus traces and a few Proteus units for Man-in-the-middle research. I've also created my own suite of CANbus trace processing utilities https://github.com/rusefi/can-log-tools/ + +## First experiments + +First let's grab a trace and a snapshot of CANbus traffic while engine is not running, both with OEM ECU and with OEM ECU disconnected. We get https://github.com/rusefi/rusefi_documentation/commit/722e81d2b0dd2b1f9661a3e9fd6383087ba4418a#diff-457155f3530fe11dbca1083aa1860f4e3cccc8f2d8b78d81634def58fbc38d9f + +Comparing these two files we confirm which packets are clearly originating from the now disconnected OEM ECU https://github.com/rusefi/rusefi_documentation/commit/8575c7292d975c2477ccf070634883f5a9423c7e