Skip to the content
4 layers72.6 × 72.6 mmFOC V1 PCB, the printed circuit board in 3D

A custom-designed, 60V 50A Field Oriented Control (FOC) BLDC motor controller built from scratch. Designed for high-performance robotics, featuring a 4-layer power PCB, isolated USB telemetry, and CAN bus communication.

Size
72.6 × 72.6 mm
Copper layers
4
Thickness
1.6 mm
Parts
95
Nets
112
Pads
383
Tracks, vias
914, 340
Pours
443
Routed
Yes
KiCad
KiCad 10.0 (file 20260206)
Created
26 Jul 2026
Updated
4 Nov 2026

Overview

FOC V1 PCB is an open-source printed circuit board by arthur-wirjo, from the arthur-wirjo/FOC_v1_project repository on GitHub, published under the MIT licence. It is a 4-layer board of 72.6 × 72.6 mm with 95 parts on 112 nets, routed with 914 tracks and 340 vias.

It is built around the STM32F405RGT6, TJA1051T/3/1J and DRV8301DCAR, with the IRFS7530TRL7PP, HYCW498-USBC16-735B and SMCJ43A among its other parts. Its parts include 43 capacitors, 26 resistors, 10 ICs, 8 connectors and 1 diode. It belongs with the robots and motor control boards and the STM32 boards of this library.

Main components

7

README

README.md

DIY FOC Motor Controller V1: Custom Hardware & Firmware from Scratch

FOC_v1 3_pic FOC_v1 3_pic2 FOC_v1 3_setup2 FOC_v1 0-1 2

A custom-designed, 60V 50A Field Oriented Control (FOC) BLDC motor controller built from scratch. Designed for high-performance robotics, featuring a 4-layer power PCB, isolated USB telemetry, and CAN bus communication.

Overview

I started this project to deeply understand the hardware architecture of modern, high-power motor drivers like the VESC and ODrive. Instead of just buying an off-the-shelf driver, I wanted to design one from the ground up to learn the intricacies of power electronics, mixed-signal PCB layout, gate driving, and hardware debugging.

The system is split into a 4-layer main power board (handling the MCU and 60V power stage) and a separate 2-layer magnetic encoder board mounted directly to the motor. This approach kept the overall footprint compact and reduced manufacturing costs.

As the project progressed, it evolved beyond "build a VESC clone" into writing a full custom bare-metal FOC firmware stack from scratch. As of October 3, 2026, the board successfully runs closed-loop Field-Oriented Control, achieving smooth velocity control. Having fulfilled its purpose as a deep-dive educational tool into power electronics and motor control theory, this project is now officially concluded. The repository remains as a documented post-mortem and reference for DIY FOC development.

Key Features

  • Working Closed-Loop FOC: Fully custom bare-metal firmware achieves smooth closed-loop current control and velocity control.
  • 60V Power Stage: 60V-rated MOSFETs capable of handling 10S Li-Po battery voltages and regenerative braking spikes.
  • Precision Current Sensing: 1mΩ shunt resistors utilizing strict Kelvin connections and RC-filtered differential amplifiers.
  • Isolated Telemetry: ADuM3160-based USB isolation to protect the host computer from catastrophic 60V transients during live tuning.
  • Robust Communication: TJA1051T/3 CAN bus transceiver with 120Ω termination for robot networking.
  • Modular Encoder: Separate 2-layer AS5048A magnetic encoder PCB using JST-GH SMD connectors.

Hardware

Computing & Control

  • Microcontroller: STM32F405RGT6 (Chosen for its floating-point unit, advanced motor control timers, and native VESC compatibility)
  • Gate Driver: TI DRV8301 (Features a built-in 5V buck converter and dual current shunt amplifiers. Chosen over the DRV8323 for VESC compatibility)

