Is it possible, that the software has any problem with the SBUS???
Log file: receiver signal lost
It was the first flight after installing the spirit 2 on my reworked T-Rex600ESP flybarless. Flight time was about 8 minutes, I was flying circles in both directions without any problems. At the next initialisation I saw the other behavier of the swash plate. Then I stopped flying and read out the log file on the PC with the message "receiver signal lost" 2 times within 10 seconds after 8 minutes flight time
. My receiver is a Taranis X8R with telemetrie connected with the SBUS an I had no message about signal lost on the telemetrie on my transmitter. The throttle signal goes direct from the receiver to the ESC and there was no problem, because my fail save setting for the throttle is null for receiver signal lost.
Is it possible, that the software has any problem with the SBUS???
Is it possible, that the software has any problem with the SBUS???
-
thestructured
- Posts: 157
- Joined: Thu 24. Dec 2015 20:13:20
Probably a stupid question, but did you maybe power off your transmitter before unplugging your helicopter after that first flight?
Where was the 'signal lost' in the logs, in the middle of the flight or at the end?
Where was the 'signal lost' in the logs, in the middle of the flight or at the end?
Very often when you will come close to the model with FrSky radio it will loose the signal.
This is quite normal behavior.
You can verify it easily just by placing radio close to the receiver.
This is quite normal behavior.
You can verify it easily just by placing radio close to the receiver.
Spirit System developer
1) No, I switched not off the transmitter before switching off the heli.
2) And yes I know that in near distance it could be that the receiver get low rssi, but then allways the transmitter report these due to the rssi meassurement over telemetrie.
The receiver signal lost message was exact 60 seconds before switching off the heli, so it is possible that this errror occured after landing at spinning down the rotor, maybe I was only 1 to 2 meters behind the heli, so 2) is maybe possible, I check it next flight
2) And yes I know that in near distance it could be that the receiver get low rssi, but then allways the transmitter report these due to the rssi meassurement over telemetrie.
The receiver signal lost message was exact 60 seconds before switching off the heli, so it is possible that this errror occured after landing at spinning down the rotor, maybe I was only 1 to 2 meters behind the heli, so 2) is maybe possible, I check it next flight
With belt driven helicopters this is sign of electrostatic discharge hit if it fits landing time.
This is very common, but not good phenomenon.
This is very common, but not good phenomenon.
Spirit System developer
-
p.i.engineer
- Posts: 21
- Joined: Tue 03. Jul 2018 18:54:25
can you clear the log/error through opentx integration?
First from all it would be good to reproduce the issue.
Do you think it is possible at the ground? This would help a lot in finding the problem.
It could be just a cable. Unfortunately sometimes a problem can happen only with motor running.
Do you think it is possible at the ground? This would help a lot in finding the problem.
It could be just a cable. Unfortunately sometimes a problem can happen only with motor running.
Spirit System developer
