search

sareph / th9x

Automatically exported from code.google.com/p/th9x
Other
0 stars 0 forks source link

subTrim min and max : wrong graphic displaying #61

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
1) Open menu LIMITS and set up subTrim to max - 63. See pic. Limits0.
2) Switch to the main screen and move sticks to max. See pic. Limits1 and 2.
In graphic form lines are out the border and overlap second column.
The same problem you can expect to set up min of subTrim.

What version of the product are you using? On what operating system?
R158

Additional information: some users reported, if you have settings of subTrim 
described in point 1 of this issue and move stick from min to max for CH1 (for 
example) it has affect for other channels ( servo in other channels move a 
little ). I have tried to reproduce it with Prodeus simulator and I can not see 
it on oscillogram. PPM has no changes for adjacent channels.

Original issue reported on code.google.com by vlad...@yahoo.com on 5 Oct 2010 at 2:10

Attachments:

GoogleCodeExporter commented 9 years ago

Original comment by vlad...@yahoo.com on 6 Oct 2010 at 5:49

Attachments:

GoogleCodeExporter commented 9 years ago 
[deleted comment]
GoogleCodeExporter commented 9 years ago 
[deleted comment]
GoogleCodeExporter commented 9 years ago 
Attached video shows problem described above.
If PPM signal in simulator seems OK, I have idea, it happens only with some 
transmitters and receivers ( we see here Turnigy, with Corona I can not 
reproduce issue) and reason is length of channel impulse with subTrim in 
boundary conditions.
Can somebody reproduce this issue ?

Original comment by vlad...@yahoo.com on 6 Oct 2010 at 6:03

GoogleCodeExporter commented 9 years ago 
ok,
I had the same effect with the turnigy receiver.
And I think I have an explanation for this effect.
If you use subtrim then you can go beyond the limit-boundary, because subtrim 
is calculated after the limit-check (like in V14)
if you increase the stick value, then you generate an output-value of mare than 
100% (163% in your case)
This leads to an impulse length of 1.5ms+160%*0,5ms = 2,3ms which is more than 
the max value of 2ms.
Obviously some receivers become confused by this large signal and then the 
neighbour channel is affected.
The solution:
Dont do this. 
If you have large subtrim values, then decrease the according limit value.
We could do this automatically by changing the calculation sequence like this 
was in a very early version.
But this was criticized by another user which said: 
V14 does no limit check with the subtrim values.
Now we run into an endlessloop :-)

Original comment by th...@t-online.de on 6 Oct 2010 at 10:31

GoogleCodeExporter commented 9 years ago 
In this case may be you can add one option : cut PPM channel impulse or not if 
length is out of standard PPM ( 2ms ) and the same for minimum.

Original comment by vlad...@yahoo.com on 7 Oct 2010 at 5:55

GoogleCodeExporter commented 9 years ago 
Apply subtrim before limits ...

Original comment by harm.del...@echostar.com on 7 Oct 2010 at 6:55

GoogleCodeExporter commented 9 years ago 
It makes more sense to me to have subtrims applied before limits. Because if 
there is a way that a channel exceeds its limits, it's actually against the 
meaning of "limit" in my opinion.

Original comment by sascha.s...@googlemail.com on 16 Nov 2011 at 9:43