-
Notifications
You must be signed in to change notification settings - Fork 11
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Implement actuators pipeline #104
Comments
This implementation is carried in feature/actuators. I realized defining and implementing a new I will proceed along this direction, and further cleanup as following can be updated during the code review, e.g., the current definition of castVectorOfSensorPtr() can be replaced by
that can be used with both the sensors and actuators. |
Following the addition of actuator related interfaces to Unlike the IWearWrapper that pools in all the available sensors information, and streams out the wearableData, the actuator To test the actuators pipeline I update the current implementation of the Paexo wearable device, with one motor actuator, that will facilitate us to do the activities related adaptive paexo. The pipeline for the actuators implementation is as shown below: and I wrote a simple test application to send the motor actuation commands to the Paexo wearable device, and tested wearable.actuator.test.mp4CC @lrapetti @evalli-iit @diegoferigo @claudia-lat @traversaro @claudia-lat |
Thanks @traversaro for the support in understanding how thrift header files are handled, and how to handle the library built from thrift files 2273d01 2273d01 |
Monday @claudia-lat and I will perform further testing with the Adaptive Paexo. |
Done in 915aec2, we could not run the hardware to perform tests on it. However, with the test application the move command for motor actuation seems to be parsed correctly simplescreenrecorder-2021-01-25_11.48.31.mp4 |
Following the discussion on how to update wearables library with actuators related pipeline #103, this issue tracks the implementation details related to it.
After the update from the meeting #103 (comment), we start with the actuators interface implementation first.
IActuator
interface will be similar to the ISensor. Considering only a haptic actuators, we start withIHaptic
interface, that inherits fromIActuator
with set and get (may be not so relevant for a haptic actuator, TBD) methods for the actuation commands. This choice is driven by the haptic actuators we are currently using in some of the projects. The actuation depends on acommand
that indicates how the haptic actuator buzzes i.e. the magnitude and duration of actuation.The text was updated successfully, but these errors were encountered: