ROBOTC DOCUMENTATION UPDATE
ROBOTC DOCUMENTATION CODE

You were NOT looking at the actual variables that control which case gets selected! Those variables are leftEncoder and rightEncoder.Īnd again, final warning - it looks like you're counting on things like motor and nMotorEncoder to be function names or keywords that do something, because otherwise it just looks like you enter an infinite loop that never actually writes any values to the motors. This is one of the tricky things with debugging - you have to be looking at the correct variables! In your video, you are looking at leftMotor and rightMotor, and what appears to be fields for those motors. Int rightEncoder = abs(nMotorEncoder) // leftEncoder)īy adding the two lines inside the while loop, now you are checking and updating the encoder counts every time you step into a new loop. So, that said, try using the following: void GOforwards() I don't know about VEX robotics, but I'll caution you that your left and right encoders are based on nMotorEncoder and, just like how leftEncoder and rightEncoder doesn't get updated anywhere in your loop, nMotorEncoder doesn't get updated anywhere either. The exception might be if those variable names are actually protected variable names that have special meaning in your development environment - more on that later.

ROBOTC DOCUMENTATION UPDATE

The problem seems to be that maybe you're thinking that the left and right encoder values will update automatically, but that is generally not the case. It looks like you don't ever update the encoder values after you initialize them.

ROBOTC DOCUMENTATION CODE

much less why it runs off into oblivion when the code should exit the while loop once the right encoder's absolute value exceeds 2000. I am not sure why the power to the wheels never changes, or why it seems to believe that the Encoder values are equal. This is a video of the code running from the debugger windows: When I run the code my robot runs without stopping and the Encoder values diverge quickly. *!!Code automatically generated by 'ROBOTC' configuration wizard !!*//

#pragma config(Motor, port10, rightMotor, tmotorVex393_HBridge, openLoop, reversed, driveRight, encoderPort, I2C_2) #pragma config(Motor, port1, leftMotor, tmotorVex393_HBridge, openLoop, driveLeft, encoderPort, I2C_1) #pragma config(Sensor, I2C_2,, sensorQuadEncoderOnI2CPort,, AutoAssign ) #pragma config(Sensor, I2C_1,, sensorQuadEncoderOnI2CPort,, AutoAssign ) This is my code: #pragma config(I2C_Usage, I2C1, i2cSensors) VEX File ManagementFrom the file management utility, you can.I have a standard VEX Clawbot, which I've been trying to make go straight for some time. Returns a true if there is space available, false if the queue is full.VEX File ManagementThe file management utility allows you to see all of the programs, sound files and other files that are loaded on your VEX. Set bPlaySounds to true to unmute the VEX.The #define shortcuts are also acceptable: MuteSound() UnmuteSound() Sound QueueThe VEX has an internal queue in order to line up sound commands.This queue will automatically process any waiting sound commands, in order that they are received.You can override/check on the queue with the following commands:PlayImmediateTone(frequency, durationIn10MsecTicks) This command will force the playTone command to jump ahead of the queue.bSoundQueueAvailableA Boolean Variable to check if the sound queue is full.

Set bPlaySounds to false to mute the VEX. Returns true if a sound is playing, false if no sound.bPlaySoundsA Boolean variable to mute the VEX. Use the File Management Utility for downloading sound files onto your VEXRobot Advanced Tools File ManagementPlaying SoundsPlaySound(sound) Plays a specific sound effect that is pre-programmed into the VEXsoundBlipsoundBeepBeepsoundDownwardTonessoundUpwardTonessoundLowBuzzsoundFastUpwardTonessoundShortBlipsoundExceptionsoundLowBuzzShortSound VariablesbSoundActiveA Boolean variable informs the user if the VEX is actively playing a sound.

Playing Sounds PlayTone(frequency, durationIn10MsecTicks) Example: PlayTone(440, 10) Plays a 440hz note for 100ms.PlaySoundFile(fileName.wav)Will play the sound file fileName.wav. ROBOTC SoundsROBOTC with the VEX has a speaker port available on it for playing basic and polyphonic tones.You can play the follow types of sounds:A specific note PlayTone() A system sound PlaySound() A user loaded sound file (.wav) PlaySoundFile()

Robotc documentation