{"action":"created","issue":{"url":"https://api.github.com/repos/TauLabs/TauLabs/issues/2074","labels_url":"https://api.github.com/repos/TauLabs/TauLabs/issues/2074/labels{/name}","comments_url":"https://api.github.com/repos/TauLabs/TauLabs/issues/2074/comments","events_url":"https://api.github.com/repos/TauLabs/TauLabs/issues/2074/events","html_url":"https://github.com/TauLabs/TauLabs/issues/2074","id":118263413,"number":2074,"title":"Automatically determine timer resolution for PWM outputs","user":{"login":"mluessi","id":647005,"avatar_url":"https://avatars.githubusercontent.com/u/647005?v=3","gravatar_id":"","url":"https://api.github.com/users/mluessi","html_url":"https://github.com/mluessi","followers_url":"https://api.github.com/users/mluessi/followers","following_url":"https://api.github.com/users/mluessi/following{/other_user}","gists_url":"https://api.github.com/users/mluessi/gists{/gist_id}","starred_url":"https://api.github.com/users/mluessi/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/mluessi/subscriptions","organizations_url":"https://api.github.com/users/mluessi/orgs","repos_url":"https://api.github.com/users/mluessi/repos","events_url":"https://api.github.com/users/mluessi/events{/privacy}","received_events_url":"https://api.github.com/users/mluessi/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":4,"created_at":"2015-11-22T13:24:50Z","updated_at":"2015-11-22T19:25:07Z","closed_at":null,"body":"We currently have a selection for timer resolution (1MHz/12MHz) in the outputs section. I think this is confusing to users, as most of them don't understand what the timer resolution is / does and why it is important. Furthermore, the 1MHz/12MHz choice is closely related to the clock frequencies of the currently used STM32 chips and may constrain us in the future.\r\n\r\nI propose that we remove the timer resolution combo boxes and let the firmware determine the optimal resolution for a given PWM frequency."},"comment":{"url":"https://api.github.com/repos/TauLabs/TauLabs/issues/comments/158791132","html_url":"https://github.com/TauLabs/TauLabs/issues/2074#issuecomment-158791132","issue_url":"https://api.github.com/repos/TauLabs/TauLabs/issues/2074","id":158791132,"user":{"login":"kubark42","id":1118185,"avatar_url":"https://avatars.githubusercontent.com/u/1118185?v=3","gravatar_id":"","url":"https://api.github.com/users/kubark42","html_url":"https://github.com/kubark42","followers_url":"https://api.github.com/users/kubark42/followers","following_url":"https://api.github.com/users/kubark42/following{/other_user}","gists_url":"https://api.github.com/users/kubark42/gists{/gist_id}","starred_url":"https://api.github.com/users/kubark42/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/kubark42/subscriptions","organizations_url":"https://api.github.com/users/kubark42/orgs","repos_url":"https://api.github.com/users/kubark42/repos","events_url":"https://api.github.com/users/kubark42/events{/privacy}","received_events_url":"https://api.github.com/users/kubark42/received_events","type":"User","site_admin":false},"created_at":"2015-11-22T19:25:07Z","updated_at":"2015-11-22T19:25:07Z","body":"Agreed, but having used these boards for strange and unusual things I appreciate their flexibility. Would be a shame to lose that if not necessary. Could also be that the hardware informs the GCS of what it can do (via the board manager, for instance), and the GCS selects the best choice. In a distantly similar manner, this is what we do for timer banks."}}