which delfly files are you using as a base ? delfly_nimble ?
Hi there, has anyone faced the problem of having zero values for their AHRS?
I am using a LisaMXS (LisaMX V2.1) with MPU6000 as my IMU and no magnetometer and no GPS. There is definitely telemetry as the battery values are updating. But my AHRS keeps reading zero (Including raw IMU sensor values are zero)
ax, ay, az, gp, gq, gr = 0
I am using the quadthopter file
I am using a LisaMXS (LisaMX V2.1) with MPU6000 as my IMU and no magnetometer and no GPS. There is definitely telemetry as the battery values are updating. But my AHRS keeps reading zero (Including raw IMU sensor values are zero)
ax, ay, az, gp, gq, gr = 0
I am using the quadthopter file
Hello everybody, I am trying to configure the new U-Blox M8P receiver of my Parrot Disco as RTK-GPS. For this is I am trying to create a TCP connection from U-center to my Disco. My steps until now involve creating a TCP tunnel from the drone`s side with "nc 192.168.42.3 12345 </dev/ttyPA1 >/dev/ttyPA1". I can listen to this connection successfully on my laptop using "nc -l 12345", however, I have trouble forwarding this connection to either a Wine serial port or establishing a TCP connection with U-center directly. Did anybody have a similar problem already or knows another way to configure the GPS directly?
Their is this module http://docs.paparazziuav.org/latest/module__gps_ubx_ucenter.html which can be used to configure dynamically the gps. I don't think their is anything special for RTK mode, but maybe this can be added if you don't succeed to make a direct connection to the GPS.
@hughhugh Hi. Unfortunately, our supplier of Apogee and Chimera (Drotek) have stopped producing them, so you might try to see with https://1bitsquared.de/ if they have some boards still available.
We are currently finishing the design of a new board http://wiki.paparazziuav.org/wiki/Tawaki/v1.00 but we don't have an official provider yet.
You can also use Parrot drones like the Bebop2 (http://wiki.paparazziuav.org/wiki/Bebop) to run the Paparazzi software with hardware modifications.
We are currently finishing the design of a new board http://wiki.paparazziuav.org/wiki/Tawaki/v1.00 but we don't have an official provider yet.
You can also use Parrot drones like the Bebop2 (http://wiki.paparazziuav.org/wiki/Bebop) to run the Paparazzi software with hardware modifications.
Does Pixhawk 2.4.8 support ppz？
@fvantienen
@hughhugh Pixhawk 2.4 seems supported, not sure how good it is working: https://github.com/paparazzi/paparazzi/blob/master/conf/boards/px4fmu_2.4.makefile
Hello, anyone recently tried to setup paparazzi 5.14 using Ubuntu 16.04 LTS (Windows emulator)? when I run the (long) "Quickstart for Ubuntu users" online command, it doesn't run the GUI app at the end (see traces) . I have the universe component enabled. When I run make, it runs but the ./paparazzi leads to a Gtk.error exception (nml_gtk_init failed). Could you please help me? @LAPTOP-SU18TUN9:~$ sudo add-apt-repository -y ppa:paparazzi-uav/ppa && sudo add-apt-repository -y ppa:team-gcc-arm-embedded/ppa && sudo apt-get update && sudo apt-get -f -y install paparazzi-dev paparazzi-jsbsim gcc-arm-embedded && cd ~ && git clone --origin upstream https://github.com/paparazzi/paparazzi.git && cd ~/paparazzi && git remote update -p && git checkout -b v5.14 upstream/v5.14 && sudo cp conf/system/udev/rules/*.rules /etc/udev/rules.d/ && sudo udevadm control --reload-rules && make && ./paparazzi
gpg: keyring
gpg: requesting key 02599182 from hkp server keyserver.ubuntu.com
gpg: /tmp/tmpx8fk6h6h/trustdb.gpg: trustdb created
gpg: key 02599182: public key "Launchpad PPA for Paparazzi UAV autopilot team" imported
gpg: Total number processed: 1
gpg: imported: 1 (RSA: 1)
OK
gpg: keyring
gpg: requesting key F64D33B0 from hkp server keyserver.ubuntu.com
gpg: /tmp/tmp2zbb1psm/trustdb.gpg: trustdb created
gpg: key F64D33B0: public key "Launchpad PPA for GCC ARM Embedded Maintainers" imported
gpg: no ultimately trusted keys found
gpg: Total number processed: 1
gpg: imported: 1 (RSA: 1)
OK
Get:1 http://security.ubuntu.com/ubuntu xenial-security InRelease [109 kB]
Hit:2 http://archive.ubuntu.com/ubuntu xenial InRelease
Get:3 http://archive.ubuntu.com/ubuntu xenial-updates InRelease [109 kB]
Hit:4 http://ppa.launchpad.net/paparazzi-uav/ppa/ubuntu xenial InRelease
Hit:5 http://ppa.launchpad.net/team-gcc-arm-embedded/ppa/ubuntu xenial InRelease
Get:6 http://archive.ubuntu.com/ubuntu xenial-backports InRelease [107 kB]
Fetched 325 kB in 4s (76.9 kB/s)
Reading package lists... Done
Reading package lists... Done
Building dependency tree
Reading state information... Done
paparazzi-dev is already the newest version (3.24).
paparazzi-jsbsim is already the newest version (1.5-4).
gcc-arm-embedded is already the newest version (7-2018q2-1~xenial1).
0 upgraded, 0 newly installed, 0 to remove and 54 not upgraded.
Cloning into 'paparazzi'...
remote: Enumerating objects: 2, done.
remote: Counting objects: 100% (2/2), done.
remote: Compressing objects: 100% (2/2), done.
remote: Total 170069 (delta 0), reused 2 (delta 0), pack-reused 170067
Receiving objects: 100% (170069/170069), 73.97 MiB | 3.15 MiB/s, done.
Resolving deltas: 100% (135455/135455), done.
Checking connectivity... done.
Checking out files: 100% (4551/4551), done.
Fetching upstream
Branch v5.14 set up to track remote branch v5.14 from upstream.
Switched to a new branch 'v5.14'
gpg: keyring
/tmp/tmpx8fk6h6h/secring.gpg' created
gpg: keyring/tmp/tmpx8fk6h6h/pubring.gpg' createdgpg: requesting key 02599182 from hkp server keyserver.ubuntu.com
gpg: /tmp/tmpx8fk6h6h/trustdb.gpg: trustdb created
gpg: key 02599182: public key "Launchpad PPA for Paparazzi UAV autopilot team" imported
gpg: Total number processed: 1
gpg: imported: 1 (RSA: 1)
OK
gpg: keyring
/tmp/tmp2zbb1psm/secring.gpg' created
gpg: keyring/tmp/tmp2zbb1psm/pubring.gpg' createdgpg: requesting key F64D33B0 from hkp server keyserver.ubuntu.com
gpg: /tmp/tmp2zbb1psm/trustdb.gpg: trustdb created
gpg: key F64D33B0: public key "Launchpad PPA for GCC ARM Embedded Maintainers" imported
gpg: no ultimately trusted keys found
gpg: Total number processed: 1
gpg: imported: 1 (RSA: 1)
OK
Get:1 http://security.ubuntu.com/ubuntu xenial-security InRelease [109 kB]
Hit:2 http://archive.ubuntu.com/ubuntu xenial InRelease
Get:3 http://archive.ubuntu.com/ubuntu xenial-updates InRelease [109 kB]
Hit:4 http://ppa.launchpad.net/paparazzi-uav/ppa/ubuntu xenial InRelease
Hit:5 http://ppa.launchpad.net/team-gcc-arm-embedded/ppa/ubuntu xenial InRelease
Get:6 http://archive.ubuntu.com/ubuntu xenial-backports InRelease [107 kB]
Fetched 325 kB in 4s (76.9 kB/s)
Reading package lists... Done
Reading package lists... Done
Building dependency tree
Reading state information... Done
paparazzi-dev is already the newest version (3.24).
paparazzi-jsbsim is already the newest version (1.5-4).
gcc-arm-embedded is already the newest version (7-2018q2-1~xenial1).
0 upgraded, 0 newly installed, 0 to remove and 54 not upgraded.
Cloning into 'paparazzi'...
remote: Enumerating objects: 2, done.
remote: Counting objects: 100% (2/2), done.
remote: Compressing objects: 100% (2/2), done.
remote: Total 170069 (delta 0), reused 2 (delta 0), pack-reused 170067
Receiving objects: 100% (170069/170069), 73.97 MiB | 3.15 MiB/s, done.
Resolving deltas: 100% (135455/135455), done.
Checking connectivity... done.
Checking out files: 100% (4551/4551), done.
Fetching upstream
Branch v5.14 set up to track remote branch v5.14 from upstream.
Switched to a new branch 'v5.14'
I wouldn't be supposed to run make, I know.
@kenstobb what do you mean by quadinplane ? Transitioning vehicles ?
@kenstobb In this airframe, their is a 3-way switch apparently to go from pure rotorcraft, rotorcraft+forward motor, forward motor only. I don't see anything special in the rest of the code specific to transition. It seems to be a customized aircraft that doesn't need to tilt to switch to go to forward mode. The airframes that are flying with controlled transition are using very specific code that is not merge into master at the moment.
The way to handle transition highly depends on your configuration (no-tilt, tilt wing, tilt body,...)
The way to handle transition highly depends on your configuration (no-tilt, tilt wing, tilt body,...)
@nilay994 you can eventually use this tool to download/upload files to the bebop: https://github.com/paparazzi/paparazzi/blob/master/sw/tools/parrot/bebop.py
@latebecomer the code of the drivers for peripherals are located here: https://github.com/paparazzi/paparazzi/tree/master/sw/airborne/peripherals
What kind of autopilot board are you using ?
What kind of autopilot board are you using ?
@latebecomer here is a working example of airframe file for bebop2: https://github.com/paparazzi/paparazzi/blob/master/conf/airframes/examples/bebop2_indi.xml
you can see line 22 that it is loading the imu module for this model which config file is: https://github.com/paparazzi/paparazzi/blob/master/conf/modules/imu_bebop.xml
the last part is pointing to the actual source files use to get the imu data over I2C.
Once you are running the code onboard, you can change the telemetry mode to get the the RAW imu data
you can see line 22 that it is loading the imu module for this model which config file is: https://github.com/paparazzi/paparazzi/blob/master/conf/modules/imu_bebop.xml
the last part is pointing to the actual source files use to get the imu data over I2C.
Once you are running the code onboard, you can change the telemetry mode to get the the RAW imu data
Hello all. I was trying to make sense of the gyroscope raw readings in hover. Since roll and pitch are zero (or extremely close to it), one can assume that the rate of change of yaw is approximately the same as the Gyroscope reading Gz. Upon integrating Gz over a very short period of time (<2 seconds), I obtain a yaw attitude that is way less than the actual yaw. I'm assuming Gz has units of deg/secs. You're insight on this is greatly appreciated