Power Stage

  • MOSFETs: Infineon IRFS7530 in D2PAK-7 (Rated for 60V, providing ample headroom for a 10S ~40V battery and regenerative braking)
  • Current Sense: Yageo PU2512FK-070R001L (1mΩ, 2W metal alloy shunts)
  • Protection: Littelfuse SMCJ43A TVS Diode (Clamps dangerous voltage spikes generated by motor back-EMF during hard braking)
  • Connectors: Amass XT90-S (Anti-spark) for battery input

Sensing & Telemetry

  • Encoder: AMS AS5048A (14-bit absolute magnetic encoder reading a 6x2.5mm diametrically magnetized NdFeB magnet)
  • Temperature: Murata 10kΩ 0603 NTC Thermistor (Placed directly adjacent to the MOSFETs to monitor power stage thermals)
  • Voltage Sensing: 39kΩ / 2.2kΩ voltage divider to safely scale the 60V bus down to the STM32's 3.3V ADC range

PCB Design & Layout

The board utilizes a 4-layer stackup to safely separate high-current paths from delicate digital signals:

  • Layer 1 (Top): Components, massive copper polygons for Motor Phases and 42V supply.
  • Layer 2 (Inner 1): Solid GND plane (Acts as an EMI shield for the signal layer).
  • Layer 3 (Inner 2): Signal routing (SPI, CAN, Gate Drive traces).
  • Layer 4 (Bottom): Additional GND and 42V copper pours, heavily via-stitched to the top layer to maximize current carrying capacity and thermal dissipation.

Challenges and Lessons Learned

Building a high-power motor controller from scratch provided an intense, hands-on education in hardware and firmware debugging.

Solder Wicking and Clearance Tolerances (V1.0)

After freshly soldering the V1.0 PCB, I felt an unusually strong resistance when I tried to rotate the motor by hand. I learned this is caused by back-EMF when phase wires are shorted together. Multimeter testing confirmed that V++, GND, and all three motor phases were dead-shorted.

Upon inspection, I realized the clearance between my GND copper pour and the soldering pads for V++ and the phase wires was very small (0.15mm). When hand-soldering the massive motor wires, the liquid solder easily wicked across that tiny gap into the GND pour.

For V1.1, I redesigned the board with strict Net Classes, increasing the clearance around high-power wire pads to 0.6mm to create a physical "moat", while keeping the MCU digital clearance at 0.15mm for dense routing.

The "Bad Internet Symbol" Trap (V1.1)

After successfully assembling V1.1 with new stencils and corrected clearances, the board still exhibited a short between V++, GND, and the phase wires.

I started isolating the issue by desoldering components one by one. I checked a bare V1.0 board and found no shorts, meaning the layout itself wasn't fundamentally shorted. I desoldered the MCU and gate driver — the short was still there. Finally, I desoldered the high-side MOSFETs one by one. Removing the last high-side MOSFET finally severed the short between V++ and the motor phases.

I probed the desoldered MOSFET and found a short between Pin 7 and the Source pins (Pins 2-6). Initially, I thought the MOSFET had overheated and failed closed during hot-plate reflow. However, I looked into the Infineon datasheet and saw a catastrophic error in the third-party CAD symbol I had downloaded.

The symbol incorrectly labeled Pin 7 as "Drain". In reality, the D2PAK-7 package uses the large back EPAD as the Drain, and Pins 2 through 7 are all Source pins. Because I followed the flawed schematic, my PCB layout drew a massive copper pour that physically connected the Drain (EPAD) to the Source (Pin 7). The PCB itself was shorting the circuit by design, while the MOSFETs were actually unharmed.

Lesson learned: Never trust third-party CAD footprints without verifying against the manufacturer's datasheet.

The USB D+/D- Swap (V1.2)

With the phase-short issue resolved, V1.2 soldered up cleanly with no shorts between V++, GND, or the phase wires. After hours of VESC firmware macro configuration, I successfully flashed VESC firmware onto the board. However, the board never enumerated over USB — nothing populated on the host PC.

