Description

The EmotiBits can now be identified by the EmotiBit serial number (unique to every emotibit) on the oscilloscope

Requirements

To test the functionality, you will also need to flash the EmotiBit with the FW linked in the PR below.

The flow of information is shown below
- EmotiBit -> EmotiBitWiFiHost (Oscilloscope) -> EmotiBit Oscilloscope (ofApp) -> GUI
Since the EmotiBit info data enters the Oscilloscope via WiFiHost, a new map has been created to store EmotiBit Info.
- unordered_map<string, EmotibitInfo> _discoveredEmotibits;
New EmotiBits when discovered are added to this data structure.
If the EmotiBit transmits a device ID, then that is used as the "key". If no device ID is found, then the IP address is used as the key.
- Example:
- _discoveredEmotibits[192.168.1.100] = {IP address, availability, lastSeen} (for old firmware)
- _discoveredEmotibits[MD-V5-0000100] = {IP address, availability, lastSeen} (for new firmware)
This data structure also allows extensibility, as it can hold additional information about EmotiBits on network like name, Fs. FW version etc.
The structure is updated periodically by the advertising channel (thread).
The structure is then pulled by the ofApp, where the "key" is used to populate the deviceGroup list.

Test Configuration:

Test	Result	Link

[ ] All dependent repositories used were on branch master
Software
- [x] Passed testing on Windows
- [ ] Passed testing on macOS
- [ ] Passed testing on linux (ubuntu)
Firmware
- [ ] Set testingMode to TestingMode::NONE
- [ ] Set const bool DIGITAL_WRITE_DEBUG = false (if set true while testing)
- [ ] Update version in EmotiBit.h
- [ ] Update library.properties to the correct version (should match EmotiBit.h)
[ ] reset log_level
[ ] Update software bundle version in ofxEmotiBitVersion.h
[ ] doxygen style comments included for new code snippets
[ ] Required documentation udpated