forked from PX4/PX4-Autopilot
-
Notifications
You must be signed in to change notification settings - Fork 2
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
parameters LPWORK -> wq:lp_default #27
Draft
dagar
wants to merge
419
commits into
master
Choose a base branch
from
pr-parameters_wq
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Draft
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
The previous check for the -j argument was not actually working. Therefore, the build always used 4 cores, unless when building with ninja when presumably the ninja default was used.
Without this ninja supposedely builds with the default of the system which is 10 for my 4 core, 8 thread CPU. With this argument, you can now actually set it. This has the benefit that the Gazebo plugins can be built with less cores in order to avoid running out of RAM.
It makes sense to trust ninja on selecting the number of cores. This is also sensible in order not to change existing setups.
Todate I have not fould a way to differentiate a 74 from a 75. as all parts map to Device ID 0x450: STM32H742, STM32H743/753 and STM32H750. One the CPU is fully differentiate in Nuttx, this can be a #ifdef.
The defualt in NuttX is OSPEED of 50Mhz. This is realy a slew rate control. At the default high slew rate the overshoot was .7 Volts. On a ICM20649 this was causing the device to output garbage. All 0s N.B. A passive scope or Logic analyser's probes load will mask the failure. Useed a FET probe to verify the issue.
We can omit param1 because it is already used for the message_id, so it's basically duplicate information and won't get used anywhere.
Default is -2, so the comments seems wrong.
This allows to send a message exactly once if requested.
That makes gazebo crash in VMWare 3D graphics accelration.
- ecl in PX4/Firmware (bd4d3f2): PX4/PX4-ECL@e4b44f7 - ecl current upstream: PX4/PX4-ECL@5356077 - Changes: PX4/PX4-ECL@e4b44f7...5356077 5356077 2020-06-21 kamilritz - Make flow_innov/-var a matrix Vector2f c2801eb 2020-06-21 kamilritz - Add const modifier and increase matrix library usage d9afc2f 2020-06-21 kamilritz - Remove repeated division by same value d16b43a 2020-06-21 kamilritz - Get rid of non functional piece of code c3653e6 2020-06-21 kamilritz - Add const modifier 48f0eb1 2020-06-21 kamilritz - Remove uninformative comments 4a69b41 2020-06-21 kamilritz - Increase matrix library usage even more 630be60 2020-06-21 kamilritz - Increase matrix library usage 22274b1 2020-06-21 kamilritz - Add const modifier 61c139e 2020-06-21 kamilritz - Remove unused variable afd4f3f 2020-06-21 kamilritz - Fix typo a3706fd 2020-06-21 kamilritz - Make relative wind computation more compact b8f9376 2020-06-21 kamilritz - Make mag_innov/-var a Matrix::Vector3f 0ea7cd8 2020-06-25 Kamil Ritz - Attempt to fix CI firmware build test 2927132 2020-06-25 Daniel Agar - clang-format set BreakBeforeBraces to Linux style b96c62e 2020-06-25 sevenbill - Optionalized build dependency on git 794e6ec 2020-06-25 Bill Morris - Enforce tabs via editorcofig
- matrix in PX4/Firmware (a1043f6): PX4/PX4-Matrix@f529358 - matrix current upstream: PX4/PX4-Matrix@9a30828 - Changes: PX4/PX4-Matrix@f529358...9a30828 9a30828 2020-06-30 Julian Kent - Add explicit matrix + scalar test f3cf615 2020-06-30 Julian Kent - Do += -= and scalar *= /= in place
- mavlink v2.0 in PX4/Firmware (2be1588): mavlink/c_library_v2@413964f - mavlink v2.0 current upstream: mavlink/c_library_v2@bd80020 - Changes: mavlink/c_library_v2@413964f...bd80020 bd80020a 2020-06-29 PX4BuildBot - autogenerated headers for rev https://github.com/mavlink/mavlink/tree/527abe53c4c9bf6fe811d5f8b236d6ecc73ded67 Co-authored-by: PX4 BuildBot <[email protected]>
…X4#15248) - sitl_gazebo in PX4/Firmware (38588f0): PX4/PX4-SITL_gazebo-classic@309f7b0 - sitl_gazebo current upstream: PX4/PX4-SITL_gazebo-classic@1af7e29 - Changes: PX4/PX4-SITL_gazebo-classic@309f7b0...1af7e29 1af7e29 2020-06-25 JaeyoungLim - Do not validate r1_rover 5e8ddfb 2020-06-25 Benjamin Perseghetti - fixes for R1 SDF PX4/PX4-SITL_gazebo-classic#533 (PX4#534) 726c066 2020-06-23 Supakorn Suttiruang - Remove the incorrect force generated by moment (PX4#532) Co-authored-by: PX4 BuildBot <[email protected]>
Signed-off-by: Claudio Micheli <[email protected]>
- Introduced COM_LKDOWN_TKO parameter - Introduced auto disarm for lockdown state - Do not trigger flight termiantion if system is in lockdown Signed-off-by: Claudio Micheli <[email protected]>
Signed-off-by: Claudio Micheli <[email protected]>
* VT_F_TR_OL_TM would silently reduce VT_TRANS_MIN_TM when VT_F_TR_OL_TM was smaller
and reorder baro startup, so that the other one is used by default.
This is an attempt to get jMAVSim to run with Java9+.
Note: only tested on I2C
- enabling stack check increases stack usage and will assert if there's any overflow
we have a setup where the sensor is connected via magnets, so the system could boot without sensor initially attached.
to avoid blocking the work queue during configuring.
dagar
pushed a commit
that referenced
this pull request
Feb 14, 2024
- gz in PX4/Firmware (c9ad60e): PX4/PX4-gazebo-models@c78f7f0 - gz current upstream: PX4/PX4-gazebo-models@f1c461f - Changes: PX4/PX4-gazebo-models@c78f7f0...f1c461f f1c461f 2024-02-08 frederik - increase monocam clipping distance 6d5db73 2024-02-07 Sergei Grichine - Added Zero Turn Lawnmower model (#27) 5332071 2024-02-06 Frederik Markus - add navsat plugin to worlds and navsat sensor to models (#26)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.