So, we’ve run into a bit of an issue. We were testing our catapult and drivetrain, but every time we started the code we would get an error code. This error code changed most times we started the code, except on some occasions where it would say Brain Memory Permission Error!. It would usually stop for a minute or two when we restarted the robot, but when we turned off the robot one time it just stayed off. We still haven’t been able to turn it on.
So far we’ve tried the following:
Waiting a few minutes and trying to turn it on.
Unplugging everything from it and waiting, then trying to turn it on again.
Changing the battery.
Changing the battery cable.
Another interesting thing that is happening is that every time the power button is pressed, the battery’s lights turn on, but the brain doesn’t.
If anyone has any solutions, that would be great. We’ve contacted technical support and are waiting for a response from them.
seriously, the number that fail are a tiny percentage of the number we sell.
or they could try calling vex support and explain the problem.
Memory Permission Error is caused by problems in the user program, generally the use of an uninitialized pointer or instance of a class that is not yet created.
You’ll probably find it is on if the battery lights are flashing when you press the power button. Connect it via USB to VEXcode and you’ll probably see it get recognised as connected. Possible that the screen is not working.
So the other error codes were Unknown Errors followed by strings of numbers and letters that I don’t have on me but a friend does, they varied throughout. I searched them up on the VEX Forum and VEX itself but nothing showed up.
Memory Permission Error is caused by problems in the user program, generally the use of an uninitialized pointer or instance of a class that is not yet created.
The only thing with this is that we tried different codes, one of which wasn’t in C++ but blocks using the default VEX Competition Template.
Brain is probably dead for good… try a new brain if possible. If not you’ll have to buy one.
Dang bruh it sucks cuz we just got this brain
Thank you all for the help, I’ll update this post later if any progress is made.
anyway, the numbers indicate the address that the error occurred, so will be pretty much meaningless to anyone except vex engineering (sometimes).
If this was a new brain, that is you just purchased it, then it could be replaced under warrantee. I’ve never heard of code actually damaging a brain, it seems quite unlikely, perhaps this brain had some hardware issue. Call vex support.
