Closed peterbarker closed 3 years ago
{code} are there some instructions on how to add message documentation?
17:48 Nope. Would you like some? :-)
I'd like to try and help out with the plane documentation as a start!
@rishabsingh3003 great!
b810a0de232680210fb2e3df250dc2839f2e32ea is a commit showing adding a single piece of documentation.
Running the autotest line in the first message in this PR (suitably adjusted for Plane) will validate the new message.
Updated to reflect Plane messages as done (still in PR, 'though)
@peterbarker I am having a little trouble with Rover documentation. Is there any reason why DPTH
and SAIL
log messages not part of this list above.
I am getting the following error when I am adding those two:
AUTOTEST: Failing tests:
LoggerDocumentation (Test Onboard Logging Generation) (Documented message (DPTH) not in code)
@rishabsingh3003 parsing failure in my autotest code. PR coming.
Looks like this test is now running in CI so all messages are documented?
Feature request
We have infrastructure in place to allow the onboard log messages to be documented. There are lots of messages yet to be documented; this is the list. This list was generated by running
... and snipping out the list of undocumented messages.
[20200401 editted to remove now--documented
MAV
andPARM
] [20200401 editted to remove vehicle-specificTECS
andTEC2
]Plane messages have been done here: https://github.com/ArduPilot/ardupilot/pull/13910
These are Plane-specific messages which need documenting:AUTOTEST: Undocumented message: AETRAUTOTEST: Undocumented message: AOAAUTOTEST: Undocumented message: ATRPAUTOTEST: Undocumented message: SONRAUTOTEST: Undocumented message: STATCopter-specific message:
Sub-specific messages:
Describe the solution you'd like Crowd-sourced documentation
Describe alternatives you've considered Doing it myself. Rather time consuming....
Platform [ X ] All [ ] AntennaTracker [ ] Copter [ ] Plane [ ] Rover [ ] Submarine