Hello Spirit Team
Today I was flying and I had a problem with my Spirit GT, I always activate the altitude limit once I take off and reach 5meters, my altitude limit is set to 2 and 100 meter, and i always go down slowly to to below 2 meter to see if the altitude limit feature is working properly or not, so today I was flying and i flew three batteries and on the fourth battery I take off I reach 5 meter I activate altitude limit then I was slowly decreasing altitude to test the feature as always but this time when the Heli reached the 2 meter the unit applied negative pitch by itself and the Heli smashed violently to the ground, I tried to retrieve the logs but for some reason the logging feature was disabled and the flight counter wad reset.
I attached the screenshot
any advice why did that happened.
Spirit GT, Issues with GeoLink, Altitude Limit
-
Ahmad.Kassem
- Posts: 42
- Joined: Tue 06. Jul 2021 13:46:29
- Attachments
-
- Setup2.4ds
- (255 Bytes) Downloaded 88 times
-
-
- spirit-log-2021-08-06-081044.pdf
- (65.04 KiB) Downloaded 98 times
-
Ahmad.Kassem
- Posts: 42
- Joined: Tue 06. Jul 2021 13:46:29
The rate was 50Hz and i think i selected 90% of the parameters but cant remember exactly
Sent from my SM-N976Q using Tapatalk
Sent from my SM-N976Q using Tapatalk
Hello,
that is very sad.
RealTime log data could be resetted when unit was turned off exactly when flight log was clearing. For example when memory was completely full it is doing clearing to allow new logs.
But we already found way how to resolve the issue and from new firmware 3.3.2 it should not happen even when clearing the logs anymore.
Unfortunately the issue related to Altitude Limit is resulting usually due to very high vibration level.
This page should help with the issue:
http://manual.spirit-system.com/index.p ... tion_drift
Alternative possibility is when unit is changing collective pitch very hard, it can cause very big stress to mechanics. Can you check if some of push rod plastic was broken?
If one linkage or servo is not moving, it can look like when collective pitch was changed, either up or down, mostly in the highest available pitch.
In the Expert Settings there is Rescue - Smoothing Factor that might reduce stress noticeably. Value 1-3 can avoid this issue in the most cases. Default is 1 so probably it is already configured.
Your settings file can help a lot for finding possible issue.
that is very sad.
RealTime log data could be resetted when unit was turned off exactly when flight log was clearing. For example when memory was completely full it is doing clearing to allow new logs.
But we already found way how to resolve the issue and from new firmware 3.3.2 it should not happen even when clearing the logs anymore.
Unfortunately the issue related to Altitude Limit is resulting usually due to very high vibration level.
This page should help with the issue:
http://manual.spirit-system.com/index.p ... tion_drift
Alternative possibility is when unit is changing collective pitch very hard, it can cause very big stress to mechanics. Can you check if some of push rod plastic was broken?
If one linkage or servo is not moving, it can look like when collective pitch was changed, either up or down, mostly in the highest available pitch.
In the Expert Settings there is Rescue - Smoothing Factor that might reduce stress noticeably. Value 1-3 can avoid this issue in the most cases. Default is 1 so probably it is already configured.
Your settings file can help a lot for finding possible issue.
Spirit System developer
-
Ahmad.Kassem
- Posts: 42
- Joined: Tue 06. Jul 2021 13:46:29
I already attached the setup file, kindly check
Sent from my SM-N976Q using Tapatalk
Sent from my SM-N976Q using Tapatalk
I have checked the log. Some values seems to be possibly configured not correctly - for example Pirouette Consistency is probably too low for optimal performance.
But regarding F.Port, we have support for version 1, since version 2 is still under development and documentation is now available. ACCESS receivers are already at version 2 however. I am afraid this could result in unexpected behavior. We have no experience with F.Port 2 yet.
So we recommend to use SBUS and SPORT in this case. It was very likely reason for such behavior
But regarding F.Port, we have support for version 1, since version 2 is still under development and documentation is now available. ACCESS receivers are already at version 2 however. I am afraid this could result in unexpected behavior. We have no experience with F.Port 2 yet.
So we recommend to use SBUS and SPORT in this case. It was very likely reason for such behavior
Spirit System developer