a lot of already answered questions about V5 are being asked again, I’m not blaming the people who are asking, it can be hard to find stuff on here, perhaps someone should compile everything Paul has said about V5 into one, easy to reference post.
OK, here are some responses to things brought up:
You guys will really like this thing. The screen did not alter button positions at all. The relationship of joysticks to buttons to the handle are all very similar to what you are used to. When designing we bought every gaming controller known to man. We realized quickly there were two distinct camps and we weren’t going to be able to please everyone (Xbox camp and PS/Logitech camp). We didn’t go to far away from our current layout but made subtle ergonomic improvements and took significant cost out of the controller, even with the LCD screen. Fun fact: the screen is the EXACT screen from VEX IQ.
The batteries and radio are integrated into the controller, just like the PS4 controller. You will notice the current competition port to support the current field control system and 2 smart ports. One is for the second controller and one is for the future field control system that has yet to be designed. The battery life is very, very good and a fully charged controller should last an entire competition day even without plugging it in between matches. The battery regulations are getting very stringent and by integrating the battery into the product you can air ship the battery with the product with no restrictions.
How many of you like the team competition switch to simulate a match? I, for one, hate it so we integrated it into the controller. You will be able to “host” a practice match from your controller and invite other team numbers to join your “match”. You can change the timers for skills, etc. I am very excited about the possibilities of this feature. The screen is essential for this functionality. Additionally, you can select your programs and switch programs from your controller. You can get debug information and will be able to program what displays.
No, you will not be able to replace the brushes. These are welded motor cans at the factory (I’m talking about the base motor we purchase, not the entire motor assembly). These brushes will wear way later than your current failure timing on the 393 motors. Additionally, you will not need to replace motors for your competition robot every year as the performance will be consistent from year to year. The motor output is meant for both the 1/8" and 1/4" shafts and the mounting screws are
#8. There is no longer a need for the #6 screws in V5. There were some questions about plastic gears. We have plastic gears wehre we need them and steel ones where we need them. Planetary gearsets significantly reduce the load on each individual gear, especially the input sun gear. We made both steel and plastic input sun gears and the plastic ones are performing marvelously so we decided on those for production.
Yes, your current pneumatics will be compatible with V5. During the transition years you will have to trade off pneumatics for number of motors just like now. Your 8 motors will get reduced if you use pneumatics.
269 and 393 Motors:
By rule, they will not be legal if you use the V5 brain. This is to protect you from yourselves. While the brain can control the 393 motor it is at significantly reduced capacity specifically for classroom usage. Our estimation is we have over 1 million 393 motors in classrooms today and rendering those useless just because we wanted a better motor for competition was a non starter for us.
Regarding the connector selection, it was a really simple goal: ANYTHING other than standard hobby connectors. If we didn’t have so many sensors out in the community I would have pushed for eliminating them in the new system all together.
We reviewing what our requirements were for all of the use cases and the fact that we were going to a higher voltage and RS485 communication protocol it seemed obvious the RJ11 was the connector of choice.
In our analysis the RJ11 was the best commercially available connector that fit our needs. We really wanted teams to be able to make their own cables so this solution seemed the best.
Of course, we could have just done a custom one, but then we would have had some of you on here accuse us of just trying to get more money from you by making you buy them from us…
Regarding the partner controller, there will NOT be a separate part for the partner controller. You will be allowed to use two regular controllers, however. This decision was based on several factors, the most being it just didn’t make much sense as the new system architecture made the two almost exactly the same anyway. In the Cortex use case, the partner Joystick is much, much simpler than the main Joystick.
Oh and please do not use the word Cortex with this new brain. It is called the V5 Brain. There is no Cortex microcontroller in the V5 Brain. We have been calling the main parts V5 BRain, V5 Controller, V5 Motor, V5 Battery, and V5 Robot Radio.
Yes the connectors for the motor are RJ11 connectors.
We will have standard cable lengths like VEX IQ AND a bulk cable option with connectors and a crimper sold directly by VEX so you can make your cables the exact length you want. As far as rules for VRC, I don’t remember where we settled on using commercial cables, but I expect that should be allowed. I’m not certain the curled cable types will be legal, but equivalent cables to the bulk cable VEX provides should fall under the current rules today as legal. Again, we have not finalized this level of detail in the game manual yet.
The battery connections are custom 1 x 4 Molex connectors based on their industrial 2x2 design. the battery has the charging circuit inside and does not have an integrated cable. So the battery and the brain have the same connector.
As far as software, there will be a full blown (well not ALL of the libraries) C++ inside VEX Coding studio in addition to the blocks and code safe text. The blocks and code safe text will be back and forth compatible to assist in the transition from block to text programming. So there will be three languages inside VEX Coding Studio to start. I suspect we will add more as the community requests it. Also, RobotMesh and PROS will be supported by those organizations right at launch as we have been keeping them in the loop on the development.
We are still doing a bunch of verification testing on the motor curves, but 10W of power at max power is the min we are getting now. This is 10W over a large range of speeds since we are using an oversized motor and limiting its output with the motor firmware. You should be able to get 10W across 50% of the speed range. This will make it seem like you have way more than 2.5 times the power of the 393 motor. So there are no PTCs in this design as we are protecting everything with firmware like we do in VEX IQ.
Also, the motor controller’s FETs used in the V5 motor are running at a significantly higher chopping frequency so in pure PWM mode you have a linear response. However, I think you will find the closed loop speed control mode and position control modes will be much more useful.
I will get the particulars on the communication rates, but please remember that the motor has its own processor so the communication rate between the motor and the brain does not need to be that fast because the motor is doing a lot of the math for things like PID, etc. Again, I don’t have those numbers committed to memory so I will get them when I get back to the office on Monday.
Right now we went with a 6:1 first stage and a 3:1 and 6:1 2nd stage giving us 6:1 (600 RPM), 18:1 (200 RPM) and 36:1 (100 RPM) cartridges. Since the first input sun is connected to the encoder wheel inside the motor the 6:1 first stage is fixed so we would have to make different second stages.
The rule on pneumatics is being heavily debated.
They are color coded: 100RPM = red; 200 RPM = green; 600 RPM = blue
I will add more as I find them or they are posted in the thread.
This saves so much time. I believe Paul also made a post regarding price estimates for each of the individual components. If you could add that in as well, there is no doubt in my mind that It will gain a lot of interest and prevent a ton of web-wandering.
The two ports mentioned about the joystick - one being for a partner joystick and the other for competition… does this mean that the programming module will no longer be useful?
The V5 has a micro-usb port for programming last I checked, so that’s a no.
I’m not 100% sure but I do remember reading that the micro USB port would be used for programming and charging.