FRSKY Taranis "How to" Thread - Page 501 - RC Groups
Thread Tools
Apr 14, 2014, 02:44 AM
Happy FPV flyer
Kilrah's Avatar
Quote:
Originally Posted by thedoble
When I set up a custom switch to monitor the "Cell" variable, it doesn't work properly and seems to shout random values at me (eg: 1.3 volts)

Cell is the lowest cell of all. Cels is the total. A2 is completely unrelated.
Sign up now
to remove ads between posts
Apr 14, 2014, 08:17 AM
Chuck 'Em and Chase 'Em
Fly2High's Avatar
Guys,
Is there a way, to limit a GV to a max value such that when it hits a defined number, it can be set to another?

What I want to do is:

if GV1 < 4 then GV1++(increment GV1) else GV1 = 0 (reset GV1 to 0).

I want to cycle through groups of playlists/functions so I can use the momentary switch to select the next group and still have the 3 position switch in front of it(default setup) to select what to play.


This might need to wait for Lua and Companion v2.0

Frank


PS Using the adjust GVx custom function with the trim tabs is exactly what I wanted for allowing a single trim to alter several variables. I set the switch to activate it to a 3 position switch and set it up so that depending on the position of the switch, the throttle trim will adjust a different GV. I then used each GV for different trimming methodologies. Each was able to remain in a different value using the same trim switch. I am happy to say that the value only changed when the switch was in the proper position AND the throttle trim was clicked. If left alone, the value would remain unchanged. Thank Kilrah!!!
Last edited by Fly2High; Apr 14, 2014 at 08:23 AM.
Apr 14, 2014, 09:06 AM
obserwator
Quote:
Originally Posted by Daedalus66
You can't fly and look at screens, let alone change screens while flying! It would be like reading your email while driving down the highway, and there's a $1000 fine for doing that! It's called "distracted driving".

A year or two ago there was discussion about how the screen on a transmitter should be mounted on the top of the case for easier visibility. But with the advent of voice messaging, that idea has pretty much gone away. There is no longer any need to look at either clock or telemetry if voice is set up correctly.
Overall I agree. But I think for this reason you have User Data screen, so you DON'T FLIP IN BETWEEN OTHER SCREENS when flying - just one, major screen with some major data... I don't want to have time said every 45 seconds... Anyways, not a big deal.. Can leave with not seeing time - it's minor to me. Thank you
Apr 14, 2014, 09:17 AM
obserwator
Quote:
Originally Posted by scott page
To be quite frank with you, the value of the spoken word for telemetry cues was completely unanticipated until it went into practice. ....(realistically),
Thank you Scott!
I must agree... I am trying to push, and to make case having this User Data screen, lol....
I usually take a look on (on the screen): timer (in the end of the flying session), and......... nothing else!!
I do have on 3 position switch :
a) voltage,
* low A2/A1, (and critical alarms on top of every setups!!)
voltage (every 20 seconds.. I could easily now change it to every 40 seconds that I started voice alarms to trust for low/critical A2/A1),
b) for variometer - tones + ft altitude spoken every 5 seconds
c) I do have RSSI spoken every 5 seconds - yes, I do use it each time I'm going with different RX into new area to fly, just to make sure.. for the first minute of flights recognized furthest corners, and what is DB level.. usually flying on 'voltage' readouts though...

So to recoup: screen data is really not even secondary to me.. having voice! (gr8 radio and software).
Apr 14, 2014, 09:36 AM
Registered User
Quote:
Originally Posted by Fly2High
Guys,
Is there a way, to limit a GV to a max value such that when it hits a defined number, it can be set to another?

What I want to do is:

if GV1 < 4 then GV1++(increment GV1) else GV1 = 0 (reset GV1 to 0).
Custom switch
CS1 ..... a>x ..... GV1..... 3

Custom Function
CS1..... AdjustGV1 ..... Value ..... 0
Apr 14, 2014, 10:14 AM
Old fart. VAAATSP
d_wheel's Avatar
Quote:
Originally Posted by scott page
Every value I needed to know could be read aloud.
I agree. Don't want to be at the same flying site with someone who is paying more attention to the transmitter screen than the aircraft.

Later;

D.W.
Apr 14, 2014, 10:26 AM
Chuck 'Em and Chase 'Em
Fly2High's Avatar
Quote:
Originally Posted by lexm
Custom switch
CS1 ..... a>x ..... GV1..... 3

