For the last 2 weeks I have been unable to download wirelessly through RobotC. :mad:
I have updated the Cortex Master Firmware, as well as the RobotC firmware. The joysticks and the VexNet Keys (white) are on the latest version as well.
I am getting the error: “ABORTED. Unable to read file system table from robot.”
I am using RobotC 4.27.
Thank you in advance! 
There are a couple of things I would like for you to try in order to trouble shoot this issue. I know some of these steps may be redundant, but I would like to ensure that we start from a solid, known point and none of the crucial (but easily missed) steps have been skipped.
-
First, please redownload the firmware to the VEXNet 2.0 keys using the VEXNet 2.0 Key Firmware Upgrade Utility (link below). Please also record what firmware version is being used on the VEXNet keys.
-
Next, open ROBOTC and confirm that the current version being used is 4.27. This can be done by navigating to the ‘Help → About ROBOTC’ menu option, in the bottom left corner of the popup that appears.
-
With the Cortex connected to the computer, please redownload the Master and ROBOTC firmware to their latest versions. This can be done through the ‘Robot → Download Firmware → Automatically Update VEX Cortex’ menu option.
-
Navigate to the ‘Robot → Advanced Tools → Software Inspection’ menu option with the Cortex plugged in, and make sure the firmware versions on the Cortex are correct (should be 4.23 for the Master and 1027 for the ROBOTC).
-
Plug the VEXNet Joystick controller directly into the computer (via the USB A-to-A cable and the VEXNet USB port in the back of the controller) and navigate to the ‘Robot → Download Firmware → Automatically update VEXNet Joystick’ menu option. This will download the Joystick Master firmware to the Joystick Controller.
-
Plug the Cortex back into the computer (via USB), load up a program, and make sure the ‘Robot → VEX Cortex Communication Mode’ is set to ‘VEXNet or USB’. Download the code to the robot, power cycle the Cortex, and set up the VEXNet system as normal.
If this does not resolve the issue, please provide us with the results of steps 1, 2, 3, and 4 and we will be more than happy to look into this further with you.
Thank you in advance!