@lacsap just pull the battery cable - no worries --- OK JUST KIDDING!
That's all I ever do.
Now that V5 battery cable pack had been announced, one of the cables could be modified to cut positive wire and put an inline switch on it. Just need to make sure it has large enough current rating to handle V5 battery.
As for V5 praise, it has some very exciting possibilities like software defined communication protocol for the ports, Bluetooth, WiFi, and VexNet connectivity, Vision sensor, ... and, probably, few more feature we don't yet know about. However, I afraid that software, which supposed to expose those features to the user, will either take very long time to catch up or may even abandon exposing many of them due to unanticipated complexity of the task and the budget overrun.
@reflxshn ... The "hold" feature is substantial! Holding lifts at a set height is vastly easier...We're even able to hold a puncher at the fully retracted position (just before launch) with no motor fatigue! ...
I am not so sure I like the new motor built-in PID and "Hold" feature that works out of the box. I hope to change my opinion after I experiment some more with existing motion profile interface (PROS ) / (VCS ) or new knobs and dials are added.
I look at VEX not like at a quick prototyping tool but more like an educational tool. I would rather have robots quickly stall their motors out of the box and then, when students ask why it happens, be able to explain them the cause and point to something like @jpearman's Smart Motor Library for the solution. However, since it didn't come with RobotC, even with excellent online tutorials , only a handful of senior teams would start using it, but only after they were tired of losing important matches because of the overheated drive-trains.
@TeamTX Umm... we've had 2 out of 10 motors overheat easily, and when the latest overheated the robot as a whole did very strange things (like randomly turn and shoot innocent bystanders). Also, as they overheat the V5 motors go slower and slower until they become non-functioning.
I would love for an educational tool to have easily avoidable problems out of the box, but then be able to tell students that if they add just one line of code to they program they could fix it. Then have students talk to mentors and among themselves not only about what kind of lift they are using and the gear ratios, but also what parameters they are passing to initialize Smart Motor functionality for those lift motors.
Initially, they could copy numbers from another team, but later this would be a great way to introduce them to the physics of what is going on inside the motors and the algorithms that drive them. Maybe I am not looking in the right place, but so far I haven't seen enough of those knobs and dials that could lead to educational conversation.
In some respect, the burned out motor ports issue, while terrible for both VEX and every team that experienced it, offers a lot of educational potential to introduce students to the ESD and how to protect electronics against it. I am taking every opportunity to talk to every student that is going to listen about it. In the past case of suspected static issues with IMEs it could be easily ignored by switching to QuadEncoders, however with V5 you don't have that many spare motor ports to ignore the issue and students tend to pay much more attention.
Even if 5% of the students, who are using V5 and are concerned about port failures, will learn about ESD now and remember about importance of protecting against it later in their professional career, then when they will be designing new devices, that could have a very positive impact on the quality of their work and net benefit for us all who will use those devices.
So, I would have to praise whoever decided not to put adequate ESD protection into V5 for sparking a very educational discussion but, please, don't do that again.