Skip to content

Commit 0507d77

Browse files
committed
made line clearer. added more git content
1 parent a3cea75 commit 0507d77

File tree

4 files changed

+23
-2
lines changed

4 files changed

+23
-2
lines changed
-50.2 KB
Loading

docs/_sections/_guide-primaries/getting-started/git.md

Lines changed: 14 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -101,6 +101,19 @@ At commit B, a new branch called `feature-branch` is created. From this branch,
101101
## How to deal with merge conflicts
102102
A **merge conflict** occurs when you try to merge (i.e. git pull) two branches that have made different changes to the same part of a file. Git can't automatically figure out which change to keep, so it needs your help to resolve the conflict.
103103

104+
{: .highlight}
105+
Note that a `git pull` that triggers a merge conflict may open a terminal text editor like Vim or Nano.
106+
107+
**For Vim:**
108+
- To save and continue: Press `Esc`, type `:wq`, then press `Enter`
109+
- To abort: Press `Esc`, type `:q!`, then press `Enter`, then run `git merge --abort`
110+
111+
**For Nano:**
112+
- To save and continue: Press `Ctrl+O`, press `Enter`, then press `Ctrl+X`
113+
- To abort: Press `Ctrl+X`, press `N` if prompted to save, then run `git merge --abort`
114+
115+
{: .callout-blue}
116+
104117
In the problem file, Git marks the conflicting area with special markers that looks something like this:
105118

106119
```cpp
@@ -137,3 +150,4 @@ int main() {
137150
}
138151
```
139152

153+
Once you've done that, you can then stage your merge fix changes and commit them (`git add .` followed by `git commit -m "<message>"`)

docs/_sections/_guide-primaries/sensors-and-actuators/color-sensors.md

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -42,6 +42,8 @@ Here is a wiring diagram:
4242
| SDA | GPIO21 |
4343
| SCL | GPIO22 |
4444

45+
If you're not sure about the ESP32 pinout, then check out [this page!](https://ut-ras.github.io/RobotathonESP32/getting-started/microcontroller-interface)
46+
4547
{: .highlight}
4648
Make sure to connect the color sensor's power pin to 3.3V! A 5V connection will fry the sensor.
4749
{: .callout-blue}

docs/_sections/_guide-primaries/sensors-and-actuators/line-sensors.md

Lines changed: 7 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -16,7 +16,7 @@ This side of the sensor will be facing the floor to detect the line:
1616
<img src="{{ '/_assets/images/line_sensor_diodes.png' | prepend: site.baseurl }}" alt="line_sensor_diodes.png">
1717

1818
{: .highlight}
19-
Note: You do NOT have to use all 8 of the LED/phototransistor pairs — You can leave the ones you do not want to use disconnected from the ESP32.
19+
You do NOT have to use all 8 of the LED/phototransistor pairs — You can leave the ones you do not want to use disconnected from the ESP32.
2020
{: .callout-blue}
2121

2222
<img src="{{ '/_assets/images/line_sensor_wire_diagram.png' | prepend: site.baseurl }}" alt="line_sensor_wire_diagram.png">
@@ -26,7 +26,12 @@ Note: You do NOT have to use all 8 of the LED/phototransistor pairs — You can
2626
| 5V | 5V |
2727
| GND | GND |
2828
| Signal | Any ADC Capable Pin (i.e. GPIO32) |
29-
| Signal | Any ADC Capable Pin (i.e. GPIO33) |
29+
30+
If you're not sure about the ESP32 pinout, then check out [this page!](https://ut-ras.github.io/RobotathonESP32/getting-started/microcontroller-interface)
31+
32+
{: .highlight}
33+
This wiring diagram only shows the situation where 1 IR/phototransistor pair is used. If you want to use more, simply use more ADC capable pins
34+
{: .callout-blue}
3035

3136
## Programming
3237
The following program will allow you to continuously read the sensor data from 2 of the photodiode sensors. You will have to calibrate the sensors by positioning the ones you want to use directly over the black electrical tape. If you need to use more than 2 sensors, then you can also move the line sensor back and forth over the black electrical tape to calibrate it.

0 commit comments

Comments
 (0)