Where communities thrive

  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
Repo info
  • Dec 27 2016 20:06

    tumbili on master

    Update SUMMARY.md Create uart-ulanding-radar.md Update uart-ulanding-radar.md and 2 more (compare)

  • Dec 27 2016 20:06
    tumbili closed #179
  • Dec 27 2016 20:02
    tumbili synchronize #179
  • Dec 27 2016 16:24
    LorenzMeier commented #179
  • Dec 27 2016 16:23
    tumbili commented #179
  • Dec 27 2016 16:21
    tumbili synchronize #179
  • Dec 27 2016 15:26
    tumbili opened #179
  • Oct 02 2016 17:42
    julianoes closed #178
  • Oct 02 2016 17:42
    julianoes commented #178
  • Oct 02 2016 11:18
    jiapei100 opened #178
  • Sep 28 2016 10:23
    mhkabir closed #177
  • Sep 28 2016 10:23
    mhkabir commented #177
  • Sep 28 2016 06:06
    mahesha-path edited #177
  • Sep 28 2016 06:04
    mahesha-path opened #177
  • Sep 27 2016 10:32
    eyeam3 closed #176
  • Sep 27 2016 10:32
    eyeam3 commented #176
  • Sep 27 2016 09:59
    julianoes commented #176
  • Sep 21 2016 16:45
    eyeam3 opened #176
  • Jul 28 2016 06:46
    LorenzMeier closed #170
  • Jul 28 2016 06:17
    LorenzMeier closed #87
Sry can pixracer replace px4 ?
Hadi Ahrovani
Multi-Vehicle Simulation
this tutorial say "source your environment" and then enter "roslaunch px4 multi_uav_mavros_sitl.launch":
output is:
roslaunch px4 multi_uav_mavros_sitl.launch
... logging to /home/cv/.ros/log/0dfb88da-e966-11e7-90f0-71f1019dd856/roslaunch-ubuntu-44603.log
Checking log directory for disk usage. This may take awhile.
Press Ctrl-C to interrupt
Done checking log file disk usage. Usage is <1GB.

Usage: xacro.py [options] <input>

xacro.py: error: expected exactly one input file as argument
while processing /home/cv/src/Firmware/launch/single_vehcile_spawn.launch:
Invalid <param> tag: Cannot load command parameter [iris_1_sdf]: command [/opt/ros/kinetic/share/xacro/xacro.py /home/cv/src/Firmware/Tools/sitl_gazebo/models/rotors_description/urdf/iris_base.xacro rotors_description_dir:=/home/cv/src/Firmware/Tools/sitl_gazebo/models/rotors_description mavlink_udp_port:=14560 > iris_1.urdf ; 'gz sdf -p iris_1.urdf'] returned with code [2]. 

Param xml is <param command="$(arg cmd)" name="$(arg vehicle)_$(arg ID)_sdf"/>
The traceback for the exception was written to the log file
Hello everyone, I need to create a new airframe
But I don't know how to adjust mixer values
for example servo limiting, tail BLDC adjusting etc. if anyone knows please send a message to me
Hi friends,,,, Has anyone worked in Single copter? I am working on pixhawk mini with px4fmu-v2_lpe firmware and finding a bit struggle in PID tuning for that. Will appreciate your all suggestions.
Chenghao Yang
@Ahrovan I found a solution, but I'm not sure.
@Ahrovan PX4/sitl_gazebo#101
I would like to ask if there are equivalent flag from micropilot in Pixhawk. I mean if there is any analogue to
in fly/on ground
Thanks for any help!
hi anybody has the px4fmuv5 hardware schematic?
hello everyone, how to write a mixer file what is the vector and scale factors and offset is it geometrical?

When I compile the PX4 source code of 1.6.2 version, I meet this error. But when I compile the latest version(1.7.3), It can be compiled successfully. Anyone who can help me?

