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
{{ message }}
This repository has been archived by the owner on Jul 19, 2022. It is now read-only.
The classifier event myohw_classifier_event_arm_unsynced = 0x02 contains a rotation/orientation value of the Myo on the users arm.
It's not specified in the Myo Bluetooth protocol but in the debugger it can clearly be observed that the event contains byte[6] of data. The undocumented data is current "WarmUpState" and the previously mentioned rotation/orientation.
There is some more information in another Myo library project for OSX. Here and here.
A comment there states:
/// Retrieve the estimated rotation of Myo on the user's arm after a sync.
/// The values specifies the rotation of the myo on the arm (0 - logo facing down, pi - logo facing up)
I did not get any meaningful values around 0 or pi during tests though.
The text was updated successfully, but these errors were encountered:
Kinda sounds like it'd be how they map a spy camera app. Flip up it can see and here, down it can only hear and on it can do both while messuring how psychically active you're being.
The classifier event
myohw_classifier_event_arm_unsynced = 0x02
contains a rotation/orientation value of the Myo on the users arm.It's not specified in the Myo Bluetooth protocol but in the debugger it can clearly be observed that the event contains
byte[6]
of data. The undocumented data is current "WarmUpState" and the previously mentioned rotation/orientation.There is some more information in another Myo library project for OSX.
Here and here.
A comment there states:
I did not get any meaningful values around 0 or pi during tests though.
The text was updated successfully, but these errors were encountered: