MultiWii EZ-GUI

Leo · Post by **Leo** » Tue Jan 06, 2015 5:58 pm

ezio wrote:this means that your data connection doesn't work any more.
In example you are out of range of your telemetry system.

Thanks eizo. It helped me to narrow it down... BTW, the error happens even if I have the Radio's 2 meters apart.
One thing I did find and repaired was a broken wire within the USB OTG cable. I will have to continue to investigate...

Leo · Post by **Leo** » Tue Jan 06, 2015 6:42 pm

Today was a thrilling, frustrating and sad day to fly.....

I did several mission flights using EZ-GUI. The frustrating part was that RTH wouldn't engage until it reached the proper altitude. This happened a couple of days ago. So today I set

Code: Select all

//Wait to reach RTH alt before start moving to home (0-no, 1-yes)
#define WAIT_FOR_RTH_ALT           0         //(**)

and uploaded it to the controller.
Unfortunately that didn't solve the problem, which surprised me.
Then after going through EZ-GUI I stumbled on the the menu "Nav Settings" and saw the "Wait to reach RTH alt." was active even so it was set to "0" in the firmware. I think there is a code error in EZ-GUI because the firmware settings should have highest priority.
After I unchecked it in EZ-GUI RTH worked without waiting for alt to be reached. Eizo, you might want to check all the options in Nav Settings and compare them to hard coded firmware settings.

One other thing that is very annoying is when setting up missions in the mission planner every step I take I get "Protocol, Navigation is not supported by your flight controller". Please get rid of that message as I do all missions without the QC connected. I then upload each mission when I'm on the field.
Also, you spelled supported wrong, it's missing a "u"

Well, the sad part is I won't be doing any more testing until I get new parts for my QC. Yes, I knew I had very little battery power left and I knew it was very cold (3°C) but when a lady comes by you want to impress... :lol:

It didn't take 20 seconds and my QC fell from 15 meters to the ground :cry:

Only me to blame!! :evil:

ezio · Post by **ezio** » Tue Jan 06, 2015 11:11 pm

Thank you for testing and feedback it helps a lot.

Leo wrote:Today was a thrilling, frustrating and sad day to fly.....

I did several mission flights using EZ-GUI. The frustrating part was that RTH wouldn't engage until it reached the proper altitude. This happened a couple of days ago. So today I set
Code: Select all
//Wait to reach RTH alt before start moving to home (0-no, 1-yes)
#define WAIT_FOR_RTH_ALT           0         //(**)
and uploaded it to the controller.
Unfortunately that didn't solve the problem, which surprised me.
Then after going through EZ-GUI I stumbled on the the menu "Nav Settings" and saw the "Wait to reach RTH alt." was active even so it was set to "0" in the firmware. I think there is a code error in EZ-GUI because the firmware settings should have highest priority.
After I unchecked it in EZ-GUI RTH worked without waiting for alt to be reached. Eizo, you might want to check all the options in Nav Settings and compare them to hard coded firmware settings.

EZ-GUI reads and displays what the FC gives. I don't have a possibility to read the hard coded settings. But I think that the #define WAIT_FOR_RTH_ALT is for normal return to home activated by a switch in the RC transmitter and not by the mission.

One other thing that is very annoying is when setting up missions in the mission planner every step I take I get "Protocol, Navigation is not supported by your flight controller". Please get rid of that message as I do all missions without the QC connected. I then upload each mission when I'm on the field.
Also, you spelled supported wrong, it's missing a "u"

Good point. It will be removed.

Dave Pitman · Post by **Dave Pitman** » Wed Jan 07, 2015 2:31 am

ezio wrote:
Dave Pitman wrote:Hi Guys,

On an Acro Naze32 clone running Cleanflight, I was able to connect to the board, but no data read. I'm using a Nexus 4, Android 4.4.4
This bluetooth board http://witespyquad.gostorego.com/accessories/serial-bluetooth-module-for-multiwiicopter-configuration.html

Any suggestions?

Thanks.

