Jan Spacil
lvl.4
Czechia
Offline
|
I updated the fw in M4P yesterday, it was an interesting experience.
It was my second update of M4P, the first one was right after I bought the M4P. I updated both the drone and RC2 and everything went fine.
Yesterday I tried to update the drone to the latest version from 08/11. I placed the drone in a place with active cooling (although the drone switches to ECO mode during the update) to eliminate any overheating problems (a good place with ventilation is the top of a Xiaomi air purifier).
The RC2 was connected to a fast WLAN, the update started, and at about 40% through the update the progress stopped and a while later a message about failed update appeared, with instructions to reboot the device and repeat the update process.
So I turned the drone off and on, but the drone didn't connect to RC2 anymore. I also tried re-pairing according to the instructions, the drone was switched to pairing mode, but did not connect.
I turned both devices off and on several times and set the drone in the pairing mode, the result was the same.
I thought that the interrupted update had corrupted the fw in the drone and that a warranty claim would be necessary... And then I thought to turn on the Bluetooth in RC2 and try to search for the drone. And indeed it appeared in the device list.
When I tried to pair via Bluetooth, the drone probably didn't connect. Still, when I tried 'normal pairing' again in RC2, fortunately, the video signal from the drone's camera had already started to transfer to RC2 and everything was connected fine.
As a result, I ran the fw update again in the drone, the data was already downloaded, so the update process started at 40% and went through to the end fine.
Maybe this will help someone if they find themselves in a similar situation. |
|