Futaba Flight Condition question
08-15-2014, 07:03 AM
#26
Bob on the 12fg it's the same screen you showed me above. Condition delay under the flight conditions menu. While the servo is
transitioning from one condition to the next, and you move the stick while its moving the servo will only move at the speed you have selected until the transition is complete. For me it's not a big deal. But for example if you required a large and slow control serface change
between flight modes it could get you in trouble.
transitioning from one condition to the next, and you move the stick while its moving the servo will only move at the speed you have selected until the transition is complete. For me it's not a big deal. But for example if you required a large and slow control serface change
between flight modes it could get you in trouble.
08-15-2014, 08:41 AM
#28
I set this up for a test on a feibao velox XL which requires much up elevator with landing flaps. I really wanted to slow down the deployment of the offset, but I am basically unable to move the elevator during the flaps deployment and that truly scares the hell out of me 
08-15-2014, 08:49 AM
#30
Mauryr speed your flaps up a little bit, then you can speed up your elevator. My bobcat requires about a quarter inch of up with full flaps.
I'm around 20 on my flap and elevator speeds. The transition is so smooth I don't even need to touch the elevator during configuration changes.
I'm around 20 on my flap and elevator speeds. The transition is so smooth I don't even need to touch the elevator during configuration changes.
08-15-2014, 08:54 AM
#31
Right now, what I do is slow down quite a bit and give a little down elevator as soon as I hit the flaps switch, but the jump up is quite noticeable because the elevator corrects right away while the flaps are not deployed yet.
It would be really nice if a firmware update would fix this.
It's really simple... right now:
final_pos=servo_pos+(gimbal_pos-servo_pos+newoffset_pos)*slow_k
should become:
final_pos=gimbal_pos+newoffset*slow_k
Essentially... take the delta position between current servo pos and requested gimbal pos out of the slowing multiplier coefficient, which should just act on the offset
Any way to get it through to futaba?
It would be really nice if a firmware update would fix this.
It's really simple... right now:
final_pos=servo_pos+(gimbal_pos-servo_pos+newoffset_pos)*slow_k
should become:
final_pos=gimbal_pos+newoffset*slow_k
Essentially... take the delta position between current servo pos and requested gimbal pos out of the slowing multiplier coefficient, which should just act on the offset
Any way to get it through to futaba?
08-15-2014, 08:55 AM
#32
Mauryr speed your flaps up a little bit, then you can speed up your elevator. My bobcat requires about a quarter inch of up with full flaps.
I'm around 20 on my flap and elevator speeds. The transition is so smooth I don't even need to touch the elevator during configuration changes.
I'm around 20 on my flap and elevator speeds. The transition is so smooth I don't even need to touch the elevator during configuration changes.
08-15-2014, 10:09 AM
#35
Join Date: May 2002
Location: Oxford, UNITED KINGDOM
Posts: 1,153
Likes: 0
Received 0 Likes
on
0 Posts
Hi Bob,
A few years ago I showed a friend how to use flight conditions and condition delay on his 18mz. He went away and started playing with this. A few days later he phoned me up and told me of the issue with the servo responding slow. At first I didn't believe him as I had been using condition delay for a long time(mainly on flaps/elevator) and never felt the slow response during flight. Of course, he was right and the 'feature' does exist.
I contacted futaba support(RCU forum) and asked them if this was correct. They said it is working as designed and there were no plans to change it.
From my experience I don't think its a major problem as I can only detect the slowness if I really 'pump' the elevator rapidly, which of course you don't do in flight. Added to the fact that I still use condition delay to this day.
It will be interesting to see if Futaba still say its not an issue.
Geoff.
A few years ago I showed a friend how to use flight conditions and condition delay on his 18mz. He went away and started playing with this. A few days later he phoned me up and told me of the issue with the servo responding slow. At first I didn't believe him as I had been using condition delay for a long time(mainly on flaps/elevator) and never felt the slow response during flight. Of course, he was right and the 'feature' does exist.
I contacted futaba support(RCU forum) and asked them if this was correct. They said it is working as designed and there were no plans to change it.
From my experience I don't think its a major problem as I can only detect the slowness if I really 'pump' the elevator rapidly, which of course you don't do in flight. Added to the fact that I still use condition delay to this day.
It will be interesting to see if Futaba still say its not an issue.
Geoff.
08-15-2014, 10:23 AM
#36
I have been giving this some thought, not being an electronics expert, but since we have delayed the servo speed when moving to a new trim position it would only make sense that any other inputs to that channel IE: a stick input would see the same delay during that brief time period. To be honest I've never noticed this delay during flight, but will have a look tonight in a static condition. I wonder if this is common to all radio brands when you use a similar feature/setup.
I've posed the question, so lets see what they have to say.
I've posed the question, so lets see what they have to say.
08-15-2014, 11:14 AM
#37
I have been giving this some thought, not being an electronics expert, but since we have delayed the servo speed when moving to a new trim position it would only make sense that any other inputs to that channel IE: a stick input would see the same delay during that brief time period. To be honest I've never noticed this delay during flight, but will have a look tonight in a static condition. I wonder if this is common to all radio brands when you use a similar feature/setup.
I've posed the question, so lets see what they have to say.
I've posed the question, so lets see what they have to say.
It's all in the software and, as a programmer by trade, my opinion is the programmer simply took the easy way out, not deeming it important to take the extra 10 minutes to do it properly.
What they did is simply to set a servo slow right before inputting the new destination coordinate to the channel position, to remove it after a given amount of time.
What they should have done is calculate the delta between the precedent condition's trim and the new one and then feed this delta into the channel over time.
As it is now, you can see that if you give an input to the channel in the opposite direction of the trim adjustment movement, it will move in the direction of the input, but very slowly.
Imagine what would happen if you had the trim adjustment slow set up onto the aileron and you needed to suddenly compensate for an unexpected asymmetric deployment of the flaps for example...
08-15-2014, 01:42 PM
#39
