Here’s how much you’re actually uploading to the V5 brain depending on what framework you use (a smaller size is better and results in a faster upload). In this chart, “First upload size” is the size of the compressed file sent to the V5 brain the very first time you build and upload your project (before any of the program is on the device), whereas “Second upload size” is the size of the compressed file sent to the V5 brain after changing a drive motor from port 1 to port 2 and reuploading (this configuration is meant to simulate tuning constants or making small code changes).
Here is an explanation of each configuration:
- VEXcode: jpearman/v5-drivecode repo, “VEXcode_Pro_V5/config_expert”, with display drawing code removed
- vexide: Official vexide “clawbot” example, with
upload-strategy = "differential"- 0.8.0: The v0.8.0 release of the framework
- dev: The Git
mainbranch of the framework
- PROS: Official PROS “Programming the Clawbot” example
- hot/cold:
USE_PACKAGE:=1in Makefile - monolith:
USE_PACKAGE:=0in Makefile
- hot/cold:
Methodology for calculating sizes: Clear all programs from the device, perform an upload, then query the size of the uploaded file(s) from the V5 Brain filesystem. Then edit the source code to change one of the drive motor ports, re-upload, then re-query the size of the uploaded file(s).
