tumbili on master
Update SUMMARY.md Create uart-ulanding-radar.md Update uart-ulanding-radar.md and 2 more (compare)
Actually the problem is if I upload the latest stable release from QGC via "firmware -> PX4 Flightstack -> stable release" QGC does all the procedures(download + erase + upload). But when board reboots, somehow it restores previous uploaded version(Or QGC fakes everything). But if I upload the firmware by downloading releases from github and doing "firmware -> PX4 Flightstack -> custom firmware" everything works just fine. Is it a QGC bug?
@eric1221bday
@aagontuk
Encountering a silly problem. I have downloaded the latest daily build of QGC(2017-06-17) and from there installed PX4 firmware v1.6.3 into my board. But after rebooting in the summary tab QGC is showing my firmware version as v1.6.1dev. What is the problem? How can I be sure about my firmware version?
@aagontuk
Actually the problem is if I upload the latest stable release from QGC via "firmware -> PX4 Flightstack -> stable release" QGC does all the procedures(download + erase + upload). But when board reboots, somehow it restores previous uploaded version(Or QGC fakes everything). But if I upload the firmware by downloading releases from github and doing "firmware -> PX4 Flightstack -> custom firmware" everything works just fine. Is it a QGC bug?
I concur. Mine was QGroundControl Development HEAD:54c92f75c 2017-06-22 02:20:17 -0300. I decided to try Custom Firmware so I downloaded the Stable Firmware.zip but there are 13 PX4 files in there. Which one is the stable verison for Quad Plane and Quad Ranger? Any assistance or direction is highly appreciated.
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