-
Notifications
You must be signed in to change notification settings - Fork 13.2k
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
[Bug] Parameters not found in custom module #23162
Comments
Update on this: I figured it out! I had used a formatter on my parameters source file (i.e. This works:
This does not work:
Technically the problem is now solved, however this seems like something that will come up as an issue again in the future, so feel free to leave this issue open, or close it and make a new one, or whatever else. Thanks! |
Describe the bug
I've been doing semi-regular syncs between the main PX4 repo branch and a custom fork that I've been using to implement a gimbal as a senior project.
Unfortunately it seems that the most recent sync has (somehow?) broken my module's parameters! Once everything is compiled and flashed, the UART output of the ARK CANnode I'm using give a wall of
ERROR [param] Parameter <whatever> not found.
for all of my module's params.I've had similar issues in the past (that is, errors related to a repo sync), and I can normally just sort through the commits to see what might've caused the issue, but I haven't been able to find anything thus far, and I'm making very little progress towards a solution compared to past issues as well.
To Reproduce
Clone my PX4 fork (LINK) and compile it for the ARK CANnode, flash it however you choose, and watch the debug UART output on boot
Expected behavior
I expect all parameters to be found
Screenshot / Media
No response
Flight Log
N/A
Software Version
Flight controller
ARK CANnode
Vehicle type
Other
How are the different components wired up (including port information)
The CANnode is currently not connected to anything except 5V and a debug breakout board
Additional context
No response
The text was updated successfully, but these errors were encountered: