merging 4.0 from upstream #1
Open
Conversation
This file contains hidden or 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
this gates the "ADSB" avoidance feature used for macro-level avoidance. It's not actually limited to ADSB as input...
this gates the "ADSB" avoidance feature used for macro-level avoidance. It's not actually limited to ADSB as input...
this gates the "ADSB" avoidance feature used for macro-level avoidance. It's not actually limited to ADSB as input...
this gates the "ADSB" avoidance feature used for macro-level avoidance. It's not actually limited to ADSB as input...
this gates the "ADSB" avoidance feature used for macro-level avoidance. It's not actually limited to ADSB as input...
this gates the "ADSB" avoidance feature used for macro-level avoidance. It's not actually limited to ADSB as input...
This GitHub Action fails occasionally, so let's upgrade its flake8 to see if that provides more stable runs. https://pypi.org/project/flake8 --> v7.2.0 flake8: Both the local issue and the flake8 issue it points to were closed 4 or 5 years ago, so let's test with current flake8.
The current implementation of pitch stick mixing is unsafe, as it introduces an attitude override that is decoupled from the TECS, and also lacks any stall and overspeed prevention mechanisms. This means that if a pitch nudge is held long enough, an overspeed or a stall will occur. This commit introduces a "FBW style (no pitch)" setting to the STICK_MIXING parameter. It behaves like the current "FBWMixing" option for roll and yaw, but doesn't provide any pitch mixing. A warning about the lack of flight envelope protections in "FWB style" mode has also been added to the description.
this doesn't actually really fix a bug at the moment as ADSB is required for AVOID_ADSB. But it is currently wrong
Setting the rate to 0 is counterproductive and causes large yaw outputs
just whitespace changes
This was a holdover from before I had the SkipChecks class, and I would pass None to enable all checks.
This prevents us from putting a value in defaults.parm for a read-only parameter. A #define value feels more appropriate for read-only params.
RC_FEEL_RP was changed to ATC_INPUT_TC. The functionality is the same, but the scaling has changed. PSC_ACCZ_FILT was renamed to PSC_ACCZ_FLTE. PILOT_VELZ_MAX was wrong to begin with (#define/param name confusion). The old WPNAV_LOIT params were moved ages ago. Only two of these have a true one-to-one mapping to new params. The others I have deleted. BRD_PWM_COUNT isn't necessary anymore. The appropriate servo pins are marked as -1 to make them GPIO already. I could have changed FLOW_ENABLE to FLOW_TYPE, but that would override the default type set in the hwdef. The 0 FLOW_ENABLE is currently doing nothing so I opted to keep it that way and just delete the line.
The profile parameters seem to have been part of SkyRocketToys' fork and never made it into upstream. I think the same is true for the FLIP parameters and some of the other TMODE parameters. SYSID_SW_TYPE does nothing anymore, and I'm not sure why it was ever set to 100 in the first place. Must have been some fork-specific thing that we don't care about.
Only the last value is used. I took the value from whatever appeared last, but shuffled the order to keep things together where possible. There is one exception, I set BRD_RADIO_TYPE to autodetect, which is the earlier appearance, as that seems like that was the intent originally, and that the later value was a mistake.
useful for working out how close a vehicle was to failsafing
useful for working out how close a vehicle was to failsafing
commit f64add0 Author: ThenYang <engineer@dakefpv.com> Date: Thu Jul 10 17:13:57 2025 +0800 lower the resolution of the images so that they are not so large commit 2352cd5 Author: ThenYang <engineer@dakefpv.com> Date: Thu Jul 10 14:29:59 2025 +0800 The DAKEFPVH743 is based on the DAKEFPVH743Pro. commit f51ac2d Author: 玄绮 <shijiahansi@qq.com> Date: Thu Jul 10 14:29:59 2025 +0800 Update DAKEFPVH743PRO commit be7b6fb Author: 玄绮 <engineer@dakefpv.com> Date: Thu Jul 10 14:29:59 2025 +0800 update: hwdef.dat: 1.UART5 use DMA for RCIN. 2.USART2,3 NODMA. 3.USART6,7 use DMA. defaults.parm: 1.setup for LEDs on chan14. WiringDiagramTop.png: 1.updated the correct wiring diagram. commit f249d5e Author: 玄绮 <engineer@dakefpv.com> Date: Thu Jul 10 14:29:58 2025 +0800 BATT_VOLT_MULT default 16.0 commit e24d940 Author: 玄绮 <engineer@dakefpv.com> Date: Thu Jul 10 14:29:58 2025 +0800 Add New Target DAKEFPVH743
this will stop a regular segv on the autotest server: [Wed Dec 29 14:29:08 2021] INS_generic[13156]: segfault at 211 ip 000055e6544bbda8 sp 00007ffee7339970 error 4 in INS_generic[55e65449e000+7f000]
this is the default
… terminating null
this allows for multiple PPP interfaces, so we can have a PPP<->ethernet bridge and an LTE modem (or other PPP device) at the same time
allows custom network routes
this reduces CPU usage in the hot frame accept path using hash on the message ID into a set of message lists
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.
Migration to ChibiOS and a host of other features/bug fixes from 4.0 release.