PayloadComputerDroneProjekt
https://konstantindege.github.io/PayloadComputerDroneProjekt/
Setup
install following
https://docs.px4.io/main/en/dev_setup/dev_env_windows_wsl.html
run simulation
export PX4_HOME_LAT=48.76816699 export PX4_HOME_LON=11.33711226 export PX4_HOME_ALT=375 cd && cd PX4-Autopilot/ && HEADLESS=1 make px4_sitl gz_x500_mono_cam_down ip addr | grep eth0clone this repo and install this package inside of your wsl instance
start wsl in the folder
clone repo to folder inside wsl
python3 -m venv myenv
source myenv/bin/activate
pip install -e .
gointo myenv foldern and open the conf file and change use global packages to true
move models to simulation
clone this repo also in the same folder as the PX4-Autopilot
cd ~/PX4-ROS2-Gazebo-Drone-Simulation-Template cp -r ./PX4-Autopilot_PATCH/* ~/PX4-Autopilot/https://www.geeksforgeeks.org/using-github-with-ssh-secure-shell/
Helper
PowerToys Color Picker
LAB(L = %Lc, A = %Ca, B = %Cb)Cron Tab
echo ‘export PATH=”$HOME/PayloadComputerDroneProjekt:$PATH”’ >> ~/.bashrc
crontab -e
@reboot start_raspi_script.sh
Systemd
mkdir -p ~/.config/systemd/user
code ~/.config/systemd/user/start_droneos.service
[Unit] Description=Start Drone Computer After=multi-user.target
[Service] ExecStart=/usr/bin/bash /home/aviator/PayloadComputerDroneProjekt/start_raspi_script.sh Type=simple
[Install] WantedBy=multi-user.target
systemctl –user daemon-reload systemctl –user enable start_droneos.service systemctl –user start start_droneos.service
systemctl –user status start_droneos.service
journalctl -u start_droneos.service
Build docs
Install Sphinx and dependencies
pip install sphinx sphinx-autobuild pydata-sphinx-themesphinx-autobuild docs_src docs
Metadata
Release files for PayloadComputerDroneProjekt 1.0.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| payloadcomputerdroneprojekt-1.0.0.tar.gz | 11.1 MB | Without provenance | Details for payloadcomputerdroneprojekt-1.0.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| payloadcomputerdroneprojekt-1.0.0-py3-none-any.whl | Python 3 | none | any | Details for payloadcomputerdroneprojekt-1.0.0-py3-none-any.whl |
Total release size: 17.4 MB
Release files / payloadcomputerdroneprojekt-1.0.0.tar.gz
| Download URL | payloadcomputerdroneprojekt-1.0.0.tar.gz |
|---|---|
| Size | 11.1 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
1081f809f2eae6c61c9959dddc87769fa0610b1c319e24e0300498d59a33f90f
|
|
BLAKE2b-256 checksum How to use checksums |
c1dff8a085fe9321d73ce1ae826a0d650d28c38e2c1f7eb2c6b4862ec7c8101c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.10.12
|
Release files / payloadcomputerdroneprojekt-1.0.0-py3-none-any.whl
| Download URL | payloadcomputerdroneprojekt-1.0.0-py3-none-any.whl |
|---|---|
| Size | 6.3 MB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
cd9744f4292f3c87ef780f9afd6f7ae94328065d07fffebc6180cc10cc53ea7b
|
|
BLAKE2b-256 checksum How to use checksums |
bc73864841d7bfb33e7f9fe4d562313981f6bcb0993b61f52ea22142d43760f2
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.10.12
|
Security for PayloadComputerDroneProjekt 1.0.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.