AvareX Android AutoPilot Functionality
David Lewis
I finally had a chance to test Android AvareX version 84 autopilot functionality. The code modification appears to have resolved the AP issue. After pairing AvareX to my Bluetooth/RS232 bridge, my Dynon autopilot responded immediately and appropriately as I stepped through the waypoints of a loaded flight plan. This was just a hangar test, but is very encouraging. I will attempt an inflight test on Friday and report back. I’ll check to see if the AP responds to a ‘Direct’ input as well. Thank you for the work done to restore this Android functionality. Loving the app and all the new features.
DL
David Lewis
I was able to flight test Android AvareX-84 driving my Dynon D180 autopilot. The results are disappointing. I created and activated a simple flight plan. When engaging the AP in GPS mode, AvareX did not want to fly the coarse lines between waypoints depicted on the map page. Instead, secondary (Brown?) lines would appear that AvareX wanted to follow. Using the AP heading mode, I could steer back to the coarse line, but when re-engaging GPS mode, AvareX would veer off the course line. To verify that the Dynon AP was not the issue, I switched to Legacy Avare with the same flight plan, and the AP in GPS mode locked in correctly and accurately.
It may be that this apparent anomaly is an operator error issue. Any guidance about properly setting up and activating a flight plan in the X environment would be appreciated. My recollection is that Brown lines depict Direct courses. How do I suspend the AvareX preference for Direct routes (unless that is the desired path) and instead follow the flight plan waypoint courses?
I can continue to flight test the autopilot mechanism as version updates become available.
DL
David Lewis
I test flew the revised Bluetooth to Autopilot functionality of Android AvareX version 88. There are still issues to be resolved. Legacy Avare operation remains flawless. My understanding is that the AP code from Legacy was ported into X, so logically, the same AP functionality should have transferred. My Dynon system recognizes that data from AvareX is being sent, but something about the data stream is flawed. Flightpaths between waypoints are not being followed. I need to set up a bench-test reader and troubleshoot the AvareX Bluetooth output. What needs to be verified is that the AvareX stream is in NMEA-0183 format, running at 4800 baud, and that NMEA sentences $GPRMB, $GPRMC, and $GPBOD are included.
I’m open to the possibility that the problem is an operator error issue, so I will also continue to explore whether there is something in the way AvareX flight plans have to be configured in order for AP functionality to work properly.
DL
Apps4av Support
Forum: https://groups.google.com/forum/#!forum/apps4av-forum
--
You received this message because you are subscribed to the Google Groups "Apps4Av Forum" group.
To unsubscribe from this group and stop receiving emails from it, send an email to apps4av-foru...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/apps4av-forum/bfb224ee-5424-4ec8-a669-917e197969e8n%40googlegroups.com.
David Lewis
Thank you Zubair . . .
Working on it. Initial attempts to sniff and visualize the BT stream have been unsuccessful, but I think that’s a learning curve issue. However, this morning I rediscovered a Legacy Avare feature that provides a bit of clarity. The Legacy I/O tab ‘top menu’ has an Auto Pilot via Bluetooth selection. With that, I can BT connect to my MacBook and an output stream appears in the tablet screen. I see nothing on the MacBook, but the Avare BT stream contains NMEA sentences $GPRMC, $GPGGA, $GPRMB and $GPBOD when there is an active flight plan running. When the flight plan is made inactive, the stream reverts to only the $GPRMC and $GPGGA sentences. This is a wonderful confirmation of what Legacy Avare currently sends to my Dynon AP system and which functions perfectly.
Not sure what the baud rate is, but whatever it Is, it works. I may have been wrong about the 4800 baud spec. It is more likely 9600. I’ll figure that out as we move forward. Next up will to be get a visualization of the AvareX stream. If I can’t get a sniffer app to see it, I’ll graduate to a hardware solution.
It would sure be nice to get input from @Ron Walker. I remember his involvement with the separate I/O plugin and eventual merger into the Avare App. Looking back in the forum archives I see @Chuck Pilot as another active participant in the discussion, but those conversations go way back to 2014. We’ll just have to reconstruct the knowledge they contributed.
I really want to figure this out. Loving AvareX and the work you’ve put in to its development. The new features are awesome. The multiplatform capabilities are a game changer. Also really like the Pro Services ability to store my data and pull it in to whatever device I happen to have handy.
Once I have results to report, I’ll post them here.
DL
David Lewis
I am now able to read the Android I/O Bluetooth streams from both Legacy-Avare and AvareX. Doing so required a hardware solution. I couldn’t get any of the BT sniffer applications to work. I can provide what the various fields within the sentences mean if you are interested.
AvareX appears to output basically the same NMEA-0183 sentences as Legacy-Avare. That’s good. However, the AvareX data somehow provides additional detail (Satellite count, Altitude fields, etc). I don’t know how these sentences are generated, but I assume the upgraded capabilities of AvareX can now add this additional information. Can’t hurt? So far, so good.
Sample Legacy Avare feed (Android)
$GPRMC,040738,A,3412.562,N,11819.754,W,000.0,000.0,150326,011.3,E*6F
$GPGGA,040738,3412.562,N,11819.754,W,1,00,0.0,0.0,M,0.0,M,,*6B
$GPRMB,A,9.99,R,WJF,CL46,3446.068,N,11843.968,W,039.0,329.3,000.0,V*67
$GPBOD,273.8,T,262.4,M,CL46,WJF*1D
Sample AvareX feed (Android)
$GPRMC,040142,A,3412.561,N,11819.755,W,000.0,000.0,150326,011.0,W*77
$GPGGA,040142,3412.561,N,11819.755,W,1,06,0.0,278.9,M,-34.0,M,,*7A
$GPRMB,A,9.99,R,KWJF,CL46,3446.071,N,11843.968,W,039.0,329.3,000.0,V*24
$GPBOD,273.8,T,261.8,M,CL46,KWJF*59
The only glaring error between the Legacy and X streams is found at the end of their $GPRMC sentences. The Magnetic Variation fields are contradictory. Legacy Avare provides a correct East variation for my location (SoCal), while AvareX incorrectly reports a West variation. Again, not sure how these sentences are generated, but this might explain why the feed from AvareX causes the autopilot deviations I’ve experienced, while the Legacy-Avare guidance follows a flight plan perfectly.
There may be additional discrepancies to be identified. If we can address the magnetic variation issue, that might be enough to get AvareX autopilot control working correctly. I will continue to explore the outputs and how they are interpreted.
DL
Apps4av Support
Forum: https://groups.google.com/forum/#!forum/apps4av-forum
To view this discussion visit https://groups.google.com/d/msgid/apps4av-forum/dcc13894-fb4d-40db-a674-7cc766c2c16cn%40googlegroups.com.