{"action":"created","issue":{"url":"https://api.github.com/repos/iNavFlight/inav/issues/3919","repository_url":"https://api.github.com/repos/iNavFlight/inav","labels_url":"https://api.github.com/repos/iNavFlight/inav/issues/3919/labels{/name}","comments_url":"https://api.github.com/repos/iNavFlight/inav/issues/3919/comments","events_url":"https://api.github.com/repos/iNavFlight/inav/issues/3919/events","html_url":"https://github.com/iNavFlight/inav/issues/3919","id":368786953,"node_id":"MDU6SXNzdWUzNjg3ODY5NTM=","number":3919,"title":"Matek F411-Wing: 2 soft serial ports....please!","user":{"login":"Wcallahan01","id":37713550,"node_id":"MDQ6VXNlcjM3NzEzNTUw","avatar_url":"https://avatars2.githubusercontent.com/u/37713550?v=4","gravatar_id":"","url":"https://api.github.com/users/Wcallahan01","html_url":"https://github.com/Wcallahan01","followers_url":"https://api.github.com/users/Wcallahan01/followers","following_url":"https://api.github.com/users/Wcallahan01/following{/other_user}","gists_url":"https://api.github.com/users/Wcallahan01/gists{/gist_id}","starred_url":"https://api.github.com/users/Wcallahan01/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/Wcallahan01/subscriptions","organizations_url":"https://api.github.com/users/Wcallahan01/orgs","repos_url":"https://api.github.com/users/Wcallahan01/repos","events_url":"https://api.github.com/users/Wcallahan01/events{/privacy}","received_events_url":"https://api.github.com/users/Wcallahan01/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":13,"created_at":"2018-10-10T18:09:51Z","updated_at":"2018-11-03T11:41:57Z","closed_at":null,"author_association":"NONE","body":"## Current Behavior\r\nMatek F411 target only allows for 1 soft serial port. This applies to both the Matek F411 mini and the F411-Wing boards...same issue with both boards in Inav. In BF the user can resource map and get 2 soft serial ports. FRsky Sport users really need the extra serial port so they can have GPS, Sbus, Sport & Smart audio connections.\r\n\r\nThe current target mapping typically requires choosing between Sport and Smart audio when configuring. This sacrifice doesn’t seem necessary if BF allows for mapping of 2 soft serial ports. I’m not an expert, but it seems possible if the 2nd soft serial was mapped to a pinout like they do in BF.\r\n\r\n## Desired Behavior\r\nAdd target with support for 2 soft serial ports (this is possible using resource mapping in BF already)\r\n\r\n## Suggested Solution\r\nAdd target with support for 2 soft serial ports (this is possible using resource mapping in BF already.)\r\n\r\nMaybe remap to have Soft Serial 1 on ST1 and the extra soft serial 2 on the S7 pad? The S7 pad might be an ideal option since all plane and quad configurations are possible without it. It’s only needed if the user is doing a pan/tilt or similar function. Besides if your doing pan/tilt, flaps or similar you’d likely want the F405-Wing board anyways. The F411-Wing seems to be primarily installed on smaller flying wings anyways.\r\n\r\n<!-- NOTE: Feature Requests without suggested solutions may not be addressed with the same level of urgency as those that have suggested solutions -->\r\n\r\n## Who does this impact? Who is this for?\r\nAll F411 users and the F411-Wing board is becoming very popular lately!\r\n\r\n## Additional context\r\n"},"comment":{"url":"https://api.github.com/repos/iNavFlight/inav/issues/comments/435581337","html_url":"https://github.com/iNavFlight/inav/issues/3919#issuecomment-435581337","issue_url":"https://api.github.com/repos/iNavFlight/inav/issues/3919","id":435581337,"node_id":"MDEyOklzc3VlQ29tbWVudDQzNTU4MTMzNw==","user":{"login":"Wcallahan01","id":37713550,"node_id":"MDQ6VXNlcjM3NzEzNTUw","avatar_url":"https://avatars2.githubusercontent.com/u/37713550?v=4","gravatar_id":"","url":"https://api.github.com/users/Wcallahan01","html_url":"https://github.com/Wcallahan01","followers_url":"https://api.github.com/users/Wcallahan01/followers","following_url":"https://api.github.com/users/Wcallahan01/following{/other_user}","gists_url":"https://api.github.com/users/Wcallahan01/gists{/gist_id}","starred_url":"https://api.github.com/users/Wcallahan01/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/Wcallahan01/subscriptions","organizations_url":"https://api.github.com/users/Wcallahan01/orgs","repos_url":"https://api.github.com/users/Wcallahan01/repos","events_url":"https://api.github.com/users/Wcallahan01/events{/privacy}","received_events_url":"https://api.github.com/users/Wcallahan01/received_events","type":"User","site_admin":false},"created_at":"2018-11-03T11:41:57Z","updated_at":"2018-11-03T11:41:57Z","author_association":"NONE","body":"Awesome!!! Thank you Sir!\n\n> On Nov 2, 2018, at 9:43 PM, Curtis Menard <notifications@github.com> wrote:\n> \n> It will be available in iNav 2.1. Until then here is a link for a 2.01 build that has the recent GPS fixes in it.\n> \n> https://drive.google.com/file/d/1MKkmMg1P8BFyMYkoHgo4U1JT4sI-__zO/view?usp=sharing\n> \n> —\n> You are receiving this because you authored the thread.\n> Reply to this email directly, view it on GitHub, or mute the thread.\n"}}
{"actor":{"display_login":"Wcallahan01"}}