Update MCU requirements #477
Conversation
✅ Deploy Preview for origin-betaflight-com ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
haslinghuis
force-pushed
the
mcu-requirements
branch
from
677def1
to
a42a04f
Compare
haslinghuis
force-pushed
the
mcu-requirements
branch
from
4a135af
to
c8f6c1f
Compare
|
|
I agree this should be updated, and I have an opinion on what the default recommendations should be, but I hesitate to make them official without some testing/data to back them up. For example, I'm pretty sure the AT32F435 is ok at 8k, but would say never for the F411 at 8k. For F411/F405, the recommendation also depends on whether timer based DShot is being used. If the FC design requires bitbang or burst DMA to work (resulting in no gyro DMA), then a lower loop rate is almost certainly required. |
| | | BMI-270 | 3.2 kHz | Disabled (not recommended) | 3.2 kHz | DShot 300 | | ||
| | MCU | IMU | Sampling Rate | Bidirectional DShot Status | PID Loop Rate | DShot Protocol | | ||
| | :---------------------------- | :--------------------------- | :------------ | :------------------------- | :------------ | :------------- | | ||
| | H7XX | MPU60X0, ICM2060X, ICM42688P | 8 kHz | Enabled or Disabled | 8 kHz | DShot 600 | |
There was a problem hiding this comment.
while i understand this cleans up the tables, does it make searching harder? (X)
There was a problem hiding this comment.
Other rows already used - so made it consistent.
But we need to decide on other factors like @ot0tot mentioned.
No description provided.