Binding with the drone.

A project log for Collective Flight for Aerial Robotics

Development of a machine vision payload to allow aerial robots robust collision avoidance and advantageous collective flight formations.

mr-kar0sh1Mr kAr0sh1 04/08/2015 at 12:540 Comments

MAJOR issues with binding to this little sucker - the UDI 818A. It seems no matter which SPI-based library I use, none of them conform to the correct protocol.

I've tried the 'HCD' library by GeekPhysical with no luck, double-checked the transceiver was actually working with this code from the guys over at Deviation and the script returns a "NO RX ID - Stopping Bind" serial response, prompting me to think the issue is either the protocol I'm using, which apparently may be different for the UDI 818A from the UDI 818, or I need to alter the code slightly to deal with my drone in regards to timing or addresses etc.

So why am I going this route rather than just attaching my own board design directly to the motors, and flying the thing myself? Well, the key is who I'm orientating my project towards. The idea is that you can get this payload, attach it to any drone, and wirelessly take charge of it without any invasive alterations to the drone itself, but still giving you higher-level functions similar to if you had actually reprogrammed it completely. There is increasing evidence that this is what industry are doing also, with military aircraft.

Other aspects of control, like being able to tether several drones to one payload and fly them in a group, could be taken advantage of - one sensor payload to several drones means you could conserve energy and weight, vital if you want to fly long distances or carry one, big, heavy object.

My weakest subject is radio transmission/ICs so this is going to be a tough start but I'm going to have to do some research into how these guys probe and sniff the protocols the SPI transceivers use. I have a Bus Pirate handy (thank God) and a pretty decent oscilloscope so I'm not showing up empty handed!