Taranis RCGroup Thread Posts Summary 7-20 to 9-17-2014

Summary of Taranis Thread Posts from RCGroups 07‐20 through 09‐17‐2014 These continuing summaries contain posts that I found interesting or believe have a potential appeal to a wide audience. Sometimes you’ll find multiple posts on the same topic but with different answers. These posts are from two of the many threads on the Taranis. PAGE 02 02‐03 03‐05 05‐06 06 07 07‐08 08 08‐09 09‐10 10‐11 11 11‐12 12‐13 13‐14 14‐15 15‐16 16 16‐17 17 18 18 19 19‐20 20‐21 21‐22 22‐23 24 24 24‐25 25‐26 26‐27 27‐28 28‐29 29‐32 32 32 32‐33 TOPIC Edge/Sticky/Timer Throttle Safety Throttle Cut Resetting Telemetry Powr Telemetry Value Sticky Throttle Lock Setting Taranis vs. Taranis Plus Sound Files in Multiple Languages Sound Won’t Play in 2.08 Current Sensor to Report Discharge Level 6‐Position Switch Setting Differential with Slider Background Music Running Companion as Administrator in Widows More on Administrator
PredimRC Slim ‐ LUA ‐ Center of Gravity calculation Trim Limits and Subtrims Bootloader Adjusting Inputs Include Trims Servo Limits Sailplane Differential Channel clipping and scaling Flaps
Setting A Deadband Dual Rates More on Deadband Conversion issues 2.08 to 2.11 Triggering Physical Switch With Another Physical Switch Changes to Edge and Sticky 2.08 versus 2.11 Sticky Throttle Alternative Differential in Inputs More on Sticky LS SBus Diagrams Inputs/Outputs and Mixes Edge Servo Testor Alternative to AT&T Text to Voice Sticky EDGE / STICKY / TIMER A. Are "Edge", "Sticky", and "Timer" unique to OpenTX Companion logic functions? The rest
of the logic functions are fairly common, but those...not so much.
B. If you were to provide a definition and an example for each of those three functions to
a beginner, what would they be?
Thanks!
Leonard
Edge gives a single impulse or Pulse with parameters of of Delay and Duration
Previously we had SH↓s and SH↓l, these are now replaced with the "Edge" logical switch - but it
can be used on any switch, not just the momentary switch.
Sticky is a flip/flop or on/off toggle.
In companion we used SA-t and now it's done with Sticky
An example of sticky switch. If we set LS1 to Sticky SA↑ SA↑ it works as what we previously
called "SA(up) Momentary Switch", the first time SA is at position SA(up) LS1 becomes ON, the
next time SA is at position SA(up) LS1 becomes OFF
Time is a pulse generator at a specific time interval. Might be used for triggering a camera at
certain increments, pulsing stobes.. ???
THROTTLE SAFETY
Here is the throttle-safe I use, which I got from one of these forums a while back. I believe it will
not enable the throttle unless the stick is down, under any condition including startup. Even if I
press buttons at startup to override both the throttle stick and throttle-safe switch warnings, the
throttle remains disabled until I physically move the stick to minimum, and then Amber
announces "throttle active." It's about as mistake-proof as I can think of without getting in the
way. See L1, L2, SF3 and SF4. Switch F is my throttle disable switch.
L3 and SF5 are just there to remind me the throttle is disabled if I try to use it when switch F has
it disabled.
Throttle Cut
I think I have worked out the differences between the two methods of Throttle Cut.
It all depends on your definition of throttle cut.
Sticky method will chop the throttle immediately if triggered when throttle applied.
Logic method will NOT chop throttle if triggered when throttle applied but will hold throttle low if
stick is put in low position while cut is enabled.
Other than that, they both will not allow throttle input until throttle enabled and stick returned to
low.
It all boils down to preference. I can see arguments to be made for either one.
Sticky Method
Logic Method
Eepe Link:
http://www.rcgroups.com/forums/showatt.php?attachmentid=7031782&d=1408580778
Comments made:
As side point on your inputs you don't have a last line on each channel of 100% if you change a
switch so that none match or if a switch fails you will not have any input pasted on to the mixer
and will probably crash. It is recommended to always have the default line of 100% for safety.
Have a look at the attached inputs in yellow. This with version 2.0.x as version one had a
hidden 100% line while version 2 shows it.
Another comment: Both methods hold the throttle at -100. The first method closes, from any
position, the throttle as soon as the switch is operated. The second method only holds the
throttle if the stick is moved to the bottom and the switch is in the lock position. This is to prevent
accidental closing of the throttle if the switch is accidentally operated. For example, could be
awkward if you had just taken off and retracted gear, but hit the wrong switch.
The default line in inputs must be the last line and not use a switch. The lines are looked at in
order of position until one is active. If you put the default first the following lines will not be
looked at.
RESETTING TELEMETRY
I set the SH switch (down) to reset Telemetry in Special Functions, works great.
Thanks
Very Similar here, but I use an Edge switch so when I enable throttle it resets timer and
telemetry and starts logs.
BTW: H is a toggle switch on this TX.
Powr Telemetry Value
I'm confused about what the Powr telemetry value is trying to tell me. I'd assumed it to be Watts,
calculated as Volts x Amps, but it appears to be a little less than half that. What is it that I don't
understand or what will I have configured incorrectly?
I am using my shiny new Taranis Plus (V2.09) with an X8r and 40A Sport sensor.
You probably didn't tell it where voltage and current have to be taken from on the telemetry
setup page.
Sticky Throttle Lock Settings
Just had a little play with setting up a few throttle safety methods. These are just thought
starters and not necessary the only or even best method. EEPE attached and explanations
below. I have used CH4 as Throttle channel and SF as the Switch (up for safe)
StickyThr1
THR -100 to release
SF up locks throttle at -100,
SF down with THR Stick is at bottom releases lock.
Uses 2 Logic Switches and one Special Function
StickyThr2
THR -100 to activate and release.
SFup only applies the throttle lock when THR stick is at, or returned to the bottom.
SF down with THR stick at bottom releases lock
Uses 3 Logic Switches and one Special Function
StickyThr3
Same as StickyThr1 except both THR and RUD need to be at -100 to release lock(left stick in
bottom left corner for mode2 TX)
Uses 4 Logic Switches and one Special Function
StickyThr4
Same as StickThr2 to lock and 3 to release.
Uses 5 Logic switches and one Special Function
if warnings are not set or overridden it is possible for any of the above switches not to have
locked the Throttle
StickyThr5 is the same function as StickyThr4with the added function that ensures the throttle
will always b e locked when the TX switches on.
Uses 6 Logic Switches and one special function
LS1 checks the throttle is not at -100 and hasn't been released by LS6'
Link to file:
http://www.rcgroups.com/forums/showatt.php?attachmentid=7038385&d=1408802506
TARANIS VS. TARANIS PLUS
Is there a post somewhere detailing the differences between the Taranis and T+ as well as
the differences in OpenTX between the two?
Comparing currently shipping versions:
Taranis Plus ships with the bootloader and a FrSky version of OpenTx 2.0.9 (the only
difference I see from 2.0.8 is the defective antenna warning is disabled)
Taranis and Plus both have identical sticks, pots, sliders, case, switches, and speaker.
Taranis Plus currently does not have SWR because of a design error. Frsky is working to rectify
this for a version B.
Taranis Plus is louder and quieter -- There is no RF hum, but the popping noise when adjusting
volume is still present. The volume to the headphone is still WAY TO LOUD. I found I have to
use a curve from -100 to -80 to reduce the volume to a tolerable level - but this only gives you
three increments of volume.
Taranis Plus screen has the same resolution (212 x 64) however the screen is sharper to look
at. The screen backlight has two colors - mine is blue or white or a combination. There are
reportedly some orange - white also, but know of nobody who is actually stocking them. The
backlight theoretically has 18 levels of color blending - but in practice only three are noticeable.
Dark Blue (like the Taranis) White, and the 16 levels between look the same shade of light blue.
SOUND FILES IN MULTIPLE LANGUAGES
The old Taranis documentation says that sound files are available in the following languages:
English – en, French - fr, Italian - it, German - de, Swedish - se, Czech - cz, Slovak - sk,
Portuguese - pt, and Spanish -es. Is this still the case for version2.0x? If so, how and where
does a user get them?
SOUND WON’T PLAY IN 2.08
I recently went up to 2.08 companion & Tx firmware seemed ok until I tried to add voice
alerts no go and existing models don't fully work either radio function seems ok but won’t
play voice files any more help would be very welcome
Navigate to the radio setup screen first -- long press on MENU
Scroll down and check the WAV volume be sure it's not down.
Then navigate to the SD card screen and into the SOUNDS folder - choose a sound listed and
long press the ENT key and choose play.
If it will not play this way you likely have an issue with your SD card. If it will play you have an
issue with how you're going about setting it up to play.
If it’s the SD card - copy the contents from the card - reformat the card - and copy the contents
back.
CURRENT SENSOR TO REPORT DISCHARGE LEVEL
Is there a way (setup or script) that would let you use the telemetry input from the current
sensor to tell you when your battery is close to being discharged?
I'm going to assume you're referring to a Lipo battery being used for power.
Two ways to do this. One is to look at voltage, and the other is to look as mAh used (cnsp).
Looking @ voltage you can examine the lowest cell (cell) or the entire pack (cells).
In the example below
L1 is checking a single cell measured by the FLVS-SP
L2 is checking the pack voltage measure by the FLVS-SP
L3 is checking the pack voltage measured by the FAS
L4 is checking the mAh used measured by the FAS
EDIT: (Added later for completeness)
Last year I used the voltage as my criteria for landing - but found that in some situations the
voltage lag was to significant and I ended up with false warnings as the voltage would jump
back up when the throttle was backed off. I then changed my approach to use the mAh used as
my criteria for landing - with voltage as my back-up.
Using cnsp I land @ 80% of expected capacity and am usually right close to 3.8 volts/cell.
(Expected capacity is the published capacity when the pack is new but drops over time)
I also keep the cell (lowest cell) set to 3.3 or 3.2 to detect a faulty cell. This is a situation which
warrants immediate landing.
As pack capacity will change over time I have a back-up alarm set to voltage @ 3.5*S. This also
warrants immediate landing.
Capacity will drop over time, so it's important to know your batteries You'll know if the actual
capacity is dropping in a pack if when you land your voltage is consistently lower than expected.
In this case you change your "expected capacity". Good tracking of the battery and the
"expected capacity" is not a WAG. If you find your voltage is giving you the warning rather than
capacity it's time to significantly drop the expected capacity for that pack. Write it with a sharpie
right on the pack.
Above screen use the logic switches to play a warning sound.
I set the "land" warning to 80% of the published capacity. I also use the FAS set to 3.5v*S as a
back-up alarm in case the capacity is lower than expected. I use the FLVS to check for a bum
cell (3.2v) as one bad cell will override everything and landing immediately is critical.
You'll know if the actual capacity of the pack is lower by the voltage when landing after using
80% of expected capacity. If you notice this voltage at rest is dropping over time - then you need
to drop your expected capacity and adjust your 80% number downward. It's important to know
your batteries.
6-POSITION SWITCH
Ok, so this is really weird. I just re-calibrated my Taranis with the 6 position switch - in the right
pot position. As you can see from the table below - the end points match - but big difference in
the steps between. Whatsupwiththat?
A7 looks like its on a funny curve , a6 is normal.
Probably just some feature or connection for something that was never implemented.
Makes sense. A7 was not functional before 2.0. It always read 0
SETTING DIFFERENTIAL WITH SLIDER
I know how to set differential to a static number in the Mixer menu on an aileron. I would
prefer to be able to adjust differential in flight with the sliders. How would you set up the
sliders to adjust differential dynamically while in flight ?
Here is a sample EEPE with the differential on S1
Link:
http://www.rcgroups.com/forums/showatt.php?attachmentid=7040170&d=1408843279
BACKGROUND MUSIC
I have all kinds of sounds tied to switches through the "Play Track" Special Function.
However, I got it in my head that it would be cool to stop a track midway particularly if it was
long.
I tried building a logic switch: Sticky; SA- (off); SHup (on); and that didn't work.
I tried adding: Add !SHup which didn't work and then tried Add !SAup...Nothing.
I changed all the Play Tracks to Background Music. Background Music appears to allow you
to choose a track (I know that Scott said in a video that you had to combine all audio into
one track for Background Music to work, so I'm not sure if the track chooser is a new feature
in 2.0.9). There's also the ability to pause Background Music.
I was about to lose hope and then stumbled on this YouTube video. At about 1:05 you can
clearly see, and hear, that he switches tracks from the Airwolf Theme to Knight Rider (so
many children of the 80's). This video is just taunting me because I know an answer is out
there but I just can't figure it out: https://www.youtube.com/watch?v=z086PevXmBA
Anyone have any thoughts?
You can use a switch to increment a GV and have a bunch of Logical Switches if you want
many tracks.
This example is for just three background tracks.
RUNNING COMPANION AS ADMINSTRATOR IN WINDOWS
You need to run Companion as an Administrator to get it to write models and settings to the
Taranis. Just another Windows issue.
I had this problem shortly after I up graded to 2.0. An easy way to always run as Admin is to
right click on the OTX Icon. Click on "Properties" then click on the "Advanced" button that is on
the "Shortcut" Tab. Check the box to "Always Run as Administrator"
MORE ON ADMINISTRATOR
If you select auto EEPROM backups, then you have to specify a folder that is writable by the
user if not running Companion as an Administrator.
Perfectly logical of course but I suspect this will catch out a few users who are not experienced
with Windows. Selecting autobackup seems a sensible idea and many people (who will not
have admin access) would just accept the default directory path, like I did.
I'm wondering if it is possible to alter the functionality to only allow autobackup if a user folder
has been explicitly selected? Just thought.
Quote:
Originally Posted by OldDmbThms
Isn't this 'run as administrator' problem/solution caused because you are trying to write to a
Program File (or its sub-floder) instead of to a folder in a directory that you are the owner?
Quote:
Originally Posted by Kilrah
One possibility is if he has enabled automatic EEPROM backups but hasn't specified a
folder. In that case it would try to write in the program's directory, which is indeed not
writable as a normal user..
PredimRC Slim - LUA - Center of Gravity calculation
!!! Updated with english translation !!!
I have uploaded in R/C Setting my PredimRC Slim script which helps you to calculate the
Center of Gravity of you plane using the same formula as PredimRC.
It's here : http://rcsettings.com/index.php/view...-predimrc-slim
Some screens :
TRIM LIMITS AND SUBTRIMS
The trim switch for left rudder stopped working on my Taranas.
Where can I reset all trims to default with the newest software V2.08?
If you mean you have hit the limit on your left rudder you need to move the trims to subtrims.
The way to do this is at the bottom of the servos menu. You press ENT key when highlighting
the Trims=>Subtrims and the trims will center and the values from the trims will be moved to
the subtrims.
Same question but another reply:
The trim switch for left rudder stopped working on my Taranas.
Where can I reset all trims to default with the newest software V2.08?
There's a [Reset] field next to the Extended Trims checkbox.
BOOTLOADER
The first time the Taranis is updated to version 2.x the bootloader is loaded as well. Once the
version 2 bootloader is on the transmitter, it will not be updated by subsequent updates to newer
version 2 firmware. If you copy the firmware binary to the SD card, then the bootloader will be
copied to the SD card as well. Go to the General Radio Settings course on OpenTX University.
The course will show you where to put the binary, and how to update the bootloader.
If you use the old non-bootloader method of upgrading firmware, which is to keep the radio off,
plug in the USB from the Taranis to the computer and upgrade the firmware via Companion, the
firmware upgrade will also update the bootloader at the same time. If you chose to send the
firmware file to the Taranis SD card and update the firmware from the bootloader, then you
won't be upgrading the bootloader version. Updating from the PC will update the bootloader the
first time. After that there is no need to update the bootloader, so it doesn't. This is according to
Kilrah.
Im still trying to figure out how/why just changing the weight of a mixed value (like aileron to
flap) would cause the flap servo to change center position even when the sticks are not
moved.
I can see how adding an offset would move the center position, but it seems to me the
weight should have no effect on center.
This will happen if your mix has "include trims".
Ail to Flap. If you include trim in the mix and the aileron trim is not centred it will include the
weight times the current aileron trim setting to the flaps channel, moving the centre position.
ADJUSTING INPUTS
I am adjusting the rudder on a new extra. I have 3 rates setup hi, med, low. This is pretty
much the same setup you will find on the opentxu example plane as that was a good start
for this plane. The problem is the rudder goes way too far to the left and not enough to right.
I have adjusted mechanical best i can. According to instructions you set in the hi rate and it
then applies to the rest. Once i get the hi rates adjusted (either mechanical center or by
using subtrim) I switch over to med and low and they are pretty far off. What would be the
best way for me to approach fixing this issue? I know I'm doing something wrong here .
See the example in images below;
First image is the INPUTS and second is mixes. Note the last line in INPUTS has no switch
assigned. That is deliberate as that becomes the default and ensures there will always be a line
active and will be active when switch SB is down. The last line should always not have an
assigned switch.
INCLUDE TRIMS
My understanding on "Include trims" is:
1) Always include trims in Inputs - unless you want to do odd things with the trim switches or
turn off trims altogether.
2) Always include trims in the primary mix. For example Ch1 Ail = 100% include trims.
3) For something like flaperons - include trims if you want the aileron trim switch to also adjust
the flap movement when its following the aileron.
4) For something like crow do NOT include trims from the throttle stick to flap or aileron.
Anything I missed or got wrong?
Ah! I just realized that another issue (now fixed thanks to an earlier post from Mike) was adding
to the problem and making it much larger than it normally would be.
I initially had my trims OFF in inputs screen when I did expo, so my trims didn’t work.
Because of that, on the maiden, I had put in huge amounts of "trim" trying to trim the model.
So when I landed and adjusted the mix weight values, it caused very large changes in center
positions on some of the mixes. That caused me to change weights and offsets to correct.
So - I had several things contributing to and exaggerating the problem.
SERVO LIMITS
I have a quick one about servo limits. When you want to set a total servo travel limit, so you
don't have two channels mixed trying to over drive a control surface beyond the limit of it's
travel, is that set in the "Servo" page by adjusting the Min and Max values (between subtrim
and servo reverse) ? So Max is one direction and Min is the other?
I highly recommend you look back a few posts for the ones by mikeshellim and check out his
Servo Calibration page. He wrote most of his stuff for sailplanes BUT the servo calibration stuff
applies to any model and bears directly on your question. Actually, he has a bunch of tips and
sugestions that apply to any model - not just sailplanes.
http://rc-soar.com/opentx/setups/calmode/calmode.htm
SAILPLANE DIFFERENTIAL
Is this trick still needed to make sure sailplane differential (I fly DLGs with flaperons) doesn't
affect the crossover point if you have trim on the ailerons? I went ahead and implemented it
and it did seem to make a difference. I am using 2.0.8 btw.
http://www.rc-soar.com/opentx/setups/diff/diff_bug.htm
Yes, it's still present and my guess is that it won't be changed. It's not a bug as such - it's the
way other radios including the Multiplex mc4000 and Cockpit SX work and there is some logic
behind it. That doesn't stop it form being unwanted behaviour though.
The nice thing about OpenTx (unlike the Multiplex 4000), is that we can do something about it!
Just to summarise, the problem occurs of the order in which OpenTx processes diff and trim. If
trim and diff are specficied in the same mixer line, then OpenTx applies the trim offset before
calculating diff, so the crossover point for diff changes with trim setting.
By disabling the trim, and adding it in as a separate mix, OpenTx process the diff then adds the
trim separately, problem solved.
And:
Yes. But more logical way is to do the ail mix with diff with "include trim no"
and then separately mix in 25% weight of TrmA
Channel clipping and scaling
Some background on channel clipping and scaling (I've added this as a new section in the
section on Servo Calibration).
http://rc-soar.com/opentx/setups/calib/calibration.htm
Flaps
Assuming you are using companion and want 3 positions, see the attached images. The first
image is using INPUTS to assign SA as INPUT 5. The other two assign INPUT 5 to MIXES for
CH 5 and CH6. I have shown one as weight 100 and the other -100, you may have to alter
them to both 100. I have also set slows of 2 seconds up and down. This will give you up half
and full flaps, but depending on your servo linkages you may have to adjust these values. You
can do this using servo end points on the servo page or use a curve. If you need help doing this
ask again.
SETTING A DEAD BAND
Can anyone tell me how to setup dead band for the sticks? Have a slight tremor
Thank you
I don't know how complicated you want to go but you could try this. This will give you a
deadband at any stick position as it moves.
Example dead band on aileron.
Ch4 is aileron channel.
Mixes
Ch4
Ch10 weight (+100) switch (!L1) No trim
Ch4 weight (+100%) switch (L1)
Ch 10
[I4] Ail Weight (+100%)
Ch 11
Ch4 weight (+100%) Notrim
CH10 weight (-100%) Notrim
Logical switches
L1 .. |a|<x .. Ch11 .. 5 .. !L2
L2 .. a=x .. Ail .. 0 .. --Here's how it works.
. Ch10 is the input from ail, Ch4 is the ail servo position output.
Ch11 calculates the difference between ail input and ail position.
Log sw 1 is true if the absolute difference (Ch11) is less than 5% and Ch4 doesn't change
because it's input is it's output.
If the difference is greater than 5% L1 goes false and ail input Ch10 is mixed to the output. L1
then immediately goes true again because the difference is less than 5% and Ch4 is held again.
Log sw 2 detects when the ail stick is centred (0) and makes L1 false so Ch4 output will centre
properly.
Result - The aileron output doesn't change unless the stick input is more than 5% different than
the present aileron position or is centred.
Tune that 5% in log sw 1 depending on how bad the tremor is.
DUAL RATES
Hi probably a basic question but how do you do switchable dual rates? I have done the expo
and weights easy enough but it seems to have changed from the quick start guide. Mark.
See attached image. I have setup dual rates on ELE using switch SB↓to give 70%.
it is essential that the last line in any input does not use a switch, as the lines are read from the
top and the first line that meets the switch condition becomes the active line. if no switch
condition is met, you have no input. aline with no switch matches when no other line does, so
becomes the default. if you put this at the top no other line will be looked for.
the input shown will give 70% if SB is down and 100% if it isn't down.
You can add another line, at the top, or between the other two lines (but not at the bottom) to
give a third rate by using SB- (middle position).
you can use any suitable value in WEIGHT. The 70% and 100% are only examples.
Yes, in inputs, no switch is essential. Just to prove it to yourself make the second line active
when SB - is active and leave SB up. Then try it in the channel monitor and you will get no
movement. Mixes are different, as they have an operator, ADD. REPLACE or MULTIPLY.
There is an exception to the No Switch rule. That is when you use all the positions of a switch,
as long as the switch doesn't develop a fault, there will always be one line active.
Three images below. The first shows the 3 switched positions. The second covers the, small,
risk of a faulty switch. You will see this quite often in posted EEPEs. The third one is the way I
do it. Two switched lines and the last with no switch. This still gives 3 positions and also covers
a faulty switch, but uses one less line.
MORE DEAD BAND
A more detailed description for those struggling:Example dead band on aileron.
Mixes
Ch4
Ch10 weight (+100) switch (!L1) No trim
Ch4 weight (+100%) switch (L1)
Ch 10
[I4] Ail Weight (+100%)
Ch 11
Ch4 weight (+100%) Notrim
CH10 weight (-100%) Notrim
Logical switches
L1 .. |a|<x .. Ch11 .. 5 .. !L2
L2 .. a=x .. Ail .. 0 .. ---
Ch4 drives the current servo position
This mix "Ch4 weight (+100%) switch (L1)" causes Ch4 to hold the current position as long as
L1 is false.
Ch10 mix"[I4] Ail Weight (+100%)" Causes Ch10 to follow the stick input.
Ch 11 mixes "Ch4 weight (+100%) Notrim" and "CH10 weight (-100%) Notrim" effectively
perform a signed addition of the stick position (ch10) and the current servo position(ch4) ,
remember CH4 is held as long as L1 is true.
Now switch L1 "|a|<x .. Ch11 .. 5 .. !L2" is comparing the ABSOLUTE value (remember absolute
disregards the sign + or -)of Ch11 (the difference between the stick position and the servo
position) to an arbitrary figure, in this case 5. So when the positions vary by 5% or more L1 will
go false. We'll look at the "and !L2" in a minute.
When L1 goes false the Ch4 hold is released and the Ch4 mix"Ch10 weight (+100) switch (!L1)
No trim" becomes active and ch4 is set to the stick position (ch10). Immediately this happens
the difference between the stick and servo is now "less than 5" so L1 goes true and Ch10 is
"disconnected" and the ch4 mix"Ch4 weight (+100%) switch (L1)" holds Ch 4 at that value until
the stick/channel difference becomes more than 5 again.
Switch L2 "a=x .. Ail .. 0 .. ---" goes true when the ail stick is at zero, (centred). This makes L1
false to force Ch4 to the correct position at centre otherwise Ch 4 could remain at some value in
the range -5 to +5 when the stick is centred and affect the centre trim. Ch4 will remain centred
until the stick moves 5% from centre and the process repeats.
(We could also make the deadband adjustable by changing L1 to compare the difference with a
suitably scaled input from a pot or slider so the amount of deadband is adjustable "on the fly",
by using some more channel mixes and some switch changes. )
CONVERSION ISSUE FROM 2.0.8 TO 2.011
The line |d|>=x was changed to d>=x
So check your models for other inconsistencies.
If you check, you can see the option still exists. I had to manually change them back.
There also a BIG difference between the operations - and the results they yield. The absolute
operation gives you all repeating occurrences.
I was under the impression that d>x triggers the switch every time the variable increases
more than x since last time it was triggered, whereas |d|>x does the same but when the
variable goes up or down x. Am I correct? I do not understand what
you mean by "The absolute operation gives you all repeating occurrences."
Essentially, yes:
d>x = triggers when d (v1) increases by more than X (v2)
|d|>x = triggers when the change to d (v1) is more than x (v2)
TRIGGERING PHYSICAL SWITCH WITH ANOTHER PHYSICAL SWITCH
Is there a way to trigger a physical switch with another physical switch.
Example: How can I trigger SH momentarily with the SD- and SD↓ switch.
It will need a time component as I don't want a SH↓ hold. I want to flip the SD- and SD↓ back
and forth triggering SH momentarily.
I don't think so, but...
You could use Logical Switches to get a momentary action using Edge:
Edge SD- 0.0 (Instant)
would give you a momentary from SD-. You could do the same with SD↓, and you could then
use these LSs to control whatever you've got SH doing. How you would go about the second
part would depend on what you're doing with SH, but you could use the LSs in mixes, inputs, to
run Special Functions etc
CHANGES TO EDGE AND STICKY IN 2.0.11
Just updated from 2.0.8 to 2.0.11
And I find that the sticky throttle I use in all my model is no longer sticky.
Went back to 2.0.8 and all is good again?
I can't see any difference in the eepe files for the models.
Logical switches and special functions haven't changed?
There were some changes made to EDGE and STICKY Functions, which could affect your
settings.
Until we hear from the developers on how the new "Sticky" logic works; my belt and suspenders
work-around where SF (up) also acts as a kill switch and disables THR. SF (down) enables
THR and stickiness. This is not my idea but cannibalized from several sources. THR is CH7.
STICKY THROTTLE ALTERNATIVE
Have remedied my sticky throttle in 2.0.11 by removing "sticky" and replacing it with "OR"
function and then 2 parameters, with SF. However will not as yet modify all the model
setting I have, and will remain with 2.0.8 until the next release. Then see what happens.
Just goes to prove you need to check all functions when updating. A smashed model is one
thing but lost fingers or worse, something else.
Looking back the past 2 days I was concerned to see issues with the Sticky throttle lock. I flew
Friday with V2.0.11 and am using a Sticky throttle that I saw here. I just checked again but can
find no fault with the planes that I have flown with it.
Looking at the firmware changes there was this added for Version 2.0.10
" Duration and AND fixed on Sticky and Edge logical switches [Taranis] "
By that it looks like if you have an "AND SWITCH" function set up with a Sticky LS that could be
where the issue is.
The Sticky Logical Switch I use (and most of the ones I have seen here) don't use an "AND
SWITCH" function. There is just one switch (V1) to turn it ON, and one (V2) to turn it OFF.
I have a screen shot to show how mine is setup. Again this was posted quite a while back along
with different variations. This one appears to work fine for me.
Are there new versions out that use the "AND SWITCH" function that are better or use less
logical switches? Is the "AND SWITCH" needed to turn ON and OFF the STICKY or just ON or
just OFF?
DIFFERENTIAL IN INPUTS
Use the diff function in inputs. It will put differential on both ailerons at once. Changes in trim will
effect differential in mixes, but not so in inputs.
This PDF was attached to a post of mine a couple of days ago.
http://www.rcgroups.com/forums/attac...0&d=1410467564
Ailerons are CH1 and CH4 in this case and I use this on Mystiques and Radian Pro's. 50% DIF
as a starting point.
Note only the first line on each of those channels MIXES for DIF and EXP. The other 2 lines are
the THO stick working the AIL and FLAP channels for crow/reflex/camber/airbrake and should
be ignored.
When testing you want to see more UP vs less Down on the opposite AIL.
The second line on CH6 RUD is the RUD/AIL mix for coordinated turns and this is way O/T for
this thread and perhaps should continue
herehttp://www.rcgroups.com/forums/showthread.php?t=2138164
MORE ON STICKY LS
Just wanted to clear up what's changed with the sticky LS. As I know the changes which came
in at 2.0.10 has caused confusion
You now need to think of it as 2 separate switches :
Sticky V1 V2
V1 turns it on and V2 turns it off
AND is an extra switch which has no effect on the sticky part, just the output
For example if you have - Sticky SHdown SHdown SAdown
When you press SH down, the sticky part is set on regardless of where SA is. If SA is up, the
switch is off. If you then set SA down, the switch becomes on, as the sticky part is already on
Again, if the sticky part is on, V2 will turn it off regardless of where the AND is set.
You also need to be aware that duration resets the sticky part, and both delay and duration are
applied regardless of the AND switch.
So like I said, think of it as 2 switches: a sticky set on by V1, off by V2 or duration, and delayed
by delay, then AND as a second step
I use this as sticky throttle:
L1: a<x thr -99 SFdown
L2: a<x thr -99 SFup
L3: stcky L1 L2
I've then use !L3 as channel override in SF
This will only activate or deactivate with throttle stick down (and won't arm throttle at startup if
stick is not down, even if I press exit on switch warnings)
I also use:
L4: AND L3 SF^!L2
As the control for a warning if i accidentally switch throttle off with throttle open
So my sfs:
SF1: !L3 override CH1 -100
SF2: !L3 play track engdis
SF3: L3 play track engarm
SF4: L4 play sound warn1
Addiitonal:
Ok.. the reason it now doesn't work is... before the AND switch used to reset the sticky part, and
now it doesnt (to bring it in line with other LSs. But not or)
The sticky part is now only turned off by either V2 or duration
So if the throttle has ever been at <-99 in your setup, the sticky part is on, and will always be on,
as there is no V2 and no duration, so so SFdown will always make it on regardless of where the
throttle is now.
I've been trying to come up with a quick fix, but the best I can come up with is replace the sticky
with
OR L1 L2 SFdown
For some reason the AND in a OR switch still resets the first part of the switch!
Sbus Diagrams
Attached rough Sbus wiring Diagrams.
The joints can be any form of parallel connection. "Y" lead, Splices or multi-block. Also Mike's
link to a new Futaba Servo allows that type of servo to be daisy chained. Warning if using multi
high drain servos, normal servo extension and "y" tend to be 24 or 22 gauge wire. I would use
20 gauge. However, you can attach extra batteries or battery leads in at any point to split the
load.
Another comment:
A lot of guys are using these to get around the added power needed for that many servos.
http://xtremepowersystems.net/prodde...rod=XPS-X10%2B INPUTS/OUTPUTS AND MIXES
First a brief explanation of Inputs and Outputs/MIXES.
An input is anything that can be used to modify an output, but does not directly control
anything. Inputs can be Switches, Gimbal Sticks, Pots, Sliders, Logic switches, Special
Functions, Curves, Telemetry and even another Mix Channel. Companion9X has a page
called STIKS which can be used to modify the 4 main controls. This outputs from this are
still inputs. OpenTx Companion has a page called INPUTS, which is similar to sticks, but
has more functions and can be used to modify any input., but the result is still an input and
will not directly control anything.
Outputs are the result of inputs being assigned to a function. the most important being
MIXES as this assigns and controls the Channels. Other outputs can be the display screen
info or sounds etc. from Firmware default warnings, Special Functions etc.
For flaps using two servos I would set up a dummy/slave channel and use that as the
Input/SOURCE for the two servo Channels.
In the explanation below I will use CH14 as Slave, CH6 & 7 as the outputs and SA as the
switch input.
How to set up flaps using TX (MENU, PAGE, EXIT, "+", "-" and ENT refer to the 6 buttons at
the side of the screen).
Switch on TX, Short press EXIT, short press MENU. If you only have one model.
or the model you want to modify is selected ignore the lines between the #s.
#Use "=/-" to scroll cursor to the model to be setup. If it is a new model you wish to start on,
long press on ENT and a pop up will appear, with Create Model highlighted. press ENT and
a new model will appear in the list. (It will need renaming).
If it is an existing Model long press ENT and Select model should be highlighted. Short
press ENT and the selected model will become the current model#
Now short press PAGE and repeat until MIXER page appears. (about 5 presses but, in
Companion, varies depending on options selected).
Press "-" and repeat until CH14 is highlighted.
Press ENT and it will open the CH14 editor. The mix name will be blank but highlighted.
Press ENT and the highlighter will reduce to a single character. short presses of "+" will
scroll through the alphabet etc. scroll to f and a long press will insert "F" a short press will
insert "f". The cursor will automatically move to the next space. Repeat until you have
"Flaps" displayed. Press EXIT and then "-" to move to SOURCE.
Press ENT and cursor will flash. Use the "+/-" buttons to scroll to SA, press ENT.
Press "-" and the cusor5 will move to the WEIGHT value, which should be 100. leave that
for now and press EXIT twice, which will close the editor. See image FLAP SLAVE
CHANNEL in images below.
(If at anytime you want to open it again, scroll to the line using "+/-". When you are on the
line the 100 will be highlighted. Press enter twice and it will open for editing).
Now scroll up to CH6, press ENT name the MIX "Flap L" using the method described for
CH14. Scroll to SOURCE press ENT and using "+/-"scroll until CH14 shows. Press ENT
and "-" to scroll to Weight 100. Leave that for now and use "-" to scroll down to SLOW Up.
Press ENT and use "+" to set time to 2.0 seconds (You change this later if it is too slow or
fast). Press ENT then "-" to scroll to SLOW Dn and set that to 2.0. See image FLAP L below
Press EXIT and"-" to scroll to CH7 and open for editing name it Flap R.
Set as CH6 except change the WEIGHT 100 to -100. (tip there is a short cut for this. Press
the + and - buttons both at the same time)
See FLAP R image below.
Now do a long press on MENU and it will open the CHANNEL MONITOR and you can
check the operation of the flap channels. Press EXIT to get out of monitor screen.
You now need to set your servos and rods up correctly in the model. If you need advice on
this or anything else, ask.
You may need to change the Direction of one or both Channels, depending on your servo
setup. Do this by changing the + to - or vice versa.
You will also almost certainly have to change the WEIGHT value and possibly the middle
position. A curve will probably be the best way to do this. When you are ready for this ask
again.
Edge servo tester
I want to do a soak test on some Sbus servos. so I had a play with the EDGE function to set
this up and to also act as a bit of a demo of the EDGE function.
EEPE attached.
CH1 is set to take four seconds up and two seconds down.
CH2 is instant up and down
CH3 uses a curve to give a Pseudo random movement. (This i s a curve I use for the pilots
head in a P51)
CH4 is ultra slow, 25 seconds in each direction.
The movements are activated with SA↓
Link to file:
http://www.rcgroups.com/forums/showatt.php?attachmentid=7107802&d=1410870793
Alternative to AT&T Text to Voice
The current best text to speech software is Text Speaker. It has customizable
pronunciation, reads anything on your screen, and it even has talking reminders. The
bundled voices are well priced and sound very human. Easily converts blogs, email, ebooks, and more to MP3 or for listening instantly.
STICKY
L1 a<x Thr -98 SFup
L2 Sticky SFdown L1
SF1 !L2 Override CH3 -100
This works before and after the change.
Someone tried this:
But what you've got there will enable with throttle anywhere, but only disable with throttle
closed. To disable with throttle anywhere, and only enable with throttle closed, it should be:
a<x thr -98 SFdown
Stcky L1 SFUp