| Competition Language | |||
| DebugLCD | DebugVar | EndDebug | How to Use |
This command starts a task that will take advantage of the LCD. It opens a window where you can navigate between all the values of the sensors, motors, I2C encoders, timers, Vex controller values, personal variables, and voltages of the cortex and backup battery.
This is a system array that contains the 8 personal variables displayed by the debugger window. You can reference and set them in your code and view them in the debugger window.
This just forcefully ends the debugger window and halts it.
The debugging commands and variables are used to display values on the screen. If you use the command DebugLCD, it will initialate a task that displays things like sensor values, motor speeds, I2C encoders, timers, controller values, your personal variables, and voltages. This command will not interfer with the running of other parts to the code, but do not use this command when some other part of the code is using the LCD, there will be conflict.
Next, the DebugVar command stores the personal variables you want to display on the window. There are eight slots of memory and you can set them by placing the slot name inside the square brackets and setting it equal to a value just like any other variable. The slot names consist of a "V" followed by the number slot.
The last command is the EndDebug command. All it does is, whenever called, it stops running the debugger window.
When navigating the debugger window, there is a name and value on the first row. On the second row there are the words "Menu", "Type", "End". Pressing the button under "Menu" will change between the types, (Sensors, Motors, etc.). Pressing the "Type" button will change the slot number (port1, port2, port3, etc.). Finally, pressing the "End" button will end the debugger window (just like using EndDebug).