fans76b622a7
lvl.3
Flight distance : 121112 ft
United States
Offline
|
djiuser_B9FYuvkDZ89c Posted at 1-1 02:34
For me, the random disconnects when using RC Pro has made the M3 experience just too risky when using that controller.
When using the RCN1 I have no issues at all, so this has to be hardware & firmware related.
I also have experienced random disconnects using the RC Pro. In addition, after completing a cold boot, it takes 1 1/2 to 2 minutes for the aircraft to connect to the RC Pro. The RCN1 connects within 10 seconds after completing cold boot.
I opened a ticket with DJI a week ago, received the usual "Robot" replies about checking the F/W, refreshing the F/W and then I was forwarded to a higher level of service (Bwaaaaa)
After explaining the issues I was told to provide my mailing address, they wanted me to send back so they could analyze. I provided my mailing address, a day later received another email stating it was normal for the aircraft to take 2 minutes to connect after a cold boot.
Replied back, show me a document that states 2 minutes is normal, also advised I find this hard to believe as my friend has the CIne version. We went flying the other day, his aircraft connected within 10 seconds after completing a cold boot. He was flying while I was waiting for my aircraft to connect to the controller.
I have sent two emails back to DJI service requesting they replace my RC Pro but have not heard back. I also asked to be connected to his Supervisor.
I bought the RC Pro from DJI direct, had I bought from B&H I could have received a replacement by now.
This has been an expensive lesson, will NEVER buy anything direct from DJI again.
|
|