Multirotor, multicopter and quadcopter discussion - The Drone thread

Off the current topic, took my hand to soldering the motors to the ESC's after I got in from work. I don't normally solder and have only done it for a couple of other projects, so not too bad! The main lesson I learnt tonight is don't use so much solder to tin the pads! Now I've got ugly blobs on the ESC's haha. All a learning curve!

Anyone with a keen eye will note how anal I've been, and the first to notice will receive an internet cookie haha.

RSAlsLP.jpg
All wired the same and very tidy. Just building one myself, I don't think I'll use BLHeli or Cleanflight pass-through for direction. Just from a spares and changeout pov. I'm planning on using inline 2mm bullet connectors and crossing wires. With 4 off the same motors and Nyloc nuts.
 
Last edited:
The thing is though, it needs to be proportional. If flying ANYTHING within controlled airspace was prohibited then you would technically fall foul of the law by flying your £30 toy drone in your garden.
It looks like the European-wide version of the CAA are in the process of publishing draft rules. They are very prescriptive indeed from what I've read (height limit of 50M, nothing home built of over 250g, mandatory registration of all craft etc etc.)

but not all uk airspace is controlled.
 
I know, I was referring to flying a toy drone within controlled airspace if your house happened to be in the flightpath of Heathrow for example.
 
even that wouldn't be controlled near ground level would it? thought there was generally a height where it becomes controlled.

either way I hope some sensible reforms are made before it goe ahead.
the registaration doesn't bother me, as long as its cheap and small models don't require a license etc.
 
All wired the same and very tidy. Just building one myself, I don't think I'll use Cleanflight pass-through for direction. Just from a spares pov, I'm planning on using inline 2mm bullet connectors and crossing a wires with 4 of the same motors with Nyloc nuts.

Indeed I'll be reversing them via software, but it's something about the wiring which took it too far according to my partner lol.
 
even that wouldn't be controlled near ground level would it? thought there was generally a height where it becomes controlled..

CTRs or Control Zones extend from the ground upwards. They are usually found surrounding major airports.

CTAs or Control Areas extend from a specified lower limit upwards.

See HERE for a nice airspace chart of the UK.
 
even that wouldn't be controlled near ground level would it? thought there was generally a height where it becomes controlled.

either way I hope some sensible reforms are made before it goe ahead.
the registaration doesn't bother me, as long as its cheap and small models don't require a license etc.

It could be. Typically the control zone around an airfield would 5 miles in diameter from ground level to 3000', or something like that. Don't know about Heathrow exactly but will be bigger and like an upside down wedding cake.

I just can't see the need for additional limitations in uncontrolled airspice. (I have an interest here,as I really really want to buy a dji mavic)
 
I just can't see the need for additional limitations in uncontrolled airspice. (I have an interest here,as I really really want to buy a dji mavic)

I would agree with you there. I think the current 7KG and 400 feet rules are fine for drone flying outside controlled airspace.

As for operating inside controlled airspace I think all that is needed is to introduce a rule that permission is required from the controlling ATC unit, who can then stipulate height limits. The advantage to this is that ATC may well be able to grant you higher than 400 feet. In the case of the Edinburgh CTR, I would be quite happy giving a drone operator a 1000ft limit in most of the CTR as long it was clear of the approach and climbout.
 
Indeed I'll be reversing them via software, but it's something about the wiring which took it too far according to my partner lol.

Ah yes I noticed the slight bends in direction of rotation. Possibly a little too far. Tidy is fine though. I always shorten cables. Like those ESC signal wires, if I was using a pin out header on the FC. I'd shorten and re-crimp the connectors, so much tidier. Have a look for a HT-225D, God send for model wiring.

Btw, I guess the twisted pair (signal/neg) on the ESC is for crosstalk. Anyone tried using just a single signal wire? Lot tidier with just 4 wires into a 4 pin Molex to FC header..
 
Last edited:
Ah yes I noticed the slight bends in direction of rotation. Possibly a little too far. Tidy is fine though. I always shorten cables. Like those ESC signal wires, if I was using a pin out header on the FC. I'd shorten and re-crimp the connectors, so much tidier. Have a look for a HT-225D, God send for model wiring.