I re-checked the firmware configuration and it looked correct, so I moved to the hardware. It turned out to be a wiring mistake on my end, though the confusing pin naming in the schematic symbol didn't help: instead of connecting DP1↔DP2 and DN1↔DN2 (the isolator-side and MCU-side USB differential pairs), I had wired DP1↔DN1 and DP2↔DN2 — crossing the differential pairs instead of linking them straight through. I corrected this for V1.3.

The Mysterious Non-Enumerating USB (V1.3)

V1.3 fixed the DP/DN wiring mistake. USB still did not enumerate.

At this point I was confident the hardware was correct, so I wrote a minimal bare-metal STM32 firmware (via STM32CubeMX, STM32CubeIDE, and STM32CubeProgrammer) with nothing but a USB CDC "hello world" to test enumeration independently of VESC firmware. It worked immediately — the host PC detected the board and the virtual COM port came up cleanly. This confirmed the hardware (including the USB isolation and the DP/DN fix) was fine, and the problem was somewhere inside VESC firmware itself.

After a weekend of digging, my working theory is that VESC firmware assumes VBUS sensing on a specific pin by default, which on my board doesn't correspond to an actual VBUS-sensing net — that pin (PA9 / TIM1_CH2) is repurposed as a motor PWM output on my hardware. If VESC firmware is waiting on a VBUS-sense signal that physically doesn't exist on my board, USB enumeration would never complete, since the firmware assumes the connection is dead.

Rather than dig further into VESC's fairly large and unfamiliar codebase to patch around this, I decided to use this as an opportunity to learn embedded systems more deeply from first principles by writing my own bare-metal FOC firmware from scratch.

The Deceiving Cogging Torque (Open-Loop Commutation)

After first achieving open-loop commutation, I later struggled to reproduce it and assumed something had regressed in the firmware. After investigation, I realized the real cause: during my initial successful test, the motor had warmed up from repeated open-loop parameter tuning, which reduced its cogging torque (magnetic detent force) enough for the open-loop drive to overcome it smoothly. On a cold motor, the same open-loop parameters weren't enough to break through cogging torque cleanly. This was a good reminder that motor behavior is temperature-dependent, and that "it worked once" isn't the same as "it's tuned correctly."

Missing Bulk Decoupling Capacitor (Current Sensing Noise)

While debugging noisy phase current readings, a senior pointed out that the DRV8301's built-in 5V buck converter was missing a bulk decoupling capacitor on my board. Without it, switching-induced ripple on the 5V rail was likely feeding through to the gate driver's built-in current sense amplifiers, degrading signal quality. I added the missing capacitor directly onto the existing V1.3 board (Frankenstein-style, dead-bug soldered), which noticeably cleaned up the current readings enough for stable closed-loop control. This will be properly integrated into the layout for the next PCB revision.

Current Sensing Offsets and Phase Anomalies (The Final Hurdle)

While closed-loop velocity control was achieved, the final hurdle involved anomalies in the low-side current sensing. Through telemetry analysis under load, I observed three distinct issues:

  1. DC Offsets: Despite software calibration, i_a exhibited a heavy positive offset (min -0.05A, max 0.35A), i_b (calculated) had a heavy negative offset, and i_c was relatively balanced. This points to inherent analog front-end biases or layout-induced ground offsets.
  2. Noise: Low-side sensing is notoriously susceptible to switching noise. Even with ADC sampling synchronized to the timer's update event (the "quiet window"), the raw data remained spiky, pushing the limits of the software's low-pass filters.
  3. The 180-Degree Phase Shift Anomaly: Telemetry revealed that i_a and i_c appeared to be roughly 180 degrees out of phase, rather than the expected 120 degrees. Initially, one might suspect a flipped differential pair on the PCB, but mathematically, inverting a 120-degree signal results in a 300-degree (-60 degree) phase shift, not 180 degrees. This anomaly is much more likely an artifact of severe layout-induced noise, ground bounce, or the inherent limitations of low-side current sensing on a noisy DIY board skewing the reconstructed waveforms.

