Inertial Sensor and Logger Board - Revision history

Donald: /* Log file format */

2009-09-16T16:04:45Z

‎Log file format

Donald: /* Data Logging */

2009-09-16T16:03:49Z

‎Data Logging

Donald: New page: ==Functionality Overview== This board has a widespread set of functionality: # Measure acceleration, both longitudinal and lateral # Measure yaw rate # Measure voltage of the electrical s...

2009-09-16T15:30:42Z

New page: ==Functionality Overview== This board has a widespread set of functionality: # Measure acceleration, both longitudinal and lateral # Measure yaw rate # Measure voltage of the electrical s...

New page

==Functionality Overview==

This board has a widespread set of functionality:
# Measure acceleration, both longitudinal and lateral
# Measure yaw rate
# Measure voltage of the electrical system supply battery
# Log data to a SD-Card

==Data Logging==

This board can write data to a FAT16-formatted SD or MMC card that is inserted into the card reader slot. When the board is booted and a valid card is detected, a new file is created and data from all messages on the can bus is written into this file.

===Log indicators===

If logging is working and dumping precious driving data to the card, the red LED adjacent to the green power LED glows.

===File naming scheme===

The data is stored to a newly created file with the naming scheme <tt>LOG<nr>.CAN</tt>. The <tt><nr></tt> part is a consecutive number to name all files differently and not to overwrite an older log. An internal counter increments each time a new log file is written, and the counter state is conserved in EEPROM over reboots. Reflashing the board resets the counter to 0.

===Requirements for the card===

The SD or MMC card must meet the following conditions:
* A partition table exists.
* The "DOS compatibility flag" must be set.
* There is exactly one primary partition.
* The partition's type is "FAT16" (set partition code to 0x06 with fdisk).
* The partition is formatted with FAT16, two fats.
Using a Unix/Linux system, if <tt>/dev/mmcblk0</tt> is your MMC/SD card device,
mkfs.vfat -F 16 /dev/mmcblk0p1
would create a valid FAT 16 partition.

Despite having the correct partition scheme and formatting, some cards just did not work. We can not tell you why and how, just check if the red LED indicates that the logger works. Cards with 2GB or more tend to be problematic, try using a 1GB card.

===Log file format===

'''TODO'''

===Log file decryption===

'''TODO'''

@@ Line 38: / Line 38: @@
 The log file has a binary format, containing a dump of all CAN messages including a timestamp for each. For each CAN message, the following data fragment is written:
   | Header | Timestamp | CAN ID  | Data Length |     Data    |
   |  0xca  |  4 Bytes  | 2 Bytes |    1 Byte   | 0 - 8 Bytes |
 The <tt>Header</tt> field is always one Byte with hex value <tt>0xca</tt>. The <tt>Timestamp</tt> field holds the time in ms since the board was booted up. The remainder of the data fragment is the CAN message's id and content.
 For each received CAN message, a new fragment of this sort is appended to the log file.

@@ Line 10: / Line 10: @@
 ==Data Logging==
 This board can write data to a FAT16-formatted SD or MMC card that is inserted into the card reader slot. When the board is booted and a valid card is detected, a new file is created and data from all messages on the can bus is written into this file.
 ===Log indicators===
@@ Line 29: / Line 30: @@
 * The partition is formatted with FAT16, two fats.
 Using a Unix/Linux system, if <tt>/dev/mmcblk0</tt> is your MMC/SD card device,
-  mkfs.vfat -F 16 /dev/mmcblk0p1
+  > mkfs.vfat -F 16 /dev/mmcblk0p1
 would create a valid FAT 16 partition.
@@ Line 36: / Line 37: @@
 ===Log file format===
-'''TODO'''
+The log file has a binary format, containing a dump of all CAN messages including a timestamp for each. For each CAN message, the following data fragment is written:
 ===Log file decryption===
 '''TODO'''