disconnecting remote to cortex please help!!!

You don’t have to use the comp template. In fact, it caused me issues. You only really have to if you want to use autonomous mode. I had to scrap that, but htat’s a whole different story.

can u explane how to do it

can u check my code i put it in comp form

#pragma config(Motor, port2, frontRightMotor, tmotorVex393_MC29, openLoop, reversed, driveRight)
#pragma config(Motor, port3, frontLeftMotor, tmotorVex393_MC29, openLoop, driveLeft)
#pragma config(Motor, port4, backLeftMotor, tmotorVex393_MC29, openLoop, driveLeft)
#pragma config(Motor, port5, backRightMotor, tmotorVex393_MC29, openLoop, reversed, driveRight)
#pragma config(Motor, port7, clawMotor, tmotorVex393_MC29, openLoop)
#pragma config(Motor, port8, armMotor1, tmotorVex393_MC29, openLoop)
#pragma config(Motor, port9, armMotor, tmotorVex393_MC29, openLoop)
//!!Code automatically generated by ‘ROBOTC’ configuration wizard !!//

/---------------------------------------------------------------------------/
/* /
/
Description: Competition template for VEX EDR /
/
/
/
---------------------------------------------------------------------------*/

// This code is for the VEX cortex platform
#pragma platform(VEX2)

// Select Download method as “competition”
#pragma competitionControl(Competition)

//Main competition background code…do not modify!
#include “Vex_Competition_Includes.c”

/---------------------------------------------------------------------------/
/* Pre-Autonomous Functions /
/
/
/
You may want to perform some actions before the competition starts. /
/
Do them in the following function. You must return from this function /
/
or the autonomous and usercontrol tasks will not be started. This /
/
function is only called once after the cortex has been powered on and /
/
not every time that the robot is disabled. /
/
---------------------------------------------------------------------------*/

void pre_auton()
{
// Set bStopTasksBetweenModes to false if you want to keep user created tasks
// running between Autonomous and Driver controlled modes. You will need to
// manage all user created tasks if set to false.
bStopTasksBetweenModes = true;

// Set bDisplayCompetitionStatusOnLcd to false if you don't want the LCD
// used by the competition include file, for example, you might want
// to display your team name on the LCD in this function.
// bDisplayCompetitionStatusOnLcd = false;

// All activities that occur before the competition starts
// Example: clearing encoders, setting servo positions, …
}

/---------------------------------------------------------------------------/
/* /
/
Autonomous Task /
/
/
/
This task is used to control your robot during the autonomous phase of /
/
a VEX Competition. /
/
/
/
You must modify the code to add your own robot specific commands here. /
/
---------------------------------------------------------------------------*/

task autonomous()
{
motor(backLeftMotor) = 127;
motor(backRightMotor) = 127;
motor(frontLeftMotor) = 127;
motor(frontRightMotor) = 127;
wait1Msec(4000);
AutonomousCodePlaceholderForTesting();
}

/---------------------------------------------------------------------------/
/* /
/
User Control Task /
/
/
/
This task is used to control your robot during the user control phase of /
/
a VEX Competition. /
/
/
/
You must modify the code to add your own robot specific commands here. /
/
---------------------------------------------------------------------------*/

task usercontrol()
{
while(1==1)
{
motor[backRightMotor] = vexRT[Ch2];
motor[frontRightMotor] = vexRT[Ch2];

motor[frontLeftMotor] = vexRT[Ch3];
motor[backLeftMotor] = vexRT[Ch3];

if(vexRT[Btn6U] == 1) //If button 5U is pressed…
{
motor[armMotor] = 127; //…raise the arm.
}
else if(vexRT[Btn6D] == 1) //Else, if button 5D is pressed…
{
motor[armMotor] = -127; //…lower the arm.
}
else //Else (neither button is pressed)…
{
motor[armMotor] = 0; //…stop the arm.
}
if(vexRT[Btn6U] == 1) //If button 5U is pressed…
{
motor[armMotor1] = 127; //…raise the arm.
}
else if(vexRT[Btn6D] == 1) //Else, if button 5D is pressed…
{
motor[armMotor1] = -127; //…lower the arm.
}
else //Else (neither button is pressed)…
{
motor[armMotor1] = 0; //…stop the arm.
}

// Open, close or do not more claw
if(vexRT[Btn5U] == 1) //If Button 6U is pressed…
{
motor[clawMotor] = 127; //…close the gripper.
}
else if(vexRT[Btn5D] == 1) //Else, if button 6D is pressed…
{
motor[clawMotor] = -127; //…open the gripper.
}
else //Else (neither button is pressed)…
{
motor[clawMotor] = 0; //…stop the gripper.
}
}

}

that may have solved the problem we shall see

Im a little rusty on RobotC, but the code looks fine to me. The only thing I would change is instead of saying this

if(vexRT[Btn6U] == 1) //If button 5U is pressed…
{
motor[armMotor] = 127; //…raise the arm.
}
else if(vexRT[Btn6D] == 1) //Else, if button 5D is pressed…
{
motor[armMotor] = -127; //…lower the arm.
}
else //Else (neither button is pressed)…
{
motor[armMotor] = 0; //…stop the arm.
}

for each individual arm motor, you could put them together and say this

if(vexRT[Btn6U] == 1) //If button 5U is pressed…
{
motor[armMotor] = 127; //…raise the arm.
motor[armMotor1] = 127;
}
else if(vexRT[Btn6D] == 1) //Else, if button 5D is pressed…
{
motor[armMotor] = -127; //…lower the arm.
motor[armMotor1] = -127;
}
else //Else (neither button is pressed)…
{
motor[armMotor] = 0; //…stop the arm.
motor[armMotor1] = 0;
}

Your original code shouldn’t have any issues, this is just to give you better coding habits.

that is for 2 seprate motors thats why i have the two seprate because they are difrant types of the robot

i will be able to post photos today

if a pct is triped will all the motors connected start jitering because if that happens thats the problem???

That could be a symptom. When they’re called to move, they don’t really do what they’re supposed to and instead just kind of stutter along.

yes that is exactly what is happing so thats right the pct is being triped

The you move the ports, and see if that fixes the issue.

ok thanks what would u recomend the ports be moved to???

Because it looks like most of your strain is on the drive, I would put front right and front left in ports 9 and 8, and back left and right in 2 and 3. If your “arm” doesn’t need to draw much power to move, those motors should be on the same ptc, say port 6. And the claw can be on 5.

thanks

ok here are photos

here are the photos sorry
WIN_20190205_12_36_33_Pro.jpg
WIN_20190205_12_36_43_Pro.jpg
WIN_20190205_12_36_54_Pro.jpg
WIN_20190205_12_37_05_Pro.jpg

thanks @Got a Screw Loose
the changing ports worked now i can compete

for your drive you definitely need to support that axle on two points

what do u mean by that???

He meant that you should support your wheels on both sides, rather than just 1. It’s not a huge deal, but it’s helpful. When is your event? How much time do you have?