Reference schematic
Can Crusher
YasiruBasura-Can-Crusher-8-Can-Crusher-schematic
Loading the viewer…
YasiruBasura-Can-Crusher-8-Can-Crusher-schematic
Take the project archive: a schematic is a root sheet plus every sub-sheet beside it, and the root alone opens with its hierarchy missing. The archive is zstd-compressed (tar.zst).
Bill of materials
28 distinct parts
17 resolve to something in the catalog — click through to the component.
| Ref | Value | Symbol | Qty |
|---|---|---|---|
| C1 | 0.1uF | Device:C_Small | |
| C2 | 22pF | Device:C | |
| C3 | 22pF | Device:C | |
| C4 | 10uF | Device:C_Polarized_Small | |
| DS1 | LM016L | ICT Project 2:LM016L | |
| J1 | USB Module | Connector:Conn_01x02_Male | |
| J2 | IR Sensor | Connector:Conn_01x03_Male | |
| J3 | IR Sensor | Connector:Conn_01x03_Male | |
| J4 | Inductive Proximity Sensor | Connector:Conn_01x03_Male | |
| J5 | AC Power | Connector:Conn_01x03_Male | |
| K1 | Relay | Relay:DIPxx-1Axx-13x | |
| Keypad1 | Conn_01x08_Female | Connector:Conn_01x08_Female | |
| M1 | Motor_Servo | Motor:Motor_Servo | |
| M2 | Stepper_Motor_bipolar | Motor:Stepper_Motor_bipolar | |
| M3 | Motor_AC | Motor:Motor_AC | |
| Q1 | 2N4403 | Transistor_BJT:2N3906 | |
| R1 | 20k | Device:R | |
| R2 | 8.2k | Device:R | |
| U1 | ATmega32 | MCU_Microchip_ATmega:ATmega32A-P | |
| U2 | HC-SR04 | HC-SR04:HC-SR04 | |
| U3 | HX711 | Sensor_Current:HX711 | |
| U4 | SIM900A | SIM900A:SIM900A | |
| U5 | ATmega32 | MCU_Microchip_ATmega:ATmega32A-P | |
| U6 | LCD-016N002L | Display_Character:LCD-016N002L | |
| U7 | L293D | Driver_Motor:L293D | |
| U8 | 7404 | 74xx_IEEE:7404 | |
| U9 | LC1-Load_Cell | Analog:LC1-Load_Cell | |
| Y1 | Crystal | Device:Crystal |
Provenance
- Repository
- YasiruBasura/Can-Crusher ↗
- Commit
- unknown
- Licence
- CC-BY-4.0
How it is used
Trace's agent reads this design as context — what parts a board like this carries, how they are grouped across sheets, what a plausible layer stack and board size look like for the job. It is not copied. The licence above is permissive, and it, the repository and the commit are recorded so the origin of anything derived from it is always answerable.