3D Robotics Comment by Chris Anderson on February 28, 2011 at 10:26am

This is incredibly impressive. I'd encourage everyone to watch this video--this is the state-of-the-art in GCSs. I've seen plenty of pro-level ones, and nothing comes close. Plus it's cross-platform (Windows/Mac). My hat's off to the team! 

Comment by pixhawk on February 28, 2011 at 10:31am

Thank you very much! One small note on Linux support: If you change Google Earth against osgEarth it works also on Linux ;-). We have almost finished debian packages for Debian / Ubuntu, compiling from source works of course by now:

 

http://qgroundcontrol.org/dev/start

Comment by CyborgCNC on February 28, 2011 at 10:50am

VERY nice work!!  Thank you for all the hardwork.  I see on the list of autopilots supported, is UAV, any chance this also supports UAVX? (http://code.google.com/p/uavp-mods/)

By the way, the hyperlink on the page for the UAV board, needs an "h" in front :-)  This is the way it is posted now...

"ttp://code.google.com/p/gentlenav/wiki/MatrixPilot" Resulting in an error off course.

Comment by pixhawk on February 28, 2011 at 10:55am

Thanks! I've also fixed the broken link.

 

About UAVP support: MAVLink has been written to be easy to integrate and there is a tutorial on it. A few function calls and you can use QGC for UAVP:

http://qgroundcontrol.org/dev/mavlink_onboard_integration_tutorial

Comment by Krokodil on February 28, 2011 at 11:02am

A marvelous piece of software. Very nice.

Two small things I have noticed:
If I select "Main -> Google earth" I get a javascript error: "console is undefined" (but the map works).
If I make the application fullscreen and change perspective, it goes back to default. Maybe there is a though behind this, but can we set it to be fullscreen once selected?
I have searched the menues but have not been able to find a setting for this.

Comment by pixhawk on February 28, 2011 at 11:04am

The console error is because I removed a debugging helper javascript file, but not the call to it - sorry, will fix that ASAP. As its just printing output, it won't affect the operation though. The fullscreen issue is because QGC initially remembered the layout for each view, but this is not that intuitive. We will change that.

Comment by Christof Schmid on February 28, 2011 at 11:12am

Congratulations, thats awsome. I like the part with view on Bürkliplatz a lot.

 

Christof

Comment by Krokodil on February 28, 2011 at 1:17pm

Is there plans for a map widget? I have not found one in the widget menu. If i´m in pilot perspective, i have to choose between map or hud in the main view. 

I can have the map in the main view have a video widget open, but I can not select to have the hud in main view and have a map widget open.  

Also, I can´t see the live view from my camera. It is connected and works in other applications, but not QGC. 
I´m only using the simulation, maybe the camera does not work then. Or how do I enable the camera? I have selected "Enable Video live feed" in the hud. 

Comment by pixhawk on February 28, 2011 at 1:20pm

You can have a HUD in the widget menu, so you can have the map as main widget and the HUD on the sidebar.

 

The video interface is currently digital only (streamed via Wifi from the MAV). I'm working on supporting video for windows, but this is still work in progress. I'll announce it once its there, shouldn't be too hard though, because its just a matter of including some Microsoft Video for Windows widgets.

Comment by Phil Cole on February 28, 2011 at 6:37pm

I connected QCG to an APM running the 2.0 trunk code (updated on Sat evening Feb 26). I used the windows binary referred to above. It installed without any issues. I had the same issues as above with Google Earth and video display.

 

On starting the connection all I received at QCG were heartbeat messages. How do I get the APM MAV to send all that good data that it's just waiting to send? Starting up the widgets (HUD, flight instruments, raw RC display) didn't seem to invoke the data they would consume. I couldn't find any buttons to push to get things to happen.

 

The parameter widget did fetch the names and values from the APM and display them. I didn't try setting any of them, or exhaustively check that the recovered data was correct. The displayed data did seem generally sensible.

 

I was able to get the widgets to display the data by using the APM planner to send the data requests and then swapping over to QCG while leaving the APM running. After that I had the HUD and flight instruments responding to APM attitude, maps following the GPS location and the RC displays following my RC Tx output.

 

I also tried reading waypoints that I programmed into the APM. QCG seemed to know how many there were, but I couldn't tell whether I was getting the actual waypoint data. I sort of expected the markers to appear on the map but that didn't happen. I didn't try setting and programming the way points.

Comment

• ‹ Previous
• 1
• 2
• Next ›
• Page