Custom Function
CS1..... AdjustGV1 ..... Value ..... 0
OK, so it would take 2 custom functions and a custom switch, one to increment and the other to reset to 0 if the custom switch is true.

Thanks!!
Apr 14, 2014, 11:23 AM
Registered User
Fig Newton's Avatar
Quote:
Originally Posted by d_wheel
I agree. Don't want to be at the same flying site with someone who is paying more attention to the transmitter screen than the aircraft.

Later;

D.W.
Quote:
Originally Posted by scott page
To be quite frank with you, the value of the spoken word for telemetry cues was completely unanticipated until it went into practice. During the planning stages of the transmitter there was considerable discussion about the location of the screen, and I for one was very disappointed when a custom designed case was abandoned in favor of case molds that were already available having the display at the bottom. I honestly believed that having the screen at the bottom would render the telemetry data useless.
It was not until those first flights last June that I realized to my shock that the screen had become superfluous while flying. Every value I needed to know could be read aloud. I grew to love the "read value" function very much! You could say it was love at first flight.
The Tx screen became further superfluous for setting up with the maturation of Companion9x -- not becoming OpenTXCompanion. Admittedly, hauling a laptop to go fly is not too practical. The addition of the 8" Win8.1 tablet with companion to the transmitter case has seen an almost complete retirement of the tx screen, except for selecting models. Honestly, programming 64 custom functions, 32 channels, 32 logical switches, 9 flight modes, and a partridge in a pear tree is more than that little screen with push buttons can handle with my limited patience. However the bluetooth keyboard and mouse and the color screen of the tablet can copy and paste and modify in a jiffy.
So the telemetry screens were expected to be a godsend, but in the end are not that necessary. BTW: in the coming months the entire telemetry section of OpenTX will be redone. This will be after 2.0 is finally released, probably after 2.1 is released - and probably won't be ready until the next flying season in the N hemisphere (realistically),
While I completely agree with the godsend of the transmitter reading values, and I do love the feature, the fact is, it's not exactly up to the second at times. When I am climbing there can be a lag between the time it takes to announce the altitude and the altitude the plane is. Ever have about 3 or 4 value announcements all hit at the same time? Lots of things can change in the time it takes an altitude, a battery voltage, RSSI, and a time announcement.

Let's also keep in mind that sometimes I have someone with me who can read the screen values off to me while I am keeping my eye on the plane. The bonus is that they can use some logic to tell me an altitude, timer reading, or battery voltage knowing that if I don't need to hear it they can keep quiet, or can scream if needed. Plus my spotter isn't using up a switch or having to announce on a timed schedule.

I also found that I had to make adjustments on the transmitter the other day when setting up a plane. I had to tweak the dual aileron servos to get them lined up to the millimeter. Something you just can't do in Companion9X as you have to be sitting in front of the plane with live settings.

