MultiWii

mahowik wrote:I suppose this solution will work viewtopic.php?f=8&t=649&p=32028#p32028

i.e. Android device+BT <==air==> BT_module<-->uart<-->long range modem (like 3DR roborics) <==air==> 3DR modem<-->uart<-->copter

juanquy wrote:YAY!!!!!!! do you already bought the OTG cable ? I think I have 2 or 3 here in my cave.

ezio wrote:

juanquy wrote:YAY!!!!!!! do you already bought the OTG cable ? I think I have 2 or 3 here in my cave.

Yes I ordered it. I have Samsung galaxy tab 2 and it has a stupid 30 pin connector instead of USB micro.

nhadrian wrote:Hi,

it looks like FTDI has support for USB ftdi devices!!!
http://www.ftdichip.com/Android.htm

Bart, what do you think about using FTDI UART/TTL for general MWI connection? (could be used for either 3DR modules, direct cable connection, XBEE or any other UART/TTL compatible methods...)
And I think many of us already have an USB FTDI mobule around.

This FTDI solution can be used for any android devices with USB HOST mode support.

BR
Adrian

ezio wrote:
Yes, yesterday I started to research about this subject.
When I receive my cable I'll try to implement it.

And for now there will be no tablet layout.
It is easy to say but hard to do.
Maybe in the future I will make one layout with everything on the screen.

Bart

juanquy wrote:Here is a link "Supporting Multiple Screen"
http://developer.android.com/guide/prac ... pport.html
and I love the actual GUI.

flyrobot wrote:Hi Ezio,

This app make me buy new android phone, i really love this app, i thank to you for your great job.

If you can port this app to IOS iPAD/iphone, i might the first person buy the app.

John (wahyu)

klaudius666 wrote:Hi. And thanks for this android software.

Is EZ GUI supporting the new Multiwii 2.2 release ?

flyrobot wrote:I have several DIY multirotor even DJi and MK, But from all, I like MWI (the most active forum and stable), Autoquad (the most accurate platform) and APM2.5 (arduino base and many features), last two using mavlink, but no from them has app as good as yours.

So, I think it will be more stronger if this app can have mavlink, so all three multirotor can use this app.

Thanks,

John

flyrobot wrote:Hi Ezio,

I understand the effort is not easy, i hope more android coder willing to support develop this app. do you have plan to make this app support mavlink? and maybe you make two version of this app, paid version with mavlink (compatible with MWI, autoquad and APM) and opensource version just for MWI.

Thanks,

John

ezio wrote:Maybe someone know what units are uses in vario?

nhadrian wrote:

ezio wrote:Maybe someone know what units are uses in vario?

Hi, cm/s is the unit for vario.

I think a ymall indicator would be even more useful like print out the number.
Ie. a circle when vario is 0 (between +-5 cm/s for deadband), and draw an arrow over or under the circle if rising/descending.
Could be even put on map view...

BR
Adrian

copterrichie wrote:Ok, you win!! lol

Are you going to add Wifi/TCP/IP support?

ezio wrote:

nhadrian wrote:

ezio wrote:Maybe someone know what units are uses in vario?

Hi, cm/s is the unit for vario.

I think a ymall indicator would be even more useful like print out the number.
Ie. a circle when vario is 0 (between +-5 cm/s for deadband), and draw an arrow over or under the circle if rising/descending.
Could be even put on map view...

BR
Adrian

Hi
I'm cooking something new. New Dashboard.
But I have another project going so you will have to wait for it.
Here is a sneak peek.

device-2013-03-23-042039.png

Nicksdesign wrote:However, please check the pitch data handling. Dashboard 1 showed -17* and Dashboard 2 showed -1*. My quad was sitting level at the time. Saddly, Dash 1 was what the FC thought was correct: bad crash.

Nick

Nicksdesign wrote:Ezio, my apologies for my bad information in my last post. I have re-looked, today, at both dashboard screens and both are consistent and appear correct.

But, I think the reason I was reading the display wrong is because that data labels are closer to the wrong value than they are to the correct value. For example, the Pitch label is closer to the roll value than it is to the pitch value and this leads me to automatically associate the Pitch label to the roll value even when I know the correct association. Any time I look briefly at the screen, I'm associating the label to the wrong value. Next time you are editing the Dashboard 2 code, consider increasing the spacing so the data label is closer to its data than the other label is.

That said, I really like the application and appreciate all of your hard work.

Nick

Watz wrote:...

Also PIDs send by eMail is not working for me,
have a Mail send but no PIDs inside,
but thats no real problem for me.

... and No, I have not forgotten to switch them on .

jrt4fun wrote:Ezio,

Good news to hear that the serial USB is working.
Just received my Crius AIO with GPS and ready to hook up the 3DR radio.
I'll be happy to test it.

Regards

Watz wrote:... even with the new update

I have the issue with the graph-en display.
The only graph I can still see is the z-axis from the ACC.

Am I the ony one?

It was working sone weeks ago ....

ezio wrote:I have just posted new version. should be available from google play in few hours.
Main change is USB Serial port support.
*Only FTDI chips are supported.
*No root required.
*Android version greater or equal to 3.1 (it will not work on 2.2, 2.3 etc (froyo))
*You have to have USB host and USB OTG cable.
Settings are in config.
I tested it on Samsung Galaxy Tab 2 and it works very good. and it is much faster then Bluetooth.
Application should automatically start when you plug your FTDI device in.

For those who can't (or don't have google play) wait here is the link: https://dl.dropbox.com/u/80566205/MultiWiiEZGUI.apk

Bart

scrat wrote:

ezio wrote:I have just posted new version. should be available from google play in few hours.
Main change is USB Serial port support.
*Only FTDI chips are supported.
*No root required.
*Android version greater or equal to 3.1 (it will not work on 2.2, 2.3 etc (froyo))
*You have to have USB host and USB OTG cable.
Settings are in config.
I tested it on Samsung Galaxy Tab 2 and it works very good. and it is much faster then Bluetooth.
Application should automatically start when you plug your FTDI device in.

For those who can't (or don't have google play) wait here is the link: https://dl.dropbox.com/u/80566205/MultiWiiEZGUI.apk

Bart

But latest version works fine just with bluetooth on all 2.x+ Android?