|
| 1 | +--- |
| 2 | +layout: default |
| 3 | +title: Technical |
| 4 | +nav_include: true |
| 5 | +nav_order: 1 |
| 6 | +--- |
| 7 | + |
| 8 | +# Technical FAQ |
| 9 | + |
| 10 | +## Why does my build fail? |
| 11 | + |
| 12 | +## What is the difference between cloning using HTTPS and SSH? |
| 13 | +HTTPS (Hypertext Transfer Protocol Secure) and SSH (Secure Shell) are both data transfer protocols used in networking |
| 14 | + |
| 15 | +The main reason why you should use SSH over HTTPS is that you can push code to your repositories without having to input credentials each time (HTTPS requires credentials each push, which is annoying). |
| 16 | +TODO elaborate more |
| 17 | + |
| 18 | +## How do I navigate the bash terminal for Robotathon? |
| 19 | + |
| 20 | +## How do I find out what my controller’s Bluetooth address is? |
| 21 | +1. Plug in your ESP32 and flash it with the starter code in your forked repository if you haven't already |
| 22 | +1. Open the serial monitor |
| 23 | +1. You should see this in the serial monitor while trying to connect your controller: |
| 24 | +<img src="{{ '/_assets/images/controller_address.png' | prepend: site.baseurl }}" alt="controller_address :("> |
| 25 | +The string of octets (something like “98:B6:E1:7C:C3:95”) is your controller’s Bluetooth address |
| 26 | + |
| 27 | +## How do I connect my controller? |
| 28 | +1. Make sure you have added your controller’s Bluetooth address to the ESP32 ([How do I do that?](TODO WRITE THIS)) |
| 29 | +1. Power and flash ESP32 with starter code |
| 30 | +1. Press and hold the home button on your controller (big H button in the middle) until the lights turn on and then speed up |
| 31 | +1. Controller should connect automatically |
| 32 | + |
| 33 | +## I've tried to add my controller's Bluetooth address, but my controller still isn't connecting! |
| 34 | +There is a maximum storage of 4 Bluetooth addresses in the allow-list. Simply remove an existing one and replace it with your controller’s Bluetooth address. |
| 35 | +<img src="{{ '/_assets/images/allowlist_list.png' | prepend: site.baseurl }}" alt="allowlist_list :("> |
| 36 | +<img src="{{ '/_assets/images/allowlist_remove.png' | prepend: site.baseurl }}" alt="allowlist_remove :("> |
| 37 | +<img src="{{ '/_assets/images/allowlist_add.png' | prepend: site.baseurl }}" alt="allowlist_add :("> |
| 38 | + |
| 39 | +If this fails, then try [hard resetting your ESP32’s flash memory](https://randomnerdtutorials.com/esp32-erase-flash-memory/) |
| 40 | + |
| 41 | + |
| 42 | +## I tried doing the above, but my controller isn’t connecting! How do I troubleshoot?(See the [official docs](https://bluepad32.readthedocs.io/en/latest/FAQ/#:~:text=true)%3B%0A%7D-,Using%20allowlist%20commands%20from%20the%20USB%20console,%C2%B6,-Note) |
| 43 | + |
| 44 | +This is probably an issue with BluePad32’s whitelisted connections. You will not be able to connect your controller to the ESP32 without adding your controller’s Bluetooth address to the whitelist. |
| 45 | + |
| 46 | +Try manually adding your controller's Bluetooth address through the serial terminal |
| 47 | + |
| 48 | +## I can’t flash my ESP32 because of a “fatal error”! What should I do? |
| 49 | +<img src="{{ '/_assets/images/fatal_error.png' | prepend: site.baseurl }}" alt="fatal_error.png :("> |
| 50 | + |
| 51 | +It sounds silly, but first check if your ESP32 is plugged in. |
| 52 | + |
| 53 | +Otherwise, this is usually caused by one of the other terminals in VS Code occupying the serial port. |
| 54 | + |
| 55 | +<img src="{{ '/_assets/images/trash_terminal.png' | prepend: site.baseurl }}" alt="trash_terminal.png :("> |
| 56 | +Delete all the terminals by clicking the trash icon for all of them and then try clicking the flash button again. |
| 57 | + |
| 58 | +If that fails, close VS Code and reopen it. |
| 59 | + |
| 60 | +If *that* fails, then check if there are any other applications on your computer that are occupying the COM port (extreme solution is to restart computer). |
| 61 | + |
| 62 | +## How to calibrate the QTR line sensor? |
| 63 | + |
| 64 | +<!-- ## Why doesn’t anything show up when I try printing to the serial monitor? --> |
| 65 | +<!-- idk if this is actually na issue?? --> |
0 commit comments