Greetings.May I thank you in advance for your patience, I am quite new to the scene but learn quickly. I apologise that some of what I am asking here has no doubt already been mentioned - I have spent the last few days vigorously looking through this site to try and learn as much as possible. Hopefully some direct responses to my custom plans will help me "synthesise" all of this information and increase my understanding of what I want and what is needed.I'm in the viability and planning stages of a UAV project to be built by and further educate the young people at our Air Training Corps squadron.While the famous Nitro Model's "Predator B" is somewhat small, it is the only model that accurately represents the MQ-9 Reaper; the newest UAV of the Royal Air Force. I endeavour to use this airframe, or a better alternative that might hit the market. Hope to tackle the lack of space by adding hatches along the spine.The radio I intend to use is the 2.4GHz Fubata 10C (with receiver), this is to allow subsequent development of the airframe (steerable nosewheel, parachute recovery, etc). As yet still undecided on motor/speed controller, suggestions please (brushless outrunner).It is desirable for the model to have the following capabilities:Autopilot (naturally!)ArduPilot (Pro) appears to be the obvious choice here.Live Visual SystemWhich feeds footage live to the GS. This must also have an OSD. The RangeVideo OSD, with a 900Mhz 500mW transmitter/receiver and DX201 camera is what I am thinking of. A 2-servo gimball device will also be developed for pan and tilt. While RVOSD has RTH autopilot capability, I guess it is far better to not connect it via the receiver (except for the RVOSD Aux config channel) and leave ArduPilot to handle all flight manipulation? This shouldn't adversely affect the OSD?Live Telemetry SystemXBee used in conjunction with ArduPilot appears to be the way to go? My concern here is that I'll either get a frequency conflict with the AVS or Fubata 10C depending on which flavour of XBee is purchased? Is it solvable by just spreading the kit out along the AF?My main areas of confusion and difficulty in specification (apart from frequencies above!) are:BatteriesMost efficient use of the least weight possible, across each of the above systems? Looking for common ground where good batteries can be shared, rather than a battery or two per system.SensorsGPS, X-Y, Z, etc. How many of these can be shared between both ArduPilot and RVOSD? It must be possible, otherwise expensive to have two of everything?Hopefully I've provided enough information for you to help me, if I have missed anything please do shout! Thanks very much indeed for your help and guidance!Kind Regards,R.

You need to be a member of diydrones to add comments!

Join diydrones

Email me when people reply –

Replies

  • 3D Robotics
    You'll have to create a wiring harness to share the FMA sensors with both ArduPilot and RVOSD, but it can be done. But why bother since we have our own ground station that has all the info that RVOSD does? Better to just keep the video downlink plain video, I think.

    BTW, can can't share GPS with an OSD with ArduPilot 2.0-2.1, since that put the GPS in binary mode, but it will be possible with ArduPilot 2.2, out in a few weeks.
  • In the UK the 868Mhz band is the only one close to 900MHz that can be used for telemetry but not from the air. You can use 433MHz for aerial telemetry and this is very useable with a number of manufacturers making modules (try LPRS in the UK).

    2.4GHz can be used for telemetry and video but limited to 10mW power.

    I personally would use 35Mhz for control, 2.4GHz for video and 433MHz for telemetry. Just make sure people are aware you are using 2.4GHz for video and switch your system on first.

    regards Peter
  • Moderator
    I was a cadet and a CI for a while, let me know how I can help.

    But only if your in Somerset and Avon ;-)

    2381 Ilminster
This reply was deleted.

Activity