6-8-22 initial transfer from staging, not linked
Westside Robotics
162
Datalogging,-Part-3:-RC-File-Transfer.md
Normal file
162
Datalogging,-Part-3:-RC-File-Transfer.md
Normal file
@ -0,0 +1,162 @@
|
|||||||
|
|
||||||
|
## Introduction
|
||||||
|
|
||||||
|
This basic tutorial shows some ways to transfer datalog or other files from the FTC Robot Controller (Control Hub or RC phone) to a desktop or laptop computer.
|
||||||
|
|
||||||
|
Manually transferring datalog files from the RC device will be of most interest to **Android Studio** users. This isn't needed with OnBot Java, where datalogs can appear on-screen for easy Download.
|
||||||
|
|
||||||
|
Another simple way to transfer files is with a USB thumb drive, not covered here.
|
||||||
|
|
||||||
|
This article is **Part 3** of a 4-part series on Datalogging. [**Part 1**](https://github.com/FIRST-Tech-Challenge/FtcRobotController/wiki/Datalogging) shows how to run a **sample OpMode** and chart its data. [**Part 2**](https://github.com/FIRST-Tech-Challenge/FtcRobotController/wiki/Datalogging,-Part-2:-Custom-Data) shows how to **customize** the sample OpMode for logging your own robot data of interest.
|
||||||
|
|
||||||
|
[**Part 4**](https://github.com/FIRST-Tech-Challenge/FtcRobotController/wiki/Datalogging,-Part-4:-Java-Learning-Exercise) describes the inner workings of a **different**, much simpler Datalogging class. It's strictly a Java learning exercise, showing basic steps to log robot data on the RC device. It does not require familiarity with Parts 1 and 2.
|
||||||
|
|
||||||
|
[<p align="right"><i>Return to Top</i>](#introduction)<p>
|
||||||
|
|
||||||
|
## Wired USB cable
|
||||||
|
|
||||||
|
The simplest transfer method is to plug the RC device into a computer via USB cable.
|
||||||
|
|
||||||
|
- It must be a 'data' cable, not 'charge-only'.
|
||||||
|
|
||||||
|
- For Control Hub use the USB-C port, not the Mini USB port.
|
||||||
|
|
||||||
|
- Connect the device for file transfer (Media Transfer Protocol or MTP mode).
|
||||||
|
|
||||||
|
- on RC phone, swipe down twice to set MTP mode
|
||||||
|
|
||||||
|
- Use the computer's file manager to locate the RC source folder.
|
||||||
|
|
||||||
|
- Copy-and-paste the datalog or other file to the computer.
|
||||||
|
|
||||||
|
- Unplug the USB cable; no need to 'Eject'.
|
||||||
|
|
||||||
|
[<p align="right"><i>Return to Top</i>](#introduction)<p>
|
||||||
|
|
||||||
|
## Wireless adb - Set-up
|
||||||
|
|
||||||
|
It's possible to connect the RC device wirelessly to a laptop (or desktop with Wi-Fi). The RC device must allow **USB debugging**, which can be turned on in Developer Options.
|
||||||
|
|
||||||
|
- Control Hubs allow USB debugging by default.
|
||||||
|
|
||||||
|
- For RC phones, follow these steps:
|
||||||
|
- open Settings and "About phone"
|
||||||
|
- tap 7 times on "Build number"
|
||||||
|
- now "Developer Options" will appear under Settings/System/(Advanced)
|
||||||
|
- turn on USB debugging
|
||||||
|
|
||||||
|
- At first connection to a laptop, check the box to allow USB debugging from that computer.
|
||||||
|
|
||||||
|
Also, the laptop must have **Android Debug Bridge** or "adb" installed. Installing adb is described many places online, and in the FTC Wiki at [this page](https://github.com/FIRST-Tech-Challenge/FtcRobotController/wiki/Managing-a-Control-Hub#connecting-to-the-control-hub-using-wireless-adb).
|
||||||
|
|
||||||
|
[<p align="right"><i>Return to Top</i>](#introduction)<p>
|
||||||
|
|
||||||
|
## Wireless adb - Command Prompt
|
||||||
|
|
||||||
|
After completing the above adb set-up steps, click the laptop's Windows 10 or Windows 7 icon at bottom left corner. In its search bar, type `cmd` to open the Windows **Command Prompt** window.
|
||||||
|
|
||||||
|
To verify that adb is already installed, type `adb devices`. An error message will appear if adb is not installed; otherwise a list of devices may appear (OK if blank, for now).
|
||||||
|
|
||||||
|
To connect a **Control Hub**, type `adb connect 192.168.43.1:5555` at the command prompt, and wait for acknowledgement.
|
||||||
|
|
||||||
|
Connecting an **RC phone** via adb can be done in two ways: with Wi-Fi Direct, or with standard Wi-Fi.
|
||||||
|
|
||||||
|
- For both methods, plug RC phone into laptop with USB cable
|
||||||
|
- optional to set file transfer (MTP) mode
|
||||||
|
- if a pop-up appears, check the box to allow USB Debugging
|
||||||
|
- at the command prompt, type `adb tcpip 5555`
|
||||||
|
- wait for message "restarting in TCP mode port: 5555"
|
||||||
|
- optional to confirm wired connection with `adb devices`
|
||||||
|
- unplug the USB cable
|
||||||
|
|
||||||
|
- **Wi-Fi Direct method:**
|
||||||
|
- open the FTC RC app
|
||||||
|
- connect the laptop's Wi-Fi to the RC phone's network, as usual for Blocks/OnBot Java programming
|
||||||
|
- at the command prompt, type `adb connect 192.168.49.1:5555`
|
||||||
|
- receive confirmation
|
||||||
|
|
||||||
|
- **Standard Wi-Fi method:**
|
||||||
|
- confirm laptop and phone on the same standard Wi-Fi network
|
||||||
|
- Airplane Mode off
|
||||||
|
- get (from Settings) the phone's IP address (e.g. 192.168.1.15)
|
||||||
|
- type `adb connect 192.168.1.15:5555`, using the phone's actual IP address
|
||||||
|
- receive confirmation
|
||||||
|
|
||||||
|
- For both methods, optional to confirm wireless connection with `adb devices`.
|
||||||
|
|
||||||
|
[<p align="right"><i>Return to Top</i>](#introduction)<p>
|
||||||
|
|
||||||
|
## Wireless adb - File Transfer
|
||||||
|
|
||||||
|
With adb in place, copying a file from the connected device to your laptop can be done with a single "pull" command. For example:
|
||||||
|
|
||||||
|
`adb pull /sdcard/FIRST/Datalogs/myDatalog_001.csv C:\Users\Public\Documents`
|
||||||
|
|
||||||
|
The 'source' field is the **filename** on the RC device. The 'target' field is the desired destination **folder** on your laptop.
|
||||||
|
|
||||||
|
And yes, it is really that easy. (There's also a "push" command.)
|
||||||
|
|
||||||
|
Some notes:
|
||||||
|
|
||||||
|
- Uppercase/lowercase is optional, but pay attention to forward- and back-slashes.
|
||||||
|
|
||||||
|
- Files with the same name will be overwritten in the target folder. Rename files as needed to avoid this.
|
||||||
|
|
||||||
|
- If a folder or file name contains a space (blank character), enclose the entire pathname in double-quotes. For example, "C:\Users\Public\My Documents".
|
||||||
|
|
||||||
|
[<p align="right"><i>Return to Top</i>](#introduction)<p>
|
||||||
|
|
||||||
|
## Wireless transfer with Android Studio
|
||||||
|
|
||||||
|
You could transfer files with Android Studio, used here for its **file manager**, not for programming.
|
||||||
|
|
||||||
|
These steps are not as fast as "adb pull", but the file manager allows you to see and navigate the source and target folders.
|
||||||
|
|
||||||
|
- connect via adb to the Control Hub or RC phone
|
||||||
|
|
||||||
|
- open Android Studio (any project)
|
||||||
|
|
||||||
|
- click ["Device Explorer"](https://raw.githubusercontent.com/wiki/WestsideRobotics/FTC-Datalogging/images/AS-01-marked.png) at right edge
|
||||||
|
|
||||||
|
- in Device Explorer, navigate to the device folder [FIRST/Datalogs](https://raw.githubusercontent.com/wiki/WestsideRobotics/FTC-Datalogging/images/AS-02-marked.png)
|
||||||
|
|
||||||
|
- right-click the filename, choose ["Save As..."](https://raw.githubusercontent.com/wiki/WestsideRobotics/FTC-Datalogging/images/AS-03-marked.png)
|
||||||
|
|
||||||
|
- at the next window, navigate to the [laptop target folder](https://raw.githubusercontent.com/wiki/WestsideRobotics/FTC-Datalogging/images/AS-04-marked.png), click OK
|
||||||
|
|
||||||
|
This [copies the file](https://raw.githubusercontent.com/wiki/WestsideRobotics/FTC-Datalogging/images/AS-05-marked.png) to the laptop target folder, confirmed with [Windows Explorer](https://raw.githubusercontent.com/wiki/WestsideRobotics/FTC-Datalogging/images/AS-06-marked.png).
|
||||||
|
|
||||||
|
To **refresh** the directory listing, re-select the RC device from the top pull-down menu, just below the heading "Device File Explorer".
|
||||||
|
|
||||||
|
[<p align="right"><i>Return to Top</i>](#introduction)<p>
|
||||||
|
|
||||||
|
## Summary
|
||||||
|
|
||||||
|
This basic tutorial showed some ways to transfer datalog or other files from the FTC Robot Controller (Control Hub or RC phone) to a desktop or laptop computer.
|
||||||
|
|
||||||
|
This article did **not** cover:
|
||||||
|
|
||||||
|
- portable USB flash drives (thumb drives)
|
||||||
|
|
||||||
|
- direct download with connected software such as FTC Blocks or OnBot Java
|
||||||
|
|
||||||
|
- methods that require installing third-party apps to the RC device, and in some cases also installing software to the laptop. Some examples are described [here](https://geeknizer.com/transfer-files-between-pc-and-android/) and [here](https://appuals.com/5-methods-to-wirelessly-transfer-files-from-android-to-pc-no-usb/).
|
||||||
|
|
||||||
|
You are encouraged to submit and describe other file transfer methods that worked for you.
|
||||||
|
|
||||||
|
[<p align="right"><i>Return to Top</i>](#introduction)<p>
|
||||||
|
|
||||||
|
------
|
||||||
|
|
||||||
|
This article is **Part 3** of a 4-part series on Datalogging.
|
||||||
|
|
||||||
|
[**Part 1**](https://github.com/FIRST-Tech-Challenge/FtcRobotController/wiki/Datalogging) shows how to run a **sample OpMode** and chart its data.
|
||||||
|
|
||||||
|
[**Part 2**](https://github.com/FIRST-Tech-Challenge/FtcRobotController/wiki/Datalogging,-Part-2:-Custom-Data) shows how to **customize** the sample OpMode for logging your own robot data of interest.
|
||||||
|
|
||||||
|
[**Part 4**](https://github.com/FIRST-Tech-Challenge/FtcRobotController/wiki/Datalogging,-Part-4:-Java-Learning-Exercise) describes the inner workings of a **different**, much simpler Datalogging class. It's strictly a Java learning exercise, showing basic steps to log robot data on the RC device. It does not require familiarity with Parts 1 and 2.
|
||||||
|
|
||||||
|
***
|
||||||
|
|
||||||
|
<i>Questions, comments and corrections to westsiderobotics@verizon.net</i>
|
||||||
|
|
||||||
Reference in New Issue
Block a user