[Split Thread] Differences between PROS and VEXCode and Respective Documentation

[sazrocks]

@anon4126930

What steps will VEX take towards making more reliable motors that do not lock up as frequently and break ports frequently (likely as a result of high current draw over the thin wires). Has VEX considered a different wiring solution that is more robust for the motors?

Unless there are a ton of instances of smart cables melting that I’m completely unaware of, the current draw of the motors (and the gauge of the wires) has nothing to do with smart ports failing on the brain or motor. The RS485 data pins are even completely separate. Also, V5 smart cables have increased wire thickness specifically to support the higher current loads from things like V5 11w motors. Can you elaborate on what you mean by “thin wires”?

@anon4126930

As it stands, despite minor differences, both PROS and VEXcode are near identical on paper and functionality

While most of the functionality of the V5 system is available in both environments, this does not at all mean that they are “identical”. Under the hood they each have some pretty significant differences such as entirely different scheduler types, different ways the program binaries are made/stored on the brain, and different supported C++ versions. And of course, the API for each environment is entirely different.

@anon4126930

especially considering that both are a VSCode extension.

Neither VEXCode nor PROS “is” a VSCode extension. Both have VSCode extensions to facilitate their ease of use in VSCode, but both are more than the extension itself.

@anon4126930

Has VEX considered merging PROS and VEXcode into one single library that has both support of VEX as well as the community?

Ignoring the logistical complexity/impracticality of this (the libraries are not really “mergable”, they are completely different), you would also have to ask if the PROS team is willing to do this alongside VEX. To that end, I’m not even sure how possible it would be legally, depending on how the end product would be licensed you may need to get the consent of all PROS contributors for their code to be relicensed.

---

On topic, here are a few questions I have:

1. What is the end goal for VEX AI? Is it intended to be more of a classroom-based competition with robust mentoring to help students through the challenge? Or is it meant to be an avenue for the top tier of VRC HS and VEXU teams to go even further?

2. Advanced vision-based programming solutions are a way I think the program can continue to stay relevant for higher tier VRC teams and VEXU teams, especially with the introduction of the new V5 AI Vision sensor with AprilTag support. Are there any plans to introduce CV markers such as AprilTags into the field and/or field elements/game objects for more approachable CV techniques?

3. To add to 2, are there any plans to open source the algorithm behind the GPS strips and sensor? In some scenarios, the GPS sensor off the shelf from VEX is inadequate, and teams prefer to rely on their own localization techniques. If the GPS strip and associated algorithm were open source, teams in VEX AI and VEXU may be able to take advantage of the GPS strip using their own cameras and processing.

4. What is the status of the VEX AI Stereo 3D camera?