root@ubuntu:~/px4_code/px4_0/xyi_px4# make px4fmu-v2_default
-- CMAKE_MODULE_PATH: /home/yst/px4_code/px4_0/xyi_px4/cmake
-- Nuttx build for px4fmu-v2 on m4 hardware, using nsh with ROMFS on px4fmu_common
-- Build Type: MinSizeRel
Traceback (most recent call last):
File "Tools/tag_to_version.py", line 19, in <module>
minor = res[1]
IndexError: list index out of range
-- PX4 VERSION: 3284b7d
-- CONFIG: nuttx-px4fmu-v2-default
-- The ASM compiler identification is GNU
-- Found assembler: /home/yst/gcc-arm-none-eabi-7-2017-q4-major/bin/arm-none-eabi-gcc
-- Found PythonInterp: /usr/bin/python (found version "2.7.12")
-- Found PY_jinja2: /usr/local/lib/python2.7/dist-packages/jinja2
-- C compiler: arm-none-eabi-gcc (GNU Tools for Arm Embedded Processors 7-2017-q4-major) 7.2.1 20170904 (release) [ARM/embedded-7-branch revision 255204]
-- C++ compiler: arm-none-eabi-g++ (GNU Tools for Arm Embedded Processors 7-2017-q4-major) 7.2.1 20170904 (release) [ARM/embedded-7-branch revision 255204]
-- Adding ROMFS on px4fmu-v2
-- Nuttx build for px4fmu-v2 on m3 hardware, using nsh
-- Configuring done
-- Generating done
-- Build files have been written to: /home/yst/px4_code/px4_0/xyi_px4/build_px4fmu-v2_default
[73/566] Building NuttX for px4io-v2 with nsh
FAILED: cd /home/yst/px4_code/px4_0/xyi_px4/build_px4fmu-v2_default/px4io-v2 && /bin/rm -rf /home/yst/px4_code/px4_0/xyi_px4/build_px4fmu-v2_default/px4io-v2/NuttX/nuttx/nuttx-export && /usr/bin/make --quiet --no-print-directory -C /home/yst/px4_code/px4_0/xyi_px4/build_px4fmu-v2_default/px4io-v2/NuttX/nuttx -r CONFIG_ARCH_BOARD=px4io-v2 export >nuttx_build.log && cmake -E touch /home/yst/px4_code/px4_0/xyi_px4/build_px4fmu-v2_default/px4io-v2/nuttx_export.stamp
stdio/lib_sscanf.c: In function 'vsscanf':
stdio/lib_sscanf.c:419:28: error: this statement may fall through [-Werror=implicit-fallthrough=]
sign = true;
stdio/lib_sscanf.c:420:21: note: here
case 'u':
cc1: all warnings being treated as errors
make[2]: [bin/lib_sscanf.o] Error 1
make[1]: [libc/libc.a] Error 2
[73/566] Building NuttX for px4fmu-v2 with nsh
FAILED: cd /home/yst/px4_code/px4_0/xyi_px4/build_px4fmu-v2_default/px4fmu-v2 && /bin/rm -rf /home/yst/px4_code/px4_0/xyi_px4/build_px4fmu-v2_default/px4fmu-v2/NuttX/nuttx/nuttx-export && /usr/bin/make --quiet --no-print-directory -C /home/yst/px4_code/px4_0/xyi_px4/build_px4fmu-v2_default/px4fmu-v2/NuttX/nuttx -r CONFIG_ARCH_BOARD=px4fmu-v2 export >nuttx_build.log && cmake -E touch /home/yst/px4_code/px4_0/xyi_px4/build_px4fmu-v2_default/px4fmu-v2/nuttx_export.stamp
stdio/lib_sscanf.c: In function 'vsscanf':
stdio/lib_sscanf.c:419:28: error: this statement may fall through [-Werror=implicit-fallthrough=]
sign = true;
stdio/lib_sscanf.c:420:21: note: here
case 'u':
cc1: all warnings being treated as errors
make[2]: [bin/lib_sscanf.o] Error 1
make[1]: [libc/libc.a] Error 2
ninja: build stopped: subcommand failed.
Makefile:164: recipe for target 'px4fmu-v2_default' failed
make: * [px4fmu-v2_default] Error 1


