https://github.com/ChrisVeigl/BrainBay/blob/master/src/ob_eeg.cpp

https://github.com/ChrisVeigl/BrainBay/blob/master/src/ob_eeg.cpp

https://github.com/ChrisVeigl/BrainBay/blob/master/src/ob_eeg.cpp

https://github.com/ChrisVeigl/BrainBay/blob/master/src/ob_eeg.cpp

https://github.com/ChrisVeigl/BrainBay/blob/master/src/ob_eeg.cpp

Fred, take a look at the C language protocol machine in BrainBay, at about line 750 here.

Joel, Kevin, hi.

A minor comment on your state machine derived from the ob_eeg.cpp (BrainBay OpenBCI driver). That original code kept track of sync loss situations by bumping a counter. And then that counter was made

loss events have occurred (as Brainbay and the ob_eeg.cpp code does.) As long as this is constant, or rarely changing, you are fine.

https://github.com/ChrisVeigl/BrainBay/blob/master/src/ob_eeg.cpp

https://github.com/ChrisVeigl/BrainBay/blob/master/src/ob_eeg.cpp

Dhruv, if you want to see the C++ code that Brainbay uses to sync up and parse the incoming packets, look at the module ob_eeg.cpp . It's a state machine that is called on each incoming byte. A simila

If you look at the source file ob_eeg.cpp in the Brainbay Github, this contains the EEG device driver, data stream packet decoding logic for all the supported devices. These are for the most part, ser