Spirit System

Spirit GT FW. 3.5.0
Geolink V2 FW 1.3.3
SAB Goblin Black Thunder

I have a problem with the geolink altimeter. At the beginning of the operation, everything was fine, but after the 13th flight, it began to glitch badly and throw up my helicopter (I fly with the height limit function). the problem is that after 30 seconds of flight, the measured height drops sharply by about 30m and goes into negative values, respectively, if the minimum height is set 2m, then it works at 32m. At the same time, GPS and other geolink functions work fine.
I am afraid for the safety of my helicopter, help me with advice.
The geolink is fixed strictly according to the instructions on the tail boom, the hole for the altimeter from below is not covered by anything. The distance to the nearest electronics is more than 10cm

Hello,

can you tell me if helicopter was stored in a higher humidity?
Could you show plot of the vibration level during flight?
If vibration level is very, very low then module will start resetting altitude, because it will think it is not flying. Then this problem could happen.

ZeXx86 wrote:Hello,

can you tell me if helicopter was stored in a higher humidity?
Could you show plot of the vibration level during flight?
If vibration level is very, very low then module will start resetting altitude, because it will think it is not flying. Then this problem could happen.

1. I can only say that there was a couple of rains (the helicopter was in the house) between the normal flight and when it started to fail, but by the time of subsequent flights the helicopter was stored in a dry room, and the weather was exceptionally sunny
2. I attach screenshots of the vibration graph of two flights below. The black graph is the altitude, the gray one is the vibration level.
3.also found an oddity in the log viewport. Sometimes in the same log one or two sharp jumps are shown, which in fact were not. When you restart the program and download the log, this jump may disappear (screenshots below)

I can't read the data because it's a strange language.
at most attach the log files and the images are in english
Have you tried reading the values in geolink settings - info ?
The blue light is solid all the time?
or flashes for one second?
in geolink - map Are the logs recorded correctly of the geolink?

Hello,

thank you for the details.

For imroved precision I recommend to wait few more seconds before lift off.
If there is bigger temperature difference the pressure difference is more apparent.
For example if model is cold and then it will go to a hotter area then a condensate will appear at the electronics and this can affect pressure.
It can take few minutes to go away.

Also make sure that GeoLink LED light is steady ON before lift off.

Can repeat by waiting little more time before lift off?

Spike in the Log can be result of loose connection between Spirit unit and USB interface. I guess your Spirit Settings software is updated to the most recent version? (3.5.0).

ZeXx86 wrote:Hello,

thank you for the details.

For imroved precision I recommend to wait few more seconds before lift off.
If there is bigger temperature difference the pressure difference is more apparent.
For example if model is cold and then it will go to a hotter area then a condensate will appear at the electronics and this can affect pressure.
It can take few minutes to go away.

Also make sure that GeoLink LED light is steady ON before lift off.

Can repeat by waiting little more time before lift off?

Spike in the Log can be result of loose connection between Spirit unit and USB interface. I guess your Spirit Settings software is updated to the most recent version? (3.5.0).

1. All firmware versions are installed the latest
2. We have dry weather now, and before the flight I go to the field for 20 minutes, then turn it on, wait for the geolink to initialize, the blue LED is on continuously, then turn on the gas after 30 seconds. I also tried to wait much longer, the result is the same. In general, the helicopter is stored and flies at the same temperature

franz88 wrote:I can't read the data because it's a strange language.
at most attach the log files and the images are in english
Have you tried reading the values in geolink settings - info ?
The blue light is solid all the time?
or flashes for one second?
in geolink - map Are the logs recorded correctly of the geolink?

Hi! I have attached the log files.
Now I wanted to see the logs on the geolink, but they all disappeared (from the geolink memory), although they were there until recently. It is very strange.
The blue LED is on continuously after 10-20 seconds from the start of switching on.
I'll try to flash the geolink again, maybe it's in the software

I made 6 flights.
all 6 flights the geolink log did not register.
I don't know why it doesn't register.
spirit logs is ok but log geolink no.
i only have the old logs.
but me too logs geolink at today they do not register.

Hello,

as I said this could be very likely due to ESC fan.
When computer is connected it does not matter if there is or isn't Status LED.
It is important it is there when flying.

Regarding your Altitude Limit issue. If you think it is not engaged even after changing switch. Have you tried to descend with the model to verify that it is really not working?

kostian34 wrote:

franz88 wrote:I can't read the data because it's a strange language.
at most attach the log files and the images are in english
Have you tried reading the values in geolink settings - info ?
The blue light is solid all the time?
or flashes for one second?
in geolink - map Are the logs recorded correctly of the geolink?

Hi! I have attached the log files.
Now I wanted to see the logs on the geolink, but they all disappeared (from the geolink memory), although they were there until recently. It is very strange.
The blue LED is on continuously after 10-20 seconds from the start of switching on.
I'll try to flash the geolink again, maybe it's in the software

Hello,

if memory is full logs are erased automatically.
I am afraid regarding Altitude readings there could be something wrong with the sensor if it is happening each time. Unfortunately we can't be unsure until we will check it. I dont know history of your module so it is hard to guess.
There is option you can send module to us for inspection or try to dry out the sensor with a blower gently or wait if new firmware will improve the behavior.
We will change behavior of the measurement not based on Vibration Level which could help you.