Lesson learned: Mixed-signal PCB layout for high-current switching requires extreme care. For V2, I would transition to in-line current sensing with dedicated isolated amplifiers, ensure perfectly matched differential pair routing for the shunts, and implement a more robust analog filtering stage.

Custom Firmware Development

Since abandoning VESC firmware, I built a custom bare-metal firmware stack using STM32CubeMX, STM32CubeIDE, and FreeRTOS (for telemetry and state management), with the actual FOC control loop implemented as a hardware-timer/ADC-interrupt-driven routine.

MCU Pinout

PWM (TIM1, Center-Aligned, Complementary Outputs)

PinFunction
PA8TIM1_CH1
PA9TIM1_CH2
PA10TIM1_CH3
PB13TIM1_CH1N
PB14TIM1_CH2N
PB15TIM1_CH3N

ADC (Current & Voltage Sensing)

PinFunction
PA0ADC1_IN0 — Phase A Current
PA1ADC2_IN1 — Phase C Current
PA2ADC3_IN2 — VBUS Voltage Sensing
PA3ADC3_IN3 — MOSFET Temperature

DRV8301 Gate Driver (SPI1)

PinFunction
PC1EN_GATE
PC2DC_CAL
PC0nFAULT (EXTI0)
PB3SPI1_SCK
PB4SPI1_MISO
PB5SPI1_MOSI
PD2CS

Encoder (SPI3)

PinFunction
PC10SPI3_SCK
PC11SPI3_MISO
PC12SPI3_MOSI
PA15CS

CAN

PinFunction
PB8CAN1_RX
PB9CAN1_TX

USB

PinFunction
PA11D-
PA12D+

Critical note: VBUS sensing on PA9 is intentionally not used — PA9 is a motor PWM pin on this board (see the V1.3 debugging story above). USB is forced to enumerate without relying on VBUS sensing.

STM32CubeMX Configuration Notes

  • Deadtime configured on the PWM timer to prevent shoot-through.
  • Center-aligned PWM mode for reduced current ripple.
  • ADC sampling is hardware-synchronized to PWM switching using TIM1's "Update Event" as the ADC "Trigger Event Selection," so current is always sampled at a consistent point in the switching cycle.
  • Third phase current is reconstructed using Kirchhoff's Current Law rather than measured directly (only two shunts are sensed).
  • ADC current sensing uses injected conversion mode so it can be hardware-triggered directly by the timer.
  • ADC interrupt enabled in NVIC settings for the current-sensing ADC.
  • Encoder SPI configured with DMA in full-duplex master mode.
  • USB configured using the USB CDC class for direct serial communication with the host PC.

Firmware Development Progress

  1. ✅ Pinout and hardware configuration in CubeMX
  2. ✅ USB CDC enumeration working
  3. ✅ DRV8301 register read helper function + gate driver wake-up sequence
  4. ✅ SPI encoder DMA callback
  5. ✅ Open-loop SPWM commutation and tuning
  6. ✅ DRV8301 register write helper function for current amplifier gain configuration
  7. ✅ ADC hardware interrupt callback for current sensing (HAL_ADC_ConvCpltCallback)
  8. ✅ FOC algorithm implemented inside HAL_ADC_ConvCpltCallback
  9. ✅ Closed-loop current control achieved
  10. ✅ Closed-loop velocity control achieved — smooth motor spin under true FOC

Current Firmware State (Final)

  • Closed-loop Field-Oriented Control is working on hardware: the motor spins smoothly under closed-loop velocity control.
  • Open-loop SPWM commutation, ADC-synchronized current sensing, and gate driver configuration are validated.
  • Future Improvements (Left as an exercise for V2): Transitioning to in-line current sensing to resolve the noise and phase shift anomalies, implementing automatic motor R and L measurement, and adding trajectory generation (slew-rate limiting) for smoother bidirectional startups.

