Skip to content
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

Pix flaming f767 to copter 4.4 #26352

Conversation

tsubashchandar
Copy link
Contributor

No description provided.

peterbarker and others added 30 commits November 20, 2023 19:25
Two structs with the same name must have exactly the same definition, no
matter where they occur in the program, otherwise the program is undefined.

Move each sample register struct definition into the associated class
definition so they are in a different namespace and no longer
identically named, thus fixing this issue.
narrower define we can use when not compiling in the backends which use this
…NABLED

narrower define we can use when not compiling in the backends which use this
calculate D feed-forward and notch applications correctly
only update notches when enabled
add notches and D feedforward to heli PIDs
add advanced flag an selectively compile advanced options
add advanced flag to PIDs and selectively compile advanced PID options
update PID notch centers at 1Hz with average loop rate
update PID notch centers at 1Hz with average loop rate
IamPete1 and others added 24 commits December 5, 2023 11:03
* Implement filter state without relying on GPS
* Implement health and initialization check based on filter state
* Fix pre-arm checks missing version
* Add version specifics to microstrain 5 log msgs
* Add utilities to microstrain packet to remove magic number array
  access

Signed-off-by: Ryan Friedman <[email protected]>
* The old descriptor is deprecated

Signed-off-by: Ryan Friedman <[email protected]>
this one has been really bad for a while
the first option is to disable DCM fallback on fixed wing. This is
suitable in environments with a high likelyhood of GPS interference
@tsubashchandar tsubashchandar changed the base branch from master to Copter-4.4 February 28, 2024 13:04
@IamPete1
Copy link
Member

Is this a new board? It should be PR'd against the master branch first.

@tsubashchandar
Copy link
Contributor Author

Is this a new board? It should be PR'd against the master branch first.

Yes I have created , #25714

@IamPete1
Copy link
Member

Yes I have created , #25714

Ah, OK, sorry that one had been open for so long. I will close this so we can concentrate the discussion there. Once that one is in we can think about backports. Although at this point I don't think we would port to 4.4, 4.5 is just starting beta, so we would port to 4.5.

@IamPete1 IamPete1 closed this Feb 28, 2024
@tsubashchandar
Copy link
Contributor Author

Yes I have created , #25714

Ah, OK, sorry that one had been open for so long. I will close this so we can concentrate the discussion there. Once that one is in we can think about backports. Although at this point I don't think we would port to 4.4, 4.5 is just starting beta, so we would port to 4.5.

Thanks peter

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.