Yesterday, I updated RobotC to the new version. I touched up on my program and downloaded it to my robot. RobotC told me that I should update the firmware on the robot, so I did. It updated successfully. However, RobotC wouldn’t recognize the Cortex after that: http://i.imgur.com/dVlNoGQ.png
The lights told me it was connected to the computer, so I decided to use the firmware upgrade utility since it always solves this kind of problem. It was successful, so I figured that the problem was fixed. I cycled it and reconnected it to the computer. The lights indicated it was connected, but RobotC still gave me the same error. I tried RobotC’s firmware update, but even that didn’t work.
I tried restarting my computer, re-downloading RobotC, and using the “configure” button on the Cortex, but nothing fixed the issue. We also tried to download onto a different Cortex. It still wasn’t recognized.
Is the new version of RobotC compatible with Windows 10, or do we have to use a Windows 7/8 PC for it to work? Are there any solutions to this?
I had the problem what I did was downloaded the program multiple times it just worked after a while. That’s not much help, but that’s all i have.
I would say look under the device manager and if it isn’t being recognized go to the website and download the drivers.
FWIW, I asked ROBOTC support today about a bug I found when using ROBOTC v4.52 on my Windows 10 laptop,* and they said that ROBOTC is indeed compatible with Window 10. I haven’t had any problems with downloading code even after doing a firmware update, but your best bet is probably to try reinstalling ROBOTC (which will reinstall the VEX drivers). Something might have gotten corrupted during the installation.
Have you tried submitted a support ticket for the problem? I’d imagine ROBOTC support might have some better suggestions.
*If you’re curious, when I have the debugger open and switch to a different program, ROBOTC has frozen when I return. Minor, but a bit annoying.
The newest version of robotC does work with windows 10, I have been using them together ever since the newest version came out
We had reports of this bug before with other versions of Windows, however, none of the developers were able to reproduce on their own machines. Did you give tech support all the details of your hardware and any other details about your setup you may think relevant?
@jpearman Yeah, I have a support ticket and am working on troubleshooting it with them.
We have also encountered this situation a number of times. I would just disconnect and try again. Maybe try downloading the program from a different computer with robotc.
Just to update, I have a support ticket.
We used v4.52 on a desktop, but we still got the error. It was running Windows 7.
I think the problem may be our school’s WiFi. I will try to download from my home WiFi and test it out.
For now, we downgraded to v4.5.
So with 4.5 you don’t have the problem? Do you connect using the USB A-A cable to the cortex or one of the serial programming cables? Are you trying to program with a VEXnet connection?
4.5 doesn’t give us the error.
We usually use a programming cable (since they’re pretty convenient). We connected directly to the Cortex with an A-A cable after it gave us the error.
So the direct connection worked?
Do you have an old (separate USB to serial adapter) or new (USB plugs into it) programming cable?
The direct connection for 4.52 still had the same message.
I think we have a new one. It looks like this:
That’s a new one.
Probably best to keep troubleshooting with Robomatter support otherwise we will just ask all the same questions twice.
What I would o is make sure that you have the right drivers installed (whether your using win10 or win8)… Secondly I would check that both your cortex and vexnets are fully updated/upgraded.
Just to update, I updated the RobotC firmware and it worked fine from there. For some reason, downloading the master CPU firmware seemed to make the Cortex lose connection.
Thank you to RobotC support 