• Content Count

  • Joined

  • Last visited

  • Days Won


Spitfire76 last won the day on September 30

Spitfire76 had the most liked content!

Community Reputation

281 Excellent

About Spitfire76

  • Rank
    Advanced Member

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. ok, great. Let us know when you get it in the air.
  2. Interesting, I did not know about this project. I assume that you are building this one as I noticed he has also moved to 32 bit processors on his later build. http://www.brokking.net/ymfc-al_main.html To get back to your original post, yes the ESC have to be connected to the flight controller, in this case the UNO, and not the receiver. Each ESC should be powered directly from the battery in order to drive the motors. These typically are thicker wires to handle the higher current and connect to a power distribution board (PDB). Some ESCs provide +5v as they have a built in BEC (Battery Eliminator Circuit) but you should not use it if the +5v is provided to the UNO and receiver by another source (you diagram shows from the battery using a diode). Does you PDB have a built-in BEC ?. If so you could use that to power the UNO and receiver.
  3. I don't see how you could have used channel 6. My understanding is that you have to use channels 7 - 12. 7 & 8 can be set from MP's extended tuning screen and you should see in the drop down Relay on/off which would correspond to aux 5 and relay 1 aux 6.
  4. Let's take a step back and continue to use the retractable landing gear as an example as I've had experience in setting that up. Firstly you have to of course know what is type of signal is required by the landing gear hardware for it to deploy and retract. In my case the landing gear controller required a PWM signal. Originally I did not have this driven from the flight controller but simply use one of the spare PWM outputs of the receiver which was in turn mapped to a switch on my transmitter. This worked but what would have happened if my drone lost the transmitter signal and the failsafe action was RTL or land ?. If the landing gear was retracted when this occurred there is no way to deploy it before it landed unless I could regain control over the drone. So this is the case when you want the flight controller to drive the PWM to the landing gear controller as the ArdCopter code does deploy it before it lands. Of course you also want to retract and deploy it from a switch on the transmitter. I used the first aux pins and so SERVO9_FUNCTION was set to landing gear and also CHXX_OPT was set to landing gear where XX was the sbus channel I was using from the receiver.
  5. Hello @UnoMatt and welcome to the Forum. Not sure how to answer your question but it may help me if you explain a bit more about your project. It looks like you are building a flight controller from scratch using an Arduino Uno. 8 bit processors were first used in early flight controllers but these days 32 bit processors are mainly used. For example the open source Ardupilot software that I use for my drones was originally designed to work on Arduino processors, hence the "ardu" in the name but the software evolved so much it required more memory and processing power and several years ago the Arduino hardware was abandoned in favor of 32 bit arm processors. So what software were you planning on using in your project or were you going to write your own ?
  6. Only having 1-14 channels for servo outputs is likely is due to having a limit of 14 PWM outputs on the original Pixhawk hardware (8 main + 6 AUX). As you may know the 16 channels coming from the receiver need to be allocated to various functions. Some of these functions map to servo functions and some do not. For example RTL does not map to a servo function but needs an input channel from the receiver to trigger it. On the other hand landing gear needs both a channel from the receiver and a servo output. Also rather than just directly mapping a receiver input channel to a servo output (passthru) you may want the flight controller to also control that function. A good example is the case of retractable landing gear as you would likely want it to automatically deploy before it lands in the case of RTL or have a mission script control that function. So don't think of the servo output functions correspond to the receiver input channel as they are really separated. These should by default (BRD_PWM_COUNT = 4) be assigned as digital output rather than PWM servo functions outputs which by the way also means that servo channels 13 and 14 and not used by default in addition to 15 and 16. in this case aux5 and 6 correspond to the first and second relays and can be operated by a receiver channel or a mission script. http://ardupilot.org/copter/docs/common-relay.html
  7. On the side of the flight controller that has the 8 main and 6 aux outputs there should be 2 more connections. One is marked RC which is the sbus connection from the receiver and the other is marked SB which is the sbus out. This should contain all 16 servo function outputs but it has to be connected to a device that understands the sbus protocol. For example I have a camera gimbal that has a controller with a sbus input so can allocate 2 channels to pitch and pan. If you want to control a device that only understands a PWM input you would need to use a sbus to PWM convertor. So have you used up all 14 PWM outputs ?. Again what are you really trying to configure ?.
  8. I believe that they would be available on the sbus output of the pixhawk and you would configure them with SERVO15_FUNCTION and SERVO16_FUNCTION. What exactly do you need to do ?
  9. I wonder if they plan on further collaboration with Parrot since they use their hardware for the optional controller ?.
  10. When you say "programmed" I assume that you mean flashed with flight controller software so the approach I would take is to first decide what software you want to use and see if the board is supported. Since the software is constantly being improved it typically requires more memory and processing power and older boards may no longer be supported with later versions. I believe that Betaflight is the most popular flight controller software for FPV racing so I would start here. https://github.com/betaflight/betaflight/wiki
  11. While I believe that controller was good in its day there is a lot more choice available today. Are you planning on building a drone and if so what do you want to use it for ?
  12. Hello @MarcusJubin - great to see another drone builder join the forum. The only component on your list that I am familiar with is the Holybro Kakute F7 flight controller and I really like it. I should point out that I am not using it for racing or freestyle but as an economical flight controller to run http://ardupilot.org open source software. The main features that I like is the separated IMU board which means you can mount the main board directly on the frame without vibration dampers. I also like the serial ports can be inverted which means I can directly connect to frisky s.port for telemetry.
  13. Correction to my previous post - its more like 1h 37 mins into the youtube video.
  14. Thanks @pemese for this post. You might want though to check the link "To buy click here" as I get a 404 error - page does not exist https://store.mrobotics.io/mRo-Control…/mro-ctrl-zero-f7.htm
  15. @Isabella | UAV Coach - Looks like today was the launch! Wow, the R2 is just $999 and one can be reserved for $100. https://www.skydio.com Its interesting that they can sell it for that price as apparently its made in the USA by a US company! The CEO of Skydio, Adam Bry, joined today's live DSTW episode (he joined at 53 mins in)