We have noticed since the last update that our code does not always execute sequentially. For example, if we program the claw motor to close the claw followed by move backwards, the
program executes the move backwards first and then closes the claw (so the object is left behind).

Hi there,

Could you please post your code here so we can take a look at this?

= Xander

Keep receiving a notification error that my file is an .rbg and it cannot be attached.

zip it up and attach it

Here is the zip file.

Is there a specific reason you're using a setMultipleMotors block and not a simple forward block as the first statement in your program?

= Xander

Feel like teaching the students to always start with set motors is good programming.

So the program you uploaded is telling the robot to do the following behavior
Drive forward continuously while lowering, raising and then lowering the arm
then drive backwards a small amount
open the claw
drive backwards a small amount again


This is also how the robot seems to be behaving when I test it. What are you trying to make the robot do exactly? Should those move motor blocks be the clawMotor or is there a reason the arm is lowering, raising and then lowering again?

Tested in RobotC 4.32

Please explain why the claw motor moves as the last step to the program when move backwards is the last command.

This is not the behavior I am seeing so it is hard to debug from my end. I have a couple ideas though

If the claw is getting stuck trying to open than it might never get to the second backward command. Does the program end on your robot?

Yes. The robot executes the backward command and then the claw motor performs an action that is not programmed.)