I am being told on another forum that latest FW along with latest GO (Phantom 3 Pro) means you MUST have latest RC version 1.9.2 installed.
Their reasoning is that they claim you can suffer strange warnings and limits happening while flying - that the 50 / 30m limits may action during flight if the RC is installed with earlier Controller FW.
I'm not so convinced as DJI tech remarked to me when I took my P3P for repair that 1.6 Controller FW was better and worked fine.
So lets say a system is :
AC FW 1.11.20
RC FW 1.6.X
Go : 3.1.43
is that so bad ?
Before the deluge of ******* ... my P3P is on
AC FW 1.11.20
RC FW 1.9.2
Go : 3.1.43
And I have had some weird warnings of 50 / 30m during a couple of flights recently. This has happened with my old and new controller. I am tending to think it may have something to do with the Micro USB ports used on Android - which do have a tendency to become 'sloppy' .... Why do I think this ? having tested the lack of GO during flight and its limiting to 50 / 30m ... I wonder if DJI have extended this to action if GO stops working mid flight ? Previously it only actioned if you powered up without GO.
Anyone have real info on this ? So far no-one has been able to state clearly and confirmed ... just conjecture.
Nigel
Their reasoning is that they claim you can suffer strange warnings and limits happening while flying - that the 50 / 30m limits may action during flight if the RC is installed with earlier Controller FW.
I'm not so convinced as DJI tech remarked to me when I took my P3P for repair that 1.6 Controller FW was better and worked fine.
So lets say a system is :
AC FW 1.11.20
RC FW 1.6.X
Go : 3.1.43
is that so bad ?
Before the deluge of ******* ... my P3P is on
AC FW 1.11.20
RC FW 1.9.2
Go : 3.1.43
And I have had some weird warnings of 50 / 30m during a couple of flights recently. This has happened with my old and new controller. I am tending to think it may have something to do with the Micro USB ports used on Android - which do have a tendency to become 'sloppy' .... Why do I think this ? having tested the lack of GO during flight and its limiting to 50 / 30m ... I wonder if DJI have extended this to action if GO stops working mid flight ? Previously it only actioned if you powered up without GO.
Anyone have real info on this ? So far no-one has been able to state clearly and confirmed ... just conjecture.
Nigel