Hi All (Specifically Tomas ),
I had a disturbing instance with my Geolink this morning and I'm hoping to be able to figure out what happened so that it doesn't happen again in the future.

I start every flight with my geolink by testing the safety features and I did this same this morning: Enabled altitude limit and tested to make sure it worked, tested the bailout function, and then tested return to home. When I enabled RTH, the heli immediately started flying off to my left, so i quickly switched it back to manual flight. I then realized that I needed to re-set it as the last time i flew was at a different field. So, I landed and did a RTH reset from the transmitter, took off again, flew about 50' away, and then tested RTH: the model returned to my location and stopped exactly as expected, so i commenced flying as usual

About 2 minutes later I engaged RTH from a couple hundred feet away... and it took off in a completely different direction. I waited 2 seconds or so and finally just killed the motor as the heli was nearing a road and I was having difficulty making out what direction it was facing. Needless to say it didn't end well, but most of my electronics seem to be still intact.

I've been using the Geolink with great success for a couple months now and have had no issues whatsoever with it until now. Is there a way I can troubleshoot what happened here? I'm very curious where the signal was sending my model as it was neither my previous flying location nor the location that i set it to minutes before. It's been my personal experience that whenever something like this happens it's user error and not a fault with the equipment, but i'm scratching my head on this one...

Thanks!

I have had this problem while doing a bit of playing with the unit
It seems to be fine until I go though the geofence then RTH goes off in random directions until I disable the geofence then it works OK again
Altitude limit does not seem to affect it the same way

I would assume that at this early point of development we're going to see a few little bugs crop-up. Your probably not at fault at all although Tomáš is obviously the one to determine that and will most likely shed some light on this with his responce

I imagine as the Firmware is developed , this kind of thing will become much less frequent !
The development of the Spirit has been stellar and can only assume they are working hard on the GeoLink to perfect it too !

Hello,

it is very hard to determine where could be a problem, for this reason we are working on a new version that will either solve a possible issues caused by imperfect data transmission but especially to determine where and why a problem is happening.
It will be ready within following days.

The most common issue is when a longer data cable is used but from time to time transmitted data are not perfect. In case that these data are used it could cause a troubles. But even then GeoLink should detect within few meters it is not going in the right direction and model should try to correct it.

This is important because many people are not using provided cables and/or recommended mounting advices. Here we are preparing also a proper solution.

_________________
Spirit System developer

Can a longer shielded cable work ok? I have a Trex 550X with the Spirit Pro at the front of the heli and I am thinking of buying the Geolink but I am worried that the 22cm cable isn't enough length to run from the Geolink unit at the tail to the Spirit pro at the front. And using a longer cable might cause issues like the one the OP had.

Sent from my SM-G920F using Tapatalk

Thanks for the insights Tomas.

FWIW my setup was on an Oxy 4 using the included cable and mounting tape. The geolink was mounted on the boom 7cm from the tail servo. Rebuild is underway and should be flying again this weekend. I’ll be more cautious with GPS functions until there’s an update or some more word from you guys on signal interruptions.

Would the logs on the unit provide info that might be of use to you?