12262015 Update:
Ok, Dji posted the 1.6.0.40 update (2015.12.22) which only has battery thermal updates, nothing new on FOLLOW ME function. So, I did another flight test to prove it. FOLLOW ME still performs erratically when in dual controller mode!! It will perform with a single controller.
Sidenote: the DJI Release notes show the "All-in-One" firmware update to be v1.6.0.40 and the IOS version to be v2.4.2 but after the firmware installation my IOS version went to 2.4.3. Did anyone else running an IOS get these results?
12082015 Update
Ok, I just upgraded my I1 to the latest DJI software package and here is what I have installed: APP 2.4.2, AC 1.5.0.30, RC 1.5.70 and Camera 1.5.0.30. So after this update I did some test flights with POI and Follow Me. The POI worked as expected, set point at 10 meters and radius at 5 meters and would not let me fly below the set limits. I'm OK with that. But as soon as I switched to Follow Me, the I1 went erratic, side to side and rotating uncontrollably. And Yes, I was in a clear open space away from high power lines. Immediately switched to "P" mode and landed. When I called DJI tech support I told them I was running the latest firmware update (1.5.0.30 with dual controllers), they said they have never heard of this issue.
Has anyone seen this before or know what is causing it? Plan to test fly Follow Me again today. Will post results and hope it is not a crash report.
12102015 Update
So, testing dual controller today! Started with just a single controller (After successful POI) and Follow Me worked as advertised. However it was very slow to respond to changes in movement of the controller. Having said that I was flying very low like 5 meters and running in multiple directions. Inspire tried to keep up, but was jerky and slow. Now, turned on the SLAVE controller and everything went erratic, just like the first time. So, quick switch to GPS-P mode and land immediately. ALL of these symptoms seem to support DJI's SDK functions for Follow Me are flawed. I think it is too early to rule out the new POI.
Ok, Dji posted the 1.6.0.40 update (2015.12.22) which only has battery thermal updates, nothing new on FOLLOW ME function. So, I did another flight test to prove it. FOLLOW ME still performs erratically when in dual controller mode!! It will perform with a single controller.
Sidenote: the DJI Release notes show the "All-in-One" firmware update to be v1.6.0.40 and the IOS version to be v2.4.2 but after the firmware installation my IOS version went to 2.4.3. Did anyone else running an IOS get these results?
12082015 Update
Ok, I just upgraded my I1 to the latest DJI software package and here is what I have installed: APP 2.4.2, AC 1.5.0.30, RC 1.5.70 and Camera 1.5.0.30. So after this update I did some test flights with POI and Follow Me. The POI worked as expected, set point at 10 meters and radius at 5 meters and would not let me fly below the set limits. I'm OK with that. But as soon as I switched to Follow Me, the I1 went erratic, side to side and rotating uncontrollably. And Yes, I was in a clear open space away from high power lines. Immediately switched to "P" mode and landed. When I called DJI tech support I told them I was running the latest firmware update (1.5.0.30 with dual controllers), they said they have never heard of this issue.
Has anyone seen this before or know what is causing it? Plan to test fly Follow Me again today. Will post results and hope it is not a crash report.
12102015 Update
So, testing dual controller today! Started with just a single controller (After successful POI) and Follow Me worked as advertised. However it was very slow to respond to changes in movement of the controller. Having said that I was flying very low like 5 meters and running in multiple directions. Inspire tried to keep up, but was jerky and slow. Now, turned on the SLAVE controller and everything went erratic, just like the first time. So, quick switch to GPS-P mode and land immediately. ALL of these symptoms seem to support DJI's SDK functions for Follow Me are flawed. I think it is too early to rule out the new POI.
Last edited: