Forum

Yup, he kind of jumps around a lot in his code. He was trying to keep the graphic display linked with the robot motion. The tricky part is trying find out where he actually takes the input from the screen, translates it into angles and SENDS that to the board. As I mentioned, I found two of them, but not the other two… I’ll have to hunt more for it. If I do find the solution, I’ll post a component that allows direct control for other’s benefit. Worst case I guess I could write the Ruby code for talking directly with the board.