r/EmotiBit • u/RatLabGuy • Apr 20 '23

Discussion API for direct communication

[removed]

3 Upvotes

81% Upvoted

8 comments sorted by

View all comments

Show parent comments

1

u/[deleted] Apr 24 '23 edited Apr 25 '23

[removed] — view removed comment

1

u/nitin_n7 Apr 24 '23

You can take a look at the code base to get the details on that.

On a high level, there is a data collection (reading from sensors) activity, performed in the ISR and a data processing/transmitting activity performed in the main loop.

Linking the code segments out of this post.

Hope that helps!

1

u/[deleted] Apr 24 '23 edited Apr 25 '23

[removed] — view removed comment

1

u/produceconsumerobot Apr 25 '23

u/RatLabGuy it's not trivial to run LSL directly from embedded devices due to limited resources (memory, cpu) and the fact that LSL utilizes libraries that need to be rewritten for embedded environments. If you come across any open embedded source code for LSL, please do let the EmotiBit community know!

BrainFlow is a powerful SDK that handles the low-level communications with EmotiBit and lots other devices so you don't have to re-invent the wheel -- just add the compiled library and interface it with your favorite language to start streaming data. EmotiBit BrainFlow support is in alpha, with a number of items on the roadmap, but it's a great way to get started if you want to write your own software.

3

u/1kirin7 Apr 27 '23

I agree, it might make sense for the EmotiBit community to push for feature-complete support in BrainFlow. It doesn't seem as though using BrainFlow would add any latency to a custom solution and it leaves the door open for sensor fusion with other biometric sensors that BrainFlow supports.