openrcforums

Just found this explanation from Kilrah I missed. See the last message for the explanation of the VERS_NUM issue:

https://github.com/opentx/opentx/issues/698

I get the same error when I compile on Windows. I do not get the problem when I compile on Linux. I asked Bertrand about it two days ago, but I think the question got lost among other problems we were fighting. It is easy to get around by inserting: #define VERS_NUM 1 in the file lua.cpp. But natura...

I, like many others, have had issues getting the STM32 drivers to work for Taranis flashing from my Windows 7 machine. In my case a Win7 64 bit Samsung Ultrabook with USB3 ports. The usual solution is to run Zadig, which is a nice program that helps installing the needed device driver support. In my...

I agree about the navigation. It is a lot easier to navigate on the 9x/9xr than on the Taranis. Having the buttons in a row along the sides of the screen does not make it possible to create a particularly intuitive interface. Mike's Taranis firmware is easier to navigate than OpenTX, since he has sa...

I am afraid that that will be hard to do. The next branch is in reality the "trunk" (to speak svn lingo). Master is nothing but an earlier version of next. The other branches are only short lived temporary excursions from next where changes are made and then merged back into next. They are...

By the way: It is not necessary to be able to build Companion to translate it, but it is nice to see the result of one's work. Building on Linux is very easy. Just follow the easy build instructions in the OpenTX development wiki. Building on Windows is almost impossible at the moment, don't even try.

There is no one making a Dutch translation. Your help is welcome. Start by installing QT Linguist and a Git client of some kind. Then use the git client to download the next (NOT master) branch of Companion from github. Use QT Linguist to test translate any of the companion translation files. This i...

I worked with electronics meant to be used in freezers a long time ago. That experience thought me that there is a huge difference between the physical tolerances of different LCDs. The ones with a wider temp range are a bit more pricey, but not all that much. The LCD on the Taranis is strange. Most...

Did you actually manage to build with 4.8? In that case I do not think you need to revert the ARM compiler. As far as I remember the problem was not that 4.8 produced any kind of bad code. The problem was that it would not build at all. It is quite likely that the code tree has been modified so that...

I just read through the thread and the poster does say that he is using 64 bit Linux, so the above two answers seem to have nailed down the problem. I noticed that the old build instructions on google.code have been used to set up the toolchain. There is an updated version in the OpenTX development ...

JimDrew wrote: If I was a C programmer, I would have already added the support myself.

Just out of curiosity;
Do you have a specific interface in mind to add support for? Or is your idea to create a new interface that is better than the two digital interfaces OpenTX supports today?

Start by adjusting the contrast value in the radio settings. The result should be better, but will not be perfect. Unfortunately the problem is in hardware, not firmware. And it is not just your Taranis, it is all of them.

Volare necesse est, vivere non est necesse.

The Swedish FrSky distributor announced two days ago on a Swedish message board that his next shipment of Taranis radios were just about to leave Shanghai. On a direct question if the radios where of the new + type he responded "Yes, naturally".

But he might have gotten things mixed up.

Hard to say, since there are more than one kind of receiver.
But putting in a the servo lead the wrong way will never harm anything. The servo will will just not work. So just go ahead and try for yourself.

I bought one of the first Orange modules produced, and there was indeed a very real problem with these. That whole batch of modules was recalled and new ones were offered without cost by HobbyKing. I think that it is information about this issue that you have found online. As far as I know, there ha...

Thanks for the heads up. I will add your findings to the Linux build instructions on Github.

Sent from my Nexus 7 using Tapatalk 4

In subversion you get a new version number each time a file is committed to the database. No such thing in Git. If you look in the master branch and you have the latest stable code. If you switch to the next branch you have the most stable work in progress. Do not use the other branches. They are in...

Tortoise-Git.

Volare necesse est, vivere non est necesse.

I have always used Tortoise for subversion on Windows. So now I use Tortoise-Git on Windows. It works exactly the same, but has all the git stuff added. Pretty good and very familiar.

There are pros and cons with both Github and Google code. The Google code web interface is easier to get an overview of, while GitHub offers much better collaboration support for developers. The latter is the reason for the move. As far as I understand, the next release will be made from Google code...

How would the existing model settings be handled?


Sent from my Nexus 7 using Tapatalk 4

If you are using the build method detailed on the OpenTX home page, it is natural to get a somewhat bigger binary than from the build server. The server is using another ARM tool chain than the standard one linked on the page. The advantage of using the linked toolchain is that it is easy to install.

That is probably true. HobbyKing made some very strange decisions designing and releasing the 9xr, which did not make it a favorite radio for the developers. There has been little interest in producing modification information etc for it. The development of new features has lately been focused on th...

Depends on if and when someone is willing to take on the integration and testing needed.

At the moment none of the OpenTX developers have the necessary hardware combination (9xr+XJT+X8R+2sbus decoders).

The problem is that the sound circuitry picks up rf from the transmitter module. The speaker, speaker wire and sound circuits are located quite close to both the internal rf module and the external module bay, which is less than ideal. According to reports on rcgroups the main problem is the speaker...

Oops, I thought PXX was available. I will close the issue ( if someone hasn't beaten me to it )

Volare necesse est, vivere non est necesse.

I have opened an issue ( #498 ) in the github issue list for openTX. Please note that openTX is moving from Googlecode to github. The issue list on Googlecode should no longer be used.

And here is a link to a version of se.h with special charcters, in encoded form:
https://dl.dropboxusercontent.com/u/176 ... .h.encoded

I have no problem inserting the character codes, but I think that you will find that in the long run it is easier to use the script the openTX build machine uses to convert unicode header files. (with language specific characters) into proper header files (with character codes). That way the transla...

Putting the special chars back is really easy, compared to the translation, so I would gladly do that.

Volare necesse est, vivere non est necesse.