Autonomous Acting Weirdly

[jpearman]

Well, hard to test without a robot. But the first thing to fix is this.

void usercontrol(void) {
  while(!autonSelected){
    Controller1.ButtonLeft.pressed(autonChanger);
    Controller1.ButtonA.pressed([]() -> void {
      autonSelected = true;
      Controller1.ButtonLeft.pressed([]() -> void {});
      Controller1.ButtonA.pressed([]() -> void {});
    });
    autonDisplay();
    wait(100, msec);
  }

assume you want to select an autonomous before connecting to field control, however, that loop is registering the ButtonLeft.pressed and ButtonA.pressed events many times. You must only register event handlers once.

also

Controller1.ButtonLeft.pressed([]() -> void {});

you cannot unregister an event handler unless you stop all tasks when the robot becomes disabled by setting bStopAllTasksBetweenModes to true.

see this post, make necessary changes and then see what happens.

Competition code - common mistakes

ok, now that I fixed the spelling of competition in all the screen shots first topic is incorrect use of event handlers, something we have covered before but it seems everyone forgets. The symptom is that, for example, an event handler on a controller button sometimes works and sometimes doesn’t. At worlds the most common use was for firing pneumatics, a button push to set one state and a second button push to revert back to original state. simple code for a callback could look as…

also this topic.

Competition code and user created tasks

We’ve had some feedback recently from teams who have had issues with competition control. I’ve looked at some of the team code and noticed that often problems are being caused by tasks started in either the driver or autonomous section of the program being allowed to run during the other phase of the match. This can occur with programs written in either VEXcode or PROS (and I assume RobotMesh, but I’m not planning to specifically discuss that programming environment in this topic) although the…