Programming our robot, I saw I had some limitations about the correct visualizing of this. In particular, the standard view does not consider the offset between the robot center, as the middle point of all robot sides, and the wheel center, so the middle point of the drivetrain.
While programming, is important to know both this aspects, because many times you need to know how your robot is moving in the field and how far is a specific part of this, such, for example, the intake for the current season, by a point of the field, such the artifacts in the autonomous period.
I think and hope an implementation like this one could help many teams in coding their autonomous path with PedroPathing.
Thanks, and sorry for my bad english explanation
Programming our robot, I saw I had some limitations about the correct visualizing of this. In particular, the standard view does not consider the offset between the robot center, as the middle point of all robot sides, and the wheel center, so the middle point of the drivetrain.
While programming, is important to know both this aspects, because many times you need to know how your robot is moving in the field and how far is a specific part of this, such, for example, the intake for the current season, by a point of the field, such the artifacts in the autonomous period.
I think and hope an implementation like this one could help many teams in coding their autonomous path with PedroPathing.
Thanks, and sorry for my bad english explanation