What language did you use?
How does the robot receive/transmit commands? Please be very specific.
So we are on the same page. I was thinking that RACO GUI should be developed with:
- multi-threading
- multi-client/server connections
- UDP thread for video
- TCP thread for commands
- all on different ports. duh
- simple serial communication, possibly UART cause it's simple
- MAYBE bluetooth module to transmit commands through my phone that has good web connection
- initial login screen that makes the password part of the transmitted packet
- this packet is parsed at RACO's end and if the password/key does not match then trash the packet
- video display
- sensor/motor display
- if electrode sensor sleeve is being used to control the robot then display electrode sensor status
- Please post more ideas!
Explanation of protocol: So we need TCP packet transmission for the commands. Why? Because we need it to be reliable!(remember little kids. lol) Since we do not want to receive garbage on the receiving end of RACO and quite possibly spit out some random ASCII characters(garbled binary code), that can enable an odd arm movement and might just damage a kid or worse RACO, we will adopt TCP!

The cool thing of the GUI is that we can also receive data directly from RACO and provide us with the robot state such as battery status, axis rotation, sensor reliability, video, thresholds(electrodes) going off and the such. This is turning out to be quite an interesting project! Thanks for contributing Jaime!



