Just got a kit, I finished assembling my robot, but when I turn on the brain(motors radio battery and anything else connected), it lets me select my language, but I can’t tap the language I want, and when it selects some random language, I can’t tap on anything, like settings, I want to change the language, but it won’t respond.
So I have to ask first, you did take the protective cover off ?
Otherwise, sounds like a defective screen, contact vex support and RMA the brain.
7 Likes
Yes, I took off the cover, the screen can change, like if I want to drive, but it won’t respond when I tap.
Here’s some simple troubleshooting:
- As @jpearman said, take off the protective covering if still on.
- Wash your hands and dry them. It could be anything on your fingers.
- Make sure the screen is clean. (Take caution if you want to clean it. Unless needed, don’t).
- Reset power button if you haven’t already and try again.
- If you try it and the brain overheats, wait a few minutes and try again.
If none of these work, then it might be a brain issue.
Feel free to add to the list for future users with similar issues.
Well I have been having problems with meny vex v5 brain’s after updating them to OS 1.1.3.
If I let it sit for about a hour, the brain will be frozen and all smart ports are blinking red.
If I start and stop my program very often, after 20~ minutes on the home screen it will freeze with the same blinking lights on smart ports.
The only way i’ve seen to fix it is to unplug the brain.
Having a USB connection to the brain when it freezes makes it worse, it will never recover after unplugging and replugging the battery. It will fix after you remove the USB cable, and unplug and replug the battery,
I’ve observed this across a total of 12 brains, so it’s not a one off.
Also, being on 1.1.2 this problem does not exist. I’ve tried and tried, but even after 6H of a program running, and keeping it plugged in, does not make it do this,
A bit off topic, I don’t think this is in any way related to the OP’s issue with touch screen,
I can’t say I’ve experienced this issue, and I run V5 systems for many hours during development and final testing, however, a few more details may help us track down what the problem is.
Usually the V5 will power down unless either a program is running, USB is connected or there is some user interaction with the brain. How are you keeping the system powered on ?
Has a user program ever been run or are you just turning on the brain and waiting ?
These are in a classroom ? Different students are using these ?
I do notice you have been trying to use a different toolchain to build your program, bear in mind that part of the C++ standard library is built into vexos. Deviation from using official tools may lead to unexpected results even though on the surface it may appear to work.
1 Like
Well when this bug triggers, I don’t need to do anything, just waiting will do it. The brain will never auto turn off, and after some time, it will completely freeze and nothing will work without a reconnect with power.
No, we each have our own brains, however everyone has been complaining to me about this freezing problem after I updated everyone’s brains to 1.1.3.
Yep, i’m aware of this. However, the other kids use block code, they are nowhere near ready to use C++. (I’m the only one using C++)
When this happens, windows will say unrecognized USB connected with the error “Cannot get device identifier”. I kept one brain at 1.1.2 to test, and the bug has not triggered.
So USB is always connected when the crash happens ? With nothing connected, no program running etc. the brain will turn off after 3 minutes.
Which version of windows is running ? Any USB-C adapters or hubs being used ?
2 Likes
No adapters, direct from type a to micro b, and after waiting a hour or so it will freeze, and you have to unplug the micro b cable and reinstall the power to make it respond again.
Windows 11, but another thing I found is that this seems to only happen on laptops, after keeping my robot plugged in for 6H on my PC, it’s fine. If I do it on a laptop, it will freeze after ~30 minutes. However, this seems to be something with USB3, as if I use a adapter (that only has 2.0) it will not crash,
When this happens, No program is running, just USB connected.
However with a brain on 1.1.2, testing it on a laptop with no adaptor and it’s fine.