The BLED112 dongle allows the Myo to work on any operating system as it acts as a COM port that forwards serial commands send to it over Bluetooth.

One reason why it's worth doing this is due to the poor cross platform BLE support, however bleak (Bluetooth Low Energy platform Agnostic Klient) may solve this and allow people without a dongle to use pyomyo.

This feature would also act as a stepping stone for makers of open source BLE EMGs to add support for their hardware to pyomyo.

Thankfully, Thalmic Labs released (most of the) the specification here.

Hi
Is there a way that I collect both IMU and EMG data at the same time?

Hi,
I am running a project that uses the Myo armband to control several servos. I have noticed that sometimes the Serial read on line 124 of the pyomyo.py file does not complete or timeout and therefore the program hangs.

Perhaps setting a timeout on the Serial may help avoid this?

This was started in the Spectrogram branch and is completed for one channel, although I am not sure about the correctness of my method.
Needs moving to all 8 channels and rebasing.

Both feature engineering and preprocessing of EMG data will likely be added for any significantly difficult project using pyomyo. If so it would be nice to contribute these implementations back so that efficiency improvements/bug fixes can be shared.
It would be nice to include a metrics.py file containing implementations and a plot_metrics.py file that can give some intuition on what each feature captures.

Some examples of metrics to include are Mean Absolute Value (MAV), Root Mean Square (RMS), Willison Amplitude (WAMP), Waveform Length (WL) and Zero Crossings (ZL). More info can be found in this paper for different metrics.
My hope was to implement them and create a notebook showing their feature importance's for different tasks and models but have not had the time so far.

Hi guys, I wonder did anyone encountered with after run self.run method for minutes, no data came out then. I have done some debugger work, and found that it's the line c = self.ser.read() in the method recv_packet of the BT class stuck.
Any ideas? Is the device disconnected after certain time?

def recv_packet(self):
  n = self.ser.inWaiting() # Windows fix
  
  while True:
	  c = self.ser.read()
	  if not c:
		  return None
  
	  ret = self.proc_byte(ord(c))
	  if ret:
		  if ret.typ == 0x80:
			  self.handle_event(ret)
			  # Windows fix
			  if n >= 5096:
				  print("Clearning",n)
				  self.ser.flushInput()
			  # End of Windows fix
		  return ret

Sensor positioning is hard and solving it is part of solving cross session generalisation, although there are fancy techniques that can be performed after the data is gathered, it would be worth having a discussion on the simple things. Here are some of my rough thoughts:

Calibration Methods

Once a placement is chosen, originally I would sharpie an outline of the whole Myo on my hand. It's important to mark the position of each sensor pod, not just one. The Myo can both rotate around the arm, move up and down, or tilt up and down.

One simple way I calibrate is by placing the Myo on my proximal forearm of my right hand, waving my wrist right and then making sure this movement only peaks one channel, e.g. channel 3.
If the movement peaks two channels, I know the relevant muscle is in-between 2 EMG sensors and then rotate the Myo slightly to minimise cross talk and maximise the amount of the signal only picked up by channel 3.

Once this placement was used a kNN classifier can be trained on relevant gestures, e.g. 5 finger flexion. Then next session, after manual calibration is attempted it can be fine tuned until the kNN classifier works.

Search for something better, or at least more scientific

Some tools could be made to tell the user to rotate the Myo and show the user how similar the readings are to the previous data gathered.
Adding live PCA plotting to the live classifiers with a print out of between/within group variance may help quickly tryout different positioning for different gestures.