Hello,

I checked your logs and I can't see anything wrong there.

All is looking correctly, including Altitude.
The error that is at the end of the log is just because battery of the model was disconnected and so telemetry variables are missing which is also correct.

Also Altitude measurement seems to be quite precise during whole flight. Difference between start and end of the flight in Altitude is less than 1 meter.

_________________
Spirit System developer

seeing the logs (diagnostic - realtime logging) Everything is ok and helicopter is perfect during throughout the flight.
But in diagnostic - log viewer I receive
GeoLink connection is broken
Power Voltage is low
RPM Sensor data are too noisy
Received Frame was Corrupted

I'm thinking current signal nasty, interference or similar
my esc it has two spines
I connected the one circled in red
the plug circled in blue I DIDN'T ENTER IT

I can connect two plugs for power supply the spirit?
for now i use port THR the second plug I can enter it in AUX ?
the two spines they have the same voltage (programmable from 5volts to 8 volts)
if I give 7.4v in THR and after in AUX other plug it has 7.4v inserting both of them do i give current for 7.4volts?
I didn't do it because I'm scared 7.4+7.4= 14.8 and that's not good.
can I use two plugs to give current?
if the error they don't disappear in port E1 can i use a capacitor?

comes supplied with hobbywing esc
4700uf 10v

why the manual says this:
Plug the JR connector of this cappack into an idle channet on the FBL system controller
(the cappack cannot be plugged into the idle channel if the GND & Power wires of the motor RPM Signal Input Pon of some FBL systems and other port are net connected in parallel), or an idle channel on the receiver (illustration 1 ).

With Futaba, you must plug the Throttle signal cable 3 in to the channel 3 of the receiver.
The Plug 1 ( BEC) connect it in to a AUX channel in the Spirit Flybarless..
And the condensator that is coming with the Hobbywing ESC, plug it in a AUX channel
Spirit Flybarless.
Remove the cable ties from the GeoLink antena, also you can Trust 100% the 3M double tape,
if you still have problems after the correct connection, make a hard reset to the GeoLink,
installing again the firmware.

Hello Franz,
don't be scared you don'get 14,8 V because this is a parallel connection of the lines, which means that the voltage remains the same - by connecting the two cables in parallel from the ESC, more current can only be transmitted. Each line/connector can only transmit a limited amount of current, but it is then easily possible to supply the nominal current for the BEC from the ESC via two paths - use both cables and the problem will disappear -

Best Regards

and the capacitor? I can insert it in a free port (e1)? I would not short circuit the spirit

Hello Franz,
look at the spirit RS Wiring in the online-manual...this should not be a problem, you can it put in E1 -

https://manual.spirit-system.com/index.php?title=SpiritRS_Wiring

Here a screenshot:

Best Regards

this is manual capacitor hobbywing

Hello Franz,
I have already equipped many ESCs and helicopters with capacitors - if you use the capacitor e.g. if you plug it into the FBL side via a Y-cable, there will never be any problems! There is only a restriction on the controller side if the manufacturer says that such capacitors are not permitted, but that is not the case with Hobbywing, YGE and others - this capacitor has no place on the motor side, it would explode immediately! A capacitor, as long as it is not defective, can never cause a short circuit -

Best Regards

Looks that you not read careful what we write here to Help you, I write you yesterday ,that the capacitor you can plug it in every free port of the Spirit Flybarless, or receiver!

I'm actual having an issue with the Geolink, too. When the rescue with altitude limit happened, the heli turned inverted (I didn't fly invert) and crashed. Unfortunately the log was corrupted. The heli is repaired now and I made some hoverings yesterday. In the log I had always the message "received frame was corrupted" like you. Could ist be the same problem?