Developer Comment by Mark Colwell on July 24, 2012 at 9:53am

With this release what Android device to buy? My G1 is really out of date. Too many choices.

Wiki Ninja Comment by Gent Armedo on July 24, 2012 at 10:23am

Good job! Next step is to buy a tablet and a 3DR radio. Whew! This getting real expensive, lol. I would like to try this on my APM 1.4 equipped Skywalker. BTW, data and telemetry are just dependent on the range of the 3DR radio? Correct me if I'm wrong. 

Comment by Jack Crossfire on July 24, 2012 at 2:06pm

It's definitely the kind of thing that's good at getting a job.  It just seems a bit slow & the screen took a few tries before it took the input.  Is that the browser update rate or the protocol?

Comment by John Wiseman on July 24, 2012 at 2:41pm

The update rate is currently 4 Hz, and I haven't experimented yet with other values.  This doesn't seem like something that needs to run particularly fast, though I think it could probably approach 30-60 Hz with some tweaking (maybe not on an iPhone).

The protocol is HTTP, so some people probably consider it lightweight and others consider it heavyweight, but I'm sure it can handle an update rate of more than 4 Hz.  If higher update rates are desired it would be easy to use the WebSocket protocol with its much lower overhead.

As far as touch input performance goes, I expect it does suffer from being an HTML app vs. a native app, in the same way that Facebook's current HTML-based app sometimes feels pokey.  This may be an unavoidable price to pay in the portable HTML vs. less portable native app tradeoff.

Developer Comment by Pat Hickey on July 24, 2012 at 3:33pm

I'm not sure why I had to double-tap on the screen twice to get that first waypoint to work, but occasionally the  double-tap detection does fail- its not perfect yet, and I hope we can improve it. I'm still learning JavaScript as I go along, so I've probably made some mistakes.

We can probably experiment with bumping the HUD datarate to the full 10hz it is sent over Mavlink at. Right now the individual HTTP requests take about 4 to 6ms roundtrip, so we might not be able to sustain more than 10hz without changing the incoming mavlink stream to work over websockets.

Comment by Delfin Magote III on July 24, 2012 at 7:08pm

Cool. Probably more lightweight than Mission Planner GCS. If it is possible to connect an Android tablet to a serial connection of an Xbee/3DR/RFD900 radio, Is it possible that the server is the Android tablet?  

Comment by John Wiseman on July 24, 2012 at 7:32pm

Delfin, that should be possible.  FYI Zachary Eldridge is already developing a serial connector and nativ... (I am concerned about the difficulty of getting Apple MFI approval, though I would love being shown that's my pessimism is unfounded).

Comment by Delfin Magote III on July 25, 2012 at 5:00am

I'm actually following his post. My target actually is to create a single Arduino server that can receive multiple inputs and transmit outputs to different gadgets through serial connection, here is my post to clarify my idea.

What I'm asking, is if Marvelous/MAVproxy server be an Android tablet instead of a computer since python can be ported to android. The GCS is exactly the same, front-end browser, but the server is running in Android.

I forgot to be specific in my first post. :)

Still, the GCS you've made is awesome, multiple input multiple output. Will be using it as soon as the APM2 and RFD900 arrives. :)

Comment by John Wiseman on July 25, 2012 at 9:03am

Yes, as I said, it should be possible.  The server code is python so as long as you can run that on your phone/tablet/whatever you're good.

Comment by steve F11music.com on July 25, 2012 at 1:40pm

OK this is my first time with GIT so bear with me. I just installed GIT, clicked on 'download this repository as a zip file', then unzipped that and ran mavproxy.py which opened up terminal and went into what I guess is mavproxy. The prompt in terminal looks like this.

Steves-MacBook-Pro-17:wiseman-mavelous-e94a6d7 steve$

When I try to do anything from there, I get errors. I read the instructions that talk about setting the baud rate and starting the browser session but I'm stuck at how to do that because the prompts in the instructions look different than mine or am I suppose to set the serial port first?

$ python mavproxy.py --baud=57600

Comment

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