Accessing Log Files

When troubleshooting problems with the REV Control System log files provide indicators of what the status of the Control Hub or Expansion Hub were during an event. Often the first log that is considered is the Robot Controller log, as they are relatively easy to decipher and can be pulled from the Control Hub or Robot Controller. While working through the troubleshooting process looking through the XML files, Wi-Fi Log, or Updater Logs in addition to the Robot Controller logs help to paint a full picture.

There are a few ways to access the log files depending on if you are looking to troubleshoot or downloading the log files for REV support to help.

Log Viewer - REV Hardware Client

The REV Hardware Client has a Log Viewer that makes it easier to parse overall log files. Through a series of filters, tags, and a search function makes it easy to see what is happening on the Control Hub or Driver Hub during any OpMode run.

To access the Log Viewer, head to the Utilities Tab.

From there you can select and open log files for connected devices or for ones downloaded onto the computer.

For more information on the Log Viewer check out the REV Hardware Client User's Manual.

Downloading Log Files

When sending logs to REV Support use the REV Hardware Client. The Client will zip all relevant log files, collect some additional information from a form, and then send them to REV for diagnosis. When running through the troubleshooting process at an event, physically connecting to a Control Hub (REV-31-1595) and using the file search of the computer allows access to the files. Alternatively connecting to the Robot Controller Console allows downloading the logs through the manage tab.

REV Hardware Client

1. Provide 12v Power to the Control Hub.

2. Plug the USB-C Cable into the top board of the Control Hub and into a PC with the REV Hardware Client installed.
3. Select the Control Hub from the Connect Hardware.

4. Click the "Send Diagnostics to REV" Button

There is a short form to fill out with additional information to help REV Support troubleshoot the issue.

File Search

Using a PC

Mac computers do not support MTP natively, the protocol used to browse files on Android devices. You need to use the Android File Transfer app: https://www.android.com/filetransfer/

Windows devices will operate without the need for an additional application.

1.Provide 12v Power to the Control Hub. 2.Plug the USB-C Cable into the top board of the Control Hub and into a PC 3.Navigate to This PC\Control Hub v1.0\Internal shared storage. Robot Controller, Wi-Fi, and Updater logs can be found on this level of the file hierarchy.

The logs are all text files that can either be open via Notepad++ and looked over or sent to REV Support via an email to be further troubleshot.

4.While in the This PC\Control Hub v1.0\Internal shared storage location navigate to a folder called "FIRST." The folder should have XML files with a naming convention that mirrors the names of the robot configuration.

Using a Mac

1. Download the Android File Transfer App on your MAC 2. Open Android File Transfer.dmg 3. Drag Android File Transfer to Applications 4. Use the USB-C to USB-A cable that came with your Control Hub (or other relevant Android Device) 5. Double click Android File Transfer 6. Navigate to Control Hub v1.0\Internal shared storage. Robot Controller, Wi-Fi, and Updater logs can be found on this level of the file hierarchy.

The logs are all text files that can either be open via Notepad++ and looked over or sent to REV Support via an email to be further troubleshot.

7. While in the Control Hub v1.0\Internal shared storage location navigate to a folder called "FIRST." The folder should have XML files with a naming convention that mirrors the names of the robot configuration.

Robot Controller Console

1.Open the Robot Controller Console 2. Select the Manage page 3. Press the Download Logs button

4. Check for the robotControllerLog.txt in the Downloads Directory of the Computer 5. Open the Logs via a text editor, like Notepad++, to view the contents of the log or send the logs to REV Support