Re: 2.30 Unstable Download of Firmware & Code
Hi Lyncas -
Thanks for spending the time to convey your experience. I'm going to try to respond to each portion of your message, so I don't miss anything.
The Master Firmware is supplied by Innovation First, and there's not much we can do about motor spasms. The motors only turn on if the Cortex is also powered by a battery, and theoretically you shouldn't need the battery to download Master Firmware, so you could switch the Cortex to "OFF" during this process if it presents a problem. A warning message is a good idea - I'll make an internal note for the developers.
We've been successfully downloading programs and firmware wirelessly (using the orange cable to connect the PC to the joysticks) for some time. Was the driver for the orange programming cable installed on the computer you were using? Download links for the driver can be found here: http://www.robotc.net/download/cortex/
Did you follow the steps to link the VEXnet Joystick and Cortex after downloading their firmware files? We have instructions for that here: http://www.education.rec.ri.cmu.edu/products/teaching_robotc_cortex/reference/VEXnet_setup_guide.pdf
The entire "approved" setup process can be found here: http://www.education.rec.ri.cmu.edu/fire/competitions/vex-robotics-competition/#gettingstarted
When the Cortex is turned on, it "looks" for how it's connected, and what it's connected to - Joystick over VEXnet, the PC over USB, or nothing. Once it figures out how it's connected it stops looking, so changing the connection method may require power-cycling. For the "USB Wired" option to show up, the Cortex has to be turned off when it is connected to the PC. If it's already turned on, it may think there's no connection, and then not make itself visible to the PC.
We've been experiencing very robust communications with the Cortex. That said, we're committed to continue to improve ROBOTC for users that are experiencing issues. In order to help us figure out why you're experiencing issues, you could help us by:
- Very specifically detailing the processes that you're using, where they're failing, and what the result looks like
- How old is your VEX Cortex
- What type of computer do you have (Operating system, age, make, model, ect)
- Anything else that seems relevant
Again, no obligation to provide any additional detail, but figuring out why you're experiencing issues goes a long way with helping us solving them. Thanks again for spending the time to write about your experience.