{"action":"created","issue":{"url":"https://api.github.com/repos/cleanflight/cleanflight/issues/792","labels_url":"https://api.github.com/repos/cleanflight/cleanflight/issues/792/labels{/name}","comments_url":"https://api.github.com/repos/cleanflight/cleanflight/issues/792/comments","events_url":"https://api.github.com/repos/cleanflight/cleanflight/issues/792/events","html_url":"https://github.com/cleanflight/cleanflight/pull/792","id":69296409,"number":792,"title":"Configuration - Allow configuration using on-screen menus (HoTT and OLED)","user":{"login":"Pierre-A","id":8274225,"avatar_url":"https://avatars.githubusercontent.com/u/8274225?v=3","gravatar_id":"","url":"https://api.github.com/users/Pierre-A","html_url":"https://github.com/Pierre-A","followers_url":"https://api.github.com/users/Pierre-A/followers","following_url":"https://api.github.com/users/Pierre-A/following{/other_user}","gists_url":"https://api.github.com/users/Pierre-A/gists{/gist_id}","starred_url":"https://api.github.com/users/Pierre-A/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/Pierre-A/subscriptions","organizations_url":"https://api.github.com/users/Pierre-A/orgs","repos_url":"https://api.github.com/users/Pierre-A/repos","events_url":"https://api.github.com/users/Pierre-A/events{/privacy}","received_events_url":"https://api.github.com/users/Pierre-A/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":43,"created_at":"2015-04-18T10:37:48Z","updated_at":"2015-05-20T15:20:06Z","closed_at":null,"pull_request":{"url":"https://api.github.com/repos/cleanflight/cleanflight/pulls/792","html_url":"https://github.com/cleanflight/cleanflight/pull/792","diff_url":"https://github.com/cleanflight/cleanflight/pull/792.diff","patch_url":"https://github.com/cleanflight/cleanflight/pull/792.patch"},"body":"Here is a proposal of an interactive procedure for setting Cleanflight parameters directly through your TX.\r\nThis first approach only concerns the Graupner Hott system as based on their Hott Text-Mode protocol which allows a bi-directionnal dialog between the firmware (Cleanflight) and the transmitter.\r\n\r\nAs shown on the pictures below, this procedure includes two main pages from which one can access more specific pages containing informations and editable parameters as found in the Cleanflight-Configurator. \r\nWhile there is no limit for this choice and presentation of data (other than memory space), all CLI parameters are not in these pages. I selected only some of them for illustration and considering what should be easily changed on the field without needing a connection to the configurator.\r\n\r\nAs usual, the Inc/Dec, Prev/Next arrows and Set/Esc buttons of the TX are used for selecting and setting every current parameter to a new value directly applied to Cleanflight (and saved in EEPROM if desired).\r\n\r\nAt this point (with 2 « selection » and 13+ « parameters » pages), I did my best to make the code as compact as possible but it takes about 12 Kb of flash memory. Always possible to change/remove some pages, reorganize the choice and presentation of parameters, find a cheapest structure for coding, other ideas..\r\n\r\nIMHO it would be fine for other than Graupner users to enjoy this facility on their TX but such an adaptation requires an opened communication protocol and structure. What about OpenTX for Taranis users ?\r\n\r\nI thank you for any comments and ideas.\r\n![hott textmode p1](https://cloud.githubusercontent.com/assets/8274225/7215100/9571d86e-e5c7-11e4-8e9d-20020d94b1d6.jpg)\r\n![hott textmode p2](https://cloud.githubusercontent.com/assets/8274225/7215106/a0c203c4-e5c7-11e4-94a2-4808fff858db.jpg)\r\n"},"comment":{"url":"https://api.github.com/repos/cleanflight/cleanflight/issues/comments/103923739","html_url":"https://github.com/cleanflight/cleanflight/pull/792#issuecomment-103923739","issue_url":"https://api.github.com/repos/cleanflight/cleanflight/issues/792","id":103923739,"user":{"login":"zdar","id":1691703,"avatar_url":"https://avatars.githubusercontent.com/u/1691703?v=3","gravatar_id":"","url":"https://api.github.com/users/zdar","html_url":"https://github.com/zdar","followers_url":"https://api.github.com/users/zdar/followers","following_url":"https://api.github.com/users/zdar/following{/other_user}","gists_url":"https://api.github.com/users/zdar/gists{/gist_id}","starred_url":"https://api.github.com/users/zdar/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/zdar/subscriptions","organizations_url":"https://api.github.com/users/zdar/orgs","repos_url":"https://api.github.com/users/zdar/repos","events_url":"https://api.github.com/users/zdar/events{/privacy}","received_events_url":"https://api.github.com/users/zdar/received_events","type":"User","site_admin":false},"created_at":"2015-05-20T15:20:06Z","updated_at":"2015-05-20T15:20:06Z","body":"@hydra Status line - (a) I'll craft something in a week or two :) The first part is here: https://github.com/zdar/cleanflight/commit/f584b649d8022f17e4f74b45b8942cf72a954c67 (warning it probably does not compile as I do not have compiler installed at the moment). Anyway comments structure are welcome (ignore syntax errors).\r\n\r\n@Pierre-A On FrSky I can probably send 100-200 chars per second. Which means that any update of screen would take 1-2 seconds. This creates BIG lag which I belive makes editing almost unusable. Sending only changes would greatly improve the responce time.   "}}