| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
The command is defined in msp_protocol_v2_inav.h and answered in fc_msp.c, but the registry never listed it, so check_msp.py fails on maintenance-10.x and on every pull request that runs the MSP consistency workflow.
MSP2_INAV_ESC_SRXL2_STATUS and MSP2_INAV_ESC_SRXL2_CALIBRATE came in with iNavFlight#11947 without an entry in msp_messages.json, which is two of the three commands check_msp.py reports as missing.
|
ⓘ Qodo reviews are paused because the subscription is no longer active. Ask your workspace admin to reactivate the subscription to resume reviews. Manage billing |
Sorry, something went wrong.
Code Review by Qodo🐞 Bugs (0) 📘 Rule violations (0) 📎 Requirement gaps (0)Great, no issues found!Qodo reviewed your code and found no material issues that require review Tip of the day💡 Did you know, you can keep summaries lean with Finding overflow, which tucks the rest behind 'View more' |
Sorry, something went wrong.
PR Summary by QodoRegister missing MAG and SRXL2 MSP commands 🐞 Bug fix 📝 Documentation 🕐 10-20 Minutes AI Description
|
Sorry, something went wrong.
|
Thanks — this fixes the red MSP consistency check on maintenance-10.x, and I verified all three entries against the handlers in fc_msp.c and the enums in motor_srxl2.h. Including MSP2_INAV_MAG_UNALIGNED is fine, since the check can't pass without it. One small addition, if you don't mind: srxl2CalPhase_e and srxl2CalResult_e aren't in docs/development/msp/inav_enums.json yet, so the enum links in the new entries point to missing anchors. Could you regenerate the enum files (src/utils/get_all_inav_enums_h.py / gen_enum_md.py) as part of this PR? Then its fine to merge. Thanks! |
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
What this fixes
check_msp.py fails on maintenance-10.x, so the MSP consistency workflow goes red on every pull request that touches MSP, whatever the pull request does. Three commands are defined in msp_protocol_v2_inav.h and answered in fc_msp.c but have no entry in msp_messages.json:
What I changed
An entry for each, written from the handlers in fc_msp.c and the enums in motor_srxl2.h, with README.md regenerated by gen_msp_docs.sh. The MAG_UNALIGNED entry is a commit of its own, so it can be dropped if its author would rather write it.
The registry version goes from 2.1.1 to 2.1.2: new entries inside the current schema, which the versioning rule counts as a patch.
Testing
check_msp.py passes ("281 C definitions match 282 JSON definitions"), and gen_msp_docs.sh leaves README.md unchanged after the commit, which is what the workflow compares.
#11979 also bumps the registry version, so whichever of the two goes in second will need that line rebased.