Hello,

During our last flights with our RedEdge MX ( via Skyport ), we found to the RTK injection get lost mid-flight. Anyone having the same issue?

- Prior take-off : all green, RTK injected.
- After landing : all green, RTK connection lost. Switched to own GPS antenna.

AGEagle support is worthless, the logs from the RedEdge are also encrypted so unable to look into it. We run on the latest firmware for M300 and Micasense ( 7.5.0 )

Any idea? We suspect a fimware incompatibility affter last M300 upgrade...but can't prove it. A scenario 'd be to rollback to an older version and check...but it's time consuming.

Regards,

AR

We fly an Altum but I've never tried RTK injection as it's typically deployed on an M210v2 w/o RTK, so I'm no help.

patiam Posted at 8-21 15:24
We fly an Altum but I've never tried RTK injection as it's typically deployed on an M210v2 w/o RTK, so I'm no help.

Are you "happy" with Micasense since take over from AGEagle?

Haven't had to deal with them since then... But you're making me worried

What do you mean by "inject the RTK"?
The camera takes the coordinates provided by the SDK port if the drone is FIX, the camera must be too.

I remember something that sometimes caused problems, you have to wait until the PPS is synchronized before launching the flight.

LV_Forestry Posted at 8-22 12:15
What do you mean by "inject the RTK"?
The camera takes the coordinates provided by the SDK port if the drone is FIX, the camera must be too.

It goes from this

to this



The "P" was near certain present on every flights we did, but could it create an issue? It seems to us it only start to happen since latest M300 firmware update.

ps: The screenshot are from the same day but not the same flights

AR_AirPrecision Posted at 8-22 22:54
ps: The screenshot are from the same day but not the same flights

This kind of intermittent failure is the hardest to solve. Basically if the synchronization is done at one time it is because on the SDK side nothing has changed. But if it occurs after the drone update, it is possible that a command interferes when launching the mission.
Is this a pre-programmed mission before update?
Otherwise I have no more idea to solve the problem.

LV_Forestry Posted at 8-23 03:38
This kind of intermittent failure is the hardest to solve. Basically if the synchronization is done at one time it is because on the SDK side nothing has changed. But if it occurs after the drone update, it is possible that a command interferes when launching the mission.
Is this a pre-programmed mission before update?
Otherwise I have no more idea to solve the problem.

Yes, pre-programmed mapping of fields in Pilot2.

The support from AGEagle is terrible, the logs are also encrypted so I have no idea what the problem is. Support doesn't answer when I ask what do the logs show.

AR_AirPrecision Posted at 8-23 05:32
Yes, pre-programmed mapping of fields in Pilot2.

The support from AGEagle is terrible, the logs are also encrypted so I have no idea what the problem is. Support doesn't answer when I ask what do the logs show.

Not surprisingly, they are certainly very busy with people much more interesting than us.

Investors - AgEagle Aerial Systems Inc.

Yeah, and trying to cut costs to decrease share value losses...

patiam Posted at 8-23 10:34
Yeah, and trying to cut costs to decrease share value losses...

Great... a 21% reduction in research and development.

Lol what is this strange feeling? We're complaining about someone other than DJI!?!

patiam Posted at 8-25 10:36
Lol what is this strange feeling? We're complaining about someone other than DJI!?!

With DJI I'm always hopeful it'll somehow get fixed...with those guys, it's money lost on a payload. In general I avoid "made in USA" as the service / support outside the US is sub-zero, especially when there are local laws protecting EU companies from such behaviour and yet don't provide any support.