This project currently is in draft status. I will update the article on my homepage, as it progresses.

Normal R/C transmitters are not the best way to control a UxV. For instance, they usually require additional components like ArduStation for the ArduPilot project, which means, the operator has to start juggling already with 2 components. Depending on mission and payload, there easily might be 1 or 2 more systems added. Based on this idea, I started thinking about a UxV controller which at least inconporates the R/C transmitter and the mission control component.

The R/C TX component is based on modules. I am planning to use the FrSky DHT module which is especially for integration in user projects. Another possible option would be to cut a matching rectangular hole into the UxV-CS' enclosure e.g. for JR compatible modules. The main board could be taken from a cheap chinese radio, e.g. the Turnigy 9x, but I am planning for the ERSKY9x board. The ERSKY9x board is a third party board which was developed as an improved replacement board for the 9x radios. It features a much more powerful CPU and runs Open9x firmware.

Instead of the usual R/C-joysticks, the UxV-CS will have 3-axis joysticks which pushbuttons. Additionally, a linear slide potentiometer and several switches are planned on the TX side.

The mission control component will be based on an Arduino Mega 2560 with a 40x4 character LC-display. The Arduino will feature  "softbuttons" with changing functions as well as a 4x4 matrix keyboard for data entry. Those will be complemented by mission-related switches and an external joystick module for camera operations. Also, a mini thermal printer will be integrated e.g. for adhoc printing of GPS coordinates in SAR missions. For communications, the 3DR 433MHz modules are planned.

Update 07JAN13, 1610UTC:
- Corrected some typos
- Updated link to project page
- Added reference to 3DR radio modules

Views: 903

Comment by Jean on January 5, 2013 at 6:29pm

What is a UxV?

Comment by Stefan Gofferje on January 5, 2013 at 6:33pm

An arbitrary unmanned vehicle.

UAV = air, UGV = ground, USV = (water) surface, ...

=> UxV = any of those

Comment by Jean on January 5, 2013 at 6:54pm

Ah, of course.  Thank you.  I just haven't seen that term used before.

Comment by Chinlin on January 5, 2013 at 7:22pm

very interested project draft.

when will you plan to make it more complete and implement it?

Comment by Stefan Gofferje on January 5, 2013 at 7:49pm

At the moment, I'm working on the idea every evening a bit. I'm not yet totally happy with the layout and I might kick the 4x40 out in favor of a 4,3" graphic LCD. I'm playing a lot with ideas.

But I'm about to order the FrSky tx module and an RX to start tinkering with the telemetry. I think, I'll order the enclosure also soon. I find it easier to think about the layout if I have the physical box on my desk.

I'd also be interested in some feedback, criticism or ideas.

Comment by Oyvind Amundsen on January 6, 2013 at 4:53am
Comment by Stefan Gofferje on January 6, 2013 at 5:12am

If you read my text and look closely at the concept drawing, you will find that the whole point is to integrate the R/C TX and the mission control system (and maybe more) into a single unit and that my draft includes functionality which is provided by neither ArduStation variant.


JDrones
Comment by Jani Hirvinen on January 6, 2013 at 8:26am

Stefan, ASM actually can be rather easily modified to use joysticks etc. I have been thinking to do system similar what you are working on. 

Basically you can even run er9x software on ASM board as they both uses same cpu and graphical units. Gruvin9x is new replacement board for Turnigy radios that will do most of what you plan. It also runs er9x software inside. This software have already full support for ArduPilot and MAVLink.

Comment by Stefan Gofferje on January 6, 2013 at 8:50am

Jani, tiedän, tiedän :).

But I chose the ERSKY9x board for several reasons: It runs an ARM Cortex architecture CPU, which is substantially more powerful than an ATMega. The ERSKY9x board has options for supplemental hardware, like LCDs which are also sold by the team, so I don't have to buy another 9x radio and rip it apart, just to get the display and other hardware. Additionally, I don't want to use MAVlink for primary flight control because of lag-issues and range, so just connecting joysticks to a GCS is no option for me (if I wanted this, I could use the laptop/joystick variant with the Windows GCS). I also don't want to start writing the software for just basic flight controls when anyways a TX is needed and a TX does this job substantially better.

I chose Open9x over er9x because of the feature set and because even the er9x developers recommend Open9x now.

The ArduPilot and MAVlink support in er9x/Open9x is pretty rudimentary. You can set the mode and display MAVlink telemetry on the relatively tiny TX-display.. That's not what I want.

I want a full featured integrated mission control system which can do much more than just switch the mode or display some telemetry on the mission control side.

Comment by Markus Järve on January 6, 2013 at 10:59am

Exactly what I have been working on and missing. Also way better. really awesome!

Comment

You need to be a member of DIY Drones to add comments!

Join DIY Drones

© 2014   Created by Chris Anderson.   Powered by

Badges  |  Report an Issue  |  Terms of Service