New major beta release for Andropilot (if reports from brave users are good, it will go out to the 'safe' general release in about a week). I'm testing out some changes to simplify the UI - this release includes some of them. Here's a 'picture' of the new code:
Please please please, provide tester reports for plane/quad/rover/jugglebot and I'll integrate your feedback...
# 1.7.07
- SimpleUI: Move status messages into their own fragment (and make them update even if fragment is not visible)
- SimpleUI: Try to guess likely modes the user would want and put them as buttons at the bottom of the screen
- SimpleUI: Show the bluetooth device connect/disconnect button
- SimpleUI: Prompt user with extra dialog if they try especially dangerous mode switches (disconnecting or disarming while we think the vehicle is flying etc...)
- I played around with the profiler a bit and many operations should now be a bit faster
- When connected by bluetooth, show proper vehicle state on the icon
- Make popup modal bar appear in correct position on portrait 7" displays
- Show HDOP (horizontal position precision) in the gps display
- Only enable arm menu item if we have a heartbeat from the vehicle
- Fix the bug where mode changes would be announced twice
- Fix some minor display glitches
- Add support for profiling/tracing when in developer mode
- Fix a couple more rare autobugs
- SimpleUI: Lots more coming in the next releases...
One thing that made this simplification possible is that I now try to model the vehicle state (flying, not flying etc...) in the GCS. It is possible that I have errors in this state machine - if that happens, the 'new' buttons on the bottom of the screen won't work. If that happens you can still use the old menu items as a work-around (please file a bug if you see this problem).
You'll need to join a special G+ group if you want to get the beta release (the slick new way Google allows users to opt-in for beta test builds). Instructions are here. Otherwise wait a week and it will be pushed to general availability.
For general support on Andropilot please post a new discussion in our group and I'm sure someone will lend a hand.
Comments
Hi Ahmet,
Sure thing - in fact you can build your own andropilot. The build instructions are here:
https://github.com/geeksville/arduleader
A developers guide is here:
https://github.com/geeksville/arduleader/wiki/Andropilot%20Develope...
And I'm happy to help if you have any questions - I'll add any responses to the developers guide.
In your case, I bet you could start by using the (very basic) Pebble watch support here:
https://github.com/geeksville/arduleader/blob/master/andropilot/src...
You can write any new code in either scala or Java ;-).
I wish we could customize the button. I want a simple mode button.
Is there a way I can fetch some data from your application? I'm thinking about developing an app for my smartwatch(Sony Liveview), its apps run on smartphone as services. It allows drawing canvas etc. onto watch. I made an app called PeekScreen that streams screen of phone to watch with it. I'm viewing HUD view of your app on my watch with it. But I think I could make a better app If i knew how to fetch those datas from andropilot.
@Kevin,
Nice work. Nothing like a state machine to help with visualizing the way the program functions.
Can't wait for the post beta release!
Regards,
TCIII ArduRover2 Developer
btw - in real life that state machine doesn't look that nasty ;-). The state machine compiler just makes ugly plots. Here's the code.