3689352689?profile=original



LabVIEW based ArduPilot Ground Control Station ( GCS) is ready for public beta test.

GCS wiki
: See wiki for installation and configuration instructions (read through it, or at least watch video )

Requirements:

- Windows OS
- LabVIEW run time engine 9.0
- Google Earth ( if you already have it you don't have to re-install it. Google Earth version prior to 5.1 ( newest) should be fine)


- Ground Control Station application (zip file) - Updated May 16, 2010 !


Optional: Code for GCS can be found here ( you will need LabVIEW 8.6 or higher)

New Features of ArduPilot GCS :
  • Data logging
  • kml logging
  • voice synthesis
  • (UI has been redesigned, code architecture has been changed, etc.)

Short introduction video explaining how to start and stop GCS:

http://vimeo.com/11772440



more comprehensive GCS video ( worth watching ! ) is here:

http://vimeo.com/11608873

E-mail me when people leave their comments –

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

Join diydrones

Comments

  • I am having the following probelms with Beta2:
    1. Everyhting is connected and I can see data coming through to the top of the debug window and the data seeme to be valid.
    2. The data file that is produced does not include all the data that I saw and seesm to stop after a period of time.
    3. Whilst GE starts it does not seem to be connected to the GCS as it stays at position 0Long, 0Lat although I can see correct lat and long data in the debug valid data.
    4. I get no messages as to the flightswtich position although again I can see the data go by in the debug window.

    I am using a dell Laptop and Win 7.

    Any suggestions
    ps It did work once correctly for a short period
  • Developer
    The video (sorry):

    http://vimeo.com/11794002

    Dario.
  • Developer
    Hi guys,
    This afternoon I tried to run the GCS. You can see the result in this video:


    My netbook (Aspire One) has a 1024x600 resolution so I can not view all the parameters. Please resize for me!! :) Other question....I live near the mountains and the field altitude is high. You can see in video that the altitude counter finish in 200 meter...I think that this counter shows the altitude refer to ground,is it right? How can I do for view the relative altitude instead of absolute?

    Thanks for this nice work Automatik.

    Regards,
    Dario
  • Automatik, it was silly mistake at my end, otherwise it is perfect;
  • Grand Automatik,

    Congratulations her GCS was wonderful and the delay is resolved.
    You the man!
  • Hi leonardo,
    glad to hear it !

    Here is the video showing data responsiveness of GCS - i.e no latency...you can see interaction with thrmopiles, throttle, mode switch... Beta 2 code was used in the video

  • Hi Automatik,

    I did another test today (now a flying test) and everything worked perfectly. Congratulations for the great job.

    Cheers,
    Leonardo
  • Automatik...the fly to speed setting is under the navigation tab :)
  • Hi Rana,
    form the above video I see that GE is slow to "zoom", but I think that's because of your GE setting, i.e nothing to do with GCS, communication with ArduPilot.

    See wiki: http://code.google.com/p/ardupilotgcs/wiki/GoogleEarth
    In GE go to Tools>Options Click on Touring" tab and find "Fly-to Speed" setting ( my suggestion would be to set it half or three quarter way of the full speed.

    Also by looking at the video, I don't think that you powered up ArduPilot ( or other auto pilot ). I can see that you cliked to connect on Com6 @ 19200 and that GCS took that setting ok ( I can see "GCS Port Set") message on the video) - that means so far so good , no problems. next step is to power up AP ( or make sure that's right port for AP, but either way you have GCS listening on com 6, and waiting for AP to connect)


    Thanks for testing

  • I released another build of GCS


    go to http://code.google.com/p/ardupilotgcs/downloads/list and download latest application ( Beta 2)

    Items addressed:

    - screen sizing: hopefully this is resolved now - it should work fine with monitors having resolution of 1024x768 or grater

    - data latency: under some circumstances data was displayed with significant lag, although it was read and logged as it came in ( I didn't change some delay values used for debugging...). Now you should see data near instantaneously
This reply was deleted.