Enabling serial 2 for telemetry breaks gimbal

[falense]

Hi!

We are developing a payload for the 3DR Solo that requires telemetry access to the Pixhawk. By enabling SER2 (on the accessory port), first by creating /fs/microsd/APM/uartD.en and then setting parameter SERIAL2_PROTOCOL to 1. The gimbal pitch control stops working.

Is the SER2 port on the accessory bay somehow connected to control of the official gimbal?

Hope to hear from you soon.

In advance thanks

[falense]

No, nothing short of dkwngrading2 firmware unfortunately

…

On Wed, Aug 21, 2019, 01:51 NiharikaPatel ***@***.***> wrote: @Sondree <https://github.com/sondree> did you ever find a way around this? I have the same issue. Thanks — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#292?email_source=notifications&email_token=AARMAWOCXPP72AMRGMMIEE3QFR7RVA5CNFSM4B4KAEPKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD4X74XA#issuecomment-523239004>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AARMAWKES6NBZQ4IF2VQKGDQFR7RVANCNFSM4B4KAEPA> .

[NiharikaPatel]

Hi @Sondree It seems like my previous comment got deleted
"@Sondree did you ever find a way around this? I have the same issue.
Thanks"
But thank you for you response. I currently have Open Solo. Which firmware did you downgrade to for it to work?

[falense]

On the official firmware 2.3.0-1 is the last before it breaks integration. On the top of my head I dont remember which ardupilot firmware that corresponds to. Are you saying that even with the open ardupilot fork serial is broken for later releases? Please be aware that Serial2 has to be enabled both through serial in the flight controller shell and through a mavlink param to work.

…

On Thu, Aug 22, 2019, 02:07 NiharikaPatel ***@***.***> wrote: Hi @Sondree <https://github.com/sondree> It seems like my previous comment got deleted ***@***.*** <https://github.com/sondree> did you ever find a way around this? I have the same issue. Thanks" But thank you for you response. I currently have Open Solo. Which firmware did you downgrade to for it to work? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#292?email_source=notifications&email_token=AARMAWNGIGRJG4HKPOPRGNLQFXKELA5CNFSM4B4KAEPKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD43PH2A#issuecomment-523695080>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AARMAWJ2AKJITDKP7ZRHAITQFXKELANCNFSM4B4KAEPA> .

[falense]

To clarify, firmwares after 2.3.0-1 breaks Serial2 altogether. I have not been able to use the gimbal on any firmware releases while having Serial2 enabled. Related issue being that later firmwares disable access to Serial2 ons. 21. aug. 2019 kl. 01:51 skrev NiharikaPatel <[email protected]>:

…

@Sondree <https://github.com/sondree> did you ever find a way around this? I have the same issue. Thanks — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#292?email_source=notifications&email_token=AARMAWOCXPP72AMRGMMIEE3QFR7RVA5CNFSM4B4KAEPKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD4X74XA#issuecomment-523239004>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AARMAWKES6NBZQ4IF2VQKGDQFR7RVANCNFSM4B4KAEPA> .

[NiharikaPatel]

Hi @Sondree we updated to Open Solo and then AC3.7 dev and everything seems to work fine now. We are able to use Serial2 to connect it to our Rpi and the gimbal still works even after changing the SERIAL2_PROTOCOL to 1

[falense]

Nice to know! Thanks for the update

…

On Tue, Aug 27, 2019, 02:50 NiharikaPatel ***@***.***> wrote: Hi @Sondree <https://github.com/sondree> we updated to Open Solo and then AC3.7 dev and everything seems to work fine now. We are able to use Serial2 to connect it to our Rpi and the gimbal still works even after changing the SERIAL2_PROTOCOL to 1 — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#292?email_source=notifications&email_token=AARMAWMTBMPPVJF7XR4NPVLQGR25HA5CNFSM4B4KAEPKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD5GDSRY#issuecomment-525089095>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AARMAWM2E45HHUHHZSYS3A3QGR25HANCNFSM4B4KAEPA> .