DOA

[deville1968]

One of the first Dual 640T in Germany arrived today . "Gimbal not ready" messages and no Camera settings possible

Frustrating, but sht happens

 

[advexure]

Have you tried uninstalling and reinstalling the Explorer app on the device you are using? We have seen this specific error occur and it was app related.

 

[deville1968]

I have used a device which was already in use for another device ( 6k ) . But I could try another device

 

[Third Eye View]

I get this setting mostly all the time when the EVO is sitting on uneven surfaces during startup. I simply pick up the unit and place it in another position and that will clear the error message and she takes off!!

 

[deville1968]

Tried moving to another surface also a couple of times (as this was described when I searched about that error) , does not make any difference. Connected now another device also. No luck. I will get it replaced

However, the camera is still working (just no settings possible , and "N/A in all below settings in the menu) but what I see so far already is stunning

 

[Third Eye View]

Tried moving to another surface also a couple of times (as this was described when I searched about that error) , does not make any difference. Connected now another device also. No luck. I will get it replaced

However, the camera is still working (just no settings possible , and "N/A in all below settings in the menu) but what I see so far already is stunning

I am guessing that you have already done a full calibration.... I hope that it is replaced if you cannot get it to operate properly. Did you contact Autel by phone??

 

[deville1968]

No. I will get it replaced by the German Main Distributor. So no worries, just loosing some time for my project

 

[RetArmy]

No. I will get it replaced by the German Main Distributor. So no worries, just loosing some time for my project

Which firmware version? If its 2.5 go the downgrade to 2.3.3. Were alot of dumb gimbal issues in 2.5.

 

[deville1968]

Yes, I heard about them. Unfortunately the problem did exist from the beginning (it was delivered with 2.3.3 ) . I then upgraded to 2.5. and the problem is exactly the same