Dual Remote Control

VEX V5 Technical Support
1

so currently my team and i are trying to do dual controls with robot c. the day i am posting this i am about 2 hours into robot c so i know almost nothing besides what i have found on the internet (YouTube and robotc.net) anyways i am trying to do dual controllers and between vex forums and another forum i have seen 2 possible ways to do it. [Ch2Xmrt2] and [Ch2DXmrt] with both of them not working, does anyone know how to get it to work? thanks!

2

@Alpha Entity
Could you post your code? I have found that the two biggest issues are that the partner controller is not properly connected and using a “or” statement.

3

so next time, im going to consult the hand book one of my teammates gave me… i just found what im looking for. thanks anyways!

4

@Alpha Entity

Ok, so you also want to add a:


task main()
{

	while(1==1)

	{
		motor[fl]= vexRT[Ch3];
		motor[ml]= vexRT[Ch3];
		motor[bl]= vexRT[Ch3];
		motor[fr]= vexRT[Ch2];
		motor[mr]= vexRT[Ch2];
		motor[br]= vexRT[Ch2];



		if (vexRT [Btn8U] ==1)
		{
			motor [ill] = 127;
			motor [irl] = 127;
		}
		else if (vexRT [Btn8D] == 1)
		{
			motor [ill] = -127;
			motor [irl] = -127;
		}
		else
		{
			motor [ill] = 0;
			motor [irl] = 0;
		}




wait1Msec(25);// This will add a 25millisecond wait to the while loop so the cortex has time to "think"
	}
}

which will make the while loop run much more smoothly. Make sure that all your while loops have a short delay so that the processor has time to think.

5

so add the wait even in driver control (DC) we dont want it to have like a stutter effect

6

@Alpha Entity
Yes, a 25-30 millisecond delay gives the cortex enough time to update the power to the motors. The cortex is not able to update the speed to the motors any faster than that, so you are making the cortex work much harder than it should be. Such a small time wait is unnoticeable to human drivers. Make sure that you use wait1Msec not wait10Msec. wait1Msec(25); will wait 25 milliseconds, while wait10Msec(25); will wait 250 milliseconds.

I don’t have the most technical explanation, but I hope it makes sense to you. If you have time later, you can look up some of the technical information about the refresh rates for the vex motors.

7

yup! makes sense to me i just dont want to be sitting there in DC stopping and going every short time. Thanks for the help!