What's new
Aloft Forums

Welcome to Aloft Forums. Register a free account today to become a member! Once signed in, you'll be able to participate on this site by adding your own topics and posts, as well as connect with other members through your own private inbox!

Unable to register Taranis RX6R with Taranis X9D plus 2019 (both new as of March 18, 2020) Suggestions?

I really Liked the Aloft RX6R Videos I am also having trouble binding my RX6R receivers I have a 2019 X9D Plus SE otx 2.3.1 (ACCST) but could someone tell me how to build or buy the adapter so I can put the proper firmware on my RX6R so they will bind and does the adapter plug into the SBUS plug My TX does not have the cool place to plug into

Thanks
Frank
 
It's useless to recalibrate after updating.

It's however easy to wipe your calibration when transferring things incorrectly with companion.

Re calibrating is a simple process if one is unsure if the current config is correct for whatever reason. I believe saying it's useless is a poor expressional term, maybe a better term is that it may have been unnecessary.
 
Useless is the correct term. That is it adds no value to the operation of the system.
Kilrah is an OpenTX developer he would know what action effect what part of the code.

Now he didn't say worthless. It might have some value if, as you say, it makes one "feel" better. But as part of the servicing of the code it has no benefit.

This is how we get a lot of irrational actions in life. That is we often don't fully understand what we are dealing with. In a broader context I keep thinking of the Stevie Wonder's song Superstition.
 
Last edited:
I am new to this hardware and software. I saw an issue and renewing the calibration removed the problem. I do not know the cause and thus there is a degree of uncertainty. I was paying attention to setup guidelines that suggested calibration removes typical issues. I take it to be like restarting software if strange behavior is seen.

Without recalibration I would still be chasing my tail. The initial calibration may have been incorrect. I may have unknowingly damaged it. There may be other possible root causes. I have only weeks of familiarity with the software. Recalibration for the moment has removed, or at least side-stepped this problem. In my particular situation, recalibration was helpful.

To be more specific, earlier I was not seeing servo motion that followed the corresponding stick motion. The servo followed the stick till the stick reached the center point and then stopped while the stick continued to the opposite travel limit. Several sticks showed this characteristic. After re-calibration the servos move in concert with the sticks. I have other adjustments to make and the setup is still clearly not airworthy.

My current study is to understand mixing and output settings more completely. There are certainly many ways to make adjustments and I am also certain many will result in appropriate outputs but also be overly complicated.
 
Calibrating the sticks is a needed function. I do it at least once a year to take care of mechanical and to some extent electrical drift.

it is also a good idea to calibrate the inputs after receiving the TX or if you have given the TX a shock (dropped it).

With OpenTX it is key to understanding that 90% of all your actions will be done in the mixer and output pages.
 
Useless is the correct term. That is it adds no value to the operation of the system.
Kilrah is an OpenTX developer he would know what action effect what part of the code.

Konrad I may be proven wrong in this but I don't see any of the Opentx development work with his name on it. There are however plenty of comments from him. In any case performing a calibration does not affect the actual code. It only ensures the sticks etc are operating in the correct full range manner.
 
Kilrah is not only a code writer but also a mover and shaker of OpenTX.

It's not that calibration rewrites any code. It is that the upgrade (new code) doesn't touch any of the values stored for the calibration. (Well unless as noted, you command Companion to change things). So assuming the radio was calibrated, recalibration after the upgrade is useless. Or more to the point a superfluous exercise. Why make things more difficult than they already are?

All the best,
Konrad
 
Last edited:
Upgrading never touches calibration, so if you lost calibration you also lost other settings. Just telling people to recalibrate is not good advice since it only hides the problem, it doesn't fix the other radio settings and won't help anyone understand what they did wrong and prevent them from repeating the same mistake.
 
I was careful to structure my post in a way that left the possibility of the situation described. If the servo motion resulted from an initial corrupt factory calibration nothing else is at issue. If I inadvertently damaged the calibration this has corrected the situation. There may be other problems yet to be found. I may have other corrupted programming and settings. I am currently using (mostly) three references; Lothar's paper manual, the building notes for my aircraft, and rc-soar.com. Comments from this forum are adding to my understanding of OpenTX. I use the OpenTX documentation as well. I have seen the term "calibration" used in different contexts. I used "calibration" to refer to the setting of the sticks as they were moved through their range. I am not completely confident that "calibration" refers to only this context and suspect it may also be used in other situations with additional meaning and context

This thread asked about binding a particular transmitter and receiver. That was explained and accomplished. The discussion is now about setting up a particular model. What is the convention on this forum? Continue with this thread? Start a new one?
 
If you are changing the scope of the discussion please start another thread.

When you do, if using the templets from RC-Soar please let us know which one. Also to help others in the future please add tags to the thread.

The term calibrate is pretty consistant in OpenTX.

I think you are confusing Cal mod in Mike Shelim's templets. In the RC-Soar templets Cal means balancing (setting the curves) of the control throws.
 
Last edited:
I am not specifically changing the scope of this thread. The discussion continues to evolve into useful areas. I am comfortable with this discussion thread and I could create a thread with a new title. How do users on this site generally respond in this situation? I could make arguments for continuing and for a new start but wanted to see what participants "usually" do. On other forums I often see "moderators" providing guidance. Too often the guidance is: " You are not following the rules .... Do something else!". I would prefer to not go down that path.

Konrad:
I am examining the Ahi 100 setup on rc-soar.com . I may elect to use it or I may program another. Others have suggested attractive, different paths. I have not yet made a (setup/input/mixer/output) decision for my next steps. Rest assured that if I ask another question I will also include background details to set the stage. My question at the end of post #49 was to gather information before a yet to be made (thread) decision.

You ask for Tags. Where is that done? Feel free to add any additional clarification you see as helpful. I earlier found a way to copy an entire thread in a very readable *.pdf form but have now lost where I found the trick? Do you recall how to make that copy?



Kilrah:
If calibration was indeed lost and not damaged all along what other settings should I examine closely? I would in general review my entire setup to see if it looks sound before test flying again.
 
Last edited:
Break down the topic into threads to help others in their research. Think of these threads as reference materials. Would you want to read through sixteen topics in a thread to get to the point you are interested in?

Also restating exactly what is the "next step" in your quest helps us all.

So here we had the title registering (binding) question. This has nothing to do with RC-Soaring templets. Or the set up of specific program actions.
 
Has this thread reached a reasonable conclusion or should it continue?


Konrad:

I have deliberately not provided what I thought was the best path forward as I wanted to elicit responses from the participants to see what they preferred relative to thread constructions. Do you prefer 16 disjointed topics to one consolidated track that now does not match the initial title?

I asked the question for the reasons you cite above and for other reasons of my own. You asked me for tabs but did not respond to my question about how to add them.

I will refine my "next steps" description when I have a better picture of just what those will be. I do not want to ask a general question and waste others time when I still have homework.
 
Tabs are done in the title bar.
And you can link to related threads to keep continuity of the thoughts or background.
 
Back
Top