Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • 05:20
    Jaroan closed #1365
  • 05:20
    Jaroan commented #1365
  • Dec 15 00:48
    Deepakgthomas edited #1367
  • Dec 15 00:46
    Deepakgthomas edited #1367
  • Dec 15 00:45
    Deepakgthomas edited #1367
  • Dec 15 00:44
    Deepakgthomas edited #1367
  • Dec 15 00:18
    Deepakgthomas edited #1367
  • Dec 15 00:17
    Deepakgthomas edited #1367
  • Dec 15 00:17
    Deepakgthomas edited #1367
  • Dec 15 00:16
    Deepakgthomas edited #1367
  • Dec 14 23:57
    Deepakgthomas opened #1367
  • Dec 14 08:56
    vooon milestoned #1366
  • Dec 14 07:19
    Jaeyoung-Lim commented #1365
  • Dec 13 23:27
    Travis mavlink/mavros (master) still failing (2712)
  • Dec 13 23:10

    mhkabir on odom_queue

    (compare)

  • Dec 13 23:10

    mhkabir on master

    Change odometry subscription qu… (compare)

  • Dec 13 23:10
    mhkabir closed #1366
  • Dec 13 20:35
  • Dec 13 20:17
    jgoppert opened #1366
  • Dec 13 18:50
    Travis mavlink/mavros@d023442 (odom_queue) failed (2710)
Alfredo Bencomo
@IeiuniumLux
Has anyone encountered issues using MAVROS with ROS Melodic? @fnoop ?
Fnoop
@fnoop
nope, working well :)
Alfredo Bencomo
@IeiuniumLux

@fnoop did you build MAVROS from source or did you just install the Release 0.33.0?

rosinstall_generator --upstream mavros | tee -a /tmp/mavros.rosinstall

Fnoop
@fnoop
yes all built from source
Sorry, tell a lie, also installed from dpkg
Works fine on x86_64
[dev] [mav@dev ~]$ dpkg -l |grep -i mavros
ii  ros-melodic-mavros                                 0.32.1-1bionic.20190809.000240                  amd64        MAVROS -- MAVLink extendable communication node for ROS with proxy for Ground Control Station.
ii  ros-melodic-mavros-extras                          0.32.1-1bionic.20190809.001819                  amd64        Extra nodes and plugins for MAVROS.
ii  ros-melodic-mavros-msgs                            0.32.1-1bionic.20190808.235553                  amd64        mavros_msgs defines messages for MAVROS.
ii  ros-melodic-test-mavros                            0.32.1-1bionic.20190809.161214                  amd64        Tests for MAVROS package
Alfredo Bencomo
@IeiuniumLux
Thanks @fnoop . BTW, did you also install the geographiclib?
$ wget https://raw.githubusercontent.com/mavlink/mavros/master/mavros/scripts/install_geographiclib_datasets.sh
./install_geographiclib_datasets.sh
Fnoop
@fnoop
yes it’s required. My build manifest is here:
What problems are you having?
Alfredo Bencomo
@IeiuniumLux
No issues. Right now, I'm just making sure that all bits required are installed. Thanks for the manifest.
Fnoop
@fnoop
cool :)
Vladimir Ermakov
@vooon
@jveitchmichaelis if you want to pass data from fcu + your messages, then you should use external gcs_bridge node. Because internal one (turned on by ~gcs_url) works on top of internal callbacks, so ROS topic data is ignored.
Prashant Dabholkar
@pdabholkar
@IeiuniumLux I am having trouble installing MAVROS from source with ROS Melodic on aarch64. I am working on debian:buster.
The catkin build manages to build most of the packages. However when building mavros it gets stuck at 9% or at 14% in the build. I have to reboot thereafter
Fnoop
@fnoop
@pdabholkar pass -j1 to your build
It’s running out of memory
Prashant Dabholkar
@pdabholkar
Thanks @fnoop that helped. Should have guessed that it was a memory issue.
Swapneel Uday Naphade
@SwapUNaph

Hi. I am trying to get velocity readings from px4flow through mavros but haven't found a way yet.
I am working on indoor position estimation without GPS and Visual odometry.
In order to that, I need velocity readings from px4flow.
The /mavros/imu/... topics are publishing data but no data is being published on /mavros/local_position/... topics.
From reading the gitter, I am guessing we need some kind of position reading to get the local_position topics get started.
Any help will be appreciated.
Thank you.

PS: I am using Ardupilot and not px4 firmware

Mert Aşkın
@mertaskin95_twitter
@amilcarlucas thank you sir
gyronikeleg
@gyronikeleg

Hello All, I am having a lot of trouble with getting into position control using mocap and matlab to publish pose data. Here is a link to my problem in github PX4/Firmware#13510

@mzahana I saw that you were able to get this to work and wrote the px4 ekf2 instructions to get this to work. Would you be able to help me resolve this?

