R5 sets the MP1584 enable divider, and the files disagree:
| Source |
Value |
control_bom.csv, control1_bom.csv |
27k |
control_xy.csv, control1_xy.csv |
27k |
Rendered schematic (control.png) |
27k |
control.pcb, control1.pcb, control2.pcb |
72k |
With R4 = 100k and the MP1584's ~1.5 V EN threshold:
- 27k -> turn-on at
1.5 * (100+27)/27 = ~7.0 V
- 72k -> turn-on at
1.5 * (100+72)/72 = ~3.6 V
The README advertises a 5-30 V input. At 27k the board would not start at 5 V at
all, so which value is actually fitted determines whether the product does what
it says.
This needs measuring on a physical board — it can't be resolved from the
files, since four of them say one thing and three say the other.
Detected by tools/check_bom.py, and baselined in
tools/known_bom_issues.txt so CI blocks on new drift meanwhile. Delete that
entry when this is resolved.
Related: C4 is 0.01uF on the schematic (a 10 nF bootstrap cap is conventional
for the MP1584) but ordered as 100nF in both BOMs.
R5 sets the MP1584 enable divider, and the files disagree:
control_bom.csv,control1_bom.csvcontrol_xy.csv,control1_xy.csvcontrol.png)control.pcb,control1.pcb,control2.pcbWith R4 = 100k and the MP1584's ~1.5 V EN threshold:
1.5 * (100+27)/27= ~7.0 V1.5 * (100+72)/72= ~3.6 VThe README advertises a 5-30 V input. At 27k the board would not start at 5 V at
all, so which value is actually fitted determines whether the product does what
it says.
This needs measuring on a physical board — it can't be resolved from the
files, since four of them say one thing and three say the other.
Detected by
tools/check_bom.py, and baselined intools/known_bom_issues.txtso CI blocks on new drift meanwhile. Delete thatentry when this is resolved.
Related: C4 is
0.01uFon the schematic (a 10 nF bootstrap cap is conventionalfor the MP1584) but ordered as
100nFin both BOMs.