-swapped Rx and Tx
-baud rate in cleanflight not the same as set in BT
-faulty BT module

The app connects to the board, but will not connect if I reverse the Rx and Tx wires, so they must be ok.
The vendor claims the baud rate is 115200 which is what Cleanflight is set to. But I don't know of a way to confirm.
No way to know if the BT module is bad. I don't have anything else to hook it up to.

Perhaps you are aware of some app that can simply verify a connection with a bluetooth device? Or, a link to a BT module that is known to work with your app?

Thanks for the support!

rubadub · Post by **rubadub** » Thu Jan 08, 2015 2:39 am

the app just auto-updated on my phone, and the latest version has re-enabled some sounds, such as the "started" voice alert, even though I have all sounds disabled in the app settings. Can this please be taken a look at?

Also, the 'back button' / multi-instance behavior is driving me insane, and makes working with the app a real hassle. Can something please be done to disable multiple instances from being launched. I.e., accessing the app from the launcher icon, status message in notification area, 'recent apps' window in android, etc., should all take you back to your last window/position within the app, instead of launching a new,separate instance & leaving 'hanging' instances in the background (seems like they might be eating up resources as well)...

ezio · Post by **ezio** » Thu Jan 08, 2015 7:57 am

rubadub wrote:the app just auto-updated on my phone, and the latest version has re-enabled some sounds, such as the "started" voice alert, even though I have all sounds disabled in the app settings. Can this please be taken a look at?

Also, the 'back button' / multi-instance behavior is driving me insane, and makes working with the app a real hassle. Can something please be done to disable multiple instances from being launched. I.e., accessing the app from the launcher icon, status message in notification area, 'recent apps' window in android, etc., should all take you back to your last window/position within the app, instead of launching a new,separate instance & leaving 'hanging' instances in the background (seems like they might be eating up resources as well)...

Nothing has been changed in the sounds settings. Disable text to speech to avoid "started"

You are right. The app reacts not very well when you switch through the other apps while it is connected to FC. It will be fixed at some point but it is not a quick fix.

rubadub · Post by **rubadub** » Fri Jan 09, 2015 12:11 am

ezio wrote:Nothing has been changed in the sounds settings. Disable text to speech to avoid "started"

I just tested it again. I made sure 'text to speech' was disabled, but the 'started' voice alert is still enabled. I even tried enabling 'text to speech', restarting the app, and then disabling it again. Same behavior, the 'started' message is still sounding.

Leo · Post by **Leo** » Fri Jan 16, 2015 5:54 pm

Ok, so I have had this problem for quite some time.

I randomly get "No data received" in EZ-GUI.

It just happened again right after I started the program EZ-GUI. I then disconnected the power from the QC and reconnected. Then I reconnected in EZ-GUI. Same issue.... I got no data received errors.
I then left my QC under power and only did a reconnect or restarted EZ-GUI, I don't remember, and the no data received error was gone.

Example:

This happens randomly! E.g. on my last flight the connection was working fine until the QC was in RTH mode. Then I got the errors. Sometimes it happens at the start or in the middle of a flight.

I have purchased new 3DR modules with the same effect. I also tried many 3DR firmware versions and settings. I don' think It's a radio problem.

I need some help as it is very frustrating.

rubadub · Post by **rubadub** » Sat Jan 17, 2015 11:21 am

It seems that the app just auto-updated again, but I'm still hearing the stupid 'started' voice alert even though I've disabled voice alerts. can this please be looked into?

Also, again, I'm begging, please fix the multi-instance problem with the app. It seems like it keeps hogging up resources and hanging the phone (battery heats up greatly too) due to the fact that it seems to launch multiple instances in the background. If this isn't the problem, then can something please be looked into to lighten up resource usage? perhaps add a 'lightweight config' mode that's only used for sending parameters back&forth, checking GPS status, check AUX switches, etc. (i.e., no need to constantly process every single variable in the background). Could this please be considered as an option?

ezio · Post by **ezio** » Tue Jan 20, 2015 4:18 am

Leo wrote:Ok, so I have had this problem for quite some time.

I randomly get "No data received" in EZ-GUI.

It just happened again right after I started the program EZ-GUI. I then disconnected the power from the QC and reconnected. Then I reconnected in EZ-GUI. Same issue.... I got no data received errors.
I then left my QC under power and only did a reconnect or restarted EZ-GUI, I don't remember, and the no data received error was gone.

Example:

This happens randomly! E.g. on my last flight the connection was working fine until the QC was in RTH mode. Then I got the errors. Sometimes it happens at the start or in the middle of a flight.

I have purchased new 3DR modules with the same effect. I also tried many 3DR firmware versions and settings. I don' think It's a radio problem.

I need some help as it is very frustrating.

Hi
I'm using 3dr radio for a while now and never had this problem.
maybe you can increase the refresh rate in settings to ie 200
maybe this will help
Right now I have no idea how to solve this.

scanman · Post by **scanman** » Wed Jan 21, 2015 10:39 am

Tried it on a naze32 flight controller on Afro Mini, works really well except the "Manual control" had no effect.
NOTE: when using with afro mini and Naze32, there is no setting for VEL PID in this app so it gets set to 0 every time you save pid values. this means your baro hold is disabled on naze32. All other settings work fine with Naze.

Exidous · Post by **Exidous** » Wed Jan 21, 2015 11:10 am

Dave Pitman wrote:
ezio wrote:
Dave Pitman wrote:Hi Guys,

On an Acro Naze32 clone running Cleanflight, I was able to connect to the board, but no data read. I'm using a Nexus 4, Android 4.4.4
This bluetooth board http://witespyquad.gostorego.com/accessories/serial-bluetooth-module-for-multiwiicopter-configuration.html

Any suggestions?

Thanks.

-swapped Rx and Tx
-baud rate in cleanflight not the same as set in BT
-faulty BT module

The app connects to the board, but will not connect if I reverse the Rx and Tx wires, so they must be ok.
The vendor claims the baud rate is 115200 which is what Cleanflight is set to. But I don't know of a way to confirm.
No way to know if the BT module is bad. I don't have anything else to hook it up to.

Perhaps you are aware of some app that can simply verify a connection with a bluetooth device? Or, a link to a BT module that is known to work with your app?

Thanks for the support!

You may need to redo the settings in the BT module. I use the witespy module and had to add:

AT+ENABLEIND0

This disables indicators. As soon as it did this it started working perfectly.

AT+BAUD8

BAUD8=115.2K
BAUD5=19.2K
BAUD4=9.6K

http://www.hobbytronics.co.uk/bluetooth-module

There is a link on this page to HT Comm program, It works ver well. You must use an FTDI to program the BT Dongle. To verify HTComm is talking to the board, Type AT in caps. It should respond OK. Typing save not required.

There is a way to know if the BT module is bad. Connect the dongles RX to its own TX. Using a computer with BT run the HT comm program. Anything you type shoud show up in the box below. This means what you type is traveling via RF to the BT through the RX/TX pins back over RF to the HT Comm programm. This is known as a loopback test.

On another issue:
Random data losses but normally connected usually means packet errors. Either from being too far away or interference or the datarate is too high. Try a lower rate like 57.6K.

ducminhkt · Post by **ducminhkt** » Thu Jan 22, 2015 9:54 am

I click button "Model control" in Config -> Advanced and receive message "Your Android version is to old". What's the problem ?
I'm using android version 2.3.5

Leo · Post by **Leo** » Sun Jan 25, 2015 9:17 am

If you have a new unused FC (without a mission uploaded) and try to download a mission from eeprom the GUI will "crash".

miztic · Post by **miztic** » Tue Jan 27, 2015 7:35 pm

I'm a little premature because I'm still building my quad

But I was thinking about the follow-me feature, you can already use the ez-gui to send the model to a certain gps coordinate correct?
A follow-me feature would just do it continuously:

When follow-me button is hit:
take device/tablet/phone current location and model gps location and compute the difference, let's call this Offset.

