Answered: Lost link between Cortex & Joystick(Computer)

[tedlawson]

Here's what happened:
I had 2 encoders plug in adjacent digital ports. (Using RobotC)
When configured like this a simple program such turning the motors on then off when a bumper is pushed will freeze leaving the motors running and the remote screen gives up a "Failure to read brick status" message.
Turning the controller off and then on to reboot the program will find the motors still running.
Trying to re-download the program fails.
Then the VexNet link fails either wifi or tethered (tried to relink via the tether).
My Joystick is sitting read with the Robot LED blinking slow green and the controller Game LED blinking fast green and I am unable to access the controller in any way.

This happened once before and after leaving it alone for a couple of days I turn the units on to find the link established.

I experimented and found that the adjacent encoders were causing (or one of the causes) the problem.

Batteries are good. Five years with Vex. An experienced programmer. But stuck on this one & left with inoperable equipment.

[Ricky Torrance]

Try using the VEXnet Firmware Upgrade Utility Tool on your Joystick to get it going again. Instructions come inside the zip file.

[tedlawson]

Did the upgrades (again) on both the joystick & controller. Same thing: no communication when tethered (does not link) or WiFi. Joystick Robot LED still flashing slow Green and controller Game LED flashing fast.

Funny thing is, that little motor test program still runs when the controller switched on?

If it is a hardware problem can I return it for repair?

[Ricky Torrance]

What happen when you ran the Upgrade Utility? Did you get the green window that states: “VEXnet is up to date / No Action required?

Also make sure you are running the latest version of ROBOTC - Version 2.20.1 BETA.

If you can not get it working, you can call our office and get a RMA Number for the return of the product for repair.