sample log file?

fens53695's Avatar

fens53695

26 Aug, 2009 08:35 PM

Hi folks:

I just ordered a mindset unit, and downloaded the SDK. Since it can be more than a month before the unit is delivered, I'd like to start development. I noticed that the ThinkGear socket server has an option for creating a log file. Is the format of the log file documented somewhere in the SDK? Is it possible to get a sample log file complete with sample EEG data?

Thanks,

Michael

  1. Support Staff 1 Posted by Kelvin on 27 Aug, 2009 08:52 PM

    Kelvin's Avatar

    The ThinkGear Connector (TGC)'s log file option simply turns on the underlying ThinkGear Communications Driver (TGCD)'s stream log and data log capabilities. The TGCD's log files are only intended to be used for general debugging, troubleshooting, and support of the TGCD, and we are planning to make some changes to the format in the next revision of the TGCD, so it is not formally documented anywhere in the MindSet Development Tools (MDT).

    Currently, it is our intention that developers, such as yourself, use the TGC and TGCD APIs to get the data values, and write their own log files in their own formats appropriate for them.

    NeuroSky does provide some applications in the MindSet Research Tools (MRT) such as NeuroView and NeuroSkyLab, which record MindSet data in some standard formats, such as CSV. The MRT is available for purchase in the Store.

    If you are still interested in understanding the TGCD's current log files' formats, here is the short explanation:

    Stream Log: A log of the actual bytes received by the TGCD from the serial COM stream. The first value on each line is a UNIX timestamp (number of seconds since epoch), in units of seconds with millisecond precision. Each two hex digits after that on the line is a byte that was received at that time. For MindSets, these bytes form ThinkGear Packets, which are fully documented in the MindSet Communications Protocol document (located in the tg/ directory of the MDT).

    Data Log: A log of the DataRows decoded from the serial COM stream. The timestamp on each line is the same as described for the Stream log. It is followed by the DataRow's CODE, which indicates what type of data is contained in that DataRow. The definitions of CODEs and data types are documented in the MindSet Communications Protocol document (located in the tg/ directory of the MDT). The values that appear after the CODE are the actual value for that DataRow. For example, a DataRow with CODE [80] indicates the DataRow contains a Raw Wave value, and the number after the code is the Raw Wave Value at that time, while a DataRow with CODE [4] indicates the DataRow contains an Attention value, and the number after the code is the Attention Value at that time.

    Please let me know if still have any questions.

Comments are currently closed for this discussion. You can start a new one.

Keyboard shortcuts

Generic

? Show this help
ESC Blurs the current field

Comment Form

r Focus the comment reply box
^ + ↩ Submit the comment

You can use Command ⌘ instead of Control ^ on Mac