Current Status

  • V1.0 & V1.1: Deprecated — used for footprint verification and short-circuit debugging (solder wicking clearance issue, mislabeled MOSFET footprint).
  • V1.2: Deprecated — resolved the phase-short issues from V1.0/V1.1, but had a USB differential pair wiring mistake (DP/DN crossed) that prevented USB enumeration.
  • V1.3 (Final): USB wiring fixed and verified via custom bare-metal USB CDC test firmware. Pivoted to a fully custom bare-metal FOC firmware stack. Closed-loop FOC achieved and validated on hardware. Smooth closed-loop velocity control is working. The project is now officially closed, serving as a successful proof-of-concept and an invaluable learning experience in embedded systems and power electronics.

Project Timeline

DateMilestone
Jun 5Project start
Jun 19Theory research complete
Jul 2Schematic & component sourcing complete
Jul 13V1.0 PCB layout complete
Jul 23V1.0 assembled
Jul 27V1.0 testing — discovered phase/GND short from insufficient copper clearance (0.15mm)
Jul 30V1.1 redesigned with wider clearances
Aug 22V1.1 assembled — short persisted
—Root cause found: mislabeled MOSFET footprint (Drain/Source swap)
Aug 28V1.2 arrives (footprint fixed)
—Discovered incorrect USB D+/D- wiring
Sep 9V1.3 arrives (USB wiring corrected)
Sep 13Began VESC firmware integration — blocked by USB enumeration failure
Sep 17Diagnosed VBUS-sensing conflict; pivoted to custom bare-metal firmware
Sep 19Open-loop commutation achieved (later traced intermittent failures to motor-temperature-dependent cogging torque)
Sep 22ADC current sensing achieved (noisy — later traced to missing decoupling capacitor)
Sep 24Fixed missing decoupling capacitor; current sensing quality improved
Sep 25Closed-loop current control achieved
Sep 28Closed-loop velocity control achieved — true FOC working
Oct 3Telemetry analysis completed. Project officially concluded and documented as a post-mortem.

Parts

