Closed GoogleCodeExporter closed 9 years ago
what's wrong with trunk?
i'm putting my hand up as the current maintainer of trunk, so please, anybody
with bug reports please post them here, or the developer list, or anywhere i
can reasonably find them..
Original comment by robert.dickenson
on 4 Aug 2013 at 11:52
1) what is the current state of testing?
2) Who has flown with what options settings?
3) Does nvram work with mavlink on udb4/5?
4) Is there mavlink nvram support on AUAV3 yet, or a plan to get there?
Original comment by kd0...@gmail.com
on 13 Aug 2013 at 1:34
1. Issues reported piece by piece in the issue list
2.
3. UDB5 physical memory has been tested with release 4.0
4. This is not part of fixing trunk. It is an enhancement. Submit an
enhancement issue as needed.
Original comment by uavflightdirector
on 13 Aug 2013 at 8:59
Original comment by uavflightdirector
on 14 Aug 2013 at 1:47
Original comment by robert.dickenson
on 14 Aug 2013 at 10:52
Original comment by robert.dickenson
on 29 Aug 2013 at 10:10
As per recent updates to trunk and successful flight testing reported by
Andrius, this issue is now deemed closed. Please report any outstanding
problems with trunk as individual issues.
Original comment by robert.dickenson
on 19 Nov 2013 at 2:56
Original issue reported on code.google.com by
uavflightdirector
on 1 Aug 2013 at 6:29