| Age | Commit message (Collapse) | Author | |
|---|---|---|---|
| 2025-02-18 | pcb: Add hierarchical labels and connections | xengineering | |
| 2025-02-18 | pcb: Replace text fields by symbol descriptions | xengineering | |
| This makes it easier to keep the descriptions and the text inside the schematic in sync. | |||
| 2025-02-18 | pcb: Set title to `iot-contact` | xengineering | |
| 2025-02-18 | pcb: Add missing text descriptions | xengineering | |
| 2025-02-18 | pcb: Rename some signals | xengineering | |
| 2025-02-18 | pcb: J7: Add motor connector | xengineering | |
| 2025-02-18 | pcb: J6: Add AC supply connector | xengineering | |
| 2025-02-18 | pcb: J5: Add door / window opener connector | xengineering | |
| 2025-02-15 | pcb: J4: Add vertical RJ45 connector | xengineering | |
| 2025-02-15 | pcb: J3: Add non-PoE 5V power input header | xengineering | |
| Power over Ethernet (PoE) has the disadvantage that GND is significantly below earth. This requires that GND of a PoE-powered device is never attached to earthed devices. In production use cases this is no problem. The earth lines are isolated. Nevertheless for debugging it is sometimes useful to connect measuring equipment like logic analyzers and oscilloscopes to the board. This is not possible with PoE. Thus an alternative earth-based 5V power input is useful. | |||
| 2025-02-15 | pcb: J2: Add UART pin header | xengineering | |
| 2025-02-15 | pcb: Fix connection errors reported by ERC | xengineering | |
| 2025-02-15 | pcb: SW1-SW2: Add switches for reboot and wipe | xengineering | |
| 2025-02-15 | pcb: D1-D3: Add LEDs for PWR, UPD and ACT | xengineering | |
| 2025-02-15 | pcb: J1: Add JTAG connector | xengineering | |
| 2025-02-15 | pcb: Update schematic hierarchy | xengineering | |
| 2025-02-14 | pcb: Add sub-schematics | xengineering | |
| 2025-02-14 | pcb: Add empty KiCad project | xengineering | |
| This is the starting point for the PCB development. | |||
| 2024-08-23 | pcb: Remove folder | xengineering | |
| It is planned to switch to Ethernet instead of LoRa for communication. Thus the custom PCB with the STM32WL MCU does not make sense anymore. To get started the Ethernet variant will use a ST NUCLEO board to avoid creating a custom PCB first. | |||
| 2024-06-08 | pcb: Add TLV70233 voltage converter | xengineering | |
| This IC has a small footprint and will provide the 3.3 V for the microcontroller. | |||
| 2024-06-05 | pcb: Split into a hierarchy of schematics | xengineering | |
| 2024-06-05 | pcb: Add 10-pin ARM Cortex debug connector | xengineering | |
| 2024-06-05 | pcb: Add USB-C connector to schematic | xengineering | |
| 2024-06-03 | pcb: Add STM32WL55JCIx microcontroller | xengineering | |
| Based on UM2592 the development kit Nucleo WL55JC which is used for firmware development is based on the STM32WL55JCI7 microcontroller. Thus this MCU should be a good starting point for now. | |||
| 2024-06-03 | pcb: Create empty KiCad 8.0 project | xengineering | |
 |
index : iot-contact | |
| IoT device to check if doors and windows are closed or open |
| summaryrefslogtreecommitdiff |