95
QtyValueFootprintReferences
10100nFCapacitor_SMD:C_0603_1608Metric_Pad1.08x0.95mm_HandSolderC16, C20, C21, C22, C23, C30, C31, C36, C44, C45
710kΩResistor_SMD:R_0603_1608Metric_Pad0.98x0.95mm_HandSolderR4, R5, R12, R14, R15, R19, R26
6IRFS7530TRL7PPFOC_foot_lib:IRFS7530_PG-TO263-7_INFU3, U4, U5, U6, U7, U8
52.2µFCapacitor_SMD:C_0805_2012Metric_Pad1.18x1.45mm_HandSolderC6, C7, C28, C29, C35
4100ΩResistor_SMD:R_0603_1608Metric_Pad0.98x0.95mm_HandSolderR8, R9, R10, R11
42.2nFCapacitor_SMD:C_0603_1608Metric_Pad1.08x0.95mm_HandSolderC11, C12, C37, C38
31µFCapacitor_SMD:C_0603_1608Metric_Pad1.08x0.95mm_HandSolderC25, C27, C42
3220nFCapacitor_SMD:C_0603_1608Metric_Pad1.08x0.95mm_HandSolderC13, C14, C15
34.7µFCapacitor_SMD:C_1210_3225Metric_Pad1.33x2.70mm_HandSolderC9, C10, C18
3470µFCapacitor_THT:C_Radial_D12.5mm_H20.0mm_P5.00mmC39, C40, C41
2100nFCapacitor_SMD:C_0805_2012Metric_Pad1.18x1.45mm_HandSolderC8, C17
215pFCapacitor_SMD:C_0603_1608Metric_Pad1.08x0.95mm_HandSolderC32, C33
22.2μFCapacitor_SMD:C_0805_2012Metric_Pad1.18x1.45mm_HandSolderC3, C4
222ΩResistor_SMD:R_0603_1608Metric_Pad0.98x0.95mm_HandSolderR24, R25
25.1kΩResistor_SMD:R_0603_1608Metric_Pad0.98x0.95mm_HandSolderR22, R23
256ΩResistor_SMD:R_0603_1608Metric_Pad0.98x0.95mm_HandSolderR6, R7
2R_ShuntResistor_SMD:R_Shunt_Vishay_WSK2512_6332Metric_T2.66mmR16, R17
1+VConnector_Wire:SolderWire-4sqmm_1x01_D3mm_OD6mmJ6
1100kΩResistor_SMD:R_0805_2012Metric_Pad1.20x1.40mm_HandSolderR13
110kΩ Thermistor_NTCResistor_SMD:R_0603_1608Metric_Pad0.98x0.95mm_HandSolderTH1
110nFCapacitor_SMD:C_0603_1608Metric_Pad1.08x0.95mm_HandSolderC26
110µFCapacitor_SMD:C_1210_3225Metric_Pad1.33x2.70mm_HandSolderC24
1120pFCapacitor_SMD:C_0603_1608Metric_Pad1.08x0.95mm_HandSolderC2
1120ΩResistor_SMD:R_0603_1608Metric_Pad0.98x0.95mm_HandSolderR18
115nFCapacitor_SMD:C_0603_1608Metric_Pad1.08x0.95mm_HandSolderC19
116.2kΩResistor_SMD:R_0603_1608Metric_Pad0.98x0.95mm_HandSolderR2
12.2kΩResistor_SMD:R_0603_1608Metric_Pad0.98x0.95mm_HandSolderR21
1205kΩResistor_SMD:R_0603_1608Metric_Pad0.98x0.95mm_HandSolderR1
122nFCapacitor_SMD:C_0805_2012Metric_Pad1.18x1.45mm_HandSolderC5
122µHInductor_SMD:L_6.3x6.3_H3L1
139kΩResistor_SMD:R_0805_2012Metric_Pad1.20x1.40mm_HandSolderR20
152.3kΩResistor_SMD:R_0603_1608Metric_Pad0.98x0.95mm_HandSolderR3
16.8nFCapacitor_SMD:C_0603_1608Metric_Pad1.08x0.95mm_HandSolderC1
1AConnector_Wire:SolderWire-4sqmm_1x01_D3mm_OD6mmJ8
1BConnector_Wire:SolderWire-4sqmm_1x01_D3mm_OD6mmJ9
1CConnector_Wire:SolderWire-4sqmm_1x01_D3mm_OD6mmJ10
1CAN_01x04FOC_foot_lib:JST-GH_4pin_CONN_SM04B-GHS-TB_JSTJ4
1Crystal_GND24Crystal:Crystal_SMD_3225-4Pin_3.2x2.5mm_HandSolderingY1
1DRV8301DCARFOC_foot_lib:DRV8301_DCA56_6P35X3P61U2
1D_SchottkyDiode_SMD:D_SMA_HandsolderingD1
1Enc_MCU_01x06FOC_foot_lib:JST-GH_6pin_CONN_SM06B-GHS-TB_JSTJ2
1FerriteBeadInductor_SMD:L_0603_1608Metric_Pad1.05x0.95mm_HandSolderFB1
1GNDConnector_Wire:SolderWire-4sqmm_1x01_D3mm_OD6mmJ7
1HYCW498-USBC16-735BFOC_foot_lib:USB-C-SMD_HYCW498-USBC16-735BUSB1
1ME6211FOC_foot_lib:ME6211A33PG-N_SOT89-3U11
1SMCJ43AFOC_foot_lib:TVS_Diode_SMCJSeries_LTFCR1
1ST-Link_01x05Connector_PinHeader_2.54mm:PinHeader_1x05_P2.54mm_HorizontalJ1
1STM32F405RGT6FOC_foot_lib:STM32F405_LQFP64-10x10mmU1
1TJA1051T/3/1JFOC_foot_lib:TJA1051_SO8_SOT96-1_NXPU10
1TS-1002S-05026CFOC_foot_lib:Button_KEY-SMD_4P-L6.0-W6.0-P4.50-LS9.0SW1

