Autoroute Project Setup
Worked for 18 sec
Autoroute could not start because there’s already an active auto-layout job on this project with status
outOfCredit.Preflight did pass, but it reported likely routing issues on
USER_BUTTON, UWB_SPI_CS, and UWB_SPI_MOSI due to blocked pins. To continue, discard or resolve the existing auto-layout job, then I can start the new autoroute.
Retry i've discarded
Worked for 6 sec
I’ll retry the autoroute now that the previous job was discarded, then I’ll check the result for remaining routing issues.
Worked for 39 sec
Retry still failed: the same auto-layout job is still blocking routing with status
outOfCredit.Board readiness check passes, but the autorouter won’t start until job
auto-layout-94801d1c-2912-4886-839c-4ea71b110296 is fully cleared/discarded. Also note: preflight still warns that USER_BUTTON has a blocked pin and may remain unrouted even after autoroute starts.Fix blocked pin
Run DRC instead
Check job clearing
Manual route key nets
Refine this doc
Ask about this doc
Project Specification — UWB Wearable Tracking Tag
Project Overview
Status: Draft schematic in progress.
Custom rechargeable UWB wearable badge/tag for warehouse employee tracking. The tag must interoperate with an existing DW3000-based RTLS anchor infrastructure, specifically Makerfabs MaUWB ESP32S3 anchors using the Qorvo DW3000 family.
Intended Use
- Wearable employee badge for warehouse environments.
- First-generation small-batch hardware platform suitable for PCBWay manufacture/assembly.
- No enclosure design in this revision; PCB and assembled component height should support a future thin badge enclosure.
What the Device Should Do
- Wake on motion and periodically perform UWB ranging/tag activity.
- Use BLE from the Nordic MCU module for local configuration/diagnostics if firmware enables it.
- Recharge from USB-C.
- Run for multiple days in active tracking mode and months in standby, subject to firmware duty cycle and battery selection.
Main Features
- Qorvo DWM3000 UWB module with integrated antenna.
- Raytac MDBT50Q-P1MV2 nRF52840 BLE module, selected instead of a bare nRF52840 to reduce BLE RF layout/certification risk.
- ST LIS2DW12 accelerometer for ultra-low-power motion wake.
- 500–1000 mAh single-cell LiPo input via JST-PH style connector.
- USB-C charging input using single-cell LiPo charger.
- SWD debug/programming interface and production test pads.
- One user pushbutton and one low-current optional status LED.
System Architecture
Diagram
Hardware Subsystems
- Power: USB-C sink input, ESD/protection, LiPo charger, protected battery connector, low-Iq 3.3V regulator, MCU-controlled UWB load switch.
- Compute/Wireless: MDBT50Q-P1MV2 nRF52840 module provides BLE, MCU, integrated RF matching/antenna, and simplified layout/certification path.
- UWB: DWM3000 module connected over SPI with IRQ, reset, wake/enable as supported by module pins; antenna keepout and edge placement required.
- Motion: LIS2DW12 on I2C with interrupt routed to an MCU wake-capable GPIO.
- UI: one normally-open tactile switch and one status LED with high-value series resistor; LED defaults off for low power.
- Debug/Test: SWDIO, SWDCLK, RESET, VREF, GND, 3V3, UART/test pads, UWB SPI test pads as space allows.
Power and Runtime Expectations
Runtime is dominated by UWB duty cycle. Hardware will minimize sleep current by keeping LIS2DW12 active, putting the nRF52840 module in system OFF/sleep, disabling the UWB module load switch when inactive, and using high-value/leakage-conscious battery monitor circuitry.
Power Tree and Initial Power Budget
Table
| Mode | Estimated Current | Notes |
|---|---|---|
| Deep standby | target <25 uA | LDO Iq + module sleep + LIS2DW12 low-power + charger leakage + divider leakage |
| BLE/config idle | 1-10 mA avg | firmware dependent |
| UWB active burst | 100-200 mA peak | DWM3000 module dominates; regulator/load switch sized with margin |
| USB charge | 100-500 mA | charge current to be set for thin LiPo cell and thermal constraints |
Selected power-path sizing target: 3.3V rail and UWB switch should support at least 250 mA peak; USB/charger path should support 500 mA charge input but default charge current should be conservative for 500 mAh cells unless the cell datasheet permits more.
Manufacturing and Assembly Expectations
- PCBWay-compatible 4-layer PCB preferred.
- SMD assembly for compact wearable form factor.
- Target board: 40-50 mm wide x 50-70 mm tall.
- Assembled thickness target under 15 mm including battery.
- Use library parts with real terminals and datasheets where possible; passives may be generic but should map to common 0603/0402 footprints.
Firmware-Relevant Hardware Requirements
- MCU controls UWB load switch enable and UWB reset/wake.
- LIS2DW12 interrupt can wake MCU.
- Battery ADC uses a high-value divider; future revision may add divider switching if leakage must be further reduced.
- SWD programming header/test pads must be present.
- Optional UART/test pads for early firmware diagnostics.
Physical Design Expectations
- DWM3000 at board edge with antenna area facing outward.
- MDBT50Q module antenna/keepout at a board edge with no copper/traces/components under the antenna region.
- No copper, traces, vias, battery, or components in UWB/BLE antenna keepout regions per module guidance.
- USB-C on an accessible edge.
- Battery connector positioned to keep battery leads short and mechanically protected.
- Decoupling capacitors close to IC/module power pins.
Important Design Decisions
- Use DWM3000 module rather than bare DW3000 to reduce RF layout risk.
- Use Raytac MDBT50Q-P1MV2 module rather than bare nRF52840 to reduce BLE RF matching, antenna, and certification risk.
- Use load switch for UWB power gating.
- Use 4-layer stackup for RF return paths and power integrity.
Assumptions
- USB-C is sink/charging only; no USB data is required unless later requested.
- Battery pack includes its own protection PCB, but board-level charger/protection-friendly design is still included.
- DW3000 anchor compatibility will be implemented primarily in firmware/protocol configuration; hardware provides the DWM3000 radio platform.
Change Notes
- Initial requirements captured from user request on 2026-06-08.
- Updated on 2026-06-08 to replace bare nRF52840 with Raytac MDBT50Q-P1MV2 module.
Project Overview
Intended Use
What the Device Should Do
Main Features
System Architecture
Hardware Subsystems
Power and Runtime Expectations
Power Tree and Initial Power Budget
Manufacturing and Assembly Expectations
Firmware-Relevant Hardware Requirements
Physical Design Expectations
Important Design Decisions
Assumptions
Change Notes
