Skip to content

Latest commit

 

History

History
28 lines (20 loc) · 1.43 KB

data-structure.md

File metadata and controls

28 lines (20 loc) · 1.43 KB
Raw

#Data structure

The world of CAN is matrix. It simply is, that's the first thing I thought when I started live CAN data dumping through Raspberry Pi CAN module into my green-black terminal.

The simplest structure that is obtained from the dump is as follows: One dump line represents one data dump (DATA_DUMP) from and address(ADDRESS_WHERE_DATA_DUMP_CARE_FROM) at a specific time(TIME_DATA_DUMP_TAKEN), that is:

<TIME_DATA_DUMP_TAKEN> ADDRESS_WHERE_DATA_DUMP_CAME_FROM DATA_DUMP

For receiving this data I used candump from can-utils. Regardless, you can always adapt data read by changing the source (See defaults.conf).

Next step is connecting this simple data-structure by a truly unique identifier: the address, thus getting everything in such structure:

ADDRESS_WHERE_DATA_DUMP_CAME_FROM:
    <TIME_DATA_DUMP_TAKEN1> DATA_DUMP1
    <TIME_DATA_DUMP_TAKEN2> DATA_DUMP2
    <TIME_DATA_DUMP_TAKEN3> DATA_DUMP3
    <TIME_DATA_DUMP_TAKEN4> DATA_DUMP4

Lastly, since we're debugging information, there might as well be some kind of test dump file (or any other source) ready, it might have several addresses of aforementioned structure.

Visually (DIAGRAM COMING) this would look: test case
/ |
addr1 addr2 addr3 / | / | |
addr data addr data addr data For implementation see data-structure.py