Suraj Bonagiri
@suraj2596
Hello all,
I'm trying to communicate with pixhawk with px4 stack from mu PC using 433Mhz link.
I decided to with MAVORS. To switch to offboard, online sources said I need to send some setpoints before switching the mode. So im sending 10 setpoint of thrust with a delay of 0.1 before sending the change mode command.
when I do that, pixhawk flashes red 3 times and goes be bop X 2 and the mode remains in manual.
What am I missing here? Breaking my head for a few days now. Any help ishighly appreciated. Thanks!
Suraj Bonagiri
@suraj2596
Suraj Bonagiri
@suraj2596
Also, tried rosrun mavros mavsys mode -c OFFBOARD i get the same be bop sound with red flashes and get timed out
Suraj Bonagiri
@suraj2596
ok, turns out... /mavros/setpoint_attitude/thrust is not a setpoint. Now I'm able to change into OFFBOARD mode
Suraj Bonagiri
@suraj2596
But the failsafe keeps getting activated and deactivated. That was fixed by disabling timesync in px4_config.yaml which seems like a bad way to address it
Andrea Belloni
@anbello
I would like to know of It Is possible to use libmavconn independently from ROS and mavros
And of Is possible some links to c or c++ examples
KHABBAB NAZAR
@khbnzr
Hi, I'm trying to run the precision landing where I've a custom aruco_detect node (https://github.com/UbiquityRobotics/fiducials/tree/kinetic-devel/aruco_detect) which passes the rel_pose to the landing_target.cpp plugin. I've set the required params to enable the precision landing for CompanionComputer. So, when the drone comes above the aruco marker, I give a land expecting the drone to land precisely above the marker which is not the case. Can anyone help me on this ?
Amilcar Lucas
@amilcarlucas
We are doing it, and it works fine.
Post more info.
KHABBAB NAZAR
@khbnzr

SITL with APM and Gazebo(v7.15)

Details of the model :
Stack: ArduPilot
Vehicle: ArduCopter
Version: 3.6.11

Plnd params:
PLND_ACC_P_NSE 2.500000
PLND_BUS -1.000000
PLND_CAM_POS_X 0.000000
PLND_CAM_POS_Y 0.000000
PLND_CAM_POS_Z 0.000000
PLND_ENABLED 1.000000
PLND_EST_TYPE 1.000000
PLND_LAND_OFS_X 0.000000
PLND_LAND_OFS_Y 0.000000
PLND_TYPE 1.000000
PLND_YAW_ALIGN 0.000000

Mavros: 0.33.3
ROS: Kinetic
Ubuntu: 16.04

Eryoruk Huseyin
@huhu1030
Hi guys, I dont have any particular problem but more like an interrogation. I'm a little bit confuse with MAVROS communicating with SITL and MAVProxy. According to the Ardupilot SITL architecture, MAVROS should communicate with MAVProxy (see on diagram udp 14550, OtherGCS). However when MAVProxy is launched, SITL output on port 14550 according to log output -> "SIM_VEHICLE: "mavproxy.py" "--master" "tcp:127.0.0.1:5760" "--sitl" "127.0.0.1:5501" "--out" "127.0.0.1:14550" "--out" "127.0.0.1:14551" "--map" "--console"". I'm a little bit confuse, to whom Mavros is sending MAVLink messages ? MAVProxy that forwards to SITL or SITL directly ?
Eryoruk Huseyin
@huhu1030
Ok I think I've the answer. MAVROS communicate with MAVProxy not SITL. The --out parameters belongs to MAVProxy (I though it was link to SITL, see doc here https://ardupilot.github.io/MAVProxy/html/getting_started/starting.html). It means MAVProxy forwards packet to 14550, which is the same port where MAVROS is listening :)
KHABBAB NAZAR
@khbnzr
@amilcarlucas Could you tell me how you are doing the APM precland functionality ?
Amilcar Lucas
@amilcarlucas
We are using our own aruco code and feeding it into the mavros PrecLand Plugin.
Melodic
MavRos 0.33.4
Arducopter 4.0-rc2
KHABBAB NAZAR
@khbnzr
Are you feeding pixel based or displacement based relative pose to the plugin ?
Fnoop
@fnoop
ardupilot only takes angular offsets, it ignores the pose inputs
KHABBAB NAZAR
@khbnzr
The angular offsets are calculated by the mavros plugin using the rel pose I give before it sends to the fcu.
Since, I've my own vision node calculating the rel_pose between the marker and the drone, the angular offsets are calculated on this line here - https://github.com/mavlink/mavros/blob/master/mavros_extras/src/plugins/landing_target.cpp#L260 but it seems like the plugin is processing the input wrongly and the drone always lands far away from the marker.
patrickpoirier51
@patrickpoirier51
Is you rel pose is in NED or ENU reference frame?