{"action":"created","issue":{"url":"https://api.github.com/repos/mirkix/ardupilotblue/issues/13","repository_url":"https://api.github.com/repos/mirkix/ardupilotblue","labels_url":"https://api.github.com/repos/mirkix/ardupilotblue/issues/13/labels{/name}","comments_url":"https://api.github.com/repos/mirkix/ardupilotblue/issues/13/comments","events_url":"https://api.github.com/repos/mirkix/ardupilotblue/issues/13/events","html_url":"https://github.com/mirkix/ardupilotblue/issues/13","id":292412595,"number":13,"title":"RC input not working with SBUS","user":{"login":"rflowers","id":11959570,"avatar_url":"https://avatars2.githubusercontent.com/u/11959570?v=4","gravatar_id":"","url":"https://api.github.com/users/rflowers","html_url":"https://github.com/rflowers","followers_url":"https://api.github.com/users/rflowers/followers","following_url":"https://api.github.com/users/rflowers/following{/other_user}","gists_url":"https://api.github.com/users/rflowers/gists{/gist_id}","starred_url":"https://api.github.com/users/rflowers/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/rflowers/subscriptions","organizations_url":"https://api.github.com/users/rflowers/orgs","repos_url":"https://api.github.com/users/rflowers/repos","events_url":"https://api.github.com/users/rflowers/events{/privacy}","received_events_url":"https://api.github.com/users/rflowers/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":7,"created_at":"2018-01-29T13:47:34Z","updated_at":"2018-03-20T16:40:49Z","closed_at":null,"author_association":"NONE","body":"@mirkix Thankyou very much for your amazing work on this project.\r\n\r\nUnfortunately currently the build instructions do not work with SBUS RC controllers, the signal is not detected by ardupilot.\r\n\r\nI have checked the output from my receiver with a scope verified that it is producing a signal, so the electronics appear good but this is not detected by ardupilot or the rcin examples test code. My best guess is that the recent device tree alterations in Linux have broken the installation code to install the PRU firmware and setup the pinmux (all the ardupilot examples I can find use the old cape manager format and give errors in the new device tree format). I have followed your instructions on a brand new beagleboard and patched with your latest patch and still cannot get any rc signal into ardupilot.\r\n\r\nI’ve managed to get Hello world PRU code working to test PRU installation and decompiled the dtbos accessed in install.sh of Linux Hal Essentials in the hope of manually installing them as a workaround, no joy yet\r\n\r\nI have tried the pre-compiled arduplane, but it doesn’t appear to install the firmware or setup the pinmuxing (which from reading the Linux HAL essentials appears to need to be set up separately), I have also compiled ardupilot from source on the bbb in case it was hidden in the source, apparently no change, my best guess is that the install.sh script needs to be run on the target bbb to enable the prus to read the receiver signal.\r\n\r\ncurrently config-pin -q on P8:15 (the multi-function pin) gives cape not found, but can be manually set to the correct value (pru in or pru ecap I guess, based on similar terms in your ardupilot service script, which also appears to have been broken by the update).\r\n\r\nAny work arounds you could suggest to get rc input working would be great. Any diagnostic code would also be very helpful.\r\n\r\nThank you for your time."},"comment":{"url":"https://api.github.com/repos/mirkix/ardupilotblue/issues/comments/374668594","html_url":"https://github.com/mirkix/ardupilotblue/issues/13#issuecomment-374668594","issue_url":"https://api.github.com/repos/mirkix/ardupilotblue/issues/13","id":374668594,"user":{"login":"rflowers","id":11959570,"avatar_url":"https://avatars2.githubusercontent.com/u/11959570?v=4","gravatar_id":"","url":"https://api.github.com/users/rflowers","html_url":"https://github.com/rflowers","followers_url":"https://api.github.com/users/rflowers/followers","following_url":"https://api.github.com/users/rflowers/following{/other_user}","gists_url":"https://api.github.com/users/rflowers/gists{/gist_id}","starred_url":"https://api.github.com/users/rflowers/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/rflowers/subscriptions","organizations_url":"https://api.github.com/users/rflowers/orgs","repos_url":"https://api.github.com/users/rflowers/repos","events_url":"https://api.github.com/users/rflowers/events{/privacy}","received_events_url":"https://api.github.com/users/rflowers/received_events","type":"User","site_admin":false},"created_at":"2018-03-20T16:40:49Z","updated_at":"2018-03-20T16:40:49Z","author_association":"NONE","body":"Ok I have now got SBUS working. However of my 2 bbs, both of which I followed the detailed instructions at https://libraries.io/github/mirkix/ardupilotblue, which give more setup info than this more popular, though apparently less up to date documentation. The problem I had was even though both had the same script, the device tree installation worked fine on one, and not on the other. I believe the disparity is due to a number of different scripts for the device tree, some using uio_pruss, on the successful board. They set something underlying correctly, and that board now works, whereas the other board doesn’t. So unsatisfying and the installation instructions do not appear comprehensive. My work around has been imaging the successful one onto the other one to copy the kernel setting or whatever, as unfortunately I’m out of time. If I can find a better solution I’ll post it on a blog or similar to help the others struggling with this problem. Hopefully the device tree rewrite for bb (currently underway) can fix this problem long term."}}
{"actor":{"display_login":"rflowers"}}