testing basic socket functions
Send 10 10-character strings to represent control data
multijoystick now relies on control_server to send joystick data to the client
(the client currently only converts the values to human-readable)
Old joystick event handling was filling up network buffer,
leading to major latency.
This approach polls the joystick for values instead of sending
a packet everytime something happens.
Constant stream of polled joystick data.
now constantly attempts to reconnect, handles Atti/Manual switching
Works via SSH tunnel with <.5s latency (will write precise latency tests)
Arm motors - hold button 12
Scaled control values to half sensitivity
Failsafe sets throttle to 40%, all others to center (if communication is lost for a certain amount of time)
And more.
Faster failsafe, joy_control loops if it errors out, attempts to reconnect.
Need to set control_client to clear socket cache on reconnect.
Update README with warnings.
fixed error in arduino code
client from Pi
Scripts will endlessly try to speak with each other.
WARNING - you will have to SIGKILL to stop these.
Timeout set on receiving end so that if no data is received, the socket is closed and recreated.
whoops
Added condition to not have failsafe increase throttle if it is already below 35%
Forgot to map the value to microseconds
Removed unnecessary file.
Modified Readme