You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Kind regards @mamo91 , your library has been quite useful for my current research.
I've run some tests and noticed that EMG data is being streamed at 50 Hz, as if only one of the four EMG characteristics is being read.
I would be most grateful if you can help me modify the code in two key aspects:
What numbers do I have to change in order to subscribe to filtered EMG data instead of raw EMG data? I haven't understood how these numbers match to the UUIDs explained in the MYO bluetooth protocol:
self.writeCharacteristic(0x28, struct.pack('<bb', 0x01, 0x00),True) # Subscribe to emg notificationsself.writeCharacteristic(0x19, struct.pack('<bbbbb', 1,1,1,3,1) ,True ) # Tell the myo we want all the data
How do I get the data from all four EMG characteristics? Here it seems as if the code only read one of the four characteristics. I believe the extra byte you mention is indicating which of the four is being read:
ifcHandle==0x27: # EMGdata=struct.unpack('<8HB', data) # an extra byte for some reasonifbusylog:
log.debug("got emg notification")
ev_type="emg_data"if"emg_data"inself.bindings:
self.bindings["emg_data"](self.myo, data[:8])
The text was updated successfully, but these errors were encountered:
Kind regards @mamo91 , your library has been quite useful for my current research.
I've run some tests and noticed that EMG data is being streamed at 50 Hz, as if only one of the four EMG characteristics is being read.
I would be most grateful if you can help me modify the code in two key aspects:
The text was updated successfully, but these errors were encountered: