Improving the moteus update rate, part 2
Back in part 1, I looked at the driving factors that limited the update rate of the full quadruped. Now in part 2, I’ll cover the first half of the solution.
Background
To begin with, there were two major paths that I could take based around the network topology. In one path, I would remove the active bridging capability from the junction board, and rely on the Raspberry Pi to drive all the servos directly, and in the other the active bridge would stick around. There were a number of key disadvantages to both approaches:




