FrSky Horus HW and FrTX OS discussion - RC Groups
Thread Tools
Sep 02, 2016, 07:51 AM
Registered User
Discussion

FrSky Horus HW and FrTX OS discussion


This thread is dedicated to FrSky Horus HW and FrTX OS questions and updates. Here is the public github for bug/issue reports, as well as suggestions: https://github.com/FrSky-OS/X12S-bug-report

We will maintain the first several posts with useful index, update information and links.
Last edited by FrSky RC; Oct 11, 2016 at 03:27 AM.
Sign up now
to remove ads between posts
Sep 02, 2016, 07:53 AM
Registered User
https://www.frsky-rc.com/horus-x12s/
Version History
Ver1.2.12:
1. Add voice alarm for inactivity after 15 minutes (add nooperation.wav file to SOUNDS/en/SYSTEM)
2. Add repeated intervals for specialFunction
3. Add repeated intervals for telemetry alarms
4. Long press the power button to shut the radio down when SD error at boot time (bug fix)
5. Fix the midpoint jumping issue caused by TRIM when switching between the flight modes (disable Instant Trim function temporarily)
6. Fix the telemetry voice bug
7. Fix the keyboard locked bug
8. Fix the reset bug when long press the power button
9. When playing the audio file, search system disk first, and SD card under the same path later if no luck

Ver1.2.14:
1. Fix the issue of no access to the FLASH and SD card after reset
2. Fix the issue of system crash by wrong sized boot-up image

Ver1.2.18:
1. Improve the RF performance
2. Fix the issue of unable to delete the model file when copying due to the file name is too long

Ver1.2.20:
Note: rebind after FW upgrade
1. optimise IXJT and implement dual antennas technology (under the external antenna mode, both internal and external antennas will be functional, FPV drones are suggested to use this mode)
2. add fast switching by PgUp/PgDn for year, SYS/TELE for month
3. add LOGIC SW to the control source
4. add LogicSw to control the mixing switch
5. add multi-point curve, 11 points can be modified by the X-axis, beyond can be modified by the Y-axis (scroll up and down the curve control points in the edit mode by PgUp/PgDn)
6. fix the ailevator does not overlap RATES/EXPO curve problem under AIRPALNE NORMAL model

Ver1.2.21:
1. Fix the issue of invalid trim under GLIDER model
2. Add trim to the control source
3. Fix the bug of RF SWR

Ver1.2.22 (Beta)
1. Fix the bug of PIT->RUD screen crash under HELI model
2. Fix the bug of logic switch invalid under TIMER screen
3. Add the timer and battery voltage announcements on SPEC FUNC screen
4. Add audio alarm for vario under SPEC FUNC screen
5. Optimize the TELEMETRY SETUP screens in alphabetical orders
6. Fix the bug of time display error after GPS sensor connected
7. V1.2.22L supports localization language while V1.2.22S CHN supports Simplified Chinese

Ver1.2.23 (Beta)
1. Fix the data display error when 2pcs FLVSS are used together
2. Fix the model change bug
3. Add the upgrade function for S.Port devices in menu system

Ver1.2.24 (Beta)
1. Fix the bug of telemetry data decimal announcement
2. Fix the issue of screenshot incompatibility
3. Fix the issue of upgrade not working when there is no FIRMWARE folder under SD card
4. Fix the bug of SPEED no response when UP and DOWN have settings
5. THR MIX will be activated if no SW is chosen under ACT mode

Ver1.2.25 (Beta)
1. Fix the issue of wrong channel output when channel speed is changed
2. Fix the issue of celsMin data display
3. Fix the issue about logic sw
4. Fix the issue of thr cut

Ver1.3.01 (Beta)
1. Timer is added as a source of LSW.
2. Fix the bug of trim values can not be saved when flight mode is changed.
3. Fix the bug of minRSSI is always 0 when the model is changed.
4. Add the Center trim in Spec Function.
5. S6R/S8R can be configured in Horus.
6. Telemetry data can work as input sources.
7. SW warning can be set to active separately.
8. Fix the bug of values can not be saved in airbrake page.
9. Fix the bug of switch setting does not work in Thr curve page.

Ver1.4.01 (Beta)
1. FW increases to 9 flight modes, and all model types support flight mode control (except for the multicopter);
2. Put part of the icons into the flash;
3. When copying the model file, the suffix “_copy” is changed to the front “_”;
4. External module will set telemetry mode in bind mode;
5. Add external RF module S.Port switch, to avoid data conflicts on RFSystem interface;
6. Added R9M module power settings in RF System;
7. The distance between the model and the GPS sensor stops the calculation without receiving data;
8. Fix the problems of GPS sensor parameters DIST_Gno data;
9. Optimize model file switching speed;
10. Optimize curve editing to avoid data confusion;
11. Add the wireless tele transmission setting interface for the users on IOS side to send TELE data.

Ver1.4.02 (Beta)
1. Fix the issue of high-precision variometer sensor display;
2. Optimize the model change speed;
3. Fix the issue of Flight Mode not working after the transfer of the old version Airplane model file;
4. Flash file for 1.4.02 is the same as that for 1.4.01.
Last edited by FrSky RC; Aug 15, 2017 at 04:34 AM.
Sep 02, 2016, 08:03 AM
Registered User
Horus X12S Flashing Instructions: http://www.frsky-rc.com/download/vie...g Instructions
Credits go to Mike Dailey and Jan Urbanek with support from the OpenTX team members Bertrand Songis and Andre Bernet. FrSky website will be in sync if edits are made by Mike Dailey on RCG.

The document covers:
1. Flashing X12S Horus with OpenTX and contains step-by-step instructions on preparing the FrTX files so the system can be recovered to FrTX at a later date.
2. The detailed steps for setting up the OpenTX SD card, installing everything you need to flash X12S Horus with OpenTX 2.2. It includes options for recovering the system back to FrTX after running OpenTX.
3. Backing up the FrTX bootloader and firmware using Companion to restore X12S Horus at a later date, but it is always good to have the actual FrTX files before installing OpenTX.
4. The FrTX flashing process for the normal FrTX firmware update process.

Updated on May. 31st, 2017
1. Updated document to cover the production OpenTX 2.2.0


Configuring a Simple Fixed Wing Model by Mike Dailey
Overview: This document is a step-by-step guide to configuring a simple fixed wing model in the FrSky Horus X12S using the FrTX OS. The sample model is fixed wing 65 span classic pattern competition aircraft called Tiporare. The FrTX OS has very powerful advanced programming options including Logical Switches and Free Mixers, but for this exercise we will use just simple basic configurations through the menu options.
FrSky-Horus-X12S---Fixed-...


Landing Gear Retraction Automation by Mike Dailey
Overview: This document is a step-by-step guide to configure a simple automated function using the FrSky Horus X12S with FrTX OS. FrTX OS is a menu driven system that provides the ability to quickly configure models using the built in functions, but FrTX also includes advanced features including Logical Switches and Free Mixers. The logic is programed so at a set altitude the landing gear is retracted and extends below the set altitude. The example provided can be used to configure other advanced functions, e.g. control throttle above set altitude or with a speed sensor control wing sweep on an F-14 Tomcat.
FrSky-Horus-X12S---Functi...


Configuring a Critical RSSI Level Alarm function to augment the built in RSSI Warning Alarm by Mike Dailey
Overview: This document is a step-by-step guide to configure a simple Critical RSSI Level Alarm function to augment the built in RSSI Warning Alarm with the FrSky Horus X12S FrTX OS using the Logic Switches. FrTX has a built in adjustable warning alarm setting for low RSSI and then the normal Telemetry Lost alert when the RF link is lost. It is sometimes helpful to have a second RSSI warning that can be set below the low RSSI warning, but before the Telemetry Lost alert. Using the Logic Switches and Special Functions a second adjustable RSSI Critical warning feature can be created.
FrSky Horus X12S - RSSI C...


FrSky XJT RF Module - 32 Channels by Mike Dailey
Overview: This document is a step-by-step guide for configuring the X12S FrTX OS and the external FrSky XJT RF module to add 16 channels to the X12S base 16 channel RF system. The configurations can be used as 32 individual channels (16 on internal IXJT and 16 on the XJT) or 16 redundant channels. There are many different combinations that can be created with the redundant RF links and this document covers the most common.
XJT 32 Channels
Last edited by FrSky RC; Jun 01, 2017 at 01:20 AM.
Sep 02, 2016, 02:45 PM
Registered User
It will be good to follow this thread. Thanks for starting it.
Sep 02, 2016, 03:13 PM
Registered User
what's the goal of this thread ?

you have had over 100 beta testers around the world (they had to pay $$$ for samples) and you didn't even consider many of their important suggestions
https://www.rcgroups.com/forums/show...&postcount=692

now that the Horus is been released it's time to start collecting all the hardware defects of the first batch LOL
Sep 02, 2016, 03:18 PM
Registered User
my question is: when are the Taranis V3, Horus X12 and X12D gonna be available ? https://fccid.io/pdf.php?id=3115467

thanks Frsky
Sep 02, 2016, 04:33 PM
Registered User
Great thread hopefully that provides direct manufacturers customer support, well played Frsky.
Sep 02, 2016, 08:26 PM
Noob
Edin508's Avatar
*subscribed*
Sep 02, 2016, 08:53 PM
Registered User
u2builder's Avatar
I am pleased to see this thread. While I have had a Taranis since it came out, I never felt all that comfortable with Open TX. I am more used to the menu system on my old Futaba 9C. I "think" in those terms. I think I am going to like Frsky OS, though I have already discovered a few features that I think should be added, and of course have a few questions.

It looks like it is designed to "speak" the name of the model if the user adds a folder of wav files of their model names. I have created such a file but don't see a name or location for it on the internal flash memory. I did add images and tracks to the memory.

How do I do the model name sounds that get "spoken" when I select a model?
Sep 02, 2016, 09:04 PM
AKA 8178 - MIke Dailey
Jet_Flyer's Avatar
Quote:
Originally Posted by u2builder
I am pleased to see this thread. While I have had a Taranis since it came out, I never felt all that comfortable with Open TX. I am more used to the menu system on my old Futaba 9C. I "think" in those terms. I think I am going to like Frsky OS, though I have already discovered a few features that I think should be added, and of course have a few questions.

It looks like it is designed to "speak" the name of the model if the user adds a folder of wav files of their model names. I have created such a file but don't see a name or location for it on the internal flash memory. I did add images and tracks to the memory.

How do I do the model name sounds that get "spoken" when I select a model?
Those model name sound files go in SOUNDS/en/model

Mike
Sep 02, 2016, 10:06 PM
Registered User
Quote:
Originally Posted by raydar
Great thread hopefully that provides direct manufacturers customer support, well played Frsky.
Yes,we will.
Sep 02, 2016, 10:27 PM
Registered User
canavanbob's Avatar
When will the support start?
Sep 02, 2016, 11:51 PM
Registered User
This support costs money.

It is not the free ( and fantastic ) support the OpenTx Devs provide just for the love of it. . .

Your Horus price is high because you obviously plan to recover your OS development costs.

Will this support cost be reflected in higher prices of your forthcoming receivers/sensors etc ? Or is it that you have factored it in on anticipation of higher sales of your products.
Sep 03, 2016, 12:04 AM
Registered User
Rick K.'s Avatar
I'm in.... subscribed
Sep 03, 2016, 12:26 AM
Registered User
mpjf01's Avatar
Quote:
Originally Posted by andytransonic
This support costs money.

It is not the free ( and fantastic ) support the OpenTx Devs provide just for the love of it. . .

Your Horus price is high because you obviously plan to recover your OS development costs.

Will this support cost be reflected in higher prices of your forthcoming receivers/sensors etc ? Or is it that you have factored it in on anticipation of higher sales of your products.
I suggest to you that the jury's still out on what support will be provided here. FRSKY could be hoping that other users will provide the answers to questions asked, if so there would be no cost or effort involved. Already happened with the first question asked here.

Someone with user name Frsky RC and representing FRSKY started this thread with the intent to provide information about their Horus firmware, how to use it, to collect bug reports (presumably) and notify fixes etc. I would love it if that someone could be left to do that, I want to see how well and how quickly FRSKY actually provides user support.

To that end, I think that it would be great, as an experiment, if other people who may know the answers to questions asked here refrained from answering them and left it to Frsky RC.