{"action":"closed","issue":{"url":"https://api.github.com/repos/bortek/EZ-WifiBroadcast/issues/17","repository_url":"https://api.github.com/repos/bortek/EZ-WifiBroadcast","labels_url":"https://api.github.com/repos/bortek/EZ-WifiBroadcast/issues/17/labels{/name}","comments_url":"https://api.github.com/repos/bortek/EZ-WifiBroadcast/issues/17/comments","events_url":"https://api.github.com/repos/bortek/EZ-WifiBroadcast/issues/17/events","html_url":"https://github.com/bortek/EZ-WifiBroadcast/issues/17","id":229674751,"number":17,"title":"1.6 suggestions","user":{"login":"geofrancis","id":5570278,"avatar_url":"https://avatars0.githubusercontent.com/u/5570278?v=4","gravatar_id":"","url":"https://api.github.com/users/geofrancis","html_url":"https://github.com/geofrancis","followers_url":"https://api.github.com/users/geofrancis/followers","following_url":"https://api.github.com/users/geofrancis/following{/other_user}","gists_url":"https://api.github.com/users/geofrancis/gists{/gist_id}","starred_url":"https://api.github.com/users/geofrancis/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/geofrancis/subscriptions","organizations_url":"https://api.github.com/users/geofrancis/orgs","repos_url":"https://api.github.com/users/geofrancis/repos","events_url":"https://api.github.com/users/geofrancis/events{/privacy}","received_events_url":"https://api.github.com/users/geofrancis/received_events","type":"User","site_admin":false},"labels":[{"id":410742763,"url":"https://api.github.com/repos/bortek/EZ-WifiBroadcast/labels/enhancement","name":"enhancement","color":"84b6eb","default":true}],"state":"closed","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":3,"created_at":"2017-05-18T13:40:40Z","updated_at":"2017-10-21T15:07:22Z","closed_at":"2017-10-21T15:07:22Z","author_association":"NONE","body":"as well as the main telemetry link that the osd works from, having some more transparent uarts would be very useful for people with gimbals, RTK gps, multiple telemetry links like frsky and mavlink or other devices that use serial ports, currently the only solution out there is to have multiple telemetry radios. wifibroadcast video uses so much bandwidth that 3x 115200 serial links should be barely noticeable \r\n\r\nIn theory it could also be used for transparent RC links. then you wouldn't have to worry about generating the rc output, you should just need the correct baud rate for the protocol so what comes in goes out. for failsafe you just stop the output simulating rc disconnect, most flight controllers will just see that as out of range and failsafe without having to configure anything.\r\n\r\nsbus is 100,000\r\ndsm and sumd is 115200\r\n\r\n\r\njust have something in the config like:\r\n\r\nTX\r\ntelemetry/osd port: /dev/ttyUSB0\r\nbaud1: 57600 \r\nserial2: /dev/ttyAMA0\r\nbaud2: 100000 (for sbus, 115200 for DSM, SUMD, MSP or 57600, 38400, 9600. )\r\nserial 3 /dev/ttyUSB1\r\nbaud3 115200\r\n\r\nRx \r\n\r\ntelemetry/osd port: /dev/ttyUSB0\r\nbaud1: 57600 \r\nserial2: /dev/ttyS0 (or \"USB\" for MSP)\r\nbaud2: 100000  (for sbus, , 115200 for DSM, SUMD,MSP or 57600, 38400, 9600. )\r\nserial 3 /dev/ttyUSB1\r\nbaud3 115200\r\n\r\n\r\nAnother idea would be to use different wifi adapters for video and telemetry, then you could have your data on 2.4ghz and video on 5ghz or just on different channels and it would avoid the problem of having to stop the video tranmitter to receive.\r\n\r\nbecause each serial connection can have its inputs and outputs setup and is standardised it would be very flexable, you could have 3 telemetry links or theoretically up to 48 channels using 3 rc links, plus there is no real limit to the number of serial links apart from the number of usb ports you have and bandwidth, but if you got the data on a different adapter it would be a lot.\r\n"}}
{"actor":{"display_login":"rodizio1"}}