opentx / opentx.github.io Goto Github PK

Some of the information in this doc https://docs.google.com/document/d/1ILh9lSW4d05qJD2rSKxep0WnJUfNCcAPCafKZeESweE/edit#heading=h.yi8zf2vndziz is incorrect or out of date. Who is maintaining it? How can I submit changes and updates? Why is this a google doc?

Is anyone else getting this or is it just me?

https://downloads.open-tx.org/2.3/release/sdcard/opentx-t16

Please add a link to the additional voices here: "voices-20.open-tx.org" and also a description on how these were created so other sounds can be created in the same voice by users.

Broken link to manual

“ See the “Flashing your Taranis Radio” section in this manual.”

Php error. Had multiple people check

the images are already uploaded, just web page needs updating.
Pull #36 assets/images/head_x10s.png assets/images/img_x10.png

Smaller version of the Horus X12
Colour outdoor TFT 480x272
8 Switches 6 x 3-position, 1 momentary, 1 x 2-position
3 Pots 1 x 6-position, 2 smooth
2 Sliders 2 rear, 2 front
Haptic vibration
Wireless trainer
Without GPS and 6 axis sensors

Hi there, I would like to share the logo on the commons gallery. Unfortunatly it need a appropriate license, to avoid copyright issues.
Could you release the logo as public domain or creative commons please or grant permissions to wikipedia?
https://commons.wikimedia.org/wiki/File:Opentx-logo.png

See bottom of
http://www.open-tx.org/screens-taranis.html
In November 2014 new images were added in a sub folder
assets/images/screens-taranis/new_startscreens/

At some point since then the link to that folder/generated page broke...

If entering http://open-tx.org into the browser, this should divert to http://www.open-tx.org. This does not affect sub-domains.

.htaccess file:

# - Divert non-www to www -------------------------------------------------------------------------------------
    RewriteCond %{HTTP_HOST} !^www\.
    RewriteRule ^(.*)$ http://www.%{HTTP_HOST}/$1 [R=301,L]
# - END Divert non-www to www ---------------------------------------------------------------------------------

I've tried multiple versions of open tx it seems like most of the 2.3.x won't open up I downloaded 2.2.4 and it opens fine but I keep getting "unable to check for updates" I'm unable to flash my x9d+

This page does not display the google doc: "Refused to display 'https://docs.google.com/document/d/1ILh9lSW4d05qJD2rSKxep0WnJUfNCcAPCafKZeESweE/pub' in a frame because it set 'X-Frame-Options' to 'SAMEORIGIN'."

http://www.open-tx.org/2014/07/19/Lua-reference-guide/

Hi Folks,

A member of the French forum named SkyRaccoon has created a very nice website with some high quality pictures for Horus radios.
Here is his website: http://www.skyraccoon.com/

I think it could be nice to mention it somewhere in order to give him som worldwide visibility.
Maybe in the section Document or in the section Download/OpenTX Images.

What do you think?

BR,
Seb

Step missing between "create subfolder" and "place the two..." steps. Should insert instruction to modify the path to reflect the model's subfolder, or enable relative paths.

http://jenkins.open-tx.org/nightly-20/

Can we rename the folders so that they use the ISO 8601 standard? This way, the most recent build will be at the bottom of the page, rather than half way down the page.
Also, this is considered good practise when maintaining a list of dates and prevents confusion for those that don't use MM-DD-YYYY date format.

I'm aware that I can sort the folders with "last modified" link.

I am regularly seeing empty posts that just have names as description in the RSS feed. For example:

31. Mai 2017, 16:55
    Roberto
32. Mai 2017, 16:55
    Eugene LaFaille
33. Mai 2017, 16:55
    Andrew Fernie
34. Mai 2017, 16:55
    Michael Napolitan

They link to pages like this: http://www.open-tx.org/2017/05/31/2015-04-22-Roberto-feedback

I am not sure why these are generated, but it's always confusing to see "oh news from OpenTX" and then there's nothing.

My changes is bold just to draw attention to proposed changes. If accepted the actual changes may not be in bold.

layout: page
title: Welcome to OpenTX
tagline: Improving yourTx
redirect_from: "open-tx.org"

{% include JB/setup %}

OpenTX is open source firmware for RC radio transmitters. It is meant for users who are comfortable with computers, trying new things, willing to research how the system works and trouble shoot when needed. The firmware is highly configurable and brings much more features than found in traditional radios. The daily feedback from the thousands of users ensures the continued stability and quality of the firmware.

• Read more about which radios are supported.

