Hi,
We upgraded to RobotC 1.97 for use with VEXnet. After the competition, we had to return the VEXnet loaner. Now when we try to connect the Crystal Receiver to the RX1 port, the corresponding LED does not go on. This also fails with the tether cord.
What am I missing?
Rob
At the current time, you should use the older version of ROBOTC for use with Crystals - version 1.04.
Starting with a microcontroller that was successfully used with RobotC 1.97 and VEXnet. Batteries are freshly charged.
Install RobotC 1.40 on computer (I assume you meant 1.40 rather than 1.04)
Connect orange cable to microcontroller and turn it on.
Battery LED is rapidly blinking, internal yellow LED is blinking. All other LEDs are off.
Select Robot->Download IFI Master CPU Firmware
Select VEX_MASTER_V7.BIN (included with RobotC 1.40)
Download was successful
Select Robot->Download Firmware
Select VEX VM0752.hex
Download was successful
Turn microcontroller off
Connect transmitter to microcontroller using the tether cord.
Turn transmitter and microcontroller on
Microcontroller Power and RX1 Status LEDs rapidly blinking, internal yellow LED is off
Compile and load a program. Successful.
Click Start in the Program Debug window
Power LED stays on, RX1 Status goes off, internal yellow LED blinks.
Transmitter does not control the motors.
Yes, the program was worked using RobotC 1.97 and VEXnet.
Anything else I can try?
Rob
If the Yellow LED is blinking on the VEX 0.5 Microcontroller, it indicates you are in Autonomous Mode; therefore, you would not be able to control Motors from the Transmitter until the Autonomous Mode has ended.
I am not using the competition template, and thus do not have an autonomous mode. I am also using the tether cord.
The code is basically;
task main() {
while (1) {
motor[port1]=vexRT(Ch1);
etc.
}
}
How is the microcontroller getting into autonomous mode?
What am I missing?
At about what rate is the Yellow LED blinking?
Trying the code you posted, always invokes Autonomous Mode. To correct this, you can use the sample program “Dual Joystick Control.c” or “Single Joystick Control.c” located in your RobotC Radio Control Transmitter directory as a starting point.
I found out what is happening.
The default value of bVexAutonomousMode under RobotC 1.97 with VEXnet is TRUE.
The default value of bVexAutonomousMode under RobotC 1.97 with Crystals/tether is FALSE.
**Use the Dual Joystick Control.c or Single Joystick Control.c as a starting template if you do not need an autonomous portion, as in the Driver Challenge.
Use the Vex_Competition_Template.c as a starting template if you want Autonomous, like the regular tournament or the Autonomous challenge.
This works using crystals or VEXnet. Tests were done with RobotC 1.98.1, master code VEX_MASTER_V10.BIN and user shell VEX VM0785.hex.**