Spirit System

Hello,
It's a pity that we haven't been able to help you so far - it's probably actually better to test a new Spirit FBL - To ensure absolute comparability, save your current configuration of the FBL on the hard drive - If you have the new Spirit FBL, then please load it the same configuration on the new FBL - also in any case leave the previous model memory in your TX16S identical without modification! This is the only way you can compare the two FBL's exactly with each other - If you don't do it like this, a comparison is pointless, because then possible errors could be corrected - You really have to take this to heart - I'm curious about the result -

Regards

From the beginning of the Spirit units there was no case of Rescue that cant be engaged properly. There is also no technical way how the unit could fail to apply collective pitch. So using different unit or radio is not needed.
Tomorrow I can connect to you by TeamViewer between 8 - 15 and fix it remotely.
Are you available in these hours?

Thank you very much for the offer of support, naturally I cannot refuse.
I have some meetings tomorrow but I am free from 08-11 and after 14.

I think you will need to see both my screen and the radio configuration as another Spirit user has tested my config file on his heli and then it behaves normally. So the issue must either be in the Spirit or in the radio. I can get Teamviewer set up on my computer in advance though.

https://www.helifreak.com/showthread.ph ... ost8664189

when you understand why let us know I'm very curious

The issue was sorted by TeamViewer now. The problem was in the sensor calibration, fortunately after resetting it all works well now.
We are only unsure how this happened but we will stay in contact in any case. So the issue was not in the programming.

Tomas connected to my computer via Teamviewer and did some troubleshooting this morning. After verifying that my setup was correct he discovered that the Spirit had lost it's sensor calibration which I belive is set at the factory. This only affects rescue and it was the first time in 15 years that this had been observed by Tomas.
After a recalibration of the sensor rescue now work correctly.

So, this issue was caused by an extremely rare fault in the gyro. But something that can be fixed remotely via a recalibration.I will not speculate on how this happened but if it was the first time in 15 years it is unlikely to happen to anyone else soon. Nevertheless, verifying your rescue operation on the ground should be advised.

Thank you so much to everyone that contributed to solving this issue, you are a credit to the heli community in that you did not give up suggesting steps to solve the problem even if we were bashing our heads into the wall.

And of course thanks to Tomas for excellent support.

I have half an idea.
while spirit is on loctite has disconnected the servo plug while it was on.
or Why it was in spirit software it disconnected while it was open.
or one or the other.

Can I know how do you do this procedure?
push button factory settings?

Sensor calibration is procedure which we are doing during manufacturing process automatically. If it is not done properly, the testing procedure will not finish and can't be sold until it all pass successfully.
For unknown reason the data for 2 axes were out of calibration and for this reason rescue mode was disabled by unit.
Unit is doing self check during each initialization to make sure it will all work correctly.
Possible technical reasons how this could happen are related to the sensor itself.
It could be for example after usage of ultrasound scanner of the package during shipping.
Since unit was new then reasons such as hard crash followed by partial sensor damage are excluded.

franz88 wrote:I have half an idea.
while spirit is on loctite has disconnected the servo plug while it was on.
or Why it was in spirit software it disconnected while it was open.
or one or the other.

Can I know how do you do this procedure?
push button factory settings?

f.jpg

This procedure can't be done by user normally or even shouldn't be done if you dont know what you are doing. If so then you can actually make unit to work incorrectly and can result in permanent failures. So doing it just for a try is not good idea.

sorry zexx86 but do not you think that in log viewer - open log there should be an error?
while no error came out
can't be added in the next update?