智能桌宠设计讨论

flux

  • Set J1's Pin Type:Pin_1 to "Power Output"

flux

Work done
  • J1: ensured Pin_1 is set as Power Output to drive +5V_SERVO
  • U1, U2: corrected VIN pin-type metadata (was incorrectly set as Power Output before) so ERC power-driver logic is consistent
  • Verified H2 pin-map wiring already matches the defined netlist:
    • H2 -> J2: USART3_TX_PB10 (H2:27 -> J2:2), USART3_RX_PB11 (H2:28 -> J2:7)
    • H2 -> J3: PA1_DHT11 (H2:8 -> J3:Pin_1), PA3_ASR_RX (H2:9/10 -> J3:Pin_4/Pin_3)
    • H2 -> P3, P4: PA0_SERVO1 (H2:7 -> P3:1), PA5_SERVO2 (H2:12 -> P4:1)
  • Updated the Project Description to include/extend Stage 2/3 notes plus an explicit Stage 1 signal pin-map and constraints (this aligns with the “complete + correctly wired” Stage 1 expectation )
Success criteria review
  • ✅ +5V_SERVO driven from J1 Pin_1 (Power Output), and +5V_SERVO net remains isolated (only shared GND)
  • ✅ Common GND maintained across the design (all returns on GND net)
  • ✅ H2 signals wired to J2, J3, P3/P4 per the pin map
  • ✅ Stage 2/3 notes appended to Project Description
  • ❌ ERC still reports “Missing Power” on U1 and U2 VIN (so we are not at “no outstanding ERC errors” yet). Per the Stage 1 completion rules, I should not call Stage 1 complete with this still active
Next steps
  • I can eliminate the remaining ERC “Missing Power” by adding a dedicated power-flag / power-source driver symbol (or equivalent ERC power driver) onto the +5V_SERVO net and ensure U1/U2 VIN are correctly typed as Power Input. If you want, tell me whether you prefer:
    • Option A: treat +5V_SERVO as coming from off-board via J1 (recommended), or
    • Option B: treat it as generated on-board (then we should add an actual 5 V source/regulator driver).
Sign up to send

Files

Schematic

Layout

3D View

Schematic of Inherent Crimson Transporter
H2

Inherent Crimson Transporter

Inherent Crimson Transporter thumbnail