-
sample capture
07/22/2016 at 03:02 • 0 commentshave added to files: https://cdn.hackaday.io/files/12644540960896/LOG40.CSV
-
github code up
07/21/2016 at 08:06 • 1 commentfirst full working commit has been made to github
-
Prototype Build
07/19/2016 at 11:25 • 0 commentsSo here is my first build of the standalone device, Some LED and an LCD for status display and a sd card for logging to csv.
The individual components:
-
Gearbox Pinout
07/19/2016 at 10:59 • 0 commentsGearbox ecu pinout: https://en.wikipedia.org/wiki/AWTF-80_SC
-
Components
07/19/2016 at 10:57 • 0 commentsDiagnostics tool used for citroen:
Diagnostics "double adapter" so a can monitor the traffic between diagnostics tool and car ecu's::
The Arduino CAN bus shield:
Adapter for shield to diagnostics port:
The Car im working on:
-
CSV Plotter / Graphing
07/19/2016 at 08:14 • 0 commentsSo i got some results, found this nice program to graph csv, this is results of B1, C1, C2, C3 against gear shift over time. http://www.datplot.com/ now just have to get the gearbox to play up while logging.
-
Progress so far...
07/16/2016 at 11:11 • 0 commentsThings are going great, im nearly done on the arduino script.
Using CAN Hacker i was able to locate 3 key CAN message ID's of interest to me,
- one with general gearbox state that is transmitted all the time 0x489
- one that is used by the diagnostics tool to transmit, 0x6A9
- and one that is used by likely the BSI to reply to requests by the diag tool, 0x689
I was then able to 'decode' how the readings where being sent back by looking at changes while triggering a change in the reading via a switch or gear shift.
And put this all into an arduino sketch to emulate the process of requesting diagnostics readings, 'translating' them into readable data, and displaying/logging them for review.