- Sep 1, 2016
- Reaction score
I have checked that the time and zone are correct and I don't think it's ever on when there's not Wi-Fi available but I don't doubt that's the case because it has always been. It was actually the first barrier of using the H520 data in during the flight. They had to alter their code to compensate for it. Apparently it changed again with the E model so we've had to tweak it again.This is unfortunately "normal" I was told when changing the ST16's battery without being connected to a WLAN (no network time). The time has to be set manually...
I had this too with the H520 E90. I don't know if it still is a problem but generally for me it worked best when having an mSD card inside the e90 that already has its folder structure and a "number-0001"-dummy-image as a "template" alreday in the images folder...Using the E90X we are 24 flights in now and we have had 3 occasions where the mSD wasn't recognized
that is what I suspect, too.trying to hit the exact coordinate of the turn waypoint
Just a question: is the X/Y-error greater the further the H520-Rover-GPS-antenna is away from the base station GPS-antenna. (I thought you were using onboard NTRIP only).Both are receiving the same corrections via NTRIP but as an example on one of the maps the east checkpoint moved about 1ft further to the east than the west checkpoint did.
Same here. I haven't had it on the H520 for a long time. I also format the card on the drone every time before I fly. I'll have to pay better attention next week to see the consistency and whether or not the formatting changes the behavior.I had this too with the H520 E90. I don't know if it still is a problem but generally for me it worked best when having an mSD card inside the e90 that already has its folder structure and a "number-0001"-dummy-image as a "template" alreday in the images folder...
Almost every time I try to format the mSD card on site (only when missioning testwise) something strange happens:
- counting images on the ST16 UI but no images are later on the mSD card (not a single one present).
- not counting images on the ST16 UI but all images are on the mSD card (not a single one missing).
I only use 64GB exFAT cards from sandisk.
If you are using a base station that communicates directly to the aircraft then yes you will lose thousandths as you move hundreds of feet away from the base. Not just the absolute accuracy but the stability of the RTK fix starts to become an issue. If you have your own base and you cast it then you have the same condition as NTRIP and are only limited to your proximity to the CORS. This is why VRS is such a good option for long roving.that is what I suspect, too.
Just a question: is the X/Y-error greater the further the H520-Rover-GPS-antenna is away from the base station GPS-antenna. (I thought you were using onboard NTRIP only).
I "learnt" or "heard" that base/rover-data is always handled relatively. So H520 RT positioning and the images' EXIF GPS values are only absolute if you use onboard-NTRIP-RTK-only.
Hi,It stays pretty consistent at a certain point if you're using GCP's but if you don't use GCP's it will continue to float up. I don't think I've done anything large enough to say definitively whether or not it hits a static point.
This was the first question I asked before getting the H520E RTK. I was assured it does use the offset and aircraft attitude data to write the correct geotag values and not just the position of the antenna. This is why they also provide the timestamp file for PPK use. It contains all the relevant attitude data necessary to make those calculations after the fact.Hi,
have you seen this already (?):
It is really a "deep dive" into this topic. Hopefully the H520E-RTK gets all the stuff "aligned" as well. Especially the "Time Sync subject" of acurately syncing the camera position below the flying GNSS antenna (rover) with the actual exposure time of the projected image plane is a challenge...
ThanksssBe assured that we'll get it figured out. The same thing happened with the P4RTK and it took us 3 months to get a proper workflow figured out. I can promise you that I won't let up until they show the effort. Supposedly they already have a group in Oklahoma that is doing it successfully. That's all I can share for now but I will update later.
I am having the same problems. This drone should be able fly further with no problems but I keep getting lost video feeds and control issues. I was hoping the OFDM update would solve some if the problems.View attachment 25358
The other threads seemed to be going a slightly different direction so I decided to start this new thread for practical experience on unboxing through troubleshooting, configuration and firmware updates. I will be using the E90X camera.
I finally got everything in from Vertigo and am starting configuration and testing today. First issue I have hit is that I have no control of the E90X. It starts correctly, centers and can even be calibrated, but the RC input is not doing anything. (UPDATED) Maybe it was just the act of a reflash, but going from E90X v1.0.74_A to v.1.0.75_A and we now have RC control of the camera. Interesting thing is that the updates according to the RC report a "newer" v1.0.65_A....
Also, what is the update protocol? The is no longer an UpdatePilot app and the software reports what is current and available but there is no action to take.
Next hiccup is that the ZIP file for the ODFM as on the downloads site seems to be corrupted and unable to be opened.
Oh no, that hurts! Did you have a maintenance agreement on it?how far do you get before video feed loss. and when the feed cuts out what's the icon like on the ofdm on data pilot. no dot, dot, dot with one line above it, dot with 2 lines above it? and for control what is your rssi percent when issues happen? what location are you flying from. just had massive repairs done to h520e and e30zx. hit a tree limb due to low bat rtl trigger at 15percent. Damage to drone not so bad but the camera was a killer lost internal lens the external lens and camera body fully intact. cost for drone alone parts and labor 250. camera repair e30zx internal zoom lens 990.00.