No Attitude Data I have had a very unhappy experience with Autel Robotics Support. They have a deservedly good reputation and are generally quick to respond to problems. They failed this time. Here is the timeline: Sat 11/05 - I flew the X-Star several times with not problems. This is my last landing: Sun 11/06 - I tried to DL flight logs and failed then I noticed that the X-Star would not boot at all. When powered up, the X-Star goes directly into an error mode, with all four LEds flashing red and continuous beeping. The X-Star manual says that this "Indicates hardware problems possibly caused by IMU deviation or other abnormalities." Mon 11/7 (02:00am) - I reported the problem to firstname.lastname@example.org I was trying to read the flight logs, using the Advanced Flight Controls, then clicking of Read. The X-Star never showed up as a drive, though the X-Star did go into the read flashing/beeping mode. I tried a couple of times without success, then I noticed that Starlink was displaying an error message, “No attitude data - Gimbal is entering sleep mode” The “IMU Warming Up” message shows on Starlink as a steady message. I flew Saturday without any problems. Mon 11/07 10:17am - Autel I was asked some questions including "does the "IMU Warming Up" message continue to display during flight or does it go away?" Wed 11/09 12:43am - Me: Has the IMU failed? That’s what the symptoms suggest. The X-Star is not flyable. Thu 11/10 01:31am - Me Do you have any information about what I can do to get the X-Star flying again? Thu 11/10 11:44am - Autel replies I'm going over your issue with one of our technicians. Once I speak with him, I'll let you know what I find out. Thu 11/10 11:44am - Autel replies How may times have you tried to get the IMU to warm up? When you do try to warm up the IMU, how long do you wait? Have you had any hard landings or incidences? Have you had any successful flights? What do the LEDs display during the IMU is warming up when you first power on the aircraft? Note - some of these questions seem to indicate a lock of familiarity with the meaning of the error messages. Thu 11/10 02:33pm - Autel replies I've spoken with the technicians and they have given me a firmware file that they would like you to upload to your aircraft. <Instructions follow, but there was no attachment of Firmware. Thu 11/10 07:30pm - Me I did not get an attachement. I also called in hopes that I could get this resolved quicker, but they were not answering the phone even thought if was before 6pm PST. Fri 11/11 10:45am - I call Autel re the missing attachment Fri 11/11 11:13am - Autel Sent email with X3P_FW_V1.08.42.bin firmware I started just the X-Star (no remote) with the firmware and waited 10 minutes each time for the lights to stop. There was no change. Still beeping with red flashing lights. Fri 11/11 11:52am - Me Reported that there had been no change and mentioned that I did not think the Firmware would load because the version # was lower than that on the X-Star, 1.2.8. Sat 11/12 10:11am - Autel Ok. That was a different patch. I will have to talk with the technicians on Monday, but it sounds like you will need to have it sent in for repair. Most likely it will be under Warranty but I won't know that until I speak with my manager on Monday. Mon 11/14 11:25am - Me It has been over 7 days since I reported this problem. Has there been any progress? Tue 11/15 06:28pm - Autel I've talked it over with the technicians. I described what has been going on and they would like to have you send in your aircraft for an Evaluation for Warranty Service. Would you be interested in having that done? Wed 11/16 01:30am - Me "Yes" - Autel should have sent me what I needed to know to start this process withouyt this exchange - another day wasted Wed 11/16 10:17am - Autel As we've discussed, you will be sending in your aircraft for an Evaluation for Warranty Service. This means that the technicians will take a good look at the aircraft, run it through some tests and pull the flight logs to find out exactly what happened. From there, they will be able to determine if the repairs will be under your warranty or if it will need to be a paid service. Just to let you know, there is a 14-day turnaround time on our repair line. Adding the time for your package to arrive in the greater Seattle area and back to you, that will give you some kind of idea on how long it will take. <This email cinluded a list of information that they needed for the RMA> Wed 11/16 06:51pm - Me I would have really liked to have started this process a few days after I reported the problem, i.e, a week ago. Will the automated email include instructions? Do I ship just the X-Star? The Remote? Battery? Wed 11/16 06:54pm - Autel <Requested Proof of Purchase which I had overlooked> Wed 11/16 08:02pm - Me Sent Invoice Thu 11/17 11:59am - Autel Thank you for that information. The RMA should be coming to you shortly. Thu 11/17 11:59am - Autel RMA was provided. However the RMA says "Reason for Returning: Crash/Damage while flying" "Action Requested: Paid Repair" Fri 11/18 02:44am - Me sent to Sr. Tech Support Manger I reviewed some of the email traffic and showed the incorrect RMA I was concerned that I sent the X-Star using this RMA, then I was agreeing that it had been crashed and Iwas requesting "Paid Repair" so I sent: "Both the Return Reason and the Requested Action are incorrect. The X-Star never crashed and the action requested was Evaluation for Warranty Service. Please send me a correct RMA." Fri 11/18 02:45am - Autel Ticket Received.... My email included the earlier ticker # so I was puzzled by this. Fri 11/18 02:55pm - Autel Sr. Tech Support Manger for Autel Robotics - will look into this and get back ASAP Attempted to call me It has been two weeks since the problem first occurred. With shipping times and the 2-week turnaound for repairs I suspect that I will not have a functioning X-Star sooner than 5 weeks after the X-Star failed. I think I should have had a valid RMA before 11/10.