
Lateral led controller
cyberboy666/lateral_led_controller
hardware network controller for addressable led installations

Proof of concept for new door controller design using a WT32-ETH01.
Door controller is an open-source printed circuit board by MetaMakersCooperative, from the MetaMakersCooperative/M2C_Yet_Another_Door_Controller repository on GitHub, published under the GPL-3.0 licence. It is a 2-layer board of 130 × 87 mm with 35 parts on 62 nets, routed with 169 tracks and 0 vias.
It is built around the WT32-ETH01. Its parts include 12 resistors, 7 connectors, 4 transistors, 3 diodes and 2 ICs.
Proof of concept for new door controller design using a WT32-ETH01.
Make sure version v1.X of the Arduino IDE installed. It is required to upload the cards file. See Cards File section.
arduino-cli also needs to be installed to compile and upload the sketch. It is possible to use the Arduino IDE v1.X or v2 but they have not been tested/verified. Milage may vary.
The sketch assumes a file named cards.txt exists within a LitteFS file system. The code will not function correctly without it.
Unfortunately, the only way to upload the file to the device is using v1.X Arduino IDE. This is because the upload using a plugin that only can be used with that version of the IDE. Setting up the upload plugin is only required if the cards.txt file needs to be updated or if the flash storage was wiped.
To setup the plugin, follow the steps outlined below:
zip file: https://github.com/lorol/arduino-esp32fs-plugin/releases/download/2.0.7/esp32fs.zipesp32fs.jar file in the following directory: ~/Arduino/tools/ESP32FS/tool/esp32fs.jarBefore uploading, create the data directory in the project root if it does not already exist. Update/create the card.txt file with the codes that should unlock the door. Make sure each code is in it's own line, like below:
Each code should be no more than 10 digits long and only container digits
0-9. No leading zeros!
1234567
8912345
6789123Double check and make sure the project structure matches the following:
~/Arduino/M2C_Yet_Another_Door_Controller/
├── data
│ └── cards.txt
├── README.md
├── sketch.yaml
└── M2C_Yet_Another_Door_Controller.inoTo upload the card.txt file, follow the steps outlined below:
When referencing the Arduino IDE, it is implied that it's
v1.Xnotv2
M2CYetAnotherDoorController.ino sketch.Tools -> Board and select WT32-ETH01 Ethernet Module if it is not already selected.Tools -> ESP32 Sketch Date UploadLittleFS then click OKTo install the esp32 libraries run the following command:
arduino-cli core install esp32:esp32@3.0.2Might need to run
arduino-cli core update-indexto update the board index.
This will install espressif/arduino-esp32 version 3.0.2.
The following libraries can be installed using the Arduino IDE or by downloading the files directly from the source repositories.
When downloading the libraries manually, make sure the source is place them within the following directory: ~/Arduino/libraries.
The libraries should look like this assuming the only installed libraries are the ones used by this project.
~/Arduino/libraries
├── LinkedList
│ ├── ...
└── Yet_Another_Arduino_Wiegand_Library
├── ...Make sure to download the source tagged with the versions listed below!
The following dependencies need to be installed manually as the latest versions are required:
The best way to get these libraries is to
git clonethem into the~/Arduino/librariesdirectory.
556e7b8 tag: 2.0.10439a72 tag: v1.3.370d3113 tag: v1.7.0b20e92e tag: v3.1.4AsyncTCP is still required even though it's not being used
Note:
/dev/ttyUSB0is the default device. Run the following command to see what device is being used:arduino-cli board list. Make sure to modify the commands below to match that device.
To compile the sketch with defaults, run following command:
WARNING: Defaults will apply not overridden which could cause a lot of problems on multi door deployments. See the Override Defaults section below.
arduino-cli compile --fqbn esp32:esp32:wt32-eth01 ./To enable more debugging messages, run the following command:
arduino-cli compile --build-property "build.extra_flags=\"-DDC_DEBUG=1\"" --clean --fqbn esp32:esp32:wt32-eth01 ./To Upload the compiled sketch:
arduino-cli upload -p /dev/ttyUSB0 --fqbn esp32:esp32:wt32-eth01 ./To monitor the serial output:
arduino-cli monitor --log-level debug --fqbn esp32:esp32:wt32-eth01 -p /dev/ttyUSB0 -c baudrate=115200NOTE: The code assumes the MQTT server connection is TLS. Only TLS v1.2 is supported. Using TLS v1.3 will result in some weird errors.
The device will send logs, lock, unlock, and other events to the configured MQTT broker. If disconnected, only a few messages will be queued and sent when it's able to reconnect.
If the door_controller/access_list topic is received, the device will replace the card file with the payload, then attempt to reload the list from the updated file.
The device will also respond to messages with the door_controller/health_check topic. This is designed to help with monitoring the healthiness of the device.
root_ca.hUse the example file, root_ca.h.example, to create the root_ca.h file containing the root certificate for the MQTT broker.
NOTE: The root certificate will expire at some point so make sure you mark it in your calendar!
If you're using Let's Encrypt, then there is a good chance that the root certificate can be download from the following URL: letsencrypt.org/certs/isrgrootx1.pem
Otherwise, check out letsencrypt.org/certificates/ for a complete list.
Note: Make sure the latest Arduino CLI is installed
The table below shows the build flags that should be overridden for each controller being deployed. Refer to the source files for a complete list of overridable flags.
| Flag Name | Default | Description | Build Argument |
|---|---|---|---|
| DC_HOST_NAME | m2cdoorone | The value that will be set as the device's host name | -DDC_HOST_NAME=m2cdoorone |
| DC_CLIENT_ID | door_one | Client ID is used by the MQTT broker to identify the client. This value needs to be unique across all clients connected to the broker | -DDC_CLIENT_ID=door_one |
| DC_MQTT_HOST | mqtt.metamakers.org | Host name for the MQTT Broker. The host name is used to get the server IP using DNS | -DDC_MQTT_HOST=mqtt.metamakers.org |
| DC_MQTT_USER | door_one | The user that the MQTT client will use to authenticate | -DDC_MQTT_USER=door_one |
| DC_MQTT_PW | Door_One!1 | The password that the MQTT client will use to authenticate | -DDC_MQTT_PW=Door_One!1 |
| DC_NTP_HOST | pool.ntp.org | The domain used to update the RTC using NTP | -DDC_NTP_HOST=pool.ntp.org |
| DC_DEBUG | 0 | Enable more verbose debugging information via the serial port. Do not enable this for production deployments | -DDC_DEBUG=0 |
Below is an example of how to override all the flags in the table above:
Documentation on the CLI compile command can be found here.
arduino-cli compile --build-property "build.extra_flags=-DDC_DEBUG=0 \"-DDC_HOST_NAME=\"m2cdoorone\"\" \"-DDC_CLIENT_ID=\"door_one\"\" \"-DDC_MQTT_HOST=\"mqtt.metamakers.org\"\" \"-DDC_MQTT_USER=\"door_one\"\" \"-DDC_MQTT_PW=\"Door_One!1\"\" \"-DDC_NTP_HOST=\"pool.ntp.org\"\"" --clean --fqbn esp32:esp32:wt32-eth01 ./| Qty | Value | Footprint | References |
|---|---|---|---|
| 10 | 10k | Resistor_THT:R_Axial_DIN0204_L3.6mm_D1.6mm_P7.62mm_Horizontal | R1, R2, R3, R4, R5, R6, R7, R8, R11, R12 |
| 4 | TerminalBlock_Phoenix:TerminalBlock_Phoenix_MKDS-1,5-2_1x02_P5.00mm_Horizontal | J1, J2, J3, J4 | |
| 4 | MountingHole_3.2mm_M3_DIN965_Pad | MountingHole:MountingHole_3.2mm_M3_DIN965_Pad | MH1, MH2, MH3, MH4 |
| 3 | 1N4001 | Diode_THT:D_DO-41_SOD81_P10.16mm_Horizontal | D1, D2, D3 |
| 2 | 2N3904 | Package_TO_SOT_THT:TO-92_Inline | Q3, Q4 |
| 2 | 2N7000 | Package_TO_SOT_THT:TO-92_Inline | Q1, Q2 |
| 2 | 330 | Resistor_THT:R_Axial_DIN0204_L3.6mm_D1.6mm_P7.62mm_Horizontal | R9, R10 |
| 2 | Conn_01x09_Socket | Connector_PinSocket_2.54mm:PinSocket_1x09_P2.54mm_Vertical | J5, J6 |
| 2 | ~ | MyLibrary:RELAY8_J104D2C12VDC.20S_CRS | RELAY1, RELAY2 |
| 1 | Conn_01x04_Socket | Connector_PinSocket_2.54mm:PinSocket_1x05_P2.54mm_Vertical | J7 |
| 1 | LOGO | LOGO | G***1 |
| 1 | WT32-ETH01 | WT32-ETH01:WT32-ETH01 | U2 |
| 1 | YAAJ_DCDC_StepDown_LM2596 | MyLibrary:YAAJ_DCDC_StepDown_LM2596_Universal | U1 |

cyberboy666/lateral_led_controller
hardware network controller for addressable led installations




loack/ESP32-ETH01-WifiMQTT-Controller
Contrôleur générique d'I/O pour WT32-ETH01 avec Ethernet prioritaire et fallback WiFi.

LuisMiguel-efe/unikey
Sistema inteligente de control de acceso universitario mediante huella dactilar, con autenticación biométrica, FastAPI, MongoDB y Angular.

ondras12345/CNC
My CNC 1610 and Stepcraft model 600 configuration and CNC-related notes

sensslen/Cfg.CameraControl.Hardware
Hardware needed to control a lanc camera with a PTZ head
It measures 130 × 87 mm and has 2 copper layers, 1.6 mm thick.
35 parts, built around the WT32-ETH01. The full list of its parts is on this page, with links to each part's symbol and footprint where PCBKit's library has them.
From the MetaMakersCooperative/M2C_Yet_Another_Door_Controller repository on GitHub, at the commit this page was made from: the board is PCB/door-controller.kicad_pcb and its schematic PCB/door-controller.kicad_sch. PCBKit opens the board in the browser, with nothing to install.
Its repository publishes it under the GPL-3.0 licence: you may reuse it on that licence's terms (keep the author's notice, and for a copyleft licence share your changes alike).