You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The hope is that this program can be used by the design team for all their prototyping needs. In order to help accommodate this, we should use the rest of the ports on the brain for more individually controlled motors.
In order to expand the usefulness of this program, we might need to revisit the control scheme. Simpler may be better.
The text was updated successfully, but these errors were encountered:
Should these other individually controlled motors be placed in pairs of 2 motors in a group? I'm only trying to narrow this down but I think a reworking of the program's manual functions such as joystick control and button control would have to be done to accommodate this change.
However, it would be harder to implement flexible testing since there could be edge cases where some part of the robot doesn't want to be run at full power whether that be due to inaccuracy or possible damage to parts. Otherwise, prototyping would still involve having to either change the values inside the program while testing. There are workarounds with variable changing the speeds of the motors through a second controller mayhaps if we want to house more control options such as L/R 1/2 or arrow buttons.
The hope is that this program can be used by the design team for all their prototyping needs. In order to help accommodate this, we should use the rest of the ports on the brain for more individually controlled motors.
In order to expand the usefulness of this program, we might need to revisit the control scheme. Simpler may be better.
The text was updated successfully, but these errors were encountered: