Closed marksev1 closed 9 years ago
On Fri, 16 May 2014 02:43:49 -0700 marksev1 notifications@github.com wrote:
I'd propose also a artificial horizon indicator as an enhancement to your gui. Like the "major" autopilot gui's have, like taulabs gcs, apm-planner etc.
Just an idea! Have fun & great work so far!
Reply to this email directly or view it on GitHub: https://github.com/stronnag/mwptools/issues/3
The original theory was that I would not reimplement MultiWiiConf, rather just build a MW planner for POSIX OS. Then I discovered that getting MultiWiiConf on my Arch ARM/Chromebook was harder than reimplementing the functions import to me .... So one day, for sure.
btw, is there a specification for "Lighttelemetry"; after the pain of extracting from Windows source code the MW nav functions, I'm in no hurry to go done the reverse-engineering route again.
Here's some info: http://www.wedontneednasa.com/2014/02/lighttelemetry-v2-en-route-to-ground-osd.html
https://github.com/KipK/Ghettostation/blob/master/GhettoStation/LightTelemetry.cpp
https://github.com/KipK/Ghettostation/blob/master/GhettoStation/LightTelemetry.h
https://github.com/KipK/baseflight/blob/LTelemetry/src/telemetry_ltm.c
Otherwise I'm discussing with the author of lightelemetry on a regular basis on irc, so I can ask him about specific things if you want?
Was the above info ^^^ what you were looking for?
It would have been nice to have a more general description e.g. as the MSP spec http://www.multiwii.com/wiki/index.php?title=Multiwii_Serial_Protocol and https://docs.google.com/document/d/16ZfS_qwc-rJeA7N5Tx0DA6wtgxl6HdGgaz-jE3lHBWs/edit?usp=sharing (out of frustration from having to generate an implementation for Windows source code).
And how is the protocol invoked, or does it just start on arming?
hi.
LTM is an air to ground telemetry, so it's one way only; No ACK & stuffs it just stream datas to the ground at low baudrates.
Depending of flighcontroller implementation & configuration it starts at boot or when armed.
Protocol is binary, using little endian. There's 3 frames to consider:
.
values are:
Each frame end with a CRC byte, it's a simple XOR from first payload byte to last one ( starting at 4th byte , headers are not xored )
Hope it helps
Thanks. On the 'todo' list.
Until the new horizon stuff is fully working, let's leave this open. Currently it highly experimental and not 100% reliable.
The horizon and flight view items appear stable (with good GTK themes). The issue will be closed after the documentation has been updated.
Completed, apparently stable (if dock items fail to update, it's probably a bad GTK theme). Documentation updated.
I'd propose also a artificial horizon indicator as an enhancement to your gui. Like the "major" autopilot gui's have, like taulabs gcs, apm-planner etc.
Just an idea! Have fun & great work so far!