More from arthur-wirjo/FOC_v1_project

1
  • 2 layers40 × 40 mmEncoder Module PCB, the printed circuit board in 3D

    Encoder Module PCB

    arthur-wirjo/FOC_v1_project

    A custom-designed, 60V 50A Field Oriented Control (FOC) BLDC motor controller built from scratch. Designed for high-performance robotics, featuring a 4-layer power PCB, isolated USB telemetry, and CAN bus communication.

    8 partsMIT

Similar boards

  • 4 layers60 × 70 mmControl board PCB, the printed circuit board in 3D

    Control board PCB

    arthur-wirjo/reaction-wheel-inverted-pendulum

    A custom-engineered Reaction Wheel Inverted Pendulum designed as a physical testbed for advanced modern control theory.

    77 partsMIT
  • 8 layers26 × 26 mmAntisparkBoard V1, the printed circuit board in 3D

    AntisparkBoard V1

    BradleyCanty/Parametric-21700-Battery-System-V1

    A do-it-yourself 21700 battery system for use in UAVs or UGVs

    21 partsMIT
  • 4 layers85 × 70 mmKICAD HT, the printed circuit board in 3D

    KICAD HT

    Nicolboy/KICAD-C2000-float-flyback

    Alimentation flyback isolée et flottante 200kHz (11-25V→5,5-13V/3A) pour chauffage filament tube + préampli bas bruit — KiCad 10.

    168 partsCERN-OHL-S-2.0
  • 4 layers72 × 51.1 mmEsp32s3-audio streamer, the printed circuit board in 3D

    Esp32s3-audio streamer

    wemaxon/esp32-audio-streamer

    Hardware design for a WiFi/Bluetooth audio streamer using the esp32 microcontroller and the PCM5102A DAC, intended to be used with squeezelite firmware.

    63 parts
  • 4 layers80 × 105.5 mmNetdaq, the printed circuit board in 3D

    Netdaq

    Gherkin/netdaq

    913 partsCERN-OHL-P-2.0
  • 2 layers80.5 × 45.1 mmRa5 2022, the printed circuit board in 3D

    Ra5 2022

    pedrohqr/ra5_2022_m

    Base/carrier board for a modular PLC (Programmable Logic Controller): an I/O front-end with no main MCU of its own — sensing and metering peripherals are driven by a separate MCU+LTE modem card that plugs into the…

    154 parts
  • 2 layers59.1 × 99.9 mmCheap FOCer 2 60mm, the printed circuit board in 3D

    Cheap FOCer 2 60mm

    shamansystems/Cheap-FOCer-2

    Low-Cost Motor Controller based on the VESC 6

    193 parts407
  • 4 layers75.2 × 99.5 mmFOC, the printed circuit board in 3D

    FOC

    nordstream3/FOC

    Date | Manufacturer | amount | includes | shipping & tax | price | -------- | -------- | -------- | -------- | -------- | -------- | 2024-01-17 | JLCPCB | 10 boards | All assembled excl fets and caps | YES, to EU |…

    261 parts81

Questions

How big is the FOC V1 PCB PCB?

It measures 72.6 × 72.6 mm and has 4 copper layers, 1.6 mm thick.

What parts does the FOC V1 PCB use?

95 parts, built around the STM32F405RGT6, TJA1051T/3/1J, DRV8301DCAR and IRFS7530TRL7PP. 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.

Where can I download the FOC V1 PCB KiCad files?

From the arthur-wirjo/FOC_v1_project repository on GitHub, at the commit this page was made from: the board is FOC_V1_PCB/FOC_V1_PCB.kicad_pcb and its schematic Encoder_Module_PCB/Encoder_Module_PCB.kicad_sch. PCBKit opens the board in the browser, with nothing to install.

Can I use the FOC V1 PCB design in my own project?

Its repository publishes it under the MIT licence: you may reuse it on that licence's terms (keep the author's notice, and for a copyleft licence share your changes alike).