The team also develops the OpenTX Companion transmitter support software. OpenTX Companion is used for many different tasks like downloading and loading OpenTX firmware to the radio, backing up model settings, editing settings and running radio simulators.

• OpenTX Companion is available for Windows, Apple OSX and Linux.

One of the main features of OpenTX is its use of a sound pack placed on a microSD card. This sound pack contain audio files files used for sounds and announcements.

• Sound packs are available from the Downloads page and by using Companion.

**REMOVE this block of text.**
There are two applications available for creating and managing the soundfiles used by OpenTX.   
**OpenTX Speaker** is used to generate voice files for OpenTX by using synthetic speech. **OpenTX Recorder** is used to record voice files via a microphone.   
Both programs can generate sound files for all OpenTX voice languages. Every radio message, including system messages, can be changed.   
OpenTX Speaker and OpenTXRecorder are available for Windows7.

New Lua section

Lua Scripts

OpenTX supports Lua scripts that can be used for new model and other wizards, display custom telemetry screens, complicated mixes and configure devices using the s.port protocol. Advanced users with command line experience will find many uses for this powerful feature.
-To learn more read the documentation.

Installation

1. Read the documentation.
2. Download and install the latest version on Companion.
3. Use Companion to download the firmware.
4. Use Companion to write the firmware to the transmitter.

**REMOVE this block of text.**
The first step to upgrade your radio with the latest OpenTX version is to install OpenTX Companion on your computer.  
Then you select the firmware configuration you want and let OpenTX Companion download and install it to your radio.  
You find the latest OpenTX Companion versions in [Downloads](downloads.html).

The news section is too long. Is there a way to limit the list to a certain number of items and then place the entire list on a news-archive.md file with a link to it?

News

{% for post in site.tags.News %}
{% include display_flags.html %} {{ post.title }} ({{ post.date | date:"%Y-%m-%d" }})
{% endfor %}

On the https://www.open-tx.org/radios.html page, the radios names are shown as PNG images.
This means that we can't search the name of a radio and that we can't find that page using search engines and searching for a radio.

I suggest using text instead for the radios names.

The download link at http://www.open-tx.org/2015/04/18/M2560-DIY-radio-documentation is "dead".

Moved here from
opentx/opentx#3615

On this page
http://www.open-tx.org/lua-instructions.html
Could this link be added
https://www.gitbook.com/book/opentx/opentx-lua-reference-guide/details

On this page
http://www.open-tx.org/documents
Could this link be added
http://www.open-tx.org/lua-instructions.html

On this page
http://www.open-tx.org/
Could this link be added
http://www.open-tx.org/lua-instructions.html

Suggestion:
Remove documentation links from everywhere on the site and place all documentation links only on the documentation page. This helps beginners access the most recent documentation. For long time users they can still have access to older documentation if they are running older versions.

I am willing to volunteer my time to help look after the website.

Being relatively new (2014) to OpenTX I am still looking for documentation. I find that there is no one place where it is complete or where clarification can be sought and then have the documentation updated. Documentation also evolves with code changes and to cater to different audiences. Having a Business and Systems Analyst background it is my opinion that often there are two (or more audiences).

1. The developers, technically advanced users
2. The common users, the beginner

The documentation for OpenTX seems to have gotten fragmented along these lines. A new user or even someone like myself with some experience has to go searching amongst different content creators for information.

Some thoughts on adding documenters, improving documentation and locating it.
(I may be using the wrong terms but I hope the general idea is clear.)

GitHub/GitBook

• Create a new GitHub linked to the existing GitBook User Manual.This provides a clean separation between user documentation and code and the documenters and the developers.
• Developers interested in documentation can join this new GitHub.
• Developers/Administrators not interested or who don't have time for documentation issues won't have to deal with the added volume of non development related issues that need to be dealt with.
• Use "Issues" to request documentation clarification and additions (forums are still the starting point when a user has questions but over time the more active and advanced users will see that maybe the documentation needs updating and create an issue). https://github.com/opentx/opentx-taranis-manual/issues
• Administrators can then tag issues with say new section, new page in existing section, update existing documentation, needs discussion... Along similar lines to development issues.
• Users can also submit documentation write ups under an open issue, have them discussed, once consensus is achieved administrators then merge the changes.
• Administrators can checkout/take ownership of issues to work on similar to how code is treated.
• All of the above done under the OpenTX banner.
• A new set of documenters may end up joining just like developers have.

Website

• Create archive pages and move information related to previous versions to those pages.
• Separate out "official" content and links to community created content or always place official content at the top (not in chronological order).
• Archive links to community content as official content encompasses it