SKYVIPER JOURNEY cannot BIND transmitter after firmware update

[patrickpoirier51]

Just builded a new firmware for the Journey
Your branch is up-to-date with 'origin/master' as of
./waf configure --board skyviper-f412
./waf build --target=bin/arducopter

uploaded the arducopter.abin file using web interface
the unit restart OK , can load in mission planner

Cannot bind radio according to procedure
http://ardupilot.org/dev/docs/skyviper.html#force-bind-a-transmitter
Go in status - radio - bind & Push Launch Button while powering transmitter
Tried DSMX option and binding with right button on TX

Reverted to Latest SKYVIPER Journey Firmware:
arducopter-2018-07-14.abin
ALL OK

[rmackay9]

I suspect this is one for @tridge

[patrickpoirier51]

Matt is suspecting a radio binding check not in place https://discuss.ardupilot.org/t/sky-viper-journey-transmitter/37727/17

[patrickpoirier51]

It seems there is some overlap between the SCOUT and the JOURNEY as the OpticalFlow is enabled by default and Journey do not have the pixart
https://github.com/ArduPilot/ardupilot/blob/master/libraries/AP_HAL_ChibiOS/hwdef/skyviper-f412/hwdef.dat#L89
https://github.com/ArduPilot/ardupilot/blob/master/Tools/Frame_params/SkyViper-F412/defaults.parm#L238

[lordneeko]

Possibly related to a previous bug
#8305

[patrickpoirier51]

That was related to the 2450 ,note that what I reported above is an issue with the Journey skyviper-f412, and it is not binding at all.