Undocumented Vex Tech Scavenger Hunt

[7996B]

Gif class made by Jpearman as a demo that can show off “a couple of C API’s that we don’t usually expose that were added to vexos 1.0.5”:

Animated GIF Demo (VEXcode)

Hers’s another demo that can be built with VEXcode. It’s not very well developed and uses a couple of C API’s that we don’t usually expose that were added to vexos 1.0.5. I’ll also explain a couple of more advanced aspects of the setup in another post later, specifically how to allow VEXcode access to more dynamic memory than is available with the default project build scripts. output looks like this. [gifdemo] and uses this animated gif. [world] You can display more than one gif by creat…

in that topic he covers how to change the HEAP size:

Animated GIF Demo (VEXcode)

Looks like I had already bumped the HEAP size up to 8MB for this demo, so 45 second gif I would have thought worked, however, you could try changing this line in mkenv.mk LNK_FLAGS = --defsym _HEAP_SIZE=0x800000 -nostdlib -T "$(TOOLCHAIN)/$(PLATFORM)/lscript.ld" -R "$(TOOLCHAIN)/$(PLATFORM)/stdlib_0.lib" -Map="$(BUILD)/$(PROJECT).map" --gc-section -L"$(TOOLCHAIN)/$(PLATFORM)" ${TOOL_LIB} The _HEAP_SIZE symbol control the size, the default for VEXcode if this is not defined is just 1MB, for thi…

factory calibration for IMU:

Full alignment procedure for Inertial sensor

This procedure calibrates the accelerometers in the Inertial sensor and saves the result in non volatile memory. This procedure needs vexos 1.0.10 or later. Only perform this calibration if your VEX inertial sensor is showing angles for roll and/or pitch that are larger than perhaps 1 or 2 degrees when the inertial sensor is on a flat surface that is known to be level in both axis. Some inertial sensors can show significant error for roll and pitch when placed on a level surface. To check a…