Tags : :
Software developers may want to work on the firmware of the Ada hand, but may not want to purchase a whole hand, or indeed any of the custom components for the Ada hand. Without the physical hardware, it can be hard to test software changes to see if they work, or to debug code as you go.
To find a way for a software developer to work on the Ada robotic hand firmware without actually having an Ada hand and still being able to debug and test their code.
1. Must be able to fully test firmware code as if it were running on Ada
- See problem section
- Designed to be a cheap way for someone to experiment with firmware
- Must make life easier for a typical programmer
- Since the original Ada hand is released under the this license, any derivatives must be distributed under the same license.
To design and program a piece of standalone simulation software to run on a desktop computer, which will graphically show the Ada hand and animate it, simulating the movements that the motors would be performing if it were a real Ada hand. Since the firmware can run on a standard arduino microcontroller (a very affordable and readily available component) programmers wouldn't need the specialist PCB or mechanical components of the hand to begin working on the firmware. The simulation software would communicate via a USB based serial connection to the Ada hand, receiving information about where the fingers should move to and returning information about where they have moved to in the simulator.
1. The simulator should graphically show the Ada robotic hand using a 3D model.
2. The simulator should run on Windows, MACOS and Linux machines.
3. The simulator should utilize a USB serial connection to transfer data.
4. The simulator should receive target motor speed commands from the microntroller.
5. The simulator should send the current position of the motor.
6. The simulator should not interfere with the standard serial communication of the microcontroller, and the user should still be able to send and receive the standard serial commands of the firmware.
1. Create a custom "fingerlib.h" for the simulator called "fingersimlib.h" to run on the microcontroller alongside the firmware which forwards target motor speed commands to the USB serial port.
2. Format these additional commands with a descriptor, so that the simulator can interpret these commands correctly and remove them from the main body of the serial data, leaving the normal serial data untouched so that normal communication between the computer and microcontroller via USB serial can occur.
3. It may be necessary to include a high level serial communication text box within the simulator so that it can effectively add and remove simulator data from the serial string and maintain the standard serial commands.
Last Edited By: JoelGibbard Jan 21 16 5:31 PM. Edited 7 times