3689428936?profile=original

 

 

There have been multiple discussions in the threads of various ArduStation posts in the last few weeks about form, function, capabilities both in conjunction with and without a GCS or planner. I have joined in on some of those discussions and what came out of many of them is that we all have different approaches to what we want out of an ArduStation-like component. Some people want a simple mechanism to just decode the LAT/LON, calculate a direction and point the antenna. Some people want it to point the antenna and pass along the data stream via another communication protocol. Still others like having the screen and buttons to tune PIDs, etc. Some wanted the whole enchilada PLUS a touchscreen to do away with the old text screen and buttons...needless to say there was not a lot of consensus - so that got us talking and a modular format became a part of the discussion.

So what I would like to propose is a new project called the ArduStation HUB. A completely modular unit that will allow people to build upon it and add each component they require. So chime in, tell me what you think. Do we even need anything like this? Is my design brilliant? lunacy? Let's crowdsource the design and I wil get them built - if we come up with something truly awesome, perhaps we can get it added to the store.  I know MANY of you have been working on various versions of hardware / software etc.  Can we come up with the modular software to match?

 

E-mail me when people leave their comments –

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

Join diydrones

Comments

  • yes, have an external video receiver outputting composite video into the hub.

    Traditionally the OSD goes in the plane, but I think this just adds weight and complexity, it makes much more sense to overlay it on the ground.

    Perhaps you are right in that it should be an additional module.

    The only problem with having multiple headers and switching between them is that it immediately limits you to the modules you have placed headers for. If you have one set of headers that accepts a carrier board then you can build a carrier board for Xbee and any other different telemetry modules that might want to be supported in the future.

  • @Andy, thanks so much for the offer of help...we will take you up on it, I am sure!  We should start coming up with some nomenclature for the different communication modes between the drone, HUB and GCS.

    @Toby - I agree, we should keep it as radio agnostic as possible, so I am thinking of having multiple headers and a way of selecting between them.

    @Toby & Suayb - So we are talking about having some other (completely separate) radio handle the video reception, then passing the video into the HUB, having the hub parse the data and then handling the overlay and outputting the composite video.  If we are going to go that far, I would say that is an additional "module".  Perhaps we can get HK / Remzibi to work with us on this ground based OSD functionality?  Why would we want VGA out rather than composite?

  • My two cents so far has been to suggest adding a second XBee radio to link back to the GCS.  The tracker can be out in the open, away from structures that block its view of the sky.  It's already tracking the airplane for video, so it will be simple to add a small 900mhz yagi for the Mavlink telemetry stream.  The new platform could scan the Mavlink data for the airplane's gps position and do all the aiming/tracking.  The second radio could likely be either a 2.4ghz XBee or one of the new WiFi XBee's.  Either way, it passes the airplane's telemetry on to the GCS and accepts the GCS commands to be transmitted up to the airplane.

    I've tried some experiments doing this with an Arduino Uno and Ethernet shield, but it probably doesn't have either the memory space or cpu power.  Using the APM board will give this new station enough horsepower to do this an a lot more.

    I'm willing to do Eagle schematic capture as this "committee" comes to agreement on the hardware features.

  • Regarding other radios, i think it should not be limited to XBee. Why not stick with the modular approach and have a 'termial device' type connector that allows an XBee mounted on a terminal board to be added, or you could add any other type of radio, cellphone etc to use for telemtry.


    The OSD idea is also appealing, perhaps a video in connector so you could take a feed from the plane and then you could used the Mavlink data to build a very powerful OSD.

    VGA is expensive, and this might also have appeal for FPV people so I would say composite video inputs and outputs would be fine. Perhaps the video output could also be used for the LCD, then all you need is a method of input and your video out gives you all the configuration, pid tuning etc by going through menus. Then people can add whatever type of LCD screen they like.

    I'm not sure about touch screen and how useful it would actually be in this application.

     

     

  • @Suayb - Are you saying you want to have the unit decode the telemetry data, generate an OSD and overlay that onto a video stream?  Where would the stream come from?  Output to?

    I hadn't really considered the possibility of radios other than XBee for communication to the Drone; but your request for VGA / OSD functionality does raise an interesting point, so I will pose the additional question...Should support for other data links like the 9Xtend radio or the MicroHard radios be included?? 

  • VGA output with OSD.

  • Looks Fantastic. I'll buy one!!! :)

    The Ardustation Hub should have USB on it as well to link to the GSC if thats the way you want to do it (also easier for firmware loads etc), this probably goes in the 'Some other communication' box. If I can help in any way, I'll be happy to lend a hand.

  • Love it. Been going back and forth with the Eagle eyes Antenna Tracker. Why would I also need the OSD stuff in the plane and an extra GPS when it's all already there? Having it all come in via xbee and mavlink is right on.

    I like the modular idea. I would like one that has xbee attached and you can do whatever (pid entry) from the HUB also display plane info, lat lon, speed, alt ect.., but if you prefer to use the PC, then be able to disable the input part (still keep the plane data on display) and send all the mavlink info down USB to the pc.. just as if it were just an xbee attached.

    This I feel would be the best of all worlds.

  • Modular is the way to go... IMHO

     

This reply was deleted.