-
Notifications
You must be signed in to change notification settings - Fork 13.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update pab_manifest.c #23477
Update pab_manifest.c #23477
Conversation
Add: {HW_BASE_ID(6), base_configuration_0, arraySize(base_configuration_0)}, // ZeroOne Base
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
With the resistors set with ID 7 means that the board's ID will be read from the EEPROM
Assuming Dronecode gives you the id 0x150... You will need to create a stanza like:
labeled base_configuration_18
You will need to add new PX4_MFT_xxx to this file for each new feature that the board needs to be controlled. Then modify any scrips that need to activate the feature.
if mft query -q -k MFT -s MFT_<new feature name> -v 1
then
your command to do new feature.
fi
and add. {HW_BASE_ID(0x150), base_configuration_18, arraySize(base_configuration_18)}, // ZeroOne Pixhawk Baseboard ver 0x150
Thanks for your answer, our base_configuration_0 can be used for our baseboard, so I just added two sentences: 1、// BASE ID 0x150 ZeroOne X6 Baseboard Alaised to ID 0 2、{HW_BASE_ID(0x150), base_configuration_0, arraySize(base_configuration_0)}, // ZeroOne Base
The value is changed to 0x110: {HW_BASE_ID(0x110), base_configuration_0, arraySize(base_configuration_0)}, // ZeroOne Pixhawk Baseboard ver 0x110
I've changed it to 0x150
@ZeroOne-Aero Please rebase on main and squash your commits into 1. |
Add:
{HW_BASE_ID(6), base_configuration_0, arraySize(base_configuration_0)}, // ZeroOne Base