Btw, I guess the twisted pair (signal/neg) on the ESC is for crosstalk. Anyone tried using just a single signal wire? Lot tidier with just 4 wires into a 4 pin Molex to FC header..

I've not bothered to neaten up the ESC's yet, until I get the PDB and get it all built up.

I'm a perfectionist, too much some times, so I want this build to look as clean as possible.
 
As for operating inside controlled airspace I think all that is needed is to introduce a rule that permission is required from the controlling ATC unit, who can then stipulate height limits. The advantage to this is that ATC may well be able to grant you higher than 400 feet. In the case of the Edinburgh CTR, I would be quite happy giving a drone operator a 1000ft limit in most of the CTR as long it was clear of the approach and climbout.

I think article 94 could be adjusted to cover this by reducing the weight limit.

And arguably, I suppose a transponder would not be an unreasonable requirement within controlled airspace where you are required to provide radar separation (or indeed any controlled airspace depending on how the risk is perceived). Most airspace in the country would still be available for those who don't want the additional cost.

I would support throwing the book at the worst offenders infringing the rules. I suspect a few £5000 fines for the real idiots would focus everybody's mind on operating these things sensibly.

I just hope the CAA chose a happy middle ground which keeps costs down for those who want to wizz round in a field in the middle of nowhere.:)
 
Last edited:
And arguably, I suppose a transponder would not be an unreasonable requirement within controlled airspace where you are required to provide radar separation (or indeed any controlled airspace depending on how the risk is perceived). Most airspace in the country would still be available for those who don't want the additional cost.

Transponders are a bit overkill and we only need to provide separation to IFR traffic. I think a simple permission system would work, same way we currently treat things like paragliders. You phone up, say I want to fly here with my drone, we say ok, not above 1000ft and give us a phone back when you're finished, job done. That way when I've got low level VFR traffic in the zone I can at least give them information.
 
I've not bothered to neaten up the ESC's yet, until I get the PDB and get it all built up.

I'm a perfectionist, too much some times, so I want this build to look as clean as possible.

There's quite a bit of wiring on these if you start adding FPV, GPS, OSD etc. For reference the pin headers on the flight controllers & OSD/PDB boards are 0.1" (2.54mm) Molex KK 254 series (Crimp Housing etc).
 
Transponders are a bit overkill and we only need to provide separation to IFR traffic. I think a simple permission system would work, same way we currently treat things like paragliders. You phone up, say I want to fly here with my drone, we say ok, not above 1000ft and give us a phone back when you're finished, job done. That way when I've got low level VFR traffic in the zone I can at least give them information.

This makes sense, I hope the CAA decide to be as reasonable. But would there not be cases where you would need to monitor where a drone was, in case it inadvertently infringed, say the final approach path?
 
There's quite a bit of wiring on these if you start adding FPV, GPS, OSD etc. For reference the pin headers on the flight controllers & OSD/PDB boards are 0.1" (2.54mm) Molex KK 254 series (Crimp Housing etc).

Might have fallen a little in love with you just now mate haha, saved me a bunch of research as that is something I was wondering about.

Ideally I don't want wires dragging longer than needed. The PDB I've gone for will still have wires going places, but I'll tuck them up.

Also ordered some conformal spray to coat the PDB to protect it from shorts. Again, way OTT but I enjoy that side of things. Over engineering stuff.
 
This makes sense, I hope the CAA decide to be as reasonable. But would there not be cases where you would need to monitor where a drone was, in case it inadvertently infringed, say the final approach path?

There's a certain amount of trust involved. If you phone up and say you're going to be operating over a certain area then we expect you to do it. Exactly the same as how we treat paragliders and gliders. Paragliders very rarely show up on radar either.

We actually do get drone operators phoning up regularly to let us know that they are there, usually over the Forth Bridges or the University, but I'm guessing that they are commercial operators. On the flipside I have also seen a few videos online of videos shot from drones over places inside the Edinburgh CTR which are too close for comfort especially when we don't know that they are there.
 
Back
Top Bottom