FOC Driver Board Archive Notes慧驱动 FOC 驱动板开发归档笔记

Starting Point起点

FOC 这条线一看就很适合放作品集：STM32F4、DRV8301、PMSM、无感控制、FOC 算法、电流采样、速度环、OLED、上位机通信。也正因为关键词漂亮，写的时候更要小心。真正能说明水平的是电机怎样起转、采样怎样进控制链路、DRV8301 fault 怎么处理、PWM 和电流波形有没有留下记录。

The FOC line looks strong on a portfolio page: STM32F4, DRV8301, PMSM, sensorless control, FOC algorithm, current sampling, speed loop, OLED, and host communication. The useful writing has to stay close to startup, sampling path, DRV8301 fault handling, PWM, and current waveform evidence.

源目录确实很厚。能看到 PCB、BOM、PickAndPlace、InteractiveBOM、STEP、EasyEDA 工程、DRV8301 和 STM32F4 资料、IAR / Keil 工程、motor 目录下的 adc、drv8301、foc_algorithm、hall_sensor、speed_pid 等模块。只列这些文件还不够，还要把启动、采样、保护、失败和测试写出来。

The folder is substantial: PCB, BOM, PickAndPlace, InteractiveBOM, STEP, EasyEDA project, DRV8301 and STM32F4 references, IAR / Keil projects, and motor modules such as adc, drv8301, foc_algorithm, hall_sensor, and speed_pid. The next layer is explaining startup, sampling, protection, failure cases, and tests.

Reading It As Clues先按线索读

Gerber and STEP look solid, and they are useful. They show that the board exists and can be inspected. They still leave the harder questions open: startup logic, sampling path, PWM modulation, protection conditions, and tuning process.

The missing records are clear:

• current-sampling path and ADC trigger timing;
• a simplified signal-flow diagram for Clarke / Park / PI / SVPWM;
• DRV8301 fault handling and register-configuration reasoning;
• waveforms or logs for failed and successful startup;
• division of work among speed loop, low-speed task, and parameter identification.

Gerber 和 STEP 看起来很硬，也确实有用。它们说明这块板存在，也能被检查。但更难的问题还在后面：启动逻辑、采样链路、PWM 调制、保护条件和调参过程。

后面要补的记录很明确：

• 电流采样路径和 ADC 触发时序；
• Clarke / Park / PI / SVPWM 的简化信号流；
• DRV8301 fault 处理和寄存器配置思路；
• 起转失败和成功的波形或日志；
• 速度环、低速任务、参数辨识之间怎么分工。

Current State现在的状态

Right now this is a development line with many materials and several unanswered runtime questions. A fuller FOC case should answer when the motor starts reliably, whether the current waveform is reasonable, how faults are triggered, how sampling noise is handled, how parameters are tuned, and what happens at low speed or high load.

现在它更像一条材料很多、运行问题还没有讲透的开发线。更完整的 FOC 案例应该能回答：电机什么时候能稳定起转，电流波形是否合理，fault 怎么触发，采样噪声怎么处理，参数怎么调，低速和高负载时会发生什么。

Files文件

The site currently provides these files for reading the board and selected firmware pieces:

站点现在提供这些文件，用来读板卡和选出的固件片段：

• EasyEDA project
• Gerber archive
• BOM table
• Pick-and-place table
• Interactive BOM
• PCB 3D STEP model
• Board configuration source
• Motor ADC source
• DRV8301 driver source
• FOC algorithm source
• Speed PID source
• DRV8301 datasheet

IAR / Keil 工程、完整 STM32F4 源码树、vendor library、Debug / Release 构建产物和重复工具输出暂时留在原始归档里。完整工程树太重，也替代不了对起转、采样、调制、保护和测试的解释。

Records Still Missing还要补的记录

• Keep it as a material trail for now.
• Add one desensitized FOC signal-chain diagram.
• Find or redo minimal test records: PWM, phase current, speed response, and fault logs.
• Continue adding short snippets, redrawn diagrams, and test records later.

• 暂时把它当材料线索。
• 补一张脱敏 FOC 信号链图。
• 找到或重做最小测试记录：PWM、相电流、速度响应、fault 日志。
• 后续继续补短片段、重画图和测试记录。

Looking Back Now现在回头看

The more advanced a topic sounds, the more it needs plain evidence. If the FOC line is made solid later, the focus should be startup, sampling, modulation, protection, and testing, with waveforms or logs close by.

越“高级”的题目越要靠朴素证据。FOC 这条线以后如果要写扎实，重点应该是起转、采样、调制、保护和测试，而且最好有波形或日志跟在旁边。现在先留材料和问题，别把还没调透的东西写成结论。