-
Notifications
You must be signed in to change notification settings - Fork 7
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
Develop serial Dextra device #176
Comments
Should match firmware at https://github.com/jgagom/Dextra |
May work. Relevant changes: 400ea3d...4b85d31 |
Blocks #171. |
On a side note, planning on moving the current USB implementation. Tracked at https://github.com/roboticslab-uc3m/sign-language-papers/issues/5 (private and subject to name change; name changes are documented here (perma and the upcoming ones are tracked at "Organize research-oriented repos roboticslab-uc3m/questions-and-answers#75"). |
Merged into develop at 11a1b22, updated title and description of this issue. Current status:
|
Let's do #171 first. |
Sorry, switching back (and actually stating this explicitly in the title) to USB device per the original intent. We are not yet close to developing the CAN device, the USB one needs polishing. |
@jgvictores OK to rename DextraControlboardUSB to DextraSerialControlboard? Future CAN device would be DextraCanBusControlboard or so. |
Seemed uncontroversial to me. Done and ready for review at #216. |
WIP at https://github.com/roboticslab-uc3m/yarp-devices/compare/issue-176-dextra
Edit (2019/06/28): two different device implementations will coexist at some point per #176 (comment). This issue focuses on the USB-related stuff, the CAN implementation depends on other tasks (e.g. PCB design, hardware, etc.).
The text was updated successfully, but these errors were encountered: