OpenTX - Nightly builds for pre-2.0 testing

[bertrand35]

There you go, the nightly build server is now up. It will build the [next] branch every night, the firmware comes with default options for Taranis, sky9x, gruvin9x and 9x/9xr, along with a companion installer:
- nightly builds:
- millestone and feature list: https://github.com/opentx/opentx/issues/milestones
- commits list: https://github.com/opentx/opentx/commits/next
- 2.0 addendum to the OpenTX manual (work in progress): https://docs.google.com/document/d/1lL8 ... sp=sharing

One BIG warning to start with of course: BACKUP YOUR EEPROM! Next has a completely different EEPROM structure, and the first time you turn the radio on after flashing this it will get automatically upgraded (for Taranis/sky9x, AVR boards need the upgrade done by companion as usual). The result is of course not useable with the release version anymore, so you need a backup to go back to normal once you're done playing around (the fastest way is to write the backup with c9x on the test firmware, power the radio off BEFORE taking the USB cable out, then plug it back in with the radio still off to flash release firmware). Also the current EEPROM format in Next will not be the one present in the final release (not all the expected new features are in at this point), so you should know that your experiments will probably have to be discarded. Don't rely on that firmware too much and start fine-tuning your competition model unless you're OK to restart from scratch after release

With that said, what we're primarily interested in:
- The EEPROM conversion. It will not take advantage of the new features as it can't guess what you want to do, but it should create equivalences that do not break the functionality of existing models (see 2nd post for exceptions). So doing a little round of your models after upgrade to see if they still work as intended would be nice.
- The inputs system. There's no manual yet, but it should be rather straightforward and correspond to what was discussed on the English forum this summer. The former D/R screen now allows you to define up to 64 "inputs" on which you can set the old parameters but also define the input control from all sources including telemetry, a fixed input (max) etc. Trim is moved there too. Mixer sources include all raw sources as usual, plus all defined inputs. This should take all the input formatting out of the mixer and thus make it more clear and simple, while adding flexibility. Would be good to know what you think of it
- Of course any other bug you'd find!

Note that the firmware now incorporates a bootloader that is accessible by holding both horizontal trims inwards while powering the radio up. SD and EEPROM access have been removed from the main firmware (when the radio is ON it now appears as a standard joystick with the first 8 channels supplied as analog axes and the next 8 as buttons), so to access SD and EEPROM the radio must be powered on in bootloader mode.

----

EDIT:
2.0 is now released, please visit www.open-tx.org to download the latest version.
Nightly builds now available are:
- Current status of the 2.0 branch (stable, no more new features, only bugfixes if needed): http://jenkins.open-tx.org/nightly-20/
- Current status of the 2.1 branch, which will be the next major version (read above, same warnings apply): http://jenkins.open-tx.org/nightly-21/

[Kilrah]

One important thing to note is that trim settings will NOT be converted if changed from the default. So any "trim off", cross trim setting etc will be discarded during conversion.
Also, Sxxt switches previously available to trigger custom functions do not exist anymore. One should now use a "Sticky" logical switch for this, there is no automatic conversion. LSx Stcky SA- SA- is the equivalent of SA-t.
Same for SH↓s and SH↓l, these are now replaced with the "Edge" logical switch. That type of switch will only trigger if the selected input is activated for a duration that matches the configured span, so you can have any number of different durations you want.

[rdeanchurch]

Anyone else having trouble running companion on Ein Vista 32bit ?
error details:
"
Windows NT Version 6.0 Build: 6002 Service Pack 2
Product (0x3): Windows Vista (TM) Home Premium
Edition: HomePremium
BuildString: 6002.18881.x86fre.vistasp2_gdr.130707-1535
Flavor: Multiprocessor Free
Architecture: X86
LCID: 1033
"
"
<?xml version="1.0" encoding="UTF-16"?>
<DATABASE>
<EXE NAME="companion.exe" FILTER="GRABMI_FILTER_PRIVACY">
<MATCHING_FILE NAME="avrdude.exe" SIZE="344078" CHECKSUM="0x4C0DA0E" MODULE_TYPE="WIN32" PE_CHECKSUM="0x63143" LINKER_VERSION="0x10000" LINK_DATE="08/30/2011 22:02:40" UPTO_LINK_DATE="08/30/2011 22:02:40" />
<MATCHING_FILE NAME="companion.exe" SIZE="5730304" CHECKSUM="0xA00E399B" MODULE_TYPE="WIN32" PE_CHECKSUM="0x583082" LINKER_VERSION="0x0" LINK_DATE="03/06/2014 10:57:42" UPTO_LINK_DATE="03/06/2014 10:57:42" />
<MATCHING_FILE NAME="dfu-util.exe" SIZE="117269" CHECKSUM="0x1097DA95" MODULE_TYPE="WIN32" PE_CHECKSUM="0x23DF8" LINKER_VERSION="0x10000" LINK_DATE="10/07/2012 16:46:07" UPTO_LINK_DATE="10/07/2012 16:46:07" />
<MATCHING_FILE NAME="libusb-1.0.dll" SIZE="286342" CHECKSUM="0xC962E14F" BIN_FILE_VERSION="1.0.9.0" BIN_PRODUCT_VERSION="1.0.9.0" PRODUCT_VERSION="1.0.9" FILE_DESCRIPTION="C library for writing portable USB drivers in userspace" COMPANY_NAME="libusb.org" PRODUCT_NAME="libusb-1.0" FILE_VERSION="1.0.9" ORIGINAL_FILENAME="libusb-1.0.dll" INTERNAL_NAME="libusb" LEGAL_COPYRIGHT="See individual source files, GNU LGPL v2.1 or later." VERDATEHI="0x0" VERDATELO="0x0" VERFILEOS="0x40004" VERFILETYPE="0x2" MODULE_TYPE="WIN32" PE_CHECKSUM="0x4AEF9" LINKER_VERSION="0x10000" UPTO_BIN_FILE_VERSION="1.0.9.0" UPTO_BIN_PRODUCT_VERSION="1.0.9.0" LINK_DATE="06/20/2013 22:54:03" UPTO_LINK_DATE="06/20/2013 22:54:03" EXPORT_NAME="libusb-1.0.dll" VER_LANGUAGE="English (United States) [0x409]" />
<MATCHING_FILE NAME="libusb0.dll" SIZE="43520" CHECKSUM="0x34C36373" BIN_FILE_VERSION="0.1.12.1" BIN_PRODUCT_VERSION="0.1.12.1" PRODUCT_VERSION="0.1.12.1" FILE_DESCRIPTION="LibUSB-Win32 - DLL" COMPANY_NAME="http://libusb-win32.sourceforge.net" PRODUCT_NAME="LibUSB-Win32 - DLL" FILE_VERSION="0.1.12.1" ORIGINAL_FILENAME="libusb0.dll" INTERNAL_NAME="libusb0.dll" LEGAL_COPYRIGHT="@ 2002-2005 S. Meyer, <[email protected]>" VERDATEHI="0x0" VERDATELO="0x0" VERFILEOS="0x40004" VERFILETYPE="0x2" MODULE_TYPE="WIN32" PE_CHECKSUM="0x188B8" LINKER_VERSION="0x10000" UPTO_BIN_FILE_VERSION="0.1.12.1" UPTO_BIN_PRODUCT_VERSION="0.1.12.1" LINK_DATE="03/20/2007 10:33:19" UPTO_LINK_DATE="03/20/2007 10:33:19" EXPORT_NAME="libusb0.dll" VER_LANGUAGE="English (United States) [0x409]" />
<MATCHING_FILE NAME="msvcp100.dll" SIZE="421200" CHECKSUM="0x3660E406" BIN_FILE_VERSION="10.0.40219.325" BIN_PRODUCT_VERSION="10.0.40219.325" PRODUCT_VERSION="10.00.40219.325" FILE_DESCRIPTION="Microsoft® C Runtime Library" COMPANY_NAME="Microsoft Corporation" PRODUCT_NAME="Microsoft® Visual Studio® 2010" FILE_VERSION="10.00.40219.325" ORIGINAL_FILENAME="msvcp100.dll" INTERNAL_NAME="msvcp100.dll" LEGAL_COPYRIGHT="© Microsoft Corporation. All rights reserved." VERDATEHI="0x0" VERDATELO="0x0" VERFILEOS="0x40004" VERFILETYPE="0x2" MODULE_TYPE="WIN32" PE_CHECKSUM="0x67E28" LINKER_VERSION="0xA0000" UPTO_BIN_FILE_VERSION="10.0.40219.325" UPTO_BIN_PRODUCT_VERSION="10.0.40219.325" LINK_DATE="06/11/2011 01:00:49" UPTO_LINK_DATE="06/11/2011 01:00:49" EXPORT_NAME="MSVCP100.dll" VER_LANGUAGE="English (United States) [0x409]" />
<MATCHING_FILE NAME="msvcr100.dll" SIZE="773968" CHECKSUM="0x6AD18B2" BIN_FILE_VERSION="10.0.40219.325" BIN_PRODUCT_VERSION="10.0.40219.325" PRODUCT_VERSION="10.00.40219.325" FILE_DESCRIPTION="Microsoft® C Runtime Library" COMPANY_NAME="Microsoft Corporation" PRODUCT_NAME="Microsoft® Visual Studio® 2010" FILE_VERSION="10.00.40219.325" ORIGINAL_FILENAME="msvcr100_clr0400.dll" INTERNAL_NAME="msvcr100_clr0400.dll" LEGAL_COPYRIGHT="© Microsoft Corporation. All rights reserved." VERDATEHI="0x0" VERDATELO="0x0" VERFILEOS="0x40004" VERFILETYPE="0x2" MODULE_TYPE="WIN32" PE_CHECKSUM="0xC0A0A" LINKER_VERSION="0xA0000" UPTO_BIN_FILE_VERSION="10.0.40219.325" UPTO_BIN_PRODUCT_VERSION="10.0.40219.325" LINK_DATE="06/11/2011 01:00:14" UPTO_LINK_DATE="06/11/2011 01:00:14" EXPORT_NAME="MSVCR100.dll" VER_LANGUAGE="English (United States) [0x409]" />
<MATCHING_FILE NAME="phonon4.dll" SIZE="270848" CHECKSUM="0x30339177" BIN_FILE_VERSION="4.4.0.0" BIN_PRODUCT_VERSION="4.4.0.0" FILE_DESCRIPTION="C++ application development framework." COMPANY_NAME="Digia Plc and/or its subsidiary(-ies)" PRODUCT_NAME="Qt4" FILE_VERSION="4.4.0.0" ORIGINAL_FILENAME="phonon4.dll" LEGAL_COPYRIGHT="Copyright (C) 2013 Digia Plc and/or its subsidiary(-ies)." VERDATEHI="0x0" VERDATELO="0x0" VERFILEOS="0x4" VERFILETYPE="0x2" MODULE_TYPE="WIN32" PE_CHECKSUM="0x42A2A" LINKER_VERSION="0x40028" UPTO_BIN_FILE_VERSION="4.4.0.0" UPTO_BIN_PRODUCT_VERSION="4.4.0.0" LINK_DATE="06/27/2013 08:19:50" UPTO_LINK_DATE="06/27/2013 08:19:50" EXPORT_NAME="phonon4.dll" VER_LANGUAGE="English (United States) [0x409]" />
<MATCHING_FILE NAME="pthreadVC2.dll" SIZE="55808" CHECKSUM="0x322CFCA7" BIN_FILE_VERSION="2.9.0.0" BIN_PRODUCT_VERSION="2.9.0.0" PRODUCT_VERSION="2, 9, 0, 0" FILE_DESCRIPTION="MS C x86" COMPANY_NAME="Open Source Software community LGPL" PRODUCT_NAME="POSIX Threads for Windows LPGL" FILE_VERSION="2, 9, 0, 0" ORIGINAL_FILENAME="pthreadVC2.DLL" INTERNAL_NAME="pthreadVC2.DLL" LEGAL_COPYRIGHT="Copyright (C) Project contributors 2012" VERDATEHI="0x0" VERDATELO="0x0" VERFILEOS="0x4" VERFILETYPE="0x2" MODULE_TYPE="WIN32" PE_CHECKSUM="0x0" LINKER_VERSION="0x0" UPTO_BIN_FILE_VERSION="2.9.0.0" UPTO_BIN_PRODUCT_VERSION="2.9.0.0" LINK_DATE="05/26/2012 15:36:05" UPTO_LINK_DATE="05/26/2012 15:36:05" EXPORT_NAME="pthreadVC2.dll" VER_LANGUAGE="English (United States) [0x409]" />
<MATCHING_FILE NAME="QtCore4.dll" SIZE="2598912" CHECKSUM="0x416815D0" BIN_FILE_VERSION="4.8.5.0" BIN_PRODUCT_VERSION="4.8.5.0" FILE_DESCRIPTION="C++ application development framework." COMPANY_NAME="Digia Plc and/or its subsidiary(-ies)" PRODUCT_NAME="Qt4" FILE_VERSION="4.8.5.0" ORIGINAL_FILENAME="QtCore4.dll" LEGAL_COPYRIGHT="Copyright (C) 2013 Digia Plc and/or its subsidiary(-ies)." VERDATEHI="0x0" VERDATELO="0x0" VERFILEOS="0x4" VERFILETYPE="0x2" MODULE_TYPE="WIN32" PE_CHECKSUM="0x283BEB" LINKER_VERSION="0x40055" UPTO_BIN_FILE_VERSION="4.8.5.0" UPTO_BIN_PRODUCT_VERSION="4.8.5.0" LINK_DATE="06/27/2013 08:09:56" UPTO_LINK_DATE="06/27/2013 08:09:56" EXPORT_NAME="QtCore4.dll" VER_LANGUAGE="English (United States) [0x409]" />
<MATCHING_FILE NAME="QtGui4.dll" SIZE="8581632" CHECKSUM="0x2261811F" BIN_FILE_VERSION="4.8.5.0" BIN_PRODUCT_VERSION="4.8.5.0" FILE_DESCRIPTION="C++ application development framework." COMPANY_NAME="Digia Plc and/or its subsidiary(-ies)" PRODUCT_NAME="Qt4" FILE_VERSION="4.8.5.0" ORIGINAL_FILENAME="QtGui4.dll" LEGAL_COPYRIGHT="Copyright (C) 2013 Digia Plc and/or its subsidiary(-ies)." VERDATEHI="0x0" VERDATELO="0x0" VERFILEOS="0x4" VERFILETYPE="0x2" MODULE_TYPE="WIN32" PE_CHECKSUM="0x83BF14" LINKER_VERSION="0x40055" UPTO_BIN_FILE_VERSION="4.8.5.0" UPTO_BIN_PRODUCT_VERSION="4.8.5.0" LINK_DATE="06/27/2013 08:16:40" UPTO_LINK_DATE="06/27/2013 08:16:40" EXPORT_NAME="QtGui4.dll" VER_LANGUAGE="English (United States) [0x409]" />
<MATCHING_FILE NAME="QtNetwork4.dll" SIZE="1053696" CHECKSUM="0xDA3E6448" BIN_FILE_VERSION="4.8.5.0" BIN_PRODUCT_VERSION="4.8.5.0" FILE_DESCRIPTION="C++ application development framework." COMPANY_NAME="Digia Plc and/or its subsidiary(-ies)" PRODUCT_NAME="Qt4" FILE_VERSION="4.8.5.0" ORIGINAL_FILENAME="QtNetwork4.dll" LEGAL_COPYRIGHT="Copyright (C) 2013 Digia Plc and/or its subsidiary(-ies)." VERDATEHI="0x0" VERDATELO="0x0" VERFILEOS="0x4" VERFILETYPE="0x2" MODULE_TYPE="WIN32" PE_CHECKSUM="0x10F549" LINKER_VERSION="0x40055" UPTO_BIN_FILE_VERSION="4.8.5.0" UPTO_BIN_PRODUCT_VERSION="4.8.5.0" LINK_DATE="06/27/2013 08:10:40" UPTO_LINK_DATE="06/27/2013 08:10:40" EXPORT_NAME="QtNetwork4.dll" VER_LANGUAGE="English (United States) [0x409]" />
<MATCHING_FILE NAME="QtXml4.dll" SIZE="356352" CHECKSUM="0xCC34EBFE" BIN_FILE_VERSION="4.8.5.0" BIN_PRODUCT_VERSION="4.8.5.0" FILE_DESCRIPTION="C++ application development framework." COMPANY_NAME="Digia Plc and/or its subsidiary(-ies)" PRODUCT_NAME="Qt4" FILE_VERSION="4.8.5.0" ORIGINAL_FILENAME="QtXml4.dll" LEGAL_COPYRIGHT="Copyright (C) 2013 Digia Plc and/or its subsidiary(-ies)." VERDATEHI="0x0" VERDATELO="0x0" VERFILEOS="0x4" VERFILETYPE="0x2" MODULE_TYPE="WIN32" PE_CHECKSUM="0x66B92" LINKER_VERSION="0x40055" UPTO_BIN_FILE_VERSION="4.8.5.0" UPTO_BIN_PRODUCT_VERSION="4.8.5.0" LINK_DATE="06/27/2013 08:10:01" UPTO_LINK_DATE="06/27/2013 08:10:01" EXPORT_NAME="QtXml4.dll" VER_LANGUAGE="English (United States) [0x409]" />
<MATCHING_FILE NAME="SDL.dll" SIZE="303616" CHECKSUM="0x84449468" BIN_FILE_VERSION="1.2.14.0" BIN_PRODUCT_VERSION="1.2.14.0" VERDATEHI="0x0" VERDATELO="0x0" VERFILEOS="0x40004" VERFILETYPE="0x2" MODULE_TYPE="WIN32" PE_CHECKSUM="0x502B4" LINKER_VERSION="0x10000" UPTO_BIN_FILE_VERSION="1.2.14.0" UPTO_BIN_PRODUCT_VERSION="1.2.14.0" LINK_DATE="01/15/2012 16:39:02" UPTO_LINK_DATE="01/15/2012 16:39:02" EXPORT_NAME="SDL.dll" />
<MATCHING_FILE NAME="simulator.exe" SIZE="3908608" CHECKSUM="0xD7DA367A" MODULE_TYPE="WIN32" PE_CHECKSUM="0x3C087B" LINKER_VERSION="0x0" LINK_DATE="02/20/2014 06:49:29" UPTO_LINK_DATE="02/20/2014 06:49:29" />
<MATCHING_FILE NAME="Uninstall.exe" SIZE="51825" CHECKSUM="0xE7DCDD87" MODULE_TYPE="WIN32" PE_CHECKSUM="0x0" LINKER_VERSION="0x60000" LINK_DATE="12/05/2009 22:50:46" UPTO_LINK_DATE="12/05/2009 22:50:46" />
<MATCHING_FILE NAME="xerces-c_3_1.dll" SIZE="1935872" CHECKSUM="0xBE3D58B" BIN_FILE_VERSION="3.1.1.0" BIN_PRODUCT_VERSION="3.1.1.0" PRODUCT_VERSION="3, 1, 1" FILE_DESCRIPTION="Shared Library for Xerces-C++ Version 3.1.1" COMPANY_NAME="Apache Software Foundation" PRODUCT_NAME="Xerces-C++ Version 3.1.1" FILE_VERSION="3, 1, 1" ORIGINAL_FILENAME="xerces-c_3_1.dll" INTERNAL_NAME="xerces-c_3_1.dll" LEGAL_COPYRIGHT="Copyright © 1999-2010 Apache Software Foundation; subject to licensing terms" VERDATEHI="0x0" VERDATELO="0x0" VERFILEOS="0x40004" VERFILETYPE="0x2" MODULE_TYPE="WIN32" PE_CHECKSUM="0x1E6590" LINKER_VERSION="0x0" UPTO_BIN_FILE_VERSION="3.1.1.0" UPTO_BIN_PRODUCT_VERSION="3.1.1.0" LINK_DATE="04/23/2010 13:33:10" UPTO_LINK_DATE="04/23/2010 13:33:10" EXPORT_NAME="xerces-c_3_1.dll" VER_LANGUAGE="English (United States) [0x409]" />
</EXE>
<EXE NAME="QtGui4.dll" FILTER="GRABMI_FILTER_THISFILEONLY">
<MATCHING_FILE NAME="QtGui4.dll" SIZE="8581632" CHECKSUM="0x2261811F" BIN_FILE_VERSION="4.8.5.0" BIN_PRODUCT_VERSION="4.8.5.0" FILE_DESCRIPTION="C++ application development framework." COMPANY_NAME="Digia Plc and/or its subsidiary(-ies)" PRODUCT_NAME="Qt4" FILE_VERSION="4.8.5.0" ORIGINAL_FILENAME="QtGui4.dll" LEGAL_COPYRIGHT="Copyright (C) 2013 Digia Plc and/or its subsidiary(-ies)." VERDATEHI="0x0" VERDATELO="0x0" VERFILEOS="0x4" VERFILETYPE="0x2" MODULE_TYPE="WIN32" PE_CHECKSUM="0x83BF14" LINKER_VERSION="0x40055" UPTO_BIN_FILE_VERSION="4.8.5.0" UPTO_BIN_PRODUCT_VERSION="4.8.5.0" LINK_DATE="06/27/2013 08:16:40" UPTO_LINK_DATE="06/27/2013 08:16:40" EXPORT_NAME="QtGui4.dll" VER_LANGUAGE="English (United States) [0x409]" />
</EXE>
<EXE NAME="kernel32.dll" FILTER="GRABMI_FILTER_THISFILEONLY">
<MATCHING_FILE NAME="kernel32.dll" SIZE="892928" CHECKSUM="0x1D9208D0" BIN_FILE_VERSION="6.0.6002.18704" BIN_PRODUCT_VERSION="6.0.6002.18704" PRODUCT_VERSION="6.0.6001.18000" FILE_DESCRIPTION="Windows NT BASE API Client DLL" COMPANY_NAME="Microsoft Corporation" PRODUCT_NAME="Microsoft® Windows® Operating System" FILE_VERSION="6.0.6001.18000 (longhorn_rtm.080118-1840)" ORIGINAL_FILENAME="kernel32" INTERNAL_NAME="kernel32" LEGAL_COPYRIGHT="© Microsoft Corporation. All rights reserved." VERDATEHI="0x0" VERDATELO="0x0" VERFILEOS="0x40004" VERFILETYPE="0x2" MODULE_TYPE="WIN32" PE_CHECKSUM="0xDDB85" LINKER_VERSION="0x60000" UPTO_BIN_FILE_VERSION="6.0.6002.18704" UPTO_BIN_PRODUCT_VERSION="6.0.6002.18704" LINK_DATE="09/28/2012 16:13:42" UPTO_LINK_DATE="09/28/2012 16:13:42" EXPORT_NAME="KERNEL32.dll" VER_LANGUAGE="English (United States) [0x409]" />
</EXE>
</DATABASE>
"

[rperkins]

Hi
thanks for the information
dont see a linux build for companion
Maybe there isnt enough demand ?

I see from the information above that qt 4.8.5 was utilized
https://github.com/opentx/opentx/issues/772

MATCHING_FILE NAME="QtCore4.dll" SIZE="2598912" CHECKSUM="0x416815D0" BIN_FILE_VERSION="4.8.5.0" BIN_PRODUCT_VERSION="4.8.5.0" FILE_DESCRIPTION="C++ application development framework."

[bertrand35]

Are you on Fedora?

[rperkins]

Sorry, i can see my post was confusing.

Yes for the nightly build i would use fedora.

For the question about the qt version the distro is tiny core linux. I am working on a bootable iso that includes companion,eepe,kkmulticopter flash tool and the related drivers.

[rdeanchurch]

Obviously my previous post was too long, Sorry.

Should Companion 1.99 run on Win Vista 32bit? ??

[jonlowe]

Is this the best place to ask questions about the Nightly Builds and Companion 1.99? Or where would you prefer we ask them? I loaded 1.99 on Windows 7 32 bit, successfully, and have questions about the new Inputs menu.

[Kilrah]

This thread should be good.

Sent via mobile

[jonlowe]

Thanks, Kilrah. On the new Inputs menu item, where do I find the equivalent of "Side" in the old Sticks menu on the Taranis, or "Stick Side" shown in C9x? It allowed me to set separate rates and expos on each side of neutral. I find this particularly useful on elevator and I also use it on rudder to give the same feel on each side of neutral.

I looked at the "Curve" menu item, but it doesn't allow me to do the same thing.

If I import an eepe created in the stable verion of OpenTx into Companion 1.99, it allows me to edit rate and expo on each side of neutral. But I can find no way to create that in 1.99.

Frankly, I liked the interface on Er9x better than on OpenTx for this function, as I could set different rates and expos on one screen, simply by moving the stick to one side or the other from neutral. I only needed one screen per dual or triple rate. But I need at least the functionality that current OpenTX has with having two separate screens for each side of neutral for each rate.

Thanks,
Jon

[Helle]

Hy,
Testing opentx 1.99 companion1.99

missing funktions
no single side with expo at inputs at opentx
no curve-generator for expo or singel + expo at companion1.99

Helle

[jonlowe]

Helle,
Glad you found the same thing. I thought I was going crazy!

[Helle]

Hi

dont see a linux/ubuntu build for companion
only a windows *.exe

dont like to take the *.bin to my transmitter
simu test for ubuntu would be ok and enough

Helle

[Helle]

Hi,

what are edge and stky at custom Functions for
in details please

Helle

[dvogonen]

The curve generation and model wizard are part of the model edit. That part of Companion has been heavily updated to handle the new eeprom format. The two functions are not yet re-implemented, but the plan is to bring them back. I can not guarantee that we will have any of them ready for 2.0. I am however working on a new Wizard and it will certainly be back in 2.1 (or whatever it is called).

[jonlowe]

What is the answer on the missing "stick sides" function?

I would suggest delaying 2.0 until all previously available features can be implemented. It will be viewed as going backwards, unless those features are available.

[DarKHawK]

USB emulated joystick.
How do I use the joystick mode , tried SA up also tried holding exit key while plugging in usb and nothing.



Sent from my Nexus 7 using Tapatalk

[dvogonen]

I do not think that USB support has been added yet. Bertrand mentioned somewhere that his plan is to first add Mikes boot loader and the the USB support contributed by Damjan Adamic

[DarKHawK]

OK thanks


Sent from my Nexus 7 using Tapatalk

[bertrand35]

'Side' is back in a dedicated branch. I didn't know whether it was still useful. Comments appreciated on this.

[Kilrah]

To me it isn't as a curve can be used instead, and the "side" option breaks the paradigm of "only one active line"...
Not to mention that in "normal" cases there is little point in having different rates per side in the first place. My guess is you're using it to make your throws symmetrical, but you should not use the rates for that purpose.

[jhsa]

I've been told a while ago that in opentx the best was to use the rates to make the throws symmetrical And that was how I did set my plane up, and it works very well. I tried other options, (like the sym option) and the rates worked best. I do think that the rates should affect both sides separately.

Just my 2c

[Kilrah]

No, the limits are the place to do it (without using the sym option on most setups).

[jhsa]

having to use offset how do you keep the throws symmetrical using the limits and without introducing dead band? I mean with the same amount of throw each side?

I use the Rates menu..

[Kilrah]

You do not need to use offset. See manual:

Then adjust the min and max limits. These should be set so that:
- You have a little bit more throw than what you'll ever need
- There is no mechanical binding
- Throws are the same on both sides with full control input deflection

Once throws are equalised using limits, you don't need different throws on each side in rates anymore. Much easier and correct to set up, especially with more than one rate.

[jhsa]

it didn't work for me.. And I like to setup things different.. limits for me are limits and not travel adjustment.


I find it such a shame if the ability to adjust rates separately for both sides is removed from the fw.. Sad and a step backwards

[rdeanchurch]

Obviously my previous post was too long, Sorry.

Should Companion 1.99 run on Win Vista 32bit? ??

Status change....New version of Companion
companionInstall_v1.99_78f36a0.exe
works on XP 32bit.

Thank you very much!

[rdeanchurch]

Obviously my previous post was too long, Sorry.

Should Companion 1.99 run on Win Vista 32bit? ??

Status change....New version of Companion
companionInstall_v1.99_78f36a0.exe
works on Vista 32bit.

Thank you very much!

Oops wrong computer meant Vista

[jonlowe]

'Side' is back in a dedicated branch. I didn't know whether it was still useful. Comments appreciated on this.

Absolutely an essential function. Very important for feel, especially for F3A aircraft. We VERY seldom use symmetrical rates and expo on both sides of elevator, and many of us use unsymmetrical rates on rudder so that stick throw is the same for knife edge both ways. Knife edge is rarely symmetrical due to aerodynamics. Some people use different rate or expo or both on aileron to compensate for small hands.

I first asked for this either in er9x or th9x (can't remember which). It was added in days. Opentx inherited it from er9x, but made it harder to use by not being able to do both sides on a single line by moving the stock from center while adjusting rate and expo. Virtually every medium to high end radio has this feature, and enabled by simply moving the stick. If you want symmetrical changes, you simply hold the stick at center.

The current Opentx firmware (pre 1.99) greatly complicates this by requiring two lines for x>0 and x<0. Every time I add a duo or triple rate I have to create two lines instead of one, and if I want to change both sides I have to edit two lines.

I fail to see why a feature would be removed because some people don't use it. 2.0 should expand on available features. If you want to make it a selectable option, like Heli or Fai modes, OK. But don't remove it.

Jon

[jhsa]

Jon, I wouldn't say it better. Tottally agree with you.
+1 here

Joao

Sent from my GT-I9195 using Tapatalk