When loaded from the AC master (last tried with http://firmware.ardupilot.org/Copter/2018-05/2018-05-04-11:05/skyviper-v2450/) the skyviper will not stay bound to the transmitter. It'll bind for a few seconds, and then at random intervals will lose, and you have to do a bind action again.
http://firmware.ardupilot.org/Copter/2018-05/2018-05-04-11:05/skyviper-v2450/
[ ] All
[ ] AntennaTracker
[ X ] Copter - Skyviper
[ ] Plane
[ ] Rover
[ ] Submarine
Skyviper
stock Skyviper hardware
The logs don't appear to show the unbinding. Even Tower HUD didn't report a RC Failsafe when it occurred.
Here is the log from when it happened, but i dont' see anything.
https://drive.google.com/open?id=1Zc0WMloyNs7vRgUx6INL1uWOKMeuaHiv
I agree this is a bug. Easy to reproduce : compile master and load it on skyviper the radio won't keep blinking ... The official firmware is working well.
I am pretty sure it was working before https://github.com/ArduPilot/ardupilot/commit/bccea9c8b933e281629b905d43ef7fceaf370eb4 ,I tried to revert it but it doesn't fix the problem. But I am pretty confident that the problem is around that time . On april 12th it the bug was already there (asked for confirmation but nobody anwser)
The last "master" that i tried before trying the one earlier was March 22 (not sure exactly which CI build i used). But that one worked just fine with absolutely no issues. Randy made a Blog post about it being available in master a few days later and that's when he updated the wiki as well.
nice ! So the error should be between march 22th and april 12th !
Can confirm this issue, with ArduCopter 3.6.0-rc1 ChibiOS build.


@mirkix, with skyviper?
edit: yep start in toy mode so skyviper
the problem was fix for me on today master (https://github.com/ArduPilot/ardupilot/commit/f3179e7934f70158d19a261c1529cafb83ccc156)
What compiler where you using ? I wonder if wasn't caused by a problem with the #ifdef AP_RADIO macro that we correct recently !
@lordneeko @mirkix could you confirm that it is working on master in order to close the issue ?
I'm out of town for a while. Can't confirm until I get back. I think there
were others that confirmed the bug as well
On Tue, May 22, 2018, 9:03 AM Pierre Kancir notifications@github.com
wrote:
the problem was fix for me on today master (f3179e7
https://github.com/ArduPilot/ardupilot/commit/f3179e7934f70158d19a261c1529cafb83ccc156
)
What compiler where you using ? I wonder if wasn't caused by a problem
with the #ifdef AP_RADIO macro that we correct recently !@lordneeko https://github.com/lordneeko @mirkix
https://github.com/mirkix could you confirm that it is working on
master in order to close the issue ?—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/ArduPilot/ardupilot/issues/8305#issuecomment-390981606,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ALCovZLtyy6eojyJP-5sKu9JCU62_Adfks5t1AymgaJpZM4TzSgy
.
@khancyr I will check it the next days with a testflight, but so far it seems to be solved. Tested only inside my lab.
I flew the v2450 tonight for quite a while on the latest master and had no transmitter issues. I think this can be closed. However I want to open a discussion in the discuss about how I could do a PR to update default parameters in !aster for the SV. It has a lot of alarms going off because of the new battery params and such. I'd like to fix those for future users.