LuvMyTJ
Admin
Be sure you test this out in the field or outside of your house. The wifi overload in my house causes connection issues with the Autel, but outside it is all good.I just cant get a video connection no matter what.
Be sure you test this out in the field or outside of your house. The wifi overload in my house causes connection issues with the Autel, but outside it is all good.I just cant get a video connection no matter what.
Be sure you test this out in the field or outside of your house. The wifi overload in my house causes connection issues with the Autel, but outside it is all good.
Thanks, I appreciate the response.So far all you do is download the current beta and apply. Autel does not archive the files.
Trust me, I have. For what it's worth I did my initial setup in my house and everything was fine until the other day. Also, the error occurred/began when I was outdoors and pretty far from any kind of man made interference (at least that I could see).
It really sounds like you have an RF problem on the video link....in fact exactly like the issue I had, namely a bad 900 MHz antenna. Your downlink video receiver in the controller is looking at mostly noise because the video signal is probably down 30 or 40 dB due to a break in the xmitter antenna. Send it back in for repair if you haven't already.
Yeah when I read your post I thought it might be similar. I could literally touch the drone with my antenna and I still couldn't get video link. It's been over a week since I sent it in, and for what it's worth the customer service in terms of response has been great, but I'm still pretty bummed because I'm missing out on a few really cool shoots this weekend![]()
Testing beta does not affect your warranty. Autel has made many statements about this.
No one seems to know when it will be final. Guessing if this fixes the orbit jerky video then this might be final. Most likely they will let this run for a few weeks and see if anymore problems pop up.
Really? Found this on the beta sign up page
The user understands that the component/drone covered by this agreement have not been fully developed and may cause unknown problems or defects. The user agrees to accept all damage and risk and will hold Autel Robotics and its companies harmless.
Really? Found this on the beta sign up page
The user understands that the component/drone covered by this agreement have not been fully developed and may cause unknown problems or defects. The user agrees to accept all damage and risk and will hold Autel Robotics and its companies harmless.
3) As the firmware is in beta release users should not use the beta firmware for commercial purposes. Autel Robotics cannot be held responsible for any losses, direct or indirect as a result of using beta firmware.
Personally, I prefer them have a perfect working FW before just sending out any old thing as a final version. Once final, this FW will be on EVERY new XSP produced in the future. They understandably want a stable product across all features.I'm increasingly concerned and frustrated about this mode that Autel is in where they just keep issuing beta releases instead of committing to an official release.
From the terms and conditions:
If you are a commercial user, I would think long and hard before using the beta firmware. Autel may be honoring the warranty, and that's great, but if you have an accident/incident that causes property damage or injury as a commercial operator, your insurance will likely be a different animal. Or you can just hope you don't have any accidents, and if you do, hope the insurance company doesn't start asking about firmware. Insurance companies thrive on finding ways to avoid paying for claims. As long as this firmware stays beta, commercial operators who are using it are essentially uninsured, even if they think they are.
This issue is the main reason why I'm still operating on ver 1.2.8, and why I'm increasingly concerned and frustrated about this mode that Autel is in where they just keep issuing beta releases instead of committing to an official release.
Personally, I prefer them have a perfect working FW before just sending out any old thing as a final version. Once final, this FW will be on EVERY new XSP produced in the future. They understandably want a stable product across all features.
From a FAA person.
Current by FAA definition is what it left the manufacture at or what ever the operator choses to update it to.
"Current" is interesting legal interpretation hard to explain on FB. Either version "could" be current.
The legal interpretation of "current" came out in 2007. Directly from an FAA employee that belongs and owns a Auel X-star on the OFFICIAL Autel Robotics Owners facebook page.
Steve Meisner
View attachment 1453
We use essential cookies to make this site work, and optional cookies to enhance your experience.