@@ -76,4 +76,22 @@ The Pause button does what you'd think it does, it pauses and resumes the balanc
The plotting of the balance beam works by the GUI calling a method in the CLI wrapper that sends a command to the CLI tool and gets the ball's current position. It is run a lot, to simulate the data being "streamed." Again, this is because we weren't able to do a direct connection to the CyDAQ to get more accurate/efficient live data.
# Debug
The debug page is a page that is used to get diagnostic information from the CyDAQ as well as a space for running whatever tests are included.
First, we have the Debug Log View. This is a text view that has all of the debug logs that are captured while running the GUI. As you can see in the screenshot below, it captures things at different levels, DEBUG, INFO, ERROR, and CRITICAL. It stores a lot file at `C:\Temp\cydaq_current.log` and appends to it live.
You can press the `Clear` button on the top right to clear the logs, and below there is an `Export Logs -->` button that can be used to export whatever is in the current logs. (The `Clear` button does not clear the log file, just the text view).
The "Test" buttons seen in the screenshot below are currently disabeld but were used to test the speed of python by reading and writing lots of data. The tests were to determine the capabilities of python for handling potential live data streaming in the future.
The Crash CyDAQ button was put there as well to test how the GUI would handle an exception being thrown and to cause the CyDAQ to crash. It currently works and is enabled but it doesn't really serve much of a purpose at the moment.
The `Show Ping Cmds in Log` checkbox allows for the ping commands to be logged. These are disabled by default because they fill up the logs fast (2 lines every one second, one for cmd sent and response received) and are only useful to diagnose connection issues.
The `Mock CyDAQ - Linux Only` checkbox enables the Mock Mode. This mode is available on Linux Only, and it mocks a serial port connection that can have commands be sent to (see `gui/serial_comm.py` for how this system works).