It's easy to call the screen superflous, but at this point it still has a reason. So I don't see why adding something to the screen is a bad idea if someone needs it.
Apr 14, 2014, 11:56 AM
↓↘→ + (punch)
theKM's Avatar
Quote:
Originally Posted by Fig Newton
While I completely agree with the godsend of the transmitter reading values, and I do love the feature, the fact is, it's not exactly up to the second at times
...if you're using FrSky's telemetry, this slowness is in part the telemetry itself, it runs at 9600 baud everywhere (in the airborne gear, transmitter module connection, etc), which is not fast. Anyone needing anything close to realtime will be probably disappointed. Even if using some other faster system for telemetry link (JR's telemetry for example), the data going into the transmitter is still at 9600 baud which takes time to get all the data from all the sensors put in. IMO, the telemetry of the system is "up to date within a couple of seconds is all I need" kind of stuff, like low battery voltage telling you to land, etc.
Apr 14, 2014, 12:02 PM
Chuck 'Em and Chase 'Em
Fly2High's Avatar
Google glasses with heads up display would solve everything guys!!!

Apr 14, 2014, 12:40 PM
obserwator
OK, another thing for me I need help with, someone please:

- I have 3 position switch for my ailerons: high, mid, and low rates (with different weights and expos). This is on the SD switch.
While I have proper voice announcements for low, and high... I don't for mid-rates... I'm assuming I must not have sound file for that.

- Is there any screen in Companion9x to tweak it? (I know there is place under Custom Functions, so and I did for mid range in the same way I do have set for low/high.. yet, nothing...

How do I go about it?

Ok..so checked on my SD card in the radio: no 'midrates.wav' there.. probably this is why... so... hm... Can someone pls. point me where I can get it from ? Thx!

Thank you !

OK.. I'm following this link if anybody has the same problem - seems to be simple enough:
FrSKY Taranis How To: Create Custom Voice/Audio Files for Alerts in OPEN-TX (14 min 51 sec)


p.s. Make sure the name of 'wav' file is the same like in Companion9x.. also, there is limitation of how long (numbe of characters) your 'wav' file may have - make it short..

Problem solved, thx.
Last edited by zawaprz; Apr 14, 2014 at 02:10 PM.
Apr 14, 2014, 01:42 PM
Registered User
scott page's Avatar
Quote:
Originally Posted by zawaprz
OK, another thing for me I need help with, someone please:

- I have 3 position switch for my ailerons: high, mid, and low rates (with different weights and expos). This is on the SD switch.
While I have proper voice announcements for low, and high... I don't for mid-rates... I'm assuming I must not have sound file for that.

- Is there any screen in Companion9x to tweak it? (I know there is place under Custom Functions, so and I did for mid range in the same way I do have set for low/high.. yet, nothing...

How do I go about it?

Ok..so checked on my SD card in the radio: no 'midrates.wav' there.. probably this is why... so... hm... Can someone pls. point me where I can get it from ? Thx!

Thank you !

OK.. I'm following this link if anybody has the same problem - seems to be simple enough: https://www.youtube.com/watch?v=Wvsq4Iio_OA
Check out these three sound packs. I'm sure you'll find what you need in here. https://www.rcgroups.com/forums/show...postcount=8738
Apr 14, 2014, 01:58 PM
Registered User
Fig Newton's Avatar
Quote:
Originally Posted by theKM
...if you're using FrSky's telemetry, this slowness is in part the telemetry itself, it runs at 9600 baud everywhere (in the airborne gear, transmitter module connection, etc), which is not fast. Anyone needing anything close to realtime will be probably disappointed. Even if using some other faster system for telemetry link (JR's telemetry for example), the data going into the transmitter is still at 9600 baud which takes time to get all the data from all the sensors put in. IMO, the telemetry of the system is "up to date within a couple of seconds is all I need" kind of stuff, like low battery voltage telling you to land, etc.
So with that being said, and forgive me for not doing the math (I should be working right now anyway {smiley face} ), what's the quickest setting we should be logging at? I have my logging set to .2, so 5 times a second. I think .1 is the quickest we can go. I guess we would need the telemetry packet size, and then do the math from there.

I don't need my telemetry that accurate, but just noticed that sometimes I can get an altitude announcement that is obviously delayed, usually due to other announcements playing first, which speaks to the value of this feature.

To counter my previous post, I would like to say that if I have my contacts in, seeing the screen is possible but it's blurry. The play value feature has made flying so much better and nicer.
Apr 14, 2014, 01:59 PM
Mark Harrison
Quote:
Originally Posted by d_wheel
I agree. Don't want to be at the same flying site with someone who is paying more attention to the transmitter screen than the aircraft.

Later;

D.W.
You mean like this?

http://eastbay-rc.blogspot.com/2011/...ode-drone.html

Apr 14, 2014, 02:00 PM
Registered User
Fig Newton's Avatar
Quote:
Originally Posted by Fly2High
Google glasses with heads up display would solve everything guys!!!

And with a GPS installed it could even point to the plane if you had to look away and then look back. It's a cool time to be alive..


Thread Tools

Similar Threads
Category Thread Thread Starter Forum Replies Last Post
New Product FrSky Taranis - 16 Channels, Full Telemetry, RSSI Rotozuk Radios 53002 Today 04:40 PM
Discussion FrSky Taranis - Owners thread mud99 Radios 2107 May 11, 2017 09:23 AM
Question FrSky Taranis - assimilating web info mcshaz Radios 10 Sep 10, 2015 03:34 PM
Discussion is the FrSky Taranis next step after Turnigy 9X 9Ch tormodnt Radios 3 Nov 30, 2014 07:58 PM