OpenBCI_GUI: Aux channels not saved in file when running 16 channel system

AJ,

This is a real bug. When I remove the Daisy board AUX1 - AUX3 appears as they should in the OpenBCI text file. As soon as I go to 16 channels all I get back in AUX1 - AUX3 are zeros. The same applies to the acceleration data in the DEFAULT board mode.

This happens using BLE as well as wifi. For wifi I have tested sample rates from 250 to 1000Hz and the bug is repeatable.

OSX High Sierra OpenBCI_GUI - Latest master 3.1.0 as well as release .app Board firmware - Latest master + LED functions

Experimental process For Default (accel) mode

Use downloaded release GUI 3.1.0
Connect to board (either 8 or 16 channels)
Set sampling rate
Start board
Check .txt files

For Marker data on the aux channel:

Use custom GUI (based on latest github master with minor changes)
Send “/4” to put the board into maker mode
Start board
Send “`n” markers (n -> 0:127)
LED flash on board indicates markers are correctly received
Check .txt files

Without Daisy board (8 Channels) the markers are correctly recorded in the file as well as Acceleration info (only every 40 samples) (BLE and Wifi)

With the Daisy board all the values for Aux/Accel in the files are Zero (for both BLE and Wifi)

About this issue

Original URL
State: closed
Created 7 years ago
Comments: 20 (12 by maintainers)

Commits related to this issue

FIX: #277 add sdcardstart — committed to andrewjaykeller/OpenBCI_GUI by deleted user 7 years ago

Most upvoted comments

@tzvet that’s great your getting the system to start working!

Can you please open two issues?

One for

Just as a side note, the SD card markers are not in the same format as the ones sent back to the computer: e.g. writing `9 gives back 57 on the computer, but it writes 0.007125 on the SD card… some conversion error, but still fine because different markers get different values 😃

and another for

Now there is another quite some big problem, sending Markers makes a huge noise on ALL electrodes at marker onset. Any solution for this?

I do not want to keep commenting on a closed issue 😃 I love that you included screen shots that’s awesome! Also if you could explain what you did to send the markers, I would love to know!

With two issues, we can work together to close each one, and maybe you, myself or another community member will write the code or patch! We are glad to help you develop your skills, no matter whatever level you are, we want to help!

andrewjaykeller on Dec 12, 2017