NeuroTechX / NeuroTechX/EEG-ExPy
extra electrode not visible with Muse2 and Bluemuse?
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 575
- Forks
- 153
- Avg merge
- 6h 44m
- Merged PRs (30d)
- 3
Description
ℹ Computer information
- Platform OS (e.g Windows, Mac, Linux etc): Windows
- Python Version: 3.7
- Brain Interface Used (e.g Muse, OpenBCI, Notion etc): Muse2 with Bluemuse
📝 Provide detailed reproduction steps (if any)
- Created extra electrode with mini usb 5 pins (https://hackaday.io/project/162169-muse-eeg-headset-making-extra-electrode/details)
- Connected the Muse2 with Bluemuse
- Started muse-lsl
✔️ Expected result
See the AUX channel
❌ Actual result
Not see the aux channel.
The Bluemuse page https://github.com/kowalej/BlueMuse says
Muse 2 has AUX channel disabled - if I try to stream from this channel I get errors. It looks like no data comes from the channel when debugging Bluetooth inside a sniffing tool, so I'm making the assumption that Muse 2 doesn't actually support the AUX (secret electrode) input - it just has a (non functioning) GATT characteristic which is the same UUID as the Muse (2016).
Confirmed? Or is there a workaround? Is there an alternative to Bluemuse for windows? Anyone else encountered this issue?
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No repository file or test is named. Start by reproducing the Muse2/Bluemuse steps on Windows and tracing how muse-lsl discovers channels, then compare the AUX behavior with the Bluemuse report. Done means confirming whether Muse2 AUX is supported and identifying a verified workaround or documenting the limitation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- embedded-iot
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100