Week 31 – Testing the Network
The main goal this week was to test how the robot reacts to commands in different situations.
First, I checked how it performed without modifying anything. The robot tends to turn to the right even when it is supposed to stay still or move in a straight line. This issue could be addressed with a higher-level movement manager that is aware of the robot’s position and can correct its direction.
In its current state, the robot is functional, but not yet useful for real tasks. In particular, it needs to properly handle arm control. To study this, I tested three different configurations:
- Keeping the arms in the default position
- Not controlling the arms at all
- Controlling one arm manually
Keeping the arms in the default position
In this test, I modified the code to continuously send the default arm position. This is based on how the network computes commands using the formula:
default_pos + action * scale
By setting the scale to 0, the network’s output is effectively ignored.
In this configuration, the robot is not able to maintain a stable position and performs erratic movements. However, it is still able to execute commands correctly, so with a higher-level controller (as mentioned above), it could be properly managed.
Not controlling the arms at all
In this case, I stopped sending any commands to the arm topics, so the motors remain inactive.
Here, the robot performs better than in the default mode. Although the difference is not very noticeable during active control, when the command is to stay still, the robot remains more stable and avoids the slight rightward turning observed before.
Controlling one arm manually
Finally, I stopped sending network commands and manually controlled one arm.
As soon as the arm is raised, the robot loses balance and enters a falling state. It begins to move in the direction the arm is pointing. In this condition, the robot cannot be properly controlled, especially if the goal is to move in the opposite direction of the arm, since it is unable to compensate for the imbalance.
Summary
- Tested the network under different arm-control configurations
- Identified stability issues related to arm movement and default control