• Content Count

  • Joined

  • Last visited

  • Days Won


Posts posted by Spitfire76

  1. On 6/5/2019 at 9:51 AM, erfan said:

    ./waf --targets bin/arducopter --upload .
    AM I right with the procedures ?

    I am not so sure about the above. The way that I have been compiling for the HK32Pilot board is

    Once its compiled the binary file to install using MP is 



  2. @erfan - I tested version 3.6.9 of ArduCopter with SITL and it seems to work at least with the simulator. This time I set the RTL_ALT_MIN to 0 in config.h and recompiled so effectively it has no minimum altitude when flying back to the launch site and will just stay at its current height. I did need to set RTL_ALT to 0 in mission planner otherwise it will climb to that value which was set to 1500 cm so 150m.

  3. Just wanted to add to my previous post. I suspect that the Betaflight configuration has already been setup so you may not need to change much but you can check that the QX7 channels are mapped correctly by going to the "receiver" section of the configurator. Also you do need to "arm" the motors which could be the cause of your issue with them not doing anything when you move the throttle. You need to configure the QX7 with a switch mapped to say channel 5 to be used for arming.

    Of course remove the props before doing any bench testing.

  4. 1 hour ago, BenL said:

    Oh the LEDs on the reciver? They do the exact same thing as in the video.

    In that case a solid green on the receiver should mean that the QX7 and XM+ are bound. Is the FC running the betaflight software and if so have you checked its working with the betaflight configurator ?.

  5. 4 hours ago, erfan said:

    Today I tested the throttle failsafe .

    Before going into too many details as to the behavior of "low throttle" method is there a reason why you can't use the "no signal" method ?. I use the "no signal" method on my FrSky Taranis as that seems to be the preferred method but it does depend on the make of receiver.

  6. 11 minutes ago, BenL said:

    The LEDs on the drone to indeed come on when I connect the battery. When I apply throttle the motors don’t do anything.

    Ok, what color LEDs come on and are they flashing or on solid ? As explained in the video the receiver is bound when power is applied and the green LED comes on solid.

  7. 14 hours ago, BenL said:

    #1 the board gets piping hot #2

    That doesn't sound too good. I don't have one of these receivers but it looks like the wiring is quite simple. Those 3 connections should go directly to the flight controller.



    #2 when I press bind it comes up with “channel 1-8 no telem channel 1-8 telem channel 9-16 telem channel 9-16 no telem” all of these are options.

    This is for receivers that have PWM pins and since this just has an SBus output it really should not matter which one you select.


    And lastly nothing happens when I apply power

    Does that mean that the LEDs don't come on when you apply power ?


  8. 28 minutes ago, BenL said:

    Yes it does have a compatible receiver, I can send a pic if needed 

    Do you know what type of FrySky receiver?. Is it the XM+ ?. If it does this video that I found should help with the bind procedure. If it does't bind you may have to flash firmware on the receiver as mentioned in this video.


  9. 8 minutes ago, BenL said:

    I have a Tero Q215mm DIY drone and a Taranis QX7 (it’s my first DIY drone) how would I connect the two? Thanks!

    Can I assume that if you are going to use the Taranis QX7 transmitter that your Q215 has a compatible FrSky receiver ?. Only it looks like some versions come with a receiver and some don't. If it does the first thing we need to work out is how to "bind" your TX with the receiver but lets first check that it has one.

  10. 1 hour ago, erfan said:

    so I need to change rtl_alt_min=0  in config.h

    In the firmware that I complied for your earlier I changed it to from 200 to 100 figuring that you still want to have some minimum height during RTL but not as much as 200cm. That's what I used to test with SITL and noticed that if I was currently at 50cm triggering a RTL would make it climb to 100cm instead of 200cm. If its 0 I would expect it to maintain its current height but would prefer to test it.


    • Like 1

  11. 1 hour ago, RogerRog said:

    What are you going to deliver in that way?

    Welcome to this forum. Note that there is a quote button that allows you to either quote a whole post or selected section of the text as its not so obvious that you are replying to the last post. Also note the date of the previous posts. This thread is from 2016 so the industry has changed quote a bit in that time.

  12. 3 hours ago, erfan said:

    which says I should not change those values.

    That looks correct

    3 hours ago, erfan said:

    so When I use this teraranger it automatically adjusts the altitude in case of a obstacles from underneath?!

    Yes, the issue with the standard barometer is that it measures atmospheric pressure to calculate altitude so it has no idea if its above an object. As the Ardupilot wiki explains you can use use the GPS data if it contains ground elevation  information in order to follow the terrain but it still does not help with objects. A rangefinder is a distance sensor so its measuring the distance to the ground or what ever object is underneath it.

  13. @erfan - the parameter.cpp file is not what you need to look as those //@ are comments. The real code is in mode_rtl.cpp and look for RTL_ALT_MIN not RTL_ALT. RTL_ALT_MIN is used in the mode_rtl.cpp to maintain a minimum height in RTL. It is not exposed in the parameter list like RTL_ALT and is defined in config.h as 200 (cm). So even if RTL_ALT is set to 0 and the current height is below RTL_ALT_MIN the UAV will still climb to that height.

  14. 4 hours ago, erfan said:

    should I set this parameter to 1 ? or let it be zero (default value) ?


    4 hours ago, erfan said:

    so should I change this parameter ?  

    Good questions. I imagine that you leave both those as default but let me check further. The last time that I configured a rangefinder on my hex I never changed those parameters and it worked fine.

  15. On 6/2/2019 at 5:07 PM, dbaker said:

    I am very new to the drone game, even newer to the drone business game.

    If I am going to get my Part 107 license and want to make money, do I need to set up a business and get state and local licenses? Or am I basically covered in that regard by the Part 107. I heard that I can get the Part 107 license and then make money the next day.


    As the FAA states on their website Part 107 certification allows pilots with a drone that is less than 55 pounds to fly for work or business by following the Part 107 guidelines. It does not replace any local or state rules for establishing and running a business.

    If you listen to podcasts you might find this one helpful.


  16. 5 hours ago, erfan said:

    1) How should I adjust that after this range the barometer should be used?

    You don't have to by configuring a range finder and setting RNGFND_MAX_CM : 300 ArduCopter will know to use the barometer above 3 m and the rangerfinder below 3m. If a rangefinder were not configured ArduCopter would know to use the barometer all the time. There is a way to check that the sensor is being used in these instructions which it looks like by how you set the parameter that you are already using.


    5 hours ago, erfan said:

    2) So when I fly now the pixhawk it self should read these range in ALT_HOLD ; POS_HOLD AND AUTO .Am I right? 

    Yes, below 3m those flight modes (plus LOITER and SPORTS) will use the Evo to maintain altitude rather than the barometer.

  17. On 5/31/2019 at 7:32 AM, erfan said:

    I got the Evo 3m . 

    Wow, that is a short range. I believe the Evo 60m is usually the one used for drones but since you are flying so low maybe the 3m one is better. You may have to change these parameters 


    The first one tells ArduCopter the distance that the range finder is reliable i.e above this height the builtin barometer should be used. The second is the distance from the ground to the sensor. This is used to know when the UAV has landed.

  18. 3 hours ago, erfan said:

    I got the tera ranger

    Which one did you get, the RangerOne or the Evo 60m ?. I am not sure it will help so much your landings in stabilize mode as I previously explained in a post it does take practice. It should help with keeping a constant height in modes that previously used the onboard barometer, like ATL_HOLD, LOITER and POS_HOLD.


  19. 2 hours ago, erfan said:

    can any body please help me out in this case ?

    Looks like SRTM means Shuttle Radar Topography Mission so its must be related to the maps that MP is trying to download. It makes sense since you only get this error when you try to use a different location. Try changing the map that mission planner is using.

    To change the map used right click in the map of the flight data screen and select Planner, change the map, then close the Planner view. The new map will now be used in the Flight Data view.

  20. @erfan - were you able to test that last firmware that I compiled ?. Since you said that the board was returning the id of px4v3 in MP I compiled it with the board option fmuv3 which I believe is the correct one. Also maybe you could share some more information about the project that you are working on.

  21. 1 hour ago, erfan said:

    Is this simulation working when we select the specific location ( - L locationname ) when runing by cygewin terminal.

    I am specifying a specific location and its working fine. I added my location to the ardupilot/Tools/autotest/locations.txt file. Note that format is longitude, latitude, altitude, heading. I then run from the ardupilot/ArduCopter directory using the following command

    sim_vehicle.py --console -m --out= --location=MYLOC

    where MYLOC is the label in the locations.txt file that I added and the IP address is the laptop running Mission Planner.


  22. 7 hours ago, erfan said:

    I have faced to two problems:

    Loading and changing parameters works on my setup so not sure whats happening with yours. Do other commands work like changing the flight mode ?