- Built-In Blue-Tooth module for easy configuration from your mobile
- USB Type-C connector
- DJI Compatible connector
- Optional secondary MPU connection
- Barometer
- Main MPU-6000
- 5 UARTS
- Betaflight Target APEXF7
#replaces spa(mixed) | |
done: spa_roll_p | |
done: spa_roll_i | |
done: spa_roll_d | |
done: spa_pitch_p | |
done: spa_pitch_i | |
done: spa_pitch_d | |
#already there |
git_notes.txt -- assumes CLI in Linux/OSX or Cygwin or WSL (Windows SubSystem for Linux). | |
https://git-scm.com/docs/ | |
https://www.atlassian.com/git/tutorials/ | |
--- | |
################################################## | |
### Recommended Windows vs Linux Compatibility ### | |
################################################## | |
# recommended git global environment configs: | |
# windows: |
[...] | |
# Upload to Bintray | |
- name: Upload to Bintray | |
if: startsWith(github.ref, 'refs/tags/') | |
run: | | |
curl -fL https://getcli.jfrog.io | sh | |
export JFROG_CLI_OFFER_CONFIG=false | |
export CI=true | |
export JFROG_CLI_LOG_LEVEL=DEBUG |
# nerdCopter's unprofessional biased starting point | |
# for tuning a generic Helio 5", maybe 6". | |
# Recommend BBL analysis for LPF modifications. | |
# Recommend raise P's as needed and balance D's afterward. | |
# Raise I's as needed. | |
# | |
# This is not exactly a diff, but definitely not a dump. | |
# It's closer to a "preset" | |
# Start with your settings, then add these configs. | |
# |
// plugin (addon) for web browser youtube controls | |
// https://www.mrfdev.com/enhancer-for-youtube | |
function sleep(ms) { | |
console.log('Taking a break...'); | |
var date = new Date(); | |
var curDate = null; | |
do { curDate = new Date(); } | |
while(curDate-date < ms); | |
console.log(ms+'ms later'); |
### FROM DEFAULTS, then add | |
# version | |
# EmuFlight / APEXF7 (APF7) 0.4.0 Sep 12 2021 / 09:41:15 (8e3969050) MSP API: 1.51 | |
# name | |
name nerdAPEX6 | |
# mixer | |
mixer CUSTOM |
With GitHub Actions, a workflow can publish artifacts, typically logs or binaries. As of early 2020, the life time of an artifact is hard-coded to 90 days (this may change in the future). After 90 days, an artifact is automatically deleted. But, in the meantime, artifacts for a repository may accumulate and generate mega-bytes or even giga-bytes of data files.
It is unclear if there is a size limit for the total accumulated size of artifacts for a public repository. But GitHub cannot reasonably let multi-giga-bytes of artifacts data accumulate without doing anything. So, if your workflows regularly produce large artifacts (such as "nightly build" procedures for instance), it is wise to cleanup and delete older artifacts without waiting for the 90 days limit.
Using the Web page for the "Actions" of a repository, it is possible to browse old workflow runs and manually delete artifacts. But the procedure is slow and tedious. It is fine to delete one selected artifact. It is not for a regular cleanup. We need