Any one there
@falcon15 are the people on PX4 moving to slack?
Rafael Rodrigues Teixeira
Throne Vault
Anyone using PX4 with Intel Aero RTF ?
@ThroneVault I am but did not play with it much :/
Sean Owens
Yeah, I am right now. Of course you asked that question over a month ago.
Good day, i need info about mag issues on pixracer
where can be found bootloader for pixracer
Why I make px4fmu-v2_default ,it shows error:expected initializer before '_PARAMS' from the
Guys, is there anyone find a method to control the thrust force and torques directly for the drone with PX4?
Vasily Evseenko
Hi, could someone review and apply PX4/Devguide#723 ?
I have the above problem when using STIL, how can I solve it?
My operating system is not ubuntu, but is deepin which is a derivative system of debian
My screenshot appears after typing the following command:
make px4_sitl jmavsim
If I don't do anything, the program will stop at this line:
INFO  [ecl/EKF] EKF commencing GPS fusion
I used to drive the computer for one night and the program still stops here.
Please help me, thank you, I am a newbie.

So I used a stereo camera, a TX2 on top of Pixhawk to achieve fully autonomous drone flight and collision avoidance.

In case someone is also interested, here is how I have done it:https://github.com/generalized-intelligence/GAAS/tree/master/demo/tutorial_1

Hi, I started working with UAVCAN using px4. I found a function inside esc.cpp called "int res = _uavcan_sub_status.start(StatusCbBinder(this, &UavcanEscController::esc_status_sub_cb));" but this function is never getting executed when I call it from uavcan_main.cpp. Can someone tell me how to access this function?
Hi Guys, New to this site. Im building a PX4 drone all up weight is 4kg with 15x5.5 props. I have chosen the Generic Quadcopter X model and the drone flies however its quite unstable on basic settings. Ive increased MPC_THR_HOVER to a level where the drone is quite good at maintaning altitude on stabilised mode. Its very rocky with default PIDS but increasing them makes it better.
I do have 2 problems though. On take off in ATTITUDE or Position it rises to a height of around 1.5 Meters and climbs or descends a lot on its own. Once I take it up to about 7 meters this stops and it feels like its locking on to ATTITUDE. what could cause this.
The other problem is Landing. In stabilised mode it lands fine But ATTI and POSITION it wont land it wants to rise and will not decrease motor speed. We are hoping to get it to land well as this is a machine that will be used for others to fly hopefully just in position mode. Ive tried Lowering MIN_PWM to 990 this is the lowest the motors do not stop while armed and tilting. Any hekp on these 2 problems would be amazing.
Alexis Paques
This is deprecated; See the slack
Hi, everyone; we are trying to build a C++ application indoor with px4 and uwb; I can push mocap position as vision pose to EKF2 ( through the MavSDK Passthrough ), but when I try to do some offboard control with mavsdk, the telemetry::health() prompts "Home position to be set"; I try to set home position with mavlink_set_home_position_t message, but it doesn't work; Has anyone met this problem before? What should I do to use mavsdk and uwb for auto control indoor? Thanks...
Alex Albert
inertial sense pixhaw??
Alex Albert
do you know any information about connecting this inertial navigation system to pixhawk or do you know a post
Alex Albert
do you have any idea how to connect inertial sense uINS with pixhawk?

When I try to calibrate radio, QGC says, " Detected 0 radio channels. To operate PX4, you need at least 5 channels".
I flash px4 omnibus_f4sd_default to eachine X220s’s flight controller Omnibus F4 V3 flight controller with STM32 F405 MCU.
At the begining all hardware was default.(flysky fs-i6x transmitter and fs-a8s receiver)
then i changed them to taranis x9d-plus and frsky d8 receiver.
i took that radio channel error on qground with both combinations.
but when the firmware was betaflight all combinations were okey.
here is my cable connection on board.
i soldered sbus slot near the "pw" led.


I need help, I downloaded the px4 Firmware, installed ros and ran the commands "make px4_sitl gazebo_iris_opt_flow" and "roslaunch mavros px4.launch fcu_url: =" udp: //: 14540@ 14557 "", however when I run "rostopic list" I don't get a topic image from the camera. Can someone point me to a tutorial on how to activate this?
UAS Nmims
Hi! i wish to run a multi-vehicle simulation on gazebo but i can't seem to figure out how to change the spawn/starting location of Individual UAVs. I have tried using export PX4HOME(LAT/LONG/ALT) , but that just seems to change the starting location of the entire batch of UAVs and I don't know how to adjust their individual positions explicitly.
Hi am trying bulid vtol drone using px4 , so I am not getting framewares only , were can find the frameware,