• Content Count

  • Joined

  • Last visited

  • Days Won


Everything posted by Spitfire76

  1. This may help. https://oscarliang.com/setup-switch-opentx/
  2. 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.
  3. 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 ?.
  4. Spitfire76

    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.
  5. 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.
  6. 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. 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. Does that mean that the LEDs don't come on when you apply power ?
  7. 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.
  8. 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.
  9. 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.
  10. Spitfire76

    Drone Delivery

    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.
  11. That looks correct 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.
  12. @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.
  13. 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.
  14. 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. https://thedronetrainer.com/drone-podcast/
  15. 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. https://www.terabee.com/connection-to-pixhawk-autopilots-teraranger-evo/ Yes, below 3m those flight modes (plus LOITER and SPORTS) will use the Evo to maintain altitude rather than the barometer.
  16. 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 RNGFND_MAX_CM RNGFND_MIN_CM 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.
  17. Remote ID Regulations For Unmanned Aircraft Systems (UAS) Are Delayed Until September 2019 https://www.jdsupra.com/legalnews/remote-id-regulations-for-unmanned-79428/
  18. 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. Spitfire76


    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. Spitfire76


    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. Spitfire76


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


    http://ardupilot.org/dev/docs/sitl-simulator-software-in-the-loop.html#sitl-simulator-software-in-the-loop Although it can be run natively on Windows I prefer to create a virtual machine running linux using Oracle's Virtualbox. https://www.virtualbox.org
  24. Where would you like me to send the file ?. Its 856Kb in size ?. You can send me a direct message if you like with the details. Once you have the file you should be able to use Mission Planner and install it as custom firmware. As you can see from the Ardupilot documentation there are several software simulators http://ardupilot.org/dev/docs/simulation-2.html but the simplest is to use Software In The Loop (SITL) http://ardupilot.org/dev/docs/sitl-simulator-software-in-the-loop.html Without going into details at the moment I have it running on linux (Ubuntu 16.04) desktop and use another laptop running Mission Planner to connect to it. Most of the same things as using the hardware flight controller. For example you can arm, take off, change mode, execute missions etc. In that case it sounds like the MS5611 is more of an accurate barometer than was used in some of the earlier versions of the Pixhawk.