then every 0.5-1 second, send the model an updated destination calculated via device current location + Offset.
and send it a POI [point of interest] of the device gps coordinate, so the model will always be looking at you.

I was thinking about implementing this myself, for fun [that's probably at least 2 months away because I need to get my quad flying first], but your software is so far ahead, it might be really easy for you to do.

Nice work.

ldonnay · Post by **ldonnay** » Tue Jan 27, 2015 10:11 pm

Ezio,
I am flying a naze32 with Cleanflight and a Bluetooth adapter. Connexion and reading of settings through EZ GUI works perfect.
I have an issue when updating settings (actually PIDs).
After updating the settings (P in rate mode), Alt Hold, which was running fine before, is not stable anymore.

I compared the cli dump output from before and after pid tuning through Bluetooth and EZ GUI and I found
set p_vel = 120
set i_vel = 45
set d_vel = 1
has become
set p_vel = 0
set i_vel = 0
set d_vel = 0
defaults resets it.

This only happens when tuning using multiwii EZ-GUI and MultiWii Configurator over bluetooth. A direct connection to my pc running Chrome Cleanflight leaves these values at default.
Looking at multiwii EZ-GUI and MultiWii Configurator on android there is no section in PID for velocity but there is in Cleanflight on the pc so I can only assume when the pids are sent via android a 0's value is sent for vel.

Does anybody else have problems with altitude hold or is it only me?

ezio · Post by **ezio** » Tue Jan 27, 2015 10:21 pm

miztic wrote:I'm a little premature because I'm still building my quad

But I was thinking about the follow-me feature, you can already use the ez-gui to send the model to a certain gps coordinate correct?
A follow-me feature would just do it continuously:

When follow-me button is hit:
take device/tablet/phone current location and model gps location and compute the difference, let's call this Offset.

then every 0.5-1 second, send the model an updated destination calculated via device current location + Offset.
and send it a POI [point of interest] of the device gps coordinate, so the model will always be looking at you.

I was thinking about implementing this myself, for fun [that's probably at least 2 months away because I need to get my quad flying first], but your software is so far ahead, it might be really easy for you to do.

Nice work.

Follow me is there for the ages.
It is in Advanced section. If you have MAG and follow me enabled at the same time the model will follow you pointing in the flight direction ( which is equal to looking at you) if the MAG is off the model will follow you without rotating to the flight direction.

FedorCommander · Post by **FedorCommander** » Wed Jan 28, 2015 12:14 am

Hi there!

Does it work over usb on 4.4.2 ???? Cant get this thing working over USB.

After installation it was crashing with Invalid BT!!!! address in the stack trace.... Ok. I made fake connection to some BT device, just to get some address valid... Then I switched back to serial usb.... Well, it stopped crashing!!!

Then it just cannot connect to naze32 at all!!!

Any ideas?

Thanks!

ezio · Post by **ezio** » Wed Jan 28, 2015 2:46 am

ldonnay wrote:Ezio,
I am flying a naze32 with Cleanflight and a Bluetooth adapter. Connexion and reading of settings through EZ GUI works perfect.
I have an issue when updating settings (actually PIDs).
After updating the settings (P in rate mode), Alt Hold, which was running fine before, is not stable anymore.

I compared the cli dump output from before and after pid tuning through Bluetooth and EZ GUI and I found
set p_vel = 120
set i_vel = 45
set d_vel = 1
has become
set p_vel = 0
set i_vel = 0
set d_vel = 0
defaults resets it.

This only happens when tuning using multiwii EZ-GUI and MultiWii Configurator over bluetooth. A direct connection to my pc running Chrome Cleanflight leaves these values at default.
Looking at multiwii EZ-GUI and MultiWii Configurator on android there is no section in PID for velocity but there is in Cleanflight on the pc so I can only assume when the pids are sent via android a 0's value is sent for vel.

Does anybody else have problems with altitude hold or is it only me?

Have you set the firmware version to Cleanflight in the EZ-GUI Settings ?

ezio · Post by **ezio** » Wed Jan 28, 2015 2:47 am

ducminhkt wrote:I click button "Model control" in Config -> Advanced and receive message "Your Android version is to old". What's the problem ?
I'm using android version 2.3.5

this works only with android 3.0 and up

ezio · Post by **ezio** » Wed Jan 28, 2015 2:48 am

FedorCommander wrote:Hi there!

Does it work over usb on 4.4.2 ???? Cant get this thing working over USB.

After installation it was crashing with Invalid BT!!!! address in the stack trace.... Ok. I made fake connection to some BT device, just to get some address valid... Then I switched back to serial usb.... Well, it stopped crashing!!!

Then it just cannot connect to naze32 at all!!!

Any ideas?

Thanks!

You are right about it. I will push the update as soon as possible.

FedorCommander · Post by **FedorCommander** » Wed Jan 28, 2015 8:49 am

Thanks a lot...

miztic · Post by **miztic** » Wed Jan 28, 2015 5:18 pm

ezio wrote:
miztic wrote:I'm a little premature because I'm still building my quad

But I was thinking about the follow-me feature, you can already use the ez-gui to send the model to a certain gps coordinate correct?
A follow-me feature would just do it continuously:

When follow-me button is hit:
take device/tablet/phone current location and model gps location and compute the difference, let's call this Offset.

then every 0.5-1 second, send the model an updated destination calculated via device current location + Offset.
and send it a POI [point of interest] of the device gps coordinate, so the model will always be looking at you.

I was thinking about implementing this myself, for fun [that's probably at least 2 months away because I need to get my quad flying first], but your software is so far ahead, it might be really easy for you to do.

Nice work.

Follow me is there for the ages.
It is in Advanced section. If you have MAG and follow me enabled at the same time the model will follow you pointing in the flight direction ( which is equal to looking at you) if the MAG is off the model will follow you without rotating to the flight direction.

That's what I get for saying something before trying it

Thanks for all your hard work! I'm looking forward to getting my model in the air.

Leo · Post by **Leo** » Wed Jan 28, 2015 6:16 pm

Well, I'm so fed up with these random "No data received" errors in EZ-GUI that I've changed my 3DR setup. BTW I'm not the only one having these errors.

I purchased 3 transmitter sets and all show the same results. Since I'm almost convinced the problem lies in the way EZ-GUI handles the protocol with 3DR devices I decide to switch to Bluetooth in EZ-GUI.

I soldered a Bluetooth module to my 3DR ground module. It's kinda shooting ones self in the knee however it does have the advantage that I can place the antenna + ground station without having any cables connected to my Android device which in turn gives me freedom of movement.

To date so far all my ground tests have not once caused a "No data received" error. I have yet to try this setup in actual flight but it looks promising.

EZ-GUI needs to look into this. Maybe offering better debug options so one can pinpoint the problem better.

ezio · Post by **ezio** » Thu Jan 29, 2015 6:58 am

Leo wrote:Well, I'm so fed up with these random "No data received" errors in EZ-GUI that I've changed my 3DR setup. BTW I'm not the only one having these errors.

I purchased 3 transmitter sets and all show the same results. Since I'm almost convinced the problem lies in the way EZ-GUI handles the protocol with 3DR devices I decide to switch to Bluetooth in EZ-GUI.

I soldered a Bluetooth module to my 3DR ground module. It's kinda shooting ones self in the knee however it does have the advantage that I can place the antenna + ground station without having any cables connected to my Android device which in turn gives me freedom of movement.

To date so far all my ground tests have not once caused a "No data received" error. I have yet to try this setup in actual flight but it looks promising.

EZ-GUI needs to look into this. Maybe offering better debug options so one can pinpoint the problem better.

Which driver do you usually use with 3dr radio connected via USB?

Leo · Post by **Leo** » Thu Jan 29, 2015 7:11 am

I have purchased 3DR transmitters for "FTDI" and "Other" drivers. Both show the same symptoms.

I also tried it on different Android devices Samsung Galaxy S2 or HTC Flyer. Both give out the error.

ezio · Post by **ezio** » Thu Jan 29, 2015 12:00 pm

Leo wrote:I have purchased 3DR transmitters for "FTDI" and "Other" drivers. Both show the same symptoms.

I also tried it on different Android devices Samsung Galaxy S2 or HTC Flyer. Both give out the error.

Could you try also with universal driver and let me know

rubadub · Post by **rubadub** » Thu Jan 29, 2015 11:42 pm

a few issues/questions:

- why does the app need to always restart when making any changes to the settings? It's very frustrating and slow. Can this please be changed?

- please fix the 'started' voice alert. It's still sounding when the app starts even with voice alerts disabled (Android 4.1.2 on a Samsung Galaxy S3)

- please make the app single-instance, the multi-instance behavior is causing a lot of problems

- in GPS screen, green refresh LED will show up as lit even when not even connected to anything

- please consider adding a dropdown list on main screen with a list of the available BT adapters that can be used to select the adapter to connect to so that we aren't forced to go into the settings screen. Simply select the appropriate adapter and click "connect", or something to this effect. I have a few BT adapters configured, and frequently need to switch between them. It sucks having to go into the settings screen,selecting the correct BT adapter, exiting settings, restarting app, connecting, etc....

- please consider making the 'connect' button bar a universal feature that appears on every settings screen so that we can re-connect from any reasonable position in the app, such as the screens for PID, calibration, nav settings, aux, etc. For example, if the BT link gets disconnected while working within the PID screen, you're forced to back out to the main screen, click 'connect', wait for the 'connected!' message, and then scroll back to the PID screen; it's very annoying

- please show the connection status up on top within the yellow ribbon (version info & connected/not connected). It sucks having to go to the main screen in order to see if the 'connected!' message has appeared.

ezio · Post by **ezio** » Fri Jan 30, 2015 5:10 am

rubadub wrote:a few issues/questions:

- why does the app need to always restart when making any changes to the settings? It's very frustrating and slow. Can this please be changed?

- please fix the 'started' voice alert. It's still sounding when the app starts even with voice alerts disabled (Android 4.1.2 on a Samsung Galaxy S3)

- please make the app single-instance, the multi-instance behavior is causing a lot of problems

- in GPS screen, green refresh LED will show up as lit even when not even connected to anything

- please consider adding a dropdown list on main screen with a list of the available BT adapters that can be used to select the adapter to connect to so that we aren't forced to go into the settings screen. Simply select the appropriate adapter and click "connect", or something to this effect. I have a few BT adapters configured, and frequently need to switch between them. It sucks having to go into the settings screen,selecting the correct BT adapter, exiting settings, restarting app, connecting, etc....

- please consider making the 'connect' button bar a universal feature that appears on every settings screen so that we can re-connect from any reasonable position in the app, such as the screens for PID, calibration, nav settings, aux, etc. For example, if the BT link gets disconnected while working within the PID screen, you're forced to back out to the main screen, click 'connect', wait for the 'connected!' message, and then scroll back to the PID screen; it's very annoying

- please show the connection status up on top within the yellow ribbon (version info & connected/not connected). It sucks having to go to the main screen in order to see if the 'connected!' message has appeared.

1. No with current design.
2. Already fixed. Please consider to try beta version.
3. Probably fixed in beta.
4. Led changes colors when data from GPS are pulled. Green color means nothing.
5. Will come with time
6. Not interested
7. Maybe some day

ldonnay · Post by **ldonnay** » Sun Feb 01, 2015 6:21 pm

ezio wrote:
ldonnay wrote:Ezio,
I am flying a naze32 with Cleanflight and a Bluetooth adapter. Connexion and reading of settings through EZ GUI works perfect.
I have an issue when updating settings (actually PIDs).
After updating the settings (P in rate mode), Alt Hold, which was running fine before, is not stable anymore.

I compared the cli dump output from before and after pid tuning through Bluetooth and EZ GUI and I found
set p_vel = 120
set i_vel = 45
set d_vel = 1
has become
set p_vel = 0
set i_vel = 0
set d_vel = 0
defaults resets it.

This only happens when tuning using multiwii EZ-GUI and MultiWii Configurator over bluetooth. A direct connection to my pc running Chrome Cleanflight leaves these values at default.
Looking at multiwii EZ-GUI and MultiWii Configurator on android there is no section in PID for velocity but there is in Cleanflight on the pc so I can only assume when the pids are sent via android a 0's value is sent for vel.

Does anybody else have problems with altitude hold or is it only me?

Have you set the firmware version to Cleanflight in the EZ-GUI Settings ?

Thanks' for the Check: I was actually NOT in Cleanflight mode. Will test as soon as the weather gets better.

ldonnay · Post by **ldonnay** » Sun Feb 01, 2015 6:21 pm

ezio wrote:
ldonnay wrote:Ezio,
I am flying a naze32 with Cleanflight and a Bluetooth adapter. Connexion and reading of settings through EZ GUI works perfect.
I have an issue when updating settings (actually PIDs).
After updating the settings (P in rate mode), Alt Hold, which was running fine before, is not stable anymore.

I compared the cli dump output from before and after pid tuning through Bluetooth and EZ GUI and I found
set p_vel = 120
set i_vel = 45
set d_vel = 1
has become
set p_vel = 0
set i_vel = 0
set d_vel = 0
defaults resets it.

This only happens when tuning using multiwii EZ-GUI and MultiWii Configurator over bluetooth. A direct connection to my pc running Chrome Cleanflight leaves these values at default.
Looking at multiwii EZ-GUI and MultiWii Configurator on android there is no section in PID for velocity but there is in Cleanflight on the pc so I can only assume when the pids are sent via android a 0's value is sent for vel.

Does anybody else have problems with altitude hold or is it only me?

Have you set the firmware version to Cleanflight in the EZ-GUI Settings ?

Thanks' for the Check: I was actually NOT in Cleanflight mode. Will test as soon as the weather gets better.

Leo · Post by **Leo** » Sun Feb 08, 2015 4:50 pm

ezio wrote:Could you try also with universal driver and let me know

Universal driver seems to be working. No problems so far.

rubadub · Post by **rubadub** » Mon Feb 09, 2015 11:05 am

ezio, thanks for fixing a bunch of stuff in the latest revision, seems to work much better now.

Not really a feature request related to EZ-GUI, but is there any chance that support could be added to the MSP to support changing conf.psensornull and conf.pint2ma variables (powermeter null value & scaling factor)? It would be great to be able to modify these items from the MISC menu. I'm not sure if the GPS-NAV protocol already has these implemented, but, if so, I'd be willing to add it myself to 2.3. Any chance something like this can be added to EZ-GUI's MSP for the 2.3 protocol?

ezio · Post by **ezio** » Tue Feb 10, 2015 2:21 am

rubadub wrote:ezio, thanks for fixing a bunch of stuff in the latest revision, seems to work much better now.

Not really a feature request related to EZ-GUI, but is there any chance that support could be added to the MSP to support changing conf.psensornull and conf.pint2ma variables (powermeter null value & scaling factor)? It would be great to be able to modify these items from the MISC menu. I'm not sure if the GPS-NAV protocol already has these implemented, but, if so, I'd be willing to add it myself to 2.3. Any chance something like this can be added to EZ-GUI's MSP for the 2.3 protocol?

as far as i'm aware these are not implemented in MSP.
You can make new topic and ask MultiWii devs to add them.

ezio · Post by **ezio** » Fri Feb 13, 2015 2:30 am

Just to let you know that I've created a website:
www.ez-gui.com

if you have issues to report please do it there:
http://ez-gui.com/report_issue/

civicexa · Post by **civicexa** » Mon Feb 16, 2015 12:18 am

Hi,

I was trying to connect Xbee Pro S2B modules to my quad and today is working. I have to test in outdoors on this days. Here a pic of the wireless bridge with the bluetooth smirfgold working in.
Xbee PRO S2B datasheet says that the range of modules its about 1500 m (5000 ft) LOS. I´ll have to test.

http://s1382.photobucket.com/user/jmaya ... c.jpg.html

http://s1382.photobucket.com/user/jmaya ... 2.jpg.html

Leo · Post by **Leo** » Mon Feb 16, 2015 6:32 am

Eizo, what version do I configure in EZ-GUI if I'm running r1743. 2.3 Nav or 2.4?

ezio · Post by **ezio** » Mon Feb 16, 2015 8:25 pm

Leo wrote:Eizo, what version do I configure in EZ-GUI if I'm running r1743. 2.3 Nav or 2.4?

It doesn't really matter but I advice 2.4
The difference will be only lack of Trims if you choose 2.3 Nav ( as I remember correctly)

ezio · Post by **ezio** » Thu Feb 19, 2015 4:01 am

I'll be less active during next weeks as I'm expecting a baby girl to join to my live so please be patient.

Bart

Drezed · Post by **Drezed** » Thu Feb 19, 2015 4:09 am

Congratulations! :-)

Jeff

civicexa · Post by **civicexa** » Thu Feb 19, 2015 6:33 am

My best wishes for you

Leo · Post by **Leo** » Thu Feb 19, 2015 7:17 am

Fantastic Bart

------------

BTW: I think it would be better to call the program "EZ-GUI Log Converter"

Also, I'm going to post some screen shots of in perfections I have when using EZ-GUI.

For example:

Pozzix · Post by **Pozzix** » Wed Mar 11, 2015 2:56 pm

Hi there,

I have updated to latest version and now i cannot connect through otg cable (universal port)

With the previous version I haven't had any problem....

I have a Galaxy Note3 with Kitkat ...the error message is "unable to connect"

How is possible?

This week I'd like to use that amazing program at the field.....help pls ....

Thanks
Max

********EDIT*****

I'm so sorry....my brain is farting today....
It works amazing....I used the OTG cable inverted (otg on naze and the other cable micro usb on the phone)....Very my bad.

Thanks and sorry again....

MAX

ezio · Post by **ezio** » Sat Mar 14, 2015 3:30 am

I want to add pre flight checklist to EZ-GUI. Any propositions what should be there?

Leo · Post by **Leo** » Sat Mar 14, 2015 7:26 am

Fix the graphic glitches first please.

handsomejackuk · Post by **handsomejackuk** » Tue Mar 17, 2015 11:51 am

Is current meter implemented on EZ-gui anywhere, i have the virtual current meter on naze32 just wondered, as i can't see it....?

if not will it be on later releases ?

a dial on the dashboard would be great ...

thanks Al...

handsomejackuk · Post by **handsomejackuk** » Tue Mar 17, 2015 11:51 am

Is current meter implemented on EZ-gui anywhere, i have the virtual current meter on naze32 just wondered, as i can't see it....?

if not will it be on later releases ?

a dial on the dashboard would be great ...

thanks Al...

howardhb · Post by **howardhb** » Tue Mar 17, 2015 7:24 pm

HI everyone.

I've just upgraded to MW2.4 and checked it out....All good!
Using 3DR telemetry radios (from ReadytoflyQuads) and Samsung Galaxy S5 (SM-G900H)
With settings as shown in attached pictures, I get perfect communication to EZ-Gui. Not a single "no data received" warning.
Going to fly it tomorrow!

: USB Setting

: ADVANCED setting

: S5

Leon11t · Post by **Leon11t** » Sat Mar 21, 2015 7:24 pm

Hi Ezio. I'm interesting wifi connection in your app. Whot protocol do you use? Whot kind of data received. Can you write a sample string from received data.

ezio · Post by **ezio** » Sun Mar 22, 2015 12:05 am

Leon11t wrote:Hi Ezio. I'm interesting wifi connection in your app. Whot protocol do you use? Whot kind of data received. Can you write a sample string from received data.

What you want to achieve?