-
Notifications
You must be signed in to change notification settings - Fork 9
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Various changes and polish to entries (#81)
- Loading branch information
1 parent
c4e13da
commit fd1abc0
Showing
10 changed files
with
97 additions
and
49 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,29 +1,41 @@ | ||
|
||
This guide mainly focuses on the parts listed in the [Hardware Buy guide](hardware-buying.md). | ||
|
||
## Hardware Requirements | ||
## Hub Hardware Requirements | ||
|
||
+ ESP-32 | ||
+ 433 MHz transmitter | ||
+ Soldering station (optional) | ||
+ ESP32 board | ||
+ 433 MHz transmitter (ASK/OOK) | ||
+ Soldering station (potentially optional) | ||
+ Hookup wire (optional, depending on whether the pins line up) | ||
|
||
## What/Where to buy? | ||
|
||
See the [Hardware Buy guide here](hardware-buying.md). For the board/ESP-32 assembly you need the ESP-32 and a 433 MHz transmitter. | ||
See the [hardware buying guide here](hardware-buying.md). For the hub assembly you'll need an ESP32 and a 433 MHz transmitter. | ||
|
||
## Figuring out the PINs | ||
## Figuring out the pins | ||
|
||
Any digital output pin on your micro-controller should work for outputting the signal for the transmitter, however the default is often close to the positive and ground pins on the controller. See the [boards](../hardware/boards/index.md) section dedicated to the micro-controller you are using to decide which pin to use. | ||
You will need to connect the 433MHz transmitter's signal input pin to one of the ESP32's IO pins, and you can optionally connect an Emergency Stop button/switch to another pin. | ||
|
||
*Most* of the GPIO pins on any given ESP32 board should work for both RF TX and E-Stop, however some pins are reserved for special usage and will return an error if you attempt to use them during setup. If you run into that error, adjust your setup to use a different pin with a higher number. | ||
|
||
Note down which GPIO pins you soldered to, as you will need to enter them during setup in a later step. | ||
|
||
For example, if you bought a [Wemos Lolin S3](../hardware/boards/wemos/lolin-s3.md) and a [Open Smart Transmitter](../hardware/transmitter/china/open-smart.md), simply connect the 5V to the 5V pins (aka VCC), ground to ground, and any numbered pin to data, for example, the 12 pin. | ||
|
||
!!! warning "Pins" | ||
You will need to set your RFTX pin during setup. If the pin is incorrect the transmitter wont be able to send any signals. | ||
If you already went through the setup process, you can change the pin via a serial terminal with the command `rftxpin #` where `#` is your pin number. | ||
Or you reenable the Captive Portal on the website and connect to it again with your phone. | ||
!!! warning "Don't forget to enter these during setup!" | ||
You will need to set your RF TX pin during setup. If the pin is incorrect the transmitter wont be able to send any signals to the shockers. | ||
|
||
If you already went through the setup process, you can change the pin via a serial terminal with the command `rftxpin #` where `#` is your pin number. | ||
|
||
You can change E-Stop pin with `estop pin #` where `#` is your pin number. | ||
|
||
Or, you can re-enable the Captive Portal on the website under the Hub's "..." menu and connect to it again with your phone. | ||
|
||
|
||
 | ||
|
||
!!! warning "Logic level compatibility" | ||
Please note that all ESP32s operate at 3.3V logic levels. To avoid overvolting your ESP's IO pins, it is recommended to either: connect your transmitter's power input to a 3V supply pin on the ESP's board, or use a logic-level shifter if your transmitter ***really* requires** more than 3V power to operate. | ||
|
||
|
||
**Next step is [flashing the firmware.](../guides/openshock-how-to-flash-your-board.md)** | ||
**Next step is [flashing the firmware!](../guides/openshock-how-to-flash-your-board.md)** |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,2 +1,11 @@ | ||
# Do-It-Yourself | ||
|
||
### As a user | ||
|
||
[Buying parts for my own hub](./hardware-buying.md) | ||
|
||
[Assembling my hub](./assembling.md) | ||
|
||
### As a host | ||
|
||
[Setting up my own OpenShock instance](../guides/selfhosting/index.md) |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters